android head unit
- Thread starter WarRock
- Start date
Pseudocyclic
Well-known member
Search results for query: head unit
How to keep MacroDroid live after fastboot
I have installed MacroDroid on my car head unit (android 4.4.2 KitKat), if I turn off the car and turn it on after few minutes the unit make a fast boot and MacroDroid is not running unless I run it manually. Can I make the system to run the app on fast boot?
Pseudocyclic
Well-known member
It may be that the only person who can answer definitively is whoever has exactly the same head unit as you.
In general yes, MacroDroid can work on an Android car head unit and I know there are users who are doing this. Some things to bare in mind.
1) These typically don't have Google services (but maybe some do) so any functionality relying on Google services will not work (Webhook, geofence etc.)
2) These types of devices can often have non-complete or non-standard Android implementations so might be missing some functionality or have weird behaviour in terms of apps running in the background.
3) Related to the above there can often be issues with MacroDroid not being allowed to auto start on device boot. (This is not something I can solve with MacroDroid as it already does everything it can to autostart if the platform allows it).
1) These typically don't have Google services (but maybe some do) so any functionality relying on Google services will not work (Webhook, geofence etc.)
2) These types of devices can often have non-complete or non-standard Android implementations so might be missing some functionality or have weird behaviour in terms of apps running in the background.
3) Related to the above there can often be issues with MacroDroid not being allowed to auto start on device boot. (This is not something I can solve with MacroDroid as it already does everything it can to autostart if the platform allows it).
Unfortunately Android on head unit is a truncated version, e.g.
- it doesn't have 'Accessibility API', so lot of trigglers won't works
- basic interface doesn't accept shorcut, widget...
- and the most problem is it doesn't memorise any app when power off.
I don't understand how some app can do ?
A trick for 'car launcher' apk is to set 'auto launch when external power is on' (which means 'always' for head unit)
Why cannot Macrodroid do same ?
Anyway, the only way to start Macrodroid on boot, as we are talking about car and as all of us use alternative car launcher:
- paid 'car launcher' using tasker to launch macrodroid (greater burden but works)
- paid 'Agama launcher' which can start any app
- I am said 'Nova launcher' also can do, but haven't tried
- it doesn't have 'Accessibility API', so lot of trigglers won't works
- basic interface doesn't accept shorcut, widget...
- and the most problem is it doesn't memorise any app when power off.
I don't understand how some app can do ?
A trick for 'car launcher' apk is to set 'auto launch when external power is on' (which means 'always' for head unit)
Why cannot Macrodroid do same ?
Anyway, the only way to start Macrodroid on boot, as we are talking about car and as all of us use alternative car launcher:
- paid 'car launcher' using tasker to launch macrodroid (greater burden but works)
- paid 'Agama launcher' which can start any app
- I am said 'Nova launcher' also can do, but haven't tried
CurioTink9938
New member
I am new to the headunit scene. I'm using both MacroDroid and Tasker on my headunit. I like the work flow of MacroDroid better, but it seems more limited on the headunit. For example, Tasker will boot with the headunit and will run tasks upon boot. This is super handy. For some reason, the headunit Android resets the MacroDroid Accessibility Permissions with every boot. But, this doesn't happen with Tasker. I'm not sure why these differences exist, but they do. I wish there was a way to get Macrodroid to boot with the headunit and maintain its permissions.
I also run Agama Launcher. I tried using it to launch Macrodroid after start up, but it launches Macrodroid into the foreground. This is rather inconvenient and adds to the system boot time.
I also run Agama Launcher. I tried using it to launch Macrodroid after start up, but it launches Macrodroid into the foreground. This is rather inconvenient and adds to the system boot time.
There is no obvious reason why the accessibility service should reset permission and Tasker doesn't. The only reason I can think of is that MacroDroid takes some additional permission that Tasker does not and your device doesn't like it for some reason. If this is the only issue you may be able to use the option in settings to auto restart accessibility services (you will need to run the ADB hack to do this).