yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] dehein:
AW: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

i don't know why. But with PA and franco 366 i had problems. after a while my phone was freezing and only running very slow. after a switch to ak the problem resolved.

Somehow sad to see the development decrease for our g nexus...
[Samsung Galaxy Nexus] osm0sis:
pkg, you were saying you liked 16gb for the bsm in cfq. What about splitting the difference between 8 and 16 at 12 for a more universal value? Please try 12582912 and let me know what you think. My phone's liking it. :)
[Samsung Galaxy Nexus] pkgnex:
I'll give it a try. As I recall, 1e6 and 1e7 both seemed fine with my prior testing, so I imagine that value will be fine... but I'll let you know if it doesn't, or if I end up liking it even better.
[Samsung Galaxy Nexus] bigknowz:
nomerges = 1

Basing my findings purely on music stutter, all other functionality seems to be unaffected.

Rocketplayer stutters when the radio (LTE / CDMA) has signal issues. With Deadline, I find nomerges = 1 decreases stutter better than nomerges = 0. I also switched back to 6/0/0 (writes_starved, front_merges, fifo_batch) from 4/1/2 after I turned nomerges back on. 2 questions:

1. Is nomerges = 1 better with deadline?

2. If you change nomerges from 0 to 1, should you change 4/1/2 back to 6/0/0?
[Samsung Galaxy Nexus] Gafanhotz:
For the second time I got an SoD after letting the screen off when transferring something through bluetooth, my phone was responding normally, but no screen. Had to pull out battery. Ironically, I've deactivated a few days ago logcat and other logs (what an dumb action to take), so if it happens again, I'll send a logcat.
[Samsung Galaxy Nexus] ciprianruse88:
All 4.2.2 based rom will lag after a while.tested and tested and tested...no solucion by now.but I respect this thread and i say that only i hope that this kernel i am testing now will resolve this and if no ,that means it's rom releated...a patch or something that is in the rom...i don't know cuz i tested them all...Here is a thread started by a guy and there are many people that are experiencing lag after a while of use - http://xdaforums.com/showthread.php?t=2178962.

Sent from my Shining Nexus using AK DIAMOND ED.
[Samsung Galaxy Nexus] grognaz:
Re: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

i also tried r365 and i get normal write speed with that version.

is there something else i can test to help?
[Samsung Galaxy Nexus] pkgnex:
Os,

12582912 seems fine to me. Phone doesn't feel any different, and there are no discernable benchmark differences as far as I can tell.
[Samsung Galaxy Nexus] osm0sis:
Nope that's great. Thanks for confirming. We're basically 98% sure it's nomerges 2 that's the problem so you can run r366 with our tweak script to fix it or wait for the next build as well since I'm sure Franco will resolve it there too. :good:

Deadline at 6/0/0 definitely seems to like nomerges at both 1 and 2, giving a very smooth and fast feeling experience, unfortunately nomerges enabled also cripples write speeds, so when anything write intensive occurs smoothness goes right down the toilet.

---------- Post added at 07:58 PM ---------- Previous post was at 07:25 PM ----------

Perfect. New version uploaded: http://d-h.st/users/osm0sis

Added add_random 0 as well since some ROMs enable it and it's only meant for rotational disks where the head movement provides entropy; SSD/flash obviously is not a good source of entropy (no head!), so this setting might be creating needless overhead for those with setups that use it.

Got some test vm settings of my own up there now. I feel they help make things pretty smooth and believe I have seen them decrease the frequency and severity of write choking in SD Card Tester. Good high speeds, for the GN, in AndroBench (>27,>7,>6,~0.25, etc.) and lower macro times as well (~120, ~380, ~420, ~1000). I left swappiness in for the sake of placebo even though we don't have ZRAM/swap enabled, and decreased min_free_order_shift to 2 since from my reading it should run better at 1, or close to it on setups with small or no swap.

Not really sure about min_free_kbytes though, seemed about the same at the default 1442, 2048, and 4096.
[Samsung Galaxy Nexus] J-Hop2o6:
Re: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

+1 osmosis. Also try a trim + reboot, then test the storage speed. Download lag fix via play store. I get (before your new io values) 30/10/10/0.5 on androbench.
[Samsung Galaxy Nexus] osm0sis:
Thanks. Yeah, I'm hoping franco will add the -discard option to the /data/ mount in the future so we won't need fstrim. :good: I've read this can reduce performance slightly but it'll be better for those that don't know/care about fstrim to run it regularly, so should improve performance overall.
[Samsung Galaxy Nexus] Khrushy:
Throwing out there that 12GB for bsm seems fine with cfq on my 16gb GN. No discernible difference compared to 8GB.

