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
easer doesn't start on boot #44
Comments
Thanks for reporting. (Not sure why you can't re-open that...I remember the default is everyone can do that.) |
1e5c2cc (v0.4.6.1) fixes the problem I observed. Not sure if this is the only cause, so I'll leave this issue open until the fix is confirmed. |
Thanks for the quick response! I will need to wait for this version to make it into F-droid before I can confirm your fix resolves the problem for me :) |
I'm running 0.4.7 now (and Android 8.1), and Easer still doesn't autostart on boot even though the option to do so is checked. Is there anything else I can provide you to help debug this? |
You are right. I tested it on an Android 8.0 phone and Easer also doesn't start on boot, though it it working correctly on my phone (Android 6.0) and the emulators (I only installed 5.1 and 6.0 emulators). It may be something related to Android system change in 8.0 (or 7.0 maybe?) that wasn't documented well or didn't emphasised enough. I searched a lot but got nothing, though there must be a "fix" somewhere. (See the note below for all I got if you are interested.) If I find out what's going on (or better a fix directly), it will be included in Easer. However, currently there doesn't seem to be a way to get around... Interestingly, during my test, the On the Android 6.0 emulator, I need to grant Easer all permissions it needs (I didn't really test whether this is necessary or not, but I tested the Notification Listeners, and the Event one must be enabled for Easer to auto-start -- though in theory they shouldn't have any relationships). Enabling and disabling the "auto start on boot" setting isn't enough in my test -- I need to
Only through this way I got Easer auto-start on boot on the emulator... Quite ridiculous in my perspective because this isn't what the Android document suggests (it only suggests the user need to run Easer at least once after installing it, which is already satisfied if you try to set it auto-start-on-boot)... (A note both for people who are interested and myself) this post on SO says the start-on-boot shouldn't be malfunctioning even on Android 8.0 (Oreo) because the this reply on SO also encounterd this issue (won't auto-start), but there is no response yet (2017-12-12). this article says there are several changes in Android 8.0 so developers should use different ways to start background services, and the article presented three examples. |
Suits Android 8.0 also Related to issue #44
I have some infomation which may be of use.I'm using redmi 8a running android 10,and encountered the boot issue too.Here is what the logcat -s ryey.easer shows: |
I'm not able to re-open #25, but this is still an issue for me on Android 8. I see the 'start on boot' permission is listed for Easer in Android, but after a boot the app does not start. I have to manually launch it and select 'start' before it is active and responding to events.
The text was updated successfully, but these errors were encountered: