yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] franciscofranco:
Wow, thats new to me. I don't know really. I don't even know how to check that up. We'll see, thanks.

I have a lot to code before thinking about exporting the GPU frequencies to sysfs, and I don't know if it's possible yet. 512mhz is a bit unrealistic, and I see it cause more trouble than whats worth.
[Samsung Galaxy Nexus] aron7awol:
At first glance, it appears to me that it's getting throttled. Do a logcat and see what's happening...
[Samsung Galaxy Nexus] stesmi:
Logcat tells me only that the GC is doing stuff, nothing else is reported.

Anyone feel like doing the exact same test as me and telling me if I'm alone in this?

EDIT: Tested my wife's phone and it does the same thing. Same ROM, same kernel, same everything. (same method, ie we both have bought the franco kernel app to show support for this excellent kernel!)

// Stefan
[Samsung Galaxy Nexus] G0belet:
Use dmesg instead of logcat. logcat mostly logs application/system errors; dmesg is the kernel output. This is where you will find if there are any throttling errors happening.
[Samsung Galaxy Nexus] stesmi:
Yeah, dmesg shows throttling is happening.

I let it run for a more extended run and on her (not undervolted) phone it throttles even from 1200 where mine (undervolted) doesn't.

So it's simply throttling and not a kernel issue.

Good that got cleared up fast.

// Stefan
[Samsung Galaxy Nexus] aron7awol:
It's throttling due to heat? I did this test on my phone at 1.35 GHz and did not get throttled at all.
[Samsung Galaxy Nexus] stesmi:
Yes, due to heat.

According to StabilityTest it doesn't go above 37 degrees C. (My UV'd one doesn't go above 33 degrees C doing the same test, with phones lying next to each other).

// Stefan
[Samsung Galaxy Nexus] aron7awol:
Do you know at what temperature it starts throttling? I guess now we know another reason that these CPUs were underclocked to 1.2 GHz...

Edit: I'm doing another stability test at 1.35 GHz. I'm up to 31 degrees with no throttling yet.

Edit2: And now I'm getting throttled a bit at 33 degrees. Not too badly, my bogomips are still pretty constant with some intermittent throttling dropping them down for a second or so at a time.
[Samsung Galaxy Nexus] stesmi:
I set it to 1350/1350 now and let it run. It never left 30 degrees C before it started throttling.

dmesg reports:

<4>[34284.788574] omap_thermal_throttle: temperature too high, cpu throttle at max 1200000

<4>[34285.784545] throttle_delayed_work_fn: OMAP temp read 64600 exceeds the threshold

<4>[34285.784637] omap_thermal_throttle: temperature too high, cpu throttle at max 920000

<4>[34285.788543] omap_thermal_unthrottle: temperature reduced, ending cpu throttling

I basically stopped the test and ran dmesg as soon as it started throttling.

And yes, regarding Edit2: that's how I saw it the first time as well, that's what got me thinking.

// Stefan
[Samsung Galaxy Nexus] mixtapes08:
Re: [KERNEL][GPL][GN] franco.Kernel r372 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

It does work..

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Khrushy:
Hah. That original purpose was long before I showed up here then. I hadn't looked at what it currently has in it in ages.
[Samsung Galaxy Nexus] alangrig:
Re: [KERNEL][GPL][GN] franco.Kernel r372 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

Well, seems people having low speed write are subjected to bad emmc chip, cause with stock kernel and ROM 4.2.2 non-rooted, I have the results as follows on the first try:
[Samsung Galaxy Nexus] 843:
Does anyone know how to reset the Core Voltage settings? I set the voltage too low and I couldn't get into the app to fix it because the display kept flickering. For now I'm using another kernel as when I switch back to franco's the voltage setting returns to the low voltage values. Clearing franco's app data doesn't work.
[Samsung Galaxy Nexus] alangrig:
Re: [KERNEL][GPL][GN] franco.Kernel r372 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

And this is result with stock kernel and ROM 4.2.2 on the 3d attempt:
[Samsung Galaxy Nexus] Khrushy:
Try flashing Osmosis' emergency reset zip from CWM.

http://x.co/rHpF
[Samsung Galaxy Nexus] The Gingerbread Man:
Re: [KERNEL][GPL][GN] franco.Kernel r372 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

My gnex is fixed, updated to 372 and updated the fku which is now very cool with the new system monitor in place (thanks Christian if you follow here!). I did a quick SD test before flashing 372 on stock 1st run I had 10.4 mbs write and 11mbs read and after flashing 372 and running fstrim I'm achieving 9.4 mbs write but 23 mbs read! I'm very happy indeed and my gnex feels great and as fast as my gf s3 :thumbup:

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] neo-X:
I am getting 16.8 MB/s write on r372, is that normal? :confused:
[Samsung Galaxy Nexus] Antob125:
Re: [KERNEL][GPL][GN] franco.Kernel r372 -gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

So all the defaults with newest 372 have all our best current settings we tested?

Also not sure if I have an old script. Where can I get the newest?

Also which scheduler is the best atm? I've been using deadline with an old script I believe

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] kecinzer:
Slow write SD speed is definetely RAMDISK related.

I'm compiling franco.Kernel from source with ROM and never had slow SD write issue.
[Samsung Galaxy Nexus] Khrushy:
No, it's not normal, it's f**king awesome. (I'm getting about 10)

Most of the schedulers are performing pretty well, but out of the box right now RoW is the best - the kernel has all the queue and latest scheduler tweaks for RoW inbuilt already.

If you use that you can safely ditch the script and not have anything to worry about.
[Samsung Galaxy Nexus] neo-X:
All I did was run lagfix and stock Franco :angel:
[Samsung Galaxy Nexus] schumici:
Ynt: [KERNEL][GPL][GN] franco.Kernel r372 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

Thanks all off you guys, my sd card write speed fixed with r372 Thanks Thanks Thanks :D

Galaxy Nexus cihazımdan Tapatalk 2 ile gönderildi
[Samsung Galaxy Nexus] Fenvarien:
AW: [KERNEL][GPL][GN] franco.Kernel r372 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

I believe there might be a typo in the new implemented ROW default tuneables.

Osmosis script included:

lp_swrite_quantum with the value of "12".

But now there's only a "2" for lp_swrite_quantum.

Can you please try to confirm this?
[Samsung Galaxy Nexus] Khrushy:
This is correct. The desired value is 2, the value you input in the script to get a result of 2 on both GNex and N7 is 12.

Blame the crazy input scaling on the GNex and N7.
[Samsung Galaxy Nexus] Bosio91:
Hello world!

After trying out all the various ROMs and kernels out there, I've decided to move back to 100% stock and take some time to focus on obtaining the best results with this particular kernel. I love how active and helpful this thread is, and I've been a consequent follower of Franco's work since the beginning of his kernel for GNex. So here I am, to learn and help with whatever I can :victory:

My first question is regarding this script/zip that was posted:

Could someone please help me with a little step-by-step guide on how to apply this please?

Thank you!
[Samsung Galaxy Nexus] Khrushy:
Re: [KERNEL][GPL][GN] franco.Kernel r372 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

You don't need to. Just flash r372 and the stock settings are good to go. Most of the tweaks from the script are now inbuilt with 372.
[Samsung Galaxy Nexus] Fenvarien:
AW: [KERNEL][GPL][GN] franco.Kernel r372 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

Thanks Khrushy for the quick explanation. :)
[Samsung Galaxy Nexus] Bosio91:
Thank you! :good: :good:
[Samsung Galaxy Nexus] Antob125:
Re: [KERNEL][GPL][GN] franco.Kernel r372 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

So 100% row is the winner out of the box. Any everything else is left alone?

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

Pretty much. You can use RoW and stock settings and be confident everything is already tweaked and the slow SD writes from previous versions is fixed.
[Samsung Galaxy Nexus] Antob125:
Re: [KERNEL][GPL][GN] franco.Kernel r372 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

What about frequencies? Osm0sis are still the winners?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] osm0sis:
row is the only one we've finalized, deadline and cfq will be in there once we're done with them. Right now Franco has just literally cut and paste chunks of the script into /sbin/fixtunapower.sh, so I'll be interested to see if it actually works for everyone considering there were some who couldn't get it to work with the systemui wait on some ROMs. Better way is for Franco to actually patch the Linux scheduler code so that ours are the defaults, so hopefully he looks into that for the future; no reboot would be required and they'd just work with no scripting.

---------- Post added at 08:37 AM ---------- Previous post was at 08:33 AM ----------

Not mine, just the ones I use. They're the winners from rounds and rounds of testing from 10-15 people many of whom I listed in my post yesterday. Anyway, I still think these are slightly better than Franco's aggressive defaults which he chose himself and we didn't test. Franco also raised boost pulse for no reason considering we don't use boost, which bothers the OCD in me. :p

---------- Post added at 09:03 AM ---------- Previous post was at 08:37 AM ----------

Great findings! As I understood it the brick bug only occurs with a format, can discard trigger it as well?
[Samsung Galaxy Nexus] Culex316:
I'd like to thank franco and the people testing these new i/o scheduler tweaks for all their hard work and effort...I used to have a slight lag whenever I wanted to share something (be it a picture, facebook post or whatever)..the menu that appears asking you how to share it (facebook, MMS, e-mail etc) used to stutter bad in past kernels but with r372 this lag is gone!
[Samsung Galaxy Nexus] bunnahabhain:
Does this Kernel imply the new Wifi Drivers?
[Samsung Galaxy Nexus] thisguy23:
Re: [KERNEL][GPL][GN] franco.Kernel r372 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

I'm sorry for my tone. I really appreciate that people help each other in this forum even though we all ask the same questions a million times over.

I've had over 10gb free this since looking into the write speed issue. I removed the script. Reset Franco app. Ran fstrim again. Rebooted and am finally getting better numbers.

Thanks Franco for the updated kernel. Thanks khrushy for the help.
[Samsung Galaxy Nexus] Gafanhotz:
Pretty bad it still. :rolleyes:

--------------------

Just confirming what I read, setting the IO Scheduler to RoW, give better performance, right? I prefer deadline but i'll wait 'till franco updates with the thread settings.
[Samsung Galaxy Nexus] Khrushy:
Re: [KERNEL][GPL][GN] franco.Kernel r372 -&gt; 4.2.2 | -&gt; 4.2 | r300 -&gt; 4.1

Good to see some improvement, even if 6mb/s is still on the low side. If anything else comes to mind I'll let you know.

The differences between the different schedulers, once tuned, is pretty minimal - it's more a "what flavour do you like" thing than a "this one clearly gives the best performance". Deadline and RoW both have nicely working tuneables preloaded with 372. I happen to think RoW is slightly smoother - but try deadline and see which you prefer.
[Samsung Galaxy Nexus] Astug:
If you are referring to the 3.4.x wifi drivers, no, they are not included in this kernel because they are not WEP compatible.
[Samsung Galaxy Nexus] ChazzMatt:
I'm also getting that speed with 372.

Running ROW.

I have 5GB free on my SD card.

____________

UPDATE:

OK, ran FSTRIM, rebooted (as per FSTRIM suggestion), ran benchmark test, got 7.0. Slight improvement over the consistent 6's I was getting. Immediately ran the benchmark test again -- doing nothing different -- and got 9.3.

Go figure.

And ran it again and got 7.5. Very inconsistent?
[Samsung Galaxy Nexus] osm0sis:
Our tuned deadline didn't make it in. Not sure why. Maybe Franco saw me say maybe it could use another once over to be sure as saying it wasn't ready. Oh well, if we're all sure about it I'm sure he'll include it in the next build.
[Samsung Galaxy Nexus] Angelakaro:
R: [KERNEL][GPL][GN] franco.Kernel r372 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

