The client has a Xiaomi Watch 2, WearOs4. After updating the watch face to WFS 1.8.10, the client, two of my already installed watch faces, began to behave inappropriately.
The screen on the smart watch constantly heats up and the watch face reboots. I will attach a video from the buyer, to illustrate the problem.
I advised resetting the smart watch cache, but the client claims that he cleared the cache for each individual watch face, but it did not help. He deleted and reinstalled the watch faces and the problem repeated.
But when he installed a new watch face, which was also updated in WFS 1.8.10, but had never been installed, there were no problems with the new watch face.
How to solve this problem? Is it possible to reset the entire cache on the Xiaomi watch 2?
Things he can try
1 - Restart the watch;
2 - Uninstall the watch face, restart and then reinstall;
3 - If the watch face is customizable, try to change one of the settings;
4 - Check if there is an update for his watch.
Things you can try:
1 - Test on a device (or emulator) to check if you can replicate the problem (if so, check the log);
2 - increase the version number, build the aab again and release an update, to check if the old aab had any problem;
3 - rebuild the watch face from zero…
Wouldn’t an update to Wear OS 5 solve the issues? Pretty soon Wear OS 4 and below are going to be left out, especially since Wear OS 6 is around the corner. Will Google Play even allow us to have “legacy” watch faces on Google Play anymore? If so, after Jan 26, 2026, we wont be able to sell them.
I am a xiaomi watch 2 pro user, technically it has the same features as the watch 2, if you want, I can install it on my watch as a tester and let you know the result so that we can understand whether the problem is in the watch or in the dial.
@Voron
would need more insight to say for sure.
Since you said, not all watch faces created using WFS 1.8.10 had the same issue. I believe it could be a problem on the specific device.
My suggestion would be to restart the watch, if it still persists maybe reset the watch and try again.