yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] nikodr:
I have been using r21 for a very long time never had such problems.
[Samsung Galaxy Nexus] bsmitty83:
The ROM is selinux enforcing, the no sim card message is an selinux denial . there is nothing I can do besides set the kernel permissive .
[Samsung Galaxy Nexus] nikodr:
[MENTION=4608636]bsmitty83[/MENTION] in kernel 3.4 the memory that is used for the ducatti to playback videos and under 3.0.x it is reserved and never free for use i think is shared and the total amount of ram is much more (on phones that have a 3.4 kernel that is).Would it be possible to backport the ram share feature of 3.4 kernel to 3.0.x ? That way the amount of free ram would be more.Does it have lots of dependencies?
[Samsung Galaxy Nexus] bsmitty83:
I uploaded R24 , again , a minor update to fix zram .

If you use zram you should download this kernel.

I still do not have a fix for touchwake ...... sorry :'(
[Samsung Galaxy Nexus] osm0sis:
Touchwake was working great for me in r23; I'll let you know how r24 does. I got some Synapse controls worked out for it and everything. I'll see about uploading tomorrow. :)
[Samsung Galaxy Nexus] :
I found R23 unstable (got random reboots during app installations from Play Store). Could that be related to the zram problem?

I can't provide any logs at the moment but will later if it's necessary.
[Samsung Galaxy Nexus] bamtan2:
I triple-checked, and after dalvik/cache wipe, only R23 shows no SIM card in latest ZMOD.

R24 bootloops for me. For some reason R24 failed to flash with the script set by Flashify (I didn't see the error in time, just the red "error" text), so I flashed it manually in TWRP. Even after dalvik/cache wipe, I get boot loops from android logo.
[Samsung Galaxy Nexus] bsmitty83:
No. I would blame selinux set enforcing for that as well .

Sounds about right for R23 , it was the 1st kernel to not set selinux , rather the Rom should dictate it .

As for the non-boot , that is bizarre . I didn't have any issues with it , and the only difference between R23 and R24 is 3 commits to zram that I reverted . try dirtyflashing your Rom then flash R24 maybe something got corrupted or some other random digital error.
[Samsung Galaxy Nexus] Martius:
I also get a bootloop with R24.

Latest ZMod, also tried reflashing it and the kernel, still bootloops.

I also checked the MD5 of the zip on my phone vs. the one XDA gives for the file, they do match.

Weird, since R23 runs (mostly, some random reboots...) fine.
[Samsung Galaxy Nexus] Fenvarien:
R24 flashed fine here and is booting too. But I'm using Ziyan's CM 12.1 8/31 build.
[Samsung Galaxy Nexus] bsmitty83:
R4 for FML is added to the Downloads Tab

Cm version will be linked here shortly

Heres a new test kernel for CM

please and thanks for testing
[Samsung Galaxy Nexus] lollipop:
haha,thats what i need to hear,so maybe waiting for new updated settings :victory:
[Samsung Galaxy Nexus] Nephilim:
Nope, I think I'll be sticking with my most recent settings, their working great.
[Samsung Galaxy Nexus] netreign:
sorry man but r4.1 not working..... constantly rebooting
[Samsung Galaxy Nexus] shadowam:
Edit ~~ Ignore, I'm dumb, flashed the old version...
[Samsung Galaxy Nexus] bsmitty83:
Did you remover the old PVR module before you flashed this ?
[Samsung Galaxy Nexus] MeHR@N:
Confirmed. I installed last CM12 and then R4.1 and wiped cache, but phone doesn't boot and just reboots on Google black screen.
[Samsung Galaxy Nexus] davinaizer:
bootloop here again with 4.1 on CM.

Does it help, if I boot to Recovery and get a dmesg?

If its bootlooping, is there a way to get a log?
[Samsung Galaxy Nexus] bsmitty83:
Are you guys removing the PVR module from cm12 before you flash the kernel ?
[Samsung Galaxy Nexus] _yen_:
Confirming that R4.1 still bootlops on cm12, not related to others PVR as I've removed /system/lib/modules.

yen
[Samsung Galaxy Nexus] davinaizer:
Yes sir! 100% sure. Bootlooping.

I decided to flash the Full_Auto_R4_FML-Ak.zip on CM, and guess what?

Cm Booted.

Is it possible?
[Samsung Galaxy Nexus] MeHR@N:
Yes but still have the problem.
[Samsung Galaxy Nexus] bsmitty83:
yes do you have audio as well ???
[Samsung Galaxy Nexus] davinaizer:
Your right, No sound... I didnt test other things...

If you need anything else to test, just let me know.
[Samsung Galaxy Nexus] bsmitty83:
K hangon
[Samsung Galaxy Nexus] bsmitty83:
ok flash this , see if it boots , if it does , check audio too

thanks :o
[Samsung Galaxy Nexus] davinaizer:
HA!!

IT HAS BOOT!!

Your the man!

I'll run some tests and Auntutu to check the power...!!

Edit: Still no sound.
[Samsung Galaxy Nexus] bsmitty83:
Sounds work as well ? If so I'll add the kernel to downloads tab for all
[Samsung Galaxy Nexus] bsmitty83:
OK next one should fix sound
[Samsung Galaxy Nexus] osm0sis:
Bootloop here on ZMoD as well, flashed over ZMoD's included kernel. The issue is likely fstab related. CM and AOSP have always differed in what flags their init binaries could handle. :good:

In the meantime, here's the updated GN Synapse Injector with T2W controls added (in Misc):

https://s.basketbuild.com/devs/osm0sis/osmods/

Peer5 d/l might be broken (lots of people unhappy with BB lately) so go with the normal d/l. It seems to work fine. :good:
[Samsung Galaxy Nexus] bsmitty83:
you may be right , as i have been using CM from 9/6 , Zmod may have changed something so I'll have to take a look .

Edit: just downloaded and installed latest zmod and installed R24 , booted first time no issues
[Samsung Galaxy Nexus] osm0sis:
Weird. I'm using a clean ZMoD flash with only TK GApps and SuperSU flashed with it, nothing else, and it definitely didn't work. :confused:
[Samsung Galaxy Nexus] massoudsh:
Bootlooo here on last euphoria rom with r24 but r22 work fine.
[Samsung Galaxy Nexus] :
I am on the latest (2019-09-19) version of Chroma ROM and have no booting problems with R24 :) I have changed SELinux to permissive and will see if the stability issues persist.

I also have the "no sim card" problem but it occurs even before installing any custom kernel. I hope changing SELinux to permissive will fix it.
[Samsung Galaxy Nexus] PythonNut:
Here's some screenshots of my memory usage on LuckyK vs Full_Auto.

Both of these are a fresh boot + 5 Min to settle and start all of the processes.

Needless to say, LuckyK is giving me more than four times the working memory. I tried all of the kernels back to R21.1_Ak2, and they all have this problem for me. Does anyone know where I can get older kernels? The issue is trivially reproducible, and I may be able to find out what revision introduced this behavior, and, of course, I could just run one of those older revs if the problem can't be solved.
[Samsung Galaxy Nexus] :
Are you sure the values displayed on the screen are correct?

The problem here is that the Full_Auto kernel shows 0.00B values for the processes (seems to be a bug to me) while the LuckyK kernel shows the values correctly.

Even though the graph on my phone looks similar to yours I don't really see any noticeable difference in performance between the two kernels.
[Samsung Galaxy Nexus] PythonNut:
No, I'm not. All I'm saying is that something is wrong, and it's reproducible.
[Samsung Galaxy Nexus] bamtan2:
[MENTION=4608636]bsmitty83[/MENTION] I don't know anything about selinux, but since you mentioned it, I downloaded SELinuxModeChanger ( https://f-droid.org/repository/browse/?fdid=com.mrbimc.selinux ) and changing ZMOD to permissive made the SIM card work with R23. I don't know why that is, but maybe that is enough to help you and [MENTION=2633638]Ziyan[/MENTION] know why ;)

I suspect this wouldn't help with R24 bootloop because this tool seems to disable/permissive selinux AFTER boot.

FYI the new injector puts a new section below the Z-RAM section: "Z-Swap", which appears redundant. Z-Swap uses "Max Pool Memory Percentage" rather than "Disk Size" in megabytes, which I would very much prefer.

The good news: Touch 2 Wake works! When I tested it before by enabling it manually, it didn't work well at all. Now it seems perfect. Magic [MENTION=4544860]osm0sis[/MENTION]! :) I haven't yet figured out a way to test if it can actually save power or not. But it sure looks cool. ;)
[Samsung Galaxy Nexus] bsmitty83:
I honestly don't know why R24 is not booting for some . it is exactly the same kernel as R23 except for 3 commits to zram that should in no way affect boot.

SElinux is "security enhanced Linux " . basically it is not allowing the sim card to be read in enforcing mode . there is also many other things that are affected by selinux as well . that's why most custom roms and kernels for older phones are set permissive . you lose alot of security with it in permissive mode , but that's the tradeoff.

You don't need an app to change it . from an adb shell or terminal emulator , gain root privilege and type "getenforce" to display what mode selinux is currently in , to change it type "setenforce 0" for permissive and "setenforce 1" for enforcing .
[Samsung Galaxy Nexus] bsmitty83:
Here's my app screen , reports just fine. I have seen that happen before , I have no idea what bug it is .
[Samsung Galaxy Nexus] Fenix46:
smitty this issue is caused from this commit on "mm, vmalloc" https://github.com/bsmitty83/Kernel_Tuna_AOSP/commits/Full_Auto?page=5

I've try these patch, and I've noticed the same issue, and I have reverted all commit ;)
[Samsung Galaxy Nexus] osm0sis:
Not redundant, zswap is different from zram. SELinux also has a toggle in my Synapse under Misc. No other app required. ;)
[Samsung Galaxy Nexus] siealex:
What is zswap?
[Samsung Galaxy Nexus] osm0sis:
This is all I've got for you, I also tried to emphasize the differences in my descriptions in Synapse. Maybe Smitty can explain it better?

[MENTION=4608636]bsmitty83[/MENTION] I dumped a working boot.img after flashing ZMoD's 0906 included kernel and then your r23 zip. Then I unpacked it and repacked with your r24 zImage - still doesn't boot. Something's not right for sure when you rule out the ramdisk entirely. :confused:
[Samsung Galaxy Nexus] E66666666:
Uh, flashing this kernel made my Galaxy Nexus bootloop at the Google logo. Just to let you know.
[Samsung Galaxy Nexus] bamtan2:
FYI: Synapse will start with this feature check box checked. Disabling and applying will generate and error saying that the feature is read only. Hopefully this means it is locked OFF, because from my research our phones shouldn't have zswap on due to NAND wear.
[Samsung Galaxy Nexus] bsmitty83:
As a result of reduced I/O, zswap offers advantages to various devices that use*flash-based storage, including*embedded devices,*netbooks*and similar low-end hardware devices, as well as to other devices that use*solid-state drives*(SSDs) for storage.*Flash memory*has a limited lifespan due to*its nature, so avoiding it to be used for providing*swap spaceprevents it from wearing out quickly .......

It's actually the opposite of your research. Zswap saves nand memory by avoiding writes to swap .

Furthermore I think the synapse issues with the check box are because zswap wasent even enabled on R24
[Samsung Galaxy Nexus] bsmitty83:
Again idk how this is possible as I fired the kernel right up. Still using it on zmod this very minute. But this has happened before so I'll clear my machines ccache , make mrproper on my source and try again. Cause I know this kernel works .
[Samsung Galaxy Nexus] bsmitty83:
My day is complete knowing this. At least you tried to be descriptive with your issue , I know you have a gnex and a bootloop at the Google logo . most just say "I have bootloop , fix plz" lol .

Sorry I can't help more , but holy crap is this post ridiculous.
[Samsung Galaxy Nexus] bsmitty83:
So heres a new kernel to try for those who cant boot R24 , I cleaned out my local sources and remade . it booted for me , but I know that really dosent matter much lol , anyways try it out , its set selinux permissive again too , hopefully it helps
[Samsung Galaxy Nexus] massoudsh:
I'm sorry to say that but bootloop problem remain in this version too.[emoji17]
[Samsung Galaxy Nexus] bamtan2:
I understand that compressed swap is better than uncompressed swap :) But I thought the convention for android was NO swap.

Tried it, unfortunately still bootloop :\
[Samsung Galaxy Nexus] Fenvarien:
The test kernel is booting as expected with Ziyan's CM 12.1. Thanks [MENTION=4608636]bsmitty83[/MENTION] for your hard work! :good: :)
[Samsung Galaxy Nexus] E66666666:
I didn't ask for a fix, as I can't get any further than that because my volume buttons are busted. This means I can't get into recovery to get you a log of some kind, as obviously adb won't work and fastboot is useless.

There's no need to attack me over this, thank you.

Sorry I couldn't help more, reconnecting internal PCB traces is out of my league.
[Samsung Galaxy Nexus] bsmitty83:
If your flashing anything without a way to recover , ie your buttons are broke ... Then obviously your smart enough to know that posting things such as " just so you know " will get you nowhere. I never said you wanted a fix or to provide logs or anything .

Again , I was only stating that my day was complete knowing your phone won't boot . because you seemed like you needed me to know this information by posting it on my thread . and quit being so sensitive , I never " attacked " you bro . I'm not sure what else I was supposed to do or say with the info given to me by you .

Lol , I don't want you to do anything like soldering or fixing anything. Matter of fact , I might break my volume buttons on purpose just so I can flash roms and kernels "on the edge" with no safety net ..........
[Samsung Galaxy Nexus] E66666666:
You just need to chill, that's all. Just don't reply or report my comment if it offended you that much.
[Samsung Galaxy Nexus] :
I flashed this version just for testing purposes as I had had no issues with R24.

In settings it says R25 but the problem is that SELinux is still set to Enforced. Flashing the kernel does not change it to Permissive.

PS Just one question (forgive me if it has been asked before). Would it be possible to implement support for the old TouchControl / PGM2 app? If not, maybe just adding support for DoubleTap2Wake?
[Samsung Galaxy Nexus] Martius:
[MENTION=4608636]bsmitty83[/MENTION]: Tried reflashing ZMod (Format System, Reflash ZMod.2015-09-06, Reflash Gapps, Reflash SuperSu, Flash Testkernel). Unfortunately, still bootloops.

Can we give you any data you could use to find the source of this?
[Samsung Galaxy Nexus] bsmitty83:
No not really , I mean if its bootlooping at the Google logo , you could possibly pull a last kmsg if your fast , but I'm going to try one thing real quick cause I think I may know what's up .

Edit : If anyone who can't get R24 to boot wants to try this kernel , feel free to do so lol . I dont have a samsung made EMMC so I can't test myself for this issue.
[Samsung Galaxy Nexus] ramosroger:
Worked great, thanks bsmitty

---------- Post added 30th September 2015 at 12:07 AM ---------- Previous post was 29th September 2015 at 11:57 PM ----------

Although zram is no longer accessible in synapse
[Samsung Galaxy Nexus] bsmitty83:
Zram is being emulated via zswap for this test kernel , its something I was testing before the no boot issue arose and I didn't feel like reverting my source , I'll most likely switch back to the normal mode next release .
[Samsung Galaxy Nexus] PythonNut:
Ziyan has added a new scheduler (BFQ) to his maguro ROM's kernel, and people are reporting good performance on it. How hard would it be to add to Full Auto for those of us without a maguro?
[Samsung Galaxy Nexus] osm0sis:
Boots again! There's something funky up with the audio though; locking and unlocking sounds are a static noise instead, flashing back to r23 everything's normal again.
[Samsung Galaxy Nexus] bsmitty83:
Well it shouldn't be too hard to add , I don't even include bfq as an ioscheduler because I really don't believe it's a good scheduler for nand devices. Bfq and cfq are naturally meant for spinning disk devices . sio , row , vr , and zen are my goto's. I can check it out and make the call myself if its worth adding .

