My 645 (non-music) froze on the first run after the update to 3.30. See attached error-log. I was using the back to starting point function (straight line) while this happened. The watch never froze before,
rtperna : Have you tried a hard reset since the update? At one point with my 235 I started getting crashes when trying to save the config of a watchface change (just one watchface) - possibly some spot of the flash was bad and the OS wasn't handling it well. After a hard reset the problem went away.
Still running 3.10 on my 645. (edited for spelling)
positive feedback. I think it has been 5 runs since the new software (3.30) and NO issues with the headphones/music etc. watch is working as advertised. I am also pretty sure the software update helped the pairing of my headphones too. Now when i turn on my headphones (Aftershokz Air) and open the music on my watch, i hear a prompt that says "device 2 connected" (device 1 is my phone and it just says connected). and everything works just fine.
rtperna : Have you tried a hard reset since the update? At one point with my 235 I started getting crashes when trying to save the config of a watchface change (just one watchface) - possibly some spot of the flash was bad and the OS wasn't handling it well. After a hard reset the problem went away.
Still running 3.10 on my 645. (edited for spelling)
By "hard reset", do you mean completely set up the watch as factory? Because I'd really rather not do that... and for the record, the crashing didn't start until I installed 3.3. It was rock solid on 3.1 and earlier.
So I went ahead and factory reset my watch. We'll see if that fixes my problem. It was a real joy spending 20 minutes going through and setting up my settings from scratch, and then trying twice to add my credit card to Garmin Pay and having it fail both times (I had used it before no problem - Chase card). Just so irritated with this product right now. Everything was smooth sailing until 3.3 came along and screwed up my watch.
Since upgrade to 3.3, altimeter accuracy seems pretty unreliable. example run screenshot starts and finishes at the same elevation and 5 x identical hill repeats hardly register after the 1st. In addition, blue triangle crash after first run following update... and today, complete locking of watch face with the backlight on, causing massive battery drain. No buttons would function once this happened and only a 'reset' [holding the power button for a number of seconds], would allow the watch to shut down. A re-start bought the watch back to a normal working condition.
Firmware 3.3 . Two days ago had the blue triangle when I pressed the button to save activity. Reset the watch with a long press . I have now noticed that lactate threshold data has been lost and reset to 46? On the watch . Connect app has the correct data but wont sync the value to the watch, allso heart rate data from connect will not sync either way. Watch detected a new max heart rate but never syncs to connect. Heart rate zones etc im sure used to sync either way on the old firmware.
Have been following this thread and I am nervous. My watch is still on 3.20 version and the run with music is working without issues so far, Had 6-8 runs already with no setbacks. Is there a way to stop the watch from updating to the latest firmware?
