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

Okay. I only ask because I can get much better read and write performance on other kernels using sio than what others have been reporting with various Franco.kernel schedulers. See below. And yes, I know benchmarks aren't everything, but when the difference in scores is this dramatic, user experience is obviously going to be better.

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

Oops, wrong screenshot. This one shows the actual read/write rates.

Maguro | SlimBean 4.2.2 | AK Cylon 728
[Samsung Galaxy Nexus] Fenvarien:
I can't confirm that. I'm using CyanDelta since months and never had any special problem with franco.Kernel. LeanKernel and Fancy Kernel both don't change the performance of the zip-building process in comparison to f.K. This is just a demanding task and you can't expect to run apps fluently side-by-side with this.

Today, with ROW and the current magic tunables, I experienced improvements regarding the speed of the build and was able to browse and read in Tapatalk while CyanDelta did it's work in the background. :good: The whole process of building/adding the zip took not more than one minute.
[Samsung Galaxy Nexus] bigknowz:
Trickster

New version of paid Trickster allows you to set/check the scheduler tweaks mentioned in this thread.
[Samsung Galaxy Nexus] arhung:
Re: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

I have using r366 for some days, it seems deadline is good battery and row is good for response/smooth.
[Samsung Galaxy Nexus] androidkid311:
Re: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

This installing app lag is beyond painful. Can you show me where those turntables values are.
[Samsung Galaxy Nexus] Sik-1:
Re: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

They are bin osmosis sig and or malaroth's
[Samsung Galaxy Nexus] wavedashdoc:
So I've been running Os and Malaroth's tunables with the default governor settings in 366 with deadline and I have been having great performance. I was just messing around in the Franco App a little while ago and I changed a few settings. Now I'm getting even better battery life while idle and screen on use! I changed the hispeed_freq to 537 and the min CPU Frequency to 192. Now before, on previous versions of Franco Kernel, (Pre 4.2 days) lowering frequencies, even by a little, would result in a lot of stutter and lag. With 366 and these settings so far there doesn't appear to be any negative side affects. It's also interesting to note that sometimes when idling the one core will jump up to 537 or 729 while the other idles at 192. I have never seen only one core fluctuate independently before.

Thoughts? Feedback with these settings?
[Samsung Galaxy Nexus] JBNex:
Re: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

What settings for Franco Kernel app are you using and what performance tweaks do you guys have causing such high benchmark results? :eek:
[Samsung Galaxy Nexus] Edward Stanbury:
I use the same settings as osm0sis but different undervoling

http://xdaforums.com/showpost.php?p=34951507

and also this script to set the i/0 settins on boot:

https://www.dropbox.com/s/h2sytxb65ym93ew/950iosettings
[Samsung Galaxy Nexus] osm0sis:
According to the redhat tuning guide for SSDs/high perf drives (of which Flash should count), slice_idle SHOULD be 0, and then group_idle should be non-zero for best results. Then according to the notes on the group_idle patch/article I dug up group_idle at roughly 8 is ideal. So them being better together is just bizarre. No thoughts on why that would be, unless cfq just behaves differently either because it's Android or because it's Flash. I take it you're doing multiple tests and just taking the average consensus? If so, between both being 0 or both being 7 was there a winner?
[Samsung Galaxy Nexus] stevensoaj:
Re: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

If you're referring to the benchmarks I posted, those aren't with Franco.kernel. I apologize for the confusion. I was trying to figure out why there was such a big difference in the read/write rates of another kernel when compared with franco kernels. I didn't get a response though, so I just left it alone. I don't know enough about IO schedulers to figure it out myself. :p

Maguro | SlimBean 4.2.2 | AK Cylon 731
[Samsung Galaxy Nexus] pkgnex:
Yeah. I read the links you listed, and I was anticipating the same thing as you. Since my subjective testing wasn't finding any "best" combo, I ran quadrants and antutu each twice for each combo and averaged them (I know, I know... benchmarks ~ angels dancing on the heads of pins). There was a 0.05% difference between 0/0 and 7/7, with 7/7 barely "winning". Each of these combos beat 0/7 or 7/0 on every individual run and by about 10% on an overall average basis, which struck me as significant.

That said, I can't really feel any subjective difference between any combinations of these two settings - the only thing that really stood out "feel-wise" for me in the cfq tunables was that lowering the quantum value made my phone feel more responsive. As it turned out, the benchmarks showed this was an improvement (lowering quantum from 64 to 8), as was setting the back_seek parameter to 1TB (instead of 0 or the other number) as you stated subjectively felt better to you.

Anyway, to make a long story short, I have no problem with slice_idle=0 and group_idle=7 since that's what the established theory says it "should" be. Just wanted to share my results, unusual as they may be.
[Samsung Galaxy Nexus] arhung:
Re: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

I am sorry, I thing I was missing something, how can I set the script to set on boot?
[Samsung Galaxy Nexus] galakanokis:
Quick question about your script. I assume you can just set it as is regardless of what scheduler you er on? I assume the settings for an unused scheduler does nothing. I only have settings for one scheduler in my script, row, and this looks interesting especially for testing.
[Samsung Galaxy Nexus] Edward Stanbury:
sorry i should have said this is not my script lol its from malaroth's signature, and yep correct it sets the settings for all the schedulers and will only use the settings on the one that is active eg row, deadline or cfq. so there is not need to have multiple scripts. and so far those are the most up to date settings that are stable (:

---------- Post added at 03:54 PM ---------- Previous post was at 03:50 PM ----------

copy the script to your phone, remove the .txt file extension with a file explorer and then copy it to the init.d folder in system/etc. if that folder is not there create it and copy the script on there and set the permissions to rwx rx rx
[Samsung Galaxy Nexus] osm0sis:
0.05% being the margin of error, might as well assume it's the same difference. I have no problem going against the established theory when someone brings good data to the table. I think we'll go with 0/0 for now and I'll see how 7/7 feels too. Thanks for all your testing. :)

If you've got a bit of time would you mind trying some other values for back_seek_max? Maybe like 100000, 500000, 1000000, 5000000, 10000000, 50000000, 100000000, 500000000, 1000000000. I'd be curious to see of there's an even sweeter spot that could help us narrow down to. :D

The other things we still need more stats on are values for quantum (2, 4, 8, 16, 32), nr_requests (128, 256, 512, 1024, 2048, 4096), and iostats (1, 0). Much obliged if you or anyone else would be willing to provide some data. :good:
[Samsung Galaxy Nexus] galakanokis:
Thanks man, appreciate the info. Malaroth's settings, good stuff. Haven't popped into this thread in awhile and haven't checked out any updates.
[Samsung Galaxy Nexus] Edward Stanbury:
its okay mate welcome back (:
[Samsung Galaxy Nexus] J-Hop2o6:
@ Os

I compared both stock CFQ values, and your original tweaked CFQ values. Stock was definitely better, especially when updating apps via Play Store. Will test your next updated values and compare. But the stock values are already very nice.
[Samsung Galaxy Nexus] pkgnex:
I'll try to tackle them one by one - subjective first, and benchmark if I can't feel a difference over about half a day of normal use. Glad to help any way I can. I think you can take 32 off the quantum list, but I haven't tried 16 or below 8. 64 and 32 felt laggy and benchmarked poorly, too. Since I've narrowed quantum down a little, I'll start there then go back to back_seek_max...
[Samsung Galaxy Nexus] reysonance:
Isn't the voltage under r366 is hardcoded? I just lowered the voltage for the 1228mhz slot down to 800mV and it doesn't crash, nor freeze.
[Samsung Galaxy Nexus] Edward Stanbury:
thats right i forgot about that >.< idk ive still set my UV settings anyway haha i think you are right though
[Samsung Galaxy Nexus] Khrushy:
Nope. Voltages are definitely changeable. I can easily induce voltage related crashing if I so desire.

Although, like you say, 800mV can't possibly be being applied - that's insane.
[Samsung Galaxy Nexus] reysonance:
That's weird, I just lowered the voltage down to 775mV and it doesn't crash, and it definitely says 775mV on the uV_mV_table.

EDIT: I rebooted and lowered the voltage once again, this time it freezes completely. I have no idea why it doesn't do that the first time I changed it :S

EDIT2: Could be a problem with Trickster, setting it manually via terminal definitely crash it.
[Samsung Galaxy Nexus] osm0sis:
Yeah the ones in the March 7 iosettings are worse than stock with the same general queue tweaks.

So right now we're at

8 / 125 / 250 / 1000000000 / 1 / 93 / 39 / 2 / 7 / 7 / 1,

8 / 125 / 250 / 1000000000 / 1 / 93 / 39 / 2 / 7 / 0 / 1,

8 / 125 / 250 / 1000000000 / 1 / 93 / 39 / 2 / 0 / 7 / 1, or

8 / 125 / 250 / 1000000000 / 1 / 93 / 39 / 2 / 0 / 0 / 1.

But leaning toward the 7/7 or 0/0 thanks to the excellent help of pkgnex. :)
[Samsung Galaxy Nexus] malaroth:
Re: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

OK... benchmarks are benchmarks... they do have a spot in generalizing good and bad performance. But quite frankly I'm going to use the one that the person I'm running their kernel helped develop.

Check out https://play.google.com/store/apps/details?id=com.cgollner.benchmark

Franco's real life friend. And we don't have sio. Simple io is similar in function to noop. I'll post some screens later on my benchmarks, which I run multiple times before changing anything. But that just tells me if my tweaks are better or worse. It doesn't solve the issue.

---------- Post added at 03:58 AM ---------- Previous post was at 03:51 AM ----------

Good work man! :thumbup: I'm taking a sort of hiatus, still tinkering but just trying to get over some real life issues. I'd noticed that had seemed to be the case but wanted to check on 15/15 as well, and I'm not currently running os's numbers (which work pretty damn well) to play the devils advocate and make sure we're not missing something with sync and async expires so I won't post mine till I'm certain

---------- Post added at 04:03 AM ---------- Previous post was at 03:58 AM ----------

Fixed dropbox to echo latest numbers
[Samsung Galaxy Nexus] --__LoRiS__--:
R: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

These settings are for cfq?
[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

Yes and its really between these two for testing

I'm trying the 0/0 variation on my n7 and gnex. Thanks for the input on this thread by everyone its really helpful!
[Samsung Galaxy Nexus] whitedragonz83:
Re: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

I like the 0/0 a lot so far on the nexus. Did some app updates and it felt pretty good. General usage feels good to.
[Samsung Galaxy Nexus] franciscofranco:
Update is up. Kernel has been tested and it works fine with a small boost performance wise due to all the changes that have been introduced.
[Samsung Galaxy Nexus] skdubg:
Hi everone,

i cant find a changlog for this custom kernel.

can you tell me what has been changed to stock kernel or modaco kernel?

thanks
[Samsung Galaxy Nexus] franciscofranco:
A lot has changed, I'm posting the changelog later.
[Samsung Galaxy Nexus] mDroidd:
You got to be kidding me..

You also have a GN?!

Welcome :)

You are beating the rest here also, I bet apple cakes for that(yum yum)

Greets

____________

mDroid - Tapatalk

Phone: LG-P500

ROM: Ciaox' openOptimus

Kernel: franco .35

Theme: HoneySandwich (by me)

Tweaks: Turbocharged and Supercharged!

Wishlist: Galaxy Nexus :)
[Samsung Galaxy Nexus] siedkins:
Hi Franco

After looking around at the roms at the moment I think I'm going to hold out on stock for the moment until CM9 or the roms get a bit more advanced.

I am interested in taking a look at some of the custom kernels. Does your Kernel work with stock ROM? Also I have taken a look at your Nexus S thread and saw a whole load of tweaks/improvements and I'm interested to see what you have ported over to the Galaxy Nexus.

Any chance of taking a look at that change log?
[Samsung Galaxy Nexus] franciscofranco:
You can use it with stock I believe. Just backup your current boot.img and try this one, Im sure it works. Changelog comes later, I promise. Mskip is using this kernel with no issues what so ever. Try and see.
[Samsung Galaxy Nexus] franciscofranco:
Not yet, but Im trying to get one! :)
[Samsung Galaxy Nexus] franciscofranco:
Changelog added.
[Samsung Galaxy Nexus] stickjohnonaah:
Do you think I will have issues flashing this to an LTE device in recovery?
[Samsung Galaxy Nexus] franciscofranco:
I have absolutely no idea. Backup your boot.img and try this one.
[Samsung Galaxy Nexus] stickjohnonaah:
Except if it causes an issue I will have no way to restore my stock boot image?? If it causes boot loop I'm pretty much screwed I would think until an sbf comes available.
[Samsung Galaxy Nexus] franciscofranco:
Well don't do it if you don't have a custom recovery to recover from bootloads of that kind of ****. I don't know if there is a difference between normal Nexus and LTE version's boot.img.
[Samsung Galaxy Nexus] stickjohnonaah:
I have clockwork installed and boot loader unlocked but if it has issues do I just go to bootloader select recovery and restore my backup?
[Samsung Galaxy Nexus] franciscofranco:
As far as I know you can just go to the recovery -> backup -> backup boot.img, then flash mine. If there is an issue you can just boot up to the recovery and restore the boot.img you just backed-up. Thats what I always did for my devices.
[Samsung Galaxy Nexus] stickjohnonaah:
Well I just made a fresh backup, maybe tomorrow when I get to work and have internet access other than my phone I may grow a sack and try this out. I I do I'll post up my results
[Samsung Galaxy Nexus] spences10:
I still can't get this kernel to boot, anyone else have any success?
[Samsung Galaxy Nexus] mskip:
If the modified kernel doesnt work then there is no problem in recovering. Just go into your bootloader and select recovery, then go down to backup/restore, select advanced restore, select your backup folder and select the boot.img. Reboot your phone and everything will be back to normal.

Mark.
[Samsung Galaxy Nexus] spences10:
I have an issue with stock recovery being re-flashed each time I reboot after I applied the OTA Patch

I now have to flash CWM recovery from ROM Manager each time I reboot =/
[Samsung Galaxy Nexus] mike1986.:
Remove recovery-from-boot.p from /system
[Samsung Galaxy Nexus] mskip:
Im assuming you have unlocked the bootloader and rooted.

I just retested the cwm version and it worked fine. Is it going into a bootloop on the animation screen or just not flashing? If you cant get the cwm version to flash I can post the boot.img file that you can try flashing via fastboot flash boot.

More details please :)

Mark.
[Samsung Galaxy Nexus] monkey hung:
I just let setcpu do recommended settings. In the big white font it shows 1400 MHz but for Max it shows 12000000 and min 350
[Samsung Galaxy Nexus] Chirality:
Can I ask you how you were able to enable USB host functionality? (A patch file would be awesome) Sorry I couldn't find it in your source because it's not in a separate commit.
[Samsung Galaxy Nexus] hosmsdos:
Everything is good so far but in OC version booting time has increased a little bit and the boot animation is very slow is that ok?
[Samsung Galaxy Nexus] minooch:
does the phone lag at all?

If it does - your phones doesn't appear to support the overclock
[Samsung Galaxy Nexus] Dmw017:
Yeah what is up with that ? Why do some phones lag with the oC and some don't
[Samsung Galaxy Nexus] inffy:
The CPU chips are always different. some chips maybe able to handle the oc better, other chip just isn't as good quality
[Samsung Galaxy Nexus] aeo087:
Horrible lag with OC

My phone doesn't just lag, it becomes unusable with the OC version... Non-OC version ran well for a while with great performance, now i'm getting horrible artifacts that make the phone unusable.
[Samsung Galaxy Nexus] monkey hung:
The OC version is giving me problems. Artifacts and if I turn off the phone while its charged, it gets stuck on the black screen with the battery icon. So its a no go at the moment :(
[Samsung Galaxy Nexus] mklass:
No issues at all for me using the new OC-UV-GPU Kernel.. Thanks Franco
[Samsung Galaxy Nexus] monkey hung:
Well mine seemed fine too but after some time, all the bad stuff started happening.
[Samsung Galaxy Nexus] mklass:
Are you running the latest Kernel? I flashed it around an hr ago and not had any problems. What kind of issues are you facing?
[Samsung Galaxy Nexus] monkey hung:
Yeah its the latest he just provided. OC to 1.4Ghz and it was great for a while. It just randomly happens after a while. Like 30 minutes or so. Especially after unlocking your phone
[Samsung Galaxy Nexus] The Gingerbread Man:
The stuck at battery screen if you power down with charger in is not cos of this kernal or any rom it is a recovery issue.
[Samsung Galaxy Nexus] The Gingerbread Man:
Everything I said to do can be done on the phone. No need for pc . Just get root explorer from android market on your phone and refer back to my post you quoted for slightly more detailed instructions.
[Samsung Galaxy Nexus] Shetlander:
Flashed the OC kernel this morning and have to say even running it at 1.2ghz I got graphical mayhem when waking the phone up too. Gone back to the none OC version to see if that works any better.
[Samsung Galaxy Nexus] hosmsdos:
I tried the non oc for like 30 min, i unlocked the phone and screen kept scrambling i could not even display a menu it did not hang but i could not see any thing i had to take battery off. Anyone had this issue?
[Samsung Galaxy Nexus] mike1986.:
@franciscofranco

Both GSM and LTE use the same kernel :) I just got my hands on 41D base for LTE and it has the same kernel as GSM version :)
[Samsung Galaxy Nexus] Shetlander:
This is the same behaviour I had with the OC kernel but for me the none oc one seems to be fine so far. I would like to try the none oc version with the GPU at 384mhz to see what happens.
[Samsung Galaxy Nexus] Danny80y:
Well mine was fine until just now and has started with the screen distortion so bad I had to pull the battery. This was with the latest kernel with OC and using setcpu to put it back to 1.2

