Accessibility permissions do not survive ignition off/on.

User_mdhjrybs

I have installed Macrodroid and Button Mapper apps on my Dudu7 headunit. Both these need accessibility permissions granted which I have done. They both work fine. However when I turn the ignition off and then back on the permissions are removed and I have to grant them over again. Is there anything I can do to make the permissions permanent?

DUDU-Meng

User_mdhjrybs
Secondary permissions are supposed to need to be reauthorized after each boot.
You can test it by installing the app to any Android phone.

WoOOOhOOO

User_mdhjrybs Button Mapper apps

I'm curious what you're using Button Mapper for. Do you have the 12.9" one with the physical buttons (I do)?

User_mdhjrybs

But is ignition off/on a reboot? The unit does not restart from scratch as in a full power down.

DUDU-Meng

User_mdhjrybs If you are talking about starting the engine with a black screen for 1 second which will cause this problem, then you can change the acc delay to 3 seconds to achieve the purpose of starting the engine without a black screen.

User_mdhjrybs

I'm just testing the unit on the bench at the moment so that I can do all the setting up possible before I install it in the car.

I have a regulated 12v power supply giving 12v to the G2 cable, Ground to G1 and then a manually switched 12v to G3. I have 4 speakers connected to G9 to G16

When I switch off power to the G3 (my ignition on/off equivalent) and then back on that is when the apps loose their permissions, but the unit is very quick to restart so isn't doing a cold start like it does when you first connect power or reboot it.

DUDU-Meng

User_mdhjrybs
The G3 you mentioned should be the ACC control line for sleep/wake or shutdown/startup.
It has the same accessibility permissions and relationships as shutdown/startup.
Android devices have several types of accessibility permissions, which can be controlled by the app itself to enable them once or permanently.
If the app developer cannot implement this, they must root the device and enable the accessibility switch automatically each time the device starts up.

User_mdhjrybs

Yes, I am using the G3 as ACC and the unit correctly goes into sleep mode when that is disconnected. I am just surprised that sleep mode seems to loose the accessibility permissions. I would expect a full restart/reboot to loose them, but not sleep.

I actually discovered while testing that if I remove power completely from the DUDU after turning off the ACC line, then when it restarts it does retain the accessibility permissions, but if I let it go into sleep mode it doesn't. This seems like the wrong way round.

This is happening with 3 different apps - Button Mapper, Macrodroid and Map Speed Limits. This does not happen with my current Android headunit, with the same apps.

DUDU-Meng

User_mdhjrybs
It has always been designed this way. If you want to hibernate and maintain an unobstructed live state, please submit a new request in the feature request section, and we will consider whether it is feasible to implement it.

User_mdhjrybs

OK, will do. Thanks very much for you quick responses and information.

User_mdhjrybs

WoOOOhOOO

I'm using a modified BMW iDrive controller connected to an arduino pro micro which emulates a USB keyboard. Button mapper then either directly, or via a Macrodroid macro, converts the button presses to the appropriate command(s).in the headunit. Eg the Media button on the iDrive starts Poweramp and after 2 seconds returns to the home screen.

I much prefer physical buttons to touchscreen for the commands I use a lot when driving.

DUDU-Meng

User_mdhjrybs
Please upload the APK file you are using and take a look

User_mdhjrybs

The one that I really need the most now is the "Map Speed Limit" app. I installed directly from Google Play so don't have an APK. This is a link to the app.

https://play.google.com/store/apps/details?id=com.amphebia.mapsspeedlimits&pcampaignid=web_share

It needs accessibility options as it provides an overlay on top of other apps showing the current speed limit of the road you are on, even if you aren't running navigation. I can thoroughly recommend it, but needing to set it's permissions on every drive is a bit tedious. Any help of this would be gratefully received.

With regard to Button Mapper and Macrodroid, again I installed them directly from Google Play, so don't have APKs. I am managing to find a workaround for those at the moment. I am now using your excellent SWC mapping function that allows access to 3rd party apps, which my previous android headunit didn't.

User_mdhjrybs

Just as an update on this, I have been doing some further testing.

I have 3 apps that have accessibility permissions granted (Button Mapper, Macrodroid & Map Speed Limit).

With all apps accessibility permission set to "on"

Then performing an ignition off then back on 2 out of the 3 loose the permissions but Button Mapper retains it

As far as I know I have the app settings the same for all three and have turned off the "Pause app activity if unused" toggle in the app settings for all of them.

I don't understand:

A) Why any of them loose permissions when it isn't a reboot just a sleep

B) Why Button Mapper retains it's permission but the other 2 don't

Any help on this gratefully received. Thanks

DUDU-Meng

User_mdhjrybs
You can test the accessibility permissions of these three apps on your phone.

User_mdhjrybs

I have been running all 3 apps without a problem on my Junsun Headunit (which claims to be Android 13). The accessibility permissions on all apps survive both sleep and complete shutdown.

I have been testing them also on my Samsung home tablet (which is Android 10) again without ever loosing the permissions even on a complete restart.

As a test, I have just tried the Map Speed Limit app on my wife's Android 14 Samsung tablet (in case it was just a problem on newer Androids) and that doesn't loose it's accessibility permission on restart either.

I absolutely love the DUDU7 headunit, and the OS - it is way better than my Junsun in many ways, but this issue is a real problem for me.

User_mdhjrybs

Further testing:

As mentioned above, until I can solve this issue, I am running the unit on a test bench. I have a regulated 12v power supply giving 12v to the G2 cable, Ground to G1 and then a manually switched 12v to G3 to simulate ignition on/off.

Simulating a normal ignition off and on again some time later is when it looses the permissions.

But if I switch off G3 and then also G2 (so the unit has no power at all). When I then switch on G2 followed by G3 this causes a cold start but the permissions remain. Also if I perform a restart from the pull down settings screen, the permissions also remain.

This is 100% repeatable (so hopefully easy for you to test). It is the act of going into sleep or shutdown mode (doesn't matter which) that removes the permissions, whereas a full restart does not. This is the exact opposite of what I would expect to happen and all my other Android devices retain the permissions regardless of reboot/sleep/shutdown.

DUDU-Meng

User_mdhjrybs
Settings - Vehicle - Startup Settings - Sleep Mode Settings.
Check this app here. Does the accessibility feature remain active?
If it still doesn't work, you can first change the sleep mode settings after the engine is turned off to shutdown. This should ensure that the accessibility feature remains active.

User_mdhjrybs

DUDU-Meng

Thanks for the sugestions but I have already tried both of them

Adding the apps to the "keep alive in sleep" makes no difference nor does changing between sleep and shutdown for ignition off.

It seems to me that there is a fault in the ignition off actions of the OS that looses the permissions (regardless of if it is set to sleep or shutdown)

There must be something wrong when just shutting off all power to the unit retains permissions when restarted, but just turning the ignition off, as it is designed to do, looses them.