yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] Zadeis:
Now since dracon decided to run some tests I decided to feed my own curiosity too and ran my own tests. I ran these tests and across the board writes were pitiful. Absolutely downright bad. All of them were 1.5 megs a second and lower which is ridiculous. These tests were all done in rom toolboxes benchmark tool under the sd booster area.The overall test took quite long to finish too.

I then decided to set both rq_affinity and nomerges, since malaroths current script sets both to 2 I figured I would give them a try, back to 1 just too see what would happen. Not only did the test over all go significantly quicker but were all above 6 megs a second and reads were up in the 30s. This is using the current cfq settings that os posted recently.

I also was noticing that when I was transferring my nightly builds of cyanogenmod to my galaxy nexus it was painfully slow. I then tried transferring it wirelessly through Solid Explorer since I can access where I store my nightly builds through my network for easy transfer. It would transfer 1 or 2 megs and stop... then transfer 3 megs and stop then transfer a couple more megs then stop.

When I set the rq_affinity and nomerges to 1 the transfers went without a hitch and were completely fine.

Just now I changed the both of them back to 2 and all writes are back down to 1 meg a second. Which is just bad. Now I have not tried your new nr_requests and iostats settings yet but that is next on my list.

I hope all that info helps :D

Edit: Just for giggles I tried setting nomerges to 1 and left rq_affinity at 2 and things are still working fine so I'm thinking that nomerges should not be set to 2.
[Samsung Galaxy Nexus] osm0sis:
Thanks for the helpful tests! But please, test one setting at a time. Tell me which one makes the difference or if both are required.

Edit: Nevermind, since rq_affinity already reverts to 1, it has to be nomerges that makes the difference. ;) We already knew this. Next time please test one at a time though. :)

Edit 2: Whoa ninja edit. Thank you sir. :D

I'll look into why it's not setting in the init.d in a few minutes, but I'll tell you this right now, if it works on stock then it's your stupid ROMs' faults. :p
[Samsung Galaxy Nexus] Zadeis:
Yeah my bad for doing both at the same time. I mostly did that since I was trying to figure out why my phone was stuttering when it came to transferring files to it. Those two settings were my last things changed (since I had played with the new cfq settings prior to that also) so I went to those first and lo and behold I found the problem.

Wait you edited as I was posting this... gah haha!
[Samsung Galaxy Nexus] Khrushy:
Using

echo 2 > /sys/block/mmcblk0/queue/rq_affinity;

echo 1 > /sys/block/mmcblk0/queue/nomerges;

Both are correctly setting their values to 1 in the respective files on my init.d. I have those commands placed AFTER the wait though (I have all commands placed after the wait actually).

Edit: On an unofficial AOKP nightly here.
[Samsung Galaxy Nexus] osm0sis:
Ah you know what? It happens on stock on my GN too. Good catch guys! It's because Franco is setting them later in the boot. Putting them all after the systemui wait is a good solution though and might help with other ROM-related bullsh*t. Thanks! Attaching the fixed one to the original post now...

---------- Post added at 09:53 PM ---------- Previous post was at 09:23 PM ----------

Done! Added rotational 0 just to make sure some stupid ROMs aren't leaving that set to 1. Also added a date to the file so you know you've got the latest. :D
[Samsung Galaxy Nexus] malaroth:
Re: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

That's really strange... my dropbox copy comes directly from osm0sis. Gonna delete the file and upload again.

---------- Post added at 08:59 PM ---------- Previous post was at 08:11 PM ----------

I apologize for not being here to catch the posts. My sig has been changed. Got some real life issues occupying my attention lately so I'm sorry I wasn't quicker to fix this. Also changing my "notepad" to jota+ with lf formatting as standard so there shouldn't be issues. I wasn't seeing the spaces but it must have been in the formatting.
[Samsung Galaxy Nexus] irminsul:
Re: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

It's not that obvious, it must be something else. With the fku 190/195/215 I don't get a pink blush, but with the init.d it does so it must be something else. I tried to lower red till 130 and below that the blush disappeared, but the other colors were horrible clearly ;)

Very strange, just deleted the script and rebooted and it's fine now.
[Samsung Galaxy Nexus] Zadeis:
As far as I can tell Cyanogenmod has rotational set to 0. Both my tablet (TF300) and Gnex run Cyanogenmod and both default to 0.
[Samsung Galaxy Nexus] reysonance:
Could be magenta, try increasing the green multiplier.
[Samsung Galaxy Nexus] irminsul:
Re: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

Thanks, ill try later. But why would setting the multipliers via init.d cause a different effect than setting them by app? It doesn't make sense.
[Samsung Galaxy Nexus] Khrushy:
It doesn't make much sense, but it's been noted to happen multiple times by different people, so you're not the only one.
[Samsung Galaxy Nexus] osm0sis:
Did you try uncommenting (ie. removing the # from) the sleep in the script? That or try commenting it out if you already uncommented it for some reason. Explanation of the newer panel bug is in my settings post. :)

---------- Post added at 06:21 AM ---------- Previous post was at 06:17 AM ----------

Yup it's weird, indeed. On my old panel it made things way better as long as wasn't set during the boot animation (if it was there was purple galore). On my new one it looks weird and dusky unless the multiplier is set during the boot animation.
[Samsung Galaxy Nexus] bigbiceps:
my gnex wont reboot

i did a clean wipe, wiped internal sd, wiped cache n dalvik,

then flashed rbj rom, everything worked fine.

then i used the fku app to flash the kernel.

now my phone wont boot up. it is stuck at the google logo.

have i gone wrong at any step?

please help:crying:
[Samsung Galaxy Nexus] Angelakaro:
R: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

So i wasn't the only one having trouble with SD write speed

Inviato dal mio Galaxy Nexus
[Samsung Galaxy Nexus] irminsul:
I've got a gnex from the first batch in the Netherlands, removing the # from the sleep line did solve the problem apparently. But I really can't tell the difference between colors set by init.d or colors by fKu. For my eyes it seems the same :) But now I'm sure things are working well.

Another point of discussion:

Since 4.2 battery life has been worsened for me. At first I just blamed 4.2, but it's the network/wifi location service that is sucking the juice out of my battery. While turned off, battery drain is very minimal. I could lay it on my desk at work while on WiFi and it will drain <1%/h. But with the service turned on, my battery would easily drain for 40% idling on a working day. It's just not normal, back on 4.1 it didn't drain as bad with the service on. It's not kernel or ROM related also, happens on stock kernel + ROM, Franco + stock ROM, custom (AOSP) rom + stock/franco kernel.

Is anyone sharing these experiences? I don't know how the service works, or how we could lower it down. While turned off my drain is 'as good as it get' on the Galaxy Nexus (as in: still ****ty, but hey we learned to live with that). But I like Google Now, and some apps that relay on the service don't fully work.

Edit:

Seems the problem is discussed here but without any good solution other than 'turn it off'.
[Samsung Galaxy Nexus] Khrushy:
I was in the same boat. Particularly with 4.2.1 I found the battery drain with Google Now absolutely terrible, but couldn't bring myself to turn it off because, well, I like the damn thing, and that's why I have the phone.

But, for me, the jump to 4.2.2 and a few changes in the Kernel seem to have alleviated a lot of the battery issues, and I can't quite pin down why. Sure it's worse than with it off, but it's actually not a major issue - I never have a problem getting through a day anymore.

Part of the issue in working out why is that I've changed so many things recently. 4.2.1 -> 4.2.2. I used to use 1.5ghz max, now I'm just using 1.2. Deadline has changed to RoW. I've added the interactive tuneables. I've reset the VM settings to my own choices from the AOKP defaults. I've disabled pretty much every "set on boot" service and just set all that crap with a single init.d.

One other weird thing, that's definitely to do with location, but I have no idea what's going on, or whether it's the cause of the improved battery life, is that I've lost Latitude in my Google Maps.

It's definitely still enabled, I can find myself on my wife's phone, and location tracking is definitely still happening when I check my Google Dashboard, but in Maps on my phone, Latitude is just gone.

Anyway /end rambling post. I've got nothing solid to add, other than the fact that after changing pretty much everything about my phone recently, I've found Google Now to be less of a battery vampire than previously.

Cheers
[Samsung Galaxy Nexus] The Gingerbread Man:
Re: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1
[Samsung Galaxy Nexus] osm0sis:
No it doesn't make a difference with init.d colors now on my new panel. Sounds like yours is the same type. Basically I just do it for the seamlessness now.

As for drain, I'm down to 0.5%/h idle on Wi-Fi now that I solved my wlan_rx_wake lock. You should get BetterBatteryStats 1.12 RC11 from the xda thread and check out your wakelocks.
[Samsung Galaxy Nexus] LibertyMonger:
After trying Xylon for a while and fighting with getting kernels to work good for me I am finally back on Baked BlackBean and finally able to run Franco Kernel again. I was having all kinds of weird issues and with the latest builds haven't been able to flash Franco. Freeze up issues with AK kernel no matter what I do. Now I have a phone that just works and just works great. I always end up back with Baked and Franco. Running beautifully now.
[Samsung Galaxy Nexus] Khrushy:
Not being rude to those devs, but Xylon started to go funky for me as soon as they started to try optimising the kernel as well as building a heavily customized ROM. Having a small crew take on constantly updating a ROM + a kernel is too much IMO.
[Samsung Galaxy Nexus] creeve4:
After properly setting nomerges=1 (must be set with a delay), lag during app installs/updates from the Play Store is nearly gone!

This is with ROW and Deadline.
[Samsung Galaxy Nexus] whitedragonz83:
What was your problem with wlan_rx_wakelock? Or how did you fix it?

Also, I've been having some real screwing Network Location Services just on a ton messing up my idle time a lot. Annoying because I can't find a way to 'reset' it or improve it at the moment.
[Samsung Galaxy Nexus] osm0sis:
Factory reset of my router with DD-WRT. Testing as I went adding my settings back narrowed it down to my IPv6 6to4 setup. Somehow since JB4.2.2 that caused the brutal wlan_rx_wake lock of 20min/hr; Now it's down to a nice and normal 30sec/hr. :D
[Samsung Galaxy Nexus] irminsul:
Re: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

Thanks for the suggestions, I'm trying out now, turned on Google Now again.

Installed the new version BBS, I removed the play store version because it didn't work.

Another possibility would be blocking the Google Play Services (where the network location provider is bundled in) with auto starts. I don't know if it will work or break other stuff though.
[Samsung Galaxy Nexus] Tommy_FIN:
Re: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

So, it was your router after all. What router was it again? And what is that IPv6 6to4 setup? I have to check my router settings as well.
[Samsung Galaxy Nexus] osm0sis:
Well, really, it was JB4.2 "after all," since the exact same setup hasn't been a problem before. Luckily I could work around it by disabling a custom setting in DD-WRT. IPv6 6to4 maps IPv6 traffic to v4 on my router since my ISP doesn't support it yet.

http://www.dd-wrt.com/wiki/index.php/IPv6#6to4_Setup
[Samsung Galaxy Nexus] malaroth:
Re: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

Kinda depressing that there's really not that much more to do with the Gnex with all the newer nexus devices coming out. She's been a good phone. I don't want to replace her with a newer model
[Samsung Galaxy Nexus] ChazzMatt:
Keeping my two Nexus for another year (mine and my wife's). After having spent about $800 (including tax, shipping, cases, extended batteries, etc)for our two Nexus in July 2012, wasn't about to turn around and do it all over again over the LG Nexus 4 just a few months later. Plus, the LG Nexus 4 isn't that much better than our Nexus. Sure, it's nice, but more incremental improvement than evolutionary.

However, looking at the rumored specs of the Samsung Galaxy S4 being announce this month, it makes me wonder what Google has up its sleeve for a (Motorola?) Nexus 5 end of 2013. Will have to be as good as upcoming Samsung's Galaxy S4. At least 5" 1080p screen, and how many cores, how much RAM? ;)
[Samsung Galaxy Nexus] Zadeis:
Re: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

I'm trying to wait out until the next nexus myself. The gnex is my first cell phone ever and she's a great one at that.
[Samsung Galaxy Nexus] ChazzMatt:
I'm thinking of switching to Slim Bean for same reason. I switched to rooted stock ROM 4.2.2, due to the problems with Xylon. My wife's Nexus is still on Xylon 15 (4.2.1) -- still haven't switched her to 4.2.2.

I don't want a ROM that uses all my RAM and has everything including the kitchen sink thrown in. The smoothness of the stock ROM is nice, but I wish it had a few of the features found in custom ROMs.

Last weekend I discovered Slim Bean 4.2.2 doing a fixer-upper for a friend. She has a hand-me-down 2010 T-mobile Galaxy S Vibrant, which had 2.3 Gingerbread, but originally came with 2.1 Eclair. Ouch. Crashing on her, sluggish. She had researched some and saw there were allegedly ICS ROMs available for the Vibrant. I checked and there were actually Jelly Bean ROMs available for the Vibrant! :D

So, I took the challenge. 4" screen, 1GHz single core CPU, 512MB RAM. I had to downgrade from Gingerbread back to Eclair to even root (using tools found here at XDA), then flashed Slim Bean 4.2.2. That phone ran so smooth, I couldn't believe it.

I started thinking, wow, if it runs like that on old stuff... how it would run on my Galaxy Nexus? :confused: The GNex 4.2.2 Slim Bean ROM is only 86MB. Xylon is about twice that -- 165MB. Yet, running Slim Bean last weekend it had lots of stuff -- status bar, nav bar tweaks, an alternate launcher, Quiet Hours, etc. Only 86MB. Seems to be intelligent customization instead of just throwing everything at the wall and seeing what sticks....

Just thought I'd mention it.

http://xdaforums.com/showthread.php?t=2060396

Going to install it on my Nexus this weekend. If that goes well, then my wife's. :good:
[Samsung Galaxy Nexus] Kurre:
Re: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

@ChazzMatt, yes you do that. I have been a long time user and can only recommend it. You won't be disappointed ;)

Sent from my slimbeaned GNex :)
[Samsung Galaxy Nexus] stevensoaj:
Re: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

I also love SlimBean on the Galaxy Nexus, definitely a great choice. I've been trying a few others lately but keep finding myself thinking things like "Slim was smoother than this...." or "I wish this had a fast charge toggle like Slim..." so I'll probably be back on it soon.

Maguro | SlimBean 4.2.2 | AK Cylon 728
[Samsung Galaxy Nexus] vlc_marcos:
Re: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

How to fix the laggy during the updates on the app on play store. What is your configuration to fix this. Iam using cm10.1
[Samsung Galaxy Nexus] Sik-1:
Re: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

Either switch the io to noop or you can try the winning tunable from malaroth or osmosis
[Samsung Galaxy Nexus] peikojose:
And how is the battery life?

It looks interesting. how can be a 80Mb difference???
[Samsung Galaxy Nexus] stevensoaj:
Re: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

Always pretty good for me! Don't have any specific stats to share at the moment, but I'm never stressing to find a charger.

Maguro | SlimBean 4.2.2 | AK Cylon 728
[Samsung Galaxy Nexus] ChazzMatt:
re: Slim Bean 4.2.2

Maybe by only putting in the stuff that works and not the half-baked stuff that doesn't. ;)

I prefer a stable, lighter ROM with the best features cherry picked from what's out there.

Seems to have the best features of other ROMs ( AOKP, Cyanogenmod, CDA, Xylon -- Android is open source, after all), while not just jamming in EVERYTHING to make a bloated, sluggish ROM.

I have not yet installed it on my dual core Nexus, but it ran very well on my friend's single core Samsung Galaxy S Vibrant, which was released back in 2010.
[Samsung Galaxy Nexus] DoUevenRoot:
Re: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

Are you guys able to mount your sdcards as ext4 using this kernel? Not just a position, but the whole thing...

Sent from a computer masquerading as a phone
[Samsung Galaxy Nexus] Khrushy:
The largest single difference is a lack of Theme Chooser support, which gives a lot more freedom for the devs to minimize systemui elements. Throw in a few apps (CM and AOKP each have an additional ~ 15mb worth of non-core apps), and a few media files (~15mb again - seriously AOKP has ~10mb of video files of an Android in space, and a sunset - what the?) and you're rapidly shrinking your ROM size without any cost to functionality.

I do think the speed gains of Slim are being overstated however - the main point of the ROM was to have a small footprint for older devices with only 512MB of RAM, and maybe 2Gb of ROM, to leave as much space free for use as possible. That's not so much of an issue for the Gnex.
[Samsung Galaxy Nexus] asder00:
Could someone tell me if GPU is OC to 512 by default in 366 kernel please?

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

Its been standard for like how long now???? I can't even remember Lol
[Samsung Galaxy Nexus] asder00:
Okkk sry for stupid question but have gnex from a short time and I couldn't find this info... Thank y so much
[Samsung Galaxy Nexus] Sik-1:
Re: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

Its cool, no such thing as a stupid question , unless like you know you couldn't read lol

But anytime you don't know just ask we'll all help, just hit the thanks after:D
[Samsung Galaxy Nexus] xI mEzMeRiZe Ix:
Not sure if this will help with the IO discussion, but I have found that the issues aren't limited to Play Store updates/installs. Any CM users should try the CyanDelta app. If you're using franco.Kernel, building the new zip will take 3-5 minutes and your phone will become a laggy mess. If you use the stock CM kernel or LeanKernel (the only other kernels I have tried), building only takes 30 seconds to a minute with only a little bit of lag.
[Samsung Galaxy Nexus] peikojose:
Re: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

That is true
[Samsung Galaxy Nexus] osm0sis:
Have you tried it with nomerges 1 and read_ahead_kb 512 yet?
[Samsung Galaxy Nexus] pkgnex:
Os & Malaroth:

My cfq testing has me favoring quantum = 8, group idle = 7 (tried 1 per one of the "light reading" links, but it defaults to 7). I still can't tell any difference no matter what I set back_seek_max to, but lower quantum feels snappier, group_idle at 0 caused some odd freezes / lag, and group idle at 7 felt smoother than 15. Hope this matches what you're finding, or at least helps in some way. All the above is purely subjective, of course!
[Samsung Galaxy Nexus] osm0sis:
Thanks! Yeah I've been having some trouble with the idle ones as well. Try slice_idle 7 / group_idle 0, and then slice_idle 0 / group_idle 7, which feels better?

I lowered my max to 384 and believe I could tell a difference enough with back_seek_max seeming better at 1000000000 over any of the other values; maybe with he even number it just makes the calculations easier - it's over a terabyte either way. ;)
[Samsung Galaxy Nexus] gaich:
512 since r300:fingers-crossed:
[Samsung Galaxy Nexus] pkgnex:
I'll play with both those combos tonight, and I'll let you know what I think in the AM.

I can buy the 1 TB back_seek_max, I didn't try running at 384. Do you have any thoughts on the "quantum" value yet?
[Samsung Galaxy Nexus] stevensoaj:
Re: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

I'm not making a request or complaining, but does anyone know why sio isn't included in Franco.Kernel?

Maguro | SlimBean 4.2.2 | AK Cylon 731
[Samsung Galaxy Nexus] Khrushy:
Franco's response to that question last time was (IIRC): "Nah, what we've got is enough."
[Samsung Galaxy Nexus] lindarne:
A cry for help

First of all I need to say that i'm an idiot.

That said, on to my problem.

I accidentaly flashed the 4.2 kernel on to CM10 (4.1).

Now my gNex locks up at the initial splashscreen that says "google" and shows the open padlock.

The same happens if I hold the volume up button and power on the phone.

If I hold the volume down button and power on I'm taken to the download screen, but it locks up there before my pc can recoqnize it and manually flash the right kernel or CM10.1.

If i simply power on the phone my pc does recoqnize it, but obviously is not allowed to flash anything.

Have I permanently bricked my gNex? Or can anyone save me?
[Samsung Galaxy Nexus] reysonance:
Reflash the CM10 .zip, that'll fix it :good:

EDIT: If you don't have the .zip on your phone, boot to cwm and push the file via adb. You need to press volume up AND volume down btw, then you nerd to press volume down twice followed by a single power button press to select it. After that you'll find yourself booted right in the recovery.
[Samsung Galaxy Nexus] pkgnex:
Ok Os and Malaroth - here goes. Got some interesting results with cfq tunables. Quantum = 8 and back_seek_max = 1000000000 are definitely the way to go, bith subjectively and per some i/o benchmarks I ran. Funny thing is the benchmarks were best when both group_idle and slice_idle were BOTH set to either 0 or 7 simultaneously and it didn't matter if they were both 0 or 7. Performance dropped when the values were mismatched - again didn't matter which was 0 and which was 7, neither combination tested as well as both being either 0 or 7.

Any thoughts on why this may be the case?
[Samsung Galaxy Nexus] Piemo:
R: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

Sorry, is this kernel stopped in developing?

Sent from my Paranoid'd Galaxy Nexus swyping with my nose.
[Samsung Galaxy Nexus] pkgnex:
Nope. It's just reached a level of maturity and awesomeness that no longer necessitates frequent updates!
[Samsung Galaxy Nexus] reysonance:
It's been exactly two weeks since the last release, I would hardly call that 'stopped in developing'.
[Samsung Galaxy Nexus] lindarne:
that did it. yes!!!! thank you sooooooooooo much.

you just saved my day. :good:
[Samsung Galaxy Nexus] Piemo:
Sorry, but when you are used to see a release every 3-4 days, a 2 week silence make you think that something might be stopped. It's not a bad question for someone not following the thread everyday..
[Samsung Galaxy Nexus] motavi:
Keep on following :)