Android 17 Beta 2 starts clamping down on apps that misuse accessibility services

Google has introduced a significant enhancement to its Advanced Protection Mode with the rollout of Android 17 Beta 2. This update brings a stricter security measure that restricts certain applications from accessing the AccessibilityService API, a move aimed at bolstering user safety.

Advanced Protection Mode, initially launched in Android 16, serves as a one-tap security feature designed for users seeking heightened defenses against potential threats and harmful applications. The AccessibilityService API plays a crucial role in assisting individuals with disabilities, enabling apps like screen readers and switch-based input systems to interact with device content effectively. However, this same functionality has been exploited by various applications, including automation tools and customization utilities, to bypass Android’s inherent limitations.

What changes in Android 17 Beta 2

With the latest update, activating Advanced Protection Mode will prevent any non-accessibility apps from obtaining accessibility permissions. If such an app already possesses these permissions, the system will automatically revoke them. Furthermore, users will be unable to grant these permissions while the mode is active. For instance, testing the dynamicSpot app, which mimics Dynamic Island functionality on Android devices, revealed that it could not be granted the necessary accessibility permissions when Advanced Protection Mode was enabled. The only recourse for users wishing to utilize the app is to disable the protective mode.

In contrast, the stable Android 16 QPR3 build on a Pixel 10 Pro continues to allow the use of dynamicSpot with Advanced Protection Mode activated. Google’s support documentation clarifies that applications that correctly identify themselves as accessibility tools, such as screen readers or voice-based services, will remain unaffected by this new restriction.

While this update aligns with the overarching goals of Advanced Protection Mode, it may lead to compatibility issues for users who choose to enable the feature. Nevertheless, Google presents users with a clear choice: prioritize security by enabling Advanced Protection Mode, or forgo it to maintain access to applications requiring accessibility permissions. As this change becomes more widespread with Android 17 Beta 2, it is expected to be integrated into the stable release soon.

AppWizard
Android 17 Beta 2 starts clamping down on apps that misuse accessibility services