yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] schizophrenia:
just did an idle testing

just did an idle testing

a bit more than 6 hours, dropped from 100% to 82%

the phone was at 85% deep sleep and 8% 192mHz (as shown on CPU spy screen shot)

config: AOKP M5, franco 152 min 192 max 1344, Lazy governor, Undervolted as shown on screenshot, Smartreflex ON, Generic hotplug off, Logger off

Kernel wakelocks and Partial wakelocks shows no significant events which is in line with the phone sleep state.

all 6 hours was on Wifi and it was no more than 6 feet away from the wifi router

anyone has any idea how does the battery drain so fast even in idle?? what was draining it?

It used to be 100% > 76% after 12+ hours when on "wifi idle" in some older version

Is "the battery is almost dead" the only reason now?

franco you reminded me before to post the kernel wakelock so I am attaching it too this time. thanks

update: 76% battery left after 8.5hours .... did not touch the phone except screen cap and battery check

i posted in Google plus too

https://plus.google.com/104818049704682891678/posts/Xy95zWrRZTW
[Samsung Galaxy Nexus] Meannekes:
sry if i´m a little bit rude..

but you should think before you post something.

i don´t know why you have such a high drain, but

it doens´t matter what you set at the UV section because you have SmartReflex ON

Set it to 10mV ;) you should try it :D

all i know is, AOKP has not the best batterylife, i get the best batterylife with ARHD + Franco r152 (but ARHD has less customization ability :/ )

(after 6-7 hours most in deep sleep i´m on 98%~)

sry for my poor english
[Samsung Galaxy Nexus] schizophrenia:
not rude at all.. it's ok

in the post i did not emphasize the UV part actually. I am well aware of what SR does so I posted the fact I did the UV so that someone can remind me if I did something wrong. (previously I tried UV with SR off, but later on I decided to turn it back on and thus the UV)

back then when I was some earlier version of franco with SAME AOKP I was able to get from 100% > 76% after 12 hours wifi idle (as mentioned) so I am actually trying to compare apple to apple.

I am not blaming the kernel nor AOKP (nowhere to blame these great products) but I am just trying to collect ideas on how would such drain happens on even Idle.
[Samsung Galaxy Nexus] ArmanUV:
LMAO That first sentence killed me :D

And I totally agree.
[Samsung Galaxy Nexus] superbobup:
I had this issue recently with LS 1.3. For some reason, I went from 2% drain overnight to 15% BBS usually showed no odd wakelocks...however, during 1 of the 3 nights I had this issue I had an odd kernel wakelock as shown:

"BT LowPower" (): 8 h 29 m 17 s (30557 s) Cnt:(c/wc/ec)0/0/0 99.8%

I ended up wiping and installing LS 1.35, and now no more issues

EDIT:

I think my issue occurred on r149, not completely sure though
[Samsung Galaxy Nexus] RayGarden:
I have been reading a lot lately. Most people are asking the same questions:

* what is the best ROM

* what is the best Kernel

* what is the best combination in order to have a good performance and good battery life

People ask if the Developers can compare this, compare that etc etc.

I am convinced that you Only can do Real Comparisson with Clean Devices which means, having:

* 2 brand new Gnex Devices

* use equal Root Procedures on both devices

* use equal Bootloader, Kernel and ROM on both devices

**** NOT installing additional Apps

From there you can try different Settings in order to compare both Performance and Battery Life.

1 single app can have deep impact on overall performance / battery life

Please trust on the developers !

THANK YOU
[Samsung Galaxy Nexus] jcpq:
What is the best method?

Flash rom

Flash gapps

Flash kernel

Reboot

or

Flash rom

Flash gapps

Reboot

Flash kernel

?
[Samsung Galaxy Nexus] mskip:
It doesnt really matter. I always do the former but thats just my preference and dont forget to wipe first to avoid complications.

Mark.
[Samsung Galaxy Nexus] coolzjai:
My Favorite way and all these while acting good.

1. boot recovery

2. wipe cache, wipe dalvik cache

3. wipe factory data (if you come from other custom rom, or feel like want to have a clean install)

4. flash new ROM

5. flash GAPPS

6. REBOOT

7. Restart into recovery,

8. wipe cache, wipe dalvik chche

9. FLASH KERNEL (if the build-in one not your preferred mod)

10. reboot & done.
[Samsung Galaxy Nexus] CommanderDuplex:
@franco

had a boot of death in the morning

the device reboot fromself and don't boot anymore , after a "re-flash" and 5min later the device started but i can't open the apps anymore ...

send you the Crash-log

Edit:

used the 152 Kernel

512mhz GPU and 1344mhz CPU undervolted with setting that i use around 2month (so it shouldn't are the fault )
[Samsung Galaxy Nexus] RayGarden:
AGREE. Never have had problems.

additionaly....maybe a good tip; when you check "Making Backup on Google Server + Automaticly Replacement" (in Settings -> Back-Up), you can do a full wipe but never loose your most important information like WiFi Passwords, Apps (previous installed) etc as soon you have flashed new ROM
[Samsung Galaxy Nexus] Emilius:
I am in the same position. Over night battery drain is more then 6% with 152. I can hardly go true whole day. I did not check 135 but with 121 I am getting excellent results. Charging every 2nd day with only 1% drain over the night is not bad. I mention this 2 times already but seems no one care about that anymore. To bad ;(
[Samsung Galaxy Nexus] mikespe:
Normally I always have fantastic battery life with Franco's kernels & I always recommend them when people ask on the message boards. But it seems the last 2 updates my battery life has gotten much worse. I haven't added any new apps so I can't blame app wakelocks since i never had them before the last 2 kernel updates. I took my phone off charge this morning at 6am and now at 7:13am I am already down to 85% with only 5min of screen time on. Maybe these last 2 updates need different settings than what I had but I always run 1228/384 generic hotplug checked, no voltage mods...I just switched to the latest stable version to see if that makes a difference...
[Samsung Galaxy Nexus] coolzjai:
i get almost 1h alarms wakelock after 11h standy.

wakeups: 126

intent: com.android.internal.telephony.gprs-data-stall

googling around, like no answer yet from the BetterBatteryStats developer himself.

any clues?
[Samsung Galaxy Nexus] :
init.d scripts are not working!

Im running MIUI v4 2.4.27 which should support init.d ?!?!

Even with other Kernels such as trinity it doesnt work...

/system/etc/init.d/

rwxr-xr-x root root S80_myscript
[Samsung Galaxy Nexus] franciscofranco:
Thanks everyone for the feedbacks.
[Samsung Galaxy Nexus] schizophrenia:
looks like I am not alone..... hmmm
[Samsung Galaxy Nexus] loudaccord:
check your alarms in BBS... my email was waking up my phone a bazillion times. Not kernel related.
[Samsung Galaxy Nexus] schizophrenia:
as I posted all those screenshots with partial wakelocks and kernel wakelocks.. there were no funny wakelocks plus you can see from my battery graph my phone was actually sleeping very well..

so it was not apps related.

http://xdaforums.com/showpost.php?p=25607962&postcount=14547
[Samsung Galaxy Nexus] jhericurls:
Every morning at 8am I unplugged my phone and logged my usage at 2pm

Kernel - 140

74% - 1 h (battery-screen time)

Kernel - 151

76% - 1h 8m (battery-screen time)

Kernel - 152

76% - 1h 7m (battery-screen time)

Kernel - Trinity

75% 1h 13m (battery-screen time)

So from my findings, all the kernels perform about the same. I can get about 4 hours screen time from a full charge.
[Samsung Galaxy Nexus] aquavalanche:
I had plenty of gprs wakelock, but no juice drain as other said.. have been using r152 with 512 gpu.. 192 mhz-1ghz with a bit of UV.. so far my phone was unplugged 12 hrs ago, with 1 hr 40 mins screen time.. now the battery still 67%..
[Samsung Galaxy Nexus] schizophrenia:
very good for both of you

actually like i said I am not pointing the problem to the kernel, dont take me wrong

instead, I am actually asking if someone can help me with finding out whats the culprits that have been draining up the battery even if it is sleeping well.
[Samsung Galaxy Nexus] Emilius:
same here. My phone is sleeping well but results are so different. Same rom just simply flesh other kernel and the problem go away. No idea what else can produce this problem.
[Samsung Galaxy Nexus] aquavalanche:
Did you check on cpuspy, what cpu step are your phone mostly on?

Once I had a super heavy battery drain, like 30% for 2 hours on idle.. but I found out that it happenned after I played some games.. after reboot the device, it all gone..
[Samsung Galaxy Nexus] loudaccord:
I saw that... you didn't post the screenshot of the "Alarms"... it's one of the options along with Kernel and Partial wakelocks.
[Samsung Galaxy Nexus] CaspaTheGhost:
Ah, I see! It sounded like you were referring to it actually being set on boot, think it may have been a language issue.

Like others have said, I would enter a different value, save, then go in again and change to your required value.
[Samsung Galaxy Nexus] schizophrenia:
thanks for helping

this is my original post

http://xdaforums.com/showpost.php?p=25607962&postcount=14547

as you can see from CPU spy, it is 85% deep sleeping and the rest are just 192mHz, I believe those are just email and stuff.

So like i said the drain is not caused by significant wakelocks

---------- Post added at 10:23 PM ---------- Previous post was at 10:20 PM ----------

my apology.

i was not aware of that option "alarm" as no one really posted it before

I did not screen cap it.. damn
[Samsung Galaxy Nexus] franciscofranco:
Just for the record I left my GN idle for 20 hours and 8% drain only. GSM is enabled since I have several SIM cards.
[Samsung Galaxy Nexus] leelaa:
Hi Franco, 152 running great for me. O have gone back to stock imm76i for better battery life.

I love custom rom but they don't compare to stock in terms of battery.

And your kernel + stock= great battery and performance. I would rather have those two over customization any day.

Will we be expecting a new nightly any time soon?
[Samsung Galaxy Nexus] schizophrenia:
thanks for the comparison..

for mine, if on 3G data and unused at all, it can't even last for 20 hours

any suggestion what is the problem with mine from just looking at the data provided?

http://xdaforums.com/showpost.php?p=25607962&postcount=14547

appreciate any help / insights from anyone
[Samsung Galaxy Nexus] Gahh Its Lee:
Serious question my friend just pointed out minimalist kernel is on 3.0.29 and were on 3.0.8. Any real reason why?
[Samsung Galaxy Nexus] danielvc:
you have all kinds of ****ty things in your statusbar (temp etc.) and imap is taking up a lot of battery. Maybe poll your emailaccounts less. Also, don't let Google+ sync. Just let Google sync your email (if you use gmail), contacts, calendar (if you use it) and nothing more.

mipi_link is related to camera, can be used maybe with Google+ and Talk. Can you please stop the services and check again?
[Samsung Galaxy Nexus] Emilius:
Can you please do the same with 121 kernel 384 GPU. Should be no more then 3% for 20 hours.
[Samsung Galaxy Nexus] jhericurls:
There is something wrong with your device or apps. I think its time for a scotched earth policy, nuke that software from obit and do a clean reinstall.
[Samsung Galaxy Nexus] aquavalanche:
i still don't get how it could happen..

My device get like 1% drain an hour when i get to sleep.. never below that..

Do you have IMs installed?
[Samsung Galaxy Nexus] nklenchik:
Because that's what the boss man wants haha
[Samsung Galaxy Nexus] RayGarden:
AOKP M5 - Franco Kernel Nightly 152

Not bad i think
[Samsung Galaxy Nexus] deezid:
Something like voodoo control would be indeed very nice :D

My screen still has a yellow tint (medium grays to white) and magenta tint (dark greys). Hope it will be possible to fix this issue in near future :)
[Samsung Galaxy Nexus] franciscofranco:
supercurio François Simond

@

.@sakiss yea #GalaxyNexus will get the #VoodooSound treatment. Louder too, but more noticeably with sound quality improvements. No ETA.
[Samsung Galaxy Nexus] razzbaronz:
Thank You!

Franco, thanks so much for your hard work! We really appreciate your time and are loving the results!

I am using this as a base for Open Kang Milestone 1 build for CDMA. In case anyone is curious, this has been working well for me today:

1200MHz 1100mV

920MHz 1000mV

700MHz 900mV

350MHz 800mV
[Samsung Galaxy Nexus] jankyboy:
Fantastic ROM! I'm running nightly 6 UV with AOKP Milestone 1 and UGKK7 radio. My GN flies and has pretty decent battery life.
[Samsung Galaxy Nexus] :
is it normal for this kernel to cause lag when waking up phone (unlocking phone) ?

it runs smooth everywhere else except lockscreen.
[Samsung Galaxy Nexus] jhericurls:
I used the music player while the screen was off and didn't experience any stuttering.

Having 180mhz is the ultimate battery saving in idle mode, you don't need that much horse power to sync emails.
[Samsung Galaxy Nexus] franciscofranco:
Please, don't give false information, or please search before talking :)

In idle mode the CPU's are power collapsed, meaning the frequency that they are running doesn't matter ****, they are dead. Like I said before having such low frequencies cause more wakeups from idle per sec than higher frequencies, it's a known fact that I've defended in every device I worked in, and in the end I was always right about this. I'm currently running with 700/1200, I find 350mhz too low.
[Samsung Galaxy Nexus] eRode:
Neither vpn nor cifs ever worked in all the builds so far since inception. Franco can you please kindly test them before claiming them as features?
[Samsung Galaxy Nexus] skyhigh2004:
Really love the new nightly. I gotta switch out again though, your kernels just chew through my battery. Smoothest ive tried period though.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] ancostel:
I've just experienced something weird...idk if it's kernel related or not, but I thought I'd posted it to see if I'm the only one...running on romanbb's xrom since christmas day with franco's #5 w/o any problems...just now my soft buttons dissapeared while I was browsing the market...I couldn't get out of it lol...restarted and it's all good now...anybody else had the issue? btw I'm on franco's #6 w/ the same rom for about 7 hours by now...
[Samsung Galaxy Nexus] altimax98:
Franco -

I wanted to thank you for this awesome kernel. It is by far the best kernel for the phone, and I have a 100% more awesome opinion of you after reading that blog you posted up. I too feel like you do about how this (android in general now) has gone downhill, and I love the way your not taking crap. Keep up the awesome work, and thanks for the awesome kernel!

-Daniel
[Samsung Galaxy Nexus] franciscofranco:
Yes, I guess the old insmod isn't working correctly with this kernel modules.

You gotta give it 2 or 3 charging cycles after installing a kernel/rom...
[Samsung Galaxy Nexus] :
this seems to be an issue with Roman's rom, this happens to me as well on the TORO (lte) version
[Samsung Galaxy Nexus] beekay201:
nice. if it's not already, that should be the first rule for ALL FOSS related projects. great to see supercurio to drop some tuning to these devices (since G&S decided to place the speaker, and from a personal perspective, once again, in the backside of the device. which is pretty useful to listen to music, show a video that has audio in it to someone..etc etc.

seems to me that your cpus spend a whole lot of time on 350 and 180mhz. 2h+ spent on each? 700/920mhz ain't seeing much action too, are they. i think if i set my device's cpus to 1200mhz ONLY i might have better deep sleep than that.

damn, those email syncs are really messing with your battery life man. what do ya carry in there? massive email notifications from a quazillion different forums and rss feeds? :D online banking? are you by any chance a workaholic?

edit: About the TUN module, are you guys also having trouble getting modprobe loading it?

edit2: forget it, just saw francisco's previous post.

edit3: read something about tun needed being built as a driver, not as a module? curiosity drives me.
[Samsung Galaxy Nexus] aron7awol:
Do you know or have a theory as to why this is? I don't dispute it to be true, but I can't think of a logical reason as to why it would be. If the CPU is power collapsed and in deep sleep, why does the frequency it was running at before it went to sleep make a difference?
[Samsung Galaxy Nexus] irishrally:
6406 on AnTuTu ... just for fun.
[Samsung Galaxy Nexus] skyhigh2004:
Yes to be perfectly accurate. But I mean 20% in mins as compared to 5% on stock. I'm not knocking your kernel at all its just it has higher drain then what I can use as a dd. Every single custom kernel for this phone has this same battery drain for me. So its not just yours.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] beekay201:
on aosp or aosp-based roms, stock kernel does not and will probably never have the performance of custom kernels. it's a like a trade. with better performance, comes higher battery consumption, i think we all agree on that? it's even true for vendor-roms vs aosp-roms, but that's just offtopic.

/me sent this from a i9250 using Tapatalk

edit: just noticed (not usually so high, so i thought i'd report back)

anything unusual, or has it always been like so, it's just that i'm too damn ****ing blind to see it? :D
[Samsung Galaxy Nexus] triStateMindgate:
Hands down the best effin Kernel for the GNex period. Thanks Franco for all your hard work.

Currently running:

1100

950

850

750

Give it a day or two, but so far all butter.....
[Samsung Galaxy Nexus] skyhigh2004:
No I completely agree it is a trade off.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] loudaccord:
the only way I could do that is if my phone were off lol :) I'm convinced the CDMA version hates batteries.
[Samsung Galaxy Nexus] sing1gnis:
No doubt.
[Samsung Galaxy Nexus] schizophrenia:
I'll try to run it without any sync tonight and see.. thanks

but i just had a very clean installed less than a week ago

but i may do it again then when i have more time

thanks
[Samsung Galaxy Nexus] Emilius:
Last night my phone was on 85%. After 5 hours when I pick up the phone was still on 85%. Thats's is 121/385 kernel on Paranoid Android rom. If I do same thing with 152/385 it will drop for 6-8%. I will take a screenshot and post it here. Also for daily usage 121/385 is way better. Like I sad before I can go true 2 days. No way to do that with 152/385.

Just take a test for one night. Flash 121/385 and check it out. With same rom and same apps installed you will see this huge difference. :o)
[Samsung Galaxy Nexus] mikespe:
As I posted earlier I had a 15% drop in battery in an hour. By the 2nd hour it dropped another 10%. I decided to switch to the Stable version (Milestone 3 I believe) just to see how much is kernel related. I kept All the other settings the same! In 4.5 hours my battery has only dropped 13% with 20min of screen on time...I only had TEN MINUTES of screen on time when the battery dropped 25%!!!

Now I understand that some versions of various kernels/roms affect phones differently. PLUS some of you have the GSM version and others have the CDMA version...apples & oranges. Even if we have the SAME EXACT PHONE they could act differently. It frustrates the hell out of me when someone post an issue they are having and someone replies "Well my phone is fine so it's not the kernel/rom". I have NEVER complained about battery drain while using Franco's kernels. And even with the last version I didn't say anything because I figured the next version would act differently. I know schitzo and a few others mentioned that they are also having battery drain issues. SOMETHING has changed in the last 2 versions to at least cause a FEW phones to not like the changes. And the fact that I went to the stable version of the kernel and the problem is gone tells me some setting within the newer nightlies is the culprit.

People need to stop taking it so personally when someone has an issue...we are just reporting how OUR phones are reacting. In some cases it IS an app on the phone. But in others it is the chemistry between the kernel/rom & the phone.
[Samsung Galaxy Nexus] danielvc:
LOL. 2 people in total. Nice. Franco: the kernel rocks as always. All those weird addons/settings/apps that causes the drain: the majority doesn't have it. And it's ok to adress, but give some more info.
[Samsung Galaxy Nexus] schizophrenia:
no offensive

but you call "beautiful widgets", "google sync" etc weird?

you use your "smart"phone just for phone calls and web browsing? alright

and mind that i never complained. i wouldn't have bought the app if I think the kernel is no good

i was merely asking for help to dig out the culprit
[Samsung Galaxy Nexus] danielvc:
I'm just saying that disabling the syncs/widgets etc. and then check if the problem still persists, is a great option to check for the rogue app. Disabling Maps/Facebook GPS/Google+ and only let it sync when I need it, have improved my battery life. I don't want 5 hours of screen on time, but 3 with all my constant syncing is great for me.
[Samsung Galaxy Nexus] schizophrenia:
thanks, i will be sure to do that as well... thats constructive suggestions yes

but you also added "All those

weird

addons/settings/apps that causes the drain"

anyway. i am nuking the phone once more
[Samsung Galaxy Nexus] Bram77:
Battery life is very good using 192/1384 Gpu @ 512. The last two hours with 1 only core active. Great work Franco! Thanks
[Samsung Galaxy Nexus] schizophrenia:
mind sharing which governor you are using? Hotplug? as you said only 1 core was active

thanks
[Samsung Galaxy Nexus] CommanderDuplex:
Franco could you please add the Temp. Control like Glados ?
[Samsung Galaxy Nexus] yoncy:
There are to many changes between milestone 3 and nightly 152 ? I cannot watch Fraco's commits. Why i'm saying that because it was nice if i would have milestone 3 patched with the new software color control. I'm not sure if this is possible. Milestone 3 it's the most stable.

Edited sorry :)
[Samsung Galaxy Nexus] franciscofranco:
I don't know, I have to think about it.

Where is Milestone 5?
[Samsung Galaxy Nexus] aquavalanche:
Thanks for the suggestion.. gonna try it starting tonight..
[Samsung Galaxy Nexus] aquavalanche:
Lol.. i bet he got mixed with aokp
[Samsung Galaxy Nexus] franciscofranco:
I know, I was joking around :)

Ok, I got fed up of these experimental OMAP4 and omapzoom patches, nightly goes tonight without all that crap just like we had on r121 and r133, compiling as we speak.
[Samsung Galaxy Nexus] Timmyfoxeh:
Awesome, I'm excited! *Spams F5*
[Samsung Galaxy Nexus] Bram77:
I'm using Franco's app so I can enable stuff you can't use without it.

Govenor: ondemand

Min/max cpu: 192/1344

Gpu: 512

Generic hotplug: enabled

Cpu Mode: Dual core

I thought I had single core mode enable. Apperantly not... I'm testing that now.
[Samsung Galaxy Nexus] yungboss22:
I need help :(
[Samsung Galaxy Nexus] Meannekes:
my Battery drain is much higher on nightly 152.. i used Milestone3 before.

don´t get me wrong, nightly 152 has a very good battery life too, but not as good as Milestone3

both are very smooth, no lags at all!

Thanks for your great work, i bought your app too

(and sry for my poor englisch)
[Samsung Galaxy Nexus] -viperboy-:
You guys gotta give kernel testing more time. You can't just base performance off of 3 hours of flashing a new kernel. The other thing I always do when I flash a new kernel is charge the phone to full, wipe battery stats, full drain, full charge. Seems to give me the best battery life and it calibrates the phone so it knows where the max and min voltages are on the battery.
[Samsung Galaxy Nexus] Angelakaro:
Hey guys,i've got som questions:

how is battery with this kernel? (i'm using latest 4.0.4 official update,this kernel will influence battery duration? );

if an official update will be released,i can update my phone easily or i'll need to restore the kernel? thanks in advance!