Hi Greg Problem My bike is recording rides correctly, and the Avinox Ride app is receiving the ride summaries, but I cannot download the detailed ride data. Symptoms Last ride that fully syncs and opens correctly in the Ride app: 24/05 Every ride after 24/05 appears in the Ride History list on the p...
@Maxi - good write-up, that's a well-isolated fault report. Let me summarise where things stand and what I think is going on.
Thread Summary: Avinox Ride App - Ride Summaries Sync, Detailed Data Fails After 24/05
What's happening
Maxi's Amflow PL Carbon Pro (firmware 01.03.01.27) is recording rides fine and the app is clearly talking to the bike - settings changes push through, Bluetooth is solid. The problem is surgical: ride summaries (date, distance, location) appear in the history after 24/05, but tapping any of them for detailed data - map, elevation, power, cadence, calories, mode breakdown - returns a failed-sync icon and nothing ever downloads.
Everything before 24/05 works. Everything after 24/05 fails. Same pattern, every ride, without exception.
What's already been ruled out
• Bluetooth connection - still functional (settings sync works fine) • App/firmware being out of date - both confirmed current
• App cache - cleared, no change • Pairing issue - deleted and re-paired, no change
So it's not a comms problem between phone and bike. The bike is talking to the app just fine - it's specifically the
detailed ride file download that's broken.
The most likely culprit Maxi's own read of this is solid: the sharp cut-off at one specific ride points strongly toward a
stuck or corrupted entry in the sync queue, not a general connectivity fault.
The Avinox system is designed so that ride data syncs automatically to the app after each ride - and the drive system records comprehensive ride data which is then synced to the app after the ride. The summary metadata clearly gets through; it's the full ride file that's stuck.
The working theory is that the first ride after 24/05 either recorded a corrupt or malformed file, and that file is now sitting at the front of the transfer queue blocking everything behind it. The app sees the entry exists (hence the summary), but can't parse or download the full payload.
What to try next 1.
Check if the Avinox app has a "delete ride" function on the bike side - Avinox did add ride deletion support in a firmware update ( one release added support for deleting ride data). If you can delete the first failing ride (the one immediately after 24/05) directly from the bike's display or the app, it may clear the queue and let everything behind it flow through. Worth trying before anything more drastic.
2.
Check your Ride Data Backup / Cloud setting - once enabled, ride data can be synced and backed up using the mobile network, and the synced data can be viewed on other devices by logging into the account. If you have this enabled, the data may already be on Avinox's servers even if it's not rendering in the app - worth logging in on another device to check. Also worth confirming this setting hasn't been toggled off around the 24/05 date, which could explain the clean cut-off.
3.
Contact Amflow/Avinox support directly - this one may need a server-side fix or a log pull.
The Avinox Ride app has had known display and feature issues reported by users, and the support team has been responsive on here.
@Amflow_Support's post shows they're active on the forum - drop them a DM with your firmware version and the exact date of the first failing ride, and reference this thread.
What this isn't It's not a Bluetooth fault, not an out-of-date firmware issue, and almost certainly not a hardware problem. The bike is fine. This lives entirely in the sync/data layer - which is actually the better outcome, because it means the ride data is almost certainly still on the bike waiting to be retrieved.
Cumbrian trails presumably aren't going anywhere while you wait for the fix.
