Supported Devices and Troubleshooting

Current diagnostic support

Environment	Status
Android 14 / API 34 and newer	Diagnosis plus guarded Pin and Restore
Xiaomi HyperOS	Initial investigation and Demo scenario
Other OEM devices	Conservative diagnosis; unfamiliar readable values require an additional write-risk confirmation
Android 13 and older	Device information only; repair unsupported
Work profiles and secondary users	Operations are bound to the explicitly detected foreground user

Typical symptoms

• A password manager is shown as preferred, but Google Password Manager handles passkey creation.
• Autofill works while Credential Manager does not bind the provider.
• Removing another provider makes a WebAuthn action appear unresponsive.
• credential_service_primary names a provider that is absent from credential_service.

These symptoms do not by themselves identify the faulty component. Registration, enabled state, primary state, autofill state, browser behavior, provider lock state, and OEM framework behavior are separate facts.

Low-risk checks

Update the password manager, browser, and system components; enter provider settings through the password manager's supported settings flow; toggle the selection away and back; restart the device; unlock the provider once; then retry both passkey creation and sign-in. Do not delete existing passkeys as a troubleshooting step.

When ADB is missing, the UI shows copyable installation instructions. It does not run Homebrew, Winget, Scoop, or Chocolatey. Unauthorized devices require unlocking the phone and accepting the USB debugging prompt; offline devices should be reconnected before restarting any ADB service. acp-fixer devices exposes the same states for CLI troubleshooting.

CLI usage

Extract the CLI archive for your operating system and run acp-fixer (acp-fixer.exe on Windows) from a terminal. Replace SERIAL, COMPONENT, and ID with the target reported by the tool.

acp-fixer --help
acp-fixer devices --no-interactive
acp-fixer diagnose --device SERIAL --no-interactive
acp-fixer pin --device SERIAL --provider COMPONENT --no-interactive
acp-fixer snapshots --json
acp-fixer restore --snapshot ID --device SERIAL --no-interactive
acp-fixer demo --json

The pin and restore commands above only preview the change. Writing requires an explicit --apply; read the change safety guide before applying. demo uses bundled data and does not access a device. For source-based development, use just dev-cli as described in Contributing.

English | 中文