Summary
Within Android Health Connect, I've been routinely exporting Steps data from my Garmin Connect, which is synced to my Venu 3 watch. Android Health Connect has an option to export the entire dataset (a sqlite .db file) each day, pushing it to my Google Drive. Throughout August 2026, I've been comparing Step reports against my Garmin Connect app. Note the export contains step data from both the Garmin Connect app and my phone's native pedometer, however I'm excluding pixel phone Steps from analysis.
I'm noticing there are certain days where Garmin Connect's one-way write is silently dropping blocks of hourly step data. This results in inaccurate step counts between my Garmin Connect app and the Android Health Connect platform.
In the month of August, there is 100% accuracy on 21 out of the 23 days so far. Inside Android Health Connect's database, 2 of the days are reporting fewer steps by 10-20%. For both days, it's related to a missing block of hourly step data.
Questions
- Is the Garmin Health Connect write triggered only by a watch sync event, with no later reconciliation? That would explain why data arriving after the last push of the day never gets written.
- Is there any supported way to force Garmin Connect to re-push a date range to Android Health Connect?
- Is this a known issue, and is a reconciliation pass on the roadmap?
I'm happy to provide the extracted per-record data for the affected dates if that would help, including timestamps, counts and record UUIDs. I have tried forcing a sync with watch Garmin Connect, and toggling the Steps data permission off and on in Health Connect.
Environment
- Phone: Google Pixel 9 Pro, Android17
- Watch:Venu 3
- Garmin Connect Android version: 5.27.3
- Health Connect version: 2026.07.09.00
- Timezone: America/New_York (UTC-4)
- Garmin has Health Connect write permission for Steps, granted and active throughout.
