yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] kingoanklebreakn:
Since JB has been going he enabled fsync by default I believe. You can change it in the app though. I've personally not had any problems though.
[Samsung Galaxy Nexus] blackhand1001:
That makes sense. I had those problems when on jellybean
[Samsung Galaxy Nexus] Antob125:
Fsync is disabled by default

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Dr01_D:
My fsync box is checked by default. I assume its on. I've never had any booting probs with JB.
[Samsung Galaxy Nexus] BankZZ:
I am probably doing something wrong but my settings are no longer sticking (using the latest version of the app) after a reboot.

Also, is r196 the last ICS release? I am seeing reference to 200+. Is that just for JB?
[Samsung Galaxy Nexus] raphenucleus:
r200 is the latest one for ICS; it's a jelly bean kernel made to be compatible with ICS. It's pretty good, but it broke wireless tethering for me so I reverted. You can find it in the GSM thread here.
[Samsung Galaxy Nexus] BankZZ:
What about the settings not sticking?
[Samsung Galaxy Nexus] raphenucleus:
There was an update to the app last night, v5.8.1, is that the one you're on? Occasionally with updates to his app, the settings just don't stick. If you don't have a backup to a version where it works, you just have to wait for franco to fix it in a subsequent app update. He usually fixes it within a couple days. Otherwise, it worth checking out the thread in the GSM section; that's the most active of his threads and the one he checks the most often.
[Samsung Galaxy Nexus] BankZZ:
hasnt worked for the last 3 releases :(
[Samsung Galaxy Nexus] kingoanklebreakn:
You might want to start using SuperSU and update the binaries. That's fixed the problem for a lot of people.
[Samsung Galaxy Nexus] xI mEzMeRiZe Ix:
I've noticed that sometimes I have to completely uninstall the app, reboot, and then install the new version (rather than just updating) to get settings to stick on boot.
[Samsung Galaxy Nexus] epphllps:
#220 released
[Samsung Galaxy Nexus] timbck2:
v220 isn't for ICS, just JB, so this is in the wrong thread.
[Samsung Galaxy Nexus] TEK112:
Isn't this now the JB kernel thread?

Franco said he is not developing for ICS anymore.
[Samsung Galaxy Nexus] I Am Marino:
I honestly think he should make a new thread for the JB kernels to keep confusion away and just provide a link to the ICS kernels.
[Samsung Galaxy Nexus] Dr01_D:
....nuff said
[Samsung Galaxy Nexus] tacosrdelicioso:
Francisco....changelog on the latest?
[Samsung Galaxy Nexus] parkson:
On 220, is the new default Max Screen Off 384 MHz?
[Samsung Galaxy Nexus] timbck2:
There is a new thread for Franco's JB kernels: http://xdaforums.com/showthread.php?t=1367341.
[Samsung Galaxy Nexus] xI mEzMeRiZe Ix:
That's just the maguro thread.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] joshtb86:
does anyone have the file for milestone 3? i have a terrible battery leak and want to revert.

thanks!
[Samsung Galaxy Nexus] raphenucleus:
As it happens, I do. See attached.

I doubt it's the kernel though if you really have bad battery drain (and I hope your battery's not actually leaking, because switching kernels isn't gonna fix that, lol), since the Milestone builds are made to be pretty solid and shouldn't vary that much in terms of battery life from build to build. But if you've run it for 3+ days, checked for CPU throttling, excessive wakelocks, deepsleep, misbehaving apps, etc. and you're still getting bad battery life, then it's definitely worth a shot. It's certainly possible that M4 isn't as great on battery life as M3 for you, but everything else remaining unchanged, one shouldn't be terrible compared to the other.
[Samsung Galaxy Nexus] franciscofranco:
Just updated OP/title to be synced with the topic over the GSM forum.
[Samsung Galaxy Nexus] BankZZ:
Any idea why r200-ICS isn't showing in the app?
[Samsung Galaxy Nexus] kingoanklebreakn:
I think it's because it was experimental.
[Samsung Galaxy Nexus] gfropr:
I lost all my voltage setting when I came back from James Bond to milestone 4. Are these ok?
[Samsung Galaxy Nexus] timbck2:
The kernel is the same for maguro and toro.
[Samsung Galaxy Nexus] raphenucleus:
Yeah, those are fine, but you really don't need to change the voltage settings; smart reflex calculates and sets the optimal voltage settings for you and from my experience and reports from a lot of other people, changing those settings doesn't really do much good and can actually do harm.
[Samsung Galaxy Nexus] Homan13PSU:
So when I switched over to JB I lost my color gamma settings. I can't remember if it was here, or on Rootz but there was a really good recommended set of settings that people were running giving some really good color. Any one have those settings or have any good gamma corrected settings to run with?
[Samsung Galaxy Nexus] upther:
I have my Gamma at 1.4

RGB tweaks:

Red -10

Green 0

Blue 10

Color multipliers:

Red 180

Green 192

Blue 235

Really love how everything looks with those settings.
[Samsung Galaxy Nexus] Doritos Bandito:
Is there any real difference between the 384mhz and the 512mhz gpu?
[Samsung Galaxy Nexus] blackhand1001:
On ics I noticed a difference especially on the notification drawer. On jellybean I didn't notice much. Battery life wise they have both been similar for me. I definitely get better battery on cm9 . Try 512mhz gpu on ics with the conservative governor. That's been the smoothest for me. Stock clock speeds is what I have it on as over locking seemed to make it a little more stuttery. I know it sounds strange but the Conservative governor really has been smoother than interactive, wheatley, and on demand for me. Great battery life as well.

This rom with Franco kernel 512mhz gpu has been my daily driver pretty much since I got the phone. I have made many nandroid backups of this and have tried pretty much every other rom but always come back to this combo.

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

You won't be disappointed, I promise.
[Samsung Galaxy Nexus] Doritos Bandito:
Im on Vicious JB 4.1.1 and used the 384mhz on interactive with over 18hours battery life and almost 3 hours of on screen time.
[Samsung Galaxy Nexus] blackhand1001:
I have gotten 5 hours of screen on time with this combo. Always get above 4.
[Samsung Galaxy Nexus] Doritos Bandito:
Even on JB?
[Samsung Galaxy Nexus] I Am Marino:
Extended battery?

I've only managed to get 4 hours screen on time once ever with the 2100mAh battery. Let alone 5.

And that's on ICS.
[Samsung Galaxy Nexus] blackhand1001:
Cm9. Not jellybean.
[Samsung Galaxy Nexus] Doritos Bandito:
OK something I really should of asked to begin with. What does the 384mhz and 512mhz do exactly? Is it the minimum the CPU runs at or is it something else entirely?
[Samsung Galaxy Nexus] TEK112:
It is the speed (frequency or clock speed) of the GPU. Faster clock speed (within reason) usually means higher performance at the cost of battery. I have noticed better fluidity (scrolling, transition animations, etc...) with 512 and negligible battery difference. However, some phones cannot run it. They will get weird artifacting or it may not boot. Download both to your phone and try them both. You will know what feels right.
[Samsung Galaxy Nexus] Dr01_D:
Phone won't boot cm10 kang using r220 kernel. Haven't tried r217 yet.

Edit...update, r217 won't boot either
[Samsung Galaxy Nexus] cj1896:
Checking in to say that the latest update fixed all my settings not persisting through reboots. Many thanks.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] tacosrdelicioso:
So...I read the CL for 220. Laughed at the 1.9 thing....I can run it just fine...also ran that 2ghz slot in one of ur early jb kernels....was surprised but it seemed fine. Didn't leave it on 2 for long though...didn't wanna push my luck
[Samsung Galaxy Nexus] Dr01_D:
Thank you Mr Franco I'm gonna flash it on my CM10 kang now

