Tasker won't restart after ultra-fast boot on Android car head unit
Zoltán Bíró
The Lenovo D2 Android head unit has the nice habit of killing a lot of things when it wakes up, such as the accessibility services, and it doesn’t let Tasker start either.
For clarity: as I saw it, there are 3 levels of the head unit’s PM:
If you only take off the ignition for a few minutes, you get everything as you found it.
If it stays without ignition for longer, then there is an ultra-fast boot, the system is operational in 2-3 seconds, but it resets the interface.
If the car stands for a few days, then it boots up from scratch.
Well, I have a problem with the 2nd case (as in the 3rd case it initializes everything anyway, so Tasker is restarted as well). That, is after the ultra-fast boot not only the Autoinput ones, but the trivial Tasker profiles are not triggered either. You have to go into Accessibility, or start Tasker manually and fiddle with the profiles (e.g. disable and re-enable them).
One would suspect the battery optimizing settings, but there are exactly 0 of them: the word battery doesn't even appear anywhere in the settings (we speak about car head unit).
So far it was that Tasker was the solution for everything, but if that doesn’t work either, then things seem hopeless.
I can hope for one of three ways.
You may give me an idea of what else I can try after this to get Tasker started,
A solution that can check the accessibility settings every few seconds and restore them if needed.
Any watchdog-like thing that starts a certain app every few seconds, whatever is wrong with the system, and I’ll take it from there, e.g. with an app exported from Tasker.
Can you help me?