yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] osm0sis:
Francisco has interactive defaults at his own variation over the winning tunables we chose because he likes his better. malaroth's latest tweaked deadline is in there. Only things missing from the latest scheduler tunables are the read_ahead_kb 512 and being able to set rq_affinity 2.

Commands are in my post a few pages back.
[Samsung Galaxy Nexus] franciscofranco:
So lets wrap things up: bunch of freezes and reboots using deadline, but not happening with other IO schedulers? Thanks.
[Samsung Galaxy Nexus] Sik-1:
Re: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

Yes definitely true, using row atm and the freezes are still there but minute, thinking of switching the old cfq and run that for a day to test
[Samsung Galaxy Nexus] Samhain77:
R: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

Just got temporary freeze updating apps from play store. Freeze are more intensive if phone go on standby while installing updates. But I've never had to pull out the battery. The phone come back to normality just waiting for about a minute after updates complete.

I'm on 366 with default configuration on a stock 4.2.2 rom.

I'm going to test if this also happen with cfq.
[Samsung Galaxy Nexus] franciscofranco:
[KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

Did it happen on r365?
[Samsung Galaxy Nexus] franciscofranco:
[KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

Does it happen with noop?
[Samsung Galaxy Nexus] Samhain77:
R: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

Yes
[Samsung Galaxy Nexus] wavedashdoc:
Not getting any stuttering or slow down when downloading apps, only one complete freeze up that resulted in the phone soft rebooting. (Was having the market download slowness on PA 3.0 before) Now I'm running MMuzzy 4.2.2 2/17 French Vanilla with Osmosis tunables and franco 366.

Glad to see you haven't forgotten the GN crowd Franco! Keep up the good work!
[Samsung Galaxy Nexus] Sveke:
Re: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

Smooth sailing here. 366. Deadline Westwood.
[Samsung Galaxy Nexus] psyren:
Quick report: flashing 366 gave me bootloops on first flash with all default settings with regards to CPU (voltages, clock speeds, etc.).

I did a cache/dalvik wipe (even though I know it's not supposed to do anything) because I know someone will suggest it, and it seems to have stopped the bootloops.

More curiously, though, flashing this kernel has broken my wifi toggle widgets AGAIN.

I can turn wifi on fine, but turning it off makes it FC, citing java.lang.SecurityException as the reason.

I've had this issue on previous ROMs (Xylon/Xenon), but surprisingly, it was fixed after a back up, flash of a different ROM (PA3), and a restore back to Xylon 18...

I've run fix permissions several times (and newest Xenon has a startup script to do this...), but it doesn't seem to do anything.

Any ideas? I know that this kernel is most likely NOT the cause of my widget breaking, but it was working fine before flashing 366 automatically through FKU, and now... yeah.
[Samsung Galaxy Nexus] Kurre:
Re: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

I had those playstore freezes with r364 also (I haven't gone to 4.2.2 rom yet). I were using those deadline init. d tweaks guys introduced. Can io tweaks be too "aggressive" and cause this?

ps. I think I had freezes with row (also used it with tweaks, fixed ones) also..but I can't be sure :(

Sent from my slimbeaned GNex :)
[Samsung Galaxy Nexus] AutomaticFailure27:
Pretty smooth on 366. Deadline and all that jazz.
[Samsung Galaxy Nexus] lippol94:
R: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

I'm using row and sometimes I have tiny freezes on typing with the consequence of keyboard crash.

Plus, I could never get rid of those freezes while installing an app.

Thanks.

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

It only happened with r365 for me, no issues or freezes with r366 interactive/deadline. :) :good:
[Samsung Galaxy Nexus] sajty:
I have not any freeze with r365 or r366 when installing app with ondemand/deadline and ondemand/noop either.I doubt,that problem is scheduler.Maybe interactive is the problem?
[Samsung Galaxy Nexus] reysonance:
Been running interactive/row here for weeks and no freezes or reboots so far.

The only freeze I get when I purposely spam the capture button when trying out CM's new HDR mode, but that's my own stupid fault anyway.
[Samsung Galaxy Nexus] sajty:
Hmmm,its challenge for franco :D
[Samsung Galaxy Nexus] slvrarrow:
Freezes and 'sticking' when opening new apps or switching between apps or when using SwiftKey on previously butter smooth bfq /interactive. Deadline /interactive seems to avoid this, but is slightly worse at scrolling. Rom is latest cm10.1
[Samsung Galaxy Nexus] amith007:
Man.. i miss that r361 performance... need the same in 4.2.2 .. that was the best kernal i have used till date..
[Samsung Galaxy Nexus] rossrogers:
Playstore Freezes

Franco,

For me, and possibly others. The playstore freeze seems to happen specifically on boot sometimes. For example.

Boot phone, while phone is still running media scanner and other boot services the playstore will begin to update an app, once the update switches from downloading to "installing", it starts to lag excessively and freeze. My only theory is that the "reads" are over prioritized and causing the "writing" of the app data to cause some sort of crash. I know others are reporting other circumstances. But I've had this behavior on your kernel for many releases now. Probably since 361 or 362? Not really sure. The same thing does not happen with Lean, even though it has default ROW scheduler. So maybe the tuning is different? It is severe enough that when I clean-flash a ROM I will flash lean first, let all my apps restore from the playstore, and then use your app to flash the franco kernel.

For me, it is seriously a playstore installing issue only. All other operations are buttery smooth and flawless.

Just my anecdotal evidence, hope it helps. (Happens on deadline and ROW for me with all stock voltages and all other settings the way you have them, but a "crash" or "freeze" does not happen all the time, so hard to test and/or track down)
[Samsung Galaxy Nexus] malaroth:
[KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

Try this with row. Set your values to 100/75/6/5/4/1/1/15/25

I really didn't want to leak this out yet but I'm pretty sure that it's a coincidental playstore screw up with coding that isn't gonna be easily fixed on Franco's end. Lean is minimalist so there's not going to be extra functions to misbehave around each other. These values have been tested by myself and some others for quite awhile and generally diminish the lags. As with ALL software, nothing plays exactly the same on every single device.

* as a side note... YES I have studied up on the functions of each value. NO I'm not an expert, but I've tested privately extensively before soliciting others help in testing before even mentioning it here. If you decide to set your values differently and it doesn't work... I suggest you find some documentation to learn why. (Not a specifically targeted suggestion)

Franco r365

JBSourcery 4.5.5

---------- Post added at 09:38 AM ---------- Previous post was at 09:32 AM ----------

Ondemand means your phone boosts to Max CPU "on demand". If you want your CPU running full throttle that's one way to fix it

Franco r365

JBSourcery 4.5.5
[Samsung Galaxy Nexus] Angelakaro:
Guys, i did some benchmarks using antutu and i get very poor SD write performance (less than 2 mb/s) but normal SD read speed (30 mb/s). I do not care really much about antutu,but i think it's not normal. What do you suggest?

EDIT: i just restored the stock kernel,without wiping anything, to test if it was something in the kernel: i'm getting 9 mb/s write speed now o.O WTF...if someone uses antutu,can you please check about your sd performance? Maybe it's an antutu bug
[Samsung Galaxy Nexus] shreddintyres:
Antutu and 99% of all other benchmark programs are horridly inaccurate, additionally depends on the scheduler you have chosen, ROW theoretically should give you higher Read speeds and lower Write speeds.

If you want to test read/write speeds id suggest downloading an application specific to testing sd card, sdcard test is one i used to use and values are fairly consistent from what i recall using it on my old Vibrant.

- Cheers
[Samsung Galaxy Nexus] Angelakaro:
In fact i do not care about it ;) ah, i also used andro bench and everything seems ok. However i'm using deadline...the strange thing is that antutu + franco = bad sd performance, but antutu + stock = normal. However, r366 is great till now,
[Samsung Galaxy Nexus] jltorrente:
Hmm, battery life is down the drain for me... Last night I lost 15% when the phone was on Deep Sleep.

Here is the BBS log.http://dl.xda-developers.com/attachdl/46d474c18db173af263aba24d8816fca/512e2f3c/1/7/6/5/7/6/0/BetterBatteryStats-2013-02-27_105439510.txt
[Samsung Galaxy Nexus] bigknowz:
ROW adjustment

Should I change the row script from 100/75/5/4/3/1/1/20/25?
[Samsung Galaxy Nexus] The Gingerbread Man:
[KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

Try using row perhaps. Scrolling is very smooth within gallery or file manager / anythng where theres a significant amoint of data. If performance is still bad you could try an sd clean up app like for ever gone which might help https://play.google.com/store/apps/details?id=com.kovit.p.forevergone&hl=en.

Your link is giving a 410 error. Look through your wake locks and Google any you don't understand and look into changing your application settings / choice of applications with excessive services running draining your battery

Yes.

To franco, can you shorten your threads title by 2 chars as when I edit my post Tapatalk app complains about thread title length being too long :p: sly:
[Samsung Galaxy Nexus] malaroth:
[KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

Change 5/4/3/1/1/20/25 to 100/75/6/5/4/15/25 ....20/25 is for the n7

Franco r365

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

I used that app some time ago. The problem is that with stock kernel i don't have this "performance" drop. (I wrote "performance" cause it's only antutu giving bad results,i don't think my SD partition it's actually slower).

Inviato dal mio Galaxy Nexus
[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

Well it just goes to show bench marks don't always show accurate or reliable or consistent results. Personally I try to avoid them, they can be helpful at times but only if you work out an average from a load of results and compare averages. If you want to run them I would recommend https://play.google.com/store/apps/...sMSwxLDEsImNvbS5jZ29sbG5lci5iZW5jaG1hcmsiXQ..
[Samsung Galaxy Nexus] Angelakaro:
R: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

Thank you! As i said,me too don't rely in benchmarks,but i think the only thing is useful is 2D/3D graphic test,which most of the times gaves the real GPU performance. However i repeat that i'm not disappointed about test results,just curious about this little bug: trinity kernel gives the same result so it's definitively an app bug

Inviato dal mio Galaxy Nexus
[Samsung Galaxy Nexus] Schneewitzchen:
AW: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2

Just tested these settings. For me the 4 ( lp_swrite_quantum) doesn't stick. Everytime i set it, it switches back to 1.

Btw the settings are really smooth!
[Samsung Galaxy Nexus] bigknowz:
Works in script

I use a script and its working. Did you copy the init.d in malaroth's signature?
[Samsung Galaxy Nexus] osm0sis:
Stock uses read_ahead_kb of 128, franco uses 1024 right now. Try our suggested value of 512 or lower.

4 isn't for lp, it's for rp. lp write is really weird and doesn't accept values like a normal tunable so we should probably leave it alone.

Check malaroth's script for the correct names you're applying the 6-5-4 to. :good:
[Samsung Galaxy Nexus] malaroth:
Re: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

Oops again... that should be 100/75/6/5/4/1/1/15/25.... but just download the script in my signature. Even if it's just for reference you'll have the correct numbers

Franco r365

JBSourcery 4.5.5
[Samsung Galaxy Nexus] Schneewitzchen:
AW: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2

I read it wrong! The way malaroth described wich value has to be changed was a little bit confusing!

I think i got it now! Thx os and malaroth
[Samsung Galaxy Nexus] natzy85:
Re: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

Does Franco kernel have improvements over mic gain in video recording? Thank you!
[Samsung Galaxy Nexus] neo-X:
Re: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

I too get this freezing upon updating apps from app store. Has anyone realized that there has been an update of the actual app store? It could be that...Google could have ****ed something up. Old version was 3.10.10 now its 3.10.14 :sly:
[Samsung Galaxy Nexus] Raijin:
Re: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

When I try to download the script in the signature of Malaroth...
[Samsung Galaxy Nexus] The Gingerbread Man:
[KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

I think he's updating them

I have thought that myself that its the play store not the kernels fault
[Samsung Galaxy Nexus] lightingcloud:
R: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

Actually, I haven't got freezes since last google play version. But I think it's because at the same time I flashed minco v6.2.1
[Samsung Galaxy Nexus] Samhain77:
R: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

Why I haven't the init.d folder under system/etc? I've installed the zip version from cwm. It should create that folder, right?
[Samsung Galaxy Nexus] reysonance:
IIRC, if the folder is empty in the .zip (which it is), it won't create anything.
[Samsung Galaxy Nexus] osm0sis:
Nope. Franco hasn't implemented my proper init.d creation stuff into the zips yet. If you want you can flash my emergency reset zip (in my sig) and that has the side effect of setting up the init.d directory correctly. ;)

Bingo. :)
[Samsung Galaxy Nexus] reysonance:
The Play Store just updated itself today (to .14), and I had a freeze when updating apps, luckily the Play Store commit suicide while it was freezing, which seems to fixed it.

So it may just be the Play Store after all.
[Samsung Galaxy Nexus] malaroth:
Re: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

Was it the row-tuna.txt? Yeah something screwy happened I opened it in dropbox and it errors after. Fixed now

Franco r365

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

BTW....

This is not antutu...

Franco r365

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

Nice i always test with benchmark and tuning also already get consistant results

---------- Post added at 09:09 PM ---------- Previous post was at 09:07 PM ----------

I always get consistant results with that app

---------- Post added at 09:10 PM ---------- Previous post was at 09:09 PM ----------

I always get consistant results with that app
[Samsung Galaxy Nexus] reysonance:
Probably more stable since the benchmark itself is very short, which means less possibility of thermal throttling ruining the scores.
[Samsung Galaxy Nexus] Sik-1:
Re: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

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

It was developed with Franco. It's reliable. I put Max load on my Gnex and results are solid. It's just a benchmark though it does point me in the right direction

Franco r365

JBSourcery 4.5.5

---------- Post added at 11:31 PM ---------- Previous post was at 11:30 PM ----------

Got a question for ya Rey... shoot me a pm

Franco r365

JBSourcery 4.5.5
[Samsung Galaxy Nexus] Edward Stanbury:
Hey malaroth do you use ROW or deadline for everyday use? (or something else ;) )
[Samsung Galaxy Nexus] lightingcloud:
This is my init.d script

Sometimes at boot I notice the screen does a weird flash, green or yellow, even a dotted pattern. Should I put another sleep somewhere?
[Samsung Galaxy Nexus] reysonance:
Hmm, that's odd. Try removing the line that refers to the gamma setting from your script, does the issue persist?

P.S. You might want to move the governor tunables down the bottom after the sleep 35, I had multiple instance of the governor tunables not sticking if I put it up first.
[Samsung Galaxy Nexus] osm0sis:
That's the omap gamma (and that glitch is what made me start using init.d for colors in the first place ;)), you've got it set to 5 (default) so you can remove that line entirely, or if you still want to keep it, just put it before the first sleep 2.

Also you don't need the second sleep 2, just one of those will suffice if you've got the panel issue I described in my settings post. :)
[Samsung Galaxy Nexus] lightingcloud:
no problem with governor tunables, actually, but I have modified my script and now it looks like this

We'll see, the flash happens kinda randomly, I can't replicate them that easily...
[Samsung Galaxy Nexus] osm0sis:
You don't need those deadline tweaks for r366, they're default now. :)
[Samsung Galaxy Nexus] lightingcloud:
I'm on MiNCO v6.2.1, Franco Kernel r364, can't update to last kernel release 'cause I don't want to change ROM (and the other one I'm interested in is still at 4.2.1) :D
[Samsung Galaxy Nexus] osm0sis:
Ahh.. well then, at least try the latest and greatest from r366 ;):

echo 512 > /sys/block/mmcblk0/queue/read_ahead_kb;
echo 2 > /sys/block/mmcblk0/queue/nomerges;
echo 2 > /sys/block/mmcblk0/queue/rq_affinity;

echo 350 > /sys/block/mmcblk0/queue/iosched/read_expire;
echo 3500 > /sys/block/mmcblk0/queue/iosched/write_expire;
echo 6 > /sys/block/mmcblk0/queue/iosched/writes_starved;
echo 0 > /sys/block/mmcblk0/queue/iosched/front_merges;
echo 0 > /sys/block/mmcblk0/queue/iosched/fifo_batch;
[Samsung Galaxy Nexus] lightingcloud:
I rebooted twice and no glitch so far. But I noticed that read_expire is set to 351 no matter what I do :/
[Samsung Galaxy Nexus] reysonance:
Totally normal, I would dig up a post than explain this, but my Search-fu is awfully weak today.

EDIT: Never mind, my Search-fu is back!
[Samsung Galaxy Nexus] lightingcloud:
I remember reading something about it and I know it's kind of normal, I was just pointing that out :)

EDIT: I also tried moving governor tunables after sleep 35 but they stopped working, I switched them back and now... they don't work anymore? :/ and rq_affinity is set to 1 ?_?
[Samsung Galaxy Nexus] jcmm11:
Re: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

Make sure the governor tunables are set to run last. In my case I have to precede them with a long sleep. Currently I'm using sleep 90. 45 is definitely too short for me and I suspect I had tried other values in between, but it's been awhile and don't remember for sure.
[Samsung Galaxy Nexus] lightingcloud:
What I don't get is why with this file they work

and with this one they don't

also, the last one leaves rq_affinity to 1.
[Samsung Galaxy Nexus] Raijin:
[KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

Thank you friend.

These days my phone is running like it should run always. So fast. We all appreciate the work you all make for us.
[Samsung Galaxy Nexus] osm0sis:
rq set to 1 is normal on the GN as well. On devices that can go to 2 (like the N7) we want that, so these are just the universal settings, much like 350 -> 351.

---------- Post added at 02:36 PM ---------- Previous post was at 02:23 PM ----------

Yup. Not all devices or ROMs boot in the same amount of time, to workaround this I wrote a wait for android os bit into my init.d to set the iosched tweaks after. Check my combined universal script in malaroth's sig (950iosettings). It requires you have f.Ku or Trickster setting the scheduler of your choice on boot, but after that the script sets the correct tweaked tunables. I tested it by wiping dalvik to increase boot time and it works perfectly. :)
[Samsung Galaxy Nexus] Empty Hand:
Re: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

I just applied malaroth's row script and my values are 100/75/6/5/4/2/2/15/25. I thought it was 100/75/6/5/4/1/1/15/25. Was it updated or (more likely) did I do something wrong?
[Samsung Galaxy Nexus] malaroth:
[KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

Updated.... though that may change LOL... you're values are correct

Remember that these tunables are just like the governor ones. We're constantly updating and testing until we find the sweet spot. Rest assured that if they're in my sig that they've been checked solid. If we find something smoother we update the sig

Franco r365

JBSourcery 4.5.5
[Samsung Galaxy Nexus] osm0sis:
Try 6/5/4/3/12, it will end up as 6/5/4/3/2; these are the ones in the universal script and which I'm liking best at the moment. ;)

Subject to change of course. :p
[Samsung Galaxy Nexus] malaroth:
Re: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

Quit hogging all the attention osm0sis. Gosh! Really.... you got the n7 forum:'( poacher :P. LOL those new values ARE pretty sweet but that's why I said they'd probably change. I won't change my script in my sig till I've personally tested them. So far so good :thumbup:

Franco r365

JBSourcery 4.5.5
[Samsung Galaxy Nexus] osm0sis:
Haha it's okay bro. I'm about to get real busy again with school so you can have all the attention from now on. ;)
[Samsung Galaxy Nexus] creeve4:
osm0sis,

When using your init.d script for colors, do I need to worry about the f.KU color settings? Is there a way to stop f.KU from applying color settings?

I ask because you have said:

I'm just curious if having f.KU set the colors interferes at all with the "completely different result" that is achieved using an init.d script.
[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

You should enter the values in your init.d to match what you set in the fku app. What he means by having a different appearance is the colours seem more natural when set with init.d and the app together. You see when it gets loaded just before the boot animation begins.
[Samsung Galaxy Nexus] Khrushy:
What editor is everyone using for their init.d scripts? I've just been using plain old notepad, but it's been throwing in annoying formatting occasionally which then takes a bit of tomfoolery to iron out, and I figure there must be something better for it.
[Samsung Galaxy Nexus] reysonance:
I just edit it directly on the phone, typing it out is painful, but it saves it to UNIX by default which saves me the extra headache.