When I tried 5.0 and 5.0.1 ROMs I had severe battery drain problems, so I went back to 4.4.4
I don't have time to waste flashing a ROM which hasn't solved the battery life issue which many (not all, I know, but MANY) people have encountered in Lollipop.
My question is this: NOT referring to your own personal setup, but regarding the N5 community as a whole - is there still a battery life problem prevalent on 5.0.2 ROMs for lots of people?
A simple yes or no will suffice. Thank you.
No. There never has been even on the L preview releases
Also there is no 5.0.2 for our device
Yes, there are definitely battery drain issues. I am not too sure it's related to the ROMs themselves but rather the radio. I have tried all Lollipop radios with a very basic set up on both stock ROMs and Cyanogenmod. At some point, I will get idle drain in the region of 2-4% an hour - way higher than I would expect.
There are no wake-locks - the device seems to sleep well - it's just idle drain is horrible. Go back to the radio from 4.4.2 and the drain ceases.
If one more person points to the Battery Life Q&A thread I might swear.
is it possible to use that radio with 5.0.1/2?
also:
fastboot flash radio radio.img is the right way to flash this, right?
Sent from my Nexus 5 using XDA Free mobile app
naien said:
is it possible to use that radio with 5.0.1/2?
also:
fastboot flash radio radio.img is the right way to flash this, right?
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Yes, I've not had any compatibility issues with any radio/ROM combo thus far. You can grab the radio image from the within stock factory images here https://developers.google.com/android/nexus/images or go straight to the radio (in both img and flashable zip format) here http://downloads.codefi.re/autoprime/LG/Nexus_5/Modems
For ref, KOT49E is the one I use. Technically this is 4.4.1 but 4.4.2 shared the same one.
The KRT16M the 4.4.2? If so i have a flashable zip if you want it
naien said:
is it possible to use that radio with 5.0.1/2?
also:
fastboot flash radio radio.img is the right way to flash this, right?
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Radios are device-specific and rom-agnostic. You can flash any N5 radio with any rom.
Is it confirmed that the battery life using the old radio is better?
t3al said:
Is it confirmed that the battery life using the old radio is better?
Click to expand...
Click to collapse
There is no confirmation.
There are too many variables, the biggest being location....
What's better for one can be completely different for another.
Test several for your usage and location. You may also find little or no difference as well
If you are still getting 'drain', narrow down the issue by logic: work out what is actually using the battery, they don't drain by themselves. Apply this thinking to any device
eddiehk6 said:
... narrow down the issue by logic: work out what is actually using the battery, they don't drain by themselves. Apply this thinking to any device
Click to expand...
Click to collapse
I believe my issue is poor signal at home on my desk causing battery drain overnight. By flashing an older version of radio will this improve my battery life in anyway?
There is no such "drain" in Lollipop. People just have wakelock issues with their own setup, the same as on KK or any version of Android. They simply put the blame on Lollipop and say there is nothing wrong with their wakelock issues.
[Battery Life Help] Troubleshoot battery issues here!
Lethargy said:
There is no such "drain" in Lollipop. People just have wakelock issues with their own setup, the same as on KK or any version of Android. They simply put the blame on Lollipop and say there is nothing wrong with their wakelock issues.
[Battery Life Help] Troubleshoot battery issues here!
Click to expand...
Click to collapse
It's a little narrow-minded to rule out all issues based on personal experience. My device, with current set up, sleeps like a baby. I don't use location services nor social apps like Facebook. My signal strength is fine.
On a Lollipop radio, idle drain after 1 or 2 days uptime will increase to around 4% an hour. On the radio from 4.4.2, my uptime can be a week or two and idle remains at about 1% an hour, everything else being equal.
Radios don't cause wakelocks, enable location services or install Facebook.
I do agree with one thing though - it's not Lollipop itself causing the battery issues. Some problem is deeper than that.
surrealjam said:
It's a little narrow-minded to rule out all issues based on personal experience. My device, with current set up, sleeps like a baby. I don't use location services nor social apps like Facebook. My signal strength is fine.
On a Lollipop radio, idle drain after 1 or 2 days uptime will increase to around 4% an hour. On the radio from 4.4.2, my uptime can be a week or two and idle remains at about 1% an hour, everything else being equal.
Radios don't cause wakelocks, enable location services or install Facebook.
I do agree with one thing though - it's not Lollipop itself causing the battery issues. Some problem is deeper than that.
Click to expand...
Click to collapse
Radio's are an entire different story.
Different ones work better for different people.
Nor are they Android version related - there is no "Lollipop radio", its just a radio version that will work with any version of Android, and was the latest one so it was packaged with the latest factory images. Again, nothing to do with Lollipop
Lethargy said:
Radio's are an entire different story.
Different ones work better for different people.
Nor are they Android version related - there is no "Lollipop radio", its just a radio version that will work with any version of Android, and was the latest one so it was packaged with the latest factory images. Again, nothing to do with Lollipop
Click to expand...
Click to collapse
Cool. That's why I said "it's not Lollipop itself causing the battery issues".
Lethargy I disagree mainly because there are a few bugs in Lollipop that need work to make it a bit more stable. They have pushed the fixes into AOSP for the ones that have been found but it seems like custom ROMs on Lollipop or a majorly tweaked stock ROM do better.
A lot of it too I think is how poor Google Play Services is with battery. I feel like I have to jump through hoops just to get Google Play Services to behave.
Sent from my Nexus 5 using XDA Free mobile app
MrObvious said:
Lethargy I disagree mainly because there are a few bugs in Lollipop that need work to make it a bit more stable. They have pushed the fixes into AOSP for the ones that have been found but it seems like custom ROMs on Lollipop or a majorly tweaked stock ROM do better.
A lot of it too I think is how poor Google Play Services is with battery. I feel like I have to jump through hoops just to get Google Play Services to behave.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
What bugs are there in Lollipop that affect battery life? Enlighten me.
And what does Google Play Services specifically have to do with Lollipop?
Lethargy said:
What bugs are there in Lollipop that affect battery life? Enlighten me.
And what does Google Play Services specifically have to do with Lollipop?
Click to expand...
Click to collapse
The RAM leak bug: https://code.google.com/p/android/issues/detail?id=79729
It causes app restarts and extra CPU churn.
MrObvious said:
The RAM leak bug: https://code.google.com/p/android/issues/detail?id=79729
It causes app restarts and extra CPU churn.
Click to expand...
Click to collapse
This is the only reason I've decided to go back to 4.4.4 as I'm writing this. I seriously have to reboot phone 5 plus times a day. Ashley every time I get into car and maps loads this is like a instant trigger. Maybe I have to many background tasks idk, but it didn't happen on kk...
Related
Hi there,
So I just flashed this ROM : http://forum.xda-developers.com/showthread.php?t=1474878
It was last night, I hopped that battery issue drain by Cell stanby~Android System would be fix, but it didn't worked for me..
I flashed the ROM correctly, everything was OK. Wiped data/cache/dalvik and even formatted /system.
I don't understand why, my battery is really strange, sometimes I lose only 2 or 3% during many hours, other times I lose 20% per hour (with inactiv use).
I never had battery issue before ICS.
I got a Nexus S i9023, I hope some of you gonna be able to help me, I really want to fix that battery !
Best regards,
SpawN-
flash a rom that doesn't suck your battery! Or try some kernels that helps you to save battery
Yea sure, but this ROM was just here for the problem with battery, so it had to fix the problem, but didn't work for me, that's why I don't understand =/
SpawN- said:
Yea sure, but this ROM was just here for the problem with battery, so it had to fix the problem, but didn't work for me, that's why I don't understand =/
Click to expand...
Click to collapse
sounds like it could be gremlins, or an app app wreaking havoc. also, apps that need to check for notifications drain battery quickly. i usually turn off all notifications(except gtalk/gmail).
I don't have any apps making annoying notifications, my Wifi and 3G are OFF and I often use Task Killer to kill useless processus.
I read that the porting of 4.0.4 for ns gsm was really smooth and battery save
This ROM wasn't even intended for your phone. All bets are off for stability...forget about battery life.
Seriously, though the behaviour you're seeing may not be the ROM. It could be programs keeping the phone awake during standby. To confirm, there's an app called Better Battery Stats on market (and in the Android Development and Hacking section on these forums) that may be able to help you figure things out.
- chris
Hello,
Have you tried to change your RADIO ?
try this kernel *Matr1x* with BLN and voodoo v16.0
http://forum.xda-developers.com/showthread.php?t=1361477
I think it would be help.
For what i've seen the 4.0.4 version was just a leak so there could be some issue/bug. Maybe is better to stay with a custom Rom+kernel and wait for the update or for a custom kernel based on oficial realease 4.0.4 version.
cheers.
The only battery fix in 4.04 was the android os stats being logged incorrectly, i.e. too high.
That has been fixed in 4.04.
I don't think there ever was a cell standby/android system logging bug.
You may be mistaken.
Is it just me, or do the JB ROMs, custom, official, just rooted, etc, get less battery life than the ICS counterparts?
I first had a HOX back in July/August, and used only ICS ROMs. So I have a pretty good deal of experience with it, got about 5.5-6 hours of screen on time every single time.
Now, I noticed a drop in battery life on JB when I had an S3, and just hated the drain. I thought maybe it was just ROM related, and moved onto an iPhone.
Now back onto another One X, and it seems like I still get less battery life than when I had ICS, and I use it the same way.
Has anyone else noticed it?
Sent from my HTC One XL using Tapatalk 2
I dunno, I got 6 hours onscreen last night. Just gotta tune it right. And make maps hibernate. That was eating half the battery.
Sent from my HTC One XL
Your battery is probably depreciating and loosing its full capacity.
Probably not JUST you, but from what I've read and experienced you're in the minority. My battery is definitely better on JB.
I've had much better life on JB, at least since I updated the whole phone (not just a JB rom). I can go almost two days without a full charge.
Hmmm, I'll try a different ROM then. And a JB radio.
iElvis said:
I've had much better life on JB, at least since I updated the whole phone (not just a JB rom). I can go almost two days without a full charge.
Click to expand...
Click to collapse
What do you mean "update your whole phone" ?
Sent from my HTC One XL using xda app-developers app
Misterowl said:
What do you mean "update your whole phone" ?
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
I think he means updated via the stock AT&T ROM, which would include the latest radio.
Misterowl said:
What do you mean "update your whole phone" ?
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
I ran the 2.20 ruu then flashed the 3.18 ota. Once on that base, I've been super stable with CleanROM and Elemental kernel.
My work phone (my HOX) is running completely stock (has to, effing government policies...) and has had terrible battery life since updating to JB. It seems to mostly be due to maps sucking me dry, which I presume is from Google Now. Maps is constantly waking my device and using whatever data connection it can get, which is why i presume the Now stuff. not sure, seems to be fine when i turn off WiFi, so it seems that the wifi use on google now is problematic. I factory reset the device but seems to still be running the same. I've been losing almost 10% battery an hour when I leave my wifi on with barely any use of the phone . this was never the case when the phone was on ICS. it's clearly some sort of data connection as it relates to Maps usage as i've been seeing high CPU usage by the app and, at times, nearly 50% of my battery life going to the maps process.
Also, just noticed on BBS that the android OS and maps high battery usage may be due to alarm manager...I'm seeing many long awake times for a number of apps. hadn't noticed it as much before because i had booted the device multiple times today. any thoughts here? i know what this app is for and there's lots of info and complaints out there about this process on other phones in the past, but not much for stock JB on the HOX...
I have had TERRIBLE battery life while running Sense JB ROMs, (seriously, incredibly bad), versus ICS ROMs. Tried nearly every Sense JB ROM that's out there and countless different radios. No idea why I'm having this problem. I'm not having problems with wakelocks BTW
It's maps. I don't have Google now and maps still ate half my battery on JB. Only way to get around it is make maps hibernate I've found, but this requires rooting.
Sent from my HTC One XL
Try Greenify. You need root, but it allows you to stop apps from running in the background. It's not a task killer, which are worse than nothing because they run constantly shutting down apps that keep restarting; rather, it uses system settings to prevent them from starting background at all. You can use it on stuff like Maps if you use another app to convert them to user apps. I've been using it a couple of weeks, and it's worked just great.
ECEXCURSION said:
It's maps. I don't have Google now and maps still ate half my battery on JB. Only way to get around it is make maps hibernate I've found, but this requires rooting.
Sent from my HTC One XL
Click to expand...
Click to collapse
iElvis said:
Try Greenify. You need root, but it allows you to stop apps from running in the background. It's not a task killer, which are worse than nothing because they run constantly shutting down apps that keep restarting; rather, it uses system settings to prevent them from starting background at all. You can use it on stuff like Maps if you use another app to convert them to user apps. I've been using it a couple of weeks, and it's worked just great.
Click to expand...
Click to collapse
Thanks. It definitely seems like Maps is the problem for me. BBS shows a number of maps-based apps with long wake times. I charged up to about 95% before bed last night, and am going to let it run down all the way today to see what happens. Will post some screenshots later, if anyone cares.
EDIT: Nevermind, will probably post this in the BBS thread, unless anyone here really wants it.
Hydromea said:
I have had TERRIBLE battery life while running Sense JB ROMs, (seriously, incredibly bad), versus ICS ROMs. Tried nearly every Sense JB ROM that's out there and countless different radios. No idea why I'm having this problem. I'm not having problems with wakelocks BTW
Click to expand...
Click to collapse
Serially doubt you've tried viper xl
Sent from my HTC One X using xda premium
Hydromea said:
I have had TERRIBLE battery life while running Sense JB ROMs, (seriously, incredibly bad), versus ICS ROMs. Tried nearly every Sense JB ROM that's out there and countless different radios. No idea why I'm having this problem. I'm not having problems with wakelocks BTW
Click to expand...
Click to collapse
Same. 2.5 hrs of screen time vs 3.5 for ICS. Same usage.
Viper JB vs Cleanrom ICS.
Stock everything else (radio, kernal)
maybe not necessarily maps like originally thought, though it's one of the culprits. the mediascanner just happens to hit maps a lot, likely due to it's typically-large cache. check this thread, particularly post #42 and the Google response another 10 posts or so later. sounds like there is definitely an issue with the device indexing and it's the same thing that affected a number android devices. my guess is that some people just dont have a lot of media files (or wipe their phones often enough that they dont accumulate much) and dont see as much of the effect.
https://code.google.com/p/android/issues/detail?id=37199
there's also a link at the end of that thread to another similar thread, found here: http://code.google.com/p/android/issues/detail?id=40370#58
i guess we really need to get that 4.2 source. also looks like someone built a sort of patch into CM10 on teh SGS3, but i dont know those forums well so i can't corroborate this. wow, i just ****ing said corroborate, time to go to bed.
Lol, corroborate.
Idk, I still think it's maps. I don't have very much media (2 albums) and disabling maps fixed my battery life (200% improvement, literally).
Sent from my HTC One XL
ECEXCURSION said:
Lol, corroborate.
Idk, I still think it's maps. I don't have very much media (2 albums) and disabling maps fixed my battery life (200% improvement, literally).
Sent from my HTC One XL
Click to expand...
Click to collapse
yeah, i'm back on this boat as well. maps still has a long wake time i'm seeing location scanner services running so i'm thinking it's a location-based thing. going to let my phone die today so i can get a good BBS log since i screwed that up yesterday. i'm noticing odd dips in battery life whenever the phone wakes up. it seems to stay awake for up to 10-20 mins, but with the screen off. really weird thing is that when i let it sit overnight, there's no spike (just greater than usual battery drain) but it's when the phone first wakes up that it seems to be really draining and staying awake.
Wondering if any of the color apps (Faux/Franco) will work with a rooted ROM using stock kernel? Noticed that on the N4 that stock 4.4.4 is amazing (lost 4% in 12 hours!), compared to my N5 using elementalx at 28% over same period.
I just hate stock colors and hoped to still be able to change them?
yes, but you need a custom kernel that supports color change/gamma. with just stock, no. its code thats added to a kernel that gives you the feature, not rom related at all.
simms22 said:
yes, but you need a custom kernel that supports color change/gamma. with just stock, no. its code thats added to a kernel that gives you the feature, not rom related at all.
Click to expand...
Click to collapse
Thanks. That's kinda what I thought.
I might just try going back to pure stock to see if the N5 can come close to the deep sleep of the N4 running 4.4.4 stock. Then decide if deeper colors are worth average battery life.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Globespy said:
Thanks. That's kinda what I thought.
I might just try going back to pure stock to see if the N5 can come close to the deep sleep of the N4 running 4.4.4 stock. Then decide if deeper colors are worth average battery life.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
why would colors affect battery life? unless you are talking about the kernel that you were using in general. anyways, battery life most is dependent on how you personally use your device, how you set it up, what apps you use, and very much your data/phone signal quality. the kernel will play just a little when it comes to battery, unless the kernel itself is just plain bad, with bad code. deep sleep could be kernel related, but it could be related to the services you are running as well. google play services has an issue lately with constantly checking for your location. this constant checking constantly wakes your device. maybe this is the issue with your non deep sleep? i know i had it, until i disabled certain services.
simms22 said:
why would colors affect battery life? unless you are talking about the kernel that you were using in general. anyways, battery life most is dependent on how you personally use your device, how you set it up, what apps you use, and very much your data/phone signal quality. the kernel will play just a little when it comes to battery, unless the kernel itself is just plain bad, with bad code. deep sleep could be kernel related, but it could be related to the services you are running as well. google play services has an issue lately with constantly checking for your location. this constant checking constantly wakes your device. maybe this is the issue with your non deep sleep? i know i had it, until i disabled certain services.
Click to expand...
Click to collapse
Colors wouldn't change battery life, I was wondering if the stock kernel could use the color apps.
But to your point, it must be something in the ROM (KangaKat) or one of the apps I'm using rather than the kernel. I think it must be an app although I can't tech l track it down as it's just a bunch of system processes that are eating the juice and nothing pointing to an app in particular. Thanks though.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Hi.
It's been 2 months that I have used my one plus one and I still have the original/vanilla build 22R.
Now I'm curious is it worth to update to the newer versions? I have heard so much bad feedback regarding battery life and other bugs.
What are the pro's and con's?
Right now I'm enjoying 3 days battery life, 5h screen time. But microphone gain for videos is bad also for sound recording. WiFi and the antenna for RF seems to be buggy and not working properly.
Thanks in advance,
Zekenka
Sent from my One using XDA Free mobile app
Just update. Updates are good. Don't listen too much the blaming people cause a lot of them just confuse themselves by doing tests right after the update.
I agree with the previous poster, update your phone, don't worry about the negative Nellies, it's usually user error anyway.
Transmitted via Bacon
Make sure you do the updates in order, or just flash the complete 44s ROM that you can find also (use search, stock rooted 44s).
Personally I would just flash the complete ROM and skip the incrementals lol
ek69 said:
Make sure you do the updates in order, or just flash the complete 44s ROM that you can find also (use search, stock rooted 44s).
Personally I would just flash the complete ROM and skip the incrementals lol
Click to expand...
Click to collapse
What about the battery life etc? I have heard like terrible stories(ofcourse myabe their nellies) but i kinda like the long one right now and I doubt there will be possibility to rollback unless i unlock my bootloader and install TWRP/CWM .
Battery life is good for me and others I've seen. It is possible to go back to old versions but like you said it requires unlocked boot loader and custom recovery probably. Why don't u want to unlock it?
Most battery problems are caused by wake locks. There's a thread in general by timmaaa called play services battery fix if you have issues. If your phone works good as is and don't care about upgrading then don't lol it's not a requirement. If you have bugs then it's probably fixed in the upgrades. Just don't blame us if you do upgrade though
ek69 said:
Battery life is good for me and others I've seen. It is possible to go back to old versions but like you said it requires unlocked boot loader and custom recovery probably. Why don't u want to unlock it?
Most battery problems are caused by wake locks. There's a thread in general by timmaaa called play services battery fix if you have issues. If your phone works good as is and don't care about upgrading then don't lol it's not a requirement. If you have bugs then it's probably fixed in the upgrades. Just don't blame us if you do upgrade though
Click to expand...
Click to collapse
Would unlocking bootloader cause any stuff related to wakelocks? Right now It is perfect 0 drain over night and no terrible wakelocks,
I remember with daily SGS2 build there were terrible wakelocks with up to 20% drain over night
Unlocking bootloader won't do that. Updating or flashing ROM might, no guarantees. My experience is good with latest update, some others have problems most I would say don't. It's your phone and your choice what to do with it lol.
Just update, dont ask to much. Phone is working great on 44S. You will see when you update, battery life is great for me.
Since upgrading to lollipop (have tried many roms, from 5.0.2 to 5.1.1, now getting it on Cynaogen OS 12 ) i get really high battery drain because some apps like facebook, sometimes xda keep mobile radio data active until i force close them. Has anyone else noticed this issue or got a clue what might be causing this? Because i was getting this bug on different versions of lollipop with different apps, i think this might rather be a lollipop issue than the fault of apps. I have also tried flashing different modems, nothing helped. I will post screenshots below
Sent from my A0001 using XDA Free mobile app
I have the same problem xd with oxygen and cm12s
https://code.google.com/p/android/issues/detail?id=165558
Sent from my A0001 using XDA Free mobile app
I have recently joined the mobile radio battery drain club running latest version of COS12 with the latest incremental update being about 2 weeks ago. since that "update" that was only supposed to fix touch screen issues I have had this radio bug. A full battery life cycle will only afford me 4-5 hours of use..... heavy use is MUCH worse! Like 3-4 hrs....
Anyone hear of a patch/fix/work around? I am also bone stock without root, never rooted, etc..... only stock updates on COS....
sick_DMP said:
I have recently joined the mobile radio battery drain club running latest version of COS12 with the latest incremental update being about 2 weeks ago. since that "update" that was only supposed to fix touch screen issues I have had this radio bug. A full battery life cycle will only afford me 4-5 hours of use..... heavy use is MUCH worse! Like 3-4 hrs....
Anyone hear of a patch/fix/work around? I am also bone stock without root, never rooted, etc..... only stock updates on COS....
Click to expand...
Click to collapse
Unfortunately it's a core google OS bug and only google can fix it. It'll happen if you use Mobile Data and there's no solution at all. Either switch to KK or pray that they'll fix it on Android M. Or get used to it like me
Yeah, I've just been using battery save mode and this has been very helpful. Although it does effect performance and gets rid of all the fun animations that make lollipop so enjoyable. It's definitely worth having at least 7-8 hours of use. But, I admit even on battery saver mode I'm noticing extreme battery issues start to effect this profile as well.
Crossing my fingers that Google does roll out a fix of some sort bcuz I'm seeing new apps and Google services show up on my battery stats!
So has anybody been looking at this outside of Google? Some of us are developers, after all, and if the bug is in the Android code and not Google Play Services, we should be able to find it. I haven't seen too many attempts, so far...
acwest said:
So has anybody been looking at this outside of Google? Some of us are developers, after all, and if the bug is in the Android code and not Google Play Services, we should be able to find it. I haven't seen too many attempts, so far...
Click to expand...
Click to collapse
I have read from a number of people that only Google can fix this problem since it is a low level android bug. And it is also supposedly in the beta versions of android M as well. The only current solution I have found to this problem is to stay on Kitkat. And not buy a phone that comes stock with lollipop (or M) until this problem is fixed, assuming you want the best battery life, since it is likely that there will not be any KK roms available for any new phone.
You can help by starring the issue at https://code.google.com/p/android/issues/detail?id=165558
As fars as I can tell, the bug should be in code we have access to, so it doesn't have to be Google that fixes it. I've fixed bugs in the Linux kernel before, and it doesn't get any more low level than that...
They have to accept the fix and include it for it to be much use, but that is an entirely separate issue...