Database Develop

Gear One and Moto G - should my battery life be bad?

Just to say I've never used the Gear with a Samsung device. I also updated it immediately to Tizen so have no idea what battery life would have been like on Android.
I'm using a Moto G LTE and the gear Manager and Stub apk. It's not rooted or modded in any way. It works fantastically but I'm finding that the battery doesn't even last a day. I have the Gear set up so it only lights up when I press the standby button so aside from incompatibilities or some problem with the flash I've no idea what the problem is. Just wanted to know if I should EXPECT poor battery life with a non-Samsung phone paired to the watch or if I should investigate re-flashing or going back to Android. The Gear is a lovely device but is a bit useless if I can't make it through the day. I'm already down to 91% and I only took it off charge two hours ago.
Does anyone have any advice? If I can expect the battery to be rubbish I might just order an Android Wear watch; though I actually prefer the extra functionality of the Gear.
Thanks in advance.

bluetooth tethering
leoni1980 said:
Just to say I've never used the Gear with a Samsung device. I also updated it immediately to Tizen so have no idea what battery life would have been like on Android.
I'm using a Moto G LTE and the gear Manager and Stub apk. It's not rooted or modded in any way. It works fantastically but I'm finding that the battery doesn't even last a day. I have the Gear set up so it only lights up when I press the standby button so aside from incompatibilities or some problem with the flash I've no idea what the problem is. Just wanted to know if I should EXPECT poor battery life with a non-Samsung phone paired to the watch or if I should investigate re-flashing or going back to Android. The Gear is a lovely device but is a bit useless if I can't make it through the day. I'm already down to 91% and I only took it off charge two hours ago.
Does anyone have any advice? If I can expect the battery to be rubbish I might just order an Android Wear watch; though I actually prefer the extra functionality of the Gear.
Thanks in advance.
Click to expand...
Click to collapse
Do you have Bluetooth tethering enabled and so you use Bluetooth often?

hoddy4 said:
Do you have Bluetooth tethering enabled and so you use Bluetooth often?
Click to expand...
Click to collapse
How do you mean? The only thing I use Bluetooth for is the watch, other than the odd occasion at home when I connect a Bluetooth speaker.
The only notifications I have it set to send to the device are Robird and Hangouts. Nothing else is set to notify me. Not even Gmail.
It's not tethered to the internet via my phone if that's what you mean. Not even sure that's possible on Tizen. It just is set to send notifications from two ticked third party apps and for phone calls. Brightness is set to 3 and auto wake with hand movement is switched off. Battery now down to 82% with basically no use whatsoever other than being connected.

leoni1980 said:
How do you mean? The only thing I use Bluetooth for is the watch, other than the odd occasion at home when I connect a Bluetooth speaker.
The only notifications I have it set to send to the device are Robird and Hangouts. Nothing else is set to notify me. Not even Gmail.
It's not tethered to the internet via my phone if that's what you mean. Not even sure that's possible on Tizen. It just is set to send notifications from two ticked third party apps and for phone calls. Brightness is set to 3 and auto wake with hand movement is switched off. Battery now down to 82% with basically no use whatsoever other than being connected.
Click to expand...
Click to collapse
Yes, I was talking about Bluetooth tethering to the internet which can really affect battery. On Android (not Tizen), I would expect battery usage to be about 2% per hour with very light usage.

hoddy4 said:
Yes, I was talking about Bluetooth tethering to the internet which can really affect battery. On Android (not Tizen), I would expect battery usage to be about 2% per hour with very light usage.
Click to expand...
Click to collapse
OK, I did a hard reset via the recovery menu on the Gear and it seems to have improved things. Currently on 96% after over 4 hours. Still only have two apps set to give notifications - SMS and WhatsApp - and only when phone screen is off. Also still have auto screen activate switched off. Not really sure what sort of battery life to expect but this is better at least!

bluetooth wakelock

Hi,
Since several days I notice a battery drain related to bluetooth. It basically started when I added a bluetooth device in the car, so I keep bluetooth on at this time.
Right now I had about 30% of battery usage for bluetooth.
Any way to find out what is causing this? The way it is behaving right I cannot reach the end of the day with the battery.
I don't want to turn off bluetooth, because that is kind of masking the underlying issue.
thanks

I was able to fix the problem. It seemed to have been Gasbuddy. After removing the app, bluetooth went back to normal battery usage.

fonteynb said:
I was able to fix the problem. It seemed to have been Gasbuddy. After removing the app, bluetooth went back to normal battery usage.
Click to expand...
Click to collapse
What is GasBuddy
fonteynb said:
Hi,
Since several days I notice a battery drain related to bluetooth. It basically started when I added a bluetooth device in the car, so I keep bluetooth on at this time.
Right now I had about 30% of battery usage for bluetooth.
Any way to find out what is causing this? The way it is behaving right I cannot reach the end of the day with the battery.
I don't want to turn off bluetooth, because that is kind of masking the underlying issue.
thanks
Click to expand...
Click to collapse
Sent from my F8131 using XDA-Developers mobile app

it's an app that can show you the gas prices around you, or if you have an account, you can add gas stations as favorites and check the gasprices (depends on if people are actually updating the prices).
But I see that in most areas which are not too remote, it is rather accurate.

Bluetooth sucking battery?

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.

Wakelocks

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.

Help! After latest "update", Bluetooth is the only thing showing in battery stats?

Help! After latest "update", Bluetooth is the only thing showing in battery stats?
OK, so there was a new stock "update" and an old problem came back, namely that my phone shows Bluetooth as the only thing using battery. I had this a while ago (in this thread here about "crazy mega bluetooth battery drain") but the same fix of resetting the logs does not seem to be working.
A short time after charging the phone and resetting the logs, the phone shows Bluetooth has a CPU total of 0s, Keep awake of 7s, and computed power use of 17895mAh. No other process is listed as using battery!
The phone is stock, not rooted, "updated" to N8I11F with the OTA that came last week.
Anyone know how I might resolve this?

Various solutions have been discussed in this thread.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers

ktmom said:
Various solutions have been discussed in this thread.
Click to expand...
Click to collapse
Well, thanks again. I've tried turning off the Bluetooth headset in the Google app (Google app->Settings->Voice).
I guess I'll know after I use Bluetooth next if it helps or not.

ModemJunki said:
Well, thanks again. I've tried turning off the Bluetooth headset in the Google app (Google app->Settings->Voice).
I guess I'll know after I use Bluetooth next if it helps or not.
Click to expand...
Click to collapse
OK, yesterday after I drove my car which has Microsoft Sync 2, the bluetooth problem returned. So I went through the threads again and did found that maybe the reset wasn't working because I was charging with an LG charger at work. So I tried topping off the battery with the OEM turbo charger (and not using a Qi charger either). Tethering is off as well.
But this is also not seeming to work. After 22 hours, BT is showing 23% battery use (though I do now see other apps in the battery stats).
Still looking for a solution.

Did you turn off instant tethering as suggested in that thread?
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers

ktmom said:
Did you turn off instant tethering as suggested in that thread?
Click to expand...
Click to collapse
Yes, instant tethering is off.
I can confirm that if I charge the phone and don't use Bluetooth, the problem does not exist. I was able to let my phone run for 24 hours and the battery stats were normal, showing more than 1 day of runtime at the beginning.
As soon as I connect to my car, then only Bluetooth shows in the battery stats and the battery life is reported as shortened considerably.

ModemJunki said:
Yes, instant tethering is off.
I can confirm that if I charge the phone and don't use Bluetooth, the problem does not exist. I was able to let my phone run for 24 hours and the battery stats were normal, showing more than 1 day of runtime at the beginning.
As soon as I connect to my car, then only Bluetooth shows in the battery stats and the battery life is reported as shortened considerably.
Click to expand...
Click to collapse
I'd factory reset at this point. Something is wacky and it's not wide spread.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers

ktmom said:
I'd factory reset at this point. Something is wacky and it's not wide spread.
Click to expand...
Click to collapse
I was hoping to avoid that but I'll give it a shot later today or tonight.

ModemJunki said:
I was hoping to avoid that but I'll give it a shot later today or tonight.
Click to expand...
Click to collapse
Fingers crossed that once you put in that effort, the problem is fixed. You could try going into safe mode and see if that resolves things. Safe mode will reset ROM/system settings, but you won't lose your apps.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers

Don't do it, it's not going to work.
I learned how to live with battery drain stats

I'm on Oreo and doesn't matter what custom ROM I'm on this annoying issue occurs always when I keep my BT open, but not connected to any device
I've tried all the "fixes": not optimizing the BT, clear the BT cache, clear the bootloader logs, disabled the BT tethering etc... none of them helped.
When I connect to a device (headphones, or car) the consumption is normal and very low, no problem of showing the correct figures in Battery menu.
The issue occurs only if BT is not connected.
I can't believe this issue has not been reported yet to Google, but it seems they don't care about it...

Well, after using Safe Mode, no difference. I think that even if I don't use a Bluetooth device the problem comes up after a while.
How can we report this to Google? They don't support the phone any longer...

