[PM-40773] bug: Track accessibility service connection state from the service

[7heMech]

🎟️ Tracking

https://bitwarden.atlassian.net/browse/PM-40773

New PR under the same ticket, as requested in
#7197 (comment).

#7197 shipped in 2026.8.0 but the reported behaviour is unchanged, so #4601 and #6267 are
still reproducible on 2026.8.0 (21819).

📔 Objective

isAccessibilityServiceEnabled returns false on Android 16 even when our accessibility service
is enabled and bound, so "Use accessibility" stays off and the autofill tile shows the "turn on
accessibility" dialog.

Both branches of that check ask the platform about our own service, and Android 16 does not
answer. Logged from inside com.x8bit.bitwarden on a Pixel 6 Pro (SDK 36, targetSdk 37),
while dumpsys accessibility listed the service under both Enabled services and
Bound services:

packageName=com.x8bit.bitwarden
enabledServices.size=0    // AccessibilityManager.getEnabledAccessibilityServiceList
settingsValue=            // Settings.Secure.ENABLED_ACCESSIBILITY_SERVICES, empty string
RESULT=false

At the same moment adb shell settings get secure enabled_accessibility_services returned the
full value, and a separate test app also targeting 37 got both services back from
getEnabledAccessibilityServiceList. The restriction applies to the app asking about itself.

That is why #7197 did not help. It widened which service names the primary check accepts, but
getEnabledAccessibilityServiceList is restricted the same way Settings.Secure is, so the
check iterates an empty list no matter which names it would have matched.

So stop asking the platform. BitwardenAccessibilityService knows when it is connected, and
AccessibilityEnabledManager was already notified from its lifecycle callbacks:

• refreshAccessibilityEnabledFromSettings() becomes var isAccessibilityServiceConnected, set
  in onServiceConnected and onUnbind. onCreate no longer refreshes, since
  onServiceConnected always follows it.
• BitwardenAutofillTileService reads the manager instead of calling
  applicationContext.isAccessibilityServiceEnabled on each tap. Without this the tile keeps
  showing the dialog.
• isAccessibilityServiceEnabled is unchanged and still provides the initial value, so
  behaviour before Android 16 is the same.

Verified on the same device with a minified standardRelease build at applicationId
com.x8bit.bitwarden, since the previous fix passed an unminified local test and did nothing in
the Play build.

📸 Screenshots

[bitwarden-bot]

Thank you for your contribution! We've added this to our internal tracking system for review.
ID: PM-42463
Link: https://bitwarden.atlassian.net/browse/PM-42463

Details on our contribution process can be found here: https://contributing.bitwarden.com/contributing/pull-requests/community-pr-process.