I was losing no more than 1% per night until three nights ago. I have also tried wiping the cache partition (yesterday) to no avail. "Android OS" is listed as the top resource hog, and it looks like it is not letting the phone sleep.
It looks like "keep awake" under the Android OS entry in the battery is going for the entire time the phone is on.
Suggestions?
{
"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"
}
hifiaudio2 said:
I was losing no more than 1% per night until three nights ago. I have also tried wiping the cache partition (yesterday) to no avail. "Android OS" is listed as the top resource hog, and it looks like it is not letting the phone sleep.
It looks like "keep awake" under the Android OS entry in the battery is going for the entire time the phone is on.
Suggestions?
Click to expand...
Click to collapse
Something isn't letting your phone sleep/doze.
You need the check which applications are running.
WiFi scanning is on perhaps?
Exchange services? That was my issue. I had to give up on using gmail for my exchange account and download Microsoft outlook for android.
Thanks I will check those. Wifi scanning is likely on, but that has been on for months now... not sure why the sudden change. May have to just wipe the phone and see what happens. Google maps, when giving directions on my car Bluetooth, has also started cutting off the last 30% or so of the voice guidance every time. Maybe a wipe will fix that, too.
hifiaudio2 said:
Thanks I will check those. Wifi scanning is likely on, but that has been on for months now... not sure why the sudden change. May have to just wipe the phone and see what happens. Google maps, when giving directions on my car Bluetooth, has also started cutting off the last 30% or so of the voice guidance every time. Maybe a wipe will fix that, too.
Click to expand...
Click to collapse
Impossible to tell what's causing the wakelocks with root. Best you can do is educated guess.
something was holding your device awake literally the entire time
hifiaudio2 said:
I was losing no more than 1% per night until three nights ago. I have also tried wiping the cache partition (yesterday) to no avail. "Android OS" is listed as the top resource hog, and it looks like it is not letting the phone sleep.
It looks like "keep awake" under the Android OS entry in the battery is going for the entire time the phone is on.
Suggestions?
Click to expand...
Click to collapse
Post image of battery use percentages... would be helpful for people here to diagnose
Sent from my Nexus 6P using Tapatalk
Well I ended up doing a factory reset. All was good at least for the first night. I will update and troubleshoot more if needed.
Bluetooth on?
Related
My phone's battery is constantly being drained by one thing or another. I shut off location services, and Google Search becomes the problem. I shut off Google Search, and Play Services drains the battery. I uninstalled Play Services and now my battery use looks like this.
{
"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"
}
I don't know what to do. Is it time for a factory reset? I am rooted, but stock. I assume I would have to unroot before a reset.
Give us some specific numbers and we might be able to help. The screenshot you put up means nothing. Either more info or BBS screenshots (or maybe even Wakelock Detector)
Yeah, hop on Android Market. Download Wakelock Detector and the next time you pull it off of the charger leave it be for a couple hours. It'll keep track of what is keeping your phone from sleeping. For example your phone can be awake without the screen being on, and that's probably where the issue lies. Make sure it's set to CPU Wakelock. Then come back with some screens of that. We'll get a better idea of what we me be able to do to help.
Sent from my Nexus S 4G using xda app-developers app
I've been using Wakelock Detector, but I guess I am unable to interpret the results. They seem inconsistent. My phone was recently rebooted and is being charged, but I will post a shot of WD later. The top result earlier today was Google Music (which I almost never use). It did not seem like a terribly long period of time it was on, though. I think it was less than 6 minutes. I turned off sync for it regardless.
I assume BBS BetterBatteryStats. I'll go purchase it.
Thanks for the help. I do appreciate it.
Hm... How long have you had the phone? If you're in the grace period still, it couldn't hurt to replace it. Every now and then, defectives slip through. Knowing how well the G2 battery is supposed be, I do it very unusual that you're suffering a hit in that department.
Edit: I still think there has to be a rogue app somewhere. Especially with android system taking so much of your battery.
Sent from my Nexus S 4G using xda app-developers app
Battery is almost full, doesn't seem odd to me with phone sleep. Need wakelock info form BBS.
Recently my phone has been dying really fast. I checked battery stats and Android system is what's killing it. I've tried everything to make it stop and nothing works. Does anyone else have this problem? Any idea on how to stop this? PLEASE HELP.
{
"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"
}
Boot into recovery then do clear cache partition. Should clear out whatever is causing this issue unless that app is still in there
Sent from my SM-N900V using xda app-developers app
ecritl ice
Clearing cache could and probably will get rid of it. But I bought an app called Better Battery Stats, (id link it but im new) which tells you exactly what is waking up your phone while its off. Chances are you have a rouge app, that is just destroying your battery, as opposed to a system-wide problem. That app will tell you what it is.
Ignore the battery charging cycle. I'm just showing you what I have to go through also and somewhat fixed the problem.
I have and still have %50 android os usage. Before I did this mod, the android os was the highest usage and showed awake time as well. It was killing my battery from a full charge it drained down to zero in 12 hours with 1hr screen time and the phone never being in a deep sleep. It was aggravating because I wiped my phone so many times, tried different roms, took sim card out, no wifi, wiped cache, and wiped phone with nothing installed. Still the high android still persist and no deep sleep. I'm thinking it has to be Verizon doing something or Google that is waking up the phone.
Some how I fixed it or maybe the OTA fixed it. I odin mj7 and updated to the newest version and flashed beans. From the screen shot it shows my android os still high... but with no awake time. So my phone is actually in deep sleep mode now. It's weird but I semi - fixed it. I'm still clueless on why it's so high when previously screen time usually trumps as the number one usage spot. I still have no answer to this reason but I hope it helps a bit to fix this issue.
View attachment 2467520
Sent from my SM-N900V using XDA Premium 4 mobile app
HEY same exact thing here. Android OS usage going nuts here. I personally think its related to certain wifi / router setups.
When im on 3g/4g all day, it doesnt happen. On the days that I am stuck at home on wifi, the android OS usage starts again.
Ive already Odin'd back to MI7, took ota to MJE, rerooted, installed beans b5 and its still happening.
I think its a bug with samsung / verizon wifi. Many times I will wake up my screen and see my GPS / Wifi being used for no apparent reason even with all location services turned off. I also notice my wifi indicators being on when i turn my screen on. Then after i turn my screen on and sit at my home screen for a few seconds. It all magically stops.
Mind you, this is with no apps installed other than what is in beans stock and nova launcher.
You guys should monitor while off wifi and see what happens. It was the first thing that struck me when i was on a road trip for 12 hours. My battery life was exceptional. If it is the wifi causing problems, i wonder what it is specifically.
Simply clearing the cache fixes this for me every time. I usually do it once every few weeks.
Settings..storage..tap on cached data and hit clear.
Hi,
Ever since I upgraded my I9505 to 4.4.2 I've noticed that one of my key battery consumers was Android System (not so on 4.3 or 4.2.2, or whatever I was running before). Right now I'm on the latest DBT ROM, but still the same issue. I've been reading numerous threads on this, tried lots of things even formatting my SD card from within the phone, but still same story. I have Google location services disabled (major issue before), Google Now hot word detection is off, S Voice voice activation is off - nada. I am running stock so getting a wakelock report is a no go. I get decent time on the phone (up to 18 hours per charge), but still want to figure out why Android System is using so much battery (it seems to be CPU time related anyway - phone is properly entering deep sleep when it should). Below is a screenshot of what my battery graph looks like about 2 hours after unplugging the phone from the charger with normal usage. Thanks for ideas!
{
"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"
}
Any ideas? In the meantime I've done a factory reset, disabled Samsung's bundled apps (e.g. S Voice), tried disabling location services altogether - still same story nothing seems to help. In OS monitor I see a constant Android system activity between 1-9%. Average is around 2-3% but it never stops.... Sadly with the KitKat permissions being what they are I can't get more details.
Here's a graph from today 3 hours after a full charge with minimal phone usage:
Clearly something is going wrong here...
Breach1337 said:
Any ideas? In the meantime I've done a factory reset, disabled Samsung's bundled apps (e.g. S Voice), tried disabling location services altogether - still same story nothing seems to help. In OS monitor I see a constant Android system activity between 1-9%. Average is around 2-3% but it never stops.... Sadly with the KitKat permissions being what they are I can't get more details.
Here's a graph from today 3 hours after a full charge with minimal phone usage:
Clearly something is going wrong here...
Click to expand...
Click to collapse
Hi ,
With this information is hard to tell what is going on , you need an app like Better Battery Stats
http://forum.xda-developers.com/showthread.php?t=1179809
Let it run for 3 to 4 hours at least and then see who is running wild
Review you settings , location , mail , FB......
Thanks. As I am running non-rooted 4.4.2 I can only see kernel wakelocks which look normal to me:
Breach1337 said:
Thanks. As I am running non-rooted 4.4.2 I can only see kernel wakelocks which look normal to me:
]
Click to expand...
Click to collapse
33 min is not enough time to see what is going on let it run for 3 or 4 hours ...
Upgraded to I9505XXUGNK4 (DBT) today and it looks like it helps!
Breach1337 said:
Upgraded to I9505XXUGNK4 (DBT) today and it looks like it helps!
Click to expand...
Click to collapse
For posterity's sake - the firmware didn't fix the problem. My Android System, and to some extent Android OS, usage was still pretty bad. After hours of trying various things I've got it though - in my case I had to disable Samsung's Unified Daemon (EUR) and now once more my top consumers are Screen and phone idle! Hope this helps folks.
The HandleMediaEvent sub service of Android System is randomly causing solid bar wakelocks for me. Rebooting the device usually fixes the issue temporarily. The only thing I could find after some googling on the issue was this older thread on a GS4 http://forum.xda-developers.com/showthread.php?t=2483630
it seemed to think the issue could be caused by bluetooth devices. I Have a Moto 360, and use bluetooth earbuds almost everyday. But, I'd think there would be more reports of this problem if it was caused by that
{
"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"
}
My stats got reset on WLD so I dont have a screenshot showing it was the HandleMediaEvent service.
Grims said:
The HandleMediaEvent sub service of Android System is randomly causing solid bar wakelocks for me. Rebooting the device usually fixes the issue temporarily. The only thing I could find after some googling on the issue was this older thread on a GS4 http://forum.xda-developers.com/showthread.php?t=2483630
it seemed to think the issue could be caused by bluetooth devices. I Have a Moto 360, and use bluetooth earbuds almost everyday. But, I'd think there would be more reports of this problem if it was caused by that
My stats got reset on WLD so I dont have a screenshot showing it was the HandleMediaEvent service.
Click to expand...
Click to collapse
i have the exact same problem anyone got an advice?
I found out what causes it, but not a solution. using a button on a bluetooth device to pause/play/skip/voulme etc, can sometimes cause the wakelock.
Grims said:
I found out what causes it, but not a solution. using a button on a bluetooth device to pause/play/skip/voulme etc, can sometimes cause the wakelock.
Click to expand...
Click to collapse
I also checked out my battery behaviour this night and was very disappointed. Although my phone was in flight mode and every peripherals and services shut down, today morning my phone was crying for energy. So I made a quick investigation in my power diagram and found out, that "Android OS" requested a wakelock during the whole power-on time. So I installed "CPU Spy" to check in which states the phone was really over the whole charging period. I couldn't believe my eyes. Although the kernel should do it's job good, cause most of the CPU times are in lower freqeuncy states, the deep sleep mode was never activated.
Therefore I installed an app called "Wakelock Detector" to check out which apps could cause that. I found out, that S Health had a big amount of wakelocks and also active-time, so the first thing was to disable S Health. After some minutes I checked back, but nevertheless still no deep sleep time in "CPU Spy".
So I searched around and found another one arguing about the wakelocks and that they could be the products of some programming issues concerning WiFi. The should be gone, after turning off WiFi and rebooting yout phone. And it seems that he was right. I waited some time and hooray, "CPU Spy" listed the phone state "Deep Sleep" the first time as an active state and also with the major active-time. So at least that was some step ahead. (I have to remark, that S Health was already unfrozen at this time, so S Health should not be responsible in any way.)
The next step was to reactivate WiFi, leave it on and set the phone on standby. After some time I checked back again the phone showed even more deep sleep time. So that was an improvement. I reactivated everything and waited some time... Deep Sleep all over the time. Can't figure out for now, if it was S Health, WiFi, or anything else that caused the wakelock for sure. At least the reboot helped. I'll check that out on a long-term test, maybe I get some further conclusions.
Hey everybody!
I have noticed some strange behavior with my TicWatch Pro 3 Ultra GPS.
During the day, the power consumption is moderate and absolutely acceptable. However, the power consumption is significantly increased at night.
Looking for the cause, I found out with the help of Battery Historian that the GPS is obviously the reason.
When I go to sleep, I always turn on Airplane Mode on the watch to further limit all network activity and save power, and turn it off accordingly after I get up.
I have attached a screenshot from Battery Historian. I have inserted the vertical red bars as markers, when the Airplane Mode was activated or deactivated by me.
The process that activates the GPS seems to be Wear OS itself (com.google.android.wearable.app).
I had also already reset the watch to factory settings.
The first night, interestingly, GPS is only ever activated briefly. Whereas on the second night GPS is almost constantly active.
Before the factory reset, the GPS behavior looked similar.
So far, I had always left GPS activated on the watch, since I assumed that it would also be deactivated when Airplane Mode was activated. However, a look into the settings told me that this is not the case.
Ultimately, I do not understand why the watch wants to access the GPS constantly and almost permanently when Airplane Mode is active.
{
"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"
}
I've exactly the same problem. I was getting crazy as the watch consumed 3 time more battery overnight with airplane mode than during the day.
Maybe the problem is related to not having a connection to the phone. As far as I know, when the watch is connected to the phone, it doesn't use its own GPS. I assume there must be some internal process (like updating the weather) that tries to get GPS signal.
I'll try different setting combination on the next nights
Dear friends,
I came here for the same exact issue and I'm glad it is a known bug and it was detected.
I'm asking to the OP which is the app you use to have that battery stats. I need it also
Thanks in advance
mrasquinho said:
Dear friends,
I came here for the same exact issue and I'm glad it is a known bug and it was detected.
I'm asking to the OP which is the app you use to have that battery stats. I need it also
Thanks in advance
Click to expand...
Click to collapse
I use this one:https://play.google.com/store/apps/details?id=strange.watch.longevity.ion
Same issues here, can anyone post the link to ticwatch FB on this issue?
I don't think the affected WearOS version is something we can really opt-out ...
alienmind said:
Same issues here, can anyone post the link to ticwatch FB on this issue?
I don't think the affected WearOS version is something we can really opt-out ...
Click to expand...
Click to collapse
https://m.facebook.com/groups/2952679438107711/permalink/8447345481974385/