yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] supernova_00:
Using 135 (don't have time to upgrade right now) I get awesome battery life in sleep mode but when the screen is on I lose 1 percent almost every minute. That would make it about an hour and 40 minutes of screen on time :/ How are you guys getting 2+ hours?

Here is my setup:

4G on (full signal) with all other radios off (GPS, Bluetooth, etc,)

Brightness at about 15% (I've tried higher and lower, higher because for some reason I got better battery life on stock kernel with more brightness)

Sync off for everything

Software ran was facebook, twitter, engadget

I haven't changed any OC/UV values. The only option for those that I've changed was "set at boot". Govenor is "on demand". Turned logger off, enabled fast usb charge, and increased maximum sound to "3"

Thanks for any help!
[Samsung Galaxy Nexus] Adan.Mejia3:
Your problem is 4G. It will drain your battery every time. People that post incredible battery life are usually on wifi and low brightness (no auto). 3G will give you much better battery life than 4G but not as great as wifi. Watch your Facebook app too because I hear that app is terribly written. I prefer to just use the mobile site. Hope this helps!

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] supernova_00:
I figured 4g had something to do with it but I can't deal with the slowness of 3G. I use WIFI when at home and there I get about 1 percent per 2 minutes. Autobrightness is off. I only open facebook once every hour or so and that takes about five minutes of running to catch up so it isn't like I'm running it for hours. Twitter about the same. BTW I've betterbattery stats and nothing is causing kernel wakes or excessive ammounts of processor.

Right now I'm at 70%, at 2hrs 49 minutes since unplug, screen used 49% of battery with 23 minutes of screen on, phone idle 11, standyby 10, no time without signal, facebook, engadget and twitter each used 6%. Engadget usage of CPU is the highest with 11 seconds. Partial waklock the highest is 1 minute 25 seconds for gmail, no kernel wakelocks. So the crappy time isn't due to rouge apps running in the background.
[Samsung Galaxy Nexus] axne1:
Franco I just flashed the 384 version of your nightly. Fast as HELL!!!!!!

4 you people wondering how to test how fast it really is, go to a web page like. nba.com/ or NFL.com they have high flash content and scroll away. Absolutely no lag awesome kernel. Now let's see how she does on battery time. The last nightly I got a hour less on screen time with 384/&512
[Samsung Galaxy Nexus] jtguf87:
Been running the #133 nightly, just updated to the #138. All around, a really great kernel...the battery life is noticeably better than stock, and its been running really smooth.

Great work, Franco...keep it up!
[Samsung Galaxy Nexus] zeke1988:
still lag on chrome beta but smooth and fast on opera mobile.
[Samsung Galaxy Nexus] Gwanatu:
So far so good on 138, this thing is BLAZING!

EDIT: 512 GPU
[Samsung Galaxy Nexus] axne1:
Thanks for the heads up :)
[Samsung Galaxy Nexus] miketoasty:
With CM9 and Franco my phone boots so fast I don't get to see the whole boot animation. #FirstWorldPains

---------- Post added at 11:44 AM ---------- Previous post was at 11:41 AM ----------

Also, Francisco, why did you take out the ability to pick your GPU overclock in the Franco.Kernel app?
[Samsung Galaxy Nexus] aliensquale:
can somebody explain what fast USB boot is?
[Samsung Galaxy Nexus] franciscofranco:
No, the GN is my main development device :)
[Samsung Galaxy Nexus] franciscofranco:
Because my kernel doesnt support gpu clock change on userspace.
[Samsung Galaxy Nexus] miketoasty:
Make's sense, thanks for clearing that up.
[Samsung Galaxy Nexus] hajabooja:
Anyone noticing any signal issues with #139? Didn't think it'd have anything to do with the kernel, but I'm getting really bad signal after flashing it. Maybe something in my area.

Edit: seems to be something in my area cause I'm getting it with #138 as well.
[Samsung Galaxy Nexus] gnexdude:
I'm missing something...what's on 139?
[Samsung Galaxy Nexus] ddgarcia05:
Can I flash build 138 on gummy 1.0.1?
[Samsung Galaxy Nexus] innov8ion:
Read Francisco's post from earlier today.
[Samsung Galaxy Nexus] tu3218:
What is the stock governor for nightlies? I want to start with that an then experiment from there.

Btw, 139 is crazy fasttttt
[Samsung Galaxy Nexus] Neo3D:
sometimes, the nav menu bar disappears, it's not going to full screen mode, the buttons just disappear, anyone else getting this?

not sure if this is a kernel or rom issue?
[Samsung Galaxy Nexus] franciscofranco:
Ondemand is the default.

The kernel has nothing to do with android framework.
[Samsung Galaxy Nexus] Charm8er:
Mine is working fine on 138 with gummy.
[Samsung Galaxy Nexus] vtmike:
Still getting the artifacts using 139 at 512mhz. Working well with 384mhz though.
[Samsung Galaxy Nexus] GinoSylum:
So far so good on 139 (512) with AOKP 32... No artifacts, phone not running hot like it did with 138 and I can send MMS. (i personally could not on the last few nightlys) Too soon to report on battery life but the glitches I have been getting seem to be cleared up.

Thanks for the hard work Franco!
[Samsung Galaxy Nexus] DroidOnRoids:
Franco, you sir are a gentlemen and a scholar. The r139 Kernel is by far the fastest kernel I have ever flashed to my phone. Not to mention my battery is loving it ;)

On top of that, you keep us updated on the kernel and app - I really appreciate that.

Thank you, sir. And I really hope I see you on the the next future Android device I receive.

:)
[Samsung Galaxy Nexus] gnexdude:
Thanks! I totally missed it...
[Samsung Galaxy Nexus] Xerrus:
I love the Franco kernels, bought the app, and have been faithful since I got my gnex. Tried a few others but always came back because of speed and battery life. Since M2 the nightlife started out pretty darn good but as of late (nightly 130+) my phone has ram hotter and had worse battery life than ever. Whatever you were doing on the kernels before, go back to it. The 139 has definitely decreased temp today but I got 1 hour 37 min screen on time by the time battery was at 33%. No good mang. Probably going to go back to M2 for a While or shop around a bit, give my phone a break from being in furnace mode.
[Samsung Galaxy Nexus] cabagekiller:
Newest kernel does not like the widget. All mv show zero for me. Any idea?
[Samsung Galaxy Nexus] DroidOnRoids:
Yeah, it's happening to me as well.
[Samsung Galaxy Nexus] thefivetheory:
The change log for 138 mentioned that it broke the Calibrated Voltages section of the app; I assume the same goes for 139. The widget I think shows the same info as that part of the app.
[Samsung Galaxy Nexus] franciscofranco:
It saddens me that people can't read changelogs.

r140

* SmartReflex1.5 is the default again for temperature and stability purposes - thanks for all the testers in the last experimental builds

* Added Lazy governor from users request
[Samsung Galaxy Nexus] laureanop:
For the record , I had no stability or temp issues with either 138 or 139. 384 mhz on liquid

"the relentless pursuit of the perfect rom"
[Samsung Galaxy Nexus] Jeremiah_1988:
What are your suggested settings for your kernal for best balance of speed and battery life?
[Samsung Galaxy Nexus] franciscofranco:
I don't have suggested settings, I barely have time to test every settings on my own.
[Samsung Galaxy Nexus] Jeremiah_1988:
Lol I understand that, you do crank them out
[Samsung Galaxy Nexus] williamthegoat:
Any chance we'll see sr3 again? 139 was pretty perfect for me.
[Samsung Galaxy Nexus] mike216:
Try conservative governor and I'll post some UV settings if your interested
[Samsung Galaxy Nexus] mike216:
Here is some UV settings you could try
[Samsung Galaxy Nexus] calebv2:
These settings are rock solid for me I have never had a prob.

Fixed for some reason xda app won't let me upload pics
[Samsung Galaxy Nexus] mike216:
I see what you mean about people reading change logs. Come on folks we were doing really good for a while there don't get lazy again!
[Samsung Galaxy Nexus] mike216:
Your 140 is good on battery. 139 was not so good so maybe SR 1.5 is where its at
[Samsung Galaxy Nexus] axne1:
Flashing right away!!!

Kanged out Google phone +

Franco's Magic :)
[Samsung Galaxy Nexus] aliensquale:
just FYI.. in your Franco app... when you do the download to .zip file it does NOT seem to work... no downloads appears to my 'custom saved path' in the franco app...
[Samsung Galaxy Nexus] upther:
I don't have a custom download path set, but I just downloaded the new nightly this morning directly from the app just fine.
[Samsung Galaxy Nexus] miketoasty:
Sometimes I need to hit download more than once to get it to actually download. Just make sure it's there before you go into recovery.
[Samsung Galaxy Nexus] danman7:
I am unable to find anything regarding what characteristics of the Lazy governor are. How does it differ from some of the others?
[Samsung Galaxy Nexus] miketoasty:
Did a search and couldn't find anything either. Would also like to know what it does.

Edit: Did a more in depth search and found this: http://xdaforums.com/showthread.php?t=1276092
[Samsung Galaxy Nexus] danman7:
Ahh, your "search-fu" is strong. :D
[Samsung Galaxy Nexus] aliensquale:
What is a typical (safe) MPU temperature? and how about UNSAFE? my phone feels pretty hot to my ear while talking.. running AOKP build 32 with Franco kernal nightly 140.

all default settings
[Samsung Galaxy Nexus] TEK112:
I flashed over to imoseyon for the time being because of the same heat issues. I am not sure what is causing it, but the phone is warm even during sleep. I had this on 135 - 140.
[Samsung Galaxy Nexus] aliensquale:
what temps are cold, okay, warm and too hot?
[Samsung Galaxy Nexus] TEK112:
I don't look at the numbers, because they don't make sense. There are too many temps and I can't determine which is the culprit (MOU, IVA, Core, Battery). All I know is that MPU (CPU) was at 109° and the phone was too hot to hold against my check. Not scalding hot, but uncomfortable to hold for longer than a second. I noticed it gets even worse when the phone is in a low or no service area.
[Samsung Galaxy Nexus] miketoasty:
That would be the radio getting hot, happens with any LTE phone when in low service areas, or after downloading a lot of data.
[Samsung Galaxy Nexus] TEK112:
Even with LTE disabled?

I run 3G only, because 4G is so sporadic where I am.
[Samsung Galaxy Nexus] mike216:
My phone can cook eggs on it downloading large files or just heavy 4g use. It always has no matter what kernel I run!
[Samsung Galaxy Nexus] TEK112:
But that's just it. My phone is idling in the top pocket of my dress shirt with LTE disabled and the screen off. I wish I knew what the hell it was doing during those times. OS monitor says the phone is idle and the CPUs are running under 3%, CPU spy says it is in deep sleep. :confused:
[Samsung Galaxy Nexus] cdchris12:
I noticed abysmal battery drain that I couldn't get a hold on around nightly 121. I finally figured it out when I didn't get a notification and made it through the night for the first time in a long while. Anyway, clear the settings on your lightflow app and clear your cache in recovery. Worked for me, worth a try for you.
[Samsung Galaxy Nexus] mike216:
does it feel hot by hand and what are you looking at to see temp readings? If your only looking at Franco's app I would say to download system panel and see what that says. I got two far different readings myself

Something is stuck on. I wonder if you could use that system panel app to see what's running and maybe clear out some data and go back in recovery and wipe again?

Hey tech make sure your inui.d folder is clean and you don't have any other kernels modules
[Samsung Galaxy Nexus] andrew53517:
What do you think the chances are of pushing your kernel past 1.35 ghz in future releases? :)

Galaxy Nexus & ASUS Transformer Rooted!
[Samsung Galaxy Nexus] axne1:
I know it was tried before (1.5)but was a fail I think?

Kanged out Google phone +

Franco's Magic :)
[Samsung Galaxy Nexus] KWKSLVR:
The latest nightly is randomly locking a GPS fix and holding it for several minutes... no apps running, no system changes. Just #140 and the latest CM9 Nightly
[Samsung Galaxy Nexus] sirmims:
Just curious is anyone still running 700 min? How's the battery life and are there any overheating issues with the new experimentals?
[Samsung Galaxy Nexus] masri1987:
Me too and right by the camera it smells like something is cooking lol
[Samsung Galaxy Nexus] Gahh Its Lee:
I'd worry about that... If my phone didn't do it too that is
[Samsung Galaxy Nexus] mike216:
Yea near the top is always on fire

If I download a large movie like 1.5 gb I can cook on top of the screen. Other then that its fine but 4g over a long period gets hot
[Samsung Galaxy Nexus] Geezer Squid:
I routinely run 700 min regardless of which kernel I'm using. I've had no overheating issues and battery life is great unless you happen to actually use your phone (just kidding). I actually see little or no difference in battery life, but then again I do not obsess about it either. YMMV
[Samsung Galaxy Nexus] laureanop:
Jesus ! You're cranking them out fast. 140 was great with lazy governor.

Go Barca tomorrow ! CR7 sucks ; Messi rules all !

"the relentless pursuit of the perfect rom"
[Samsung Galaxy Nexus] tu3218:
M2 consistently proves best battery life out of all kernels for my phone. I'm trying to take this a little further and undervolt. I've heard taking everything down "25" from there values as is. So for 1228mhz, take the 1380 to 1355. Is that safe to do for all slots?
[Samsung Galaxy Nexus] kingoanklebreakn:
That should be just fine. If smart reflex is enabled then you probably aren't actually UVing anyway as it's probably doing way more than 25.
[Samsung Galaxy Nexus] phydo:
Noob question. What exactly is the sync framework? Like contact / mail sync etc?
[Samsung Galaxy Nexus] Adan.Mejia3:
Hey Francisco,

Does selecting the auto flash feature in your app wipe cache and dalvik (davlik?)

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] shakuyi:
cant wait to see a sprint version of this i heard really good things about this kernel and im anxious to try it
[Samsung Galaxy Nexus] DroidOnRoids:
It doesn't wipe caches. And it wouldn't matter anyway since the kernel has nothing to do with the cache. Just flash it without any wipes.
[Samsung Galaxy Nexus] tu3218:
Ahh I see. Yeah it seems I have it enabled since its suppose to be checked to disable. I guess I'll leave it at that then, since that's more efficient. Are they any other measures I can take to try and achieve best battery life? Just bought the app and there is a lot of settings in there.
[Samsung Galaxy Nexus] gnexdude:
Thank you!!! Franco you're a beast!

141 here we go!
[Samsung Galaxy Nexus] axne1:
I'm hoping this one is money $$. The last few has been :/

Kanged out Google phone +

Franco's Magic :)
[Samsung Galaxy Nexus] sirmims:
What governor do you run?
[Samsung Galaxy Nexus] axne1:
Must say it's fast 3739 on quadrant!!

Kanged out Google phone +

Franco's Magic :)
[Samsung Galaxy Nexus] patmw123:
Excuse me for sounding stupid, but could you explain what smart reflex is and how it is enabled and disabled?
[Samsung Galaxy Nexus] mike216:
SR calibrates your mpu (CPU) voltages
[Samsung Galaxy Nexus] franciscofranco:
MPU, IVA and CORE ;)
[Samsung Galaxy Nexus] mike216:
hi Franco, you have any good suggestions for Iva and core UV settings?
[Samsung Galaxy Nexus] patmw123:
Thanks guys. :)
[Samsung Galaxy Nexus] OneNutShort:
The new kernel (141) feels super snappy! Totally in love.
[Samsung Galaxy Nexus] houzuoguo:
first time Franco kernel user here :-)

I recently got my Nexus Galaxy and today I flashed Franco kernel. While using the Franco Kernel Updater app, I've got these questions:

- If I manually undervolt in "OC/UV" tab, do the voltage settings apply on boot? does "Set at boot" affect undervolt settings??

- In "Settings" tab. If I turn on "Generic hotplug", does the "CPU Mode" settings affect generic hotplug when screen is off?

- In "Calibrated voltages" tab. Is there any way to know the current voltages when smartreflex is turned OFF? Also, are my undervolt settings always ineffective when smartreflex is Not disabled?

