Check the App’s Discovery List, Not Only Android Settings
If Ledger Live on a Google Pixel cannot find Nano X, begin with the scan inside the official application. The current name is Ledger Wallet. An empty in-app list, an old saved Bluetooth entry and a device appearing but failing to pair are different outcomes.
Record the Pixel model, Android release and app version. Do not assume every Pixel generation or Android update uses exactly the same settings labels. A radio test is unnecessary if the app is actually waiting for a permission decision.
Make Nano X Available for the Scan
Bring Nano X close to the phone, check that it has power, unlock it and inspect its Bluetooth setting using the hardware controls. End an ordinary connection to another phone if that session is occupying the device. Do not change these conditions during an actively progressing device OS installation.
The Nano X specifications establish its mobile Bluetooth capability. This is different from Nano S Plus, whose missing Bluetooth radio cannot be repaired through a Pixel permission change.
Inspect Pixel’s App Access
Open the verified Ledger app’s information page in Pixel Settings and review Permissions. The current request can involve Nearby devices, while older discovery flows can involve location-related access. Follow the actual supported app and Android combination.
Google’s Pixel permissions guide explains access controls. Grant the capability needed for the scan rather than enabling every denied category. If the category is absent, note that separately from a category explicitly denied.
Retest One Scan and Follow the Result
- If the expected Nano X appears, continue with the app-led pairing flow.
- If it appears but the connection times out, preserve that later-stage message.
- If codes appear, compare them on the phone and Ledger before approving.
- If the list stays empty without a permission warning, report the hardware and radio conditions you checked.
Do not approve a different nearby device or a mismatched code simply to move past the screen. A familiar saved name alone is weaker evidence than the expected physical pairing interaction.
Use Pixel Bluetooth Troubleshooting at the Right Stage
Google’s Bluetooth troubleshooting covers general phone checks. A normal restart or Bluetooth toggle can be considered during an idle session, after preserving the failure. It should not interrupt active Ledger OS progress or an unresolved signing action.
If stale pairing is specifically indicated, use Ledger’s current model-specific removal and re-pairing procedure. Do not factory-reset Nano X or clear the entire phone as a first response to an empty scan. Those steps affect much more than discovery.
Check which scan list you are observing after each change. Android’s saved-device settings and the app’s current discovery result answer different questions. If an old Nano X name remains in Settings while the app finds nothing, preserve both facts; the saved name does not establish that the hardware is currently advertising or available to this app.
Pixel and Nano X Questions
Does working Bluetooth audio prove Ledger discovery must work?
It shows that another Bluetooth use case works. Device availability, app permission and the wallet’s BLE workflow remain separate, so keep the actual scan result in the report.
Should I type the Nano X PIN into Pixel?
No. Unlock the hardware on its own controls. Android permission, local app access and the Ledger PIN are different decisions; recovery words are never part of discovery.
Can I use USB to compare?
A supported wired Android setup can help assess another transport, but it does not prove the Bluetooth path repaired itself. Keep the results separate and use only the connection supported for the exact task and hardware.