Also pkgnex, what are the entropy settings in your script for?

I happily admit I've not looked into it much, but I thought most of the entropy issues were pre-ICS, when tasks that called for a random number could get held up if the current entropy was insufficient. Post ICS I thought they moved all that to /urandom or something like that, meaning the entropy settings shouldn't matter?
[Samsung Galaxy Nexus] pkgnex:
Yeah, sorry if that across a little harsh, Khrushy - didn't mean it to. There are so many different lmk/oom/minfree settings in both ROM and Kernel locations that it gets confusing at times. I think we were saying/reading the same words and interpreting them differently!
[Samsung Galaxy Nexus] Khrushy:
No stress - I didn't interpret it as harsh anyway ^^

Besides, you led off with "respectfully disagree" - that's some awesomely oldschool politeness, and makes the English nerd in me go all soft and gooey.
[Samsung Galaxy Nexus] osm0sis:
Just looked into it myself. From the description of sEFix on the Play Store:

From that page starting with zepplinrox' post you can get the idea. :)

I'm experimenting with the following right now:

pool="$(cat /proc/sys/kernel/random/poolsize)";
rwt="$((pool/3))";
echo $rwt > /proc/sys/kernel/random/read_wakeup_threshold;

Since poolsize is 4096 for f.K we end up with 1365 like zepplinrox suggests.
[Samsung Galaxy Nexus] pkgnex:
Honestly, I added them for testing back when the whole random / urandom / lagfix / entropy debates were raging on XDA a few months back (pretty sure some were saying it was only pre-ICS, others vehemently disagreeing). I ran through several different values of the listed parameters and found that huge increases (as suggested by some) actually seemed counterproductive, but that a small increase seemed to maybe make my phone a little snappier. I considered just deleting them, but in the end decided leaving them wasn't hurting anything. It very well might be placebo, like Osmosis spending time tuning swappiness on Franco kernel :p.

You can feel free to play with these values if you want, tune to taste, but I certainly wouldn't suggest spending much time on it. There are definitely more effective tweaks to be done.
[Samsung Galaxy Nexus] LibertyMonger:
I have this issue only with opposite kernels, I always get freeze up issues with AK and revert back to Franco 366 and it runs fine. I haven't been following this thread and I haven't had time to dig and i am sure this has been answered and I seen where franco mentioned no point in updating kernels just to be updating, but i would really like to know where we stand in the kernel world lol. I am kinda lost. I haven't had any luck with any kernels lately, I get freeze ups no matter kernel i use, except Franco, seems I have the best luck with it but it still isn't like it used to be in the kernel world for our Nexus'. I'm almost to the point to where I want to return my phone back to stock and just sell the sucker, since 4.2.2 I just haven't liked my phone all that much. Is Franco officially done here? Can someone else give me their thoughts on this issue? Everyone seems to rave over AK but I just can't get any of them to work for me. Any help would be greatly appreciated. I am stuck and could use some advice lol.
[Samsung Galaxy Nexus] jakis39:
Literally never bothered with kernels until now, so I'm a little new here. I've heard this one is pretty alright, but I have a question.

My ROM has a performance menu in settings that allows me to set cpu speeds and governors among other things. If I flash this kernel will that menu still control the kernel as it does now? Or what?

inb4 search flaming. I searched this thread and didn't find anything that answers my question.

TIA
[Samsung Galaxy Nexus] reysonance:
Yes, the path for changing governors and all that is the same across kernels, it'll control it just fine.
[Samsung Galaxy Nexus] osm0sis:
Depends on the ROM but many of them do the same thing as the tweak apps, so I'd say try it out. Of course I highly recommend franco.Kernel updater for having all sorts of tweaks to play with. If you do end up using another tweaking app, remember to disable the Performance menu stuff or they may conflict. Cheers and welcome! :)
[Samsung Galaxy Nexus] grognaz:
Re: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

could you tell me where to put that script? and i assume its the 950iosettings.bin?
[Samsung Galaxy Nexus] reysonance:
Remove the extension, and put it in /etc/init.d/ OR /data/local/userinit.d if your ROM supports it, userinit.d is preferred since it persist between dirty flashes, if your ROM doesn't support it however, you can put that script under /etc/init.d and it'll work. Also don't forget to set permission to 0755, and you're done.

EDIT: 755 is (-rwxr-xr-x) for the record.
[Samsung Galaxy Nexus] bigknowz:
init.d wait

Which settings require the init.d file to wait for android os to start? If you put the wait in a file titled 900etc, guessing there is no reason to put a wait in 910etc - correct?
[Samsung Galaxy Nexus] pkgnex:
Os,

Speaking of fstrim, do you have a script or terminal command you use to run it, and how often do you run it? I've only done a fstrim once, and I used an app (since deleted) to do it.

Thx.
[Samsung Galaxy Nexus] grognaz:
Re: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

so i tried r366 with the iosettings script today and its a lot better but does not completely solve the problem.

when running sd card tester with a cpu load monitor one can see whats going on.

the write speed starts really fast, about 12mb/s but after a short time it completely stops. during that time the cpu spikes to 100%. after a short time it recovers and continues for a short while until the overload happens again. this is resulting in an overal speed which is qbout the same as on stock. however these full cpu loads in between causes the device to be locked for every other action.

any other idea whats causing this? im happy to do some more testing
[Samsung Galaxy Nexus] osm0sis:
They run in order, so yup.

I've only ever used that Lag Fix app once or twice. Nothing scheduled.

Really good info here. Thanks! Perhaps this indicates the CPU is the bottleneck and we could tweak our winning settings a little more.
[Samsung Galaxy Nexus] J-Hop2o6:
I run a TRIM once a week. Since write speed slows down a bit, I TRIM it. Especially after many installs and added files to the storage card.
[Samsung Galaxy Nexus] Khrushy:
Playing with max_free_order_shift today - 4 -> 2. In testing it made no difference (less than 1% difference over multiple tests - which is basically just test noise), but in use I feel that 2 sometimes lags (a little) when there's a lot of background events happening (incoming notifications in particular). I'm going to run 2 for the rest of the day and see if I come to a preference.

Mind you, all differences here are really really minor.
[Samsung Galaxy Nexus] Dmw017:
he had wifi on.. and you can easily get 4-5hrs of screen if ur brightness is off
[Samsung Galaxy Nexus] 2dorr:
I have a problem with my Nexus. 2 times now it rebooted by itself an it get stuck at the animation screen. It might be related to full charge. Anyone had this?
[Samsung Galaxy Nexus] AzzaD:
you uv'ing at all? happened to me when I saved the settings when I hadn't really tested them yet
[Samsung Galaxy Nexus] Hemulen:
I noticed my screen colors got a bit brighter after installing your kernel. Is that what the colorcontrol feature is? :)

Can it damage the screen somehow?
[Samsung Galaxy Nexus] saywhat4118:
I keep my brightness on full.
[Samsung Galaxy Nexus] Hemulen:
I ment the colors, not the light. ;)
[Samsung Galaxy Nexus] 2dorr:
I haven't UVed it, I even clicked - Restore stock voltages, even though I haven't played with UV or OC.
[Samsung Galaxy Nexus] JcMalta:
I believe Franco's Rom is already under-volted by default to stable and realistic values
[Samsung Galaxy Nexus] Reppu:
I think anything above three hours of screen time can be considered good at the moment. 3h40h is very good. I have not seen many stats better than yours.
[Samsung Galaxy Nexus] i4mt3hwin:
No it can't damage the screen, it's no different than adjusting the color properties of a TV or similar device. It's tweaked to bring white closer to real white.
[Samsung Galaxy Nexus] kecinzer:
I still have unlock lags with autobrightness and latest build.
[Samsung Galaxy Nexus] Stretlow:
This is acrooss the board, all roms, all Kernels (unfortunatley).

I've resigned myself to putting it on 50% and leaving it there
[Samsung Galaxy Nexus] lillypad_33:
I've got that same face recognition unlock brightness issue, but I don't care too much about that.

The newest kernel has really improved batter performance alot.

With an older kernel version I lost 40% of battery life in airplane mode over my 8 hour sleep.

With this kernel version I lose about 3% of battery life in airplane mode over my 8 hour sleep.

Good job Franco!
[Samsung Galaxy Nexus] loudaccord:
I ended up going back to 13 from 13.1 last night and my battery life is now better. I didn't seem to have the problem others were reporting with 13. I'm on the CDMA Nexus if that counts for anything. (AOKP b17)
[Samsung Galaxy Nexus] franciscofranco:
Were you undervolting?
[Samsung Galaxy Nexus] kecinzer:
I don't think so. I have this behaviour only with franco.Kernel. Glados, Leankernel - no lag.
[Samsung Galaxy Nexus] Hemulen:
What exactly is color control?
[Samsung Galaxy Nexus] loudaccord:
No, I just use the defaults as is with 700/1200 conservative gov. For some reason "modem_usb_gpio_wake" and "modem_usb_suspend_block" was taking up some of my battery. I don't know if that was what was causing the drain, I never use usb tether. I tried a couple reboots and that didn't work, I toggled tether on and off with no success. Flashed nightly13 and it doesn't seem as bad.
[Samsung Galaxy Nexus] franciscofranco:
A mod to change the RGB gamma values.

That's strange, I don't have those wakelocks. Let's hope they get fixed in #14.
[Samsung Galaxy Nexus] IIIPowerIII:
Nice job on the kernel! :-)
[Samsung Galaxy Nexus] osm0sis:
Yeah I took down my vm test settings because something felt slower. Maybe it was that. Haven't had time to go through them again.

Still happens with performance governor so that takes that out of the equation; must be queue, io or vm.
[Samsung Galaxy Nexus] Khrushy:
Weirdly, I only get CPU2 maxing out in spikes. CPU1 is hovering around 40-60% the whole time during SDcard tests.
[Samsung Galaxy Nexus] osm0sis:
Happens regardless of governor or scheduler, tweaks or defaults. So queue or VM? Hmm. I'm flashing stock for comparison and Google's values.

Edit: Happens just as badly on stock. In fact stock feels awful. Added the old magic tunables for the old interactive and that still worked well. Good news is all our iosched tweaks also improve the feel of stock with cfq and deadline. Stock has deadline at 2/1/16 by default which is interesting.

Settings dump: http://pastebin.com/2NY4zvUY
[Samsung Galaxy Nexus] Khrushy:
Interesting, but also good to know it's not something kernel related, or something we specifically broke with the VM / IO settings. Can you record the stock kernel and IO settings for reference?

Also happens for me with Performance, and CFQ, BFQ, and noop all max out CPU 2 in spikes. Interestingly, noop, the simplest of all, spent the most time maxing out.
[Samsung Galaxy Nexus] osm0sis:
Edited my post. Deadline tweaks were good too, just a random dip.

Stock settings: http://pastebin.com/2NY4zvUY

r366 default settings: http://pastebin.com/M78i7ZSE

Of course we know nomerges is better at 0 now.
[Samsung Galaxy Nexus] irminsul:
Re: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

Lagfix says my device doesn't support fstrim. I'm on rasbean / Franco. Strange, I remember using that app before on other ROM.

Verstuurd van mijn Galaxy Nexus met Tapatalk
[Samsung Galaxy Nexus] grognaz:
@osm0sis: in case you use twrp, i think theres something wrong with wiping because i was not able to revert back to stock performance with it.

only when i wiped and installed with cmw i got the stock speed back. i can try to reproduce that if it would be helpful.

i also dont have any slowdowns with the sourcerizer kernel which comes with the sourcery rom, so maybe you can see a difference there.
[Samsung Galaxy Nexus] osm0sis:
Whaaaat? I use stock ROM and was just talking about going back to stock kernel for comparison. I use CWM anyway, but thanks for the heads up. ;)
[Samsung Galaxy Nexus] Khrushy:
Re: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r30&gt; 4.1

So I definitely prefer 4 to 2 for the max free order shift. Tried 3 also and couldn't notice any difference - I think I'm going to stick with 4.

I also tossed overcommit_memory 1 and overcommit_ratio 50 into my script, but that's not changing anything from default, so anyway.
[Samsung Galaxy Nexus] pkgnex:
I agree with 4 being best for max_free_order_shift. Phone is more responsive than with this value set to 2 or 1.
[Samsung Galaxy Nexus] J-Hop2o6:
And where is this max_free_order_shift?
[Samsung Galaxy Nexus] osm0sis:
It's a vm setting. 4 is the default though, so don't worry about it. :)
[Samsung Galaxy Nexus] stevensoaj:
Re: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

May I ask which CPU load monitor you're using? Also, sorry I haven't had time to help with the testing Os. I've been needing my phone a lot lately.
[Samsung Galaxy Nexus] bigknowz:
Check init.d settings

I improved on my original hack to make it possible to check if init.d settings took hold without going into terminal or using fku / trickster. The script in my signature will ask you for the settings file name (ex. 950iosettings) and create a text file showsettings in /sdcard that shows the expected and actual values.

Change the extension from .txt to .sh before you run it..

I'll try to work on having the script list the contents of init.d folder and give you the ability to select the settings file you want to check.

EDIT: Moved script into my signature.
[Samsung Galaxy Nexus] emd2009:
So what settings and kernel version are people suggesting these days?
[Samsung Galaxy Nexus] Astug:
I've been using osm0sis's governor tunables, which were the most popular after public testing a while back.

These differ from the ones set by default in the latest version of f.K.

Him and quite a few others members are currently trying to figure out the best IO scheduler tunables (per scheduler), but this is more advanced stuff and nothing has been set in stone just yet.
[Samsung Galaxy Nexus] emd2009:
Re: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

Thanks good to know!
[Samsung Galaxy Nexus] J-Hop2o6:
Good lookin'

I use (for status bar/notification slide) Usage Timelines, and SysInfo Notification
[Samsung Galaxy Nexus] osm0sis:
Thanks I've been working out. :p

Those winning governor tunables are everyone's, not just mine. A lot of us tested to find them. :)

As for schedulers, I think I can safely say deadline and row are pretty much finalized. For cfq we're on to phase two now; just the 5 sync/async tunables left to play with. :good:

Then there's the whole mess of vm tunables to take a look at and a couple other random tweaks I'd like to get some opinions on. :silly:
[Samsung Galaxy Nexus] pez910:
I have been getting some audio clipping in Spotify on my Toro GNex. Any recommendations? I can't attribute blame to anything yet, so I posted this in the PA 3.10 thread, too.
[Samsung Galaxy Nexus] Khrushy:
That awkward moment when you realise you've been running noop for the last day because you forgot to reset your f.Ku data.

/facepalm
[Samsung Galaxy Nexus] mforminio7:
Hey guys, I know a few of you have been messing with governor settings/io sched settings/vm settings. I dont run fk so I cant comment on io settings since I use sio, but I have been using the interactive winning(small deviation by me with the above speed delay and hi speed freq) with great success so I thought id throw my vm settings in the pile for you guys to check out. Basically its as close to stockish (google knows best, right?) but keeps things in cache a little longer with a few more goodies that I think should be enabled by default. Been running great for me so have a look and let me know.
[Samsung Galaxy Nexus] Khrushy:
Thanks mforminio7, we'll check it out.

On the CFQ front I just spent a chunk of the morning testing a variety of quantum / slice_async_rq combinations.

quantum = 8

slice_async_rq = 2

(which is where we have it) is definitely the sweet spot.

quantum = 6 had a few really good numbers, with slightly better writes and slightly lower reads overall. The differences were well within the limits of test noise however, and more importantly, it lacked the consistency of quantum = 8.

Both raising and lowering slice_async_rq made things worse (tried with settings of 1 and 4, with different quantums, and all results were noticeably worse, and noticeably less consistent).
[Samsung Galaxy Nexus] osm0sis:
Great work! Good to confirm that again. If you'd be willing to take a stab at fifo_expire_sync/async and slice_sync/async the next time you've got some time, those are our final stop for cfq. There's also a slight possibility that adjusting those four will make a change in quantum and slice_async_rq work better. ;)
[Samsung Galaxy Nexus] malaroth:
Re: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

the updated script should be up by now with nomerges disabled and everything back to standard. Everything's still a lil rough for me. I'm gonna put osm0sis' site in my sig since people associate the tunables with me even though it's a massive group effort. :thumbup: to all who have contributed. This has gone way further than I dreamed
[Samsung Galaxy Nexus] Khrushy:
I actually just did that with slice_sync/async and there's definitely something to be found in this one.

Ballpark halved both values to slice_sync = 54 and slice_async = 23 and saw about a 3% improvement in I/O. More importantly though, it was damn consistent with it, and the low values for both read/write were consistently better than the low values using the previous settings.

I don't have time now to push this any further, so I'm going to run it for the rest of the day with these settings to see how it feels in use, then take a look at it again later to see if there's a sweeter point than just "halve it and see" :p

Edit:

Oh, and I found this on IO Schedulers - has info on Deadline, Anticipatory and CFQ - some interesting reading that's actually 99% plain english if people want to check it out.

https://www.dropbox.com/s/g0ua5u3wx2x6vqs/IO Schedulers.pdf