Related
Hi guys,
I have had the phone for a while, and it is perfect. The only issue I have had (same as others), is the battery sometimes seems tempremental. However, I noticed this weekend, it really lasted as expected.
I check every morning, the phone would stay awake for hours (disabled app after app, uninstalled etc, factory reset), same problem persisted. A lot of the apps (Enterprise service for example) like to override their deactivation, which is always fun.
Anyway, I realised that I connect my bluetooth headset to listen to music, and once I disconnect it the wakelock doesn't go away (I am not rooted, but based on two weeks of observations this is 90% confident hunch). Only restarting the phone, would cause the activity to stop and normal battery drain to resume.
So, I reach out to you guys, is there a way to stop the bluetooth from somehow remaining active after I disconnect the device, or whatever wakelock affects it. I am not ready to root this phone yet, but if there is no other option...
TL;DR connect my bluetooth headset every morning, keeps the phone awake even after disconnecting, (and turning bluetooth off). can you please help?
Thanks...
Looks you're on your own with that problem. I keep BT on at all times, connecting&disconnecting flawless to the hands-free of my car as well as the BT headset in my office. No such thing like battery drain anywhere.
Raza46 said:
Hi guys,
I have had the phone for a while, and it is perfect. The only issue I have had (same as others), is the battery sometimes seems tempremental. However, I noticed this weekend, it really lasted as expected.
I check every morning, the phone would stay awake for hours (disabled app after app, uninstalled etc, factory reset), same problem persisted. A lot of the apps (Enterprise service for example) like to override their deactivation, which is always fun.
Anyway, I realised that I connect my bluetooth headset to listen to music, and once I disconnect it the wakelock doesn't go away (I am not rooted, but based on two weeks of observations this is 90% confident hunch). Only restarting the phone, would cause the activity to stop and normal battery drain to resume.
So, I reach out to you guys, is there a way to stop the bluetooth from somehow remaining active after I disconnect the device, or whatever wakelock affects it. I am not ready to root this phone yet, but if there is no other option...
TL;DR connect my bluetooth headset every morning, keeps the phone awake even after disconnecting, (and turning bluetooth off). can you please help?
Thanks...
Click to expand...
Click to collapse
You are not alone!! Please take a look here: http://forum.xda-developers.com/z3/help/bt-wakelock-z3-deep-sleep-t3059084
Unfortunately lollipop did not solve it.
I still have no idea what is causing it! It does not look to be a popular issue, this is why I hope it is an app. It could also be an HW issue.
---------- Post added at 03:44 PM ---------- Previous post was at 03:43 PM ----------
sxtester said:
Looks you're on your own with that problem. I keep BT on at all times, connecting&disconnecting flawless to the hands-free of my car as well as the BT headset in my office. No such thing like battery drain anywhere.
Click to expand...
Click to collapse
It could be you've not noticed it!!
This is killing my battery. Is anyone having this issue?
Nada boss.
Sent from my XT1254 using Tapatalk
Well that's the top on my list of my battery usage for the last 4 days even after rebooting the phone couple of times. The only way to prevent it is shutting down the BT but I don't want to manage my BT all the time.
also having this issue
Just saw your post. I am also having this issue. To test, with BlueTooth on and the phone idle with screen off, I was burning 3-4% an hour. Battery drain was worse if I actually used the phone. Turn off BT and I'm around 1-1.5% an hour. The keep awake percentage with BT on was something like 75-80% awake (the bar on Battery Info looked almost solid). Now that BT is off, the phone wakes up a few times an hour when idle/screen off.
I previously had a Droid Razr Maxx HD and kept BT on all the time with no real effect on battery drain. I had BT paired to my car radio for hands free and to a Motorola Keylink (using the Moto Connect app) for SmartLock. I'd like to keep BT on all the time for the KeyLink/SmartLock feature in Lollipop, but not with that kind of battery drain.
Have you had any luck figuring out how to get BT to work without the Keep Awake?
Has anyone find out what's causing this?
I'm having the same issue - seems to have just started within the past week or so - anyone know what's going on?
Yeah I am manually turning off my Bluetooth when not in use again. Haven't had to do this on any phone since ICS.
Sent from my XT1254 using Tapatalk
The same issue just started for me today. I may have found the cause and (at least temporary) solution. My phone is no longer constantly awake and Bluetooth awake time has stopped increasing.
Cause: power cycling the phone while Bluetooth is on
Solution: turn bluetooth off before power cycling the phone
This is just a rudimentary discovery, but if people can confirm if this also works for them we can maybe get closer to a real cause/solution for this.
edit: False alarm. Bluetooth is now keeping the phone awake again, even without a reboot. Gonna try changing around smartlock settings to see if this helps.
Two days ago, I disabled the settings to let smartlock unlock my phone when in range of my watch. I did not reboot, however. That evening, the phone ran out of power and shut down. Since then, it's been fine. Phone still shows awake all the time, but the battery usage has been much more reasonable (20 hours use out of it vs. 12). Once I verify that it's working reliably, i'll re-enable each setting separately to try to figure out what's going on.
"Bluetooth Share" draining battery...even after full wipe and flash from 5.1.1 to 6.0
Hey guys - for the last few weeks I've noticed "Bluetooth Share" as the top culprit for my battery drain...haven't had this problem before and can only fix it by turning off Bluetooth...I'm accustomed to leaving Bluetooth on 24/7 because it's a pain in the butt to turn it on and off every time I get into my car, and the battery drain has never been significant.
Anyways, I was eager to update to 6.0, figuring that would cure the problem...but after wiping, flashing, wiping again...Bluetooth Share is still killing my battery! The only Bluetooth item I have paired is my car stereo.
See the attached screenshots.
Please let me know if you have any advice for solving this. Thanks!
I had the same issue turned out to be the app "Tasker." Dunno if you have that app at all but I figured I'd say since I had exactly the same issue and deleting some random profile I had setup for something that didn't have anything to do with bluetooth ended up fixing it.
StykerB said:
I had the same issue turned out to be the app "Tasker." Dunno if you have that app at all but I figured I'd say since I had exactly the same issue and deleting some random profile I had setup for something that didn't have anything to do with bluetooth ended up fixing it.
Click to expand...
Click to collapse
Hmm I hope I don't have to go through the painful process of uninstalling all my apps until it stops! I don't have Tasker installed right now so maybe it's something else...thanks for the heads up.
exactly same problem here...have to say that first days on android 6 didn't notice this wakelock, but started after second charge.
i am also using tasker to change the audio setting when i connect to my car bluetooth, but also uses android smart lock to disable security code with my pebble.
did you try to disable bluetooth scanning from location settings menu?
beren said:
exactly same problem here...have to say that first days on android 6 didn't notice this wakelock, but started after second charge.
i am also using tasker to change the audio setting when i connect to my car bluetooth, but also uses android smart lock to disable security code with my pebble.
did you try to disable bluetooth scanning from location settings menu?
Click to expand...
Click to collapse
Yeah that's the first thing I tried - disabling that Bluetooth scanning setting - but it didn't change anything.
Have you tried disabling Tasker to see if it fixes your problem?
not yet, i am going to do and check in the next hour.
btw it's strange that this problem didn't come out since the first charge, as i activated tasker immediately...
this is my first charge on android M:
http://forum.xda-developers.com/showpost.php?p=63262307&postcount=2610
disabled only the tasker profile that checks for bluetooth interface that i have in my car and seems that the problem is solved....now i have 8 alarms/hour made from bluetooth.
don't know if i should put tasker in the whitelisted apps for Doze, maybe this would help...
beren said:
disabled only the tasker profile that checks for bluetooth interface that i have in my car and seems that the problem is solved....now i have 8 alarms/hour made from bluetooth.
don't know if i should put tasker in the whitelisted apps for Doze, maybe this would help...
Click to expand...
Click to collapse
I'm curious if we have the same sort of issue - I know I don't have Tasker installed but another app may be doing the same thing...however I did have this issue on 5.1.1 as well, so I don't believe it's Doze causing it.
Seems tasker is not the problem after a while the wakelock comes again, now I am focusing on smart lock, will try to remove all trusted devices...
Inviato dal mio Nexus 6 utilizzando Tapatalk
Having similar issue on Nexus 5 with 6.0. Just removed android wear and disabled smart unlock. In looking around, it seems like many things seem like a fix but come back after the device is charged. Or certain bluetooth devices are connected and then disconnected. On disconnect, the wakelock occurs so rooted users are killing bluetooth and having luck with that. Also found this older, but still active group. https://code.google.com/p/android/issues/detail?id=87778 many there have found apps that are causing the issue. GassBuddy being number one.
acwalter said:
Having similar issue on Nexus 5 with 6.0. Just removed android wear and disabled smart unlock. In looking around, it seems like many things seem like a fix but come back after the device is charged. Or certain bluetooth devices are connected and then disconnected. On disconnect, the wakelock occurs so rooted users are killing bluetooth and having luck with that. Also found this older, but still active group. https://code.google.com/p/android/issues/detail?id=87778 many there have found apps that are causing the issue. GassBuddy being number one.
Click to expand...
Click to collapse
Ooh interesting - I use GasBuddy - I wonder what it needs Bluetooth for...
jeffreii said:
Ooh interesting - I use GasBuddy - I wonder what it needs Bluetooth for...
Click to expand...
Click to collapse
Wow I just tested 10 minutes with Gasbuddy enabled...then froze it with TiBu and tested 10 more minutes...and the Bluetooth Share drain was down from 14% to 0.3%...
What a shame that the new app permissions in 6.0 don't allow you to take away Bluetooth access...I really like GasBuddy...time to email the dev.
Great find! Thanks for the help!
may i ask if you see bluetooth in android battery stats? because i don't see it, but i notice wakelocks only in BBS.
btw for me it's related to pebble time, if i leave the smartwatch disconnected the wakelocks go down. Will try to remove android wear as suggested...
beren said:
may i ask if you see bluetooth in android battery stats? because i don't see it, but i notice wakelocks only in BBS.
btw for me it's related to pebble time, if i leave the smartwatch disconnected the wakelocks go down. Will try to remove android wear as suggested...
Click to expand...
Click to collapse
For me it was "Bluetooth Share" in GSAM Battery Monitor. I don't recall if I saw it in the normal battery stats or not.
I was slowly picking my way through apps, uninstalling and watching the bluetooth usage. I lost patience after removing maybe 15 apps, I don't use any of the "usual suspects". I ended up doing a complete wipe and flashing the 6.0 factory image and am now adding apps back in one by one. For reference, I enable all services and do not turn them off... Wifi, bluetooth, location, Wifi scanning etc. I am too lazy to turn them off and on.
Day 1 - Nothing but factory installed apps, google authenticator and bar code scanner. No bluetooth devices paired but bluetooth in on. Battery last forever, not wake lock.
Day 2 - Added strava app and connected to bluetooth HRM. No wakelock, same battery performance
Day 3 - Added android wear, moto connect and paired moto360. No wake lock and bluetooth keep awake is increasing by about 1 minute per hour so battery life is looking good. Have not enabled smart lock yet, will do that tomorrow.
I keep bluetooth on all the time and complete a full 24 hour cycle with full charge just to make sure that is not part of the problem. Based on my experience, the issue is not the OS or android wear. That leaves misbehaving apps, you just have to find which one through trial and error.
thanks for reporting, can you check how many alarms/hour you have from bluetooth?
Not sure what you mean by alarms/hour. It takes forever for bluetooth to show on my usage now. Yesterday bluetooth got to 2% of total usage for the day.
On day 4, Wi-Fi started rising to the top of the battery used list. Came out of nowhere and it seems like it is an actual bug Google is working on. The fix for me was 3 steps:
1. In Settings/Location click triple dot in top right and select Scanning, disable Wi-Fi scanning
2. In Settings/Backup & reset select Network setting reset
3. Reboot phone
This greatly improved battery life for me. The change is dramatic, I barely went under 50% per day over the weekend. I would suggest everyone try it, it took 4 days to show up but after the battery is outperforming my clean install with no apps. I still have all other services turned on.
I have this same issue!! I Have had the 6 for almost a year now and sinse day 1 I have had BT on almost 24/7. I have my MiBand connected the entire time, LG Tones and Tones+, a couple hours a day also connected to my vehicle (when tones aren't in use) and BT has never ever been a battery drain.
Switch to 6.0 BAM Bluetooth all over the place! I do not have any new apps, no android wear, google fit, pebble, gas buddy etc installed. Nothing new aside the same devices and apps that were there before 6.0.
But at the same time, by battery isn't lasting any less than before, at times a bit longer too (20+ hours) So I don't know if the BT battery data is just skewed? BBS, GSam and Phone all have different stats. I'll post screenshots in a few.
Today isn't the best example of screenshots as the first hour unplugged I had WiFi on (and not connected, forgot to turn off) GPS, MapMyRide app running GPS, Bluetooth and Google Play music all on at the same time (screen off though) and then I downloaded a Rom and Gapps but I'm showing the differences in the battery stats I get
Jeimygirl said:
Today isn't the best example of screenshots as the first hour unplugged I had WiFi on (and not connected, forgot to turn off) GPS, MapMyRide app running GPS, Bluetooth and Google Play music all on at the same time (screen off though) and then I downloaded a Rom and Gapps but I'm showing the differences in the battery stats I get
Click to expand...
Click to collapse
It seems as though certain apps are not working well with 6.0 and causing this issue...GasBuddy seems to be the most popular. I haven't had any problems since I disabled it last week.
You might have to manually determine which app is causing it by uninstalling/reinstalling apps until you find the culprit...
If you do, please post it here so others can find the answer without going through that hassle!
The other choice is to wait until the app gets fixed or Google issues a fix.
I just got this watch and updated it. On the first day of real-world use, it sucked up around 10% an hour. At first I thought that this was normal, but when I looked at the battery stats Bluetooth had used 80 to 90 percent, while the others only used 1%. Are there any tips or way I can help with this? I did update to the beta version (the one with Android o as the base and not n) so if that's the issue I'm fine with that, it does make it to around 4 pm and I wake up at 6-7. This is a very good watch though. I had tilt to wake, aod, Bluetooth and wifi although wifi didn't appear to use much. Cellular is disabled because I don't have a plan for it.
I also just got this watch, and was concerned about the rapid battery usage. However it is now much better. This could be for 2 reasons, or one or the other. The first is that the initial pairing causes a lot of activity over Bluetooth while the watch updates and syncs all apps and may have just settled down. The other, and from advice on this forum, was that I disabled cloud sync (not that easy to find, go into Android Wear app on phone then Settings, then Privacy and Personal Data). Since then the battery life has improved vastly. Hope that helps.
zjjpp said:
I just got this watch and updated it. On the first day of real-world use, it sucked up around 10% an hour. At first I thought that this was normal, but when I looked at the battery stats Bluetooth had used 80 to 90 percent, while the others only used 1%. Are there any tips or way I can help with this? I did update to the beta version (the one with Android o as the base and not n) so if that's the issue I'm fine with that, it does make it to around 4 pm and I wake up at 6-7. This is a very good watch though. I had tilt to wake, aod, Bluetooth and wifi although wifi didn't appear to use much. Cellular is disabled because I don't have a plan for it.
Click to expand...
Click to collapse
At least you get something other than Bluetooth. I'm on the beta as well as now I get nothing but Bluetooth listed. I had major drain and thought it might be because I tried sideloading apps via Bluetooth. Whatever it was I couldn't figure it out. Factory reset and I'm back to normal
Sent from my Pixel XL using Tapatalk
Yea today I woke up at the same time and before, at 3 I would be charging it from 5%. Today, it's 6 and it's at 33. I did disable cloud sync and a weather complication. I also disabled NFC. Other than that I dont remember changing anything else.
You don't happen to be using a Pixel 2 XL?
iliketrains said:
You don't happen to be using a Pixel 2 XL?
Click to expand...
Click to collapse
Having a very similar problem and I am indeed using a PIxel 2 XL, is there something you know about this?
I started a thread in the questions section for battery consumption, which still shows on the first page. The biggest consumers of the battery I've found are the Bluetooth/wifi radios and Tilt to Wake Sensor. That TtW Sensor was sucking down about 4% of the battery just on its own. The best configuration I've found is no wifi, no TtW sensor, no bluetooth, using LTE combined with AT&T NumberSync, from which I get approximately 24 hours. If you want to see other configurations that have been tried and reported, you can check out the other thread.
Taguiera said:
I started a thread in the questions section for battery consumption, which still shows on the first page. The biggest consumers of the battery I've found are the Bluetooth/wifi radios and Tilt to Wake Sensor. That TtW Sensor was sucking down about 4% of the battery just on its own. The best configuration I've found is no wifi, no TtW sensor, no bluetooth, using LTE combined with AT&T NumberSync, from which I get approximately 24 hours. If you want to see other configurations that have been tried and reported, you can check out the other thread.
Click to expand...
Click to collapse
I've had pretty decent battery life on my watch (depending on what it's doing in a day) but today the thing was dead in less than 7 hours and it shows it's all from Bluetooth. So, riddle me this....do I even need to be synced via Bluetooth when I have NumberSync? What are the advantages/disadvantages (besides battery drain) to leaving Bluetooth on and connected to my phone?
jeffreycpackard said:
I've had pretty decent battery life on my watch (depending on what it's doing in a day) but today the thing was dead in less than 7 hours and it shows it's all from Bluetooth. So, riddle me this....do I even need to be synced via Bluetooth when I have NumberSync? What are the advantages/disadvantages (besides battery drain) to leaving Bluetooth on and connected to my phone?
Click to expand...
Click to collapse
Sounds like something wasnt letting it sleep
Do what I do. Every 2-3 days do a restart of the watch just keeps things fresh.
Mine can easily last 2 days if stretch it. Normally I'm around 50% by the time I get home after 12 hours
Thanks for the advice! I'll start that routine tomorrow and see how it works out.
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.