I'll try to get R25 up before the end if the week ....
[Samsung Galaxy Nexus] bsmitty83:
Ha-ha , yea ill have to look at that , there are some commits included in the test kernel that were audio related from MWisbest , I really wasent concerned with the functionality of the test kernel as long as it booted on Sammy emmc's . I'll straighten everything out next release
[Samsung Galaxy Nexus] Ziyan:
Be sure to set slice_idle to 0 :)
[Samsung Galaxy Nexus] osm0sis:
These also help: https://groups.google.com/forum/m/#!topic/francosdevteam/_1mNC5pJfK4 :)

Credit to [MENTION=4793042]pkgnex[/MENTION]
[Samsung Galaxy Nexus] nikodr:
R21 all ok but usb mouse connect does not work ok. I can scroll screen with middle mouse wheel but i see no cursor and moving mouse does nothing. Can it be fixed?
[Samsung Galaxy Nexus] massoudsh:
I cant wait for r25, is there any news about that?!!!
[Samsung Galaxy Nexus] bsmitty83:
Lol , I didnd forget about it . I'm hoping for Saturday . want to make sure its ready to be set free
[Samsung Galaxy Nexus] nikodr:
On the otg cable when mouse is connected only the middle wheel works and scrolls screen on browser up down. I cant see mouse cursor.

Any plans for fix? I am on zmod and i use r22
[Samsung Galaxy Nexus] bsmitty83:
Ok , I uploaded R25 finally lol .

For this kernel I disabled Zswap , and frontswap. With both turned on , they essentially do what zram does . It was overkill with all of them active . In the future I may disable zram and use frontswap and zswap as a replacement, but for now I'm sticking with the former .

I added the Emergency Reserve Power feature , courtesy of [MENTION=1048318]zzpianoman[/MENTION] , he can explain all about it lol . Basically you can squeeze out some extra battery in a pinch by enabling through sysfs .

to enable :

echo 1 > /sys/battery_reserve/enabled

to read the new adjusted battery value :

cat /sys/battery_reserve/vcell_adj

Also I reverted a few of my latest changes to LMK , and I'm quite happy with the results . LMK seems to be in working order again .

Other than that , a few ARM-related commits are about it for this version . Hopefully it will boot for all and work well

:fingers-crossed:
[Samsung Galaxy Nexus] Martius:
Unfortunately, R25 does not boot for me. Boot stops at the Google logo, and it does not bootloop in the same way as R24 (i.e. rebooting over and over again), but rather does nothing. Just sitting there, showing the Google logo.

It could be possible this is the eMMC-Bug-Stuff again, since my Nexus has a "VYL00M"-eMMC.

If there is any other info you could use, I will be happy to provide it.

Anyways, R23 is an awesome kernel.
[Samsung Galaxy Nexus] Marvelix:
I confirm I have the same problem, phone stuck at boot logo with R25 kernel.: crying:
[Samsung Galaxy Nexus] bsmitty83:
I included the emmc fixes for Samsung emmc, but I will double check everything real quick . be ready for some test kernels lol . it has to be emmc related , it boots great for me .

Heres the 1st
[Samsung Galaxy Nexus] Schneewitzchen:
Didn't boot for me! Sits at Google Logo as with the former version.
[Samsung Galaxy Nexus] Childe89:
I have no problem booting and using R25 Kernel, with latest 9/27 CM 12.1
[Samsung Galaxy Nexus] siealex:
It would be better to add the exact production dates of your phones.
[Samsung Galaxy Nexus] bsmitty83:
here's Test #2
[Samsung Galaxy Nexus] osm0sis:
Tried all the test zips and this is the first one that boots! :good:
[Samsung Galaxy Nexus] bsmitty83:
Interesting. I think it's gotta be ccache on my machine holding on to something that is messing up the boot for the Samsung emmc's

Thanks for testing ( that goes for everyone ) , I'll update the downloads page in a few .
[Samsung Galaxy Nexus] bsmitty83:
I replaced R25 with R25v2 in the DevDB section . Sorry for the mistake , it seems like it happens every release lol . I have no idea how to test for it on my end so I'll just make sure to build clean for the releases from now on .
[Samsung Galaxy Nexus] massoudsh:
Now R25V2 work for me like a charm, thanks so much [MENTION=4608636]bsmitty83[/MENTION] ....
[Samsung Galaxy Nexus] Martius:
R25v2 works for me as well.

Thanks for making our Nexuses (?) fly, [MENTION=4608636]bsmitty83[/MENTION] :D
[Samsung Galaxy Nexus] bamtan2:
Thanks for your work as usual. This kernel seems to work great after a day!

I noticed some changes, but I never know if I'm really seeing something or if I'm going crazy :) Do you have any comments about the changes? I think the graphics clock speed is different?

[MENTION=4608636]bsmitty83[/MENTION] [MENTION=4544860]osm0sis[/MENTION] I have noticed more trouble with Synapse than normal. Setting Zram size sometimes works and sometimes does nothing. I'm not sure what does this. It used to be that I couldn't lower the capacity, which is fine, but now I sometimes can't raise it over the default. Even when saving the setting when it works, and having Synapse boot up automatically. PS: In the past I have found ~180MB a good number (with 100% swappiness and minimum page number) because it seems to work and results in only ~80MB of actual RAM usage.
[Samsung Galaxy Nexus] PythonNut:
[MENTION=4608636]bsmitty83[/MENTION] have you had a chance to look at the memory issue from 4db116d..2c9c621 that Fenix46 might be related to the high memory usage I'm seeing? I know you were busy with more important issues ATM.
[Samsung Galaxy Nexus] osm0sis:
That's a crazy number. Our device doesn't even have 180MB of free RAM to be used as zram... :eek:

zram is a finicky beast. To change anything it has to be disabled then reset, then have the settings changed, then started again. I have scripted Synapse to do this and retain the settings best it can between the resets so the enduser doesn't notice anything, but I agree it can be weird sometimes. That said, it also generally works for me and I don't think there's a different/better way to do it; the script's pretty straightforward.

I'm going to add in a button for Emergency Reserve Battery in Dev Tools since it's not something we want available all the time nor set on boot. Probably tomorrow I'll get around to it, I've got a crazy head cold and just had to backport a bunch of stuff from Marshmallow to my pre-M-style self-contained mkbootfs repo. Headaches upon headaches. Now I'm off to bed before I fall out of my seat from the cough medicine. :silly: :good:
[Samsung Galaxy Nexus] bamtan2:
My understanding is that the 180MB isn't RAM -- it's swap ;) At the compression rate and overhead I commonly see, that 180MB Zram swap equals about 80MB RAM usage, which has worked well for me. (Correction: I looked up the screenshots and it's 63-68MB for 174MB real data filling a 183MB zram swap [these data show the compression rate and overhead of the Zram system])

How do I disable Zram so I can reset it higher? Changing it to zero in synapse doesn't seem to do it. Disabling it in the kernel default settings (like it used to be) would work around this problem, but ideally we'd be able to have it on by default AND customizable.
[Samsung Galaxy Nexus] osm0sis:
It's automatic. The Synapse script disables it when you set something new. 0 would set it to disabled.

Edit: New GN_Synapse_Injector_Addon-AK2.zip is up on my BasketBuild! Adds a button for [MENTION=1048318]zzpianoman[/MENTION]'s Battery Emergency Reserve feature that [MENTION=4608636]bsmitty83[/MENTION] added in R25. :good:
[Samsung Galaxy Nexus] Syakir Imran:
anyone trickster mod setting for this kernel??? good one?? or did Nephilim update the setting for the new kernel??
[Samsung Galaxy Nexus] nikodr:
Any idea if ram share feature of 3.4 kernels can be backported? We really need that ram that is allocated for video playback, now that marshmallow rom appeared. 750 ram is not enough . I know that kernels of 3.4 can share that ram. Is it portable? Or a unique 3.4 feature that requires a full 3.4 Gnex kernel?
[Samsung Galaxy Nexus] christianpeso:
Dude...you really want that 3.4 kernel, dont you???LOL :laugh::laugh::p:good:
[Samsung Galaxy Nexus] eternal70:
I think backporting is not an easy thing. It even can make additional problems