yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] dcoy82:
Anybody have any idea on this one? I still get an error when I try to purchase his kernel app on the market. I can purchase or download anything else, except this? :confused:
[Samsung Galaxy Nexus] sinik420:
i dont see a screen on time
[Samsung Galaxy Nexus] PaulG1488:
With that screen percentage I'll guess less than 2 hrs

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] kevguillot:
Can y'all see that one?
[Samsung Galaxy Nexus] kevguillot:
lol forum tough guy
[Samsung Galaxy Nexus] sinik420:
dont think i wouldve used frye if i was going for the tough guy. I just dont understand how you see a screen on time in the pic you keep posting
[Samsung Galaxy Nexus] kevguillot:
It says screen on, awake, and charging.

What exactly are y'all wanting to see??
[Samsung Galaxy Nexus] sinik420:
the screen on time smh -.- the relevent part to battery shots here
[Samsung Galaxy Nexus] TEK112:
They want you to go into the battery stats and press the screen battery usage to show them how long the screen was on. It will give you a time.
[Samsung Galaxy Nexus] grifforama:
You're in luck

http://xdaforums.com/showthread.php?t=1708763
[Samsung Galaxy Nexus] butikofer08:
this is normal for Franco kernels, at least for experimental versions

Does 241 have the hotplug governor as an option?
[Samsung Galaxy Nexus] jcmm11:
Hotplug was removed awhile ago. Franco said that it's not needed and that the kernel automatically takes the 2nd cpu offline if it's not being used
[Samsung Galaxy Nexus] butikofer08:
I wonder if it disables it when it's not used or only when the screen is off. Cuz that's the difference between the hot plug governor and the interactivX governor seen on some kernels, interactiveX only disables second cpu when screen is off.
[Samsung Galaxy Nexus] Hungry Man:
Having some odd problems with franco.kernel updater app not locking frequencies in.
[Samsung Galaxy Nexus] Hungry Man:
Awesome, thanks. When will the app update?

edit: 230mhz slot still defaults to 384mhz voltage.

Is 241 newer/older than M5?
[Samsung Galaxy Nexus] nnnnr14:
384mhz :(

I got 99 problems but bamf ROMs ain't one! -nnnnr12
[Samsung Galaxy Nexus] JLO155:
Any chance at getting M5 with 512GPU?
[Samsung Galaxy Nexus] Wynnded:
I think that Franco already said something like.... "Nop".
[Samsung Galaxy Nexus] bbernardini:
Two questions about M5:

1. Does this fix the Settings > Storage FC bug?

2. Does GTA3 work with this kernel now?
[Samsung Galaxy Nexus] Ammontj:
I'm running m5 with the Vicious AOSP 4.1.1 v1 JB ROM. I can't say that I tried going to settings > storage before m5 but I can say that but does work right now for me.

And can't help you with question 2 sorry
[Samsung Galaxy Nexus] JLO155:
OK. How about the 512 GPU nightly patched up to 3.0.41!
[Samsung Galaxy Nexus] gfropr:
I have an extended battery if I want to charge all the way up do I set the battery life extender to 0 or 100 in the Franco app? Thanks.
[Samsung Galaxy Nexus] sway40:
100 foo, doesn't matter if you have extended battery or not.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] geronemo:
I have GNex Verizon running:

Android 4.0.4

Build IMM76k

which of the following should i download so update the kernel,

also what's the difference between Nightlies 512 and 384.

Downloads:

Milestone 4: http://minooch.com/franciscofranco/Galaxy Nexus/

Nightlies 384Mhz GPU: http://minooch.com/franciscofranco/G...es/gpu_384mhz/

Nightlies 512Mhz GPU: http://minooch.com/franciscofranco/G...xus/nightlies/

Thanks :)
[Samsung Galaxy Nexus] DoobiHowserMD:
Do these numbers seem kinda off to anyone else?
[Samsung Galaxy Nexus] Hungry Man:
Seems normal to me.
[Samsung Galaxy Nexus] jcmm11:
They're not normal. Just reset the timers or reboot. I had that happen to me once, not sure what caused it.
[Samsung Galaxy Nexus] DoobiHowserMD:
Considering all the individual times should add up to the total time, these numbers are wrong and add up to over 100%. My deep sleep is over 100% alone. I've never seen this in all my time on android. Just seemed off.
[Samsung Galaxy Nexus] TEK112:
It looks normal for a 230 MIN. Try upping it to 384 and it should look more linear and stable. My thought is that since 230 is so low the ramp up causes it to jump 384 and go right to 729. That is why the usage looks so uneven.

---------- Post added at 09:25 AM ---------- Previous post was at 09:21 AM ----------

Wiping the battery stats in recovery usually fixes that. Normally it comes from a dirty flash of a ROM or screwing with multiple batteries.
[Samsung Galaxy Nexus] Hungry Man:
I haven't been getting 'deep sleep' much at all.
[Samsung Galaxy Nexus] fk.gregor:
this app keeps giving me issues when trying to flash imoseyen kernels on the latest cm9 stable rom. is anyone getting this problem as well? can this get fixed??
[Samsung Galaxy Nexus] Deathwish238:
Anyone have any stats for battery life using Wheatley and/or Lazy with 1.8 GHz max frequency?
[Samsung Galaxy Nexus] bbernardini:
Just updated to the latest nightly (and running the latest Jellybro)...still getting the FC on Settings > Storage, and GTA III still doesn't run. Other than that, everything seems great. I'm just perplexed by these two issues.
[Samsung Galaxy Nexus] Hungry Man:
I don't get the FC but yeah, GTA3 doesn't run.
[Samsung Galaxy Nexus] kdo23:
Just recently bought the Franco app and was wondering about battery extender.

If I leave the charge level at 100% will it still do the normal thing where after it hits the top level it will stop charging for a bit?

I am basically worried that I may lessen the life of my battery if this tweak allows the charge level to be too high or if there is another value I should set it too.

Checked a bunch of pages did not see any answers. I am on tapatalk and advanced search is not available. Thank you for any help in advance.
[Samsung Galaxy Nexus] k_nivesout:
Setting the BLX to 100% is the same as the stock value, no need to worry about overcharging as it's the stock behavior. The idea behind BLX is that by not charging the battery to 100% each time, you extend the overall lifespan of your battery. The mod doesn't allow for overcharging, so you're good to go with whatever value you want to set.
[Samsung Galaxy Nexus] kdo23:
Sweet was just wasn't sure about the context.
[Samsung Galaxy Nexus] demill66:
Need Tips for Battery Savings

Ok, this is my first time ever flashing a kernel, though I've been flashing roms since my incredible. I've had terrible battery life since day 1 with the GNex and the extended battery. Never lasting beyond a day. I flashed Franco's yesterday and charged over the eve. I've had the phone unplugged for about an hour, made a phone call (5 min at most) and checked email. I'm now down to 90% battery. I don't think that this is any different than the drain I've had in the past, but not necessarily better. Does anyone have any suggestions as to what I should do to reduce battery drain (other than not using the phone at all)? Any and all tips are welcome. Thanks. BTW- using mmuzzy's 8/17 rom.
[Samsung Galaxy Nexus] EDNYLaw:
First thing (if you haven't already) is purchase Franco's App is it will allow you to change all the settings for the kernel (and support an amazing developer).

Second, try messing with different governors. I've had lots of luck with interactive, but wheatly definitely isn't bad either. Mess around with overclocking and underclocking. My kernel is set at 230 min and 14xx max with no undervolting, just using smart reflex (which is enabled by default).

Stock (for Franco) screen off max is 729, you could mess with that, but from what I hear having it at 729 provides the best screen off race to idle (how fast the process is completed and phone goes back to sleep), but you can try lowering it to the 300 or 200 slots.

Also consider adjusting your brightness on the phone if it's all the way up, mine's around 30% or so. Along this line, make sure content adaptive brightness is enabled. Whites will look more grey, but it'll use less power.

You can also disable logging and that MAY save SOME battery, but if it does it'll most likely be negligible.

Also, you can try the different GPU speeds, 512 and 384. I usually use 512 but it does run at a higher voltage (thus uses more energy) than the 384 which uses the same voltage as the stock GPU.

If you really want to max out battery, have as few apps as possible syncing. I have gmail, contacts, calendar and chrome syncing, everything else is off.

Get rid of facebook (if you have it installed) it's the worst programmed app around. If and when I use it, I just use the mobile website.

Download better battery stats (link is on XDA somewhere) or badass battery (may be called something different now) and monitor any rogue apps that are causing excessive wakelocks.

Basically, to sum it up: each user experience is unique and you really just have to play with the settings until you find what works.
[Samsung Galaxy Nexus] k_nivesout:
As I understood it, content adaptive brightness will actually lower the screen brightness when displaying whites and light backgrounds, meaning leaving it on should theoretically help a little bit.
[Samsung Galaxy Nexus] EDNYLaw:
Sorry, yeah I meant enabled. I'll edit that. You're correct, disabling it blows out the whites, using more power. Just got the check box to disable and uncheck box to enable reversed :)
[Samsung Galaxy Nexus] demill66:
Super User Permission

Everytime I boot, I get the Grant Permission request for this kernel. Is there any way to have it automatically apply, so the dialog doesn't always appear?

Thanks.
[Samsung Galaxy Nexus] EDNYLaw:
Make sure you're using SuperSU and make sure when the dialogue box pops up, you don't have the box checked that says ask again or something like that. If you're already doing all that, try clearing the data on SuperSU (settings --> apps --> SuperSU --> clear data) and open Franco's app up again and approve it.

If you have not been using SuperSU, download it from the market, install it, open it and update the SU binaries. At that point, SuperSU is set up and you can uninstall SuperUser (the other su program, NOT SUPERSU).
[Samsung Galaxy Nexus] demill66:
Will do. Thanks EDNYLaw.
[Samsung Galaxy Nexus] lynxznet:
Sooo, I tried one of the nightlies for JB and it actually caused the boot to freeze. Took me a while of looking around to figure exact what to do.. I put the phone into recovery via bootloader - and was able to ADB push the milestone 5 kernel thank god. The milestone 5 kernel is working great so far! Not sure why the nightly caused problems.
[Samsung Galaxy Nexus] TEK112:
I had that happen with 246. Smooth sailing now on 248.
[Samsung Galaxy Nexus] jaenizzo:
Can someone tell me step by step how to setup Franco kernel updater to make my phone perform well and have the best battery life thanks
[Samsung Galaxy Nexus] EDNYLaw:
Read a few posts back

http://xdaforums.com/showthread.php?p=30874795

Sent from my Galaxy Nexus using Xparent Blue Tapatalk 2
[Samsung Galaxy Nexus] jaenizzo:
Thanks
[Samsung Galaxy Nexus] Smokeey:
Looks like an error with the new OMAP drivers, specifically with the L3, L4 cache.
[Samsung Galaxy Nexus] JRJ442:
Maybe try 248. Its been amazing so far.
[Samsung Galaxy Nexus] Eschmacher:
No reboots overnight, it's been 11 hours. I wasn't paying attention in the franco app and checked "apply governor settings on boot" which is only for interactive (I'm using wheatley).
[Samsung Galaxy Nexus] nvrMind:
I always have trouble with my camera when I'm running a kernel with the 512 gpu. Is this common? Is that why we have it in both varieties. I don't have any problems with the 384, just curious.

Thanks
[Samsung Galaxy Nexus] bbernardini:
Has anyone figured out why GTA 3 doesn't run on this kernel? It just perplexes me.
[Samsung Galaxy Nexus] Alton (Halo 2):
Yea my GTA 3 doesn't work either . But thanks Franco for the updates ! :)keep them coming ! :P
[Samsung Galaxy Nexus] EDNYLaw:
Did you replace the su binary? If not, go to the OP (not sure if this one, but definitely in the GSM thread) and get the su binary file. Or, get the zip you flashed your ROM from and navigate to /system/bin and swap the sdcard binary file in your current ROM with the one from your original zip. Set permissions to rwxr xr x and reboot or follow these instructions:

Take the flashable zip your ROM came from and navigate to /system/bin and pull the sdcard file

then:

adb shell

busybox mount -o remount,rw /system

exit

adb push sdcard /system/bin

adb shell

chmod 755 /system/bin/sdcard

exit

adb reboot

or you can do all that in root explorer I just prefer typing on the computer

Perhaps Franco's sdcard binary that you downloaded isn't playing nice with your ROM. Try the original one from your ROM and see how that works. Just know that I believe every time you flash Franco's kernel in recovery you may have to do this. But if you auto-flash with his app it doesn't flash the sdcard binary. I don't remember whether Franco said he changed whether the binary flashes in recovery.

Sent from my Galaxy Nexus using Xparent Blue Tapatalk 2
[Samsung Galaxy Nexus] amessina:
This might be a newbie kernel question, but is there a standard benchmarking results that compare individual kernel performance and different kernel settings?
[Samsung Galaxy Nexus] EDNYLaw:
You can try using the same benchmark for different settings. However, you have to wait for the phone to cool back down between benchmarks because thermal throttling can scale back the CPU and thus give you lower scores.

That being said, benchmarking is largely useless, as Franco's quote from Chainfire states: "However, if you put any trust in Quadrant scores you could use them to prove that dancing naked for 5 minutes in your garden affects device performance."

But if you want to use it to compare settings (for what it's worth) then make sure all other variables are the same, like temperature, apps running, power consumption and the like. By removing all non-tested variables, you'll get the most accurate benchmarking between different settings. However, you don't necessarily have to go by benchmarks, just try different settings, see what is stable and what feels best for your device and what gives you optimal battery, it's different for everyone, so try tons of different things out.
[Samsung Galaxy Nexus] amessina:
When I typically flash roms, I always do a wipe cache/wipe dalvek. Afterwards, upon reboot, you see "android is optimizing" as a result.

I noticed when using the Franco app, that these procedures are not done (or are they).

Is what I've been doing with other kernels unnecessary? Is Franco doing something else?

BTW - love the kernel!
[Samsung Galaxy Nexus] EDNYLaw:
Franco's app does everything necessary to have it run properly. That being said, you certainly won't hurt anything by wiping cache and dalvik. But I auto flash all the time and have never had a single problem with one of Franco's kernels, even some experimental ones. The guy is a genius.

Sent from my Galaxy Nexus using Xparent Blue Tapatalk 2
[Samsung Galaxy Nexus] timbck2:
I just switched to the new Affinity Series kernel for my GNex (I was running Liquid Smooth). It's only the first beta, but it seems very polished and well-thought out. And it works well with Franco kernel (as I expected it would!)
[Samsung Galaxy Nexus] TEK112:
Huh?
[Samsung Galaxy Nexus] timbck2:
Sorry, I meant ROM - Affinity Series ROM. It's too early in the morning to be posting to forums!
[Samsung Galaxy Nexus] TEK112:
It's all good.
[Samsung Galaxy Nexus] hawkinsandponcho:
franco.Kernel updater + Nightly #248 is running terrifically for me with CNA 3.4.1

Thank you.
[Samsung Galaxy Nexus] t1n0m3n:
If I tried to tell a car group that a dyno was largely useless, I would get laughed off the forum. Computer benchmarks (and dynos) are very valuable tuning tools, that if used correctly can extract the best performance out of your device. Any benchmark that is unrepeatable and easily influenced (quadrant) is useless. Benchmarks themselves, done correctly, are very useful and noteworthy.
[Samsung Galaxy Nexus] TEK112:
Apples and oranges man...

A dyno won't let a car run a 3rd gear pull WOT and show 300HP and subsequent pulls of 250HP, 500HP, 100HP, etc... Yes, some dynos (like the mustang dynos) will show incorrect data (comparatively), but it will be consistently off; which is useful.

The problem is that there are so many dynamics to the various benchmarks that consistent reliable reuslts are almost impossible to come by and end up causing people to chase ghosts wondering how they lost "performance." Thermal throttling, memory handling, background process', etc, are all contributing factors.
[Samsung Galaxy Nexus] EDNYLaw:
Hey, you're entitled to your opinion, but Franco, ya know the one makes the kernel, he's got his own opinions on benchmarking just check his signature. Too many variables to control. Best benchmark, using the phone and deciding how that particular kernel and ROM feel over a given time period.

Sent from my Galaxy Nexus using Xparent Blue Tapatalk 2
[Samsung Galaxy Nexus] raddacle:
So I'm quite new to the nexus and I'm getting terrible battery life. I'm running CM 9.1 stable and the #196 384 gpu with interactive at 384-1036 and screen offf max at 729. It shows that my display is the biggest killer for the battery but I have it set to 25 and I content adaptive brightness on. The battery dies at about 2 min to 1% ratio even with data off and obviously worse with it on. Recommendations? Help??
[Samsung Galaxy Nexus] npainter7:
Hi I just flashed this kernel. Looking forward into some great things. Now in the OP I see the change log like what the kernel does and capable of doing. Now is there a settings section I can go to for this kernel?? I just don't know where to look for it if there is one. Thanks in advance
[Samsung Galaxy Nexus] stickerbob:
I believe you have to use this app from the Play Store

https://play.google.com/store/apps/details?id=com.franco.kernel&feature=nav_result#?t=W251bGwsMSwxLDMsImNvbS5mcmFuY28ua2VybmVsIl0.
[Samsung Galaxy Nexus] blay76:
Well worth it too, imo.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] EDNYLaw:
Flash JB Bootloader, JB radios, JB ROM and a Franco JB kernel. Without any serious tweaking my battery lasts easily all day, granted I'm at work and not using it much, but it's on 4G and I still end the day with about 30% left with 2 hours of screen on time and that's on battery for like 16 hours. My settings are 2xx to 14xx, interactive (no settings touched), 729 max screen off, brightness around 20-30%, content adaptive brightness enabled, 4G on all the time when not at home, WIFI and no data when at home. Only syncing calendar, contacts, gmail. Get rid of facebook app if you have it, if you need to use facebook use their mobile webpage but the app is terribly coded. Download BetterBatteryStats either from the Play Store (paid) or from XDA (free) and see if there are any rogue apps causing wakelocks. Also make sure after flashing a ROM you open up maps and let the GPS get a lock on you. Everyone's phone is different and we all have different apps and such, just got to find the best combination of apps and settings for your device.
[Samsung Galaxy Nexus] raddacle:
Thanks for all the great advice!! I really do want to try to JB but I'd rather wait till its more stable. Do you know if I can flash JB then switch back to ICS? And if not, do you know anyway to achieve better battery while on ICS?
[Samsung Galaxy Nexus] Antob125:
Its been 100% stable since it's release from source. Stop waiting.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] czonin:
Nightly 249 has been running great as far as performance and screen on battery life. The only thing I've noticed is my screen off battery while on 3g isn't where it should be.

---------- Post added at 06:25 PM ---------- Previous post was at 06:09 PM ----------

Do you have all location services checked as well?
[Samsung Galaxy Nexus] EDNYLaw:
Yes, all the services under settings--> location services are enabled. Probably could disable them but I don't want to affect Google Now, I use it all the time. But, along those lines, I have an automateit pro rule to turn off GPS when the screen is off.

Sent from my Galaxy Nexus using Xparent Blue Tapatalk 2
[Samsung Galaxy Nexus] czonin:
Can't connect to WiFi with nightly 250
[Samsung Galaxy Nexus] aggrophobik:
No wifi issues here on #250.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] tacosrdelicioso:
No WiFi issues.....but I did just get my first BSOD in a long time....:(
[Samsung Galaxy Nexus] TEK112:
Really? A BSOD on Linux.
[Samsung Galaxy Nexus] tcapote:
No problem with wifi on 250 running Jellybro 9/10
[Samsung Galaxy Nexus] tacosrdelicioso:
I've seen the term used here on the forums...its for Black instead of blue though. When u try to wake your phone and only get black screen

Edit: on a lighter note...after my battery pull no issues..that happened like 5 minutes after flash kernel and its been a good 10 hours since
[Samsung Galaxy Nexus] TEK112:
Yeah, but even then it usually isn't frozen. Something upsets the JB filesystem and it can take 15 minutes for the phone to boot stuck at the Google logo. Pulling the battery during that time is bad and could corrupt the ROM.

Upgrading from the ICS bootloader to the JB bootloader has minimized this, but it still happens.
[Samsung Galaxy Nexus] tacosrdelicioso:
Ik I am aware. I've been pretty lucky though...been flashing jellybean since the first builds were available for toro...never had the long wait at Google logo. Even before I flashed the jb boot loader. No issues....
[Samsung Galaxy Nexus] tacosrdelicioso:
Thought I'd share this....lte just popped up at my house literally last night. So...after a full charge this morning I've been able to do some battery testing. Keep in mind. STOCK battery. 4g on the whole time. Right now I'm at 2 hours battery. 65% and 1h50m screen time. Tapatalk surfing mostly and texting. Low brightness
[Samsung Galaxy Nexus] krazie1:
Really good battery life on r249 384 gpu & aokp build 9/13 & black exodus theme. 4G on the whole time.
[Samsung Galaxy Nexus] blackhand1001:
My WiFi will not connect on 250. I know you changed the WiFi drivers on 250. It works on 249 and the stock cm kernel. It still doesn't work even when standing right next to the router. I reset it tried everything.
[Samsung Galaxy Nexus] :
Hmm, may be a CM Problem. I was using AOKP jb build 1 and I used r250 and the WiFi connected and worked just fine. Although, the battery life isn't as great as r249.
[Samsung Galaxy Nexus] jonstrong:
Flashing 251 now with CNA 3.5.0.... doesn't show in the free version of the Franco updater yet, but you can download from his site.... changelog suggests this will improve Wi-Fi stability over 250.
[Samsung Galaxy Nexus] Wynnded:
Is your security WEP or WPA/WPA2? Joining the 21st century and changing it to WPA made the difference for me.
[Samsung Galaxy Nexus] blackhand1001:
I am on WPA. There are new wifi drivers on 250. It works on the stock cm kernel and on 249. It won't connect on the new drivers no matter what I do. I even wiped the data partition and tried a fresh ROM. Same issue. Factory reset the router as well. No luck. There's obviously a bug in the new wifi drivers that makes it not work with certain routers. Its the Verizon FiOS g router BTW.
[Samsung Galaxy Nexus] Wynnded:
I thought that I would ask. BTW is would appear that 251 is out. It doesn't show up in the app, but if you go ahead and download and flash "250", it downloads and flashes 251 (I just did it that way). Hopefully that will sort you out.
[Samsung Galaxy Nexus] aggrophobik:
Odd, WiFi was perfect for me on 250.
[Samsung Galaxy Nexus] :
For some reason, I'm getting really poor battery life on r250 and r251 nightlies. Anyone else experiencing this? The r249 is absolutely amazing though. I'm getting quite the battery life with it.

~Sent from my Galaxy Nexus VZW
[Samsung Galaxy Nexus] czonin:
Still no WiFi on 251 with WEP.
[Samsung Galaxy Nexus] jonstrong:
I'm finding WiFi and battery excellent on 251 so far.

Sent from a Galaxy Nexus far far away...
[Samsung Galaxy Nexus] :
Hmm idk. When I flashed it, and waited for like 10 minutes, it drained really bad. Like 10%

~Sent from my Galaxy Nexus VZW