yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] PAING1990:
Guys, please help me out. I just flashed Franco kernel r366 through the app from Play Store on my GNexus Stock 4.2.2 (Rooted). I think the performance seems to be better but battery life is much much worse. (12 hours, with 1 hour on screen time)

The real problem is I use battery widget reborn and last night, from 2 to 9 am, my phone data, wifi, notification were totally off except the Call/SMS. Even so, during that time, the battery drain was just so bad and it drained from 85% to 40% :(

I have not changed any settings after I installed except some minor color changes. Am I doing something wrong?

Thanks for your advice.
[Samsung Galaxy Nexus] whitedragonz83:
It is likely other issues. Bad cell signal, rogue app, GPS lock going crazy. I've had so many of these random things occur for no reason. I'd reboot, see what happens tonight/during the day. Most should obtain 2-3 hrs screen on with 24 hr between charges I'd imagine.

For sake of asking, what ROM are you using and what kernel did you come from?
[Samsung Galaxy Nexus] PAING1990:
Thanks for your reply. My GPS is always off. And in the battery report, I didn't see any other crazy app.

I just rooted my phone and the first thing I did was to flash Franco Kernel. The phone is relatively new (4 months) so I am sure battery is still in good health.

But I will see tonight and see how it performs.
[Samsung Galaxy Nexus] malaroth:
Re: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

I personally like the higher cache at 4096 but general testing seems to show it best down lower.
[Samsung Galaxy Nexus] mforminio7:
Re: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

Yea I'm finding most things in the VM should be lower. Dropped the Dirty ratio from 70 to 50 and background ratio from 50 to 20. Vfs cache at 50 seems to be the sweet spot. Also realized you probably shouldn't kill swap,but to make it a number less aggressive like 30.
[Samsung Galaxy Nexus] osm0sis:
No swap on f.K at all actually, so no point there. :p

First off give it a couple cycles to "settle" - some swear by this. I'd also try our winning tunables (check the settings post in my sig). Franco's defaults are a bit more aggressive with hispeed and target loads lower. I think ours are smoother too. ;)
[Samsung Galaxy Nexus] malaroth:
Re: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

Alright crack flashers, testers, tweakers and generally maladjusted settings changers. My sig now contains Osm0sis' Devhost site to get the latest, CORRECT downloads on iosettings. Perhaps we'll get vmcache settings up there soon as well but mine is going to be my own personal best settings while osm0sis will run the "winning" values since the winning ones work best for him
[Samsung Galaxy Nexus] EniGmA1987:
Sounds like your phone isnt deep sleeping, but simply staying at its lowest frequency setting instead
[Samsung Galaxy Nexus] osm0sis:
Only difference I'm seeing is you've got cfq bsm at the flat ~1TB still, and both group and slice idles at 7 where we only have group according to the Linux documentation for disabling the bsp on solid state drives.
[Samsung Galaxy Nexus] wavedashdoc:
Re: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

So I'm sure everyone noticed when the OTA leak of 4.2.2 Verizon (or Google) tweaked some settings with the default colors of the amoled screen. Personally I think the stock looks a lot better now. Randomly tonight I dug back into Franco color settings and messed with some of the bars and I think I've ended up with the best color settings. I have NO color discoloration. Blues are not over blown, whites are white and I think I've removed all purple/green discoloration on low brightness levels. I've been studying calibration for the last 2 years now, I did not use a cal-mon for these settings. I think you'll be please. Leave your feedback.

*remember ever panel is a different results may very.
[Samsung Galaxy Nexus] PAING1990:
So what should I do? It happened again last night and I think it is not deep sleeping :( It dropped from about 80% when I slept to 40% when I woke up :(
[Samsung Galaxy Nexus] Zadeis:
Better battery stats can be your friend in this situation.
[Samsung Galaxy Nexus] CADude:
This looks pretty good. I will make this my default!
[Samsung Galaxy Nexus] arhung:
Is franco going to forget our galaxy nexus and be concentrate to nexus 4? It seems a long time for no update...
[Samsung Galaxy Nexus] wavedashdoc:
Re: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

Patience. Plus its hard to improve on something that is already so well tuned. I think he might have hit a threshold. Try the new tunables if you haven't yet.
[Samsung Galaxy Nexus] mforminio7:
Ah I dont run fk so I was unaware. After the last few days of testing im convinced the stock dirty ratio and background ratio are best. Anything more and the system will allow an insane percentage of memory to be dirty and thats not a good idea. I think the stock 20% is more than we'd ever need. From linus torvalds himself "no amount of IO scheduling will make it pleasant to try to handle the situation where that much memory is dirty" Adjusting the vfs cahe presure and minfree are still good ides and will benefit android. Heres a nice little chart to show how much minfree is a good idea http://dd.qc.ca/people.redhat.com/kernel/min_free_kbytes.html. Ive chosen 3072 for now, taking into consideration that a portion of our ram is dedicated to our gpu
[Samsung Galaxy Nexus] Kurre:
Franco has pushed some commits to github few days ago, so maybe something is coming.. ;)

it's nothing special, but still there's an activity in case someone's are wondering.. :)

Sent from my slimbeaned GNex :)
[Samsung Galaxy Nexus] arhung:
I am trying the 950iosettings and 97pktweaks at the moment and the phone really runs great.:good:
[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

Franco kernel case anyone? I just saw this on Google+ http://www.cruzerlite.com/catalogsearch/result/?q=franco

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] joaonds:
Please, im noob.

How install this kernel with extension .img ?

I know .zip is CWM, and .img ?
[Samsung Galaxy Nexus] osm0sis:
Fastboot
[Samsung Galaxy Nexus] lightingcloud:
R: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

Or Franco's app.
[Samsung Galaxy Nexus] Ronaldo Forenucci:
950iosettings problem -

My read_ahead is getting set to 512, but going into scheduler tweaks in Franco's app, the numbers don't match what's in the script. I downloaded from the dev_host link. init.d in system/etc, permissions set correctly on both folder and file???? Stock read_ahead is 1024, so I know something is working. Same thing on my N7.

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

In the init.d folder, check to see if the sysctrl file is in there. If it is, just add .bak to it. Then reboot and check the values in Franco's app again.
[Samsung Galaxy Nexus] pkgnex:
97pktweaks FTW!

Seriously didn't know anyone picked those up.

We'll be collectively working on fine tuning the vm settings in the near future, but I'm convinced those values are a decent starting point... Been running them for nearly a year and haven't found any values that seem any better on my phone.
[Samsung Galaxy Nexus] xI mEzMeRiZe Ix:
Those look really cool, but white TPU takes on the color of your pocket real fast.
[Samsung Galaxy Nexus] shreddintyres:
just fyi for those interested do not flash Franco with BAMF paradigm, it will lead to boot loops, has something to do with the ramdisk from what ive read, i was under the impression that Franco Kernel utilized AnyKernel format which is required for Bamf but that appears to have changed.

if anyone has any suggestions to get it working i would appreciate it, back to my previous rom

EDIT

I talked to one of the BAMF devs it is an issue with the ramdisk, if you decompile the kernel then replace the ramdisk with theirs it should work while keeping all the other amazing fku tweaks

to decompile see another one of Osmosis's amazing threads, http://xdaforums.com/showthread.php?t=2073775

works perfectly in BAMF but it should be noted that their Ramdisk does not support init.d, might be enough for me to revert.
[Samsung Galaxy Nexus] Gafanhotz:
But what about the write speed bug? I had to fallback to r365 to had stable speed. Hope we get news coming soon.
[Samsung Galaxy Nexus] osm0sis:
If you read back we've had that figured out for awhile now. Our latest test script fixes it on r366.
[Samsung Galaxy Nexus] peikojose:
Re: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

Lagfix doesnt work , ir grays out the checkmarks.
[Samsung Galaxy Nexus] arhung:
Are you meaning the script from you and malaroth??
[Samsung Galaxy Nexus] akash3656:
Re: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

You could use this.

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

I use Trinity and Rasbean. This combo does not support init.d But with this app, it all works flawlessly. Give it a try.
[Samsung Galaxy Nexus] shreddintyres:
Re: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

I saw that im actually playing around with the the ram disk to edit th e init.rc to support init.d as well as to see the difference between the two so i can possibly integrate francos ram disk tweaks to improve the Bamf ones, aside from that there were a few things I found missing in Bamf so im looking into making the mods my self before I switch over permanently
[Samsung Galaxy Nexus] grognaz:
Re: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

is there a new script? the last i tested helped bu did not fox the issue.
[Samsung Galaxy Nexus] zoomy942:
Re: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

Is there a change log somewhere?

I didn't see one in the OP
[Samsung Galaxy Nexus] franciscofranco:
r370:

* Merge 3.0.70

* Merge new interactive patches from Google

* Merge new patches from upstream

* Device boots faster with this version

* Some minor fixes

