Problem with latest Android Wear

Mats Post time 2016-11-18 00:23:48 | Show all posts  Close [Copy link]
19 6461
View: 6461|Reply: 19

Problem with latest Android Wear

 Close [Copy link]

9

threads

345

posts

1871

credits

Diamond Member

Rank: 4

credits
1871
Post time 2016-11-3 02:10:34 | Show all posts |Read mode
IMG_20161102_190659_415.jpg WTF, Umi? My Wear watch is suddenly unusable!



3

threads

13

posts

55

credits

Senior Member

Rank: 2

credits
55
Post time 2016-12-20 18:10:34 | Show all posts
Mats replied at 2016-12-14 17:35
Seems like this is fixed in latest version (2.0.0.141773014.gms) according to Android Wear Help For ...

Solved by last official Android Wear update (from google play)

1

threads

28

posts

159

credits

Senior Member

Rank: 2

credits
159
Post time 2016-11-25 17:18:21 | Show all posts
well,
i am using an official rom (unles clean android 6 on umi plus is not official) and still i am facing this issue with androidwear 2.
so downgrading to android 1.5 still keep all functions ok and there are no problems with the connectivity to my smart watch.
will wait patiently to any future updates or any new version of functional androidwear 2.0

0

threads

6

posts

47

credits

New Member

Rank: 1

credits
47
Post time 2016-11-18 00:11:12 | Show all posts
Install the Android Wear 1.5 version. It works
http://www.apkmirror.com/apk/goo ... -download/download/

9

threads

345

posts

1871

credits

Diamond Member

Rank: 4

credits
1871
 Author| Post time 2016-11-7 17:45:35 | Show all posts
By the way, the solution to this problem is to change ro.build.prop from user to userdebug in the build.prop system file. Now the Android Wear phone app works again. However, it's be nice if Umi could get official Google certification, so we don't need this kind of trouble in the future. Maybe for the release of the Nougat update?

8

threads

12

posts

96

credits

Senior Member

Rank: 2

credits
96
Post time 2016-11-5 06:47:44 | Show all posts
Me too. Umi, Wtf have u done with the latest ROM. Android wear will not work as it thinks the phone is rooted. Bence please advise urgently. Thanks.

9

threads

345

posts

1871

credits

Diamond Member

Rank: 4

credits
1871
 Author| Post time 2016-11-5 19:09:41 | Show all posts
This isn't just Umi's fault. Google has done some breaking changes in the 2.0 Wear app. Even Nexus phones with Nougat are affected, along with many custom ROMs.

9

threads

345

posts

1871

credits

Diamond Member

Rank: 4

credits
1871
 Author| Post time 2016-11-7 17:32:42 | Show all posts
Here's an official Google explanation to this issue:
Thank you very much for contacting Google, my name is Vlad and we spoke over the phone. It was a pleasure to support you!
I've reviewed your account and I'm afraid that your devices, Elephone P9000 and Umi_Super, isn’t currently supported for use with the Google Play Store app or with play.google.com.
Sometimes a hardware manufacturer will use the free Android operating system on a device even if the device doesn’t pass Google’s compatibility requirements to have the Google Play Store app installed
In these cases, Google services such as Android Wear may not function correctly or at all on the device.

1

threads

45

posts

169

credits

Senior Member

Rank: 2

credits
169
Post time 2016-11-9 01:03:18 | Show all posts
Wtf... Didnt kno Android Wear was going to go that route. It better not start using SafetyNet.

0

threads

2

posts

31

credits

New Member

Rank: 1

credits
31
Post time 2016-11-17 14:14:26 | Show all posts
I have the same problem with my Zenwatch, i didnt noticed anything not working. Did you? Only the app wont open.

9

threads

345

posts

1871

credits

Diamond Member

Rank: 4

credits
1871
 Author| Post time 2016-11-17 16:09:51 | Show all posts
Yes, the app won't open. That's basically it, but I find that a problem enough. The cure is to edit build.prop and change ro.build.type to userdebug (instead of user).
The wear app checks ro.build.fingerprint and if it contains "release-keys" then ro.build.type should be "user". If not, ro.build.type should not be "user".  In the stock UMi Super ROM, ro.build.fingerprint does not contain release-keys (it's "test-keys" instead) but ro.build.type is set to "user" making the check fail.

Comments

Hi, could you explain how to do what you say?  Post time 2016-11-23 20:10

3

threads

13

posts

55

credits

Senior Member

Rank: 2

credits
55
Post time 2016-11-18 00:23:48 | Show all posts
Mats replied at 2016-11-7 17:45
By the way, the solution to this problem is to change ro.build.prop from user to userdebug  in the b ...

And no risk to modify a system file?
12Next
You have to log in before you can reply Login | WELCOME TO UMIDIGI COMMUNITY

Points Rules

Quick Reply Top Back to list