This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Vivoactive locks up at "updating" when removing from charging cradle

Former Member
Former Member
This problem started about 2 weeks ago, maybe shortly after updating to 4.30. But my device now will lockup when I remove it from the cradle after a sync. Normally I see the message "updating" pop up for 3-5 secs and then the regular watch face appears with the time. But every so often, it will just hang at that updating screen and there is nothing I can do but let it sit until the better goes dead which normally takes 8-10 hours.

Is there some update that it is trying to apply and it's getting hung? Or is my watch just starting to die? Is there a way I can manual wipe and reload the software to give it a fresh start?

Thanks
  • This has happened to me maybe once or twice in the year I've had my VA. What I started to do is to do a USB safe remove from my computer prior to removing the VA from the cradle. It has never happened since.

    What I recall doing when it happened to me was to simply press and hold the power button long enough so that the watch turned itself off. Then I restarted the watch and it would be fine. There was no reason to wait for the battery to die.
  • This has happened to me maybe once or twice in the year I've had my VA. What I started to do is to do a USB safe remove from my computer prior to removing the VA from the cradle. It has never happened since.

    What I recall doing when it happened to me was to simply press and hold the power button long enough so that the watch turned itself off. Then I restarted the watch and it would be fine. There was no reason to wait for the battery to die.


    Can advise what you meant by "to do a USB safe remove from my computer"? Do you mean "eject the disk" before unplugging the cable?
  • Yes. Exactly.
    I use a program "USB Safely Remove" from Crystal Ridge rather than the standard eject feature in Windows so that's why I called it that.