• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Update pushing out now [ 2/12/16]

The update pushed to my device. I was very guarded about talk of the always-on dimmed mode being higher resolution than it had been. If it compromised battery life I would be against it. My fears were unfounded. I'm on ~16 hours and still at 55%.

And if you use a watch face that has high resolution images in dimmed mode, you're going to be in for a treat.

I think you guys will like it when you see it.
Upvote 0
Semi-unrelated question; I read somewhere (but can't find it now) that one of the Wear updates removed the ability to disconnect the watch, is that true? I use Android Pay and have to disconnect/reconnect to get it to work right with the PIN. I haven't updated Wear in a while because of that.
I think they briefly removed that from the phone's android wear application and put it back in the next version. I'm up to date on android wear version on my phone (no updates showing in playstore) and disconnect is available (top switch of attached screenshot)

My 360 mark 1 watch is on Lollipop LCA44B. Like some others I'm still impatiently waiting for marshmallow update (M-something) on my watch.


  • Screenshot_20160214-110517.png
    385.1 KB · Views: 216
Last edited:
Upvote 0
What I'm dieing to know is what happens if we use the new permissions to block all apps (moto and google) from accessing the heart rate monitor.

I have always been bugged by that watch heart rate monitor because:
  • It probably wastes juice.
  • I don't use it anyway.
  • It interferes with proper display of my chest-strap H.R.M. data displayed on the watch via my phone's SportsTracker app. During every run, three or four times the displayed number jumps out of whack and I have to do a couple of swipes to fix it (and I almost tripped one time... swiping while running doesn't always work so well!)

Maybe this will be the solution (I can only hope...)
Last edited by a moderator:
Upvote 0
Yeah, I've heard it is a staged rollout over approximately two weeks. Perhaps it gives them more opportunity to stop the rollout with limited numbers if big problems are uncovered in the first few installations. Or maybe it limits the load on motorola's servers. For whatever reason, that's what they do.

I've heard some folks say you can hasten the update by doing a factory reset of the watch, but I don't think it's a guarantee. I'm not that desperate yet, but I'll probably try that if I don't get an update by the end of the month.

In the meantime, I guess patience is the word of the month. Screaming at the watch doesn't help, I've found. But it made me better to scream here on the forum (my post all caps above).
Last edited:
Upvote 0
I'm wondering if there are others who have yet to receive the update? I have the 1st Gen Moto 360 and still show I have build LCA44B, with no updates available. From what I'm seeing from Motorola, it should be updating to MEC23I.

Is the update really going out this slowly or, for some reason, is my phone just not seeing the update?

I'm still waiting on the update as well.
Upvote 0
I got my update 2 1/2 weeks ago for my moto 360 1st gen. Got notice for update. Waited til I got home to charge it. 100% Did update. Checked watch 1/2 hr later. It was off. So turned it back on. Turned on...barely. It freezes every single tine on the Motorola "M" logo. Did hard reset by holding power button for half a minute until it shuts off. Decided to put it back on charge cradle thinking when it was updating battery went down (even if it was only 1/2 hr after 100%). It turned on when place in cradle but still freezes on the logo "M". Nothing. It's literally just freezes on logo. Any ideas to fix it. I'm out of warranty.
Upvote 0


We've been tracking upcoming products and ranking the best tech since 2007. Thanks for trusting our opinion: we get rewarded through affiliate links that earn us a commission and we invite you to learn more about us.