Skip to content
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

Open
Jacques-Olivier-Farcy opened this issue Aug 24, 2022 · 5 comments
Open

Android 12 on RPI4, Launch on Boot is not working #26

Jacques-Olivier-Farcy opened this issue Aug 24, 2022 · 5 comments

Comments

@Jacques-Olivier-Farcy
Copy link

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 ?

@Jacques-Olivier-Farcy
Copy link
Author

With another app (Autostart Manager it worked adding Enabled Applications Overlay Authorisation

@iDVB
Copy link

iDVB commented Nov 26, 2022

Also having this issue on TCL 50" 4-Series Smart Google TV
I've enabled "Display over other apps" to my "target app" but I don't see "Launch on Boot" in the list of apps I can give that permission to as well.

@iDVB
Copy link

iDVB commented Nov 28, 2022

Is there a ADM command that can be run to enable this autostart? Sounds like they disabled something in 10 and 11?

@DoctorMcKay
Copy link

The same is happening for me on Chromecast with Google TV, Android version 12. I took a crack at fixing it and added android.permission.SYSTEM_ALERT_WINDOW to the manifest, which did enable me to turn on the "display over other apps" permission, but it still didn't work.

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 android.permission.SYSTEM_ALERT_WINDOW (and internet permissions, because everything has to have ads). It also targets SDK version 30, which I tried doing for Launch on Boot in case that's important, but it still doesn't seem to work. Also, targeting SDK version 31+ makes all apps disappear from the selection menu except a very few (like the Play Store and Settings).

@andysheen
Copy link

This fork by jeff2900 fixed for me running Android 12 https://github.com/jeff2900/Launch-On-Boot/releases .
I had to run adb shell appops set news.androidtv.launchonboot SYSTEM_ALERT_WINDOW allow after installing to get it to work on launch.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants