I've noticed something strange which seems to drain my battery faster when it happens.
Some apps that use sensors seem to leave the sensor active after closing the app itself (even with force close from app manager).
I've first noticed this problem with the app "GPS Essentials", then "GPS Status" the next day, they left the "Magnetic Field" sensor active after manually force closing them.
After a few hours, in Badass Battery Monitor, I could see that the Apps were eating about 75% of the battery, and when looking at the details, "GPS Essentials" was using about 45%, more than the kernel and android system), and it said that it had been using the "Magnetic Field" sensor for more than 5 hours, although the app was manually force closed about 20 minutes after I've started it.
That was in the stock ROM.
Since then, I've installed a custom ROM (CheckROM V2, so it's still based on Samsung's base ROM), and the problem is appearing again.
This time, I've had the same problem with Sygic that left the "Orientation" sensor active, and continued using it according to Badass Battery Monitor, even after force closing Sygic.
Did anyone else notice that or is it a problem with my phone?
Is there a solution besides rebooting every time after using any of these apps?
Thanks!
I've found a similar problem, and explanations on why it's happening, but it says that it appeared in Gingerbread but has been corrected in Honeycomb and ICS.
It does seem like the exact same problem with the same symptoms though, so I wonder if it really is gone...
Here is the page where I found the info :
http://fivasim.pcriot.com/androsensor.html
And here is a quote from that page :
Update: After many months of testing and debugging I haven't found a way to fix the battery issue for good. Perhaps I shouldn't... It's not really my issue but a general android problem (just google for "gingerbread battery drain"). And it happens with EVERY app that makes use of the sensors that are the root of the problem.
The battery leakage comes from android sensors that are not well supported by the kernel or the android OS. Most usually the accelerometer sensor causes the issue but sometimes the light sensor and the proximity sensor can cause this issue as well. Other sensors seem to have nothing to do with battery drain.
However I have found what's causing it and ways to `patch` over it (unfortunately, no way to permanently fix it).
Trying to invoke a sensor with such a problem, will cause the sensor to stay open even after the app is stoped and disposed of memory.
Another common issue is a conflict. Two apps register the same sensor, then one app unregisters but fails because the sensor is in use by the other app. The sensor stays in use by one of the two apps and this will remain even after both apps are killed.
In most cases there is a way to fix this:
- In the first case, you may just find which sensor is misbehaving (strange readings, very slow response or 'Failed to start' error etc.). Go to AndroSensor's settings and disable that sensor. Then reboot, run AndroSensor once and wait to see if the problem persists. Most usually the light and the proximity sensors are to blame for this issue. Sometimes the issue is caused only if both light and proximity are enabled, but disappears after disabling any of the two.
- If you don't have a misbehaving sensor then there is probably some conflict. Conflicts can be caused (usually in Gingerbread) when having auto-rotate (accelerometer use) or auto-brightness on.
Solution: Go to your device's display settings and disable auto-brightness and auto-rotation. Then reboot, run AndroSensor once and wait to see if the battery drain continues. If the problem persists then there is probably a conflict with some hidden/system service. Most usual is the conflict with SGS and SGS2 secret menu ( by dialling "*#0*#" on the dialer ). I have found no way to bypass this and it can only be solved by disabling the accelerometer and orientation sensors in AndroSensor, then reboot (orientation sensor makes seemless use of the accelerometer).
The only good thing about this, is that in HoneyComb and ICS the issue seems to have disappeared for good!
Am I really the only one with the problem?
Mithrandir007 said:
I've noticed something strange which seems to drain my battery faster when it happens.
Some apps that use sensors seem to leave the sensor active after closing the app itself (even with force close from app manager).
I've first noticed this problem with the app "GPS Essentials", then "GPS Status" the next day, they left the "Magnetic Field" sensor active after manually force closing them.
After a few hours, in Badass Battery Monitor, I could see that the Apps were eating about 75% of the battery, and when looking at the details, "GPS Essentials" was using about 45%, more than the kernel and android system), and it said that it had been using the "Magnetic Field" sensor for more than 5 hours, although the app was manually force closed about 20 minutes after I've started it.
That was in the stock ROM.
Since then, I've installed a custom ROM (CheckROM V2, so it's still based on Samsung's base ROM), and the problem is appearing again.
This time, I've had the same problem with Sygic that left the "Orientation" sensor active, and continued using it according to Badass Battery Monitor, even after force closing Sygic.
Did anyone else notice that or is it a problem with my phone?
Is there a solution besides rebooting every time after using any of these apps?
Thanks!
Click to expand...
Click to collapse
Does CPU Spy confirm that problem, showing awake instead of deep sleep?
chamonix said:
Does CPU Spy confirm that problem, showing awake instead of deep sleep?
Click to expand...
Click to collapse
It does seem to go to deep sleep, but I still see a big difference in battery life between when it happens (around 7-10%/hour), and after I reboot (~ 1%/hour).
Before I start applications using those sensors, the battery life is normal as well, so I don't think it's something else.
I've just made a few screenshots to show what's happening.
Last night, before going to bed, I've rebooted the phone, then started Sygic and AndroSensor, exited the apps, then manually force closed them to make sure.
Then I left the phone charging for the night.
This morning, I remove the phone from the charger, and Badass Battery Monitor starts from that point to calculate the battery drain from everything (so I'm sure neither Sygic nor AndroSensor have been running at all since I unplugged the phone).
Since then, a bit less than 2 hours have passed (I've barely used my phone during that period since I was getting ready then driving to work).
There was a 5% discharge (which is strangely not as much as I had yesterday, but still more than the usual 1%/hour when in standby) and we can clearly see what's eating the battery the most in Badass Battery Monitor.
The "Orientation", "Pressure", "Magnetic Field" and "Accelerometer" sensors have been running the whole time since it was unplugged.
What do you think, is this normal behavior?
I've now installed another custom ROM (Omega 8, with the new samsung firmware update), and the problem seems to remain..
If I'm the only one with the problem, I'm starting to think it might be something hardware (or an app I've installed every time maybe), since I've had the problem with every ROM I've installed...
Switching to another kernel didn't seem to help either.. I'm really starting to wonder if this is something I can fix.
Does no one else have the problem?
I think I've found the reason but now I wonder why no one else seems to have the problem (or maybe I'm the only one who actually cares ).
It looks like it's a battery usage reporting bug in the Samsung firmwares, not an actual drain.
Whenever you run an app which uses sensors (like GPS Status, AndroSensors, Sygic, ...), there is a good chance that when quitting the app, Android will not register the sensors as "stopped", even though they are not running anymore.
This means that the current battery life calculation takes those sensors into account as if they were still running, and the battery % drops faster than it should.
Here's a post from the creator of GPS Status, explaining the problem :
http://forum.xda-developers.com/showpost.php?p=23106668&postcount=491
There is also a small explanation from the author on the Google Play page for GPS Status, I'll quote :
"KNOWN FIRMWARE ISSUES (please do not report them):
- Samsung phones: Because of a firmware bug those phones may report extreme battery consumption for GPS Status (and for other programs using sensors) even if it is not running. This is harmless and no power is consumed! Just ignore it and let's hope that a future firmware upgrade will fix this."
So I'm still wondering if this is something we can fix, or if we have to wait for Samsung to correct that bug?
Mithrandir007 said:
I think I've found the reason but now I wonder why no one else seems to have the problem (or maybe I'm the only one who actually cares ).
Click to expand...
Click to collapse
Yes I care. Thanks very much for posting this. I've noticed exactly the same thing and it's been driving me crazy. Good to know it's just a false alarm. With ICS 4.0.4 coming to the Galaxy S2 soon, maybe it will be fix there.
Mithrandir007 said:
I think I've found the reason but now I wonder why no one else seems to have the problem (or maybe I'm the only one who actually cares ).
It looks like it's a battery usage reporting bug in the Samsung firmwares, not an actual drain.
Whenever you run an app which uses sensors (like GPS Status, AndroSensors, Sygic, ...), there is a good chance that when quitting the app, Android will not register the sensors as "stopped", even though they are not running anymore.
This means that the current battery life calculation takes those sensors into account as if they were still running, and the battery % drops faster than it should.
Here's a post from the creator of GPS Status, explaining the problem :
http://forum.xda-developers.com/showpost.php?p=23106668&postcount=491
There is also a small explanation from the author on the Google Play page for GPS Status, I'll quote :
"KNOWN FIRMWARE ISSUES (please do not report them):
- Samsung phones: Because of a firmware bug those phones may report extreme battery consumption for GPS Status (and for other programs using sensors) even if it is not running. This is harmless and no power is consumed! Just ignore it and let's hope that a future firmware upgrade will fix this."
So I'm still wondering if this is something we can fix, or if we have to wait for Samsung to correct that bug?
Click to expand...
Click to collapse
If this is really the problem that would be an deep in Android or between the hardware and android as it is the 'batteryinfo' service reporting sensors data.
Indeed, I don't think there is an easy fix for this one, unless someone has already worked on that part ((un)registration of sensors from the battery measurement service).
Hopefully it'll be fixed in a future version of the firmware, or in Jelly Bean.
XDA-Usr : maybe it'll be fixed in that version, indeed..
It is just a false alarm, although it still leads to inaccuracy of the battery level.
Mithrandir007 said:
I think I've found the reason but now I wonder why no one else seems to have the problem (or maybe I'm the only one who actually cares ).
It looks like it's a battery usage reporting bug in the Samsung firmwares, not an actual drain.
Whenever you run an app which uses sensors (like GPS Status, AndroSensors, Sygic, ...), there is a good chance that when quitting the app, Android will not register the sensors as "stopped", even though they are not running anymore.
This means that the current battery life calculation takes those sensors into account as if they were still running, and the battery % drops faster than it should.
Here's a post from the creator of GPS Status, explaining the problem :
http://forum.xda-developers.com/showpost.php?p=23106668&postcount=491
There is also a small explanation from the author on the Google Play page for GPS Status, I'll quote :
"KNOWN FIRMWARE ISSUES (please do not report them):
- Samsung phones: Because of a firmware bug those phones may report extreme battery consumption for GPS Status (and for other programs using sensors) even if it is not running. This is harmless and no power is consumed! Just ignore it and let's hope that a future firmware upgrade will fix this."
So I'm still wondering if this is something we can fix, or if we have to wait for Samsung to correct that bug?
Click to expand...
Click to collapse
Now 1 year has past since your original post. I'm still experiencing the same problem on my Galaxy Note 2. :silly:
luzok said:
Now 1 year has past since your original post. I'm still experiencing the same problem on my Galaxy Note 2. :silly:
Click to expand...
Click to collapse
On my Galaxy S4, the problem seems to be gone, so hopefully it'll be gone on your device as well once Samsung releases the 4.2.2 update.
Sent from my GT-I9500 using xda app-developers app
Related
Greetings Fellow XDA fans
So I have a very annoying problem
I have noticed that my device has been getting large amounts of battery drain in the last few months after using any sort of navigation app on it..
Software that has been tested is:
Google maps, Sygic, Route 66, Drive and Walk.
I have installed "bad ass battery monitor" which seems to show that even when the navigation is closed the orientation sensor seems to still be active.
I have since wiped the device and re-installed checkrom but have had no improvement in the issue.
I have attempted changing kernels and modems as well.
I am currently in Neak 1.4.2 and Checkrom v6
It seems that the only way to stop the drain after running a navigation app is to restart the device.
To be clear... I can simply open navigation for a second and then close it and this huge drain will begin to occure untill a device reboot, Even though I have turned off GPS in the phone settings.
Freezing the app is not a solution ether
Any Solutions would be most welcome??
Regards James
You got Latitude app switched by any chance as that is a known battery drainer .
jje
Nope.. Made sure I didn't go near latitude because i heard it eats the battery big time.
Hello to all and thanks for your time.
First of all i did search about such a thread and could not find any which seemed to help including the stickies.
My problem is something on my room is misbehaving and chews trough the battery like hell.i need help identifying it.
To id my system :I'm on 9100xxlpw stock rooted no additional battery managers.
to describe the problem. I charged the phone to 100% and 5 hours later it was 50%.(i was sleeping so they're was no usage)
CPU spy reports 30 min of deep sleep rest 200mghz.
I'll add battery stats later.but basically Android system is chewing the batt. System appears to sleep but doesn't go deep sleep
Sent from my GT-I9100 using XDA
Install BetterBatteryStats. That should give you some clues as to what's causing the drain.
MistahBungle said:
Install BetterBatteryStats. That should give you some clues as to what's causing the drain.
Click to expand...
Click to collapse
Added Screen shots, please ignore media player and usb. I took screen shots as soon as I notice strange stuff but somehow system showed the screen shots duplicated so I deleted duplicates. Later I noticed I deleted the originals (most probably there was one c to begin with but gallery showed me duplicates, which is strange ).
New ones are taken after apprx. 1 hour of XDA browsing & listening to music.
emk2z said:
Added Screen shots, please ignore media player and usb. I took screen shots as soon as I notice strange stuff but somehow system showed the screen shots duplicated so I deleted duplicates. Later I noticed I deleted the originals (most probably there was one c to begin with but gallery showed me duplicates, which is strange ).
New ones are taken after apprx. 1 hour of XDA browsing & listening to music.
Click to expand...
Click to collapse
open BBS app then press soft menu key ones then select more and in that press Dump to file
then u see the log file in ur internal sdcard, post the same so that it can be checked to determine the wakelocks causing batt drain
Sun90 said:
open BBS app then press soft menu key ones then select more and in that press Dump to file
then u see the log file in ur internal sdcard, post the same so that it can be checked to determine the wakelocks causing batt drain
Click to expand...
Click to collapse
Gladly....
I think I have a possible culprit while searching for suspend_backoff
I found this http://forum.xda-developers.com/showthread.php?t=1697899 the phone model is different but I decided to turn wifi off to test and my battery consumption is almost like flat line when I'm not using the phone now (Data & synch is still enabled ). I do not know what causes this but I am not trough yet. I'd appreciate anyone to ID the source of the problem and how to overcome it (other than keeping wifi off) or should I switch to another rom
I have the same problem as you, but I think it is related to the (known and not yet solved) problem of the "dirty WiFi network", as it happens only with my office WiFi and not with my home one...
However in my case the problem is intermittent, while I always have the same high drain under the office WiFi, the major source of drainage changes, sometimes is suspend_backoff, other times it's deleted_wake_locks...
The_Flatline said:
I have the same problem as you, but I think it is related to the (known and not yet solved) problem of the "dirty WiFi network", as it happens only with my office WiFi and not with my home one...
However in my case the problem is intermittent, while I always have the same high drain under the office WiFi, the major source of drainage changes, sometimes is suspend_backoff, other times it's deleted_wake_locks...
Click to expand...
Click to collapse
I also had a feeling it might be wifi. I'm not sure what you mean by dirty wifi but. My home network seems to be suffering from dns problems. Also when I go to work one of my customers has a proxy while other has a unprotected wifi with web login. in both cases phone is able to connect to wifi but not to internet.
I also considered this might create some drain but it is too severe. I even thought my phone battery to be dead.
Greetings,
I had been using my Xperia Neo V with Cyanogenmod 10 (10-20130519-NIGHTLY-haida) for the last 2 months. It was all ponies and rainbows for me for the first 6-7 weeks.
Issue:
Now I'm facing with a random and ridiculous overnight battery drain issue since a week ago. Ridiculousness here is being referred to the amount of the drain (almost 60% overnight) and to the fact that there's no particular change of use of the phone by me,comparing with the days before. As you can see in the screenshots, the main actor here is "Operating System". I don't really know what this drain is related to, so I was not able to do comparisons of use.
Facts:
-Mobile Data was active but only at 2G
-Location services were off
-Bluetooth and all other possible signals were off
-No active apps, all were hibernated with Greenify
What might be the reason of this problem and what would you advice me to try?
Thanks in advance.
what kernel are you using? overclocked?
maybe you can try re-flash the rom
60% overnight is way high battery drain
You should try to see a pattern. Does it happen after specific usage "ritual" or just purely random?
It may be kernel bug/core system bug. Try dumping dmesg and logcat when it happen next.
I would start by trying to flash other kernel.
Install BetterBatteryStats (ther's an SDA thread); It will give you better info of what is draining your battery. In addition to that, you can post your logs in the thread (BBS thread) and they will provide better help.
Good luck
Edit: here's the link http://forum.xda-developers.com/showthread.php?t=1179809
Install wakelock detector app uninstall those... Try greenify too
Firstly we have to know what kernel are you using...
2.6.32.9 or 3.x.x version?
Hi there all, thank you for replies, and here are some extra info;
Fresh facts:
- Kernel: 2.6.32.9-FXP [email protected] #1
- Not overclocked
New observations:
So far I don't see any pattern as to what could possibly be the reason for this issue.
The last time I faced with this, the phone was fully charged and on 2G mode I left it on my desk (my wi-fi router was located next to it, keep it in mind so that it might be a clue coinciding with the BetterBattery logs I will reveal next) and after 3 hours, when I went to check if there were any calls, nearly 30% was drained. Comparing with the initial drain issue (which is a 60'ish% drain overnight) I can say it's the same issue within a proportionate period.
Well takin' a quick look at the BetterBatteryStatus report, drain was mainly caused by some wake thingy called "rx_wake". I don't really know much about all these wake calls in Android system but I googled it and reached to a brief conclusion that it's somehow related with Wi-fi connection. So I'm suspicious that maybe my Android system is perpetually sending wake calls related to a Wi-fi signal even when the Wi-fi mode is off on my phone (only relation I could make here is that I left the phone next to my wi-fi router)
I attach the screenshot and BetterBatteryStatus logs to this post, thanks in advance for your further comments.
Further comments, anyone?
Post the logs in BBS thread. There people has more knowledge and they can help you.
Issue Solved on Galaxy S - Will fit all I assume
Hi
I face the same issue from the day I install the ROM (CM 10.1.2)
I browse the Internet and found the issue
The issue is Wi-Fi and mobile network location
When it is on in this version it turn on the Wi-Fi not only on GPS request and No GPS status
You need to shout it down and issue solved
To change this setting:
System Settings -> Location access and disable the "Wi-Fi mobile network location"
Nachum
Hi all,
this is my very first post here on xda, so please forgive me if this is not the proper section for my thread. I searched for other thread about similar issues, but I didn't find anyone. I'm Italian, so I even hope to not being wrong in English writing.
I recently bought (on November 2014) an Huawei Ascend Y550-L01 (Android 4.4.4, EMUI 2.3, ROM B137), coming from a (Portuguese) Samsung Galaxy Y Pro GT-B5512. Soon I experienced a very strange GPS behaviour: GPS turns itself off. No problem in signal fixing, nor in quality or precision. It simply deactivates.
First I noticed this using the OruxMaps app (which works fine on many phones, even my old one), simply recording the track. Indeed, at the beginning the app was being killed (because of the integrated task-killer) when screen was off, but after setting it as a "protected" app, when I record a track, GPS works while screen is on and, if screen turns off, then most of the times (not always) GPS is deactivated from within Android settings.
I even received (from the purchasing time) some GPS errors while in the home screen... I don't remember exactly that error, but in a fast Internet search it was told being caused from the weather widget, precisely from the "actual position" setting. I deactivated it and added manually my town and those errors were gone.
Then I noted another strange behaviour: GPS turns off even in standby, during night. It is on "extreme precision" on evening and it's off at morning. Sometimes I notice these deactivation (in the notification menu or into the energy saving widget) while I'm using the phone (but always when screens is off), without any error or message popping out... It simply gets deactivated.
Any other experiencing this strange issue? What could be the cause? I sent a mail to official support, but they asked me to take the phone in a service point... I can't stay without phone, so I would like to avoid this if it's not strictly needed.
I think it's a ROM issue (said that even in the mail), but unfortunately still there is no alternative one (or at least I found none). I think also that (almost) every app that uses GPS suffers for the same behaviour I faced using OruxMaps.
PS: phone IS rooted by a couple of week, but I'm facing this issue from the first day.
What the hell is going on? Any help, idea or trying suggestion is appreciated...
Many thanks!
Up?
I also see strange problems on the Y550-L01 connected to GPS.
In my case the GPS does not disconnect completely, but during car navigation the signal gets lost from time to time (tested with different navigation apps).
This is only the case when the Y550 is NOT connected to the charger. If I connect it to the power supply, GPS works quite reliable and accurate!
For me this sounds like a software problem (maybe connected to a power saving mode?). I hope a firmware update will fix this soon.
Even to me this is a firmware issue. Before of your answer, I was really beginning to think it's a fault of my phone. Now that I'm not the only one, I went back to think of a bug.
If it is a power save problem, then try to use this app to stop the power save mode :
https://play.google.com/store/apps/details?id=eu.thedarken.wl
(ultra light : 35K, free/no adds)
"Wake Lock gives you control over the Android Power- and WifiManager.
For example, you can force the PowerManager to keep the screen on or have the CPU still running in standby mode or make sure the Wifi connection keeps running at full performance.
You can use it on any android phone or tablet.
Use it to keep the screen on in full brightness or dimmed mode during movies or slideshows.
To make sure the CPU is still running in the background doing your tasks when you press the standby button."
Thank you for the report.
It seems that the new huaweï G620S has the same GPS problem :
https://www.google.fr/search?q=G620S+GPS+problem+fix
Any news of an Huaweï update ? Hope yes...
magooz85 said:
Hi all,
this is my very first post here on xda, so please forgive me if this is not the proper section for my thread. I searched for other thread about similar issues, but I didn't find anyone. I'm Italian, so I even hope to not being wrong in English writing.
I recently bought (on November 2014) an Huawei Ascend Y550-L01 (Android 4.4.4, EMUI 2.3, ROM B137), coming from a (Portuguese) Samsung Galaxy Y Pro GT-B5512. Soon I experienced a very strange GPS behaviour: GPS turns itself off. No problem in signal fixing, nor in quality or precision. It simply deactivates.
First I noticed this using the OruxMaps app (which works fine on many phones, even my old one), simply recording the track. Indeed, at the beginning the app was being killed (because of the integrated task-killer) when screen was off, but after setting it as a "protected" app, when I record a track, GPS works while screen is on and, if screen turns off, then most of the times (not always) GPS is deactivated from within Android settings.
I even received (from the purchasing time) some GPS errors while in the home screen... I don't remember exactly that error, but in a fast Internet search it was told being caused from the weather widget, precisely from the "actual position" setting. I deactivated it and added manually my town and those errors were gone.
Then I noted another strange behaviour: GPS turns off even in standby, during night. It is on "extreme precision" on evening and it's off at morning. Sometimes I notice these deactivation (in the notification menu or into the energy saving widget) while I'm using the phone (but always when screens is off), without any error or message popping out... It simply gets deactivated.
Any other experiencing this strange issue? What could be the cause? I sent a mail to official support, but they asked me to take the phone in a service point... I can't stay without phone, so I would like to avoid this if it's not strictly needed.
I think it's a ROM issue (said that even in the mail), but unfortunately still there is no alternative one (or at least I found none). I think also that (almost) every app that uses GPS suffers for the same behaviour I faced using OruxMaps.
PS: phone IS rooted by a couple of week, but I'm facing this issue from the first day.
What the hell is going on? Any help, idea or trying suggestion is appreciated...
Many thanks!
Click to expand...
Click to collapse
Hi! Better post your question in our small Huawei Ascend Y550 thread. Maybe there someone of us can help.
If you understand German:
http://www.android-hilfe.de/huawei-...gation-unzuverlaessig-nur-im-akkubetrieb.html
These folks have the same proplem, but no solution.
Try it while a charger is attached.
Hi,
I'm having battery issues with OPX again, first it was a faulty battery, but now it looks like the there's something wrong with the settings. The device loses about a third of it's battery overnight, but when I look at the stats I can see that WiFi is always on and the device is always awake!
I have installed naptime as well and told it to ignore sensors (not that it matters as the device is not moving overnight) and to sleep even if connected to a charger etc. No matter what I try the device is always awake.
Is there a way to find out what is keeping it awake?
When I look at usage since last full charge there's nothing unusual there, just regular apps and single digit percentage numbers.
Thanks for your help!
System version?
I'm on Android Marshmallow, using Resurrection Remix ROM.
I'm not quite sure how to use the wakelock blocker, but I just installed Wakelock detector and it shows TripAdvisor as #1 on the list. I have it blocked in notifications, but I can't find anything related to TripAdvisor in wakelock blocker.
Is there any way to prevent apps from keeping the system awake, or should I just unintall TripAdvisor completely?
Not sure if I'm on the right track, but something is keeping the system awake and I need to find out what
OS3 with google back up turned off I get zero drain. Maybe 2-3℅ max over night. Also turned off automatic updates playstore. With just those two things off dont see drain anymore might just be lucky.
Well I think I'm back on normal drain. I uninstalled TripAdvisor, not using it except when I'm on holidays. I disabled the option to keep WiFi on even during sleep.
I used wakeblocker to block all weather/facebook entries, and I have two gmail accounts, one which is use a lot and one which I don't - so I blocked all wakelocks from syncing the account I don't use often.
Battery history confirms device is now correctly going to sleep and turning off WiFi. Automatic updates are still on.
I probably blocked too much, but I don't care anymore, I have 30% more battery every morning and that's good enough for me
crótach said:
Hi,
I'm having battery issues with OPX again, first it was a faulty battery, but now it looks like the there's something wrong with the settings. The device loses about a third of it's battery overnight, but when I look at the stats I can see that WiFi is always on and the device is always awake!
I have installed naptime as well and told it to ignore sensors (not that it matters as the device is not moving overnight) and to sleep even if connected to a charger etc. No matter what I try the device is always awake.
Is there a way to find out what is keeping it awake?
When I look at usage since last full charge there's nothing unusual there, just regular apps and single digit percentage numbers.
Thanks for your help!
Click to expand...
Click to collapse
Which ROM and recovery do you use?