Thank you very much :-)
[Samsung Galaxy Nexus] darrendm:
Undervolt settings do not set on boot (This will always be the case because undervolting can lead to freezes on boot if voltages are too low)

Generic hotplug shuts down cpu1 when screen is off, so I assume if you are using single core mode, cpu1 is already off thus no cpu is turned off by the generic hotplug (my assumption)

Your undervolt settings are not ineffective when SF is enabled. Your settings will act as the maximum voltage which the SF will hit, so they will be at your set value or lower.

There is no way to check your current voltages (directly) using the calibrated voltages tab (when SF is off), however in the tab it tells you the MHz at which the phone is running at, and then you can go to the UV settings tab and see what you've set that speed to. (as SF is off your phone will always use this value at this clock speed)

With SF off, the phone will use your applied voltage for each frequency

With SF on, the phone will use your applied voltage OR LOWER at each frequency
[Samsung Galaxy Nexus] Droid_JD:
Just curious, anyone else experiencing GPS issues? The last three times I went for a run I have been unable to get a signal. I keep up with the nighties and use the on demand governor. No UV and using.cm9. I don't know what other information is helpful/relevant.

And of course, thanks for all the hard work Francisco, it's absolutely appreciated by all!
[Samsung Galaxy Nexus] sway40:
Mine works... you sure it's not the rom?
[Samsung Galaxy Nexus] Droid_JD:
I'll try a new one next time I run. thanks for the suggestion-never had any issues with cm though, but certainly worth trying.
[Samsung Galaxy Nexus] sway40:
Cm9 is a good rom, but not done by any means so there's chance something somewhere is not working. Try aokp, I was always loyal to cm until I tried aokp and haven't looked back since.
[Samsung Galaxy Nexus] aliensquale:
Do people recommend using "generic hotplug" does it save a lot of battery?

How about using the "sqlite" setting?
[Samsung Galaxy Nexus] aliensquale:
I just got 3198 all default settings on franco 141 and aokp build 32.. I have the full 4.0.4 radios too btw.

How did you get so high?
[Samsung Galaxy Nexus] Flip35:
Same here, all I used to breathe was cm and I was always desperate waiting but once I tried aokp that was it, feature rich and lots of stability I'm not saying once cm is done I'll give it a shot then but right now aokp is the rom to have imo
[Samsung Galaxy Nexus] Droid_JD:
I've been trying not to make the switch, I'd feel like a traitor. Haha., maybe I'll give it a shot.

GPS is working fine now though, think it was just the heavy overcast this morning?
[Samsung Galaxy Nexus] Tree of Knowledge:
Would this kernel have any effect on tethering speeds?
[Samsung Galaxy Nexus] Flip35:
lol i laugh cuz i swear if felt the exact same thing, but once i tried aokp i also use black ice every now and then plus this kernel, my phone is complete
[Samsung Galaxy Nexus] Dr. Hax:
I notice in the latest nightly it said "disabled sync framework"

So if I flash it, no sync will work such as Gmail, contact sync, Facebook, and other apps or is it referring to something else?
[Samsung Galaxy Nexus] chris157:
Where do you find the changelog for the nightlies? I only see the milestone one on the first post
[Samsung Galaxy Nexus] Gahh Its Lee:
Its referring to something else.
[Samsung Galaxy Nexus] innov8ion:
He posts nightly changelogs in the thread. Not too hard to find them.
[Samsung Galaxy Nexus] Orio56:
r141 is super !!! This is the first Franco kernel I have been able to run on my Gnex using 512mhz. I always had to use the 384mhz version. Thanks Franco !! :D
[Samsung Galaxy Nexus] Flip35:
If is not too much to ask, what's the difference between 384mhz and 512mhz, when I just to download it asks me which one and I always choose 384mhz cuz I'm scare to mess my phone up cuz I don't knw what 512 would, is it faster or better battery
[Samsung Galaxy Nexus] TEK112:
Higher clock speed means faster speed and worse battery. However, some phones have issues with the higher GPU. Download the 384 version and rename to 384 (as both have the same file name) and then download the 512 version and rename accordingly. Then flash 512. If you have issues, you can always revert to 384.
[Samsung Galaxy Nexus] Flip35:
Thanx I'm gonna give it a shot since I have 2 batteries even though I'm on hotplug 384 and the latest nightly n I got good batt all day, thanx for the info
[Samsung Galaxy Nexus] timbck2:
Has anyone else been experiencing Wifi problems on franco 141? I've been having problems connecting to my home Wifi since upgrading to 141 (512 MHz) this morning. I'm going back to 140 to see if the problem goes away.

Update

: I went back to kernel 140 (384 MHz) and Wifi connected right up.
[Samsung Galaxy Nexus] sway40:
Seems like mine was dropping a lot, couldn't confirm if it was kernel related. I was to lazy to flash back knowing they'll prolly be a new kernel tonight.
[Samsung Galaxy Nexus] Flip35:
Dam what a difference, I flashed 512 n I do feel the better performance I like how it feels, my wifi is working though so far no issues
[Samsung Galaxy Nexus] foueddyf:
Yeah I have the wifi problem as well on 141 (384mhz). Was fine on 140 though.
[Samsung Galaxy Nexus] axne1:
I've been getting high #'s Idk?

Kanged out Google phone +

Franco's Magic :)
[Samsung Galaxy Nexus] Adan.Mejia3:
My wifi is running fine on 141. Weird.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Flip35:
Mines too, I downloaded wifi analyzer just in case to check n all seems fine, I'm on 512
[Samsung Galaxy Nexus] MONKY_1:
Dude I'm getting amazing battery life on 141! I love it!
[Samsung Galaxy Nexus] axne1:
Wi-Fi smooth here!

Kanged out Google phone +

Franco's Magic :)
[Samsung Galaxy Nexus] Jeff Zaugg:
Is there a r142 out somewhere?? I've seen a couple posts where people are saying they have franco's r142 installed on there phones over at rootzwiki
[Samsung Galaxy Nexus] mikespe:
Franco is working with the Liquid crew on their rom...142 is built into Liquid
[Samsung Galaxy Nexus] Jeff Zaugg:
oh ok thanks
[Samsung Galaxy Nexus] Rootuser3.0:
I'd have to say out of all the kernals I've flashed I've seen a significant speed boost with R140. Its no placebo effect either its actually a real speed difference you made me a believer Franco thanks!
[Samsung Galaxy Nexus] Droid316:
Franco is there a 512 version of #142
[Samsung Galaxy Nexus] gnexdude:
Battery life is pretty solid so far on 141! Seeing better results than 138-39...
[Samsung Galaxy Nexus] axne1:
Great job on this one Franco!

4hrs on screen with r141.

This feels right.

Kanged out Google phone +

Franco's Magic :)
[Samsung Galaxy Nexus] zeke1988:
i got 2 hrs max on all of this kernel...
[Samsung Galaxy Nexus] Flip35:
Yup and the performance is also nice, I'll be on this one for a while
[Samsung Galaxy Nexus] Shamrock13:
I've never actually flashed a kernel before, but I have a simple and quick question. Do I have to flash it each time I install a new ROM? Say I install AOKP and then I want to try LiquidSmooth, will I have to wipe data/etc and then install the ROM then the kernel?
[Samsung Galaxy Nexus] Flip35:
yeah thats correct
[Samsung Galaxy Nexus] timbck2:
Yeah, I updated to Liquid 1.3 today after I posted about the Wifi problem with 141 (and went back to 140) and was surprised to see kernel 142 after I rebooted. No Wifi problem with 142 though.
[Samsung Galaxy Nexus] dw3bb10:
Running AOKP & just flashed M2. Im trying to enable Hotplug, but whenever I try to change the "0" to a "1" (which I assume activates hotplug", Im not able to save the file. Any suggestions?
[Samsung Galaxy Nexus] axne1:
WOW!!!

I'm staying on this one. It trumps M2!

sent from a Android device :)
[Samsung Galaxy Nexus] axne1:
Lol of course I fed it up...

sent from a Android device :)
[Samsung Galaxy Nexus] sing1gnis:
Can you post your settings? I just don't see how you do it.

I'm the same way. I feel so inadequate. :(