joshuajb / pebble-accel-log Goto Github PK

Things that should to be done:

1. Fix spelling mistake in Android code: "DOMINATE_WRIST"
2. Activities: change running to jogging, remove stretching, add staying still.
3. Watch and Android: Inform users that they need to completely exit the app to stop logging.

@naricdurmus reported in #5:

...if we want to measure for a longer time period (several minutes), we get the following error on the phone: 'It seems like a data buffer is out of sync. Data will be corrupted. Please flush buffers and try again.'

This message is displayed on the phone when the first message it receives from a sensor is not in the expected format (source code). Possible causes:

1. False detection of the start of a data stream
2. Loss of initial message between sensor and phone application in the datalogging component
3. Fragments from previous datalogging session

@naricdurmus: When you originally detected this issue, do you remember if the application showed the receipt of any data before the message popped up? If not, (1.) can be eliminated as a cause.

I downloaded today's code, and tried to run it on my phone. But every time I press the "Start" button, I get an message saying "Unfortunately, Pebble Data Logging has stopped". Joshua, does this happen on your phone?

@naricdurmus mentioned in #5 that it is very easy to accidentally exit the Pebble app. As this can ruin logging sessions, it would be optimal to ask for confirmation or require a longer button press on any activity which stops logging.

Adding the capability to run the logging application as a background app on the watch would also help avoid many of these issues.

Dear Joshua,

I have installed the app on my Sony Xperia S, running on Android 4.1.2, but when I try to open it, it gives the error 'Pebble Data Logging has stopped'. I also installed it on a Sony Xperia z3 (Android 5.1.1). On that phone it does work. Do you have an Idea what causes this?

Dear Joshua,

We have tried logging accelerometer data for a longer time. Our goal is to log for 24 hours. However the first measurement gave the following error after 8 minutes: 'It seems like a data buffer is out of sync. Data will be corrupted. Please flush buffers and try again.' The second measurement did continue but the Android app displayed a negative time. When we checked the data we saw the following time values over sample numbers, see Plot_Time-sample.

. Although we expected a linear line, as time increases with a fixed step.
Do you know how to solve these problems and is it possible to measure for 24 hours?

Also we wondered if it is possible to require to press the stop button for a longer time to stop the measurement, to prevent it to be stopped accidentally?

Greetings from the Netherlands!

@naricdurmus reported in #5:

Another error occurred on a different smartwatch and phone combination, the smartwatch displayed after several minutes: 'Someone else is writing to this logging session.' Afterwards, the phone application restarted itself (while receiving the data from the Pebble) and no data was saved.

Not entirely sure why this is happening. Something similar occurred once during my longest test session on #5 while I was disconnected from my phone. Through some combination of button presses (which I do not remember) I managed to get the watch app back into the normal logging mode without exiting. I was then able to save the results and noticed no abnormalities besides a few missing minutes of data.

I suspect that this message is appearing and pausing logging due to a temporary lack of accessibility to the datalogging session on the watch. A possible fix may be retrying the write or temporarily storing readings in-RAM until the datalogging session can be accessed again.

The reported issue with the Android application is rather baffling. Unless ADB logs of the crash are available, I'll assume that it's a side-effect of the watch app error and focus on that.