yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] ncandy:
[MENTION=4608636]bsmitty83[/MENTION]

I have a problem with sound record function. I think, it's a kernel related problem because I try to record by used the "Zalo" app on ZMod lastest and your FML build. When I pressed record button, its freeze for 2-3 seconds and reboot. Everything is ok when I have used the lastest official FML and your R11 kernel.

P/s: To be sure, I'll flash other kernel, test again and report to you later
[Samsung Galaxy Nexus] siealex:
Flash LuckyK and try again.
[Samsung Galaxy Nexus] pkgnex:
bsmitty83,

Thanks for the unofficial FML ROM and Full-Auto kernel! This definitely works better on my device than any other Lollipop build to date. There's still some lag and a few minor quirks, but I can definitely live with this!.

Until now, I had been sticking with 4.4.4 - kept going back to it after having tried FML every time it was updated (too much lag was driving me crazy). I think this new combo is "daily driver" worthy until I get a new device later this year.

---------- Post added at 07:50 AM ---------- Previous post was at 07:29 AM ----------

I had this problem the first go-around as well. I had 4G, but then after setting everything up, I lost it. I think it was when I went into the settings / Wireless 7 networks / more area. I had set the roaming from "automatic" to "home" and that's when 4G wouldn't come back. Changing it back, or changing any of the other settings in that menu, didn't help, nor did doing a dirty flash with cache / dalvik wipe. A clean flash brought back 4G, and I have just avoided even going into that area of the settings since then. I've had consistent 4G for 3 days now.
[Samsung Galaxy Nexus] erk1725:
Thanks for the update. I was wondering if I did something wrong. Glad to hear 4G is working out for you! I will try a clean flash again and see how it goes:good:
[Samsung Galaxy Nexus] PainFly23:
I've been getting a few random soft reboots on the latest Bluetooth test kernel. Anybody else experienced this? There doesn't seem to be any reason for it. Sometimes it'll happen while I'm using the phone, other times it'll happen while the phone is sleeping in my pocket.
[Samsung Galaxy Nexus] trzesickipiotr:
I didn't test the version you mentioned, but I've been getting those reboots on the earlier versions of Full Auto and on CM12.1 stock kernel too. I've reported this in CM12.1 thread bug reports section, but didn't get any reply or comment. What ROM are you using? Maybe it's not kernel related.

I have some logs after that soft reboot, so if anybody would like to look at it, I can post them here.

PT
[Samsung Galaxy Nexus] PainFly23:
I'm pretty sure it's the kernel, I've been running the same build of LiquidSmooth 5.0.2 for months and nothing else has changed on my phone recently. The kernel logs didn't give anything useful, but that's probably because the test kernel I'm using doesn't have debug features enabled. I'll definitely see if a logcat gives anything useful next time though. Also keep in mind I was on FA R14.1 before, so this may not be a brand new bug.
[Samsung Galaxy Nexus] trzesickipiotr:
Part of my logcat (time when soft reboot happened):

05-27 13:22:18.892 W/Watchdog( 423): *** WATCHDOG KILLING SYSTEM PROCESS: Blocked in handler on ActivityManager (ActivityManager)
05-27 13:22:18.892 W/Watchdog( 423): ActivityManager stack trace:
05-27 13:22:18.892 W/Watchdog( 423): at com.android.server.net.NetworkPolicyManagerService$2.onProcessStateChanged(NetworkPolicyManagerService.java:453)
05-27 13:22:18.893 W/Watchdog( 423): at com.android.server.am.ActivityManagerService.dispatchProcessesChanged(ActivityManagerService.java:3439)
05-27 13:22:18.893 W/Watchdog( 423): at com.android.server.am.ActivityManagerService.access$700(ActivityManagerService.java:247)
05-27 13:22:18.893 W/Watchdog( 423): at com.android.server.am.ActivityManagerService$MainHandler.handleMessage(ActivityManagerService.java:1687)
05-27 13:22:18.893 W/Watchdog( 423): at android.os.Handler.dispatchMessage(Handler.java:102)
05-27 13:22:18.893 W/Watchdog( 423): at android.os.Looper.loop(Looper.java:135)
05-27 13:22:18.893 W/Watchdog( 423): at android.os.HandlerThread.run(HandlerThread.java:61)
05-27 13:22:18.893 W/Watchdog( 423): at com.android.server.ServiceThread.run(ServiceThread.java:46)
05-27 13:22:18.893 W/Watchdog( 423): *** GOODBYE!

There is nothing special in dmesg and kmsg logs.

PT
[Samsung Galaxy Nexus] kb8no:
The FML build links in OP are broke.
[Samsung Galaxy Nexus] bsmitty83:
Check the downloads page , the builds you are referring to are months old . I fixed the op through . thanks
[Samsung Galaxy Nexus] bamtan2:
Thank you for changelog [MENTION=4608636]bsmitty83[/MENTION] :good: ;)
[Samsung Galaxy Nexus] siealex:
R20 lags even more than R19, even pressing navbar buttons lags 1..2 seconds.
[Samsung Galaxy Nexus] bsmitty83:
Idk , zero lag here . it just must be something local on your phone . a old trickster mod config , an app/mod your using , something . I've noticed zero lag anywhere on any release . I've been benching this kernel and others , using it hard . nothing but performance .
[Samsung Galaxy Nexus] siealex:
Trickster configs are automatically disabled when I change the kernel. LuckyK (and the stock zmod kernel) works fine, Full Auto lags always and everywhere.
[Samsung Galaxy Nexus] bsmitty83:
Like I said , its gotta be something on your phone. Your the only one who seems to have a problem . if its that bad for you version after version , I suggest not using it . simple as that . use luckyK or whatever else . there's not much I can do when all I have to go by is " its lags " . if I had that complaint from everybody, then I'd say its a kernel problem .

do you dirty flash the ROM your using before flashing this kernel ? Have you ever formatted your sdcard partition ? Try taking just the zimage out of the zip package and fastbooting it , so your not including the ramdisk edits . maybe its something in the bootscript that's causing problems for you .
[Samsung Galaxy Nexus] Punkiderma:
For me is the same, I don't know why but since I started using zmod, I had to stop using your kernels :( even after clean flashes. The one that worked better was R17, but still not as good as the stock one or luckyK. And this JUST on zmod.

Notice that is absolutely not a complain, I'm very grateful to you for your incredible work, is just a report. I really don't know why zmod (at least, for me, on maguro with f2fs) doesn't want to play nice with your kernel.

Never, never had a problem with other roms, even on lollipop (I was on liquidsmooth 5.0.2 before zmod) and since you started developing dirtyV on Jb and KK.
[Samsung Galaxy Nexus] bsmitty83:
Believe me , I have no problem with criticism . I don't take anything personal and I know that your just reporting what your experience is . I always want to know if a problem arises , because that's the goal , to fix things and make them better .

That being said , I actually have been running zmod for some time now with no problems . so that is the reason I believe its a conflict with some app or setting or something that is to blame . if it was simply just the kernel it would be across the board the same experience for zmod , or any ROM for that matter.

I've built and flashed hundreds and hundreds of kernels that never make it to be posted on XDA , for one reason or another. If it doesn't work right , I change it or fix it or revert whatever I did . I've had kernels not boot , fc process, lock up , randomly reboot , but never just lag. When I've had a system that lagged , i could solve it by clearing my cache from recovery , or clean installing a ROM , or even formatting my sdcard partition .

My kernel is in no way shape or form perfect , but IMHO system lags are usually caused by some other reason besides the kernel itself.

I'd love to hear other peoples opinions and experience with this kernel and zmod or any ROM , because I haven't been able to reproduce any type of lag with my phone . I don't use xposed, gravity box ,greenify or any major system modifying apps so maybe its something not playing nice with my kernel .

I'm just trying to get to the bottom of the problem
[Samsung Galaxy Nexus] osm0sis:
Could it be a toro vs. maguro thing with ZMod?
[Samsung Galaxy Nexus] bsmitty83:
It could be I guess. But I figure most gnex users that are still active are using maguro , I don't think there are many toro users left .
[Samsung Galaxy Nexus] siealex:
Yes, otherwise the system won't boot at all.

Never.
[Samsung Galaxy Nexus] erk1725:
Toro user here. Running Smitty homemade FML ROM.....I've always ran [MENTION=4608636]bsmitty83[/MENTION] kernel even back during kk. Never had any major issues with ram or lag. I do get occasional launcher redraws with nova but I think that is just lollipop on a 3 almost 4 year old device :(

I'm very happy overall with lollipop on my device and really appreciate all the work the developers do for us here! Looking forward to the next FML update and I'm going to continue using Full-auto as long as its available to me :)
[Samsung Galaxy Nexus] jguerdat:
Toro here, too. I can't get the newer kernels to work for much time at all - reboots during first boot, optimizing apps, when finally at launcher screen. I'll come back a bit later if successfully booted only to find it rebooting again. No Trickster set up partly because I can't even get there. Your unofficial kernel fails, too, similarly. I'm beginning to think it's the hardware version of the phone - early Toro (no idea when other hardware versions were released). The last FML works fine as long as I use an older kernel or just plain. I've tried factory wipe, dirty, format this and that, etc. and can't come up with a workable solution. It's not a huge thing for me since it's just my bedside clock that I play with but it'd be nice to be able to update if possible.
[Samsung Galaxy Nexus] erk1725:
This is using [MENTION=4608636]bsmitty83[/MENTION] homemade FML?
[Samsung Galaxy Nexus] jguerdat:
Yup.
[Samsung Galaxy Nexus] nikodr:
On latest zmod i applied nephelim settings. Clean install rom. Zram on. No lags no crashes. I assume those with problems most probably do not know how to setup trickster or they do not clean flash. Its very fast. I am switching between zmod with auro kernel and paranoid android beta two with lucky kernel. Both work very fast. :)
[Samsung Galaxy Nexus] akhi24nick:
[MENTION=4608636]bsmitty83[/MENTION]

R20 No Debug and zMOD latest in my Maguro - No lags and even better performance than before :)

EDIT : There's a big improvement in the smoothness of in app animations and the overall system animations too. :)
[Samsung Galaxy Nexus] Punkiderma:
Sure is a problem with my device or a conflict between something I don't know, the next time I have time to clean flash I'll surely try that kernel again!
[Samsung Galaxy Nexus] nikodr:
Did you apply nephelim settings? The minfree in trickster is from top to bottom 50,70,116,130,165,370. Undervolt from 830 to 810 turn on zram. Turn off fsync. Westwood. And sioplus. Max screen on 550 min screen on 350. Max frequency 1520 min 250.gpu 512. Does it change something?
[Samsung Galaxy Nexus] siealex:
What? 370???
[Samsung Galaxy Nexus] nikodr:
From top to bottom
[Samsung Galaxy Nexus] siealex:
370 for empty apps? Our phone does not have 370 free even without any apps.
[Samsung Galaxy Nexus] nikodr:
http://xdaforums.com/galaxy-nexus/general/nephilims-custom-kernel-settings-t2401653 if you check lollipo settings nephelim did this. He is a recognized developer.

---------- Post added at 08:54 PM ---------- Previous post was at 08:54 PM ----------

And whenever i apply those settings trickster says apply succesful. So they are ok to use.
[Samsung Galaxy Nexus] GilGameshn1:
Min free in LL is working differently than KK . So it is okay . [emoji13]
[Samsung Galaxy Nexus] kb8no:
On the homemade FML it starts on LTE after a flash but as soon as it drops to 3G then it will not ever go to LTE and is stuck on 3G. Deferred network type defaults to 3G CDMA and 4G LTE will not stick so it defaults to 3G at the first opportunity and stays there.
[Samsung Galaxy Nexus] siealex:
Are these OOM settings specific for this kernel or for any 5.* one? I've set them on LuckyK - Google Now Launcher gets constantly killed.
[Samsung Galaxy Nexus] PainFly23:
The same settings can be applied to any kernel, it shouldn't make a big difference across kernels.

