Related
Hi all,
After noticing my battery was draining quickly, and then after reading this thread , I installed Android System Info to see what was draining my battery so fast. I notice that whenever I would turn on WiFi, the phone will never go to sleep , regardless of what I set the WiFi sleep policy to. After turning off WiFi, the battery still drains heavily.
The WiFi will shut off after 15mins (if you set it to "When screen turns off" or "never when plugged in"). However it seems to keep the CPU on causing it to drain down the battery.
It would seem that whenever WiFi is enabled, the Android system process creates a partial wakelock that does not go away even if you turn off WiFi, and even when the WiFi shuts off as per the WiFi sleep policy. The only way to resolve this is by powering off or rebooting the phone.
You can verify this in Android System Info by going into Battery-History-Other Usage-Partial Wake usage to see how much time the "Android System" process holding a partial wake.
I even did a factory reset on the device; and it is still happening so it doesn't appear to be any app that caused the issue. As I said, it works fine as long as I don't enable WiFi.
I already know of two users having this issue, but I'm wondering if folks having battery problems are going through this as well. Is anyone else having similar issues after using WiFi? I'm hoping someone will be able to identify what exactly is putting the wakelock on and we'll be able to find a fix for it. Other than not using WiFi at all or rebooting the phone after using Wifi.
Does someone know if there is a utility to drill down and see which process would be causing the wakelock? "Android System" doesn't give me any more details.
Any help would be greatly appreciated.
btw I'm not using any battery savers or task killers.
Update...i have the wifi sleep policy set to "never". Also have the network time sync disabled. I am no longer getting alot of battery drain from the Android System partial wakelock.
However, this means WiFi is on all the time....which burns up the battery as well.
Do you think this is a Samsung bug or Android that won't properly let the device sleep when the WiFi sleep policy is set to anything but Never?
Hoping someone at XDA can figure this one out.
I wonder the same thing...I lose about 20% during the night when the phone is not used for about 7 hrs. Not sure if that's normal or not
fldude99 said:
I wonder the same thing...I lose about 20% during the night when the phone is not used for about 7 hrs. Not sure if that's normal or not
Click to expand...
Click to collapse
Set the WiFi sleep policy to "Never" and reboot the phone. Shut WiFi off if possible overnight. You should notice a big improvement with battery life.
Devs - is there any way to see what is wakelocking the Android System process?
The WiFi sleep policy seems to be broke on the Captivate so hoping someone that really knows these things can help out to identify what is going on.
I've had wifi sleep policy to "never" since I got it. Turning off wifi when going to sleep will slow down battery drain when the phone is not in use all night?
fldude99 said:
I've had wifi sleep policy to "never" since I got it. Turning off wifi when going to sleep will slow down battery drain when the phone is not in use all night?
Click to expand...
Click to collapse
It should. Also setting the network to gsm only will use less battery. We need to find a way to see what process is holding that lock. Any dev experts out there please chime in.
fldude99 said:
I wonder the same thing...I lose about 20% during the night when the phone is not used for about 7 hrs. Not sure if that's normal or not
Click to expand...
Click to collapse
That is anything but normal unless you live where your cell signal is very weak. I see about 1% lose every 60- 90 minutes when idle. 10-12% when browsing or reading xda. Dont do heavy gaming do not sure what you should see there. Weak cell signal will kill battery life as can other factors.
I do have a weak cell signal at my house. I'll have to ck it in idle mode in my office, where I have a good signal to see if that makes a difference
On the other hand I just recently installed beautiful widgets and use it's live wallpaper. Also lookout..I'm thinking that could be a battery hog
I'm experiancing the exact issue in the op.
Android System is holding a partial wake lock of about 30-40%
My battery drains 40% overnight.
Are there any fixes for this?
The problem for me was definitely the stock email app continuously polling my Exchange server, killing the battery and my data plan. I resolved it by removing the Exchange server from the stock mail app, and by using Nitrodesk's excellent Touchdown app for mail instead. Touchdown isn't free but it's very good. And now my battery performance is back where to it was prior to the Gingerbread update.
Thanks, Google, for carefully testing this update before releasing it on the unsuspecting public (NOT). You caused a lot of grief for a lot of people.
FAIL!
DarrylGittins said:
The problem for me was definitely the stock email app continuously polling my Exchange server, killing the battery and my data plan. I resolved it by removing the Exchange server from the stock mail app, and by using Nitrodesk's excellent Touchdown app for mail instead. Touchdown isn't free but it's very good. And now my battery performance is back where to it was prior to the Gingerbread update.
Thanks, Google, for carefully testing this update before releasing it on the unsuspecting public (NOT). You caused a lot of grief for a lot of people.
FAIL!
Click to expand...
Click to collapse
I may be wrong, but isn't the default email app from Samsung?
Though, you are correct. I setup my work exchange on it as well and it is definitely a killer. Lately I haven't really been giving a **** and just charge my phone every night. However, I might look into this Touchdown app now.
DarrylGittins said:
The problem for me was definitely the stock email app continuously polling my Exchange server, killing the battery and my data plan. I resolved it by removing the Exchange server from the stock mail app, and by using Nitrodesk's excellent Touchdown app for mail instead. Touchdown isn't free but it's very good. And now my battery performance is back where to it was prior to the Gingerbread update.
Thanks, Google, for carefully testing this update before releasing it on the unsuspecting public (NOT). You caused a lot of grief for a lot of people.
FAIL!
Click to expand...
Click to collapse
for the stock email app you can configure the sync schedule so it doesn't continuously poll your exchange server overnight. i have my sync schedule set to push when i normally wake up and an hour after i get off of work. during off peak hours its set to manually update.
waldo98 said:
for the stock email app you can configure the sync schedule so it doesn't continuously poll your exchange server overnight. i have my sync schedule set to push when i normally wake up and an hour after i get off of work. during off peak hours its set to manually update.
Click to expand...
Click to collapse
how did you set this up??
In the last week or so I have picked up my phone three times and it has been dead.
The power button doesn't turn it on again.
I have to take the battery out and then restart it.
I'm running a rooted 2.35 JVT.
I have nothing untoward running ...
Settings
Sense analogue clock
DRM content
Software update
SnsService
Google Play Store
Samsung keypad
Apart from Angry Birds, there's almost nothing else, and nothing new for months except Bad Piggies.
deanbilly said:
In the last week or so I have picked up my phone three times and it has been dead.
The power button doesn't turn it on again.
I have to take the battery out and then restart it.
I'm running a rooted 2.35 JVT.
I have nothing untoward running ...
Settings
Sense analogue clock
DRM content
Software update
SnsService
Google Play Store
Samsung keypad
Apart from Angry Birds, there's almost nothing else, and nothing new for months except Bad Piggies.
Click to expand...
Click to collapse
Could it be a dead battery?
otherwise, tried to wipe and (re)flash a rom?
The battery is fine, and the ROM has been there for well over a year with no problems.
Finding the root cause of battery drain...
deanbilly said:
In the last week or so I have picked up my phone three times and it has been dead.
Click to expand...
Click to collapse
There are a number of standard steps to run through to find the root cause of battery problems, assuming the drain is caused by the OS or apps and not actually due to a physically failing battery.
I have been tracking a few battery issues myself recently and this is what I have learned from doing some reading on XDA:
There are two free apps on the app market that are typically used to diagnose battery problems:
Better Battery Stats
CPU Spy
I would recommend installing both apps. The third place to look is in the battery details in the system settings...sorry I can't remember what they look like on Gingerbread because upgraded to Jelly Bean a couple months ago, though I do remember there was less information in the stock battery info on Gingerbread.
IF you are not, indeed dealing with a physically dead battery, then the root of your battery drain is most likely caused by a background process or app that is keeping the processor in a partially active state even though the screen is turned off and one would assume the phone should not be using any power.
Android OS will automatically change the running speed of the processor in the phone based on the demand of the system. If only a few background tasks are running and updating information the speed might be 200 or 400 Mhz. If the system is running full out servicing a graphic intensive game the processor will likely be running at the full 1000 MHz speed. The speed of the processor will directly effect the battery drain.
The expectation is that when we turn the display off (not power down, just put the phone to sleep) the processor should need fewer resources and slow down, tending towards a state known as "Deep Sleep". At this point the processor us using very minimal amounts of power. Any app or process that is active in the background will prevent the processor from getting to Deep Sleep. The CPU spy app will allow you to check how much time the phone runs at various speeds. Once you install it and run it, then reset the timers in the menu and turn your screen off for about 10 or 15 minutes. Then 'refresh' the timers. Normally, you should see most of the time accumulated in Deep Sleep. There are standard background tasks such as syncing with the cell tower, updating time, mail, checking alarms etc. That will engage the processor momentarily but they should be relatively short compared to the deep sleep time. In my case, an errand process was keeping my phone at 100Mhz constantly preventing deep sleep.
Once you know that something is keeping the phone awake in the background, you can use Better Battery Stats to narrow down which process or app it is the cause. This app allows you to track the individual processes that are consuming the most time and preventing 'wakelocks'. Wakelocks are essentially an app preventing the sleep state and are very well explained in this post: http://forum.xda-developers.com/showthread.php?t=1827676
The battery info in the system settings can also be used to give clues though again, I can't remember how much detail was included in Gingerbread..
If your problem only started happening recently, then it could be a new app that you installed recently, a feature or setting you changed recently or possibly a recent update to an app that was already installed. Try to think back at any recent events that could have triggered a change in the system.
Common problem apps I have read about are:
- Facebook - seems to be bad at using lots of background processor time. (Don't run this app but reading several posts shows its a processor hog)
- Google Apps that sync - Gmail, Chrome (syncs browser history, tabs etc.), Google location stats.
The wakelocks link goes into a great deal of detail and is hugely valuable in nailing your issue down.
Good Luck, let use know via a post if you find the root cause...
Sorry, maybe I wasn't clear about it being 'dead'.
The battery is 100% or thereabouts, no problems ever with the battery.
The phone looked as though it was turned off, but wouldn't turn on again with the power button.
I have to take the battery out and put it back again, then it starts on the button.
I've cleaned the contacts, and it still happened.
User error.
Sent from my GT-I9100 using xda app-developers app
To me, it sounds more like a rogue process messing up power managing or response, but it's hard to tell what it could actually be.
For instance, you might come a cross a game that leaves your phone locked in max cpu frequency, draining the battery without explanation.
If it was me, I'd re-flash the rom from Odin, perhaps with an sd card wipe too.
Sent from horseback.
Hi.
My battery loses abot 2-3% per hour in idle. Is it some software or hardware problem? Or Tegra 4 specific issue? (No Wi-Fi, apps closed etc)
DarthVZ said:
Hi.
My battery loses abot 2-3% per hour in idle. Is it some software or hardware problem? Or Tegra 4 specific issue? (No Wi-Fi, apps closed etc)
Click to expand...
Click to collapse
Try to give it a cold boot.
Often that helps.
Sent from my superfast Asus Infinity TF701with Dock
Snah001 said:
Try to give it a cold boot.
Often that helps.
Sent from my superfast Asus Infinity TF701with Dock
Click to expand...
Click to collapse
Yeah seems to be a common android problem, some apps have runaway processes, others prevent deep sleep and I have also seen kernels lock CPUs. Shame Google can't put some effort into fixing it.
It's not an Android or a Google problem, it's the fault of the developer of the App which is causing this...
Since 4.3 I lose 0 % over night and I can use the table 1 hour every day for reading magazines, e-mail and angry birds for at least 5 days! Just great
Yezariael said:
It's not an Android or a Google problem, it's the fault of the developer of the App which is causing this...
Since 4.3 I lose 0 % over night and I can use the table 1 hour every day for reading magazines, e-mail and angry birds for at least 5 days! Just great
Click to expand...
Click to collapse
Google / Android should not let an app prevent deep sleep imo. Or runaway with resources. But yes you are right some responsibility has to be with the app developer for sloppy programming as well.
sbdags said:
Google / Android should not let an app prevent deep sleep imo..
Click to expand...
Click to collapse
In some cases it could be useful or even wanted. Think of an emergency app with running bluetooth and GPS. You would not want Android to kill the app in the middle of your tour
Cold boot didn't help and no draining app seems to be running(. Is a hardware issue possible? Is there a way to check it?
Here's a screeshot from System Panel (results of this night's battery bleed)
P.S. The back of the device seems a bit warm when I touch it...
DarthVZ said:
Cold boot didn't help and no draining app seems to be running(. Is a hardware issue possible? Is there a way to check it?
Here's a screeshot from System Panel (results of this night's battery bleed)
P.S. The back of the device seems a bit warm when I touch it...
Click to expand...
Click to collapse
You can wathc under "settings" -> "energy management" -> "energy table" which app it is and you can prevent it to wake the device up and to keep the device alive.
A few weeks ago I had a similar but stronger akku draining problem with the google apps but its gone (a pitty that I can´t say what it was: me doing this things in the energy management or google updating its app).
My google play-services still wake the device 869 times in 3 days.
New results. Very strange. No power consuming app seems to be running, but I still got -3%/hour.
Battery statistics shows that 80% most power is consumed by the screen. But it the tablet was in sleep all the time, so the screen was off...
DarthVZ said:
Battery statistics shows that 80% most power is consumed by the screen. But it the tablet was in sleep all the time, so the screen was off...
Click to expand...
Click to collapse
Check in Settings on "Energieverbrauchstabelle" (something like "engery consumption table") from Asus, there you can see the power consumption of the apps without Display. If you click on a specific app you can disable it to keep awake or wake tablet from deep sleep...
If that not helps you you should reset everything and go back to stock. Then you can check without installed additional apps if your "bleeding" still is there. Then install one app after another and wait between every single one to check which is the "bad app"...
So, in fact it was a hardware issue. I took another unit and it works perfectly. For now...
Anyway, thanks for your help, guys
With tablet off (deep sleep) I get 1 % battery loss in 12 hrs.
Best I have ever seen on an android device.
Snah001 said:
With tablet off (deep sleep) I get 1 % battery loss in 12 hrs.
Best I have ever seen on an android device.
Click to expand...
Click to collapse
Yep, now I've got the same thing. 1% instead of 30%
With my N4 and now N5, I use better battery stats to find the culprit of battery drain. But you have to be rooted
Sent from my Nexus 5 using Tapatalk
have you registered a asus account on the tablet?
i did and i got same issue was chewing through the battery like crazy.
go to settings and power consumption and it should say how many times it woke up the tablet or stopped it from sleeping
I have a Moto G 2014 (XT1064) running Android 6.0 that will not go into deep sleep. I could see that the CPU was never going into the deep sleep state even when the phone was not being used and no user apps were actively running in the background. This is causing abysmal battery life as expected. The phone was updated to Android 6.0 via regular OTA updates. I haven't flashed any third party ROMs onto it at all since I bought it.
The first thing I did to investigate was to unlock the bootloader (it was still locked since purchase prior to this) so that I could obtain root access to see what was going on. This also had the additional affect of wiping the phone to stock Andoird 6.0, which I had hoped would maybe solve the problem but it did not.
My first thought was that it was a user app that was holding a wakelock keeping the phone awake. I looked at the user and kernel wakelock counts via BetterBatteryStats and WakeLockDetector, but from what I can tell it is not any user app that is holding a wakelock at all. Instead it must be some kernel level app keeping the CPU awake, but I can't determine what it is. There isn't any single entry in the wakelock list that sticks out as the culprit.
I have done some other investigative tests such as turning WiFi off while the phone sits unused overnight. This did not have any effect as the phone still remained awake the whole time. I also repeated this test with the phone in airplane mode (WiFi + cellular radios off) and again it had no affect. From this I could only conclude that it was not the wireless radios that were keeping the phone awake. The wakelock counts also didn't show any evidence that WiFi, cellular or GPS were holding wakelocks.
Here are two screenshots I took of the BetterBatteryStats and WakeLockDetector apps showing the highest count kernel wakelocks over a roughly 17 hour period:
(I'd link them in properly but I am prevented from posting outside links on this forum until I have 10 cumulative posts...)
i.imgur.com/nPAY3S6.png
i.imgur.com/5VfgFv1.png
You can see that the phone has been awake 96% of the time during this period, and that the highest count kernel wakelocks are from "event8-1877", "event9-1877", "qpnp_soc_wake" and "qpnp-vadc-e4a28400". I could not find any information as to what these entries mean or what they're related to. Whatever they are, they appear to have abnormally large wakelock counts which leads me to believe that they are related to this problem. The other thing that puzzles me is that the total time for the top four entries in that list only sum to about 2 hours, yet the phone has been awake for almost 17 hours within the same period.
If anyone has any idea about this I'd appreciate the help. I may be completely wrong about the root cause here but I'm running out of ways to debug this.
Updating this thread to say that I have also tried re-flashing stock Android 6.0 using the firmware files linked from this thread (in my case I used XT1064_TITAN_RETCA_6.0_MPB24.65-34_cid14_CFC.xml since I am in Canada). I still experienced the same behaviour where the phone would rarely enter deep sleep. It seemed to be marginally better after re-flashing, going into deep sleep about 10% of the time over a 12 hour period or so, where as before it was only going into deep sleep about 4% of the time during the same period. This still doesn't solve the problem though.
Now I am thinking about downgrading to stock Android 5.0.2 and see if that fixes the problem since I don't know how else to diagnose this.
Anyone using battery monitoring apps like BBS or GSam, can you share some of your stats here? I'm trying to figure out whether the seemingly massive amount of wakelocks I'm having is normal or not. The biggest problems seem to be coming from the kernel itself. BBS shows a lot of kernel wakelock time, and GSam consistently lists the kernel as the highest drain in its app sucker screen. Also, the Phone app seems to be waking the device a lot since upgrading to .5.51, which wasn't a problem on .3.374.
I've attached some screenshots that illustrate the problem. I'm already using ForceDoze and Greenify, which have been enabled via ADB, and I've restricted background activity and data for the vast majority of my apps. I'm really hoping there's something I can do about this given that it's impossible to use another kernel (LB and none available for this phone anyway). I've software repaired/clean flashed 3 times.
My battery drain is actually not bad at under 4%/hr (combined screen on/off) and about 1%/hour with the screen off overnight. Today I've logged over 4.5 hours SOT in a period of 17 hours and am sitting pretty at 36%. That's better than any phone I've ever used. But I worry that all the wakelocks are using my phone's CPU, raising its temperature, and might contribute to faster battery degradation.
Also, this is with bluetooth off and my Pebble not paired, but battery drain becomes substantially worse with that setup. My idle drain triples with my Pebble connected. I'm trying to troubleshoot one issue at a time and want to nail these wakelocks before moving onto the bluetooth issues.
If your battery stats looked like mine and especially if you figured out how to fix it, please share!
Given that Sony ended .5.51 deployment prematurely and is currently rolling out .8.49, I think you should update to .8.49 (or wait until your region gets the update if you don't have it yet) then recheck if your problem still persists.
Pouring time and resources into a version that Sony is no longer pushing isn't that great of an investment, especially since it's possible that it was fixed in .8.49.
mhaha said:
Given that Sony ended .5.51 deployment prematurely and is currently rolling out .8.49, I think you should update to .8.49 (or wait until your region gets the update if you don't have it yet) then recheck if your problem still persists.
Pouring time and resources into a version that Sony is no longer pushing isn't that great of an investment, especially since it's possible that it was fixed in .8.49.
Click to expand...
Click to collapse
Everything except the phone app using more battery was the same on .374. And I fixed that after force stopping the phone app and rebooting. I've been trying to troubleshoot this for weeks but just upgraded to .5.51 a couple of days ago. I will flash it when it comes out for Customized UK, but I don't think .5.51 is the root of the problem.
(Oh cool, Xperifirm actually shows .8.49 available for Customized UK now. Time for some flashing!)
Edit: I'm seeing the same degree of wakelocks so far on .8.49.
Update: The battery drain from "phone" is actually Android System. There's a bug in Oreo where sometimes Android System is showing as Phone/RCS in the battery stats. Doesn't explain why Android System is using so much battery though.
https://www.reddit.com/r/GooglePixel/comments/7f7jk2/pixel_2_rcs_battery_drain_is_there_any_way_to/
https://www.reddit.com/r/GooglePixel/comments/7edcav/rcsservice_draining_battery/
https://forums.oneplus.net/threads/rcs-draining-battery.657535/
https://forums.oneplus.net/threads/rcs-service.666045/
https://forums.oneplus.net/threads/found-way-to-end-rcs-sucking-battery-after-oreo.659711/
So I managed to get a lot of my battery drain figured out, but a few things are still bothering me.
1) Google Play Services and Android System and/or Phone (see my last post) are using the Significant Motion Sensor to wake my device constantly.
2) Sony's smart charger (com.sonymobile.smartcharger) is waking my device. I'm assuming this has something to do with Battery Care, which I find to be a useful feature. But why does it need to continue sending alarms to wake up our phones when not plugged in?
I've attached 2 screenshots from Better Battery Stats showing the first issue (Sensors/Play Services and Phone) and 1 showing the second (Alarms/Smart Charger). Note the "wakeup=true" and long times recorded for Significant Motion. This held true when I had my phone sitting face-down on a table for 6+ hours to do battery testing earlier.
Anyone else who uses battery monitoring apps: have you noticed any similar issues?
jrbmed08 said:
So I managed to get a lot of my battery drain figured out, but a few things are still bothering me.
1) Google Play Services and Android System and/or Phone (see my last post) are using the Significant Motion Sensor to wake my device constantly.
2) Sony's smart charger (com.sonymobile.smartcharger) is waking my device. I'm assuming this has something to do with Battery Care, which I find to be a useful feature. But why does it need to continue sending alarms to wake up our phones when not plugged in?
I've attached 2 screenshots from Better Battery Stats showing the first issue (Sensors/Play Services and Phone) and 1 showing the second (Alarms/Smart Charger). Note the "wakeup=true" and long times recorded for Significant Motion. This held true when I had my phone sitting face-down on a table for 6+ hours to do battery testing earlier.
Anyone else who uses battery monitoring apps: have you noticed any similar issues?
Click to expand...
Click to collapse
I'm with you on RCSService being main culpirt for me. No I don't think it's a bug, it actually does use lots of battery. I listen to 3+ hours of bluetooth music a day and when I saw that RCSService was using more power than my bluetooth, then I thought it was time to experiment. So I uninstalled Carrier Service and RCSService and suddenly my battery life jumped by 20%. There was something in the November update to these services that made them go nuts. Several people have noticed a jump in battery usage, but most people, myself included, thought it was down to the new firmware. Uninstalling these 'features' has made no difference to SMS for me, other than I don't get a read confirmation.
I don't know about smart charger, sorry.
Pretty sure the proximity sensor is always on and that must use some power, but I don't know what that would be called in BBS.
Didgesteve said:
I'm with you on RCSService being main culpirt for me. No I don't think it's a bug, it actually does use lots of battery. I listen to 3+ hours of bluetooth music a day and when I saw that RCSService was using more power than my bluetooth, then I thought it was time to experiment. So I uninstalled Carrier Service and RCSService and suddenly my battery life jumped by 20%. There was something in the November update to these services that made them go nuts. Several people have noticed a jump in battery usage, but most people, myself included, thought it was down to the new firmware. Uninstalling these 'features' has made no difference to SMS for me, other than I don't get a read confirmation.
I don't know about smart charger, sorry.
Pretty sure the proximity sensor is always on and that must use some power, but I don't know what that would be called in BBS.
Click to expand...
Click to collapse
Thanks! I should clarify that when I say it's a bug, I believe something is using a lot of battery, but I don't know that it's necessarily Phone/RCS, because it shows up randomly as either that or just Android System. I think it might be something within Android System but being labeled as Phone or RCS. (Edit: Or the other way around; it could be 100% RCS and sometimes shows up as Android System because the phone is part of that umbrella.) I could be wrong but based my judgment on the links I posted above.
That being said, I disabled Carrier Services on your recommendation in the other thread because my carrier doesn't support VoLTE, VoWiFi, or RCS, I've never seen a "delivered" message, and I don't even use the Google Messages app anyway (I use Texra for SMS and keep Messages disabled). So like you, I don't need these services. And I do think there's been an improvement. Might be time to go through the rest of what you recommended via ADB. The only thing that concerns me about doing that is that I'll have to factory reset if I ever switch carriers and want those services, but I guess that's a small price to pay and an unlikely scenario anyway.
The smart charger thing is just weird. It shouldn't need to constantly check whether I'm charging since it kicks in when you plug in. Yesterday I disabled battery care during the day and re-enabled it at night to charge, and I had the best battery life since I've owned the phone: 4.5 hours of SOT over 18 hours off the charger with 30% remaining. I may have to look at idle drain with battery care disabled. I like the idea of battery care, but if it's draining my battery then it just defeats the purpose.
Regarding sensors, BBS has its own category for proximity sensor; this is a separate sensor for significant motion. Somehow Google Play Services and either Phone/RCS or Android System are using that particular sensor all the time. And not just listening to it, but causing lots of wakeups and doing so while the device is sitting on a table all night. I can only deduce that it's somehow seeing motion when there isn't any.
jrbmed08 said:
Regarding sensors, BBS has its own category for proximity sensor; this is a separate sensor for significant motion. Somehow Google Play Services and either Phone/RCS or Android System are using that particular sensor all the time. And not just listening to it, but causing lots of wakeups and doing so while the device is sitting on a table all night. I can only deduce that it's somehow seeing motion when there isn't any.
Click to expand...
Click to collapse
Do you have 'On Body Detection' enabled in smart lock? That would force the phone to affirm if it's moving/stationary regularly and quite often.
Didgesteve said:
Do you have 'On Body Detection' enabled in smart lock? That would force the phone to affirm if it's moving/stationary regularly and quite often.
Click to expand...
Click to collapse
I never enabled that from the start, but just checked in case Google did something, and it's still off.
I also checked my app permissions, and the only ones with access to body sensors are Google Play Services and Tasker. None of my active Tasker profiles require the significant motion sensor. One of them does use the orientation sensor to turn the speakerphone on when it's face-up during a call, but I tried disabling that profile and the stats didn't change.
Maybe I have a messed-up accelerometer...do you know of a way to test that? (Edit: Found it in the Support app - my accelerometer, gyroscope, and proximity sensor are fine)
I think I might head to the Sony Mobile forums with the smart charger issue for that matter. It may be a bug that affects all phones with Qnovo features, or maybe they could at least give me an explanation.
jrbmed08 said:
Might be time to go through the rest of what you recommended via ADB. The only thing that concerns me about doing that is that I'll have to factory reset if I ever switch carriers and want those services, but I guess that's a small price to pay and an unlikely scenario anyway.
Click to expand...
Click to collapse
Correct me if I'm wrong, but couldn't you just "reinstall" those services via the same adb commands? Where you typed uninstall, just replace with install?
Maybe, but I don't know where I would be installing them from...? Since I don't have a backup of the package. I uninstalled a bunch of stuff via adb before and it didn't return with a dirty reflash. I had to flash userdata. So that's all I'm going by.
I'm not sure of the actual technical mechanics, but I believe uninstalling system apps doesn't actually remove the package from the system image, so you can reinstall them at any time.
I think it's like taking down a sign on a store, the actual store is still there, just all references to it are no longer there, so to the OS it's not listed - "uninstalled".
Hello - was there any solution found for this issue?
jrbmed08 said:
Anyone else who uses battery monitoring apps: have you noticed any similar issues?
Click to expand...
Click to collapse
Hi there, what was the final solution to your issue?
Dean F said:
Hi there, what was the final solution to your issue?
Click to expand...
Click to collapse
I gave up. I still have a ton of wakelocks. GSAM shows a bunch of them even when my phone is supposedly dozing. My battery life is OK, not nearly as great as I hoped I'd have with this phone, but it gets me through the day so I've just been living with it. I have noticed better battery on the latest firmware (July patch) than June. I also got rid of the RCS stuff, which helped a bit. And finally I traced a lot of my drain to an app I was using called "hide running in background notification" which the last few firmwares can do natively.
(Edit: Sorry for missing your previous post!)
Edit: I was sadly mistaken about better battery on the July patch. The battery is only better if I'm not on wifi. I posted in the wifi drain thread about it just now.