Mine is getting ≈8 mbps write speed on antutu (noop) on r372

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

Seems like there isn't much problems anymore with r372?
[Samsung Galaxy Nexus] cucisan:
AW: [KERNEL][GPL][GN] franco.Kernel r372

on rasbeanjelly with stock kernel.. So not quite there for me 361 was the last speedy one

View attachment 1832670

sent from my important phone
[Samsung Galaxy Nexus] schumici:
Ynt: [KERNEL][GPL][GN] franco.Kernel r372 -&gt; 4.2.2 | r364 -&gt; 4.2 |

My sdcard write speed is generally this with 372. Sometimes it goes 11-12 mb/s. I'm so glad, after old 1 mb/s write speed :)

Galaxy Nexus cihazımdan Tapatalk 2 ile gönderildi
[Samsung Galaxy Nexus] Kurre:
Re: [KERNEL][GPL][GN] franco.Kernel r372 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

well, somehow my head is saying that someone has warned about using discard with problematic chips before kernel patching. :p And that patch in question would disable discard option if problematic chip is found (in a hardcoded way). So using the discard option with those chips wouldn't make any difference.

But I can't say for sure..need to dig those brick bug / fstrim threads up for some more information. :)

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

WEP - kill it. Kill it with fire.
[Samsung Galaxy Nexus] irminsul:
Re: [KERNEL][GPL][GN] franco.Kernel r372 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

There were more problems, as I reckon it broke WiFi tethering and caused some instabilities like WiFi signal drops that won't revive. Not only wep.

Verstuurd van mijn Galaxy Nexus met Tapatalk
[Samsung Galaxy Nexus] osm0sis:
Hmm.. Damn. I think I saw Franco had committed the fix for those chips from way back when he was still on bitbucket. Can't say for sure if it's in the current codebase though.

AK took an interesting approach. Released with the 3.4 WiFi drivers then has an add-on flashable zip that will revert to the old WiFi drivers if you tragically require WEP or can't live without whatever other minor problems there were like Tethering.
[Samsung Galaxy Nexus] Ronaldo Forenucci:
I'm waiving the white flag on 950iosettings. For some reason, I can't get it to work on my device. I spent a few hours this morning, trying every technique, and the values wouldn't change. Does an encrypted device matter? On r372 and RasbeanJelly 3-24 build. All permissions are 755, no sysctrl.conf anywhere I can find. Tried manual, and tried osm0sis' .zip. Cleared Franco cache + data, rebooted 100 times, etc... Deadline was always still 500/5000/4/0/1...or whatever stock is. Ah well, I don't reboot often, so I just set manually through the app.

RF
[Samsung Galaxy Nexus] osm0sis:
Sweet jesus. Good write speed. Do me a favor and download the following to your sdcard, rename it to settingsdump.sh, then run it from Terminal Emulator.

/sdcard/settingsdump.sh:

#!/system/bin/sh

output=/sdcard/r`cut -d\ -f1 /proc/sys/kernel/version | cut -c 2-`-output.txt;
location="/sys/devices/system/cpu/cpu0/cpufreq /sys/devices/system/cpu/cpufreq/* /sys/block/mmcblk0/queue /sys/block/mmcblk0/queue/iosched /proc/sys/vm /sys/module/lowmemorykiller/parameters";

echo "" > $output;
for target in $location; do
echo $target/ >> $output;
for file in $(ls $target); do
echo "`cat $target/$file`" $file >> $output;
done;
echo -e "\n" >> $output;
done;

To run it (assuming you just put it in /sdcard/) type: sh /sdcard/settingsdump.sh

Then put the contents of the /sdcard/r*-output.txt file it creates on pastebin.com and link us please. :)
[Samsung Galaxy Nexus] osm0sis:
The zip should be fool proof in terms of permissions, etc. I think there's ROM incompatibility somehow, sometimes. Though Ras is pretty clean so I'm not sure why there would be there... :(

With r372 do the new default tuned row settings work for you with

no

init.d scripts at all in /system/etc/init.d/?
[Samsung Galaxy Nexus] Empty Hand:
Re: [KERNEL][GPL][GN] franco.Kernel r372 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

As one who was having trouble with the 950io script, I can happily report that the row settings work with no script. Now all I need is to use is the color script that has always worked fine. :)
[Samsung Galaxy Nexus] osm0sis:
You have no idea how freaking bizarre that is considering it uses the exact same method, maybe just a little later in the boot. Oh well good to know we can just edit the ramdisk and jam more sh*t into /sbin/fixtunapower.sh if we ever want it to work universally! ;)

Hopefully Ronaldo can confirm. :good:
[Samsung Galaxy Nexus] bigbear6708:
Re: [KERNEL][GPL][GN] franco.Kernel r372 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

Is the GPU ob latest nightly clocked to 307 or is my phone reporting bad info?! Thought Franco hard coded 512?!
[Samsung Galaxy Nexus] osm0sis:
The GPU should still be 512 max. It ramps from 153 to 307 to 384 to 512 only as needed just like the MPU (CPU) does to meet load, so maybe that's what's confusing you; running at 512 constantly would be wasteful and silly. :p
[Samsung Galaxy Nexus] Sik-1:
Re: [KERNEL][GPL][GN] franco.Kernel r372 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

How is it possible for the gpu to be locked at a certain speed when setting the min clock speed to 729mhz????,

I would like to if its possible to lock that same clock speed for the gpu on the 384mhz of the CPU
[Samsung Galaxy Nexus] Raijin:
Re: [KERNEL][GPL][GN] franco.Kernel r372 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

So good results I am getting with r372 and Row.
[Samsung Galaxy Nexus] Gafanhotz:
O_O

27MB?! Is it possible?
[Samsung Galaxy Nexus] alangrig:
Re: [KERNEL][GPL][GN] franco.Kernel r372 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

Only if fsync off :)
[Samsung Galaxy Nexus] Ronaldo Forenucci:
Switching to ROW, and re-booting, IO Sched Tweaks shows:

100/75/5/4/4/3/2/15/25

In the script, I show:

100/75/5/4/4/3/12/10/25

So, no joy.

As an aside LagFix (fstrim) doesn't work on encrypted devices, but my read and write speeds seem ok with tweaked Deadline, fsync ON - ~15 MB/s read and 10 MB/s write according to AnTuTu. Remember, I run an ENCRYPTED device.

RF
[Samsung Galaxy Nexus] osm0sis:
No that's exactly what we want to see! :D

12/10 are input values that resolve to outcome values of 2/15 on the GN and 2/10 on the N7. Totally intended due to differing scales on devices, etc. I am both confused and pleased that it works from in /sbin/fixtunapower.sh for you where it doesn't from /system/etc/init.d/. :cool:
[Samsung Galaxy Nexus] Ronaldo Forenucci:
Ok then, GREAT! :D Can't wait for tweaked Deadline to make it into the kernel proper - for us init.d challenged device owners. As an aside, read_ahead is default at 512 - don't know if it is Franco or Rascarlo doing it, but it used to be 1024 on my device.

RF
[Samsung Galaxy Nexus] osm0sis:
All the general queue tweaks from the init.d script made it in too, so that's us. If you want to see exactly what is in there, open Terminal Emulator and type: su -c cat /sbin/fixtunapower.sh

:good:

The simple conditional backup and replace which I wrote for the PowerHAL so it doesn't strand stock ROM users when OTAs drop, Franco's debugging disabling to improve overhead, some commented-out leftovers from Franco experimenting with ZRAM, and a good chunk of our latest 950iosettings including my "disable sysctl" and "wait for android os". ;)

One thing I notice he took out is the launcher lmk exemption, like with my lmkwhitelist script. Not sure if it makes much of a difference though. I haven't seen any launcher redraws.
[Samsung Galaxy Nexus] Ronaldo Forenucci:
Awesome, will do. Thanks for continuing to teach...almost a year hacking on Android and I still don't know much! :D

RF
[Samsung Galaxy Nexus] Raijin:
No, fsync on. I only use Franco Kernel to download the new versions, always delete settings in menu.

Using the script downloaded from Osm0sis page of day 19 March. I still need to add the "disable sysctl". The only addons I have is "vm settings" as follow and governor tweaks (default Osm0sis, only added to init.d script), CPU max 1536. I have LagFix app scheduled every two nights.
[Samsung Galaxy Nexus] bigbear6708:
Re: [KERNEL][GPL][GN] franco.Kernel r372 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

In performance settings in my ROM, gpu changing ability is grayed out, and it shows the max level at 307. That's why I was wondering
[Samsung Galaxy Nexus] Spoderman:
Hello, i'd like to share something with you!

I've never had terribly lags, or any lags at all regarding the emmc ship, but none the less, i installed LagFix and ran it, it's been a couple of days now since i started to Trim, (i never experienced lag, i just like to be on the safe side, and i do have a faulty emmc chip).

I'd like to share this with you now, take a look:

I got those write speeds, with everyone here saying that the normal is 9-10! And i do have fsinc on, here are my settings!

Keep in mind that those clock speeds and thermal throttle off, were only like that because of the benchmark ;)

Have a nice day :)

Edit: Sorry for those enourmous images :/
[Samsung Galaxy Nexus] osm0sis:
Yeah that ROM interface doesn't go with franco's.
[Samsung Galaxy Nexus] Frenix27:
Bootloop for me with paranoidandroid 3.1 even if I downloaded the right version.
[Samsung Galaxy Nexus] bunnahabhain:
Damn i lost my 950iosettings - can anybody point me to it? I am running CM10.1...

I also have a color script (init.d) - can i just merge that 1 with the iosettings-script or should i hold them apart?
[Samsung Galaxy Nexus] ChazzMatt:
You didn't address that to me, but I'm wondering if Slim Bean ROM has some incompatibility problems. I hit 9.3 once but most other times I'm in the 7s even after using lagfix.
[Samsung Galaxy Nexus] shreddintyres:
I'm presently running Slim and only have seen my write speeds dip below 8 once, it may just be you particular device that doesnt like the combination of FK and Slim.
[Samsung Galaxy Nexus] mforminio7:
Re: [KERNEL][GPL][GN] franco.Kernel r372 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

Your dirty expire and writeback settings are actually stock. And you might have problems with such a low background ratio and such a high dirty ratio
[Samsung Galaxy Nexus] franciscofranco:
[KERNEL][GPL][GN] franco.Kernel r372 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

I have some ideas about those scripts.

I also plan to take a look into the sound driver and color control again through the knowledge I learned from mako.

Just need time :)
[Samsung Galaxy Nexus] shawnaye:
Re: [KERNEL][GPL][GN] franco.Kernel r372 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

And we've got nothing but time to provide. :D
[Samsung Galaxy Nexus] Edwrib:
Re: [KERNEL][GPL][GN] franco.Kernel r372 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

I was having really bad lag in 366+ in apps like chrome, to swype tabs out, but this last they're very nice! Ty!
[Samsung Galaxy Nexus] Khrushy:
After a bit more testing we came to the conclusion that the ratio settings weren't really a big deal - You're talking about such a big value given today's available memory that the defining writeback setting is the dirty_writeback_centisecs.

On stock this should be 2 seconds for expire and 5 for writeback, which is fine.
[Samsung Galaxy Nexus] osm0sis:
No no no.. Incompatibility with the way the init.d script works (or doesn't for those affected), not anything to do with write speeds. :)