Updated yesterday via USB and garmin express and since then, it is randomly restarting after some notifications, already happened 4 times since last night. Anyone else?
Updated yesterday via USB and garmin express and since then, it is randomly restarting after some notifications, already happened 4 times since last night. Anyone else?
There is an open ticket with our engineering team that is being investigated. We have gathered error logs from users that are affected and hope to have a resolution soon. This continues to be an issue…
We wanted to touch base with everyone as we are still looking into this issue. I know there have been questions as to why we are not able to reproduce this internally. This is a thread dedicated to this…
We have released a beta to address this issue which can be found here. We will be closing this thread and monitoring feedback in the sticky post linked.
The changes in the above linked beta will be rolled…
This was my data yesterday. The first gap is overnight and I wasn't wearing the watch. The second gap from 8:30am to 3:50pm I was wearing the watch the entire time and after receiving a notification at…
I disabled most notifications (left calendar reminders on), and have still had 2 reboots this morning. I also have the missing sections in my 'graphs' as others have described. This OS update is…
This was my data yesterday. The first gap is overnight and I wasn't wearing the watch. The second gap from 8:30am to 3:50pm I was wearing the watch the entire time and after receiving a notification at 3:50 the data has just gone. There are similar gaps for stress and body battery.
245 non music, connected to Sony XA-2 running Android 9. Ultra Slim watch face installed.
Watch was perfect for a week before this update. Pretty disappointed with it now. it doesn't say much about the testing process if this can't be replicated. I only get a handful of notifications each day (between 3 and 5, sometimes more) and the watch restarts around once a day, losing all data since the previous sync.
Is there a memory issue with the 2.70 update? Could the notification cause a memory spike and cause the watch to crash? Is it possible to access logs on the watch to find a crash dump or some other reason for the restart?
If Garmin are unable to replicate the issue you should be leveraging your users here to assist, because at the moment it's been 11 days since this update went live which has a watch breaking bug in it and the official response is lacking.