Danny
[Samsung Galaxy Nexus] coolbho3000:
Indeed, they made it easy this time. The kernel will detect if the board is maguro (GSM) or toro (CDMA/LTE) and adjust.
[Samsung Galaxy Nexus] franciscofranco:
Look at the screenshot. The kernel aint ****ed, otherwise I would have the same drain as you guys.
[Samsung Galaxy Nexus] c00king.c0w:
thx for that screen... that what my battery drain used to look like... may i ask what rom you are running?
[Samsung Galaxy Nexus] Thracks:
I would kill for that battery life. I don't even get that when I flash a fresh ROM and don't install any apps!
[Samsung Galaxy Nexus] Nebucatnetzer:
Check the screen on time. He's barely using his phone and even the wake locks are quite rare.
[Samsung Galaxy Nexus] Manya3084:
Your not using some secret, unreleased kernel with that Wheatley governor are you? ;)

Battery life for me is what I expect, since I got the phone a can't put the bloody thing down.
[Samsung Galaxy Nexus] franciscofranco:
Just checked 1h 30m screen on time. I used my phone more than it shows. Using AOKP 19.

It's #14 true, but it's with conservative.
[Samsung Galaxy Nexus] minooch:
Maybe let them know your radio & (god forbid) your bootloader version - *Might* Help *Might*
[Samsung Galaxy Nexus] lovejoy777:
sorry to be a noob but could i run your kernel on my kindle fire.

as im so impressed with it on my gnex.

also i much prefer the new app icon

thanks for all of your hard work.
[Samsung Galaxy Nexus] Thracks:
No.

10char
[Samsung Galaxy Nexus] AzzaD:
hey franco, really loving this kernel, just wondering if you were aware of the "misprint" on the dialog in the updater app when setting the desired voltage for 350mhz, it says 3500mhz instead:
[Samsung Galaxy Nexus] franciscofranco:
Yes eheh, I already fixed it on my local build =)
[Samsung Galaxy Nexus] AzzaD:
haha alrite sweet, just thought I'd let you know if you hadn't noticed it
[Samsung Galaxy Nexus] darrendm:
Can someone link a kernel prior to 13?

Either my router is playing up or its the new wifi driver messing with me.
[Samsung Galaxy Nexus] franciscofranco:
I think that should be fixed on #14 ;)
[Samsung Galaxy Nexus] Manya3084:
So were aiming at a 100% overlock?! ;-)
[Samsung Galaxy Nexus] shawnn218:
Pardon the ignorance, new to flashing kernels.

Kernels are like roms right? In that i can have a kernel for every rom, unlike a radio?

Do i need to wipe anything when flashing a new kernel?
[Samsung Galaxy Nexus] JcMalta:
NANDBACKUP FIRST !

Then Flash ROM (full wipe if coming from an another ROM "family" or much older version of the same "family" otherwise a cache wipe is probably enough - note a full wipe may still be needed of things start going weird)

Kernel flashes should be done last ... no need to wipe.
[Samsung Galaxy Nexus] samizad:
Make sure you don't flash a kernel intended for ICS 4.0.3 onto a 4.0.2 based ROM.
[Samsung Galaxy Nexus] saywhat4118:
Is this considered good battery life?
[Samsung Galaxy Nexus] Nebucatnetzer:
Sure but split over 20h. Check the guy above me that's more what I call usage ;-).
[Samsung Galaxy Nexus] JBNex:
Re: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

I have a question, how do you set Trinity Contrast values through a init.d script?
[Samsung Galaxy Nexus] reysonance:
It's on the second post of this thread, you need to echo your desired values, for example:

echo -24 > /sys/module/panel_s6e8aa0/parameters/contrast

The above line will set the contrast to -24.
[Samsung Galaxy Nexus] JBNex:
Re: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

Thank you. Forgot to check that :P

Also, do the numbers in front of init.d scripts mean anything?
[Samsung Galaxy Nexus] reysonance:
It determines the order in which the script will be executed.

Example: 05init will be executed before 34init, but not after 04init.
[Samsung Galaxy Nexus] JBNex:
Re: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

3D gaming just got better with Franco Kernel. :cool:
[Samsung Galaxy Nexus] tnap1979:
does the current nightly still have cpu1 shutdown ?

i ask because it has been a while since i used FK, i used to use trinity, and im looking for the best possible battery life from my device,

i read a post about franco kernel having ability to shutdown cpu1 when in sleep mode..

thanks in advance