Re-enable the Permission for the Feature You Chose
If Ledger Live reports Nearby devices permission denied on Android, inspect that application’s Bluetooth-related permission before trying to pair again. Ledger Wallet is the current app name. A denied discovery permission can prevent the app from finding compatible hardware even while Bluetooth is turned on for the phone.
This is not the hardware PIN and not a wallet-ownership check. Do not provide recovery words to an app, website or support contact to unlock Android permissions.
Check Android’s Actual Permission Model
Open the phone’s app information for the verified Ledger application and inspect Permissions. On modern Android configurations the relevant request is grouped under Nearby devices. Google’s Bluetooth permission documentation explains that the required permissions depend on the OS and the app’s target version.
Grant only the access needed for your intended Bluetooth connection. Do not enable contacts, microphone, photos or permanent background location merely because another guide says to allow everything. An older Android discovery workflow can use a location-related permission, so its wording should be checked separately.
Reproduce the Discovery Step Once
- Confirm that the installed app came through the official Google Play listing.
- Enable Bluetooth and bring the supported Ledger model nearby.
- Unlock the hardware and confirm its Bluetooth setting through its own controls.
- Return to the app’s device-connection flow and start discovery.
- Compare the result with the earlier permission-denied message.
If devices now appear, permission was at least one missing condition. If discovery remains empty but no permission error returns, investigate the Ledger model, power state, another active phone session and the specific pairing stage rather than broadening Android access indefinitely.
When Nearby Devices Is Missing From Settings
A missing permission category is different from a category showing Denied. Check the Android release, app release and the action that should request access. Menus vary between manufacturers and OS versions. Google’s Pixel permission guide provides a concrete example without establishing identical labels on every phone.
Do not install a modified APK to force a permission prompt. If the official current app never requests the documented access on an otherwise supported phone, preserve the screen and versions for Ledger support.
Understand What Permission Does Not Establish
Granting discovery access does not authenticate the Ledger or complete pairing. Follow the app-led flow and compare any codes on both devices before approving. Do not accept a mismatched code, an unexpected device or a request that repeatedly appears without your action.
Permission also does not guarantee uninterrupted background Bluetooth. If the connection works in the foreground but fails after locking the phone, investigate that timing and the manufacturer’s app-management settings separately. Do not interrupt a progressing Ledger OS installation to run permission experiments.
If access changes back after a period of disuse, record the unused-app setting as part of the reproduction. A one-time permission grant is different from ongoing system permission management. That observation can explain why discovery worked last month without establishing that the app update removed Bluetooth support or that the Ledger needs resetting.
Nearby-Devices Questions
Will this enable Bluetooth on Nano S Plus?
No. Nano S Plus uses a supported wired Android connection and has no Bluetooth radio. Android permission cannot add a transport the hardware lacks.
Could an unused app lose permission?
Android can manage access for unused applications, depending on configuration. Review the current setting after a long break rather than assuming the previous permission remains effective.
What should I report if access is allowed but pairing fails?
Include the phone model, Android and app versions, Ledger model, exact permission state and last completed pairing step. Keep the hardware PIN, recovery backup and unnecessary account details out of the report.