09-09-2023, 05:53 PM
(This post was last modified: 09-09-2023, 05:56 PM by Jens Noriʇzsɔɥ.)
Typically, it‘s the out-of-memory killer of the smartphone OS that kicks in on long measurements. There is nothing we can do about that and it also depends on other apps running in the background, so it is hard to quantify when it happens. Accelerometer or gyroscope data collection on Android can rather quickly lead to this. You could check if reducing the rate has an effect.
A lockscreen or putting phyphox into the background should not lead to data loss. Collecting data in the background would require some fundamental changes in the code – and there are substantial restrictions on (at least) iOS. We have added the option “Proximity lock” to the settings so that you could avoid unintended touch events.
For the time being, the app is not really built for offline long term measurements. You could find a remedy by writing the data to a web or MQTT client by the REST API, https://phyphox.org/wiki/index.php/Remot...munication, or network connections, https://phyphox.org/wiki/index.php/Network_Connections (requires changes to the .phyphox file). Alternatively, you could send data to a microcontrolller.
A lockscreen or putting phyphox into the background should not lead to data loss. Collecting data in the background would require some fundamental changes in the code – and there are substantial restrictions on (at least) iOS. We have added the option “Proximity lock” to the settings so that you could avoid unintended touch events.
For the time being, the app is not really built for offline long term measurements. You could find a remedy by writing the data to a web or MQTT client by the REST API, https://phyphox.org/wiki/index.php/Remot...munication, or network connections, https://phyphox.org/wiki/index.php/Network_Connections (requires changes to the .phyphox file). Alternatively, you could send data to a microcontrolller.