This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Edge 1040 takes very long to upload ride over Bluetooth

andorsn
over 1 year ago

I have an Edge 1040 Solar that needs multiple attempts to successfully upload a ride over Bluetooth (connected to an iPhone 11). This can easily take 15 minutes or more. It doesn't matter whether the phone is connected to the mobile network (with good signal) or a Wifi access point. When I end an activity at home, in range of my own Wifi that is configured in the Edge, uploads are quick.

There is a similar thread from a year ago where people thought it would be specific to e-bikes, but it seems to be a general problem?

  • 0 over 1 year ago

    I would review the Bluetooth profiles saved in your iPhone to be sure there is nothing stale. Then I would delete your iPhone's Garmin Bluetooth profile and re-establish a fresh profile. Be sure to update your iPhone and Garmin head unit first.

  • 0 over 1 year ago

    I agree with to delete and re-establish the Bluetooth pairing.

    But Bluetooth Low Energy is inherently a low bandwidth protocol. It works fine for shorter rides (eg. 1 hour). But for longer rides (200-300km) where the file size is going to be quite large (I use a power meter and HRM, which increases file size), I will often just hot-spot my phone at the end of a ride for a much faster upload.

  • 0 over 1 year ago in reply to mcalista

    I don't think Bluetooth Low Energy being relatively low-bandwidth is the problem.

    Let's say the data is sent through GATT without any of the BTLE extensions. A throughput of 0.2 Mbit/s should be easily possible (according to https://interrupt.memfault.com/blog/ble-throughput-primer) - that's about 25 kbyte/s. A recent 4 hour ride with HR, Power and Core sensor data has a 1311kb fit file. At 25 kbyte/s that would take 52 seconds to transfer, way less than the 15+ minutes I am seeing. Unless each packet is sent directly to (and ack'ed by) Garmin's servers, adding huge amounts of latency, which would be... not very optimal.

    The next time I am in this situation I will see if Wifi works better. Trying it at home, I just get "sync failed".