yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] prembox:
Answers:

1. Yes

2. No, you don't need.

3. No it won't.

4. Majority of the users reported >3.5 hrs screen time on both 384mhz and 512mhz.....for moderate users ..like me it gives >4 hrs screen time

Suggestion: Buy the app and support Franco for bringing this awesome kernel to us.....as I'm hearing ...the latest kernel R240 could be as smooth as your *****'s butt!! ;)
[Samsung Galaxy Nexus] jellymelly:
4hrs is amazing screen time I can only dream of. Are you using stock battery?

Also when you said "384mhz and 512mhz" do you refer to underclocking the CPU to these speeds? Sorry I'm new to this
[Samsung Galaxy Nexus] ac3theone:
Which one do I flash? I'm on jb 4.1.1 stock. Do I flash milestone 4 or r240-jb?
[Samsung Galaxy Nexus] dropback:
384 or 512 is the speed of the gpu. Can´t be changed with the app.

You can only change the cpu speed...

Milestone 4->ICS

r240->JB
[Samsung Galaxy Nexus] prembox:
Do not get into OC/UC and Under Volting etc when you do not know what its all about.....Yes, I'm on stock battery and as I said I'm a moderate user. Flash either the 384 or 512mhz version of Kernel and stay as is until you read a great of this thread and understand what customization of these aspects (OC/UC etc) are about...
[Samsung Galaxy Nexus] The Gingerbread Man:
I just find it best to leave smart reflex on my self, it works absolutely fine. Its good because it auto under volts for you.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] leets4uc3:
Agreed.
[Samsung Galaxy Nexus] vialpado:
I flashed r240 and Android Upgrade is during a life..
[Samsung Galaxy Nexus] creeve4:
+1 this would be great
[Samsung Galaxy Nexus] Tarun95:
Go to recovery and wipe cache and dalvik cache
[Samsung Galaxy Nexus] vialpado:
Thanks but i solved removing the battery.. buttery level has fallen from 50% to 19% -.-
[Samsung Galaxy Nexus] jellymelly:
so I just flashed r240 nightly on my 4.1.1 JB from within the franco updater app

Do i need to do anything else? Will I see better battery life immediately?

Should I undervolt my CPU? I want maximum battery life but not slow down my phone too much
[Samsung Galaxy Nexus] Pr0fess0rX:
Since last three versions for JB when I flash the kernel and check in About in setting, I found out the Kernel version was written: Unavailable! I'm using CM10 nightly builds. In any other kernel the version is written correct.

View attachment 1256559
[Samsung Galaxy Nexus] krneki10:
Is it worth turning on high performance sound? Are there any noticeable differences?

How about other tweaks, such as color control, etc., do you use them?
[Samsung Galaxy Nexus] Tarun95:
High performance sound is not needed. Our nexus produces amazing sound. Color control just reduce the green color multiplier you'll notice a lot of difference.

Try these values

Red 200

Green 170

Blue 200

Gamma

Red 2

Green 2

Blue 2
[Samsung Galaxy Nexus] The Gingerbread Man:
Its a good option, I find it helps stop music distorting if you like listening to it loudly and the quality is better but makes it quieter. Have a try and see what you like. The volume increase mod is good, I keep mind set to +3 all the time and it really boosts bass.

As for colours I use 135, 135, 205, 0,0,0 with trinity at 0 and everything looks nice and natural with good whites.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] GeekMcLeod:
This has been known for quite a while now. It's no big deal, use another app if you need to check the version Such as francos app.
[Samsung Galaxy Nexus] simacai:
Every AMOLED is different, Samsung's masterpiece. It is said that there are 5 or 6 different kind of color.

Your values for me make the my screen look terrible. ;)

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] meanwhile:
As for colours I use 135, 135, 205, 0,0,0 with trinity at 0 and everything looks nice and natural with good whites.

- - - -

I've set trinity - 5, and omap 1.2, then it looks ok
[Samsung Galaxy Nexus] syncopy:
What?! :banghead:

via GNex!
[Samsung Galaxy Nexus] The Gingerbread Man:
I just put Trinity to -5 but changing omap from 1.0 just makes too much contrast and makes ICS / jb greys look too dark / black. I like the natural colours of the theme

Sent from my Galaxy Nexus

---------- Post added at 01:30 PM ---------- Previous post was at 01:29 PM ----------

Its not too bad, but stock audio isn't great I agree.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Tarun95:
Yes its way better compared to other phones I have tried.
[Samsung Galaxy Nexus] CaspaTheGhost:
Mine isn't as smooth as your *****es butt, not the last time I had a grope...

Franco, could you give us any insight as to why this might be?!

Haven't you got the butt smoothing calibration set?

;) :D

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] krneki10:
I tried you values, now my whites have more contrast, they are "more white". It's hard to calibrate it properly though, because I don't have any references. Are there any calibration tools, like THX for home cinema?
[Samsung Galaxy Nexus] Kappa Lamda:
I am on Trinity's and i want to flash franco's! For the features can I use the TKT? Or do I need franco's app for controling the features?
[Samsung Galaxy Nexus] m.alkhalel:
For the whitest white i use these setting:

Red: 200

Green: 200

Blue: 266

Gamma :

R: -6

G: 0

B: 8

Trinity: - 15

OMAP: 1.2
[Samsung Galaxy Nexus] Tarun95:
No idea I just reduced green value and it reduced my yellow tint and for gamma I used display tester
[Samsung Galaxy Nexus] mikeandjaimie:
Hey franco, I just got up this morning to a bootloop. I had to do a battery pull to get it off a the boot animation. 240 with 384/1.8 OD @512Mhz GPU. Sorry no more info as I was asleep when it happened though I was plugged in charging overnight.. If it happens again I'll post last_kmesg
[Samsung Galaxy Nexus] franciscofranco:
Yes if it happens next time give me logs. But I'm pretty sure that high frequency caused the soft reboot.
[Samsung Galaxy Nexus] intrepidd:
Just to let you know, i flashed r240 over trinity via franco app and it was stuck at boot.

I tried to reflash Trinity but i had a bootloop.

I'll try to reflash an older franco kernel and if it doesn't work i guess i'm good for a full wipe / reflash rom :(

Edit :

reflashed and older version & reboot -> Success

Downloaded .zip via the app, rebooted into cwm and flashed r240 -> Success

I guess it was just a problem w/ the app :)
[Samsung Galaxy Nexus] mikeandjaimie:
Wipe caches first before you try a full wipe
[Samsung Galaxy Nexus] intrepidd:
I did wipe cache & dalvik.

I fixed my problem anyway (look at my post), thanks for your help !
[Samsung Galaxy Nexus] djjonastybe:
Franco I have a question. I am making a kernel myself. And I need to know what I need to do to have overclocking in my kernel.

This is your first commit mentioning overclocking:

https://github.com/franciscofranco/Tuna_JB_pre1/commit/137a7e02173c768d7bff124c93c78f6c89ee079c

Is this really all I need to do ?

Here is the commit by Ezekeel:

https://github.com/Ezekeel/GLaDOS-nexus-prime/commit/2e536ea162b053a112d4d887e8f1b96c64a6c8dd

This is something completely different. But I don't see the 1400/1600/1800/2000mhz frequencies enabled...

I thought I needed this commit as well from him:

https://github.com/Ezekeel/GLaDOS-nexus-prime/commit/c6f96def55704d8628e4eb7307add681cda68a7b

I enabled the module mentioned in the last commit by setting default n to default y.
[Samsung Galaxy Nexus] franciscofranco:
Ezekeels patch is to allow higher frequencies to be stable, otherwise its a no go. My patch is only enabling higher freqs than stock.
[Samsung Galaxy Nexus] Flukester69:
Hey Franco, excellent work there on your last few kernels. I don't really fudge with freq and stuff but since 230 your kernel has been top notch. Just wanted to express my thanks!
[Samsung Galaxy Nexus] yahyoh:
imo omap gamma should be 1.2 it's nicer if u watch dark videos ( on 1.0 i get weird colors on the dark scenes idk why but omap gamma @ 1.2 fix it :fingers-crossed: )
[Samsung Galaxy Nexus] osm0sis:
Hah, yes indeed. :laugh: I recommend everyone share and contribute to the following thread's spreadsheet:

Galaxy Nexus Collaborative Optimal Color Settings

The idea in the long run is we eventually figure out the 5-6 'optimal' settings if we get enough data, but for now it's a great way to share what worked for you.

For me anything over 1.0 causes all colors to look oversaturated, so I leave OMAP unset via franco.App (ie. I never touched a setting so they appear blank). This leaves it at the default 1.0 and doesn't cause a screen flicker/glitch during boot. Anyone wanting to get rid of the flicker but still have a custom OMAP value can set it via an init.d script, as the flicker won't occur when it gets set during the Google boot logo, just once the OS is loaded.
[Samsung Galaxy Nexus] RoscoeDpG:
after running 240 since release i have got best performance from phone got 3hrs screen on time 1hr 45 min talk time and up time of 1 day 4 hrs untill i hit 3 % :victory:
[Samsung Galaxy Nexus] Serious_Beans:
R240 is a beast. Running at 1536mhz SR on and 50% brightness and battery is holding solid so far. Great work on this last release. Also bfq does make scrolling smoother, at least for me.
[Samsung Galaxy Nexus] yahyoh:
ya @1.0 color look more natural and little brighter :)

O.o i tested now 2 videos that have dark scenes and there is no wired color @ 1.0 :eek:
[Samsung Galaxy Nexus] mikeandjaimie:
But if the screen was off and phone sleeping (charging overnight doing nothing but syncs) how would the higher clock affect it? I have screen off set to 729 max cause I use slacker (streaming rasio) and I was wrong.. I was running 384/1.6 forgot I turned it back down couple days ago.

Not arguing, just ignorant of kernel internal workings and wanna know heh
[Samsung Galaxy Nexus] osm0sis:
r240 is retarded fast guys. Finally the Settings list doesn't microlag at the Accounts section and the Widgets drawer doesn't microlag as much. Apps seem to generally load faster as well.

Only things I've notced are with the franco App: it won't let me set 230MHz for max screen off, and the disable logger option seems to disappear and reappear randomly after reboot. The latter started once I disabled fsync; thought it had to do with that as it came back after I reenabled and did a reboot, but now it's disappeared once again with fsync still enabled so I don't know. Tried clearing data/cache for franco App but it still happens, and always comes back after another reboot.
[Samsung Galaxy Nexus] The Gingerbread Man:
Blame the video its self but I'm now fairly confident that 135, 135, 205, 0,0,0 -5, 1.0 is the best iv ever had!

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Moz007:
Why 230mhz and not 192mhz step ?
[Samsung Galaxy Nexus] The Gingerbread Man:
I think quite a few people reported that using 192 their phone wouldn't wake up from sleep SoD (sleep of death) and requires battery pull for reboot.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] yahyoh:
that what i think :laugh:

i'm using : 145,160, 205 ,0.0,5 , -5 , 1.0

and i'm really now hate my s2 screen color look like **** there no color calibration inference which is available on Gnex and s1 :cool:
[Samsung Galaxy Nexus] matius44:
Did you change the min cpu to 230 instead of the stock 348??
[Samsung Galaxy Nexus] nikulogical:
Bfq >
[Samsung Galaxy Nexus] osm0sis:
Ah yes.. I should have remembered that. Works!

Though, now I get why people wanted screen off lower like 50 pages back...

I don't want it lower than 384 screen-on to avoid microlags, but 230 screen-off would be nice for battery savings.
[Samsung Galaxy Nexus] dreamhawk:
Currently experiencing a very slow boot.

I went from 232 to 240 with franco-app, i downloaded it and chosed "YES - BRING IT ON"... It usually works fine, but now i've spent 3-4 minutes at the boot-logo.

Pull the battery or what to do ?

Regards

------

Pull the battery did the deed
[Samsung Galaxy Nexus] cyanoviper:
i would rather adb reboot if possible
[Samsung Galaxy Nexus] IAmAN00bie:
Setting a low screen off frequency does not necessarily give you better battery life. http://xdaforums.com/showthread.php?t=1297535
[Samsung Galaxy Nexus] slvrarrow:
Does francos kernel have deep idle?
[Samsung Galaxy Nexus] osm0sis:
Franco's must, since those patches have been around since Oct/11... Good read! Thank you. I'll bump it back to the default 729 and see if I notice any difference!
[Samsung Galaxy Nexus] qsec:
Usually i don't notice better performance with the new versions of kernels, probably most because I'm not playing games and such things that uses much resources from the phone.

But with 240 even I notice the improvements. It is a beast. My phone flies with the stock settings, amazing speed and smoothness.

Big up to Francisco Franco!

Tapatalked.
[Samsung Galaxy Nexus] P3aK:
Just reporting that I got stuck on Android Updating after flashing r240 also. Battery pull and Cache & Dalvik wipe worked :)
[Samsung Galaxy Nexus] rachid59860:
me too :)

Galaxy Nexus using Android 4.1.1 :)
[Samsung Galaxy Nexus] nikeman513:
Sorry if this has been asked, but what is the difference between lean kernel and nightlies on Franco updater apk? Which has higher GPU speeds, has better battery, and do you prefer? Thanks for the advice.
[Samsung Galaxy Nexus] murdah204:
Yea but after rebooting you'll be stuck right back at android updating or stuck in boot loop....
[Samsung Galaxy Nexus] franciscofranco:
I have no idea why some have a problem stuck in the boot process then after a wipe of cache and dalvik it boots. Without logs is hard to figure out.
[Samsung Galaxy Nexus] LNJ:
It's totally random. First time I flashed it booted fine.

Second time I flashed, I needed a battery pull. Third time I flashed, I needed a pull and wipe!
[Samsung Galaxy Nexus] evelxe:
For me it dont boot in anymode and any procedure you suggest, i'm running Android Revolution HD 6.0.1 ( stock ) with Franco #240 ( with apps , flashed from a zip download by app ) FULL Encryption software (using JB setting ), i will do a logcat , but adb don't recognize my device within i insert password, and it dont appear :(, nothing to do :(
[Samsung Galaxy Nexus] murdah204:
I just reverted back to r232 and everything is back to normal, I'll remain on this one until a fix :)
[Samsung Galaxy Nexus] eddie_gordo:
These issues with the boot after flashing 240 are keeping me from trying to flash it, even though lots of people seem to be really enjoying 240.

It would be really nice if someone with these issues could help Franco tracking the problem. :)
[Samsung Galaxy Nexus] franciscofranco:
Its a very strange issue indeed. I will take a look today.

I stealthly uploaded new r240 files today without the changes to opp.c file in hope to fix it. Did anyone try to flash r240 in the last 6 hours?
[Samsung Galaxy Nexus] The Gingerbread Man:
Not yet but next time I reboot and get stuck I'll post a log for you, was kinda hoping someone else would by now. No matter though its cool :)

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] atsavlis:
Many of the JB roms that are out there use init.d scripts.... and lots of them too. Most of the times these scripts end up doing more harm than good. Could possibly be a script affecting booting up.
[Samsung Galaxy Nexus] franciscofranco:
I doubt it, my ramdisk has init.d support for a long time already and this never happened before. Its either my connection that is uploading semi faulty boot.imgs or something I changed in the kernel. I'm checking it out, though its weird as ****.
[Samsung Galaxy Nexus] ledionkoci:
Hey franco.i've just reflashed the new r240. now it works.no boot loop.thank you so much.
[Samsung Galaxy Nexus] mike216:
Long boots on jelly bean is the way it is. Sometimes there some kind of ram disk check going on. I've tried all roms and kernels and they all do this from time to time? Maybe Franco could clear this up. I'm trying to describe what I've read?
[Samsung Galaxy Nexus] ledionkoci:
But i don't feel any significant difference from r232.for me is pretty the same in terms of smoothness and speed.sometimes the people without any real reason are exited about any new kernel version.anyway,thank you again
[Samsung Galaxy Nexus] sway40:
I can already tell 240 is better with battery, I've been having bad battery lately.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Marcb:
my phone just turned off by itself and I had to do a battery pull to turn it back on... now it just stays in the "X" logo and doesn't boot... sorry Franco I don't have any logs, I was using r240, downloaded 1 hour ago...

thanks!
[Samsung Galaxy Nexus] creeve4:
For what its worth, I've been running r240 since it was released and have had no problems. I have found deadline to give somewhat better I/O performance. Would love to have SIO.
[Samsung Galaxy Nexus] murdah204:
Have you tried rebooting just to see if the problem really was resolved?
[Samsung Galaxy Nexus] mike216:
This happens on all roms and kernels on jelly bean. If they wait long enough it'll boot. Sometimes it could be up to 5 minutes or even longer
[Samsung Galaxy Nexus] franciscofranco:
Just pushed r241:

* Attempt to fix the strange and rare lockup on boot for a few users - according to minooch's tests its fixed

* Further tweaked BFQ for better performance on flash memory devices
[Samsung Galaxy Nexus] osm0sis:
Nice. I just had the weird lockup after a day on 240 with no problems.. Happened once my battery hit 0 and I booted it on the charger. Had to pull my battery a couple times after waiting 5 min. Once it finally booted I took a look through the k_lastmsg but didn't see anything out of the ordinary.. 241 is so far so good..
[Samsung Galaxy Nexus] mrm43:
hi, i just flash the r240 kernel(downloaded yesterday) a couple of hours ago on XenonHDv8 Jelly bean Rom and I did get stuck at "upgrading android starting apps" . I had to do a battery pull to restart my phone again. I did a restore on my previous apps using backup pro and after restarting it got stuck again on "upgrading android starting apps". Battery pulled again and it started fine. I don't know why this keeps repeating.

I tried to redownload the r240 kernel just a moment ago and reflash the kernel once more (including my rom), upon reboot and restoring of my apps it does not anymore get stucked on "upgrading android" . I hope that's the last of it.

update: just downloaded r241 kernel a couple of minutes ago and flash it. No stuck at "upgrading android" anymore also. thanks for the update
[Samsung Galaxy Nexus] ledionkoci:
Thank youuuuu,again.you are the man
[Samsung Galaxy Nexus] nopaycheck:
#241 fixed the problem. Thanks!
[Samsung Galaxy Nexus] creeve4:
I/O performance on r241 with BFQ is noticeably better than r240 with BFQ.
[Samsung Galaxy Nexus] LNJ:
Pure cream!
[Samsung Galaxy Nexus] mike216:
Just so you guys know. If you do get stuck in a lock up just hold the power button in to reboot instead of battery pull

---------- Post added at 04:43 AM ---------- Previous post was at 04:40 AM ----------

Hi Franco, and could you make a kernel for U. S. branded galaxy S3?

Sorry guys for getting off topic here!
[Samsung Galaxy Nexus] Wynnded:
Worked for me. I had the reboot hang up but never mentioned it as I almost never reboot my device outside of flashing something...and it seemed that there were plenty of others having the issue as well. Thanks for your continued work and patience with us.
[Samsung Galaxy Nexus] osm0sis:
First thing I tried when I was stuck at the bootanimation with r240.. After waiting for 5 minutes for it to do something (usually boots in 30 seconds), I held in the power button for at least 20 seconds. No change, had to pull. :(
[Samsung Galaxy Nexus] ac3theone:
Just flashed, so far so good
[Samsung Galaxy Nexus] frenchy714:
First off, thank you for your great work Francisco! Just wanted to report that I'm seeing pretty good battery with nightly 240. This is my first charge cycle.

The 2 things that impressed me about this kernel is:

1. I live in an area where I get sh*tty signal ALL THE TIME.

2. I achieved this screen on time with my screen brightness at 75%.

I usually keep it at 25% but I watched a movie and a few episodes of American Dad on Netflix....I wonder how much more screen on time I could have squeezed out if my screen brightness was at 25% the whole time.
[Samsung Galaxy Nexus] Culex316:
My reaction when I first loaded r241: "puta que pariu!" (in a good way)

The battery life on this one is nothing short of amazing this is prime milestone material.
[Samsung Galaxy Nexus] mike216:
This kernel is something beyond amazing and I would pay one hundred and fifty billion dollars or euros to run it side by side on my U.S. galaxy 3:D
[Samsung Galaxy Nexus] Mancubus99:
I'm having the same problem with this kernel for several versions now.

The fast charge doesn't seem to stick even though the box is checked in settings. I find myself checking the charge type, seeing it registered as USB when it should be AC and then toggling the option and reconnecting the cable to get quick charging. Is there any way this can be fixed? FYI I'm running on stock JB.

thanks!

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] mike216:
Get off stock. No unit.d support and that's why your settings don't stick. I suggest a rom like CNA. Everything works perfect
[Samsung Galaxy Nexus] frenchy714:
+1 for CNA. Great ROM!

Sent from my Galaxy Nexus using Xparent SkyBlue Tapatalk 2
[Samsung Galaxy Nexus] mike216:
This 241 is holding up pretty damn good so far on battery as I read and play games. Its definitely standing out above previously tried kernels out there. The other great thing is I knew performance would be beyond great and this is definitely the case!
[Samsung Galaxy Nexus] ac3theone:
Can u post a link to the cna ROM plz
[Samsung Galaxy Nexus] nikeman513:
Which is CNA?
[Samsung Galaxy Nexus] mike216:
http://codenameandroid.com/forum/index.php?/topic/7-codename-android-320/

Do yourself a favor and run it. Please PM me for further info. Sorry don't wanna hijack francos thread

---------- Post added at 07:03 AM ---------- Previous post was at 06:50 AM ----------

I haven't seen this kind of battery life since 4.0.3 builds! Loving it Franco and man do I appreciate it. Won't have to worry about carrying my charger around tomorrow.
[Samsung Galaxy Nexus] bat0nas:
Data signal loss problem :(

Same with r232 (or what was the number) and r240. No fix in r241. So I expect the same behavior.

Sometimes I just can't browse Internet via 3G. Signal bars go grey (normally when data signal is active - they are blue). It just happens accidentally. Nothing helps - just reboot.

Doesn't help: airplane ON/OFF, data ON/OFF, 3G->2G->3G. Nothing. Just reboot of the phone.

Any ideas if this is Kernel related?
[Samsung Galaxy Nexus] monkey hung:
Is there a reason why I get an infinite boot loop on Android Revolution HD 6.0.1. when installing this kernel?
[Samsung Galaxy Nexus] mike216:
Maybe that rom doesn't like the ram disk francos brings? Sorry just a guess

You won't see this on Verizon Nexus's often
[Samsung Galaxy Nexus] :
I'm having an issue right now where if I set under volt I lock up and reboot and didnt have the problem with pre-240. Imma do some tests and see if it maybe its CM nightly and not kernel
[Samsung Galaxy Nexus] LNJ:
SR tends to get reactivated on occasion after reboot even if the disable check mark is ticked. Just toggle it!
[Samsung Galaxy Nexus] :
Well I been running these with SR enabled for a month now with no issues. I'm positive its CM as reverting to 232 doesn't fix the problem. Just wondering what could have changed to cause the problem :P oh well I guess
[Samsung Galaxy Nexus] LNJ:
It's in the Franco Kernel Updater app.
[Samsung Galaxy Nexus] jaycarag:
Just flashed version 241. So far so good. No issues encountered yet. :)
[Samsung Galaxy Nexus] Kappa Lamda:
Can I control franco's kernel features with trinity kernel toolbox?
[Samsung Galaxy Nexus] RevengeFNF:
Just flashed 241 from 240 with Franco App Auto Flash. Everything went fine.

Just a little thing, "Maximum frequency for screen off", changed from 384Mhz to 1228Mhz after the update. I dont know why, but i changed it back to 384.