We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The sensing is not restarted when connecting the device. Here is the log:
[log] New connected device with serial: 233830000816 [log] [CAMS DEBUG] MovesenseDeviceManager - setting device status: connected [log] [CAMS DEBUG] MovesenseDeviceManager - Successfully connected. [log] [CAMS DEBUG] MovesenseDeviceManager - Getting device info. [log] [CAMS DEBUG] MovesenseDeviceManager - Setting up battery monitoring. [log] [CAMS INFO] MovesenseDeviceManager - Restarting sampling... [log] [CAMS INFO] Restarting TaskControlExecutor [729843102] (started) [log] [CAMS INFO] Restarting NoOpTriggerExecutor [740692428] (started) [log] [CAMS INFO] Restarting TaskControlExecutor [552593698] (started) [log] [CAMS INFO] Restarting ImmediateTriggerExecutor [680206657] (started) [log] [CAMS INFO] Starting BackgroundTaskExecutor [602670991] (started) [log] [CAMS WARNING] Trying to start a BackgroundTaskExecutor in a state where this cannot be done - state: 'started'. Ignoring this.
which shows that the BackgroundTaskExecutor isn't started, since it is already in a started state.
BackgroundTaskExecutor
started
The text was updated successfully, but these errors were encountered:
Similar to #408
Sorry, something went wrong.
fix of #442
8b4d071
Fix of Movesense issues
5a09329
* fix of #442 * fix of #444 * fix of #445
bardram
Successfully merging a pull request may close this issue.
The sensing is not restarted when connecting the device. Here is the log:
which shows that the
BackgroundTaskExecutor
isn't started, since it is already in astarted
state.The text was updated successfully, but these errors were encountered: