I have got a battery drain issue with my nexus s I9023 working on android 4.1.2 default factory image , no rom no kernet edited
While sleeping in 6 hours battery Drain down from 55% to 5%
The was the last day , I have this issue over two weeks ago , I have used BetterBatteryStats trying to find the process causing that ,
and I found the suspend backoff process cause that , I have changed the wifi with a static IP instead of a dynamic one and the problem still there
any suggestion ?
And thanks in advance for any help.
Have you installed any recent apps that might be causing this (any system panel app, chrome, etc)?
In Wireless Settings, press the Menu button and go to Advance.
You can try to check/uncheck (so that you can test) the following options:
- Wi-Fi optimization
- Keep Wi-Fi on during sleep --> Try setting to Always or Never
You can also check for any app that might be causing this. I've seen Chrome opening this process and staying there, causing the battery drain. But this might not be your case. You can try to reboot your phone (to clear all processes), and then open one app, close it, lock your phone and let it suspend and check if the suspend_wakelock occurs in betterbatterystats. Tedious....yes....but that way you can know which one is causing the battery drain.
Oogway13 said:
Have you installed any recent apps that might be causing this (any system panel app, chrome, etc)?
In Wireless Settings, press the Menu button and go to Advance.
You can try to check/uncheck (so that you can test) the following options:
- Wi-Fi optimization
- Keep Wi-Fi on during sleep --> Try setting to Always or Never
You can also check for any app that might be causing this. I've seen Chrome opening this process and staying there, causing the battery drain. But this might not be your case. You can try to reboot your phone (to clear all processes), and then open one app, close it, lock your phone and let it suspend and check if the suspend_wakelock occurs in betterbatterystats. Tedious....yes....but that way you can know which one is causing the battery drain.
Click to expand...
Click to collapse
Mine does it with wifi off and fresh reboot not opening any apps. I seem to get between 4 hours and 12 hours of lifetime from 100%. I should be upgrading this year but it would be nice if someone could figure this out because I know I am not the only one having an issue.
***********************
**** I have been performing controlled experiments to the best of my ability. See below for results. ****
Experiment #1: Isolate if this is due to Wifi
Methodology (one test per night)
1. Keep wifi off. Perform a set usage pattern, then keep phone on sleep all night.
2. Perform the set usage pattern using wifi, then keep phone on sleep all night with wifi turned on.
3. Perform the set usage pattern using wifi, then keep phone on sleep all night with wifi turned off.
Results:
http://forum.xda-developers.com/showpost.php?p=50548879&postcount=27
Experiment #2: Isolate if this is due to GPS/Location Services (Ongoing)
Methodology (one test per night)
1. Keep GPS off. Perform a set usage pattern, then keep phone on sleep all night. [This is identical to the WiFi experiment, so there is no need to replicate this]
2. Perform the set usage pattern using WIFI, then keep phone on sleep all night with GPS turned on.
3. Perform the set usage pattern using GPS, then keep phone on sleep all night with wifi turned off.
Results:
http://forum.xda-developers.com/showpost.php?p=50685378&postcount=69
***********************
So, I've been battling idle drain battery problems for a while now . I was unable to make much progress because I did not have visibility into partial wakelocks on the system . So I did what any inquisitive person would, I rooted my phone. Bye bye warranty.
Now that I have root, I am able to see the partial wakelocks in better battery stats. To my partial surprise , I do not see any substantial partial wakelocks that would explain the significant battery drain at night. I have good cellular signal, and wifi signal where the phone is placed.
Any clues?
Almost 25 percent in 9 hours. Also notice the lack of activity between successive awake blips, and the constant battery drain that occurs between them. Before I even got root and was able to look at the partial wakelocks, I had already suspected that there were no wakelocks going on but yet the battery was draining.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Below are screenshots from the stock battery app showing the top battery drainers and the details of the major ones.
By the way, I would attribute approximately 6 percent of the battery drain due to the screens. I have quite a bit of data that suggests at the brightness levels I was using the screen for those 30 minutes, the drain rate should have been around 12 percent per hour. That still leaves 18 to 20 percent of battery to be accounted for. According to better battery stats, the phone was only awake for around 30 minutes total when the screen was off. And looking at the CPU Lodge, it's clear that those 30 minutes or so were spent in the lowest frequency mode , and that the phone was in deep sleep at all other times.
Attached are the better battery stats logs that shows the partial wakelocks as well. I don't know why the CPU's states are not included in the file but I can assure you I took a look look at it and the 30 or so minutes of awake time were perfectly captured by the 300mhz state.
http://pastebin.com/j685pa5q
Sent from my XT1034 using Tapatalk
I turned airplane mode on, and left location services on. Battery drain was 2.8%/hr (measured over a 5% battery drain interval) with the phone only being awake for 7min 28sec when the screen was off. There were around 5min of NLP wakelocks, and some other miscelaneous ones. I don't think that explains the battery drain fully.
Then, I turned off location services, and the battery drain has been 1.7%/hr (measured over an 8% battery drain interval) with a total awake time of 5 mins, and of that only 1 min of awake time when the screen was off. Very few to no wakelocks.
What is wrong? Why is the battery draining at ~2%/hr with airplane mode on, location services off, and the phone being in deep sleep pretty much the whole time!?
Hey I'm trying to find if there of a pattern with the battery drain and the battery voltage (mv) .I slightly have the felling the battery is a bit wonky . Could you check the battery voltage while charging just before 100% and the voltage when it has fully charged ? .. Try the code *#*#4636#*#*
I feel the my peak battery voltage has dropped significantly over the last 2 weeks.
Sent from my XT1033 using Tapatalk
I have the same problem with mine, no clue what the problem is, I turned off location services and I dont use 3g at all, only wifi while at home or other places sometimes, but the drain persists, still dont know what to do
Sent from my Moto G :3
Try a Cache wipe in recovery - http://forum.xda-developers.com/showthread.php?t=2634361
neu - smurph said:
Try a Cache wipe in recovery - http://forum.xda-developers.com/showthread.php?t=2634361
Click to expand...
Click to collapse
I don't think a cache wipe is the solution. For example, see the updated battery settings screenshot below. The flat line at the end is the result of just rebooting the device (no cache wipe). The battery is no longer draining constantly, even though the same services are activated.
I'm the OP of the thread that I think first reported this issue. Note that I found that the drain is noticeable in airplane mode as you expect there to be almost zero drain, however it still happens when not in airplane mode as well, you just notice it less as the device is doing other stuff which all adds up to battery drain.
I think there is a driver bug, most likely a WiFi driver bug or possibly GPS driver bug. For example maybe GPS is somehow constantly active but the bug manifests itself in such a way that this is not reported to the OS itself which is why you do not see it active in the battery screen .
I had the exact same issue as reported above, no wakelocks over and above the normal amount but the drain was 3% hr or so. A reboot fixed it but it would reoccur when i connected to another WiFi network.
A factory reset fixed it completely until a few weeks ago when I was on the road and used GPS. That night I had the battery drain issue again.
So whether its WiFi or GPS that's the cause I don't know, and why, for me, did it stay fixed for so long. I also can't remember if I had GPS switched on when I first had the issue before the factory reset so makes it harder for me to determine the cause.
The above was all on 4.3. I've now upgraded to 4.4.2.
I think the only way to debug will to be to pull off all the various logs from android, you may even need to turn on various debugging/logs from the OS to capture more logs. I'm pretty sure you wont diagnose from just looking at wakelocks and battery screens.
If you can recreate this problem, and sounds like some of you have it a lot, then you are in a good position to get the logs.
BTW does anyone use the BBC weather app, I noticed this caused a LOT of NLP wakelocks so don't think its related but I did notice on 4.4.2 that it drained battery fast so I uninstalled. There is a thread in xda that I started about it.
A poster above says to clear cache, this is normally pointless as /cache will usually contain nothing except a few empty folders and a couple of log files. Also clearing cache means a reboot which temporarily fixes the issue anyway.
scott_doyland said:
I'm the OP of the thread that I think first reported this issue. Note that I found that the drain is noticeable in airplane mode as you expect there to be almost zero drain, however it still happens when not in airplane mode as well, you just notice it less as the device is doing other stuff which all adds up to battery drain.
I think there is a driver bug, most likely a WiFi driver bug or possibly GPS driver bug. For example maybe GPS is somehow constantly active but the bug manifests itself in such a way that this is not reported to the OS itself which is why you do not see it active in the battery screen .
I had the exact same issue as reported above, no wakelocks over and above the normal amount but the drain was 3% hr or so. A reboot fixed it but it would reoccur when i connected to another WiFi network.
A factory reset fixed it completely until a few weeks ago when I was on the road and used GPS. That night I had the battery drain issue again.
So whether its WiFi or GPS that's the cause I don't know, and why, for me, did it stay fixed for so long. I also can't remember if I had GPS switched on when I first had the issue before the factory reset so makes it harder for me to determine the cause.
The above was all on 4.3. I've now upgraded to 4.4.2.
I think the only way to debug will to be to pull off all the various logs from android, you may even need to turn on various debugging/logs from the OS to capture more logs. I'm pretty sure you wont diagnose from just looking at wakelocks and battery screens.
If you can recreate this problem, and sounds like some of you have it a lot, then you are in a good position to get the logs.
BTW does anyone use the BBC weather app, I noticed this caused a LOT of NLP wakelocks so don't think its related but I did notice on 4.4.2 that it drained battery fast so I uninstalled. There is a thread in xda that I started about it.
A poster above says to clear cache, this is normally pointless as /cache will usually contain nothing except a few empty folders and a couple of log files. Also clearing cache means a reboot which temporarily fixes the issue anyway.
Click to expand...
Click to collapse
Thanks you very much for your reply Scott.
As you can see in my troubleshooting, I eventually turned location services and wifi off, but still measured a considerable battery drain. Do you suppose that once you use wifi, or location services after bootup, the effect may remain afterward even if they are switched off? If so, do you agree that if I turn off location services and wifi, then reboot so that the phone boots up with neither - that should be able to verify your hypothesis?
I'll go ahead and try that for a few days and see how it goes. Will report back.
Others have mentioned something to do with the cellular radio power management, and how rebooting and clearing the cache helps with that (apparently this came from a motorola rep...). I've included a data point in this thread where I merely rebooted without a cache clear and the problem went away. So, perhaps the clearing of the cache really does nothing at all ...
If this is a software issue, why aren't all phone with the same software version effected? How are people getting 6-7 days of standby time consistently? Maybe they never use wifi or location services? Well, I intend to test the wifi/gps hypothesis soon .
google+, google now etc caused me a massive battery drain until i greenified them. now i get a solid 2 days and about ~6 hours screen on time.
twist3d0n3 said:
google+, google now etc caused me a massive battery drain until i greenified them. now i get a solid 2 days and about ~6 hours screen on time.
Click to expand...
Click to collapse
Do you need the donate version to hibernate them?
twist3d0n3 said:
google+, google now etc caused me a massive battery drain until i greenified them. now i get a solid 2 days and about ~6 hours screen on time.
Click to expand...
Click to collapse
So that´s exactly what I did, too. Turns out my Moto G is a battery monster, 2 days with average screen time without any problems.
tictac0566 said:
So that´s exactly what I did, too. Turns out my Moto G is a battery monster, 2 days with average screen time without any problems.
Click to expand...
Click to collapse
This thread is specifically about battery drain caused by something unknown, not an app or wakelock, I think we should try to keep it clean by not cluttering with app related issues as that can then be confusing for people who are reading through the thread. Thanks.
---------- Post added at 11:40 AM ---------- Previous post was at 11:16 AM ----------
if0rg0t said:
Thanks you very much for your reply Scott.
As you can see in my troubleshooting, I eventually turned location services and wifi off, but still measured a considerable battery drain. Do you suppose that once you use wifi, or location services after bootup, the effect may remain afterward even if they are switched off? If so, do you agree that if I turn off location services and wifi, then reboot so that the phone boots up with neither - that should be able to verify your hypothesis?
I'll go ahead and try that for a few days and see how it goes. Will report back.
Others have mentioned something to do with the cellular radio power management, and how rebooting and clearing the cache helps with that (apparently this came from a motorola rep...). I've included a data point in this thread where I merely rebooted without a cache clear and the problem went away. So, perhaps the clearing of the cache really does nothing at all ...
If this is a software issue, why aren't all phone with the same software version effected? How are people getting 6-7 days of standby time consistently? Maybe they never use wifi or location services? Well, I intend to test the wifi/gps hypothesis soon .
Click to expand...
Click to collapse
Well I cant answer all your questions but I will tell you about my test last night. I hardly use GPS at all (and my battery is normal) and last time I did use GPS I had the battery drain as per my post above, so last night I:
1. Drove 15mins from my house.
2. Switched on GPS (high accuracy).
3. Started google maps and drove for 2mins with GPS in use.
4. Shutdown maps app and drove home (GPS still on - ie high accuracy).
5. At home used phone for bit of XDA on wifi for a bit.
6. Switched on airplane mode but location service still on (note airplane mode does NOT switch off GPS), woke up at 02:00AM and noted I had the annoying battery drain - arghhh.
7. Switched off GPS - woke up 2 hrs later and drain still happening.
8. Switch off location altogether - woke up in morning and drain still happening.
9. Rebooted phone and now battery back to normal, Im back on wifi/mobile location (battery saving).
So to me it looks like its maybe related to GPS in some way but whether its purely GPS or a GPS/wigi/location combo I have no idea.
However I have in the past switced on GPS in my house just to play about and havent has the drain, so is it due to a larger change of location when GPS is on (ie 15mins drive from my house) that causes it to go bad.
So annoying, I took a CWM backup before I booted up my phone so I will pull that to my laptop and see if there are any obvious error logs to look at but I doubt it.
Im still leaning towards a driver issue or maybe some component, eg GPS chip, staying alive/awake even when not in use but m sure others have reported they have it with location/GPS off completely. Maybe its even a few different problems.
You said not everyone has the error, but I bet quite a few non-xda people do but do not realise. A lot of people will just charge their phones overnight so wont even realise, during the day they will think ~2% drop per hour is normal. Even if they do notice the drop in airplane mode they probably think thats normal and ignore it.
I think getting Motorola to accept there is an error is going to be almost impossible especially if its hardware related. Also as we have unlocked bootloader I doubt they will even accept a call once they know that.
I think it would be interesting to get a list of phones that are affected, ie model, serial no, location brought, ROM etc. maybe its a certain batch of phones, if we can determine that it would be some help, maybe we could buy one that isnt affected
So to start it off my phone is
XT1032 UK retail brought from Basildon, Essex, UK from phones4u.
Problem happens on 4.3 stock and 4.4.2 stock.
Baseband version is MSM8626BP_1032.340.63.00R.
Im tempted to flash GPE and/or new basenband radio but I bet the same thing happens.
I may see if there is a new GPS driver but no idea how to flash it etc.
Such a shame as this phone is excellent for me otherwise.
Just seen this thread as well, it blames GPS
http://forum.xda-developers.com/showthread.php?t=2607641
if0rg0t said:
Do you need the donate version to hibernate them?
Click to expand...
Click to collapse
if they're system apps, yeah. totally worth it tho cos you can do maps/fb etc too, also you can allow apps that get push messages to still give you notifications whilst greenified.
e: just to note, i have gps (high accuracy) enabled constantly and still manage 2 days.
twist3d0n3 said:
if they're system apps, yeah. totally worth it tho cos you can do maps/fb etc too, also you can allow apps that get push messages to still give you notifications whilst greenified.
e: just to note, i have gps (high accuracy) enabled constantly and still manage 2 days.
Click to expand...
Click to collapse
Maybe you can help test if you don't mind.
1. Use Google maps with high accuracy when you go out for 5mins or so.
2. Once home use phone as normal on WiFi for a bit, just 10mins will be enough.
3. Take note of battery percent.
4. Switch on airplane mode for 2hrs - DO NOT USE PHONE during this time.
5. After 2hrs take note of battery percent.
6. Report the battery percents recorded in this thread.
If you can do this we would be grateful.
Let us know your phone model, where purchased, ROM etc.
Thanks.
Hi,
Following this MotoG thread for some time I have to admit that my MotoG also has the same issue from time to time.
This is the reason now that I joined XDA because this issue is a real pain.
Having my MotoG for three weeks now I had to restart it four or five times to get rid of the excessive battery drain.
My MotoG (XT1032) is bought in the Netherlands, unlocked, rooted, CWM and stock ROM.
I did remove some Motorola apps and disabled some.
Because of the last remarks that it seems to be GPS related, I want to let you know that it also happened to me without using the GPS.
Yesterday it happened at school, at first the drain was not present but suddenly it started.
In the between the two situation I only checked my mail through Wifi and checked some news.
My MotoG has Wifi always on, bluetooth off, GPS off.
There must be something more than just GPS which causes this drain.
Hopefully we can find the root cause soon.
Mickeyvdb said:
Hi,
Following this MotoG thread for some time I have to admit that my MotoG also has the same issue from time to time.
This is the reason now that I joined XDA because this issue is a real pain.
Having my MotoG for three weeks now I had to restart it four or five times to get rid of the excessive battery drain.
My MotoG (XT1032) is bought in the Netherlands, unlocked, rooted, CWM and stock ROM.
I did remove some Motorola apps and disabled some.
Because of the last remarks that it seems to be GPS related, I want to let you know that it also happened to me without using the GPS.
Yesterday it happened at school, at first the drain was not present but suddenly it started.
In the between the two situation I only checked my mail through Wifi and checked some news.
My MotoG has Wifi always on, bluetooth off, GPS off.
There must be something more than just GPS which causes this drain.
Hopefully we can find the root cause soon.
Click to expand...
Click to collapse
Thanks for your reply, have you confirmed this drain happens when in airplane mode as well and that no wakelocks occur, no unusual statistics in battery screen etc. I ask as some people say they have the issue but then say they have greenified an app etc to stop it which basically means they dont have the issue at all. Im not saying I dont believe you, far from it, I just want to confirm its exactly the same issue as a few of us are seeing. Next time can you NOT reboot but leave phone in airplane mode for a few hours and DONT use it at all, then see if battery has gone down by 2-3% per hour.
Thanks.
Have not used airplane mode to check it, but will sure do this when it happens next time.
What I observed in battery stats was a high percentage of android-os.
I have not used greenify so far.
Sent from my GT-P3110 using xda app-developers app
Mickeyvdb said:
Have not used airplane mode to check it, but will sure do this when it happens next time.
What I observed in battery stats was a high percentage of android-os.
I have not used greenify so far.
Sent from my GT-P3110 using xda app-developers app
Click to expand...
Click to collapse
Doesn't sound like the same issue if android OS shows high in battery stats. That sounds more like a wakelock issue of some kind which still means you may get drain in airplane mode but for a different reason.
This thread is specifically for the problem of ALL battery stats looking normal, so android OS doesn't show up as high.
I think your best get is to root and install 'wakelock detector' app and you will probably see some high wakelock for android OS.
Thanks for your post on the Motorola forums Scott. It was well written, and to the point. I hope this issue gets the attention it deserves. I'll be reporting in the next few days with my experiments.
scott_doyland said:
Doesn't sound like the same issue if android OS shows high in battery stats. That sounds more like a wakelock issue of some kind which still means you may get drain in airplane mode but for a different reason.
This thread is specifically for the problem of ALL battery stats looking normal, so android OS doesn't show up as high.
I think your best get is to root and install 'wakelock detector' app and you will probably see some high wakelock for android OS.
Click to expand...
Click to collapse
Sorry to post this wrong condition.
I had the impression that I was suffering the same problem.
Will have a look with a 'wakelock detector' to see if I can tackle the high android-os consumption since I rooted my device already.
Although the issue seems different I will have a good look this morning since I have to use the GPS.
Will keep you informed if I notice something weird.
Sup XDA!
When I updated to android 5.1.1 (cm12.1, rooted) android system started to drain my battery, even more than my screen would. This wasn't an issue back on 5.0 and I wonder what the problem is, and I thought you guys could be able to help me out as this forum has helped me before, thx for that!
Ive attached 3 screens, first is from battery monitor and the other 2 are screens of my battery 'page' in settings. Let me know if you need any additional information and or screenshots and I'll be happy to provide.
Thanks in advance
Disable all of the google services you feel that take RAM (and so, battery) using the Disable Service app. Don't disable GCM Service. Don't disable FusedLocation Service if you use GPS. The only google service running on my phone is GCM. Disable location services, key chain, pppreferences, CM logger, dev tools, etc. just anything that you find isn't important and takes battery! Use apps like Greenify, Disable Service and Titanium backup to greenify, disable and freeze the apps/services.
TheHighLife said:
Sup XDA!
When I updated to android 5.1.1 (cm12.1, rooted) android system started to drain my battery, even more than my screen would. This wasn't an issue back on 5.0 and I wonder what the problem is, and I thought you guys could be able to help me out as this forum has helped me before, thx for that!
Ive attached 3 screens, first is from battery monitor and the other 2 are screens of my battery 'page' in settings. Let me know if you need any additional information and or screenshots and I'll be happy to provide.
Thanks in advance
Click to expand...
Click to collapse
This seems to be a common issue.... the fix involves downgrading the modem. However downgrading the modem requires downgrading your TWRP Recovery... which you cannot do if you are running CM12.1, the downgrade will fail every time no matter which "tricks" you use.
lotherius said:
This seems to be a common issue.... the fix involves downgrading the modem. However downgrading the modem requires downgrading your TWRP Recovery... which you cannot do if you are running CM12.1, the downgrade will fail every time no matter which "tricks" you use.
Click to expand...
Click to collapse
You don't need to downgrade TWRP to flash a modem. You can very easily flash a modem without TWRP even installed; fastboot. It isn't even certain that the modem is causing this drain either.
Working on the likely assumption that it is the same problem, the modem is indeed not to blame.
I have moved through COS12.1, CM12.1, sultan, paranoid android, and exodus, with and without flashing the modem and gapps, using both stock and Boeffla kernel.
They all exhibit the same drain, 9-11% overnight or 16-40mA/h (via dumpsys). This is regardless of wifi/cellular/ambient and other features being disabled.
The only obvious anomalies differing from 5.0.2 are high system_server cpu (25-450% via top) when asleep, and intermittent floods of "unknown" wakeups without wakelocks (Observed by dumping batterystats, and are not registered by settings - battery).
On one of my many reflashes Exodus 12.1 suddenly began behaving reasonably, with 6-10mA/h drain and 2% overnight.
The high System_sever cpu and intermittent wakeups were still present at this point, and may be unrelated oddities.
I later made the mistake of flashing a newer nightly (and later the correct modem), upon which the problem reappeared.
Doing a wipe and reflashing in the same manner did not resolve the issue, and many attempts later I have been unable to reproduce the same state.
Coming from kitkat I figured 5.0.2 would be the same, but it has been smooth sailing since flashing it last night (Exodus), with 6-10mA/h drain and 0% overnight.
Roughy said:
Working on the likely assumption that it is the same problem, the modem is indeed not to blame.
I have moved through COS12.1, CM12.1, sultan, paranoid android, and exodus, with and without flashing the modem and gapps, using both stock and Boeffla kernel.
They all exhibit the same drain, 9-11% overnight or 16-40mA/h (via dumpsys). This is regardless of wifi/cellular/ambient and other features being disabled.
The only obvious anomalies differing from 5.0.2 are high system_server cpu (25-450% via top) when asleep, and intermittent floods of "unknown" wakeups without wakelocks (Observed by dumping batterystats, and are not registered by settings - battery).
On one of my many reflashes Exodus 12.1 suddenly began behaving reasonably, with 6-10mA/h drain and 2% overnight.
The high System_sever cpu and intermittent wakeups were still present at this point, and may be unrelated oddities.
I later made the mistake of flashing a newer nightly (and later the correct modem), upon which the problem reappeared.
Doing a wipe and reflashing in the same manner did not resolve the issue, and many attempts later I have been unable to reproduce the same state.
Coming from kitkat I figured 5.0.2 would be the same, but it has been smooth sailing since flashing it last night (Exodus), with 6-10mA/h drain and 0% overnight.
Click to expand...
Click to collapse
So right now you are on the 5.0.2 exodus builds and having minimal battery drain? Which modem are you using?
f41lbl0g said:
So right now you are on the 5.0.2 exodus builds and having minimal battery drain? Which modem are you using?
Click to expand...
Click to collapse
Correct, with the Xposed Mobile Radio Active fix applied.
bacon_firmware_update_2015_04_03.zip from ... <10 posts and am not allowed to post links yet.
It's on Exodus' 5.0.2 download page along with the roms.
As usual the modem will not flash in TWRP, and has to be done manually via fastboot.
Paresh Kalinani said:
Disable all of the google services you feel that take RAM (and so, battery) using the Disable Service app. Don't disable GCM Service. Don't disable FusedLocation Service if you use GPS. The only google service running on my phone is GCM. Disable location services, key chain, pppreferences, CM logger, dev tools, etc. just anything that you find isn't important and takes battery! Use apps like Greenify, Disable Service and Titanium backup to greenify, disable and freeze the apps/services.
Click to expand...
Click to collapse
I did all of this but it's still draining battery, should I post new screenshots?
TheHighLife said:
I did all of this but it's still draining battery, should I post new screenshots?
Click to expand...
Click to collapse
As you have tried many things to improve your battery life, last option I wanna suggest you to use your device in safe mode for one complete charge cycle from 94% down to 5% (I know that this mode is pathetic).
If you still find that it's causing battery drain, you need to reflash the ROM and please do not restore any backup(restore only those which are most important).
If you find that Android system is not causing anymore battery drain, then it's one of the third party app that is doing so.
Mr hOaX said:
As you have tried many things to improve your battery life, last option I wanna suggest you to use your device in safe mode for one complete charge cycle from 94% down to 5% (I know that this mode is pathetic).
If you still find that it's causing battery drain, you need to reflash the ROM and please do not restore any backup(restore only those which are most important).
If you find that Android system is not causing anymore battery drain, then it's one of the third party app that is doing so.
Click to expand...
Click to collapse
Ive only tried to disable some services that show up under android system. How do I put it in safe mode tho?
By the way, I just noticed that the CPU total time for android system is exactly the same time as the SOT, what does this mean? It only drains this much battery when the screen is on?
TheHighLife said:
Ive only tried to disable some services that show up under android system. How do I put it in safe mode tho?
By the way, I just noticed that the CPU total time for android system is exactly the same time as the SOT, what does this mean? It only drains this much battery when the screen is on?
Click to expand...
Click to collapse
Boot your device into safe mode https://support.google.com/nexus/answer/2852139?hl=en
Just post some screenshots of the battery (complete overview of graph screen and app list screen) after using your OPO in safe mode atleast for one charge cycle (90%+ down to 10%)
This will help us to figure out what is the exact issue you are facing.
If you are not interested in troubleshooting, just flash fastboot images of this build(CMOS12.1) using following guide
forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471
For OnePlus One, about a month ago after systems update, my battery started draining fats and it has gotten worse over the past week. The battery barely holds four hours of after a full charge and the phone gets very hot. Also, over the past week, my main SMS messaging app (SMS) crashes nine out of 10 times -- I can start the app but when I click any of the messages I was to read or type, it freezes and crashes. Also, since yesterday, my phone dilaer crashes very often. Any thoughts/help? I am not familiar with how to flash ROM, etc. Also, since yesterday, charging has been very slow -- overnight, the charge went from 35% full to 74% full. I tried safe mode as well and no luck -- battery still keeps draining at 1% every three minutes.
I have the same issue. Any fixes which work ?
I am running into a Wakelock issue and I am completely stumped. For some reason, my phone refuses to go into deep sleep for hours on end. Better Battery Stats shows that the phone spends the majority of its time with the CPU at its lowest frequency, but refuses to go into deep sleep. The issue started when I clean flashed LinageOS back when I tried 14.1. Since 15.1 has recently released, I tried to have another go, yet the problem remains. I am using a Oneplus 5.
The very weird thing about these Wakelocks is, is that they are completely invisible. Wakelock Detector isn't showing any specific wakelocks (Advanced mode enabled), but does show that the phone isn't entering the deep sleep state. Not even for a single second. Better Battery Stats shows the same thing, with zero seconds spent in Screen off (deep sleep) and all the time spent in Screen off (Awake). No application is listed anywhere that's causing these wakelocks. They aren't visible under partial wakelocks nor kernel wakelocks.
Now this is where things get bizarre. I tried removing all my applications and reinstalling them one by one to find out if it was an app that was causing the issues. Each time I installed an app, I would check whether the phone would go into deep sleep when I wasn't using it. It turns out that the phone stopped going into deep as soon as Whatsapp was installed. Yet Whatsapp would never register more than a few seconds of wakelocks each passing hour.
I'm not sure where to even begin to try and solve this issue. Has anyone else ever experienced these kind of invisible / hidden wakelocks, and if so, how did you manage to fix these issues? Thank you very much in advance for helping me out
Nobody with a similar problem to mine? It's really killing battery life for me
Mushoz said:
Nobody with a similar problem to mine? It's really killing battery life for me
Click to expand...
Click to collapse
I think I may have something similar happening with WhatsApp. My stats show lots of time spent with CPU on and screen off. Wakelock detector shows WhatsApp at the top of the list. But I don't really understand how to solve it other than deleting WhatsApp, which I don't want to do. Did you get anywhere with it?
Ian
IanHodgson said:
I think I may have something similar happening with WhatsApp. My stats show lots of time spent with CPU on and screen off. Wakelock detector shows WhatsApp at the top of the list. But I don't really understand how to solve it other than deleting WhatsApp, which I don't want to do. Did you get anywhere with it?
Ian
Click to expand...
Click to collapse
No, I still have the same issue unfortunately. Though my issue seems to be slightly different than yours in the sense that Whatsapp is very low in the list. The total minutes of Wakelock is far below the total minutes of awake (screen off). But uninstalling Whatsapp instantly solves the wakelock issue. Out of interest, what phone are you using and what rom?
Mushoz said:
Out of interest, what phone are you using and what rom?
Click to expand...
Click to collapse
Redmi Note 4, Pixel Experience Oreo 8.1
I got here through a google search. I am not sure it's whatsapp causing this (haven't removed it yet) but on a Moto G3 with LOS 15.1 unofficial by Rahul I have the same symptoms.