Mishaal Rahman / Android Authority
TL;DR
- Android 17 Beta 2 now permits a stricter Superior Safety function we beforehand noticed in improvement.
- When the mode is enabled, Android blocks apps that aren’t categorized as accessibility instruments from accessing the AccessibilityService API.
- This implies apps like automation instruments, launchers, or customization apps that depend on the API will lose performance when Superior Safety is turned on.
Google has quietly rolled out a brand new safety measure tied to Superior Safety Mode in Android 17 Beta 2. If in case you have Superior Safety enabled in your machine working the most recent Android 17 beta, you’ll now face a restriction that stops sure apps from utilizing the AccessibilityService API, thereby proscribing their performance. We first found the change final month, however can now verify it’s rolling out extensively.
Don’t wish to miss the most effective from Android Authority?
Superior Safety Mode is the one-tap safety function launched with Android 16 for customers who need stronger safeguards in opposition to assaults and dangerous apps.
In the meantime, the AccessibilityService API helps folks with disabilities work together with their gadgets. Apps like display readers, switch-based enter programs, and different assistive instruments depend on it to learn display content material or carry out actions on behalf of the person.
Nevertheless, the identical capabilities can be misused. Apps with accessibility entry can view display content material, observe person interactions, and even carry out gestures routinely. Over time, many apps, together with automation instruments, customization utilities, monitoring apps, and a few launchers, have used the API to work round Android’s system limitations.
As we beforehand reported, Google has been working to tighten this loophole inside Superior Safety Mode.
What adjustments in Android 17 Beta 2
With the brand new conduct enabled, turning on Superior Safety Mode prevents apps that aren’t formally categorized as accessibility instruments from receiving accessibility permissions.
If a non-accessibility app already has the permission, the system routinely revokes it. Customers additionally gained’t be capable to grant the permission whereas the mode is energetic.
We tried this by downloading dynamicSpot, an app that emulates Dynamic Island conduct on Android telephones, on our Pixel 9a working Android 17 Beta 2. With Superior Safety Mode enabled, we have been unable to grant dynamicSpot the accessibility permissions it must show floating pop-ups. The one manner to make use of the app now could be to disable Superior Safety Mode.
In the meantime, the secure Android 16 QPR3 construct working on our Pixel 10 Professional nonetheless permits us to make use of dynamicSpot with Superior Safety Mode switched on.
Google’s help web page notes that apps that correctly declare themselves as accessibility instruments, equivalent to display readers or voice-based accessibility providers, will stay unaffected by this transformation.
Whereas the brand new conduct matches the broader mandate of Superior Safety Mode, customers who allow the function could lose compatibility with sure apps. What’s good is that no less than Google is giving customers a transparent alternative: use Superior Safety Mode and defend your self from malicious apps, or danger not utilizing it and maintain accessing the apps that require accessibility permissions.
With the change now showing in Android 17 Beta 2, there’s little doubt it’ll be part of the secure launch.
Thanks for being a part of our neighborhood. Learn our Remark Coverage earlier than posting.
