Suunto 9 Peak Pro no watch faces on watch and in app
-
@Antanas-V I’m running the same iOS and SA version as you. I’m guessing that’s the issue.
-
@duffman19 I guess too, but don`t want to change my iPhone SE 1gen for that!
-
@Antanas-V I thought I was the only one still using that phone! Hopefully it’s a backend issue with SuuntoPlus (maybe related to upcoming watch firmware or SA updates) and it will get resolved soon.
I don’t mind the stock 9PP watch face, but I much prefer having an analog one. In fact, I’ve gone back to wearing an original 9P while this gets sorted since all of the faces are built-in to the software.
-
Today I switched back from the Vertical to the 9PP. The question wasn’t whether the watch faces would be deleted and reset to the default watch face, but whether it would happen on the first or second sync with the app. Surprise, it was the second one!
-
The 9PP resetted over night to the standard watch face without beeing connected to SA.
The Vertical with the first sync this morning.
-
@pilleus This is strange, I do not have any issue with watch faces and my SVTS, I’m using last SA beta and las firmware in the watch. I just have synced the watch and everything went as expected. My current watchface is the Race 2 one.
-
I use this one on both watches. Since a long time. Never before the first crash on Suunto’s Plus side any issues. Since that moment again and again the reset to the standard watch face and no other watch faces on the watches. After some syncs the watch faces will be back, but all configuration is löst.
I resetted both watches to factory settings, no luck.
-
Have I already told you what the 9PP did this morning? The daily watch face madness is going on.
-
Okay, it was in the morning. Now I connected the Vertical to use it for cycling.
Suunto app decided to show the standard watch face during the first sync.
Suunto, I accept the challenge!
-
@pavel.samokha Any updates on this? My watches (9PP and V1) are still affected and unable to load any SuuntoPlus watch faces.
-
@duffman19 Same problem still persists on my V1.
