-
Notifications
You must be signed in to change notification settings - Fork 37
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
Android 12 on RPI4, Launch on Boot is not working #26
Comments
With another app (Autostart Manager it worked adding Enabled Applications Overlay Authorisation |
Also having this issue on TCL 50" 4-Series Smart Google TV |
Is there a ADM command that can be run to enable this autostart? Sounds like they disabled something in 10 and 11? |
The same is happening for me on Chromecast with Google TV, Android version 12. I took a crack at fixing it and added This alternative did work for me, so apparently running an app at boot is still possible somehow, but that app isn't open-source (and I didn't feel like reverse-engineering) so I can't see if they've done anything significantly different. I'm not an Android dev anyway, so I'm not sure I'd be able to recognize if they have. The manifest for that app doesn't seem hugely different; it seems like it just requests |
This fork by jeff2900 fixed for me running Android 12 https://github.com/jeff2900/Launch-On-Boot/releases . |
Hi,
I have installed an android 12 version of LineAgeOS on a Raspberry Pi 4.
(From https://konstakang.com/devices/rpi4/LineageOS19/)
I tried to use Launch on Boot (instaleld with F-Droid), but it is not working, nothink happened at boot.
Did i forgot something ?
The text was updated successfully, but these errors were encountered: