I use a few different WearOS devices in my day to day. I bought a Galaxy Ring so that I could get continuity of metrics in Samsung Health since some data (like steps) are not read from Health Connect into Samsung Health. So, with the Ring, I was hoping I could have it update metrics in Samsung Health while I was wearing my Pixel Watch 3. However, I also want Samsung Health to Write to Health Connect for steps because sometimes I wear a Galaxy Watch Ultra.
This should all work with the Health Connect API resolving data conflicts to prevent duplicate counting from different sources at the same time.
The only problem is, Samsung Health is writing steps to Health Connect with a 12:00am to 11:59pm timestamp, all in one entry spanning the whole day. Usually apps write steps to Health Connect in small chunks in a few minute time span.
Because Samsung Health is time stamping the steps for the full day in one entry, the Health Connect API isn't properly able to throw out duplicate entries if there are conflicts. It also means you don't get activity level detail by knowing how many steps per hour you are talking when viewing the data in Health Connect.
This greatly diminishes Samsung Health's contribution to Health Connect and it would be great if it could be corrected to write data at the same temporal resolution that it stores it in Samsung Health.
