good stuff - thanks for doing this. i wonder whether autolocation needs to be on internal storage or not?
mine is on internal and does NOT give the option to move to sd, so i’m guessing it is SUPPOSED to be on internal anyway… but often that doesn’t really matter.
DriveFi does set the configuration of autolocation - but it doesn’t have to do so to a clean install of autolocation. DriveFi reapplies the settings each time the background service starts up (should be once per reboot, but possibly more often if you use a task killer, etc). i’ll check, but i don’t think enabling/disabling the service would actually trigger the config function for autolocation (it is handled automatically as part of the ‘context’ settings from Tasker - in other words it is beyond the scope of my own code and is performed by the framework I used to write the app).
if you see the issue again, it would be very interesting to also test:
does it remain an issue after a reboot?
what about if you move autolocation to internal storage? (perhaps requiring a reboot as well)
what if you uninstall DriveFi but start autolocation manually?