Google is testing a change in Android Advanced Protection Mode in Android 17 Beta 2 that prevents non-accessibility apps from using the AccessibilityService API, automatically revoking existing permissions while AAPM is active. The update, alongside a new contacts picker and the AdvancedProtectionManager API, tightens app privileges and gives developers a way to detect and adapt to the hardened security state. #AndroidAdvancedProtectionMode #AccessibilityService
Keypoints
- Android 17 Beta 2 will block non-accessibility apps from using the AccessibilityService API when AAPM is enabled.
- Only tools flagged with isAccessibilityTool=”true”—like screen readers and Braille programs—are exempt from the restriction.
- AAPM’s core protections also include blocking app installs from unknown sources, restricting USB data signaling, and requiring Google Play Protect scans.
- The AdvancedProtectionManager API lets apps detect AAPM status and automatically adopt a hardened posture or limit high-risk features.
- A new contacts picker allows apps to request only specific contact fields or let users select particular contacts for more granular data access.
Read More: https://thehackernews.com/2026/03/android-17-blocks-non-accessibility.html