yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] Droid316:
161 :)
[Samsung Galaxy Nexus] theneighbor:
Coming from r158 and noticing improvement in battery life already on r160. Very nice.
[Samsung Galaxy Nexus] alphanu22:
Signal isnt a Kernel problem-
[Samsung Galaxy Nexus] laureanop:
How is this possible ? 999 and 160 have been superb with my phone. On liquid

"the relentless pursuit of the perfect rom "
[Samsung Galaxy Nexus] fix-this!:
funny as i just went back to 158 and im back to 3 bars. when i had my thunderbolt i read the kernel does in fact play a role with the radios too.
[Samsung Galaxy Nexus] alphanu22:
i guess it somewhat, but i cant say that ive notice a difference, im always in 3-4 bars-
[Samsung Galaxy Nexus] fix-this!:
yeah i don't get much more than 2-3 bars in my home. outside i get about 3-4. the biggest difference to me is the battery life. i went back to 158 and it's already like night & day from 160. it's weird how our phones handle these kernels differently. :eek:
[Samsung Galaxy Nexus] alphanu22:
8h and im at 63% r160

not to bad-
[Samsung Galaxy Nexus] fix-this!:
on stock battery i went 25hrs on 158. just got my 2100mah extended today so we shall have to test it out. 160 seemed to be draining alot for me today.
[Samsung Galaxy Nexus] kennyp987:
#157 384mhz is a winner for me....#160 was was stuttering a little for me so I'm back to #157
[Samsung Galaxy Nexus] beefdog:
Do you guys turn your data off when you say you got like 25 hour battery life
[Samsung Galaxy Nexus] Shamrock13:
I always wonder this, too. I feel like that's a crazy number. I don't think I can get 16 hours out of my phone, and I see people getting 2.5-3 hours on screen time with 16-17 hours and I probably couldn't get 1.5 hours on screen and 15 hours.
[Samsung Galaxy Nexus] mark manning:
They probably have very few apps on their phones. Also the apps the do have most likely don't have ads within the app. I, at least for myself, have noticed that those two things make a big difference

Treating LTE similarly to wifi (only have it on when you need it ) also helps

Sent Telepathically ©
[Samsung Galaxy Nexus] past_pluto:
That signal you have is killing your battery. Nothing you can do. I never see red lines like that.
[Samsung Galaxy Nexus] relax24:
Is anyone undervolting Core & IVA values? If so, what are you using that is deemed stable for YOUR phone.
[Samsung Galaxy Nexus] sway40:
I have over 100 apps on my phone, data off with aokp power saver, and certainly no lte. I got 1 day 2hrs on battery with 3hrs screen on time yesterday.

~ Sent from my GNexus on Aokp ~
[Samsung Galaxy Nexus] eleer:
I've gotten similar numbers as well, though I have the 2100 mAH battery. I'm running AOKP and got 1 day, 1 hour, with 3 hours and 9 minutes of on-screen time. My brightness is a quarter of the way, 3G is ON, WiFi is ON and I have 60 apps installed on my phone. I do not run 4G, all my data comes from WiFi.

*I am running Franco Kernel r151 nightly and in my opinion, it's the best nightly Franco has made. I've ran all of them and still go back because I don't get the battery savings I do while using r151*

---------- Post added at 09:41 AM ---------- Previous post was at 09:37 AM ----------

I use stock voltages that Franco has set.
[Samsung Galaxy Nexus] LothianScykle:
r160 Warm Reboot (last_kmsg included)

I'm running r160 (3.0.8-franco.Kernel-nightly-384GPU) with LiquidSmooth 1.35. I just had a warm-reboot, followed by what looks like a normal startup. Everything seems to be fine at the moment. Attached is a compressed last_kmsg file.

Thanks,

~
[Samsung Galaxy Nexus] fix-this!:
no, im usually on wifi though, i never turn off 4g either. im running 158 @ 384 gpu with it undervolted and using interactive governor.
[Samsung Galaxy Nexus] phaze one:
I used to use power saver on AOKP but it was kind of dodgy so now I manually disable/enable data when I need it and it's boosted my screen on time to 3.5 hours+ and 24 hours+ on one charge. It's pretty sweet. I'm using AOKP MS5 and franco's MS3 underclocked and undervolted. MS3 has been the best for me as far as battery and temperature. I have the OEM extended battery btw.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] TEK112:
I think the point he was making is that the number of apps that need to call home correlate heavily to negative battery life.

You saying you have over 100 apps would be a good counter, but you said you turn data off which kinda negates the whole argument. Just sayin.
[Samsung Galaxy Nexus] Droid316:
I have 321 apps installed on my phone but I only run like 5 of them most of the time. does it matter battery life wise if you have lot of apps installed but don't run many of them.i have a crappy 3g signal at work so i turn off data alot. but only get like 1.5 hours screen time with extended battery.
[Samsung Galaxy Nexus] TEK112:
That sounds normal for crappy signal. Apps affect battery life minimally, but if you turn data off it will help offset that.

I always delete apps I don't use because I don't want them starting up with my phone and I don't want to live in a startup manager or micromanage my apps.

I just got done flashing back to 160 and the phone lasted 3hrs 45min. with 8% left after playing Where's My Water for 2hrs (2hrs screen on time). I say not bad!
[Samsung Galaxy Nexus] phaze one:
+1. Delete the crappy apps you don't use. No use having them.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] stick1300:
Ok, forgive me if what I'm asking isn't even possible, but could a kernel issue be causing apps to freeze up? If I try to launch certain apps, my phone will freeze up and require either a battery pull or for me to toggle the screen on and off, then launch another app from my lockscreen. It's mostly games, but not exclusively. Barcode Scanner and Google Goggles do it too. It happens with the same apps, every time, regardless of if they've been installed off the market or from backups. The issue has persisted over multiple versions of Franco's kernel, so I'm not sure they're linked.
[Samsung Galaxy Nexus] TEK112:
Does it do it on another kernel? IMOSEYON?
[Samsung Galaxy Nexus] stick1300:
Just flashed the latest stable IMOSEYON and tested it out. Angry Birds, Age of Zombies, and Google Goggles all ran fine, but they all freeze instantly on Franco 154 and 156 (both 384).
[Samsung Galaxy Nexus] TEK112:
What are the speeds you had it set to, max/min?

edit: Also, did you have smartreflex disabled?
[Samsung Galaxy Nexus] stick1300:
1036 max, 384 min. ondemand governor, generic hotplug enabled, smartreflex enabled (never bothered messing with undervolting). But, I've tried interactive gov., disabling hotplug, and 1228 & 1344 max and nothing's changed.

EDIT: Was flashing back to 156 while I posted this and it seems like all is well now. The apps that were hanging seem to be launching fine. I even installed Fruit Ninja, which wasn't working last night, and it's running a-ok.
[Samsung Galaxy Nexus] TEK112:
I would reboot into recovery and wipe cache/dalvik and then upon boot disable hotplug and disable smartreflex. Live there for a day or so and see how it is.
[Samsung Galaxy Nexus] sway40:
Not really bc my data is set to come on every 30 min to check for updates and sync, I know what he's saying.

~ Sent from my GNexus on Aokp ~
[Samsung Galaxy Nexus] flytechguy:
I would try to wipe the caches and do a fix permissions just in case. Seemed to fix my problem.
[Samsung Galaxy Nexus] peterlemonjello:
I'm undervolting on my VZW GNexus with AOKPb36 & Franco M3. I haven't really pushed the limits to see how low I could get them. I've only decremented IVA and Core a little bit. FWIW, I seem to be getting better battery life than with SmartReflex.

CPU:

1344 = 1100

1228 = 1100

1036 = 1050

729 = 875

384 = 775

IVA:

266 = 1010

133 = 850

Core:

307 = 1027

153 = 862
[Samsung Galaxy Nexus] laureanop:
I've noticed that the 512 and the 384 gpu speeds draw the same voltage. Does anybody know if this means that in everyday use they use up the same amount of battery ? Or is it just calibrated numbers by SR that don't mean much ?

"the relentless pursuit of the perfect rom "
[Samsung Galaxy Nexus] cancerouspete:
Roughly, more Hz=more drain at same voltage because it is doing more work per second

--gnex toro bb 4/9 4.0.4--
[Samsung Galaxy Nexus] phydo:
Woo. Trying this one out. I had better stability on 160 than 157/158 but ultimately ended up back on a more stable kernel. Let's hope this is better. Thanks Franco!
[Samsung Galaxy Nexus] LothianScykle:
Flashing now - Thanks, Franco. Please accept this donation, and have a beer (or 2) on me :)

~
[Samsung Galaxy Nexus] fix-this!:
franco i see you mention something about increasing voltage for wifi. does your kernel control voltage for the radios as well? i was having serious signal issues yesterday and im curious if your kernel plays a part in that or not? some say kernels can affect radios and some say it doesn't.
[Samsung Galaxy Nexus] phydo:
5 hours uptime no lockups on r161. We're getting there!
[Samsung Galaxy Nexus] TEK112:
I am starting to question the kernel affecting the radios myself. Ever since 158 I have had weird occurrences where the signal will drop from 2 or 3 bars to zero while I am on a call and my bluetooth will turn off and back on. This happens simultaneously. Anyone else?
[Samsung Galaxy Nexus] Gahh Its Lee:
I've had some issues...
[Samsung Galaxy Nexus] laureanop:
Quite frankly I don't know what to think anymore. Between Samsung s poor radio quality ( that's two phones now :this one and the fascinate ) and vzw s network woes is kind of becoming an issue.

Yesterday I set my voltages to what sr was telling me. In areas where it didn't before , my signal started dropping to 1x . The problem went away when I went back to stock voltages.

"the relentless pursuit of the perfect rom "
[Samsung Galaxy Nexus] jbdan:
If the kernel affected the cell/wifi radio couldn't one just run the stock kernel for a few days and see how it compared? Or what about all the people who do run stock and know nothing about rooting a phone and have signal issues? idk just thinking out loud
[Samsung Galaxy Nexus] fix-this!:
It could be the voltage settings causing issues. I mean i know this phone has weak radios but the past few days for me dropping to one bar is highly unusal. My rezound had a constant 3 bars. I guess it could be rom related too. Ive heard aokp and cm9 can have lower signal for some reason.
[Samsung Galaxy Nexus] djd338:
I've noticed the same lately, more than normal it seems. Bluetooth drops away, bars flux wildly. Had a call drop yesterday, but that's Ops-Normal for Verizon here. I always blame it on Verizon. Don't know. Maybe Franco will chime in here with his thoughts? With Verizon on Samsung radios we need all the help we can get!
[Samsung Galaxy Nexus] suprafreak1000:
Thanks for the kernels franciscofranco!

On 156 currently and everything's been great, appreciate the work.
[Samsung Galaxy Nexus] Amphibliam:
Really weird, not really an issue, but pretty funny. When I turn my phone screen off for like 10+ minutes, the battery goes up between 1-3%. I don't know why, but amazing battery life on this with Liquid.
[Samsung Galaxy Nexus] Sveke:
Sounds like you need to do some trouble shooting...I've never had a lock up on any of Francos kernels and have been using them as my primary kernel for months.

What do you mean by lock ups exactly?
[Samsung Galaxy Nexus] fix-this!:
had the same happen here on aokp.

---------- Post added at 09:58 PM ---------- Previous post was at 09:21 PM ----------

fyi.. ogdobber confirmed that the kernel does in fact play a role in radio/signal strength. if you don't know who he is, he is the james bond kernel dev.
[Samsung Galaxy Nexus] sway40:
It's been doing that too me since milestone 2, battery would be 58% turn it off and back on a lil later it would be at 60%.

~ Sent from my GNexus on Aokp ~
[Samsung Galaxy Nexus] TEK112:
It doesn't actually calculate real battery usage left, but through a mathematical formula whereby usage is calculated based on battery capacity and voltage. If you are beating on the phone or are using a higher clock speed and then turn the device off, the last percentage you see before it sleeps is the estimated usage based on the current draw. However, when you let it sleep it equalizes and when it wakes it is basing the calculation off of nominal usage giving you a more accurate % which actually may be higher than the previous estimate.

Just like a vehicle that calculates MPG while driving. If you get on it the mileage will go down, but when you let it settle and drive normally the MPG comes back up. The same correlation can be made to the battery as you really don't know what usage you will get until the "tank is empty."
[Samsung Galaxy Nexus] Amphibliam:
I'm using m3. Should I try r161? I tried 160, but it drained the hell out of my battery.
[Samsung Galaxy Nexus] sway40:
I knew that!!!

~ Sent from my GNexus on Aokp ~
[Samsung Galaxy Nexus] franciscofranco:
r162

* Fix USB bugs introduced on r161, specially losing ADB on screen off and some other perks that are now fixed

* Corrected compiler flags

* Removed generic_hotplug and hotplug governor for good as we don't need this anymore. The system does its power management by itself, including shutting down cpu1 during screen_off if it thinks its a good idea. (note to self: open my eyes when reading dmesg logs)
[Samsung Galaxy Nexus] phydo:
Has anyone had the phone randomly reboot to get stuck on the CM boot animation? Not sure about in 162, but it's been happening for 160 / 156
[Samsung Galaxy Nexus] snubs:
Running 162 now, smoothly, but the newest version of the app is not any saving my "set at boot" choices.
[Samsung Galaxy Nexus] BigBake88:
Interesting. R160 has given me some of the best performance/battery life I have experienced yet with my GN. Did you have any bad wakelocks that you know of?
[Samsung Galaxy Nexus] LothianScykle:
Flashing this one now. This would explain all those CPU1 Shutdown/Up messages we were seeing in my logs, right?

~g
[Samsung Galaxy Nexus] Sveke:
Are you undervolting?
[Samsung Galaxy Nexus] phydo:
yeah. not a ton though. it happens like once every day or two
[Samsung Galaxy Nexus] Sveke:
I would advise to give up on that and let smart reflex do its job. I tested for months and was hooked on undervolting and then realized that it didn't help at all and my battery time was nearly identical.

Smart reflex is straight, try it, bet your issues stop.
[Samsung Galaxy Nexus] phydo:
Thanks for the insight. I'll try it
[Samsung Galaxy Nexus] LothianScykle:
Is Smart Reflex a generic Android kernel thing or a Franco kernel thing?
[Samsung Galaxy Nexus] gnexdude:
Not exclusive to Franco's..
[Samsung Galaxy Nexus] Shamrock13:
So.. apparently, the latest nightly (162) makes me unable to plug my phone via USB. It's coming up as an INTF2 device and no matching driver found so it's not installed.
[Samsung Galaxy Nexus] spinkick:
Do you have fast charge enabled by chance?
[Samsung Galaxy Nexus] Sveke:
Do you have fast charge enabled?

Edit: damn it, ninja'd
[Samsung Galaxy Nexus] sway40:
It's not, do you have it enabled? It's you have it enabled...turn it off and your golden.

~ Sent from my GNexus on Aokp ~
[Samsung Galaxy Nexus] Amphibliam:
Battery is draining a bit on the latest. Anyone else have any ideas?
[Samsung Galaxy Nexus] laureanop:
I need someone to clarify the following for me : does SR actually set the voltages or does it suggest how low it thinks they can go ?

"the relentless pursuit of the perfect rom "
[Samsung Galaxy Nexus] kingoanklebreakn:
It sets them.
[Samsung Galaxy Nexus] sway40:
Considering it just came out, let it settle. Run your phone normal just let the battery run down and should be ok after a charge or two. This is only if it's not a rogue app, or something else causing it. Still needs time to settle in though.

~ Sent from my GNexus on Aokp ~
[Samsung Galaxy Nexus] raphenucleus:
Specifically, it's a Texas Instruments OMAP processor thing (which is what the GNex uses).

Well it depends on which version(s) of SmartReflex the kernel has enabled (e.g. class 1.5 vs. class 3), but on most kernels including franco's it actually sets them to the suggested values.
[Samsung Galaxy Nexus] Shamrock13:
I noticed that too. Specifically out drains when the screen is on even if it's for one minute or a second. Goes down usually two to three percent in about minutes, but it is a random percent and doesn't look to matter what I'm doing.
[Samsung Galaxy Nexus] phydo:
My battery life is phenomenal on 162. Like ridiculous
[Samsung Galaxy Nexus] Amphibliam:
To me it seems like people's phones love this kernel or hate it. There are people like the guy above me who are like ZOMG mai batri lastz forevarrr. Then there are people like me who are like OMGEEEE my batt suxorz why this kernal sux so b4d. I haven't heard of many people who say "meh".
[Samsung Galaxy Nexus] dspcap:
Loaded 161 yesterday and wondering if this is normal. When I went into CPU Spy this evening, I noticed that 86% with 384 mhz and only 2% with Deep Sleep. Is this normal for this kernel?

Loaded 161 and I have Hotplug checked
[Samsung Galaxy Nexus] TEK112:
You should flash the latest which has the hot plug option removed and sort of enabled by default. However, if you want to stay on 161, reboot to recovery and wipe both caches. Your phone will then sleep.
[Samsung Galaxy Nexus] dspcap:
Are you suggesting flashing the latest stable? What does sort enabled by default mean? I really need to read this thread more often

Edit... I see you are referring to 162, I just flashed it. So what is sort of enabled by default mean?
[Samsung Galaxy Nexus] TEK112:
If you read the change log you will see that he removed hot plug. Then he mentioned that he built it into the ROM because he sees it as a benefit. Therefore hot plug is enabled, but not under the strict guidelines the old hot plug was. I'm sorry I can't be more specific, then again, Franco wasn't that specific with the changelog.
[Samsung Galaxy Nexus] dspcap:
I follow you now, thanks.
[Samsung Galaxy Nexus] Amphibliam:
I get good battery with 162 but not the amazingness as far as I can tell. I have the OEM 2150 mah battery and with 4 hrs off charger and 1 hr 10 min screen on I'm at 70%. I've been on WiFi the whole time. Is that good?
[Samsung Galaxy Nexus] TEK112:
Yes that is good. Stupid life is 4 hours and normal is 2.5 ish. You're projecting more than three hours so that to me is good.
[Samsung Galaxy Nexus] hyp3nitis:
Im on 156. I used the power save. data off when screen off. No wifi brightness 5%.

Sent from my Galaxy Nexus using Xparent ICS Blue Tapatalk 2
[Samsung Galaxy Nexus] sway40:
I can officially say 162 isn't mind blowing, but I haven't seen anything like that since m3 and before. Im starting to think it's the higher gpu causing more battery usage, anything m3 and before I was getting 4hrs on seen time and close or over a day of battery. I haven't seen anything close to that after m3 except for I think 156 where I got a day and 3hrs screen time. That's really the only thing that's changed consistently is the higher gpu...and im talking about 384, I don't use the other one.

~ Sent from my GNexus on Aokp ~
[Samsung Galaxy Nexus] Sveke:
I'm on pace for 4.5 hrs screen on on 162 512 version. Stock battery
[Samsung Galaxy Nexus] Amphibliam:
I'm using 384 gpu and to update my post above now about 7 hrs off charger, 2 hrs screen on 51%. #winning
[Samsung Galaxy Nexus] sway40:
Well im out of ideas, I guess I'll just go back to m3...the higher gpu is useless anyway if that's even the reason. I know every phone is different but there hasn't been one nightly to come close to this, my settings and usage haven't changed either. Maybe it's the rom, who knows. Maybe my phone just sux but it's funny I got this right before m3.

~ Sent from my GNexus on Aokp ~
[Samsung Galaxy Nexus] sway40:
Im just in a complaining mood I guess. Kernel is great, it just seems it's lost that great battery it had before.

~ Sent from my GNexus on Aokp ~
[Samsung Galaxy Nexus] Metallice:
No that's not really right. Also not sure what "ROM" you're talking about?

It turns out there was some hotplugging going on by default. If you look at dmesg you can see it shutting down and turning on CPU1 by itself.

Franco didn't have to "add" anything in. My galaxy tab 2 with the 4430 does the same exact thing on the stock kernel. Same dmesg's and everything saying shutting down CPU1 etc. on all govs and configurations.
[Samsung Galaxy Nexus] TEK112:
Good pickup.

I really need to do a better job proofing my voice to text. Then again, it was late and I was drinking. I can't really be expected to type it myself through tapatalk...lol

Apparently it thinks "it" is "he." Also, sees should be seen.

It should read:

"If you read the change log you will see that he removed hot plug. Then he mentioned that it's built into the ROM because it's seen as a benefit. Therefore hot plug is enabled, but not under the strict guidelines the old hot plug was. I'm sorry I can't be more specific, then again, Franco wasn't that specific with the changelog."

The ROM I am talking about is any 4.0 ROM.
[Samsung Galaxy Nexus] Metallice:
No worries. Just wanted to clarify as I am unfortunately not drinking due to finals. And its not really the ROM or any thing ROM related. Dmesg is where you have these messages, and dmesg is for the kernel. If you could pop a Cupcake ROM on our phones with the stock ICS kernel youd still see the second CPU offlining. As I said my touchwizzed gtab exhibits this same behavior. It was just already part of the kernel.

Sorry to be such a pain when it comes to the details. :)
[Samsung Galaxy Nexus] dspcap:
Just had something weird happen. Woke up from my phone charging all night and the battery was at 77%. That's not right.

Unplugged and plugged it back in, while typing this post, I am now at 80%.
[Samsung Galaxy Nexus] TEK112:
No worries. I appreciate the education. What ROM are you running on the gtab?
[Samsung Galaxy Nexus] cancerouspete:
I'm losing wifi and data at times while phone is asleep, only occurred after going from 161 to 162

Been using 384 gpu and using the balanced profile

--gnex toro bb 4/9 4.0.4--
[Samsung Galaxy Nexus] laureanop:
Francisco: will you be implementing the sched changes you've been discussing with ch33ky in your next release? It sounds like a great find for UI responsiveness.

"the relentless pursuit of the perfect rom "
[Samsung Galaxy Nexus] fix-this!:
yeah i had alot of signal problems when using this kernel too.
[Samsung Galaxy Nexus] droidholic:
Same here. I was tethering and my computer kept losing connection after a few times. While I like to save battery, I would much rather have a reliable connection. Great work, Francisco!
[Samsung Galaxy Nexus] Metallice:
Mostly CM9 but sometimes touchwiz... its like the Gnex's big brother. Both Omap4 at 1350mhz, both running ICS AOSP, both Samsungs, same color backing and front etc. But one's for textbooks, lecture powerpoints, and Netflix, while the other's for phone calls. Its too bad there's no FrancoKernel tho. But hey its a great purchase for $220.
[Samsung Galaxy Nexus] flytechguy:
Completely lost data permanently driving home tonight. Does seem to have a problem. Wouldn't come back after a cache flush either.
[Samsung Galaxy Nexus] Amphibliam:
Hasn't happened to me on 162. If it does, it's an excuse to try out Popcorn Kernel.
[Samsung Galaxy Nexus] exzacklyright:
SO i just got this BEAUTIFUL phone... after 4 hours.. got everything set up how I like.. I'm running this kernel with liquid 1.4

1stly, How do I customize it? What settings should I use? I'm mostly aiming for good battery life. Thanks.
[Samsung Galaxy Nexus] wayneb02:
It really differs phone to phone. Main thing seems to be to lower your screen brightness

Ooh and u should purchase the kernel app to make everything easier and to donate to Francisco..if u haven't already
[Samsung Galaxy Nexus] grinch247:
http://xdaforums.com/showthread.php?t=1447757
[Samsung Galaxy Nexus] jameslfc5:
Thanks I posted here hoping someone would point me in the direction of this thread as I'd forgot where I had seen it :)