Ticket Created
over 3 years ago

ACROPOLIS-2956

Transferred

Bug: Media / Communications SyncDelegate blocks charging

Media.SyncDelegate and Communications.SyncDelegate should have the same behaviour. The Media.SyncDelegate is marked as 'deprecated' and therefore I moved the app to the Communications.SyncDelegate version. This caused the syncs that are started automatically (e.g. during charge) to BLOCK the charging and remain at 0% progress.

The complete set of issues:

For Media.SyncDelegate: the Sync process can only be started automatically (e.g. during charge) or through the ConfigureSyncView (which is quite impossible to find for new users). Media.startSync() will open the ConfigureSyncView instead of actually starting the sync. Additionally, the class is marked as deprecated.

For Communications.SyncDelegate: the Sync process can be started from anywhere using the Communications.startSync() (which is good!). However, the automatically called syncs (e.g. during battery charge) will fail: the notifyProgress() function does not work anymore, the progress will remain at 0% and the battery charging is interrupted (or severely limited). The sync is performed in the background though, but the sync view is never updated and remains at 0%.

  • I confirm that this happens on the Fenix 6 Pro and the Forerunner 945.

  • @Alexis: The automatic synchronization happens during battery charge, not necessarily immediately after plugging in the device. Currently I implemented a workaround to detect manually started syncs by setting a property on user click, and unsetting it after sync completed. For automatic syncs this property is not set, and thus we know it is an automatically started sync. The getSyncDelegate function then returns either a Communications.SyncDelegate or a Media.SyncDelegate respectively. 

    @Rachael: The devices I got reports for are:

    Forerunner 245 Music - FW 5.50

    Forerunner 645 Music - FW 6.70

    Fenix 5 plus - FW 14.00

    Fenix 6X pro - FW 13.10

    Devices that I know do not show the problem:

    Vivoactive 4s

  • In physics I have 6XPro
    but even on the simulator on the devices handling the music there is the worry.

  • Are there any specific devices that you guys notice this is happening on? 

  • Hello, I noticed the same problem but for the users I went through Communications.SyncDelegate because it's easier directly from the provider than through ConfigureSyncView.

    Related question, how do you make sure that there is an automatic synchronization as soon as you plug the watch in? I never got the request.