Closed louisg1337 closed 4 months ago
@louisg1337 I will push this to staging once the UI changes have been pushed to production. you should also be able to manually kill the foreground service using adb
, at least for testing why the foreground service doesn't restart after it is killed
Previous Changes
ActivityRecognitionChangeIntentService
and checked to see if location services were availableNew Changes
DataCollectionPlugin.java / onResume()
gets called already implemented (here)DataCollectionPlugin.java
calls onStop()
, onDestroy()
, and onSaveInstanceState()
ActivityRecognitionChangeIntentService
These are all the logs that I have added in this PR. I think these should be sufficient as they cover our basis of checking the foreground service, the current state, and if the plugin itself gets killed by the OS. If there are any other places where I should put some logs please let me know!
@louisg1337 you also need to bump up the version in plugin.xml
Add logs to the FSM to figure out why trips don't track or why their tracking is messed up on Android.