Edit.. no dice. A big bowl of booty loops for me. :(
[Samsung Galaxy Nexus] djh816:
Just a second confirmation that it bootloops on cm10 skank at least.
[Samsung Galaxy Nexus] jprakes:
Just updated the kernel update app, and it is force closing on me.
[Samsung Galaxy Nexus] tcapote:
No issue with the update on my gnex LTE with CM9 0716 and imoseyon lean kernel
[Samsung Galaxy Nexus] jjhiza:
I got blown into boot loops when I tried to reapply my under volt settings on the 220 kernel, but once I updated to #221, everything is fine again. Just took me a minute or two of tinkering to figure out what was going on. Loving the kernels so far...I just wish I could get my values to persist after a reboot.

Galaxy Nexus - Slim Bean a4
[Samsung Galaxy Nexus] jbdan:
221 with XenonHD is the smoothest my GN has ever been since the phone launched and that is saying something. Great work franco really dig it
[Samsung Galaxy Nexus] jamor414:
Good to hear. I'm on Vicious Jelly and I want to try out a Franco Kernel on this...
[Samsung Galaxy Nexus] mikespe:
I posted this in the other thread by mistake...

Just flashed 221 and got my first reboot ever on a Franco kernel...had to do a battery pull & then reflashed 220...then perfect reboot. I did not make any changes in CPU or voltage...never had a chance since it was the reboot after flashing 221 where the problem occurred. Anyone else having this?

Sent by an Android Guy using an iPad...
[Samsung Galaxy Nexus] stick1300:
So, is there a way to disable Trinity Contrast? I'm not sure that I prefer it.
[Samsung Galaxy Nexus] Antob125:
I believe 24 is the default.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] stick1300:
I'm assuming you mean -24, right? I thought I'd read that somewhere, but it feels like it looks different than before. Maybe it's just my brain trying to trick me
[Samsung Galaxy Nexus] Antob125:
Yes -24. Sorry

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] kynolin:
So are you saying 221 fixed loops with CM10? I'm having no luck with today's nightly Kang.
[Samsung Galaxy Nexus] raphenucleus:
You can do it using the franco app; under color control, go to Trinity's Contrast Interface and set the value to 0. Otherwise, if you're using a ROM that supports init.d, you can use a script I wrote; see my post here.
[Samsung Galaxy Nexus] Antob125:
-24 is default not 0 go up a few posts

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] raphenucleus:
Default as in what the franco kernel normally boots at, or default as in what the stock kernel normally boots at? It might be different for JB, but the stock default for ICS on r196 and r200 was 0, at least when I was using it several weeks ago.
[Samsung Galaxy Nexus] stick1300:
I could easily be wrong (because I'm dumb), but 0 does appear to be the same as before I had Trinity, whereas -24 seems different.
[Samsung Galaxy Nexus] dmeadows013:
Franco will you ever add a zip for your latest kernel that just includes the zImage and uses the users current ramdisk? Easy workaround if you know what you are doing, but I am aware that some people have tried to use this on CM10 kangs with a boot fail because of the CM custom ramdisk. Thanks :D
[Samsung Galaxy Nexus] jbdan:
0 is rom default in trinity contrast settings. I do remember it booting after a flash once at -24 though. Can't remember which version though. 1.0 is default for gamma thingy setting
[Samsung Galaxy Nexus] raphenucleus:
0 is the ROM default for trinity contrast for kernel version r207 and up; for all the kernels before r207, which includes all the ICS kernels, the default value is -24. The option to change the value using the app was added in version 5.5, which means that if you are using this app version or later, whatever you set the trinity contrast value at will be set at boot, overriding the kernel default.
[Samsung Galaxy Nexus] kynolin:
Any directions on how to do this? I'm stuck in the field with the Army and really, really need more than a 500mah charge speed. I'm killing my phone on the charger, because I physically don't have any AC charging.
[Samsung Galaxy Nexus] jjhiza:
Not sure about CM10... I haven't used it yet, since there's no official build out (only kangs as far as I know). Yesterday's app update claims to have fixed the CM10 problems though.

Galaxy Nexus - Slim Bean a4
[Samsung Galaxy Nexus] Dr01_D:
223 working on cm10 kang thanks Franco!
[Samsung Galaxy Nexus] blckngldhwk:
223 booted on Paranoid which is CM10 based. All previous versions caused boot loops. Thanks Franco!
[Samsung Galaxy Nexus] phydo:
You can test a zimage with fast boot.

Do fastboot boot zimage. It won't flash but it'll boot it. If it works then next time you can fastboot flash boot zimage
[Samsung Galaxy Nexus] macdroid14:
I'm just wondering why on the jb version using interactive, it usually only maxes at 1.2ghz and only sometimes goes higher than that. Is ondemand better?
[Samsung Galaxy Nexus] HTCluva:
I like I interactive better than on demand.but honestly I don't see a reason to go past 1.2ghz on jellybean
[Samsung Galaxy Nexus] Neo3D:
Which kernel is better for ICS roms?
[Samsung Galaxy Nexus] EDNYLaw:
R196 is the last stable ICS release. R200 has some JB source merged in but is not considered stable by Franco's standards. M4 is several releases behind R196&200. You will NOT be able to use a strictly JB kernel (r201 and above) on ICS.

Sent from my Galaxy Nexus using Xparent Blue Tapatalk 2
[Samsung Galaxy Nexus] blackhand1001:
Can you release 196 again without trinity contrast set to -24. Makes dark greys get tinted green really badly no matter how much you mess with the gamma. Setting it at zero or above fixes it.

The ideal default colors would be

Multiplier

200, 200, 200

Gamma

-4, 0, 5

Trinity contrast

+3

Omap gamma:

1.2

Best color settings. I have then set but every boot it goes back to trinity -24 and omap gamma resets to 1.0
[Samsung Galaxy Nexus] Antob125:
Get the app so you can change values of colors.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] blackhand1001:
I have the app. They never stick on boot like they should. Sometimes the color gamma settings stick but the trinity contrast never sticks.
[Samsung Galaxy Nexus] TEK112:
Does the ROM you have use superuser or supersu?

I seem to recall superuser having issues.
[Samsung Galaxy Nexus] blackhand1001:
Yes. Cm9. It grants it permissions on boot.

The issue is the default setting on the trinity contrast is set really off on the last ics build. It was changed in that specific build. Older builds had it set to zero. Its annoying that the last build available has it set so poorly. Also the settings I set in the app and in the config files on the system partition don't get restored.
[Samsung Galaxy Nexus] TEK112:
Reread what I wrote.
[Samsung Galaxy Nexus] Antob125:
What he means is check you apps, do you have superuser or supersu installed. People were have trouble with stuff sticking after reboot when they were using superuser.

So if u do have superuser, just install supersu, update binary and remover superuser

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] blackhand1001:
Yup fixed the issue thanks.
[Samsung Galaxy Nexus] jjhiza:
Just wanted to throw this out there, to see if anyone else is experiencing this issue. I just flashed the 223 384GPU kernel for Toro, and got blown into 5 minutes of bootloops. I think the reason for this may have been having ROM Toolbox Property installed alongside the Franco app, and having each one setting different types of kernel tweaks on boot. Is this a known issue, or has anyone else run across this particular problem? I uninstalled Toolbox, and the bootloops stopped immediately, so I'm assuming there was some kind of conflict. I'm going to download it again, set my values up, and see what happens, in an attempt to replicate the issue.

