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.
Related
Any idea why my replacement GNex reboots randomly, many times a day? It will be sitting in my pocket, screen off, and I will feel it vibrate. Look at the phone, it's at the Google logo rebooting. Also, if I'm outside on cell data, streaming music with the screen off, it will die in a few minutes.
I did some digging and someone said there is a location bug in 4.2.2, and it is causing certain GNexs to act like this. This morning I shut off all location services and disabled Google Now. My phone lasted the whole day without a single reset, and I was able to stream music.
Is anyone aware of a fix for this? It seems to be an issue on my phone in stock 4.2.2, stock+franco kernel, and CM 10.1.
Thanks!
I've got a small issue with my N7. Since I bought it, my display turns on periodically without touching it or hitting any of the buttons. It seems, that the time periods inbetween are always the same (e.g. today its always 24 minutes after a full hour when it turns on). It just displays the lock screen and turns off again.
Is there a possibility to find out which app or service is causing this? As far as I can observe, there are no notifications coming in which could potentially turn on the screen.
I'm on stock 4.3 and switched meanwhile from the stock kernel to that one by faux123 (problem occurs with both kernels)
Thanks for your help!
The screen does not turn off
The problem with my N7 Wi-Fi is that the screen does not turn off. On the Nexus 10, the screen turns off within a minute.
On phones and the Nexus 7, when plugged in, the screen never turns off. Many customers have been complaining that the screen turned off at unsuitable times, so I think Google went crazy with it.
On my Nexus 7, the display is turned on by incoming Sipdroid calls.
What you can do is to look at logcat, but it will cost you tons of time to figure it out.
It occurs to me while the tab is unplugged. Perhaps i check if it also occurs in flightmode. Then i could see if wifi or an other connection is the problem!
Sent from my Nexus 7 using xda app-developers app
There were lots of comments (and still are) about how wifi is a battery killer on android wear. I'm not seeing this to be the case at all, when it's working like it's supposed to.
Since 5.1.1 my battery use has been around 3% and hour with all features on. Turning off bluetooth on my phone, with a 2/3 wifi signal on the watch, I'm seeing 2.5 to 3%.
Quick drain happens when walking around the edge of bluetooth range, as the watch switches back and forth between bluetooth and wifi. It seems that as long as it's not finding bluetooth, battery use is normal at worst for me.
I know that the moto 360 will switch to a state of only checking for updates occasionally to save battery, but I don't see this happening. Notifications are coming to the phone, and shortly afterward on the watch. I have not seen a time when a notification was delayed more than a few seconds.
The downside to wifi-only use: some apps that communicate with a phone app don't work. My watchmaker face doesn't update the phone battery level. Google voice commands fail too often, maybe half of the time.
I think google should change the frequency of attempting to reestablish bluetooth connection while on wifi.
Has anyone else tried this? Either turn off your phone's bluetooth, or make sure it is well out of range.
I'll give it a go tomorrow at the office and report back.
Sent from my Xperia Z3
Thanks to a heads up by DarkRazorZ, I learned wifi can be turned on in airplane mode. Will be looking to see if this makes any more difference.
Watch maker has been my biggest battery drain. It also makes the drop down menu laggy and impossible to use.
Yeah, I had that problem with watchmaker. I use intelligent and it seems to work well. Other people report facet works too.
I concur. Wi-Fi uses a lot less battery than Bluetooth, with an acceptable lag - 1-2 seconds on notifications. Bluetooth seems like a big battery drain on the phone and on the watch.
Sent from my Xperia Z3+
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.
Hello everybody,
sorry to bother this community, but I have a weird issue with the phone. My nephew gave me the Motorola G7 Play and when I am under any wifi (tried many) I do not received any notification. This does not happen immediately, but after the screen remains off for at least 30 minutes.
As advised from the assistance we have reset the phone at least twice and nothing has changed.
Do you have any idea if there are any tricky setting or application that are causing the issue?
Please, let me know if there is a quick fix, otherwise I will keep using 4G only as I am doing at the moment, this way there are no issues at all.
Have a nice day,
Cosetta
It might be memory management or there is a battery optimization setting that sends the phone to sleep when using wifi to conserve battery... Take a look deeper in the settings and perhaps turn off battery optimisation for apps that you need to keep receiving notifications for.