yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] sophware:
slicker than @#$%

Love the feature and interface for clock, battery, and sofkey selection.

Center justification of the softkeys (esp for 240 or 241 DPI): If you get around to it, take as much time as needed to maintain your level of quality.

Brilliant

i.imgur.com/GQEtO.png
[Samsung Galaxy Nexus] combatmedic870:
My screen looks great at -10 -5 -5. To my eyes atleast. Every screen is going to need a different combination. making green -5 took the green hue out of yellow....for my phone at least. I thought my screen looked fine before...who knew :confused:
[Samsung Galaxy Nexus] coverton341:
So, I went to the market to download the updater and it says not compatible with my phone, which is funny because I'm running GummyNex 0.5.5 with nightly #12 right now. Anyone know what that is about? Sorry if this has been addressed, but it's late and I'm scrolling through the thread on my phone.

Sent via pixie dust, blasted through a Galaxy Nexus
[Samsung Galaxy Nexus] JFMFT:
Just bought your app earlier today Franco. Thanks for your work. My phone loses less than 1%/hour on this kernel in standby. Amazing. I can go all day now without charging unless I'm using my phone a lot. So glad for this setup!
[Samsung Galaxy Nexus] sinik420:
Echo 0 disables
[Samsung Galaxy Nexus] sinik420:
Usually a rom issue, see if you can go online and do it
[Samsung Galaxy Nexus] Wicked4u2c:
What ROM is the best with this Kernel, also what is Franco running?
[Samsung Galaxy Nexus] sway40:
This has been asked before, just read.

~ Sent from my Galaxy Nexus running Cm9~
[Samsung Galaxy Nexus] EyeOfTruth:
Its mainly user preference. I use Gummy I liked the features and it looks to have a dev that has a good background of making Roms. Plus it feels fairly light, and has built in google wallet.
[Samsung Galaxy Nexus] yondercomesthetrain:
I'm using Codename Android with this kernel. Makes my phone crap rainbows. Good stuff.

For those of you who haven't heard of Codename Android, Google it. You may be very happy with what you find.
[Samsung Galaxy Nexus] Znomon:
Battery life:

4g on all day, moderate use (no games or video) over 2 hours of air Droid. Over an hour and a half of screen on. Running gummy nex 0.5.0 and nightly 12 of this kernel. With hotplug enabled. 700 min 1350 Max and conservative governor.

And a short 15 min car charger break...

Over 13 hours on battery. AND I plugged it in at around 25-30% remaining.

Edit: turns out I am running 1350 instead of 1200...
[Samsung Galaxy Nexus] Znomon:
It wouldn't let me edit and post a picture so I'll post my CPU spy here.

"I'll post my CPU spy. (Obviously I didn't reset it when I unplugged this morning but you can still get the picture =P)"
[Samsung Galaxy Nexus] jameslfc5:
Anyone know the optimum settings for color control please?

Also is stock 0,0,0?

Cheers
[Samsung Galaxy Nexus] kichard:
So weird...I swear it comes out bright green. When I took a screenshot this morning it looked perfectly normal! Idk what's going on here haha.
[Samsung Galaxy Nexus] pa.pn2:
how can i change the colors?
[Samsung Galaxy Nexus] jameslfc5:
You need his app I think
[Samsung Galaxy Nexus] zeppelinmad4:
You can do it from terminal. For example, if for some reason you wanted to make it 0/0/0, open a terminal and type "echo 0 0 0" (without the quotes).

---------- Post added at 07:45 AM ---------- Previous post was at 07:39 AM ----------

Thanks. I figured that was it but didn't want to start throwing random numbers in the terminal.
[Samsung Galaxy Nexus] TEK112:
Turn off hot plug.
[Samsung Galaxy Nexus] ghilliek9:
Does anybody know what the true difference is between ondemand and interactive?
[Samsung Galaxy Nexus] supernova_00:
Hot plug actually helps with the battery life...usually around 30 extra minutes.

Btw 158 killed my battery today. Kernel wake every 5 minutes or so. Looks like sync loop causing it. Didn't change anything other than kernel from nightly 156 to 158.
[Samsung Galaxy Nexus] ghilliek9:
105 min of talk time plus little over 2hrs of screen time.
[Samsung Galaxy Nexus] Flip35:
I'm still rocking 156 and I'm getting good battery, I also use hotplug and I'm satisfy with my battery life
[Samsung Galaxy Nexus] tacosrdelicioso:
Rom and specific Franco kernel please
[Samsung Galaxy Nexus] ghilliek9:
Liquidsmooth 1.35 with franco's best kernel EVER 156 384 gpu...I've posted more details and pix of like 4hr screen on in previous pages if you'd like to scroll back. Standard battery...love this kernel...i dont think i'll flash anything else
[Samsung Galaxy Nexus] fix-this!:
both underclocking and undervolting help from my experience.

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

maybe i should go back and flash the 156 kernel then.
[Samsung Galaxy Nexus] ghilliek9:
You have to give it a try
[Samsung Galaxy Nexus] tacosrdelicioso:
Reverted to 156. Uc and UV......aokp build 35...awesome so far
[Samsung Galaxy Nexus] supernova_00:
Tried to revert to older kernels but the download always ends unsuccessfully for some reason even though it looks like all 3.1 MB were downloaded. So I had to revert back to the only one I have, 141. Sorry for wasting about 30 MB of bandwidth.
[Samsung Galaxy Nexus] VinceT3:
I did this and my battery life went back to normal.. I noticed I turn my phone on & off pretty often just to check a message quickly.. wonder if franco could add a configurable delay before turning on the second processor, maybe based on how high the first cpu gets for x seconds.. or how long the screens been on before turning the second cpu on? Would help me greatly in saving battery.
[Samsung Galaxy Nexus] TEK112:
Have you tried disabling hotplug with the newest kernel?
[Samsung Galaxy Nexus] ghilliek9:
+1 I hope thats possible. I used to turn on my screen frequently as well but now just check for my notification light.
[Samsung Galaxy Nexus] supernova_00:
No, I started using generic hotplug around 145 and haven't turned it off since.
[Samsung Galaxy Nexus] Sveke:
Not sure about international users but for us in America, signal strength and whether your on 4g or 3g or wifi essentially makes or breaks battery life.

4g/LTE= forget it, no more than 2.5 hrs screen on

3g= better, 3+ hrs screen on

Wifi = best 4+ hrs screen on.

I've given up on undervolting and just try to run a clean set up and let smart reflex do its job.

Either way great kernel Franco and great app. Cheers

Edit-derp, didn't see I was posting in Verizon section. Disregard
[Samsung Galaxy Nexus] TEK112:
Start there by disabling it for a couple of days. A lot has changed since then and you may find that hotplug hinders performance for some users. I am one of those users.
[Samsung Galaxy Nexus] upther:
Me too. In fact, my phone hates hotplug as that was the only time I ever got the dreaded SOD.
[Samsung Galaxy Nexus] past_pluto:
I've come to realize that using Pandora for 3hrs a day is never giving more than 3hrs screen time with a 3800 trexcell. I guess all the skipping I do is killing me. And constant screen on and screen offs.
[Samsung Galaxy Nexus] cancerouspete:
it seems the franco widget is reporting the wrong cpu temp, by exactly 10C on vzw gnex, peteralfonso 404 4/9. battery monitor, and a few other apps seem to report the correct temp. didnt just happen, last version had same issue, but never got a chance to report it

currently my phone is ~140F but coolish to the touch :)

if there is anything youd like me to test please PM i'd be happy to.
[Samsung Galaxy Nexus] Sveke:
Not a huge deal but my color multipliers wont stick.

Used to until this morning when I updated apex but it worked fine on last apex.

Any ideas anyone?
[Samsung Galaxy Nexus] axne1:
Me either Franco knows

sent from a Android device :)

I'm always on!
[Samsung Galaxy Nexus] b33zy682:
Loving 158 but I'm getting a ton of wakelocks that I've googled and I think (key word is THINK) are kernel related and aren't because my apps are staying awake. But that's why I'm posting here. I'm looking for a solution. Via BBS the wakelocks I have constantly are gps location provider and activity manager launch. Any info on these would be amazing

---------- Post added at 03:33 PM ---------- Previous post was at 02:48 PM ----------

Also audio out 1. And I listen to no music. Thanks again
[Samsung Galaxy Nexus] sway40:
Yeah im pretty sure im getting a ton of kernel wakelocks I wasn't getting on m3. I don't have any rogue apps. Yesterday I managed to squeeze 3hrs screen on time and 20hrs battery, although good yes I used to get 4+hrs screen on time...im greedy. Never changed any settings so it's not that, I have played and tried tweaking but with no better results.

~ Sent from my GNexus on Aokp ~
[Samsung Galaxy Nexus] b33zy682:
Your right. I think I'll go back to m3 wait a week and find results. What ROM you running
[Samsung Galaxy Nexus] laureanop:
I concur with you guys. I'm on liquid and with the same settings 158 has had terrible battery drain. Went back to 157

"the relentless pursuit of the perfect rom "
[Samsung Galaxy Nexus] rjskalet:
Yea in all honesty I think 157 got probably the best battery life since like 12x. 158 hasn't been too bad for me but I noticed a little more drain with less use.
[Samsung Galaxy Nexus] sway40:
Aokp, it's in my sig and tapatalk sig.

~ Sent from my GNexus on Aokp ~
[Samsung Galaxy Nexus] dracon6ai:
Was wondering. Since the 192 and 310 slot use the same voltage with SR (810mv) is their any benefit to use the 192 slot or just leave it at 310 for minimum?

Laziness is nothing more than the habit of resting before one gets tired!
[Samsung Galaxy Nexus] Gahh Its Lee:
Yea there is an equation for battery consumption. The clock speed does come into play even if its the same voltage.
[Samsung Galaxy Nexus] JackpotClavin:
Hey Franco, can you make a few modifications to the init scripts in the ramdisk? One is for security https://android-review.googlesource.com/#/c/35950/

and the other one is to disable the bug reports feature that oftentimes goes off when trying to take a screenshot https://github.com/CyanogenMod/andr...489886c9a1451f7ccedc67e144c500e2#init.tuna.rc (unless you use the bug report features to improve your kernel of course)
[Samsung Galaxy Nexus] ghilliek9:
Have you guys tried 156? I got 36 HOURS off battery with almost 3 HOURS of screen time and almost 1 hours of talk time. Now, I know that almost 3 hrs isn't a whole lot of screen time but those are still good results. I used the phone normally. Most of that was 4g and very little WiFi. No 3g. You can see the small percentage on wifi....I'd say 25 to 30 hrs was 4g. Data was on the whole time...I've texted, and other minor things. Nothing too crazy. I've posted before where I had 4+hrs of screen time and have used the phone on those results a lot more. Games and internet surfing and all. It was like 15hrs off battery. I'm just posting this for those who can't get close to 20hrs off battery even. This is stock battery, too. It works...156 with the 384 gpu and some tweaks...I haven't tried another kernel since 156 came out.
[Samsung Galaxy Nexus] sway40:
I'll go back and try 156/157, I didn't have 156 on long bc franco it's too fast and puts new ones out.

~ Sent from my GNexus on Aokp ~
[Samsung Galaxy Nexus] ghilliek9:
Yeah, he did bust out the 157 too fast but as far as I remember, the 157 had some issues (for most ppl) and then 158 came out. Thus far, 156 is amazing. Even the 512 gpu had great battery life for me
[Samsung Galaxy Nexus] andrew53517:
What were your settings? Governor, min and max?

Galaxy Nexus & ASUS Transformer Rooted!
[Samsung Galaxy Nexus] ghilliek9:
Well, in the past, I've done 192 and the 1036 max with interactive. That's when I got 4hrs of screen on and I think those stats were more impressive to me becuase during those 4hrs I've used it a lot. Gaming and google chrome...I've posted more details in previous posts. I have always had it undervolted and all. These stats are ok, IMO. Only shows long battery life off charger but not a whole lot of screen on. Even though almost 3 hrs and almost 1hr of talk time is still pretty good. Esp for 36hrs off charger. But this time, I have the max at 729. I did this to try it out. Kind of like it. Still very snappy...games run smooth. I have a bunch of other settings ... dark gamma but high on color multipliers and stuff...plus i have the blue infinitium background theme...that gives me all black (for example, in your messaging folder app, background is white in stock but this turns it all black with blue writing and lines so it's still very clear with the gamma and color settings so I can see it easily on AUTO brightness in daylight)

I love it! Finally! lol
[Samsung Galaxy Nexus] rjskalet:
Anyone have issues with the app not setting CPU values at boot?
[Samsung Galaxy Nexus] andrew53517:
Thank you for this! It was very helpful :)

Galaxy Nexus & ASUS Transformer Rooted!
[Samsung Galaxy Nexus] TEK112:
Do you have the ROM controlling the CPU?
[Samsung Galaxy Nexus] rjskalet:
Yep that's the issue thanks.
[Samsung Galaxy Nexus] grzechopl:
hi, i have problem

i installed .zip file by recovery mode "franco.Kernel-milestone3.zip" and my phone doesnt turn on

i have only google logo and nothing more

anybody can help me ?

i dont have more kernels on my phone, so i cant change it back ;/ what can i do ?
[Samsung Galaxy Nexus] ballbusta:
If you could boot into recovery restore a backup
[Samsung Galaxy Nexus] Geezer Squid:
You can also reboot into recovery and just reflash the original rom or any rom that you have on your phone. You can also just reflash the kernel and see if that helps.

Good luck
[Samsung Galaxy Nexus] sirmims:
So what do the power saving modes actually change. From what I've seen so far it changes the governor and CPU freq but what else do they do?
[Samsung Galaxy Nexus] zeke1988:
maybe voltage setting?
[Samsung Galaxy Nexus] kingoanklebreakn:
I think it just changes governor and frequency. Smart reflex handles voltages the same would be my guess. It also changes dual core and single core mode I believe.
[Samsung Galaxy Nexus] snubs:
Yeah, I'd like a more detailed explanation of what each setting does. I don't want to change something manually and have conflicting settings battling each other.
[Samsung Galaxy Nexus] b33zy682:
Ok I'm getting audioout_1 wakelock but not listening to any music or anything with sounds.Iwas told to uncheck touch sounds and screen unlock sounds in settings and I've already done that. Also I gave quick ics browser as a wake lock. Any one else
[Samsung Galaxy Nexus] akademix:
Have to say 156 has been amazing on battery and performance and unless it can get way better, I'm staying. Great job Franco
[Samsung Galaxy Nexus] TEK112:
I thought the audio wakelock was anytime your phone made a sound, ringtone, notification alert, etc... The touch sounds and unlock/lock sounds were the biggest users due to frequency which is why it was suggested that you disable them.
[Samsung Galaxy Nexus] avlfive:
So I've been looking around at the various threads and haven't found a fix but a couple others with the issue.

Anyone having problems with the volume boost sticking? I'm constantly having to go in to the settings and reset it zero and then back to my desired setting.

EDIT: Playing around more seems to show that one of the reasons is caused by removing the headphone jack. It doesn't actually reset my app to the 0 setting, that stays at my desired setting, the music just gets quieter until I select zero and then my setting again.
[Samsung Galaxy Nexus] ghilliek9:
I agree! I've finally been able to hit the 6 hr screen on mark! It's actually 6.5 with almost 19hrs off battery! All on standard battery...love 156!! Nothing too heavy as far as use...little bit of games and decent amount of chrome browsing. Texts...emails...mostly 4G with data on
[Samsung Galaxy Nexus] petecraig612:
I can also confirm that r156 is giving me kick ass battery but where did you get the lower GPU one? I downloaded it from his nightly page and it downloaded the 512GPU kernel.
[Samsung Galaxy Nexus] VinceT3:
Wow.. what do you have your screen set to auto? if so what are your auto settings please? :)