* OTG should work fine now
[Samsung Galaxy Nexus] gaich:
I see I did miss something - what`s this?:eek:
[Samsung Galaxy Nexus] wavedashdoc:
Re: [KERNEL][GPL][GN] franco.Kernel r370 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

And he's back!
[Samsung Galaxy Nexus] Culex316:
Obrigado!!!!!!!!!!!!!! :laugh::good:
[Samsung Galaxy Nexus] dracon6ai:
Re: [KERNEL][GPL][GN] franco.Kernel r370 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

Just threw a quick test on the schedules. Write speed bug is still there. Another unusable update for me... Crap. Don't understand how it didn't get in there, Os and Mal found the fix over a week ago. Guess I'll chill on Lean Kernel till r371. Other than that it does run good for everything else.

Laziness is nothing more than the habit of resting before one gets tired!
[Samsung Galaxy Nexus] franciscofranco:
I changed the IO scheduler to noop to make sure that bug isnt there, I have no such problem.
[Samsung Galaxy Nexus] wavedashdoc:
Fixed for me. Also no lag/freeze installing apps from market. Thank you Franco!
[Samsung Galaxy Nexus] vinmoto:
Write speed bug is still there.

---------- Post added at 07:40 AM ---------- Previous post was at 07:30 AM ----------

although like normal
[Samsung Galaxy Nexus] franciscofranco:
I'm wrong, theres something ****ed up here. I couldn't reproduce until now. Just got my device deadlocked two times in a row. I got no clue what it is at this point.
[Samsung Galaxy Nexus] franciscofranco:
Think I just found the cause, it was memory leak patch for the memory allocator that Google merged for Mako, but I guess it ****s things up here. I reverted it and I couldn't reproduce the bug again after downloading 4 different apps from the Play Store.
[Samsung Galaxy Nexus] abalam:
Re: [KERNEL][GPL][GN] franco.Kernel r370 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

I do nothing of. What is actually the problem. I see nothing because of problems. Sit on deadline
[Samsung Galaxy Nexus] franciscofranco:
:eek:
[Samsung Galaxy Nexus] franciscofranco:
There r371 should fix everything back to normal. Sorry for the hassle!
[Samsung Galaxy Nexus] J-Hop2o6:
Sad to see your not here often like before :( But thanks for the update + quick fix :victory:
[Samsung Galaxy Nexus] franciscofranco:
I can't, I have no time to be in all threads and my main focus has shifted for Mako!
[Samsung Galaxy Nexus] J-Hop2o6:
*Looks at Maguro/GNex; feels disgusted* ... Lol, can't wait for Nexus 5! Hopefully you'll be there Franco :fingers-crossed:
[Samsung Galaxy Nexus] Moz007:
I do not know if this is related to the kernel, but on every boot, I have an application of updates.

Do you know how I can remove it?
[Samsung Galaxy Nexus] Edward Stanbury:
you might have an init.d script or app that wipes dalvik cache on boot ? cause i do not get that
[Samsung Galaxy Nexus] Angelakaro:
R: [KERNEL][GPL][GN] franco.Kernel r371 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

R371: SD card write speed sucks as in r366 (average 1.7mbps)..it's just me or anyone else is experiencing this? (I didn't touch any settings,the first thing i did after flashing was to put governor to performance and start benchmarking)

Inviato dal mio Galaxy Nexus
[Samsung Galaxy Nexus] Moz007:
i don't think so but how can i see that ?
[Samsung Galaxy Nexus] Khrushy:
Nope. I'm getting 8.4mbps atm on 371, which is already lower than the ~9mbps I was getting yesterday with 366, but that's not kernel related, it's due to me filling up the card too much in the last day.

I checked 366 vs 371 and both get similar write speeds.

Not sure what's giving you 1.7mbps, but that's truly terrible :-\

How full is your SD card? I find that when I start dropping below 2GB free then write speeds totally plummet. With 1.5GB free I only get ~5mbps, and with 1GB free I get only 2mbps.
[Samsung Galaxy Nexus] Angelakaro:
R: [KERNEL][GPL][GN] franco.Kernel r371 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

I still have 7.2 GB free. WTF?! Only from r366 i'm having bad SD write speed (and only on franco kernel but some days ago i restored r365 and it was normal..). Franco said he fixed it in last build,very strange

Inviato dal mio Galaxy Nexus
[Samsung Galaxy Nexus] vinmoto:
Re: [KERNEL][GPL][GN] franco.Kernel r371 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

Anttutu write 1.5 mb.s :thumbdown:

Отправлено с моего Galaxy Nexus через Tapatalk
[Samsung Galaxy Nexus] osm0sis:
If franco didn't also change nomerges back to 0 then it's not entirely fixed (haven't had time to update yet so I haven't checked). And that'll be regardless of scheduler change to noop since it's a general queue tweak that affects them all. Either way, the sdcard write seems to only be a problem for a couple people now, my guess is your sdcard was full at some point. If you're already running our latest test script for optimal scheduler settings then you should run Lag Fix (fstrim) and see if it helps.

Edit: Yup, in r371 deadline is still default with 350/3500/6/0/0 and nomerges 2. For shame Francisco, you haven't been reading your group emails? :(:p

Settings dump: http://pastebin.com/EcPAnd4q
[Samsung Galaxy Nexus] thegtfusion:
Re: [KERNEL][GPL][GN] franco.Kernel r371 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

Try trimming your storage. Search in play store : lagfix (fstrim).

It improved my speeds a little!

Sent from my Nexus Prime
[Samsung Galaxy Nexus] osm0sis:
Buddy, check your PMs? ;)
[Samsung Galaxy Nexus] PIKO1982:
R: [KERNEL][GPL][GN] franco.Kernel r371 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

For me 365 is the best
[Samsung Galaxy Nexus] Angelakaro:
R: [KERNEL][GPL][GN] franco.Kernel r371 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

I use fstrim sometimes,i already installed it a couple of months ago. It seems that trimming is not the way when this "nomerges" thing isn't disabled (correct if i'm wrong, i'm not familiar with these things)

Inviato dal mio Galaxy Nexus
[Samsung Galaxy Nexus] Culex316:
Re: [KERNEL][GPL][GN] franco.Kernel r371 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

Hey franco on your latest app update that you said fixed the voltage settings code my custom CPU voltage settings are not sticking after I exit the menu.

That is If I click on "decrease all voltages by 25 mv" it sticks but if I put in a value of my own then exit and come back whatever value was there before is shown instead of my custom value. And this only happens in the CPU undervolt menu the IVA and Core menus save my custom entered values just fine (tested them)
[Samsung Galaxy Nexus] osm0sis:
Exactly. Welcome to "the know". ;) Please get our test init.d script so that things are back to normal (or better) until Franco (hopefully) fixes it in r372 or something:

http://d-h.st/users/osm0sis/
[Samsung Galaxy Nexus] Angelakaro:
R: [KERNEL][GPL][GN] franco.Kernel r371 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

Mmm...i think i'm doing something wrong since it didn't fix anything..i have to install it as every init.d script,right? (Copy to etc/init.d,set permissions and group and reboot?)

Inviato dal mio Galaxy Nexus
[Samsung Galaxy Nexus] osm0sis:
One can only explain this so many times..

http://xdaforums.com/showpost.php?p=39425517&postcount=4868

If that doesn't work then your ROM is probably at fault. Remove /system/etc/sysctl.conf
[Samsung Galaxy Nexus] abalam:
Re: [KERNEL][GPL][GN] franco.Kernel r371 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

Without 950io settings

View attachment 1829705

With 950io settings

View attachment 1829706

big difference in writing!!
[Samsung Galaxy Nexus] Angelakaro:
R: [KERNEL][GPL][GN] franco.Kernel r371 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

Thanks! Sorry if i didn't search,but my PC is gone and it's really difficult and annoying to search through xda app :(

Inviato dal mio Galaxy Nexus
[Samsung Galaxy Nexus] abalam:
Re: [KERNEL][GPL][GN] franco.Kernel r371 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

sorry for the double screen:eek::eek::eek:
[Samsung Galaxy Nexus] grognaz:
Re: [KERNEL][GPL][GN] franco.Kernel r371 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

still 1mb/s write on 371 and the script does not fix the problem it just makes it less worse.

reverting back to 365 which works perfect.
[Samsung Galaxy Nexus] osm0sis:
Hey at least you thumbnailed them. That guy the other day who posted 6 full-sized instead of just writing out his color settings was a bit ridiculous though. :eek:

---------- Post added at 09:23 AM ---------- Previous post was at 09:23 AM ----------

You are what's wrong if the script "doesn't work," many have proven it, see the screenshots above. Follow the instructions I gave to Angelakaro.
[Samsung Galaxy Nexus] The Gingerbread Man:
Re: [KERNEL][GPL][GN] franco.Kernel r371 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

Check permissions....

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Angelakaro:
R: [KERNEL][GPL][GN] franco.Kernel r371 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

SD card speed restored :thumbup: (however it didn't work before cause i forget to delete the extension)

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

and insulting makes the script so much better... great way to deal with a problem.

i never said it doesnt work, it just does not fix the real issue with the cpu spikes.
[Samsung Galaxy Nexus] abalam:
Re: [KERNEL][GPL][GN] franco.Kernel r371 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

etc / init d ------> check permissions example with root explorer and check this on
[Samsung Galaxy Nexus] osm0sis:
Not an insult, just an observation meant for everyone. This isn't the init.d help desk thread, so people need to search. If the xda app or tapatalk make that hard, use Google to search it with site:xdaforums.com in your query. And yes, we already explained the "spikes" on CPU2 are present on Stock kernel, so if you have a problem, take it to Google. Which brings me back to "search", and "PEBKAC". If you're not willing to read I'm not willing to help, or at least don't expect me to be all sunshine and rainbows while doing it.
[Samsung Galaxy Nexus] grognaz:
Re: [KERNEL][GPL][GN] franco.Kernel r371 -gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

...
[Samsung Galaxy Nexus] osm0sis:
You is a plural. I did not directly attack you as you have just done me. Your post has been reported.* Have a nice day.

We have verified there is a problem on CPU2 but it exists on stock kernel at stock defaults so it's not franco.Kernel and there is nothing we can do. What more do you want? How do you propose we fix something that was either always broken, or that Google broke and we have no idea how or when?

* Edit: And moderated. ;)
[Samsung Galaxy Nexus] lippol94:
For convenience, I've been using a flashable zip created by myself to set IO optimizations that have been around since a while.

It copies init.d script to proper folder and sets right permissions.

@Osm0sis, if you want, feel free to upload it to your devhost account in order to have stuff more organized.

Cheers :)

EDIT: Removed my zip as Osm0sis published his own and improved version. If you have downloaded mine, please delete it and flash the new one :) Thanks Dude for it ;) This thread would be nothing without you and a few other members!

Wish you a great sunday!
[Samsung Galaxy Nexus] osm0sis:
Thanks! Great idea! :good:

The test scripts were never really meant for mass consumption and are changing on a daily basis as we work more out so that's why I hadn't really considered putting them in a flashable zip (that creates the init.d dir, ensures the correct permissions, etc.). But seeing as how it's turning more into an "ongoing workaround" situation, I'll take a look and likely put it up. :)

Edit: Yours has the old broken settings from 7-Mar though, that still have nomerges 2 which cripples write speed. :( Everyone sit tight and I'll do a zip up with the latest. :cowboy:

Edit 2: 24-Mar-2013 950iosettings is up in both raw script format for the savvy, and my own flashable zip init.d script installer for the less-savvy. Credit to lippol94 for the idea. :D I've got a new little bit of code at the top of the init.d script that disables sysctl.conf to hopefully resolve that annoyance as well. ;)

http://d-h.st/users/osm0sis
[Samsung Galaxy Nexus] dracon6ai:
Re: [KERNEL][GPL][GN] franco.Kernel r371 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

Wondering if anyone tried the scrip with r370. Franco said he thought it was the memory leak patch from Mako causing the issue but some already showed it wasn't that so I'm curious if the memory leak patch is still viable with the 950iosettings scrip. *Looks at the time* I got some time till church, will try some tests real quick. :D

Laziness is nothing more than the habit of resting before one gets tired!
[Samsung Galaxy Nexus] reysonance:
Running the script it just fine here, no negligible (if any) differences between r366 in the feel and benchmark department.

No freezes here so far, stutters on heavy i/o is still there, but it's always been here anyway and there's not much we can do.
[Samsung Galaxy Nexus] funkyblue04:
Re: [KERNEL][GPL][GN] franco.Kernel r371 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

I tried this again. My phone turns into a stuttering slow mess.

What causes this? I switch back to CM kernel and it's fine.
[Samsung Galaxy Nexus] osm0sis:
Probably nomerges 2. Flash the zip for our 950iosettings init.d script and report back please. :)

http://d-h.st/users/osm0sis/
[Samsung Galaxy Nexus] vinmoto:
fixed! good
[Samsung Galaxy Nexus] funkyblue04:
Re: [KERNEL][GPL][GN] franco.Kernel r371 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

Better but still not as smooth as it should be. Slow to wake up.

Nexus 4 arrives tomorrow so it does not matter too much.