ModemJunki said:
Well, after using Safe Mode, no difference. I think that even if I don't use a Bluetooth device the problem comes up after a while.
How can we report this to Google? They don't support the phone any longer...
Click to expand...
Click to collapse
Use the Nexus support forums.
Is your battery original? The only time I have personally had to trouble was when my battery started failing. It was a precise to the early shutdowns and when I replaced the battery, I never had the problem again. Not on Nougat or Oreo.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers

ktmom said:
Is your battery original? The only time I have personally had to trouble was when my battery started failing. It was a precise to the early shutdowns and when I replaced the battery, I never had the problem again. Not on Nougat or Oreo.
Click to expand...
Click to collapse
Yes, original battery. The phone was purchased as new old stock last August. The battery is good, runs all day with heavy use, or more than a day when I'm not using the phone much.

Well, all I can tell you is this doesn't not exist on every phone. And unlike the earlier post indicating it's an inherent problem on Oreo, the attached screenshots show that's not true on my device.
The first image is after some time with Bluetooth on but not connected and the second with a device connected.

OK, so Google support connected me to Motorola support and they had me try clearing my storage cache which did not work. I will try calling them back tonight as I have a case open.
If that doesn't pan out I'm going to try doing a factory reset and setting up the phone as a new device - I've not done this before so I hope it's straightforward. Then I will use the phone stock for a day to see what if anything happens. If it's all good I will re-add my applications one at a time. I don't have all that many apps on the phone.
It might have to wait since I have some other work and household projects going on, but if I do find the root cause I will post back here.

OK, reporting back. Motorola support was polite but unhelpful. Reset the phone, reset the logs, oh thats it - out of warranty, replace the phone for $$$ even though it was our OTA that caused the problem.
No thank you, Motorola. I'll spend my money elsewhere after you broke my phone.
However, my complaints aside, I am tentatively pleased to report that the behavior has changed, and if it keeps running this way I'll hang on to the phone until it's well worn.
The change is that now even though only Bluetooth is shown as battery draining, the phone shows more normal battery stats so it's like it was before the update. For example at the moment I have 68%, 1 day 6 hours left, 14 hours after last full charge (I charged it and let it sit idle overnight, then today have been re-installing the few apps I use like Authenticator, Outlook, Facebook, WhatsApp, WyzeCam, DropBox, Dark Sky, Alarm Clock Xtreme). The only change made from stock was to turn off Bluetooth tethering in settings and to turn off Bluetooth headset in the Assistant. Before this, after connecting to my car radio and driving for 30-40 minutes or so, the battery estimate would drop from >1 day to 7-8 hours. It did not do that today so I figured I'd try and reinstall my apps.
This change is purely by chance, I am not certain that this can help anyone else. Here is what I did:
1) Backup local data.
2) Reset phone to factory from the menu in Settings.
3) Setup up phone as a new device.
4) Turn off Bluetooth tethering in settings.
5) Turn off Bluetooth headset in the Assistant.
6) Shutdown, clear logs.
7) Restart, install Battery Calibration app (Imobs Ltd.) (paid version).
8) Run a "Premium Calibration".
9) Charge phone to 100% using the OEM TurboCharger.
10) Let phone sit idle overnight.
I'm hoping the behavior sticks after I reinstall my apps. I'll post back if it does not.

It's been a while and I was going through my phone cleaning up pictures when I remembered this thread.
So I opened my battery settings on the phone and somehow the battery statistics are working properly - I see a normal list of items for power consumption.
I am confused because I have not made any further changes to the phone settings or attempts to solve this aside from uninstalling Battery Calibration and using AccuBattery to keep an eye on battery life, but those changes were made months ago.

ModemJunki said:
It's been a while and I was going through my phone cleaning up pictures when I remembered this thread.
So I opened my battery settings on the phone and somehow the battery statistics are working properly - I see a normal list of items for power consumption.
I am confused because I have not made any further changes to the phone settings or attempts to solve this aside from uninstalling Battery Calibration and using AccuBattery to keep an eye on battery life, but those changes were made months ago.
Click to expand...
Click to collapse
Did you update your Oreo ROM to a newer version? I am running ABC ROM and my battery stats weren't working until a recent update. It never bothered me so I never made any attempts to fix it, it just started working on its own again.

alryder said:
Did you update your Oreo ROM to a newer version? I am running ABC ROM and my battery stats weren't working until a recent update. It never bothered me so I never made any attempts to fix it, it just started working on its own again.
Click to expand...
Click to collapse
No updates for me - I'm running stock build N8I11F.
It must have been an update to some other component that fixed it. I can not think of any other way for it to suddenly be "fixed".