Page 1 of 1
"Failed to sync watch face"
Posted: 16 Sep 2020, 02:36
by e2m
AmazFaces app (Android), version 1.6.90
Zepp app version: 5.1.1
Watch: AmazFit T-Rex, ver. 1.0.0.1
Trying to install watch face, the AmazFaces app finds my watch and connects with it, and shows install progress all the way to 100%, and then about a minute later it fails - see screenshots below.
What could be the problem?
Thanks!
- af_100.png (40.88 KiB) Viewed 7312 times
- 20200915_D72_6825.jpg (54.09 KiB) Viewed 7312 times
- 20200915_D72_6826.jpg (55.11 KiB) Viewed 7312 times
- af_reconnect.png (31.86 KiB) Viewed 7312 times
Re: "Failed to sync watch face"
Posted: 16 Sep 2020, 07:06
by GIK-Team
e2m wrote: 16 Sep 2020, 02:36
AmazFaces app (Android), version 1.6.90
Update the application to the latest version.
Also, you can try the beta version:
viewtopic.php?f=23&t=590
Re: "Failed to sync watch face"
Posted: 16 Sep 2020, 12:12
by e2m
GIK-Team wrote: 16 Sep 2020, 07:06
e2m wrote: 16 Sep 2020, 02:36
AmazFaces app (Android), version 1.6.90
Update the application to the latest version.
This is the latest version available on Google Play.
Re: "Failed to sync watch face"
Posted: 16 Sep 2020, 12:41
by e2m
I just downloaded your beta (1.9.100). Still same problem.
I am also seeing this message popping up:
- af_2a.png (53.93 KiB) Viewed 7264 times
Re: "Failed to sync watch face"
Posted: 16 Sep 2020, 12:54
by Stas
You have the same error resetting the setting at 100 percent, right?
Re: "Failed to sync watch face"
Posted: 16 Sep 2020, 12:57
by e2m
Stas wrote: 16 Sep 2020, 12:54
You have the same error resetting the setting at 100 percent, right?
Yes, it goes to 100% and then says "Installed," but the watch says "Failed to sync watch face."
Re: "Failed to sync watch face"
Posted: 16 Sep 2020, 13:20
by e2m
OK, this issue seems to be specific to my Pixel 2 phone only. I just tried it on my old phone (Nexus 5x) and it worked fine. Strange.
Re: "Failed to sync watch face"
Posted: 06 Nov 2020, 22:16
by Jcvictor
I am using my Pixel 3 XL and I've been getting that error ever since I upgraded (accidentally) to Android 11.
Does anyone have any idea what I should do/try to resolve this issue?
-Jason