GoKawiilMishaal Rahman / Android Authority
TL;DR Android 17 Beta 2 now enables a stricter Advanced Protection feature we previously spotted in development.
When the mode is enabled, Android blocks apps that aren’t classified as accessibility tools from accessing the AccessibilityService API.
This means apps like automation tools, launchers, or customization apps that rely on the API will lose functionality when Advanced Protection is turned on.
Google has quietly rolled out a new security measure tied to Advanced Protection Mode in Android 17 Beta 2. If you have Advanced Protection enabled on your device running the latest Android 17 beta, you’ll now face a restriction that prevents certain apps from using the AccessibilityService API, thereby restricting their functionality. We first discovered the change last month, but can now confirm it’s rolling out widely.
Don’t want to miss the best from Android Authority? Set us as a favorite source in Google Discover to never miss our latest exclusive reports, expert analysis, and much more.
to never miss our latest exclusive reports, expert analysis, and much more. You can also set us as a preferred source in Google Search by clicking the button below.
Advanced Protection Mode is the one-tap security feature introduced with Android 16 for users who want stronger safeguards against attacks and harmful apps.
Meanwhile, the AccessibilityService API helps people with disabilities interact with their devices. Apps like screen readers, switch-based input systems, and other assistive tools rely on it to read screen content or perform actions on behalf of the user.
However, the same capabilities can also be misused. Apps with accessibility access can view screen content, observe user interactions, and even perform gestures automatically. Over the years, many apps, including automation tools, customization utilities, monitoring apps, and some launchers, have used the API to work around Android’s system limitations.
... continue reading