Update: Strangely enough, I can't replicate the bootloops, even with Toolbox setting CPU voltages, systctl, and scheduler parameters on boot. I'm guessing this may have been an isolated incident, as a result of flashing the new kernel (it's never happened before though). Oh well... All is right with the world again, and my values persist through a reboot, so I'm happy. Hopefully, my troubleshooting can help someone else if they run across a similar issue. As always Francisco, excellent work, and thank you for making kernels that rock!

Galaxy Nexus - Slim Bean a4
[Samsung Galaxy Nexus] raphenucleus:
I posted Franco M3 a little while back; see here. It appears that the links remain for all the nightlies, but the links for the milestones get replaced every time he posts a new milestone.
[Samsung Galaxy Nexus] juanzr1:
What values do you guys recommend for the colors to look like the galaxy s3 display. I have it set to default at the moment
[Samsung Galaxy Nexus] juanzr1:
Messed with the settings for couple of hours and I was comparing it to my nexus 7 , I'm using

182,190,200

0,0,0

+10trinity contrast

1.0 omap Gamma if anyone gives it a try let me know what you think

Its the closest I can get to the nexus 7 colors
[Samsung Galaxy Nexus] jbdan:
I use multi's R210 G190 B205 and gammas all at 0. CAB checked and trinity contrast at 0 and 1.2 OMAP4 gamma.

Franco 225 is killer thanks!
[Samsung Galaxy Nexus] EvoRocker:
Is NFC working for everyone using this JB Franco Kernel? Currently on 220
[Samsung Galaxy Nexus] yami951:
Absolutely sick. At first I thought the whites were tinted but then I realized that it is just super bright. Thanks man
[Samsung Galaxy Nexus] Antob125:
No prob! Enjoy! I love it!

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Hungry Man:
Damn, wish that updater tool were free.

Either way the kernel's great.

I just flashed the latest one for JB but I don't see a 192mhz slot.

Also, will it disable 1 core on its own?
[Samsung Galaxy Nexus] StormCell:
Sorry, I but I gotta take exception to the aforementioned statement. This guy works his a$$ off to perfect his little slice of Android, which benefits us in immeasurable ways. To not want to spend a few dollars on this hard work is.... Well... Disappointing.

Do you work for free?
[Samsung Galaxy Nexus] Hungry Man:
Did I say "He should release it for free" or did I say that I wish it were free?

There's a big difference.

I think I must have used the wrong link for the JB kernel. Or is there no milestone 4 for it?
[Samsung Galaxy Nexus] kingoanklebreakn:
All the milestones so far are for ICS.
[Samsung Galaxy Nexus] Hungry Man:
Thanks.
[Samsung Galaxy Nexus] yami951:
Buy it man, its totally worth it.
[Samsung Galaxy Nexus] larkhillv:
I flash r225 yesterday and undervolted, I was getting great battery all day but when I was going to bed, my phone rebooted twice within 5 minutes.... I am went back to air and lean kernel, but neither is showing nearly as good battery life. Anyone else having boot issues on 225 or recent builds?
[Samsung Galaxy Nexus] Hungry Man:
I'd love to buy it if only to support the dev. No can do unfortunately.
[Samsung Galaxy Nexus] TEK112:
You can't support the dev?
[Samsung Galaxy Nexus] BeardedB:
I forgot what the higher GPU on the kernels meant!

Simba was moving too slow, so I told him to Mufasa.
[Samsung Galaxy Nexus] edgie168:
The kernel is already undervolted as default...
[Samsung Galaxy Nexus] aksolanki:
Hi, I've just switched over from a LG O2X to the Galaxy NEXUS, so far I really love the handset and Jelly Bean. The only slight annoyance is the color tint of the screen.

I have read that in order to adjust the colors I need to use a different kernel, not a problem. But I switched to the NEXUS for stability and having every feature working. But reading through this thread, I have read stories of reboots, and certain features that either don't work, or work intermittently.

I am happy apart from the color annoyance. I have no wish to get better battery life, or higher Quadrant scores. So, finally to my questions. Would a milestone build give me what I want? Or should I flash a nightly build? Or should I just stick with what I have?

What do you folks recommend? Many thanks. Anil
[Samsung Galaxy Nexus] Hungry Man:
What I'm saying is that I wish I could buy the app and support the developer. I can not buy the app so I can not support the developer.

See?
[Samsung Galaxy Nexus] jcmm11:
There are no jellybean milestones yet. All the milestones are for ICS. Flash the latest nightly, you should be fine. Once the next milestone is released you can jump on that, or you may find you like staying on the nightly express and keeping up with the latest one.
[Samsung Galaxy Nexus] TEK112:
Not really. I don't understand how anyone with a $700 phone and $100/ month cellular bill can't afford $3 to support a developer.

Well, maybe I could, but then to turn around and ask for help in his thread and expect support and at the same time say you can't buy his app just seems ungrateful.

Maybe I'm just too old fashioned.
[Samsung Galaxy Nexus] aksolanki:
Hi jcmm11, thanks for the info. I've flashed franco.Kernel-r225-384GPU ad bought the app from the Play store. I used some settings from a post on this thread. Immediately I saw an improvement. Perhaps I could tweak it to make it better. But being a graphic designer I've had my fill of calibrating monitors.

I am 100% happy with my Galaxy NEXUS now. Thanks. Anil

---------- Post added 30th July 2012 at 12:07 AM ---------- Previous post was 29th July 2012 at 11:52 PM ----------

Hi TEK112, $700!? Is that the going price on your side of the planet? WOW. And $100 a month for a cellular contract? Double WOW. I bought my Galaxy NEXUS for €300 last Thursday. Brand new with a 24 month warranty.

I pay €4.50 every 30 days for 1GB of data. I use WhatsApp for most of my texting needs. And phone calls are fairly cheap, but rarely used by me.

Either way, $3.00 is out of this users budget. Perhaps the phone was a gift or a freebie. Regardless of how they acquired the phone, I don't see what is old-fashioned about being unable to understand another persons financial situation. That just seems plain old judgmental to me.

Each to their own. Have fun. Anil
[Samsung Galaxy Nexus] Hungry Man:
Well let me explain my finances to some dude on the internet.

Oh wait, that's idiotic lol

p.s. it was 40 dollars down and 30/month
[Samsung Galaxy Nexus] yami951:
No need to explain your financial situation to anyone man. I am a full time student and so I've definitely had my share of penny pinching months, especially when I was between jobs. Everyone has their struggles, but when the time comes when you have an extra 3 bucks, go buy it. Franco is always trying to update it and his kernels.
[Samsung Galaxy Nexus] TEK112:
You don't have, just don't expect support.
[Samsung Galaxy Nexus] ghilliek9:
You can't afford $3.00 for the APP?? Stop using the Kernel you *****! I think everybody here has purchased the app...I've even donated $20.00...not it's not much, but guess what, he has made my phone a million times better by putting countless hours into this work. The first donation won't be the last from me that's for sure! I'm not saying you need to start donating a lot of money, do what you can/want, but shut your mouth about $3.00 you vagtastic vagina!

You disgust me...I'm going to donate $3.00 in your name right now! I'll even throw in a tip....pathetic!
[Samsung Galaxy Nexus] TheGratefulDead:
Stfu the dude can't afford it get over it good for you you gave 20 bucks I'm sure the dev doesn't except anyone to give him money. The dev isn't *****ing so why r u?

Sent from my GNex-Slim Bean 1.0
[Samsung Galaxy Nexus] ghilliek9:
Same reason that you are...stop defending your son and start donating you mooching freeloader or do I need to donate in your name as well??

Anyway, can we get back on track here?
[Samsung Galaxy Nexus] TheGratefulDead:
Haha I bought the stupid app I ain't broke just sick of you douche bags running your mouth cuz some kid don't have money to buy an app or give it to someone who does this for fun. Where foes it say u need to give money to receive support get your head out you ass. And yea this kernel is good

Sent from my GNex-Slim Bean 1.0