Speaking of big differences, I just raised the value for empty apps from 150 to 256 (the highest the app I use will allow, it seems) and WOW, what a difference! Performance is not only a bit better, but multitasking is leaps and bounds ahead of what it used to be. Not really what I expected. This just goes to show that LMK values really are one of the most important settings for low RAM devices such as ours. I'll see if raising Empty Apps to 370 will make any noticeable difference.
[Samsung Galaxy Nexus] bamtan2:
Thanks for recording these settings :) My notes: I'm not sure if these are a good idea: 250mhz cpu minimum, fsync off. Also I think "Max screen on 550" might be an error? ;)

Since we're talking about LMK minfree settings, I've noticed that my "recently used" multitasking list of apps is huge. Every app I've ever used is there, even though they're all CLOSED except for ~3 of them. Is there any way to make the closed apps disappear from the list? At least then the list would serve a purpose. You'd know what was running because it'd be on the list. Right now it's a useless list :P
[Samsung Galaxy Nexus] PainFly23:
I haven't tried it myself, but Chainfire's app Recently does exactly that.

https://play.google.com/store/apps/details?id=eu.chainfire.recently
[Samsung Galaxy Nexus] bamtan2:
That is awesome! Leave it up to [MENTION=631273]Chainfire[/MENTION] to make things better! :) It's kind of sad that Google didn't notice this problem and do something right away. No one can use a recent apps list with 100 things on it. Even if we could, we'd need a search function... and considering they're a search company, Google sure lacks useful search in some places!

Chainfire Recently is now a must-have app for me, especially while testing LMK minfree variables.
[Samsung Galaxy Nexus] fivefour:
Try bumping the voltages up a bit.
[Samsung Galaxy Nexus] erk1725:
[MENTION=4608636]bsmitty83[/MENTION]

When I go into settings/apps/running, my system is showing ~650mb, apps ~52 and free ~15mb? My setup is the same as it always has been, so my question is what is everyone else showing these values to be on their devices? I'm running FA20 with smitty homemade FML, stock minfrees, nothing whitelisted. Performance is good, maybe a little faster, multitasking is what I'm used to........its just odd these values are so low now. The free value used to be ~200? Not trying to complain, just curious if that is an expected result to something that changed in the kernel?

Thanks as always for everything you do!:good:
[Samsung Galaxy Nexus] siealex:
System must be no more than 400 M.
[Samsung Galaxy Nexus] erk1725:
Thanks!

I think it used to hang around 400 before, I'm not sure what is going on. I forgot to mention I'm on F2F data and cache if that matters in this case. I don't know how to resolve this and get that value to go down. Using nephs min free values don't seem to help change the system value, and I don't have any more apps running now that I any time in the past. Like I said my setup is the same its always been

Thanks again!!:good:
[Samsung Galaxy Nexus] nikodr:
Something is wrong with auto 20 and nephelim settings. Check this picture on latest zmod. Below is a pic from trickster where ram is ok
[Samsung Galaxy Nexus] cujo6801:
My bad...

Cfq is having problems

Sent from the "DOG" pound
[Samsung Galaxy Nexus] Nephilim:
It is never wrong to use Neph's settings.
[Samsung Galaxy Nexus] Syakir Imran:
Guys what good/best .. Good battery Life Good performance ... Scheduler and cpu ... (trikster mod)

My current setting

CPU:Interactive

Scheduler:Siopluss
[Samsung Galaxy Nexus] shadowam:
No.
[Samsung Galaxy Nexus] Heart1010:
[MENTION=2853378]Nephilim[/MENTION] I have a problem when i use your settings that after the boot everything is perfect for a few minutes but then the phone becomes very "luggish", it hangs after every touch and so on. What settings can cause thing behaviour?

