Acknowledged

Calling Communication.startSync() after recenty sync sometimes fails and then drains battery in background

I have found an odd bug with audio providers and the request to start sync (Communication.startSync).

If I start a sync that then completes, and immediately after start another sync, the sync will fail immediately (before/during "connecting to wifi"). I've added logging to my app to verify that this happens after calling startSync(), but before the control enters my app again.

When this happens (the sync fails during wifi connection phase), the battery of the watch (Fenix 7 Pro) will then drain very quickly until the watch is restarted (or runs out of battery).

I'm not sure what the exact thing is to trigger it, but it seems like it only happens when requesting another sync closing after completing one.

Parents
  • I guess this has to be fixed in the firmware. Would be good to provide example device(s) with firmware version so Garmin can reproduce it. Actually even better to provide them with an example app that reproduces it.

Comment
  • I guess this has to be fixed in the firmware. Would be good to provide example device(s) with firmware version so Garmin can reproduce it. Actually even better to provide them with an example app that reproduces it.

Children
No Data