Hey all, so I'm having a very annoying and strange issue: My Moto 360 will wake up (i.e. screen turns on) randomly and without reason, ranging from within seconds of each wake to minutes, but it absolutely kills the battery (I can't make it more than 10-12 hours with absolute minimal usage). This is with tilt to wake off, theater mode on, all possible apps except the Android Wear app uninstalled. and the watch sitting completely still on a table. It was happening with Android 5.1 and 5.1.1 on my Nexus 6, and is still happening with the recent 5.1.1 Android Wear update.
The only way to "fix" the waking up issue is if I turn on airplane mode on my phone, which obviously disconnects the watch. So clearly my Nexus 6 is waking up the watch remotely, be it through the AW app or through the connection itself somehow. One other note: when I reset the watch and pair it with my 2013 Nexus 7, the issue doesn't occur, so clearly it's not a problem with the watch's hardware or software, but with the way the Nexus 6 communicates with the watch.
Really would appreciate any insight or guidance as to what's going on - I'm truly at a loss, and the only explanation I can possibly come up with is an issue with my phone's internal hardware (maybe something bluetooth-related)? I've even reset my phone on multiple occasions and that won't fix it.
The only other reference on the internet I can find to this issue is here, where this guy seems to be having the same problem, albeit with a different Mororola-produced phone: https://productforums.google.com/forum/#!topic/android-wear/5vB-dKc5IGI.
Hi!
Since the first (official) upgrade to Android 7, and even now with the new 7.1, I've been having this issue everytime I use any of these apps.
I always used runkeeper to track my mtb trails and it always worked perfectly. When this started to happen once, twice, etc, I decided to change to Strava, as I assumed it was an app problem.
The same thing happened on strava!
This situation happens on a random time (it happened once after 10 minutes of use, it happened other time after 2 hours of use, completely random). I have kept with strava as, after a force close, when I open the app again, it recognizes that a problem has happened and it restarts from the last recorded place.
Anyhow, this is a very annoying situation, as if I don't notice that the app closed, I will loose most of the trail.
I have disabled "Agressive doze & app hibernation".
Any other ideas?
Thanks
I have the same on 8.0. Compleate stopper for using OP.
All fitnes apps that use gps stop after 10 or 20 or 30 min of bacground work.
Also i use heart rate sensor and it does not restarts itself. It stales Bluetooth and you can not reconnect hr sensor without rebooting device
Considering to swith to Samsung)
Try turning battery optimization off in settings for those apps. I am not sure if this works but give it a try.
So I have a Moto 360 gen 1 and Samsung Galaxy Edge+. I just got the Nougat update on the phone.
After the update, my watch has been draining battery like crazy. I usually got a full day out of it and charged it fully at night. Now, I can't even get to 5pm.
I reset the watch and re-synced with the phone. No change. This morning it's draining at a rate of about 20%/hour which means I will hardly make it past lunch. I also don't even get call notifications now.
I'm fiddling with Android wear and watch settings to try to disable any unneeded app (I only use the watch for basic notification and step counts).
Hello,
About Nougat and Moto 360 ... I received it on my Moto G4 a few weeks ago and I'm not experiencing any battery drain.
Watch battery behaviour is the same as before when phone was in Marshmallow.
isearchable said:
So I have a Moto 360 gen 1 and Samsung Galaxy Edge+. I just got the Nougat update on the phone.
After the update, my watch has been draining battery like crazy. I usually got a full day out of it and charged it fully at night. Now, I can't even get to 5pm.
I reset the watch and re-synced with the phone. No change. This morning it's draining at a rate of about 20%/hour which means I will hardly make it past lunch. I also don't even get call notifications now.
I'm fiddling with Android wear and watch settings to try to disable any unneeded app (I only use the watch for basic notification and step counts).
Click to expand...
Click to collapse
try uninstalling updates on Google Play Services (some app will prompt and make you update again, do that).
Uninstall and install all apps that have Wear app as well (like what apps show in Wear, uninstall the app in phone and reinstall and sync the watch in Android Wear app settings)
With such draining its just best to turn off everything unnecessary. Or turn off watch completely. With all resetting and resyncing, the watch will be dead soon anyways.. But probably it was just syncing or updating something by itself and you interrupted it by the reset so it had to do all the syncing again, draining the battery again ..
Helllo there!
Since a long time, I am experiencing issue with push notifications on my device. Especially when an app is not used for few days, the notifications stops appearing from the app. The frequently used app are displaying notifications.
Is it common? Anyone experiencing this? Is there a setting which I can change to get this fixed?
Tired searching the forum but could not find any info.
This was happening when I was running OxygenOS 4.1.6 and even after recently upgrading to Open Beta 20, the problem still exists.
Any info would be helpful.
Thanks!
Turn off the Battery Optimization for the apps... it is part of Android's "Doze" functionality.
I had this issue when I chose "deep clear" in recent app management and cleared the tasks. After switching to "normal clear", and re-starting apps everything started working as normal again.
I have been having this issue since updating my phone (Pixel 6 Pro) to Android 13. The battery life of my Galaxy Watch 4 Classic (SM-R890) has tanked. I used to get 2+ days of battery life with the watch and after the Android 13 update I got well less than a day. Many people on reddit have the same issue. It is not related to the watch, Other Wear OS watches are having same issue (like TWP3). This appears to be a Bluetooth issue with phone. When I turn off Bluetooth on my phone, my watch is back to 2+ days. In the Sept. update bulletin It said "Fix for issue occasionally preventing certain Bluetooth devices or accessories from connecting". I was hopeful that the Sept. update would fix this issue but alas it does not. I have the Verizon Sept. update (TP1A.220905.004.A1). I currently turn off Bluetooth on my phone so my watch's battery does not drain. It kind of sucks having a smart watch not connected to phone. Does anyone know if there is a way to resolve this issue?
I have the exact same watch and pixel 6 pro, I am not experiencing this issue. Although I do not use google assistant, which was draining my phone and the watch like crazy as you report, after stopping to use I stopped having problems. August update Android 13 galaxy watch app was draining the crap out of my phone, to the point I mostly disabled it and manually allowed the sync, again after Samsung software updates and Sept build all of this has gone away again.
August update was so crap I also did a factory reset of the phone no restore to try to fix all of this, and other issues with Bluetooth, made no difference. With September update almost all these issues have gone away.
If you upgraded from 12 -13 not factory reset I would recommend doing that.
Or backup the watch and reset it, making sure you remove the watch for bluetooth devices on the phone before, so it sets up clean as a bluetooth device.
Do you think that if I disable Assitatant on phone this could resolve issue? I use this feature very infrequently. I do not have installed on watch. I did upgrade from from 12 to 13 as apposed a factory reset. I'm fine doing phone reset though a bit more work (backing up texts, photos, etc.). I did reset of watch after A13 update but pre sept update. Do you think resetting watch now after sept update could resolve? Thanks for your help!
It's Samsung health that's draining the battery. I rolled back to the July version of Samsung health and battery is great. You can also turn off Samsung health permission to "physical activity" and that will help. The problem is the August update for Samsung Health basically keeps keeps the app running constantly on Android 13 because it's trying to sense all physical activity from your phone and doesn't allow the phone to deep sleep. It's interesting because if you roll back to the July build of Samsung Health, you can keep the physical activity permissions on and it doesn't have the deep sleep issue.
Sorry to tell you I'm not experiencing this. I get a good 2.5-3 days of battery life with samsung health and everything running as normal on Android 13 and the latest GW4 update.
shiftr182 said:
It's Samsung health that's draining the battery. I rolled back to the July version of Samsung health and battery is great. You can also turn off Samsung health permission to "physical activity" and that will help. The problem is the August update for Samsung Health basically keeps keeps the app running constantly on Android 13 because it's trying to sense all physical activity from your phone and doesn't allow the phone to deep sleep. It's interesting because if you roll back to the July build of Samsung Health, you can keep the physical activity permissions on and it doesn't have the deep sleep issue.
Click to expand...
Click to collapse
I do not have Samsung Health installed on phone.
Teet1 said:
Sorry to tell you I'm not experiencing this. I get a good 2.5-3 days of battery life with samsung health and everything running as normal on Android 13 and the latest GW4 update.
Click to expand...
Click to collapse
On your phone did you upgrade from 12 to 13 or do a factory reset?
fliptwister said:
On your phone did you upgrade from 12 to 13 or do a factory reset?
Click to expand...
Click to collapse
I upgraded from 12 but didnt have any issue. I recently did a factory reset and I still don't have this issue.
fliptwister said:
Do you think that if I disable Assitatant on phone this could resolve issue? I use this feature very infrequently. I do not have installed on watch. I did upgrade from from 12 to 13 as apposed a factory reset. I'm fine doing phone reset though a bit more work (backing up texts, photos, etc.). I did reset of watch after A13 update but pre sept update. Do you think resetting watch now after sept update could resolve? Thanks for your help!
Click to expand...
Click to collapse
Yes, absolutely, do a search for something like huge battery drain after google assistant launches on watch 4, you will see it littered everywhere and the recommendation was to uninstall it. Quick and easy test, then if it makes no difference then just install it again.
shiftr182 said:
It's Samsung health that's draining the battery. I rolled back to the July version of Samsung health and battery is great. You can also turn off Samsung health permission to "physical activity" and that will help. The problem is the August update for Samsung Health basically keeps keeps the app running constantly on Android 13 because it's trying to sense all physical activity from your phone and doesn't allow the phone to deep sleep. It's interesting because if you roll back to the July build of Samsung Health, you can keep the physical activity permissions on and it doesn't have the deep sleep issue.
Click to expand...
Click to collapse
Yes there is a number of Samsung chats, blogs about this behaviour and for the best part Samsung seemed to shrug it off
shiftr182 said:
It's Samsung health that's draining the battery. I rolled back to the July version of Samsung health and battery is great. You can also turn off Samsung health permission to "physical activity" and that will help. The problem is the August update for Samsung Health basically keeps keeps the app running constantly on Android 13 because it's trying to sense all physical activity from your phone and doesn't allow the phone to deep sleep. It's interesting because if you roll back to the July build of Samsung Health, you can keep the physical activity permissions on and it doesn't have the deep sleep issue.
Click to expand...
Click to collapse
I do not have Samsung Health installed on phone.
edit - Is it Samsung Health on phone or watch which is causing battery drain?
danw_oz said:
I have the exact same watch and pixel 6 pro, I am not experiencing this issue. Although I do not use google assistant, which was draining my phone and the watch like crazy as you report, after stopping to use I stopped having problems. August update Android 13 galaxy watch app was draining the crap out of my phone, to the point I mostly disabled it and manually allowed the sync, again after Samsung software updates and Sept build all of this has gone away again.
August update was so crap I also did a factory reset of the phone no restore to try to fix all of this, and other issues with Bluetooth, made no difference. With September update almost all these issues have gone away.
If you upgraded from 12 -13 not factory reset I would recommend doing that.
Or backup the watch and reset it, making sure you remove the watch for bluetooth devices on the phone before, so it sets up clean as a bluetooth device.
Click to expand...
Click to collapse
danw_oz, when I finally reset my phone this fixed the issue for me. Thank you! I tried multiple other things and nothing worked. For me it was not assistant or Samsung Health.