WristviaWatch records have reached Health Connect, and Tomas confirmed synced data in Google Fit. Sync is optional and requires consent and permissions. Nearby transfer now uses Bluetooth; approved Internet Backup adds a route while apart.
From watch permission to Android history
With Health sync enabled, Wristvia reads the Apple Watch HealthKit types you authorize, transfers encrypted batches over the nearby Bluetooth link or approved internet route and keeps received records in Wristvia’s phone archive. It writes supported records to Health Connect when Android permissions allow it. This implementation’s Health Connect writer requires Android 14 or later.
Health sync has its own opt-in and permissions. The current nearby path transfers health records over Bluetooth without requiring Internet Backup. Approved backup remains an optional internet fallback; nearby linking alone does not grant Health consent. See the health privacy explanation.
Verified results and destination limits
2 November update: the physical watch sent one real health record through the dedicated Bluetooth receiver, and the phone saved it and completed one Health Connect write. Internet Backup was not switched off during this test, so it verifies the direct Bluetooth route, not an airplane-mode run. Large imports, interruptions, coexistence with alerts/media, overnight behavior and physical unlink remain unqualified.
Recorded 29 October runs wrote supported sleep, heart-rate, resting-heart-rate, respiratory-rate, blood-oxygen, steps, energy and walking/running-distance records to Health Connect without reported write failures. Tomas confirmed Google Fit displayed synced data after its read access was granted. Later checks recorded three sleep nights on the phone.
Some watch types have no faithful Health Connect equivalent and stay in Wristvia’s archive. Newer workout/route and other types exist in source but do not all have equivalent physical qualification. Receiving apps choose which types they read and display; these tests do not establish Samsung Health, Honor Health or universal receiving-app support.
Permissions and source priority
Allow only the HealthKit types and Health Connect write permissions you want. Wristvia’s Android implementation requests writes, not reads of other apps’ Health Connect data. A receiving app such as Google Fit needs its own read permission in Health Connect.
If another app or the phone also writes steps or other activity, review Health Connect source priority to avoid misleading totals. Revoking permission stops future access but does not necessarily erase records already stored.
Apple explains HealthKit privacy; Google explains Health Connect access.
Sleep and ongoing qualification
The app derives a sleep view and estimated score from available records. The score is Wristvia’s calculation, not a direct import of Apple’s score, and its calibration remains limited. It is for personal wellness, not diagnosis or medical decisions.
Reboot recovery, long-term completeness, background timing, deletion propagation and each newly supported data type need further physical checks. Archived records and confirmed Health Connect writes are different states.
Two separate places to delete
Under Health sync → Your data, Delete Wristvia’s data from Health Connect removes records Wristvia wrote there. Delete health history on this phone clears Wristvia’s archive. Each keeps the other store, so choose both if you want both cleared. Pause sync first to avoid new transfers.
Neither control deletes the original Apple Health records or copies other apps already retained. Full deletion propagation remains a device-test gate. See all data controls and deletion requests.