Locate the Broken Stage on Android
When Ledger Live Android is not connecting, use the earliest failing stage to choose the repair. Ledger Wallet is the renamed companion app. A phone that never discovers the Ledger, a rejected pairing, and an account that refuses to refresh are three different situations even if each interrupts the same task.
Write down your Android version, Ledger model, and exact message. This independent decision guide starts with hardware visibility and ends with account data, so you can stop once the relevant fault is identified.
Branch One: The Hardware Never Appears
Confirm that the connection method exists on your model. Nano S Plus requires compatible Android USB OTG; it cannot appear in a Bluetooth scan. Nano X, Stax, and Flex have Bluetooth support, subject to current phone and software requirements.
For Bluetooth, inspect the app’s discovery permission and the hardware’s unlocked state. Older Android systems can require location services for scanning. Use Ledger’s Bluetooth diagnostic instructions for the current model-specific details.
For a wired device, look for the Android USB-access request. Substitute a proven data cable while leaving the phone unchanged. If an OTG toggle exists on your phone, check whether it timed out. A powered Ledger display does not establish successful USB communication.
Branch Two: The Device Appears but Connection Fails
End other phone or application sessions that might hold the hardware connection. Restart the phone and Ledger, then make one fresh attempt inside the app. Compare any displayed codes carefully rather than approving successive requests without examining them.
If the same stale association keeps failing, follow the documented procedure to forget or reset pairings. Do not select the hardware’s wallet-reset command. The goal is to rebuild the communication relationship, not erase the keys or initialize new accounts.
For USB, unlock both devices and review which app requests access. Ledger’s Nano S Plus Android guide covers the OTG workflow. Avoid random developer settings or driver-download apps, which do not establish a supported phone connection.
Branch Three: Hardware Works but the Account Does Not
If My Ledger can communicate with the device, move to network and account diagnostics. Check whether the failure affects all assets or only one blockchain. A service incident can prevent account refresh while the Bluetooth or USB session remains healthy.
Confirm you selected the intended account network and that any required blockchain app is available on the hardware. A missing account, a pending transaction, and a failed genuine check should each be recorded with their own message instead of combined into one connection complaint.
Keep Changes Reversible
Obtain app updates through the official Google Play route linked by Ledger. Test on another supported system when practical, changing one variable at a time. Describe whether the problem follows the phone, cable, or hardware rather than reporting only that everything failed.
Keep recovery words away from the Android keyboard. Neither connection repair nor official support needs a screenshot of the backup. If a site requests it to reconnect the device, stop using that site.
Diagnostic Questions
Does the Phone Need to Stay Unlocked During Testing?
Keep both devices accessible while following prompts so you can see permission requests and hardware confirmations. Do not overlook an unanswered dialog behind the app.
When Is Reinstallation Useful?
Consider it only after identifying an application-level problem and understanding local-data consequences. It cannot create a missing Bluetooth radio or repair a faulty USB cable.