A Saved Bluetooth Pair Is Not a Live App Session
If Bluetooth appears paired in phone settings but Ledger Live cannot connect, test the application’s actual device interaction. The app is now Ledger Wallet. The operating system can remember an association while the app lacks permission, the hardware is locked, another session holds access, or the stored state needs repair.
Do not use a visible portfolio as proof that communication works. Account information can remain available from public records after the device session ends. Choose a harmless device-dependent action and record the exact failure.
Verify Which Connection the App Expects
Identify the host, application edition, and hardware model. Ledger’s touchscreen Bluetooth documentation explicitly distinguishes mobile pairing from the dedicated desktop app, which does not use that pairing transport.
For desktop, establish the supported USB data route instead of pairing the hardware in the computer’s Bluetooth panel. Account synchronization between desktop and mobile is another feature and should not be mistaken for a desktop radio session.
For mobile, ensure the model has Bluetooth. Nano S Plus does not, so a similarly named system entry cannot establish a valid wireless connection for it. Use the documented supported transport for the actual device.
Restore the Preconditions for App Access
Unlock the Ledger, enable its Bluetooth, and check battery and proximity. Grant the wallet app the discovery or Bluetooth permission required by the phone OS. A radio working for an accessory or another app does not prove authorization for this app.
End competing phone sessions and close wallet clients attempting access. Start the connection through the app’s current My Ledger or device flow. Follow the hardware screen for the selected action; an account-signing task and a management request can expect different states.
If the app now completes a device interaction, the saved system pairing was not the only condition involved. Record which targeted change helped so the same symptom can be understood later.
Rebuild Inconsistent State Only After Those Checks
Use Ledger’s pairing repair procedure when a stale relationship persists. Coordinate the app device record, phone association, and hardware pairing state. Repeatedly forgetting one side can leave other stale information unchanged.
Select the model-specific command. Nano X uses Reset pairings through its button-operated security settings; Stax and Flex use Remove pairing in touchscreen Bluetooth settings. Those operations are distinct from erasing the wallet.
For a new exchange, compare both codes and cancel any disagreement. A valid retained association may reconnect without a new code every time, so judge the result by the app’s intended interaction rather than demanding the original setup screen repeatedly.
Separate Later Network Errors
If hardware communication succeeds but history or a provider remains unavailable, investigate that request separately. A repaired radio session does not guarantee remote services are responding. Do not keep rebuilding pairings to repair unrelated data loading.
Preserve an advancing Ledger OS installation before host restart or pairing experiments, and never clear app data during that operation. Intentional hardware restoration, when genuinely needed, uses trusted hardware input; recovery words must not be typed into a phone or support site to authorize a session.
Paired-versus-Connected Questions
Does the Word Connected in Settings Settle It?
It describes an operating-system observation, not successful completion of every wallet operation. Read the app and hardware results together.
Should I Send a Small Payment to Test Bluetooth?
An intended management or address-verification action can test device communication without creating an unnecessary transfer. Check prior transaction status before any repeat send.
What Should I Report?
Include the system entry, app operation, hardware display, model, permission state, and versions. Keep PINs and recovery backup information out of diagnostics.