Open kjuntu opened 1 year ago
It is expected and intentional trade off.
Watch has limited resources. Sending the data to phone would impact sampling frequency of the watch in some cases and resulting signal would not be complete from my experience.
Starting the measurement from the phone only starts the measurement on the watch and no further interaction is taken, in order to free up watch resources.
Getting full signal is preferred during measurement.
Ok. It just seems weird because I can get the Acceleration data from the watch (it's a Galaxy watch 5) if I use the "I" in a circle on the phone app. Figured if I selected " Acceleration Wear OS" and then selected "Start Measurement", it should show data from the watch or at least say that it is being recorded by the watch app but not displayed live.
When I select the circle with the I next to Acceleration Wear OS, the small graph shows data from the watch and it seems to be relatively accurate and fast updating. However, as was already mentioned in the app, in order to get the graph on the phone to keep running and not stop after a short while, I have to turn on the always on display function on the watch and then open the SensorBox app on my watch, select view sensor, and then select Acceleration.
I will make it more straightforward in the next update that the graph on the phone cannot show the data from Wear Os measurement live. Thanks for pointing it out :)
When I open the app, tap the watch icon to connect to my watch, scroll to Acceleration Wear OS, tap the circle to select that option, then tap start measurement, it is showing my the accelerometer data from my phone, not from my watch.
If instead of starting a measurement, I tap the circle with the I next to Acceleration Wear OS, I get the correct graph with the watch accelerometer data.