You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
During testing of #2576 it became clear that some sensors need some time after initialization to send valid data. In the implementation suggested in #2576 the sensors are initialized on every orientation change which results in missed and in invalid data in orientation change.
Expected Behaviour
The sensor should not be re-initialized on orientation change and fetching sensor data should not be stopped on orientation change. This may be prevented by moving the fetching of sensor data to a service.
Steps to reproduce it
Attach a sensor to the PSlab board, attach the board to the phone, open appropriate sensor activity, change orientation. There should be a gap in the data diagram.
Screenshots of the issue
In the following screenshot I have changed the orientation twice which resultes in two gaps.
Would you like to work on the issue?
Maybe
The text was updated successfully, but these errors were encountered:
Actual Behaviour
During testing of #2576 it became clear that some sensors need some time after initialization to send valid data. In the implementation suggested in #2576 the sensors are initialized on every orientation change which results in missed and in invalid data in orientation change.
Expected Behaviour
The sensor should not be re-initialized on orientation change and fetching sensor data should not be stopped on orientation change. This may be prevented by moving the fetching of sensor data to a service.
Steps to reproduce it
Attach a sensor to the PSlab board, attach the board to the phone, open appropriate sensor activity, change orientation. There should be a gap in the data diagram.
Screenshots of the issue
In the following screenshot I have changed the orientation twice which resultes in two gaps.
Would you like to work on the issue?
Maybe
The text was updated successfully, but these errors were encountered: