AOD with enhanced security

[W-e-e-Z-e-l]

I'm not sure if this is related to GlucoDataHandler, from my understanding this issue is sourced at Googles side...but let me explain, maybe there is something what GDH can do!?

Im on a Pixel 10 Pro with newest Android 17 and I enabled the enhanced security feature of Google. This morning there was a message from Google, that the enhanced security feature has changed for Apps with "accessibility features" rights.
I noticed immediately that the AOD display of GDH isn't working anymore and GDH detects correctly that its missing the accessibility feature right.
I cant re-grant these rights to GDH without disabling the enhanced security entirely. Obviously this is something i dont want...
It seems there should be a way to allow an App to gain these accessibility rights even with the enhanced security feature enabled, but i wasn't able to activate this since the exclusion settings don't show up for me.

I already was in contact with Google support, but they were not able to help and they just told me that this doesn't work anymore. Case closed. :(

Has someone else the same issues or am I the only one? If its something general, can GDH do something to bring back the AOD info display on devices with enhanced security enabled?

Best regards, Daniel

[pachi81]

Hi Daniel,

I have not heard about such a problem, yet.
But in the last weeks, I had some troubles with Google, because they rejected my next version as the policy for the accessibility feature was not fulfilled. Maybe the problem is related to this rejection...
This morning, I got the ok from Google and the new version is available for beta users.
Can you try to assign yourself to the beta program of GDH. If it is not possible, please send me a mail to GlucoDataHandler@michel-inside.de, so I can provide you a link to the beta program.

Michael

[W-e-e-Z-e-l]

Ok, im in the beta program from GDH now. Thankfully Michael provided me a link to this 👍
Unfortunately, this hasn't changed anything. The issue is the same...

I did some research on this, and it seems Google has tightened the rules for the accessibility feature rights if you're using the enhanced security mode. What i've found, only Apps with "isAccessibilityTool="true"" flag set in the manifest can get these rights in enhanced security mode.
I dont think GDH is using this flag and i can understand that you dont want to implement it since this comes with additional restrictions and expectations from Google you're probably not happy with...

[pachi81]

Hi Daniel,

"isAccessibilityTool="true"" is not a solution as this can only be set for full Accessibility-Apps and GDH is not such an app. So Google will never approve this...

Can you try this solution:

Even with the Enhanced Security Mode active, Android usually allows users to manually whitelist a specific app without turning off the entire security feature. However, Google hides this option deep within the system menus.

Please try the following steps to manually bypass the restriction for GlucoDataHandler:

• Step 1: Open your device Settings.
• Step 2: Navigate to Apps -> All apps -> GlucoDataHandler.
• Step 3: Look at the top right corner of the screen and tap the three dots menu icon (the overflow menu).
• Step 4: Select "Allow restricted settings".
• Step 5: Confirm the action using your device PIN, pattern, or fingerprint.

Note: Once you have granted this permission on the app info page, return to the Android Accessibility menu. The toggle to enable the service for GlucoDataHandler should no longer be grayed out, allowing you to re-grant the required rights.

[W-e-e-Z-e-l]

Yeah, that is the way you could have a exclusion configured before Google tightened the rules today. This procedure doesn't work anymore...
I think it all comes to a trade off between feature vs. security, at least for me and I will not disable enhanced security. But I'm using the lockscreen wallpaper feature from GDH now...its not the same, but it does the trick as close as possible.

Thank you for the support anyway!

[pachi81]

Thank you very much for reporting! I will check in emulator, but sometime the behavior is different.
Can you post a link to the new restriction, so I can inform/warn other users.

[W-e-e-Z-e-l]

I dont have a single source where everything is explained but if you have a look here: https://blog.google/security/whats-new-in-android-security-privacy-2026/
there is mentioned that Google will remove the accessibility right for all Apps if its not a real accessibility App in Android 17. And this article is already a bit older, but is talking about this change in the Android 17 beta: https://thehackernews.com/2026/03/android-17-blocks-non-accessibility.html

So, from my understanding this should only happen on Android 17 devices and it's probably rolled out in waves. It just hits me today...

[pachi81]

Do you know, how to disable the AAPM?
I found this solution from AI, is it correct!?

How you can solve it right now:

To get the AOD functionality back on your Pixel 10, you have to temporarily disable the device-level protection:

1. Go to Android Settings -> Security & Privacy.
2. Scroll down to Advanced Protection (under "Other settings" or via Google settings).
3. Disable Device Protection.
   (Note: A device reboot might be required afterwards).

[W-e-e-Z-e-l]

Yes, that way you can disable the AAPM. I did it already this morning for testing and after this the AOD from GDH works fine again.