Mismatched versions

pazzo02

Well-known member
Feb 16, 2011
1,168
75
0
I've had issues with my watch over the last week. First when I updated the Android Wear app, then when I updated my phone to 7.1.2. Both times I had to factory reset the watch, and setting it back up didn't go as smoothly as the first time. For instance, the first time I set it up it had phone audio, media audio, contact sharing, and message access in the bluetooth settings on the phone. Now it only shows phone audio and contact sharing. Also I can't set up wifi anymore because when I tell it to open on phone it says that bluetooth is off or the phone is too far away, neither of which are true. So in trying to figure out what is up, I noticed in the watch settings under about>versions that the Android Wear version doesn't match the app version and the Android OS version doesn't match my phone. Can anyone confirm that they see the same thing?
 
Here are the versions of the various things on my phone and watch.

On Phone:

Zenwatch manager 3.2.0.170126
Android wear 2.0.0.145450541.gms
Android version Phone (Pixle): 7.1.1

Watch:
Settings/About:
Android Wear 1.5.0.3579309
Google Play services 10.2.89
Android OS 6.0.1
Android security patch level December 1, 2016

No problem for me to connect to the phone. Other than a recent significant drop in battery life (see separate thread) everything seems to work fine.
 
Those are the same for me except my 5X is on 7.1.2, and that could be part of the problem. Another specific issue that I have is that I can't change watch faces when the Zenwatch Manager app is installed. It just says "loading" for about 10 seconds then says "refresh" with no face in the background. When I uninstall Zenwatch Manager it works fine, although you can't change the look of the faces (steps, battery, etc.). I reported this to Asus and got a response back to make sure the apps and Play services were updated, and they are and still having the problem. I relayed that back to them and I'll report back here if I hear back.
 
Happened to me. Luckily I had the previous version to rollback to. I saved the apk. The latest zenwatch manager causes this so I rolled back and its all good now.