Moto 360, Android Wear, Blocking Apps (or NOT), and Battery Drain (Google Maps)

It doesn't surprise me that navigation drains it. The key is what is happening when the app is blocked. If you can, can you try and have the app blocked and see if ti's a moto360 problem, or an android wear problem.

Thanks!
I have to travel locally later this week for work, making another 2 hour trip (each way) and will be using navigation for that as well. I'll block the navigation app on the ZenWatch and see what happens :) .
 
Well, I got home today, did a RESET and it still seems to be draining fast. I had 88% battery once I charged it for like an hour, but then it was already down to 66% after just doing the reset and setting it back up. What am I doing wrong?

I cannot uninstall apps from what I can figure out? I only have a few on my phone which also have a companion wear app (Fit, Amazon)

Also, I Did not add any watch faces. UGh!
 
Well, I got home today, did a RESET and it still seems to be draining fast. I had 88% battery once I charged it for like an hour, but then it was already down to 66% after just doing the reset and setting it back up. What am I doing wrong?

I cannot uninstall apps from what I can figure out? I only have a few on my phone which also have a companion wear app (Fit, Amazon)

Also, I Did not add any watch faces. UGh!
I would call Motorola. Let us know what happens.
 
I don't think it's a Motorola issue, it looks like an Android Wear issue. My LG G3 and G Watch have started having the same problem.

I don't often use Maps for navigating as I have a separate TomTom when driving, but when I had an issue with it a week or so back, I used my phone instead. My G Watch died after less than three hours on the road.

So I blocked Maps via the Android Wear app and tried again on the return journey the next day; exactly the same, G Watch died in less than 4 hours.

Something isn't right, but not sure what as I didn't have this issue a few months back.

Posted via Android Central App
 
I don't think it's a Motorola issue, it looks like an Android Wear issue. My LG G3 and G Watch have started having the same problem.

I don't often use Maps for navigating as I have a separate TomTom when driving, but when I had an issue with it a week or so back, I used my phone instead. My G Watch died after less than three hours on the road.

So I blocked Maps via the Android Wear app and tried again on the return journey the next day; exactly the same, G Watch died in less than 4 hours.

Something isn't right, but not sure what as I didn't have this issue a few months back.

Posted via Android Central App
Agreed, I never had this problem before. So weird. I actually turned in airplane mode when navigating somewhere today. An hour away, and I needed my watch later on for a race, so couldn't afford having a dead watch, so I turned on airplane mode. Hope this big gets fixed. How do we report this?
 
I made a three hour round trip Saturday with navigation on and my watch was dead when I got home. Not good!
 
I've been having the same issue since the last update. I have an hour long commute and use navigation to help avoid traffic. When I blocked the navigation app I still see the same problem. I don't have the issue on the weekends when I'm not using navigation. Is Google aware of this issue? I haven't found much information about it.
 
It doesn't surprise me that navigation drains it. The key is what is happening when the app is blocked. If you can, can you try and have the app blocked and see if ti's a moto360 problem, or an android wear problem.

Thanks!

I have to travel locally later this week for work, making another 2 hour trip (each way) and will be using navigation for that as well. I'll block the navigation app on the ZenWatch and see what happens :) .
My apologies for the delayed response here.... Been rather busy of late :( .

Here's what I found... On my way out to my destination (about 2 hours away), I used a Moto 360 connected to a Nexus 6 running 5.1. I I set yup the navigation on the phone and then waited for the first couple navigation notifications to come through on the watch, then blocked the navigation notifications on the watch. I didn't receive any more navigation notifications, but as mentioned here, my watch was just about dead by the time I reached my destination (I think it was at 13%). Serious battery drain there.

Now, here is the interesting part... On my way back, I performed the same exact test but with the Asus ZenWatch. As many have suspected, I had the SAME EXACT serious battery drain. This definitely appears to be an Android Wear issue not just a Moto 360 one.

One thing to note tho... This was all done *BEFORE* the android wear update on April 23rd. That update may have changed things!

Sadly, I don't have any more trips planned and really don't have much of a commute to test this again :( .
 
I've seen no change in this behaviour with the latest Android Wear update.
 
I've seen no change in this behaviour with the latest Android Wear update.
Ugh...So you have the latest Android Wear update and still the same problem? Which watch do you have again?

And how do we report these things to Google?

I keep forgetting to call Motorola. I have to make a reminder to do that! ! !

I have had serious battery drain issues on my watch, it's been weird. Without Google maps navigation, either...
 
Ugh...So you have the latest Android Wear update and still the same problem? Which watch do you have again?

And how do we report these things to Google?

I keep forgetting to call Motorola. I have to make a reminder to do that! ! !

I have had serious battery drain issues on my watch, it's been weird. Without Google maps navigation, either...
Moto 360. Had a further Android Wear update last night and will test with that next week.
 
Ugh. I am going to call Motorola tomorrow. Will let you know what they say...
 
Called. First guy was going to replace the watch immediately, but my serial number didn't work. This was on the phone. Second person, online chat, gave me some trouble shooting battery saving tips. Then I will get a replacement. All of this doesn't look good, basically, as in they don't seem to know it's a problem. Maybe a new watch will help? But if you guys are having the same problems...
 
This isn't a hardware defect, its a software problem introduced with one or more app updates.
With an unchanged pattern of use I went from less than 10% drain whilst driving for an hour using Play Music and Navigation on my Moto X2 with the 360 in cinema mode to 30% drain under the exact same conditions.
 
This isn't a hardware defect, its a software problem introduced with one or more app updates.
With an unchanged pattern of use I went from less than 10% drain whilst driving for an hour using Play Music and Navigation on my Moto X2 with the 360 in cinema mode to 30% drain under the exact same conditions.

I agree... but how do we get people to realize there's a bug out there? ANybody finding this type of thread elsewhere? How do we submit this problem... it's a HUGE problem. setting my watch to AIRPLANE mode when I use navigation isn't a good solution...
 
I agree... but how do we get people to realize there's a bug out there? ANybody finding this type of thread elsewhere? How do we submit this problem... it's a HUGE problem. setting my watch to AIRPLANE mode when I use navigation isn't a good solution...
Saw some chatter on Reddit about it a while back, other than that very little.
It would probably be more effective to get the major android news sites mentioning it though.
I've reported bugs to Motorola a couple of times with little / no effect apart from the odd email reply indicating that they've not really understood (or think I'm an ***** who can't use the technology concerned).
 
So, how can we tag Phil Nickinson?

@philnickinson?
No idea tbh.

I'm just hoping that the latest round of updates has sorted it. I should be able to test next week. Failing that, maybe Android Wear 5.1 will improve things.
 

Trending Posts

Forum statistics

Threads
957,078
Messages
6,971,382
Members
3,163,710
Latest member
liliin