(with default beta3 kernel settings this doesn't happen)

Gesendet von meinem Galaxy Nexus mit Tapatalk
[Samsung Galaxy Nexus] ahmadairfan:
Bump up core voltages, maybe?
[Samsung Galaxy Nexus] rohitchouhan07:
bump down the max cpu frequency to 13500.........
[Samsung Galaxy Nexus] Nephilim:
I'm still on Beta3 but I'll be giving the new kernel a try sometime today. Try using sioplus on stock I/O tunables instead of row and let me know if that helps for now.
[Samsung Galaxy Nexus] bsmitty83:
Ok here's R4 , If I get 2 people to flash without problems , i'll add the links to the OP

Row is Back , SIo+ is default , CFQ is gone

regular anykernel install until I can set up anykernel2

R4 For FML is in the OP , CM is still being tested
[Samsung Galaxy Nexus] Schneewitzchen:
Flashed r4...booted with no problems, until now all is fine! Keep up your great work!
[Samsung Galaxy Nexus] bsmitty83:
FML or cm ?
[Samsung Galaxy Nexus] Schneewitzchen:
Sorry...fml
[Samsung Galaxy Nexus] massoudsh:
i flash FML version & booted without any problem...thank you smitty.

P.S: plz add TouchControl support to this kernel.
[Samsung Galaxy Nexus] Nephilim:
That's what I like to see. Going to flash now and compare with Beta3.
[Samsung Galaxy Nexus] netreign:
problem with flash cm version..... stuck google logo
[Samsung Galaxy Nexus] ardeus_ua:
Me too on CM12 2014-01-10
[Samsung Galaxy Nexus] bsmitty83:
OK I think I know the problem I'm working on it .
[Samsung Galaxy Nexus] jguerdat:
I've got it installed on FML. A few reboots needed to get Nephilim's settings installed but all has settled down.
[Samsung Galaxy Nexus] Nephilim:
New FML build working great with all my settings including row tunables. Benchmarks are on par with Beta3 upon first run. Will test again after a few hours. Multitasking seems even better and performance/speed is great so far.
[Samsung Galaxy Nexus] davinaizer:
Bootloop on CM...
[Samsung Galaxy Nexus] nikodr:
Ram
[Samsung Galaxy Nexus] nikodr:
Bit why do we get negative numbers? Apart from that the phone is very fluid and fast no lag
[Samsung Galaxy Nexus] erk1725:
I agree performance is very good for me. Not a single random reboot or anything either...very speedy overall:thumbup:
[Samsung Galaxy Nexus] hubik.j:
He is not the only one. I had the same problems on R19, so I went back to stock for a while and then to LuckyK for the color correction. My ROM is clean flashed, sdcard was formatted quite recently. XDA really needs a "Me too" button for these situations, because I do not have anything to say - just wanted to let you know that he is not the only one noticing lags.
[Samsung Galaxy Nexus] alagga:
+1 ... me too
[Samsung Galaxy Nexus] Ales98:
Is this compatible with Lollipop 5.1.1 (Cm 12.1)?
[Samsung Galaxy Nexus] massoudsh:
Yes.
[Samsung Galaxy Nexus] Ratedzelaya:
Can anyone tell me how to build my own FML rom ?
[Samsung Galaxy Nexus] danny39:
So this thread hasn't been posted in for a while, but has anybody found the (in your opinion) best Kernel settings for Full Auto?
[Samsung Galaxy Nexus] huyphuco:
You can try my setting

TCP: westwood

I/O: Scheduler: sioplus, RAB: 768

CPU freq: Min: 250, Max: 1350, Max off: 550, Min on: 250

Gov: zeneractive

The rest: default

Battery with this settings: about 20hrs - 22hrs

- ~1hr call

- ~2hrs messaging

- ~1hr using browser

- ~45mins listen to music
[Samsung Galaxy Nexus] Jacklya:
Thanks, your setting is good. I've using this for 2 day without freeze or reboot...
[Samsung Galaxy Nexus] Djalaal:
[MENTION=4608636]bsmitty83[/MENTION]

A while ago (I think on R14), I said bluetooth game controller was not working properly under your kernel, but it was under zmod's stock kernel. I just tried R20, and it works fine now. Thanks!

However, something else is off now. This started happening right after flashing your kernel (did no wipes though). It's the USB OTG. When I copy a relatively large video (300MB+) from USB to internal memory, the whole UI becomes unresponsive. It does in fact complete the copying, but the UI is completely frozen during the transfer. I tried this 3 times, same result. Actually, the first time was slightly worse; I got a forced soft reboot right after the copying finished. Didn't happen the other 2 times. Does this happen to you?

Can provide any logs needed.
[Samsung Galaxy Nexus] siealex:
I had the same behavior during intensive file operations such as full Titanium backup.
[Samsung Galaxy Nexus] christianpeso:
Back on this phone for a while. Using R20 gives me substantial lag. Enough to the point I thought it was the device itself and flashed back to a Kit Kat ROM with someone elses kernel. Then going back and reading a few pages I noticed that some other people were having that lag issue with R18 and above. Flashed back a Lollipop ROM and this time used the kernel that came with it and it worked fine. Looks like people are having good times with R17.

Does anyone have a link to R17 please and Thanks!
[Samsung Galaxy Nexus] GilGameshn1:
Salute to nexus world . I am really miss this thread . B me well all . ?
[Samsung Galaxy Nexus] bsmitty83:
So it's been a while , but I think R21 is ok to put out . I have been working with zram mainly for this build .

It's still a work in progress , but I am happy with the results on my phone . Anyways , the major changes are

updated zram to linux 3.18 ,

added and updated zsmalloc to 3.14 ,

removed zcache and added zswap from 3.11 ,

removed touchboost and added input boost to cpuboost ,

removed my personal f2fs mount flags from the fstab

zram now has the ability to switch compression algorithms

and set the max number of compression streams used .

I also fixed zram crashing on swapoff or at other random times . I've had zram on for days at a time , almost totally full , swap completely full , turned it off , changed partition size , etc . All without a reboot .

I also updated the synapse interface to [MENTION=4544860]osm0sis[/MENTION] 's latest . For now input boost and zswap tunables are controllable from a command prompt , under /sys/modules/cpu_boost/parameters/

and /sys/modules/zswap/parameters/ , respectively .

FOREWARNING : unless my emmc is getting bad from so many flashes , I've been experiencing much longer boot times with this version . like 2 min on google logo , so be patient , I haven't had one not boot , just takes longer than previous .

I would post the changelog , but its a few hundred commits , so if your that interested , head over to my github

Other than that , hope it works well for everyone , feel free mess with the tunables , there are many .

I personally feel like zram makes a difference , but by no means do you have to use it .
[Samsung Galaxy Nexus] netreign:
its not boot by me....with the last version
[Samsung Galaxy Nexus] h4xx0rr:
It boots fine, just be patient, wait 2-3min
[Samsung Galaxy Nexus] netreign:
its not to be patient.... restart and restart from google logo
[Samsung Galaxy Nexus] rohitchouhan07:
Agree with him same thing happening ...........bootloop on google logo.......on chroma rom .
[Samsung Galaxy Nexus] eternal70:
Works fine here with chroma, about 30secs at google logo.

Btw, great update ! Many performance improvement here and there. These days i almost throw my phone because the lag is extremely annoying. Well eMMC is likely can't hold it anymore. Maybe soon we can see "Strongest GNex in the world" thread
[Samsung Galaxy Nexus] h4xx0rr:
I can't play yt videos on r21, idk why o.O Can anyone confrim?
[Samsung Galaxy Nexus] rohitchouhan07:
Tried again on recommendations of you but same thing happening

....shows google logo vibrates n show google logo again.

....i m on ext4 with 29 june build of chroma.
[Samsung Galaxy Nexus] h4xx0rr:
Me too, ext4 and 29 june build. Weird...
[Samsung Galaxy Nexus] mowto:
Stuck on google logo for 10 minutes...seems too much (cm12.1 06/18)
[Samsung Galaxy Nexus] eternal70:
eMMC chip bug again ? Oh god.......
[Samsung Galaxy Nexus] rohitchouhan07:
Ohhhh yes indeed coz i am having a vyl00m .....the buggy emmc