Reset while charging
-
@Kornel-van-Doorn I’ve only had this problem once since the watch came out. Full charge, black screen and reboot. As @surfboomerang says, it’s normal for the fields to be empty after a reboot.
-
@Lechamoix yes understand, BUT WHY do the watch a reset by charging?!
-
@Kornel-van-Doorn I’m having the exact same issue. When charging the Vertical crashes, creates an error log message and restarts.
Doing so, I lose all data and custom workouts. It requires me to reenter each one as I had before. Quite annoying!
-
@GiPFELKiND I think there must be some kind of bug related to charging. Mine appeared to be bricked after I left it on the charger but came back after some button mashing.
Suspect a lot of the reports on the forum about dead verticals is the same issue.An update any day now would be good Suunto…. Clearly not enough resources at the company to support the vertical and the upcoming release next month.
-
Yesterday my Vertical crashed when connected to charger.
After a pair of minutes it showed this message in the screen: “The device is being restored to a safe state”:After some minutes in a loop, watch started and showed these messages:
Error 1403.
I tried to connect again to the charger and same behavior after some minutes charging: “The device is being restored to a safe state”. I tried several times until charge was over 50% disconnected from charger and performed a factory reset.After that I reconfigured the watch, charged full battery and downloaded maps without problems, only one watch reboot (watch rebooted itself while charging) as it’s said in this topic.
Today I’m going to try it outside in a running training. Hope it performs well…
-
This post is deleted! -
@jjpaz I’ve seen the exact same thing when charging. Reboot and restore. Not sure why this is occurring as I’m using the factory cable and correct wattage charger. Never saw this before with my Peak
-
Solar or non-solar version?
Could it be that the watch crashes on a pending map download? That is the only thing that starts after a while when connected to a wall charger (and WiFi) as far as I know. -
@surfboomerang Non solar (All black model).
No, I wasn’t dowloading map, only my every 2 weeks ordinary battery charge because watch had 10% battery left. And watch is 4,5 months old, it’s been full charged several times since may and this is the first “charging issue”.The curious thing was that I wasn’t be able to perform reset to factory settings until battery is at least at 40% of full charge so watch suffered at least 3 “reset to safe state” loops until reach 40% battery level.
-
@jjpaz Did you send the log files to Suunto?
-
@SuperFlo75 Nope… ️
-
@jjpaz I guess it is “solved” for now.
I am curious what happens if you disabled bluetooth on your phone before charging. Or unpair the watch at all from SA. -
Logs sent to Suunto, 18:54 Madrid time.
-
@surfboomerang Mine is a solar; was connect to wifi to update maps and charging. Crash occurred while watch switched from the round charging display to the watch display with charging icon.
Crashed at 97% charge and performed factory reset causing the data to be lost and having to manually change the settings on the watch (sex, height, weight, sounds, sleep tracking, sport mode, etc).
What is strange is I do not see the option to send logs to Suunto on the app.
-
@Todd-Danielczyk Same for me. Screen changed to watchface with time and charging icon instead of the round charging bar screen. I’ve never seen that screen before, always the new charging screen…
-
@jjpaz please send logs and DM me email you use in Suunto App (and please don’t create duplicate posts/topics)
-
@Todd-Danielczyk Depending on the app version/platform feature to send logs is either in the end of the Settings or in the Watch menu
-
@pavel-samokha Done, thanks!
-
@pavel-samokha thank you. I will check and send.
-
@Todd-Danielczyk @jjpaz
Thanks for your logs.Unfortunately we couldn’t pinpoint exact cause from them, but there are two things I’d like to ask you to do:
- Try to disable WiFi on the watch (Settings -> Connectivity)
- If issue happens again please try to send the logs as soon as possible