Right now I'm getting roughly 3h screen time.
[Samsung Galaxy Nexus] TEK112:
What happened at the end? It looks like the phone spent the last two or so hours of its life on airplane mode with the screen on.
[Samsung Galaxy Nexus] gaming09:
Ive been having an issue with my earpiece thinking there is a headphone plugged in, but i didnt think it was the kernel, maybe theres an issue with the latest nightly, anyone else experiencing this?

using toggleheadphone2 widget as a workaround for the time being
[Samsung Galaxy Nexus] phydo:
For anyone asking I happen to have the 384 156 kernel zip. I also keep reverting to this:

http://db.tt/W268Ss6T
[Samsung Galaxy Nexus] axne1:
The next kernel is the SAUCE!

sent from a Android device :)

I'm always on!
[Samsung Galaxy Nexus] ghilliek9:
The last several hours were WiFi. I don't think that I have ever used airplane mode on this phone. The screen was mostly on Auto. Sometimes i'll take it down much lower, almost all the way, when I'm at home at night and looking at things.
[Samsung Galaxy Nexus] LothianScykle:
I've been using this kernel with LiquidSmooth 1.35, and am very impressed. It's amazing how much faster and more usable the device is.

Last week, I switched to r158, and used it for a few days with no issues. I then tried undervolting based on a screen cap another user had posted in this thread, and all was well for about a day. Then the phone hot booted, and was fine. A few hours later, the phone hot booted again, so I went into the Franco app to check the voltage settings, and heard a "click", followed by a hot boot that never completed - just the boot animation for a few minutes. After 2 battery pulls, I recovered (via CWR) to a known good save state, and all has been well since.

Has anyone experienced that "Click" sound immediately preceding a hot boot? Is this something I should be concerned about?

~
[Samsung Galaxy Nexus] Gahh Its Lee:
I've experienced it. Also experienced the phone refusing to boot after a hot boot. I think its something about data corrupting because if the lower voltages. I could easily be wrong but I've read that a few times
[Samsung Galaxy Nexus] TEK112:
That is just a speaker pop. The same thing happens for computers when they are shut down or booted. The hot boot while not normal will cause the speaker pop which is normal.

---------- Post added at 12:08 PM ---------- Previous post was at 12:08 PM ----------

It just looked weird seeing the battery start like the Rockies and end like the flat plains of Kansas...lol
[Samsung Galaxy Nexus] ghilliek9:
lol yeah i noticed how long the red state was but the last 10% were over night with no activity...maybe that's why. Either way, 156 is amazing. I'm done with flashing Kernels lol
[Samsung Galaxy Nexus] TEK112:
I went back to 156 as well. It was the only kernel that gave me 3.5hrs of screen on time with my typical use. A month ago I was barely getting 1.5 hrs...lol
[Samsung Galaxy Nexus] ghilliek9:
Its amazing! Few pages back, I've posted some other stats where I got 4hrs screen on time with a lot more use than the 6.5hrs. And the 4 was Auto the whole time. Phone calls too. So it works all the way around. Great kernel! Liquidsmooth 1.35 seems to go well with 156. Kind of want to try AOKP again...but too afraid that 156 won't go well, then I try to go back and for some reason doesn't click together as well as it does now. Too much of a risk. I wish that Franco would come out with some kind of delay timer for the hotplug. I do check for messages often (even though now i just check for the notification light) so having a 10sec or so delay before core 2 kicks in would be nice.
[Samsung Galaxy Nexus] TEK112:
Agreed. I am using PZ from DT which is a AOKP Kang and it is great.
[Samsung Galaxy Nexus] Mayze23:
^^ Total agreement. 156 is working perfectly for me. IMM76K stock.
[Samsung Galaxy Nexus] XTRoRDiNAiRE:
do these kernels work with the sprint version?
[Samsung Galaxy Nexus] andrew53517:
Yeah, check the sprint forum to get them though.

Galaxy Nexus & ASUS Transformer Rooted!
[Samsung Galaxy Nexus] jcarlm:
You can get them from here as well. Either forum will work as long as you are just using a kernel from the Verizon forum.

DO NOT FLASH ROMS FROM THE VERIZON FORUM.
[Samsung Galaxy Nexus] agrifoni:
Is it normal to have a delay on notifications (gmail, gtalk, whatsapp) while in deep sleep?

It seems that, while in deep sleep, data are disconnected, and reactived from time to time (for example every 10 minutes) to check if there are some notifications.

Am I wrong?

Franco Kernel milestone 3 with Aokp release 35 (galaxy nexus GSM)
[Samsung Galaxy Nexus] stick1300:
^ I didn't seem to have the issue on 154, but, after flashing 156 last night, I've been seeing that too today.
[Samsung Galaxy Nexus] TEK112:
Seems like you need to clear both caches in recovery.
[Samsung Galaxy Nexus] nvleafs:
After installing this kernel DoubleTwist does not show any of my music. I've tried clearing data, reinstalling DoubleTwist, reflashing AOKP and the kernel and still nothing. DoubleTwist works fine without the kernel though.
[Samsung Galaxy Nexus] kingoanklebreakn:
Anybody know what the boost option does for the interactive governor?
[Samsung Galaxy Nexus] tacosrdelicioso:
Why is this guy running stock? Is the latest stock amazing in battery or something?
[Samsung Galaxy Nexus] Mayze23:
I have yet to use a custom rom that didn't have a quirky bug I couldn't stand. IMM76K with 156 works perfectly bug free.
[Samsung Galaxy Nexus] LothianScykle:
Thanks. The speaker pop does sound right, but was a bit scary. I thought I had killed my phone for a few minutes.
[Samsung Galaxy Nexus] kennyp987:
I'm using 157 and I'm very happy with it....158 was giving a few hangups where 157 is smooth as butter
[Samsung Galaxy Nexus] theneighbor:
+1 this. Stock is most stable for me. Franco runs great with it. Nothing wrong with stock and I don't need all of the additional customization for no speed increase.
[Samsung Galaxy Nexus] agrifoni:
The problem is that when I wake the phone from deep sleep, the signal bars are grey (full signal but not blue), and they become blue only after 2-3 secs (connection to Google servers)

Is it normal the behavior?
[Samsung Galaxy Nexus] phydo:
R160 doesn't instantly crash on my r156 voltage settings. Woo!

Edit: note that I don't use 1350. So no real tweaking there.
[Samsung Galaxy Nexus] TEK112:
It is for me. I spend a lot of time with each color and I still get push notifications and SMS just fine. Honestly, I stopped paying attention. It was making me paranoid.
[Samsung Galaxy Nexus] gaming09:
mine does on those settings lol
[Samsung Galaxy Nexus] ballbusta:
Anybody else having issues with the updater app not downloading 160?
[Samsung Galaxy Nexus] adlzian:
is this the same as the r999 kernel?
[Samsung Galaxy Nexus] phydo:
Yeah I just realized it does too. I'll have to retweak. My 156 works fine on those
[Samsung Galaxy Nexus] kingoanklebreakn:
Yeah he said 160 was going to be r999 with 0 changes.
[Samsung Galaxy Nexus] phydo:
These are my new low settings on the under volt. I'm not sure if 384 and 1228 can go any lower. Still tweaking.

Furthermore, it doesn't look like the 1228 voltage setting is actually getting applied in the smart reflex window panel
[Samsung Galaxy Nexus] tacosrdelicioso:
I get my 384 down to 270ish...usually keep 1228 at 1150
[Samsung Galaxy Nexus] laureanop:
What ???

"the relentless pursuit of the perfect rom "
[Samsung Galaxy Nexus] JetBomber117:
My phone appears to hate 160. The little blank gap is where my phone rebooted to flash it, and the rest is self explanatory. No, my conditions are not ideal for battery life, but this thing is absolutely tanking with me just playing solitare or whatever. It's dropped 3% with just me typing this out.
[Samsung Galaxy Nexus] TEK112:
Same here, it seems to live at the highest MHz and then sleep, not much else. Back to 156 for me.
[Samsung Galaxy Nexus] axne1:
What's next now? Lol

Sent from my iPad2

using Tapatalk
[Samsung Galaxy Nexus] fix-this!:
I just installed 160 and my signal is horrid, constsantly down to one bar. Didnt have that on 158. Battery is draining pretty fast too.