-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
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
Sensorium starts at boot regardless of settings #15
Comments
|
@anarcat: Sorry for that, it seems that we don't handle the settings checkbox value correctly. Do you happen to have |
|
On 2016-03-30 09:49:31, aaaaalbert wrote:
I can give you that when i finally reboot the phone, but i'm in the |
|
Oh, okay. No worries though, I can check on a device of my own later today. |
|
this starts with the checkbox on, i disable it an re-enable it: i am not sure how to extract relevant parts of the boot process unfortunately. |
|
Thanks! I tried with a debug build and see pretty much the same log output when I toggle the setting. On boot, the boot completed broadcast receiver seems to read the new value OK: ...but then it is started anyway, I guess from the manifest. I'll try to remove the |
|
Removing After some debugging, I saw that I tried to isolate the boot comleted receiver so that it doesn't import other parts of the app, but the Application still binds. Alternatively, removing the boot completed receiver from the manifest completely disables autostart. Looks like this requires larger changes to the app architecture to fix. When set to do start on boot: When set to not start on boot: |
I just rebooted my phone and sensorium is running even if i disabled that in the sensorium settings. I can't find a way to make it not start at boot.
The text was updated successfully, but these errors were encountered: