Related
The short version: I have kernel wakelocks bluesleep and msm_serial_hs_dma, which keep my phone from going to deep sleep until I kill and disable the bluetooth-adapter-service.
This is what I tried till now:
I updated my Galaxy S4 (GT-I9505) from Android 4.4.2 (I9505XXUGNG8_I9505ATOGNF1_I9505XXUGNG8 ROM, Austria unbranded, phone was originally "3 Hutchison" branded) to 5.0.1 (I9505XXUHOE3), that was downloaded automatically via OTA. I rooted the phone with philz-touch (had rooted 4.4.2 also). I noticed a very heavy battery drain, but only after I had already "cleaned" some of the bloatware. Battery life was less than 10 hours, while it held out almost 2 days with my usage pattern on 4.4.2. So I did a factory reset, which didn't help. I started disabling services, including system services until the point where WIFI and bluetooth wouldn't work anymore at all (even enabling the services again didn't help). But at least I noticed that the battery drain was gone and it seemed to be one of the bluetooth system services.
Since I had to reinstall anyway, I used the I9505XXUHOF2_I9505OXAHOF2_I9505XXUHOF2 ROM (Germany unbranded, I couldn't find an Austrian UHOE3 or UHOF2 to download). Also did a factory reset of course. The battery drain was there again. This was even before rooting the phone, which I then did again to have more options to find the culprit (but I did not uninstall anything that came with stock). BBS showed me the bluesleep and msm_serial_hs_dma wakelocks. The wakelocks stayed no matter if bluetooth was enabled or not. I even flashed the modem on its own (although my phone info showed the right UHOF2 baseband before already), because this sometimes seemed to help people. Didn't change anything either.
In the end I narrowed it down to a single thing I have to do after installing stock (and rooting): disable the Bluetooth-> AdapterService (com.android.bluetooth.btservice.AdapterService) with the "Disable Service" app. The wakelocks are gone and I get almost two days of battery life (a little bit worse than on 4.4 though). Of course bluetooth will now not work at all until I reenable the service and reboot (and remember to disable and reboot as to not have my phone dead in a few hours).
I don't use bluetooth on a daily basis, but killing a system service can't be the solution. Why are the wakelocks there in the first place, even when I never had bluetooth active after a reboot? Are there different hardware revisions and you can't flash all you want? Since most people seem not to have a problem like this on a stock ROM after a factory reset, the only difference can be the hardware, or not?
Hi,
bumping your thread and a question for ya, is 5.0.1 that bad? I'm still on 4.4.2 stock and I did notice a OTA update notification, but I didn't accept it yet.
Erroneous91 said:
Hi,
bumping your thread and a question for ya, is 5.0.1 that bad? I'm still on 4.4.2 stock and I did notice a OTA update notification, but I didn't accept it yet.
Click to expand...
Click to collapse
If the thing bluetooth wouldn't happen (which it obviously does not for everyone or the outcry would be much bigger), there's nothing wrong with it. After I killed bluetooth completely battery life is only slightly reduced compared to 4.4. I liked the dark look of 4.4 more though. Now everything has a bright background. But that's personal preference.
Hi all...
So, I think I may have gotten the latest update last night, and I think it may have broken all sorts of things. My battery is draining faster than my wireless charger can actually charge it (which has never happened before), and I can't seem to install apps from Google Play. It's super awesome.
My friend with the same phone seems to be experiencing similar problems, and I was just wondering if anyone here was too?
Update: I just plugged my phone into Smart Switch, and it found an update . . . soooo, I don't think that getting an update last night was the problem. I'm running the update now and we'll see if that solves the issue.
I do experience battery drain. This phone battery life gets worse and worse each update. Screw this 3600mah
Sent from my SM-G935T using Tapatalk
It's the latest Oculus update. Freeze it or uninstall until fixed. Oculus home is trying to install over and over again.
NH Apache said:
It's the latest Oculus update. Freeze it or uninstall until fixed. Oculus home is trying to install over and over again.
Click to expand...
Click to collapse
I'm thinking is the oculus update as well because my lookout continues to scan oculus rooms every 2 mins. It's just a weird coincidence that it happened about the same time as the update though. I'm having severe battery drain, texts and mms not being sent or received sometimes, and generally laggy overall.
jza802k said:
I'm thinking is the oculus update as well because my lookout continues to scan oculus rooms every 2 mins. It's just a weird coincidence that it happened about the same time as the update though. I'm having severe battery drain, texts and mms not being sent or received sometimes, and generally laggy overall.
Click to expand...
Click to collapse
Oh man, thank you! The battery drain is being reported as "Android System" which is no help at all. I'll give the Occulus thing a try
Mine is draining from the latest good lock update
Sent from my SM-G935T using Tapatalk
Since updating this morning my phone runs hot and the battery drains 35% an hour. Charging is slow and phone has tons of lag. Worst device performance i've had since i ran ICS on my HTC G2
I'm wondering if using adoptable storage is causing it. I'm actually backing up and attempting a factory reset in a bit. My device is not rooted. Never even attempted root on my S7E.
Mine is smoother than ever. But im carefully looking at the battery and it seems to be draining faster. I have to look at oculus. But it doesnt seem i have that install
My phone has the same problem. Lookout is scanning Oculus Rooms two or three times a minute. So, is it an Oculus problem or a Lookout problem?
What baseband version you guys got?
I flashed my phone from sammy mobile (on the 28th i believe) dated 9/21 and security patch dated 9/1 and seems to be working much better than it was prior. Phone was getting hot and now it has not at all. on 2nd day right now. I still having used my wireless charge though.
I had the same issue. I was having extreme lag, overheating, battery drain(54% drain in less than two hours and it was in my pocket) and the screen kept refreshing every few seconds. All my apps were basically affected. The worst was snapchat and the keyboard. I saw the post on reddit about oculus being the problem. I uninstalled all the oculus and gear vr apps that could be unistalled and disabled the rest. My phone is working perfectly now.
It was the Oculus update. They (Oculus? ) pushed a fix out and now it's corrected. Confusing for users of Good Lock, because the Oculus problem happened the same night as the 9-29 Good Lock update, which was also very buggy. Uninstalling the 9-29 Good lock did not fix the problem though. All better now thanks to the Oculus Home update. I believe Good Lock was also fixed with the 9-30 update. I haven't gotten the OTA software update yet (PIA).
Woke up this morning and my battery was down 40%, rebooted which is recommended anyway everything mellowed out, charged my phone back to 100% have over 4 hours of screen time with 47% left. I disabled lookout because it's always scanning and running chewing up battery. I have no idea what Oculus is. Duh on me I guess
Hi
Just wondering how those running Stock Firmware 32.2.A.0.305 have found the phone to be working?
Any issues or improvements with:
- battery life
- overheating
- phone/wifi signal
- fingerprint sensor
- camera photo quality
- Bluetooth music jitter
Or anything else?
Thanks
R
I'm running Heptyle's kernel, .305 Custom DE and debloated with script.
I haven't reached conclusions yet but so far I think my battery life is better than .253
During app installation (clean installation) I got the feeling it ran less hot.
No further differences until now regarding to your other items.
I'm only going to run STOCK I'm not going to root the phone.
Nothing special here.
Volume for notifications got fixed. And security level is aug 2016 (shame on Sony)
The option to enable the google now pane in the Xperia Launcher (beta?) is back. Note that I did join that Google+ group for getting beta updates of the Launcher.
Camera format settings were reset for me after the upgrade. The version of the app is now 1.0.C.2.7 but I didn't check before the upgrade what it was.
So far it's been smooth, but nothing notably new.
Feels just about the same in all regards
I'm running 32.2.A.0.224 and heard bad things about .253 so have not updated.
I upgraded to the latest one (.305) from EE (UK) on Thursday, and accidently bricked the device (took over an hour to upgrade and so I forgot it was upgrading - d'oh) so have ended up with a clean install.
- battery life : At this time of the day I used to be at 52% (.253), currently 80% (has been off charge for 5 hours so far), was pretty poor for the first two days while Google Play music was hammering the WiFi connection downloading music (why can't it see what's already on the SD Card - argh!), but still an improvement of .253 which was appalling.
It used to be that Google Play Services and Android System were the top users by a country mile - today it's Screen (27%) and Beyond Pod (9%)
- overheating : Certainly running cooler
- phone/wifi signal : No issues before or since
- fingerprint sensor : No issues before or since
- camera photo quality : No issues before or since
- Bluetooth music jitter : As solid as it has been since the last upgrade, i.e. Bluetooth is problem free, Wired occasionally jitters approx 20 minutes after losing Wifi.
Or anything else?
WiFi Calling still temperamental (i.e. needing a reboot), less of an issue for me now I have VoLTE and new masts cover work and home better.
Thanks very much for that excellent and detailed response
I hope this will fix things. On .253 I'm having issues with the finger print scanner, saying hardware is unavailable after long periods of not using the phone. Also, the camera crashes when trying to take a video. gifs and videos on apps such as facebook or youtube doesn't play too. Restart fixes things but it's annoying that I have to do it at the start of the day, every single day. Would love to hear from somebody with same issues who upgraded from .253
I updated to this and done a factory reset (I always do this after installing new update). My device for more than 10 hours now has problem with volume.
If I play any music (on full volume) for more than 1 seconds the volume level is reduced dramatically. My phone has never been in contact with water or anything. As of now I have turned the phone off/on and still no difference. I have used Google Play, Spotify and the same problem occurs.
On the other hand it doesn't heat up. Battery life seems a tad better if I recall so far. Other than that no difference apart from a message I got about battery charging.
Seems to be the hearing protection. New build.prop in .305 is without persist.audio.hp entry. Just re-add it to build.prop (persist.audio.hp=false), reboot and should be working again (you need to be rooted).
MiracleMiah said:
I updated to this and done a factory reset (I always do this after installing new update). My device for more than 10 hours now has problem with volume.
If I play any music (on full volume) for more than 1 seconds the volume level is reduced dramatically. My phone has never been in contact with water or anything. As of now I have turned the phone off/on and still no difference. I have used Google Play, Spotify and the same problem occurs.
On the other hand it doesn't heat up. Battery life seems a tad better if I recall so far. Other than that no difference apart from a message I got about battery charging.
Click to expand...
Click to collapse
Di you have Root?
Ever have problems before?
Yes, I'm rooted (just check tobias waldvogels rootkernel thread), but you need to have unlocked bootloader first (don't forget to make TA backup!).
i found that the phone gets warm (more than previous firmware) when browsing the web using chrome.
i noticed that the sony email client doesnt check/update as quickly enough compared to previous firmware.
i did notice couple of things have been fixed, but my overall suspicion of this firmware is that it introduces more issues than it fixed.
also some kind of security has been introduced to stop you from hiding apps such as the quick apps bar.
im also curious why sony introduced that "battery optimization"? has it to do with maybe the batteries starting to bubble hence causing the back cover to crack? so by reducing the charge amount it sort of stops that from happening?
im also running stock firmware.
I would appreciate you come back w/ a review after a month of usage. If you have been using Android for a significant amount of time, then you know that it's always good in the beginning. I don't think much stock should be put in a review done after a day besides ease of installation and (maybe) initial impressions, imho
ive gone back to .253 firmware. this previous version seems to work much better on my australian z5 compact.
no heating issues. battery is better. email app works better etc. etc.
yes it does have the annoying low volume and a issue with the sms app (when trying to add certain photos). but overall to me it works better than .305 version.
harry_turtle said:
I'm running Heptyle's kernel, .305 Custom DE and debloated with script.
I haven't reached conclusions yet but so far I think my battery life is better than .253
During app installation (clean installation) I got the feeling it ran less hot.
No further differences until now regarding to your other items.
Click to expand...
Click to collapse
Which Script you are using to debloat?
Baron1971 said:
Which Script you are using to debloat?
Click to expand...
Click to collapse
A few weeks ago, I tried this. From @FcukBloat
But for me it didn't work. When I flashed, I got a message that the zip was corrupt (which I can't believe, and it's not the first time this happened). And I also had a problem with Online Nandroid, so in the end I had to redo it.
This time, I just did manually what the script should automate. Next time I'll figure out how to build it myself, if I'm smart enough.
So after a week of 305 vs 253 - I've managed to get through to the end of the day without needing to charge one or twice throughout the day every single day, the phone is running much cooler (i.e. most of the time there is no heat detectable), and is also less laggy, especially when launching the camera. Battery life is getting better by the day too - now at 60% (after being off charger for 12.5 hours) with Google Play Music, twitter, and an hour of MapMyWalk (so GPS usage) - on 253 I'd have been below 20% at this point of the day.
rossyl said:
I'm only going to run STOCK I'm not going to root the phone.
Click to expand...
Click to collapse
im also going pure stock unrooted locked bootloader ,at least till warranty void anyway\ OR the phone become really slow for some reason, and root will help
example: this phone got only 2GB RAM which very bad multitasking , and heavy apps like CSR2 left my phone with only 200MB .
so i guess il need more Swapfile\Z-ram @1s
---------- Post added at 07:48 AM ---------- Previous post was at 07:42 AM ----------
BTW
305 still didn't released in my state anyone got idea how to check when it will come out? it is possible?
hi MI A1 owners.
for those brave enough to use the latest vanilla, official OTA rom, what change did you notice?
does the battery still suffer huge drain that appeared in 2018 roms?
it's a big "NOPE" for me to update, i'm still on official DEC rom because of this drain issue.
Battery life is good on 8.1 no issue for me getting 5-6 hours SOT on gaming.
Never had battery drain problems. Only "issue" is notification led not blinking.
Just noticed that led light is no longer blinking when notifications arrive. Light stays on only when screen is off. Also Bluetooth is constantly disconnecting.
Ambient display isn't working for me.
Led notifier is also not blinking anymore!
Led not blinking, proximity sensor doesn't work properly all the time, some scrolling lag. That's what I've got so far
dudes thanks for your answers.
i'm just more convinced to not doing the update.
maybe the drain i had was magisk-related. (?)
Nothing for me, even got ten hours of screen after some cycles. Led doesn't bother me and it's the only thing i noticed.
Yes, the LED is always on, which is annoying, but the bigger issue is there is no change in the battery drain. I charged to 100%, set the phone down and did not move it or use it overnight. 8 hours later almost 14% of battery was drained. I have tried everything I can think of to try, including turning off high accuracy location, not allowing any location things like safe area, etc. and still I get this drain even when the phone is not in use. Android kernel and system consumed 85% of that usage, and System UI, Play Store and Phone Services accounted for 7%! SO basically, basic Android paired with the A1 hardware seems to be the issue and I don't know that there is any fix for that.
At one point, I thought an upgrade to the A2 was going to be a no brainer, but with the issues with updates being broken and this battery drain issue that nobody seems to be able to pinpoint and resolve, I am thinking I may not buy ANY other Xiaomi. It may be time to try something else because the only way I can get two days of battery is to turn on airplane mode when the phone is not in use!
KB_Thailand said:
8 hours later almost 14% of battery was drained.
Click to expand...
Click to collapse
Dunno what to say man. Mine is below.
2-3% at most over night.
And now it would appear that there is an issue with airplane mode.
I put the phone into Airplane mode at 2300 last night with 90% battery and did not pay attention to it. This morning I turned to phone on to find there was only 69% battery left, and WiFi was working. (see screen shot) WTF???? I have started using airplane mode to keep the battery drain to a minimum when the phone is not in use, and now it would appear that this doesn't work either.
I am REALLY getting frustrated with Android and Xiaomi as it seems that every time they do an update, something else goes bump! I have gone from totally happy with the AI when I first got it to being ready to write off Xiaomi as a company I would consider for purchase.
IjazCI said:
Is your WiFi scanning is on. ( Under location / scanning)
Play services also cause these type of sudden battery losses.
Try downloading latest play services apk from apkmirror . Latest one is
"com.google.android.gms_12.8.74_(090408-204998136)-12874034_minAPI26(arm64-v8a,armeabi-v7a)(480dpi)_apkmirror.com.apk"
Uninstall your current one. Install this .
Power off your phone for a few seconds and reboot.
Click to expand...
Click to collapse
Thanks for the thoughts, but unless I totally misunderstand what airplane mode is, WiFi should not be active when airplane mode is invoked. You can see by the screen cap that airplane mode is on AND WiFi is active. This seems to be a one off as it has not happened again for the last two days. I turn airplane mode on to stop the overnight battery drain while the phone is doing nothing. I have location set to GPS Only. IIRC play services was just updated 3 days or so ago, so it should have the latest version. I will check it and see though. Again, thanks for the thoughts.
KB_Thailand said:
At one point, I thought an upgrade to the A2 was going to be a no brainer, but with the issues with updates being broken and this battery drain issue that nobody seems to be able to pinpoint and resolve, I am thinking I may not buy ANY other Xiaomi. It may be time to try something else because the only way I can get two days of battery is to turn on airplane mode when the phone is not in use!
Click to expand...
Click to collapse
I can't logically understand why you would think it is the hardware causing the issue. If it was hardware, what you are seeing would be happening to every owner of the phone and clearly that is not happening. By saying it is the hardware when you have other software loaded is akin to saying your car's air conditioning doesn't work properly when you have all the windows wound down.
There is something loaded on your phone that is causing the systemUI to be working when you think nothing should be happening. The first thing I see on the screenshot on your phone is that in the top left of the screen you have two non standard icons. That tells me that you have a skin or non standard software constantly running.
The way to solve any issue like this is to go back to basics. I would get the fresh rom and do a Miflash whilst keeping your data. Make sure you do a backup first.
If that does not work, back up your data and do a clean install and check the phone's battery life. Do not load any non google software / app at this stage.
Then each day add one app and test for 24 hours. You will find this issue and the offending app or apps and I would be willing to bet you a few Singhas it will be an app you downloaded not the hardware causing this.
ludditefornow said:
I can't logically understand why you would think it is the hardware causing the issue. If it was hardware, what you are seeing would be happening to every owner of the phone and clearly that is not happening. By saying it is the hardware when you have other software loaded is akin to saying your car's air conditioning doesn't work properly when you have all the windows wound down.
Click to expand...
Click to collapse
Actually, I think it is a combination of hardware/software, but that is just a WAG. Others have noted the exact same issue without running the same software. My bet would be on the RCS services stuff.
There is something loaded on your phone that is causing the systemUI to be working when you think nothing should be happening. The first thing I see on the screenshot on your phone is that in the top left of the screen you have two non standard icons. That tells me that you have a skin or non standard software constantly running.
Click to expand...
Click to collapse
Those icons are my Email client and GSAM Battery Monitor (presently 0.1% and 0.8%) and are the only two constantly running programs other than the stock apps and Sophos (0.3%). Neither use much battery compared to the Android stuff. Presently Kernel is 41.6%, RCS/Phone is 30.3%. SystemUI is 3.3%, Play Services is 2.0% and Phone Services is 1.8%
The way to solve any issue like this is to go back to basics. I would get the fresh rom and do a Miflash whilst keeping your data. Make sure you do a backup first.
If that does not work, back up your data and do a clean install and check the phone's battery life. Do not load any non google software / app at this stage.
Then each day add one app and test for 24 hours. You will find this issue and the offending app or apps and I would be willing to bet you a few Singhas it will be an app you downloaded not the hardware causing this.
Click to expand...
Click to collapse
Good advice. I will do this when I have a few days to play with it. In the interim, it's airplane mode every night. Thanks for the reply. If it turns out to be one of these apps, let me know where to send the Singhas.
Good luck with it. I hope you find the solution. It can be frustrating, but getting to the bottom of it will be worthwhile. I haven't used Sophos for a long time and even then it was for PC. I am not up with how Sophos AV is integrating into Android but that would be my first guess.
I have only had one issue with this phone after updating and it was that the OS was constantly asking for a password on unlock after using fingerprint not just on startup. A clean install solved it and I have been trouble free since with every update. With over 50 PCs in my office, I could only wish that I had so few issues with Windows updates as I do with Android.
For me, night light auto schedule not working properly.
I can't tether via wifi/bluetoth/usb
Made another post with the problem.
ludditefornow said:
Good luck with it. I hope you find the solution. It can be frustrating, but getting to the bottom of it will be worthwhile. I haven't used Sophos for a long time and even then it was for PC. I am not up with how Sophos AV is integrating into Android but that would be my first guess.
I have only had one issue with this phone after updating and it was that the OS was constantly asking for a password on unlock after using fingerprint not just on startup. A clean install solved it and I have been trouble free since with every update. With over 50 PCs in my office, I could only wish that I had so few issues with Windows updates as I do with Android.
Click to expand...
Click to collapse
Just for grins and giggles, I uninstalled my email client, GSAM, and Sophos, the only programs that run constantly other than system and Line. I then turned my phone off and back on, forced stopped Line, charged it to 100% and set it down with the screen off. It did not move of get used for 8 hours, yet it still used 12% of the battery. (see screenshots) This is better than the 20% with those apps installed, but still not close to what I would consider normal. When I first got the phone, it easily lasted 2-3 days between charges, with 6-7 hours SoT. Overnight would use MAYBE 2% of the battery. Now if I want it to last 2 days I need to turn on airplane mode overnight and then I can make it through a day.
So I guess the next step is to do as you recommended and load up the fresh rom when I have time to mess with it. At least I am now pretty sure that those apps aren't the culprits causing the biggest part of the battery drain. I hate to do it, but I am seriously thinking of a factory reset and seeing if that clears the issue. Would that put me back to Nougat?
IjazCI said:
I always disable carrier services apk. As rcs is not here in India.
Click to expand...
Click to collapse
How do you disable this apk? I seriously think this is the major culprit in the battery drain.
KB_Thailand said:
charged it to 100% and set it down with the screen off. It did not move of get used for 8 hours, yet it still used 12% of the battery. (see screenshots) This is better than the 20% with those apps installed,
Click to expand...
Click to collapse
So those apps were causing 40% of of the 20% of the battery drain. That is a good start. I am confident there are software issues with your phone. I see you have some GPS app on your home screen, if that was running askew, it might be constantly pinging. That is just a guess.
In things like this, work methodically through it. But of cause a hard reset would be the best way to go. I see no reason why you wouldn't stay on your current version after a hard reset.
If you want to go make to version 7 you would need to use the MiFlash program and a downloaded standard fastboot rom. You may need to do something else to the phone to go back to 7, but I would not think so.
Since the first release of oreo I started using the rom as a daily driver, later on paired with a good kernel it had some good perfomance
But after some days of using the rom i started to notice a huge battery drain caused by the Mobile network standby process?
My battery was old (OEM 2014 battery) so i decided to revert back to lineageOS just after a couple of days where I haven't had any issues with that mobile network standby
Now I'm really curious what is causing this issue,drain because I am using the phone on the same settings as on 7.1 nougat, I am living in a country where all networks run on 3G,H+,2G etc. so no 4G if this can be a cause
Changed the network modes many times and tested throughout the days but there was no sucess the drain was still persist, tried updating,downgrading bootloaders swithing modems but again no sucess
If there, in the world of android is any solution, here is the thread to discuss about this issue. :fingers-crossed:
I've wondered this too. I've been running los15 on my g900v , I rooted and boot the first ROM that would work without having or remembering todomuch, I ran the first custom kernal I could find via google, and ran whatever was noted as the latest Verizon modems. its like right off the bat, smooth , consistent battery life and nice. Then the next day I noticed things would crash, my Bt temperamental at best and restarted it just to get by. if I have sync on at home, WiFi off, it just chills , if I turn sync off and drive around town, my battery life gets eaten by the unknown. I pulled some logs to see whats up with my BT but haven't got around to it yet. But my battery too is old (I literally found my s5 in the trash) and I run weird processes and tweak settings all the time just to mess with it, so that could be it to. If I see anything weird I'll let you know.
I'm struggling with this issue for months, since the first port of an Oreo custom ROM (LOS and RR) for the Galaxy A3 Duos (my device) started being developed.
From the beginning I had this problem, and what, since then, puzzles me the most is the fact that only some of us, flashing the same ROM in the same device, experience the issue. Whenever I flash any of those ROMs, even before installing any user apps (or when running in safe mode), the drain is there, which leads me to think that the culprit must be some setting: not an app, because I have none installed; not the ROM itself, because not everybody has this problem.
Unfortunately there seems to be no developers looking into this bug.
For the sake of information, I've observed two things that should help to narrow down the issue; or maybe not.
First, all the devices affected, as far as I've searched, are double SIM.
Second, the Mobile Network Standby (MNS from now on) drain is narrowy connected with the Bluetooth drain (which "also" occurs in Oreo). I've experienced the following: If, after a full charge, I don't switch on Bluetooth at all, then what drains my battery (according to Advanced Battery Usage information) is MNS. However, if I switch bluetooth on -even if only for one minute- then what apparentlyh drains my battery is Bluetooth, at the same speed as MNS did before switching bluetooth on.
Funny enough, the battery use info reports zero minutes activity for both Bluetooth and MNS. But how can a process which runs zero minutes drain 50% of the battery?? I'm afraid that the battery use information isn't reliable. But then that's very bad news, since, in such case, it might well happen that the real juice sucker is neither MNS nor Bluetooth!! We might be dealing with a "ghost" here, since we can't even trust the battery use information provided by the OS.
If someone has something with which to contribute to this research, or any ideas, please comment.
I'm having the same trouble on android 9 betas, even better, my phone gets without signal during those times and there's nothing I could do but rebooting the phone.
How can we help solve this? it looks like it's annoying a lot of people now