Problems syncing long dives

I have noticed that I get multiple sync failures after doing log dives (90 minutes and greater). It appears the FIT file gets to a size where a timeout between the Descent and Garmin Connect Mobile becomes more likely. This happens even when the Descent is less than a metre from my iPhone.

I'm sorry the image is so small. These fora make it impossible to upload a image and keep its size. You can at least see how many times sync has failed.

Here are the errors from the sync report which are common across all the failed syncs for long dives. Eventually, it will sync but it can take an hour of trying.
[FONT=courier new]UPLOADS

File Type Filename Size (bytes) Status
-------------------------------------------------------------------------------------------------
FIT_TYPE_4 1-3966683484ble-FIT_TYPE_4-2859-31-893653287 245543 Error
FIT_TYPE_35 (null)79 Cancelled
FIT_TYPE_32 (null)2901 Cancelled
FIT_TYPE_32 (null)484 Cancelled
FIT_TYPE_32 (null)431 Cancelled
FIT_TYPE_32 (null)624 Cancelled
FIT_TYPE_32 (null)431 Cancelled
FIT_TYPE_32 (null)569 Cancelled
FIT_TYPE_32 (null)554 Cancelled
FIT_TYPE_32 (null)902 Cancelled
FIT_TYPE_32 (null)749 Cancelled
FIT_TYPE_32 (null)554 Cancelled
FIT_TYPE_44 (null)335 Cancelled
FIT_TYPE_41 (null)14789 Cancelled

DOWNLOAD DEVICE FILE TYPES

File Type
-------------------------------------------------------------------------------------------------

DOWNLOADS

File Type Download ID Size (bytes)
-------------------------------------------------------------------------------------------------

ERROR DETAILS

Error Domain=GCMSyncErrorDomain Code=2 "Device connection error" UserInfo={SyncErrorReason=File UL: Failed to receive file from device, NSLocalizedDescription=Device connection error, NSUnderlyingError=0x1c4a5f3e0 {Error Domain=GarminDeviceSync.FileTransferErrorDomain Code=16 "(null)" UserInfo={GarminDeviceMessageError.ErrorReasonKey=Timed out waiting for file data request.}}}[/FONT]

0 Garmin-Heath over 6 years ago

atj777, Thank you for all this information and the error message you got too.

The issue you are experiencing could be caused by multiple things and we need to narrow them down to see where the issue is.
Bluetooth transfer at a very slow rate, due to that, any interference in the area could cause the upload to fail. Have you noticed that you having any issues with just one location or has this been happening at multiple locations?

Other things that could be causing that to happen is a slower than normal internet speed. Avoid using work or public hotspots to upload larger activity files due to the fact they have slower than normal upload speeds. If you are not using WiFi but instead using your phone’s internet connect, restart your phone and try again. If it fails again, try with your home WiFi connection to see if that makes a difference.

0 atj777 over 6 years ago

Have you noticed that you having any issues with just one location or has this been happening at multiple locations?

It has been happening in multiple locations. I normally try it at the dive site and after it fails a few times, I try in the car on the way home. It eventually works after 3 to 10 retries and the location it finally works varies.

Other things that could be causing that to happen is a slower than normal internet speed. Avoid using work or public hotspots to upload larger activity files due to the fact they have slower than normal upload speeds. If you are not using WiFi but instead using your phone’s internet connect, restart your phone and try again. If it fails again, try with your home WiFi connection to see if that makes a difference.

I'm normally away from home (dive sites are more than an hour from home) when I attempt to sync and am connected via 4G on my phone's internet connection. I will run a Speedtest next time to get the internet connection speed.

0 atj777 over 6 years ago

I did a 102 minute dive today and it synced immediately.

The only thing that has changed is my Descent was automatically upgraded to 2.50 some time in the last few days. Either something in 2.50 fixed the issues or the recycle that must have occurred as part of the 2.50 upgrade fixed the issues.

I now see no sync failures in the sync reports for the last 2 days.