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
(1) Issue observed during field testing with SampleApp 3.9.2, Android 8.1.0, Samsung SM-J327V.
To duplicate: Launch app, turn on toggle to start service, close app. Move phone until plugin wakes up (icon in system tray), then go to device Settings and turn off Location (little map icon). Plugin will not sleep after stationary state detected as it normally does, will stay awake indefinitely (if you tap Location back on, plugin will sleep again).
Expected behavior: Plugin will sleep shortly after stationary state detected (based on the 3 sensors M+A+G), independent of the user's Location setting.
(2) Beyond this I’ve observed the plugin not sleeping under other (normal) circumstances, for example driving in car and leaving phone while in store, then coming back to find the plugin still awake. I infer from this (based on my limited understanding of the plugin’s inner workings) that there are certain environments which might ‘adversely’ affect the behavior of the sensors, and in turn prevent the plugin from sleeping. Are there are any known issues or similar behaviors from your own testing that might help make sense of this?
The text was updated successfully, but these errors were encountered:
(1) Issue observed during field testing with SampleApp 3.9.2, Android 8.1.0, Samsung SM-J327V.
To duplicate: Launch app, turn on toggle to start service, close app. Move phone until plugin wakes up (icon in system tray), then go to device Settings and turn off Location (little map icon). Plugin will not sleep after stationary state detected as it normally does, will stay awake indefinitely (if you tap Location back on, plugin will sleep again).
Expected behavior: Plugin will sleep shortly after stationary state detected (based on the 3 sensors M+A+G), independent of the user's Location setting.
(2) Beyond this I’ve observed the plugin not sleeping under other (normal) circumstances, for example driving in car and leaving phone while in store, then coming back to find the plugin still awake. I infer from this (based on my limited understanding of the plugin’s inner workings) that there are certain environments which might ‘adversely’ affect the behavior of the sensors, and in turn prevent the plugin from sleeping. Are there are any known issues or similar behaviors from your own testing that might help make sense of this?
The text was updated successfully, but these errors were encountered: