Expert VerifiedLedger Live iPhone Bluetooth Pairing: Bond, Permission and Radio Checks
- Last Updated: 10 Oct 2026
-
Fact Checked
Our team recently fact checked this article for accuracy. However, things do change, so please do your own research.
Contributors:
Ledger Live iPhone Bluetooth Pairing: Bond, Permission and Radio Checks
Ledger Live iPhone Bluetooth Pairing breaks at one of four points: the system radio permission for the app, a bond the signer still holds for another handset, a firmware build below the minimum the app expects, or a battery that cannot sustain the link. Each failure looks different on screen, which is why replacing hardware before separating them wastes time and money. The comparison below sets the radio route against cable and air-gapped alternatives, and the five checks at the end prove the link works before any real transaction is attempted.
What actually happens when the app bonds with a hardware signer?
The app requests a low-energy radio slot from the operating system, scans for a powered signer, and the signer displays a short code that the owner confirms on its screen. Both sides then store a bond, so later sessions reconnect without a code as long as neither side forgets the other.
The permission layer the operating system controls
The first scan triggers a system prompt, and the answer is remembered until someone changes it. Denying it produces no error inside the app; the device list simply stays empty, which is why a switched-off permission gets mistaken for broken hardware. That permission lives in the system settings for the app, not inside the app's own menu, and reinstalling the app resets the prompt but leaves the signer-side record untouched. The exact wording of that switch differs by system generation and is published on the manufacturer's documentation.
The bond stored on both sides
Every successful handshake writes a record on the signer and on the handset, and the signer keeps only a small number of them. Once that list is full, the oldest entry has to be removed before a new handset can attach, and the signer's own connection menu is the only place where removal happens. Clearing app data or deleting the app does not touch the signer-side record, so a clean installation can still be refused by a device that believes it already belongs to someone else.
What the signer screen has to be doing
A signer that is locked, asleep, or parked on its dashboard will not answer a scan. The radio advertises while the device is released with its PIN, and the asset application for the account in question has to be open before the handset can read addresses or prepare anything. If the screen shows a padlock or a menu the owner did not open deliberately, the scan times out long before a confirmation code appears, and the app reports a device it can see but cannot reach.
Where the cable-free route applies, and which signers support it
It applies to owners of signers that ship with a low-energy radio, on handsets whose system version the app still supports, and in situations where carrying a cable is impractical. Signers without that radio, and any task that writes firmware, remain wired-only.
Hardware models with and without the radio
Not every signer in the range carries a radio; the entry-level units connect over a cable and nothing else. That difference decides a purchase, because a cable-only device cannot be made wireless by any setting inside the app. The current compatibility list, including which models work with which mobile builds, is published on the manufacturer's support pages and changes as new hardware ships, so it is worth reading before concluding that a unit is faulty.
Asset coverage inside the mobile app
Transport and asset support are separate questions. A signer that links over the air can still sign only for networks whose applications are installed on it, and the mobile app offers an account only when the matching application is present. Installing those applications is itself a wired operation on most models, so the first setup almost always involves a cable although everyday use does not. An empty account list therefore points at missing applications, not at a weak radio.
Mobile-first workflows
Owners who never open a desktop build lean on the handset for balances, address verification and transaction approval. That routine holds while the bond stays intact and the signer has charge; it breaks the moment the handset is replaced, because the new phone has to be added to the signer's own list. Keeping the original cable in a drawer shortens that recovery from an afternoon to a few minutes, and it is also the only path back if the signer's list is already full.
The cable-free link next to wired and air-gapped alternatives
Three routes move a signed transaction from a hardware signer to a phone or computer: a low-energy radio link, a USB cable, and an air-gapped flow where a screen and camera carry the data. Each one trades convenience against a different constraint.
The comparison below weighs those routes plus two adjacent setups that owners often confuse with them, judged on the situation each fits, the limit that bites first, and the check that shows the path is genuine rather than spoofed.
| Route | Best suited to | Main constraint | Verification step |
|---|---|---|---|
| Low-energy radio link managed by the mobile app | Everyday signing from a handset with no cable | One bonded handset at a time; firmware work needs a cable | Short code shown on the signer screen at each new bond |
| USB cable to a handset or computer | First setup, firmware writes and recovery | Requires an adapter matching the handset port | Signer screen reports the connected state while attached |
| Air-gapped flow using screen and camera | Owners who accept neither a radio nor a cable path | Slower per transaction and dependent on optics | Address and amount confirmed on the signer screen before approval |
| Browser extension plus cable on a desktop | Managing many accounts from a workstation | Needs a supported browser and a computer | Extension displays the same address as the signer screen |
| Watch-only account inside a mobile wallet | Checking balances while the signer is elsewhere | Cannot approve anything without the hardware present | Imported address matched against the signer screen once |
The radio route fits daily use and fails the moment firmware has to be written; the cable fits setup, recovery and desktop work but needs the right adapter in the bag. The air-gapped flow suits owners who reject both a radio and a cable, at the cost of speed on every transfer. A browser extension is a convenience layer over the cable, never a replacement for the signer screen, and a watch-only account is read-only by design. Exceptions run in one direction: a cable solves almost every radio problem, while no radio setting can substitute for a cable during a firmware write.
Why firmware work still demands a cable
Writing firmware rewrites the code that runs the radio, so the transport carrying that write cannot be the radio itself. The mobile app therefore hands the task to a wired session, and a handset without the correct adapter cannot complete it at all. Owners who attempt an over-the-air update on an unsupported model see the progress stall rather than an explicit refusal, which is the single most misread symptom in this area. The supported combination of model, cable and app build is published on the official source and shifts with each release.
What the one-handset limit costs in practice
The signer stores a small number of bonds and answers one handset at a time, which keeps the attack surface narrow but creates a recovery chore whenever a phone is lost, wiped or upgraded. The old entry has to be deleted from the signer's own connection menu, and that deletion requires physical access to the device and its PIN. Until it happens, the new handset sees the signer in a scan and never receives a confirmation code, a pattern that resembles a hardware fault closely enough to fool most owners once.
Why does the handset keep showing a signer that will not connect?
The handset and the signer usually disagree about a bond that already exists, or the scan is answered by a device that is locked, flat, or running a build below the minimum the app expects. Deleting the old record is the single most common resolution.
Stale bonds that survive a reinstall
A signer remembers the last handset even after that handset is wiped, sold or replaced, and it refuses a new one until the old entry is removed from its own connection menu. Reinstalling the app does not touch that record, and neither does restarting the phone or updating the system. The symptom is distinctive: the signer appears in the scan, no code ever appears on its screen, and the attempt ends in a timeout. Owners who keep a spare handset bonded for convenience meet this failure most often.
Radio congestion and physical obstructions
The low-energy band is shared with Wi-Fi, wireless peripherals and, on some desks, USB 3.0 ports that leak interference across the same frequencies. A handset resting on a metal table, inside a bag, or more than a few metres from the signer drops the link mid-session, often after the bond has already been confirmed. Moving both devices onto an open surface and removing the case restores the connection without changing a single setting, which makes position the first variable worth testing before anything is reset.
Charge level and the signer's power budget
The radio draws more current than the idle screen does, so a signer near the end of its charge will advertise, accept a bond, and then drop the link during the first signing request. Charging it for a few minutes before a scan removes that failure mode entirely and costs nothing. A signer that misbehaves only when unplugged, or only after an hour of use, is describing a battery condition rather than a software one, and the fix belongs in the hardware column rather than the settings menu.
What confirms that the signer and the handset can exchange data over the air?
A confirmed bond plus one signed and verified transaction proves the link end to end. Have the signer charged and its PIN ready, the matching asset application installed, and the mobile app updated to a build that supports the model.
Step 1: Grant the wireless permission to the app
Open the system settings for the app and switch the wireless permission on. A denied permission leaves the device list empty with no error shown inside the app, so this check belongs before any hardware troubleshooting.
Step 2: Clear the stored handset list on the signer
Delete every stored handset from the signer's connection menu. The signer holds only a few bonds and refuses new ones once the list is full, which looks identical to a radio that has stopped working.
Step 3: Release the signer and open the right asset app
Enter the PIN on the signer and open the asset application for the account you intend to use. A locked or idle signer does not advertise, so the scan times out before any confirmation code reaches the screen.
Step 4: Run a scan from close range
Start a fresh scan from the app's device list with the signer within arm's reach. Distance, metal surfaces and busy wireless bands weaken the signal enough to break the handshake halfway through.
Step 5: Approve the code and confirm with a balance refresh
Compare the code on the signer screen with the one shown in the app, approve it, then refresh an account balance to confirm the link. A balance that reloads without a timeout shows the bond is stored on both sides and ready for signing.
What shifts between app releases, handset generations and signer models
Menu labels, permission wording, supported model lists and firmware minimums move with each release, while the order of permission, bond, PIN entry and confirmation stays the same across the whole range. Anything that depends on a version number is published on the official source.
Menu labels move between app versions
The path to the device list has been renamed more than once, and instructions written for an older build send owners hunting for a screen that no longer exists. When a walkthrough and the app disagree, the app is authoritative and the walkthrough is dated. Screenshots in third-party articles age fastest of all, because each one captures a single build from a single region, and the underlying function may have moved two levels deeper without any announcement.
Handset generations change the permission path
The switch granting radio access sits in the same settings area on every system generation but under a different heading, and older handsets stop receiving updates long before the app withdraws support for them. Checking the app's stated minimum system version takes less time than guessing from the layout of the settings screen. A handset below that minimum can still install an older app build, which then behaves in ways no current walkthrough describes.
Firmware minimums decide whether the radio answers at all
A signer running an older firmware build can advertise in a format the current app no longer recognises, and the remedy is a wired update rather than any change on the phone. Because the required build number rises over time, it is published alongside the release notes on the official source rather than fixed in any article. Owners who update on a regular schedule rarely meet this failure, while devices left in drawers for a year meet it almost immediately.
Check iPhone Bluetooth Settings for Ledger Nano X Visibility begins with three switches that decide whether the Nano X ever appears in the app's scan list: the radio state in Settings, the per-app wireless grant, and the wallet's own advertising window. Miss one and the list stays empty with no error text, which is why repeated searches waste time instead of solving anything.
Check iPhone Bluetooth Settings for Ledger Nano X Visibility
Visibility rests on three independent states: the short-range radio switched on in Settings, the companion app holding a wireless permission entry, and the Nano X itself advertising while unlocked and free of a cable. Any single failure empties the scan list, and running the search again cannot compensate for a disabled switch or a missing grant.
The radio switch, Airplane Mode, and cable interference
Switching the radio off in Control Centre or leaving Airplane Mode engaged stops every short-range scan on the handset, so no app can see the wallet. Lower Power states do not normally cut the radio, but they stretch the gap between scan windows, which is why a device sometimes appears on the second or third attempt instead of the first. A charging cable plugged into the Nano X also changes the discovery path, so unplug it before searching.
Where the app's permission entry lives
Apple introduced a per-app wireless permission prompt with iOS 13, and the row sits under Settings, Privacy and Security. The app appears in that list only after it has requested access at least once, so a fresh installation that was never opened leaves no row to toggle. A row switched off and a row that never existed look identical from the scan screen: the system sees the accessory, the app does not.
When a Visibility Audit Belongs Before Any Reconnection Attempt
Run the audit after a handset change, an operating system upgrade, an app reinstall or a phone reset, and whenever the wallet shows in the system's own settings page but not in the app's search results. It also applies when the accessory was previously linked to a different handset that still holds the record.
Handset migration and restored backups
A restored backup returns accounts to the new phone but never returns the wireless bond, because link keys live in the handset's secure hardware rather than in the backup file. The previous phone keeps that live record until the entry is removed inside its own app or settings. While the old record stands, the accessory behaves as occupied and stays invisible to the new handset's scans, so migration should always include clearing the earlier link.
After an operating system upgrade or app reinstall
Major releases occasionally reset privacy grants, so an app that worked yesterday can return with its wireless toggle off. Deleting and reinstalling the app removes its permission row entirely and the prompt reappears on the next launch; declining it there leaves the wallet undiscoverable with no warning. Checking the toggle after every upgrade takes seconds and removes the most common false alarm.
Wireless Link Versus Cable and Other Discovery Routes
Three routes reach the same wallet: a wireless link from this handset's companion app, a cable link to the desktop application, and a wireless link from a second handset. They differ in what they require, what they cannot do, and how quickly a failure can be confirmed.
The table compares those routes by the situation each suits, the prerequisite each imposes, and the fastest check that proves the route works.
| Route | Suits | Prerequisite | Fast check |
|---|---|---|---|
| Wireless link from this handset's companion app | Daily use away from a computer | Radio on, app permission granted | Name appears in the in-app scan list |
| Cable link to the desktop application | First setup and firmware work | Compatible cable and desktop build, published on the official source | Application lists the device after connection |
| Wireless link from an Android handset | Testing whether the wallet still advertises | Wallet freed from the earlier handset | Name shows on the second handset's scan |
| Second attempt from the same handset | Ruling out slow scan timing | Scan started while the wallet is awake | List refreshed and still empty or populated |
| Wallet-side link record removal | No handset can see the device | Reset path published on the official source | Name returns to scan lists afterwards |
The wireless route fits anyone who signs transactions on the move, but it fails whenever the accessory is already bonded elsewhere; the cable route fits setup and recovery work and ignores the radio question completely, though it ties you to a computer. The Android test fits the moment you suspect the wallet rather than the handset. Removing the wallet-side record is the last resort, because it forces a fresh link on every phone you own.
Why the cable route sidesteps the radio question entirely
A wired connection negotiates over the port instead of the air, so neither the handset's radio state nor its permission rows matter. That makes it the cleanest way to separate a wallet fault from a handset fault: if the desktop application finds the device over a cable, the accessory and its firmware are working. The trade-off is that a cable cannot confirm wireless discovery, so a successful wired test still leaves the original question open.
Stale bonds that outlive an app reinstall
Removing the app clears the handset side of the link but can leave a peer record on the accessory, and that record keeps the wallet answering only its known counterpart. The symptom is consistent: one phone lists the device, every other phone does not, and reinstalling changes nothing. Clearing the record on the wallet side, through the path documented on the manufacturer's official support pages, returns the device to an unclaimed state.
Which Mistakes Keep the Accessory Out of the Scan List?
Three mistakes dominate: trusting the system's own wireless list as proof that the app can see the wallet, leaving a live bond on an older handset, and closing the app mid-scan. Each produces an empty list without error text, which is why people repeat the same failed search instead of checking the underlying state.
Reading the system list as proof of availability
The handset's settings page shows previously connected accessories from stored records, not from live broadcasts, so an entry there proves only that a link existed once. The companion app scans for advertisements in the moment and shows nothing while the wallet is asleep, cabled or bonded elsewhere. Treating the settings page as confirmation sends people down the wrong path for hours, chasing a device that was never broadcasting.
A wallet still occupied by an earlier handset
A Nano X links to one handset at a time, and while that record stands it may not answer a second handset's scan. The remedy is to open the app on the first phone, use its device menu to remove the wallet, then confirm the entry disappears from the system list as well. Only after that does the accessory advertise to a new phone.
What Sequence Confirms the Device Is Discoverable Before Linking?
Work through five checks in order: radio state, app grant, device awake state, cable removal, and a clean scan, each taking under a minute. Have the handset unlocked, the companion app installed and opened once, the wallet charged, and any earlier link removed from a second phone before starting.
Step 1: Confirm the radio is live
Open Settings and confirm the short-range radio is switched on and Airplane Mode is off. A radio disabled at system level stops every scan, so any later check would answer a question that never mattered.
Step 2: Grant the app its permission
Open Settings, then Privacy and Security, and switch on the permission row that names the companion app. Without that grant the app cannot register any advertisement, and the row exists only after a first launch.
Step 3: Wake the wallet
Unlock the Nano X and leave it on its dashboard until the search finishes. The accessory advertises while awake, and locking the screen stops the broadcast within seconds, which is the usual reason a scan returns nothing.
Step 4: Clear competing links
Unplug any cable from the wallet and remove the old link on the handset that was used before. A cable changes the connection mode, and a retained bond marks the device as already claimed by another phone.
Step 5: Verify the name before tapping
Start a fresh scan in the app and confirm that the device name appears before you tap it. Seeing the name proves discovery works end to end, while tapping a half-loaded entry can abort the handshake and send you back to step one.
What Shifts Between Releases and What Stays Fixed
Menu labels, prompt wording and the exact path to the permission list move between operating system releases, while the three-condition rule itself does not. Apple has relocated that list more than once, and the vendor's minimum app and firmware builds change with each release, so exact paths and version numbers belong on the official source rather than in a static guide.
Permission menus that move between releases
Each major operating system revision tends to rename or regroup privacy entries, so a written path can be one level off within a year. The stable part is the shape of the problem: one radio switch, one per-app grant, one advertising device. Hunting for the toggle by that description, rather than by a memorised path, keeps the check usable across updates.
Version floors and where they are published
Compatibility floors for the app and the wallet firmware are set by the vendor and republished with each release, so any figure quoted in a third-party article ages quickly. Confirm the current requirement on the vendor's own release notes before concluding that hardware is at fault. A device below the floor may connect to one tool and not another, which looks like a radio fault but is not.
Q&A:
Why does Ledger Live on my iPhone not find my Ledger Nano X when Bluetooth is on?
Several things can block discovery. The Nano X must be powered on and past its PIN screen. Bluetooth must be enabled in its settings. On iPhone, open Settings > Bluetooth and confirm it is on. Then open Ledger Live and allow Bluetooth access. Keep the Nano X close to the iPhone, within a few feet, and away from USB hubs or other wireless devices. If the device appears in iPhone Bluetooth settings but not in Ledger Live, remove it from iPhone Bluetooth settings and pair through Ledger Live again. Also check that Ledger Live is updated and the Nano X firmware is current. For iOS, pairing usually happens inside Ledger Live, not from the iPhone Bluetooth menu. If the app still cannot find it, restart both the iPhone and the Nano X, then try again.
My Ledger Nano X used to connect to Ledger Live on my iPhone, but now pairing fails. How can I fix it?
First, forget the device in iPhone Settings > Bluetooth. On the Nano X, go to Settings > Bluetooth and turn it off, then back on. Open Ledger Live, go to the device connection screen, and choose to pair a new device. Keep the Nano X on and past its PIN screen and near the phone. If Ledger Live asks for Bluetooth permission, allow it. If the app still fails, close Ledger Live completely by swiping it away, restart the iPhone, and try pairing once more. A stale pairing record on either side can cause this. Also update Ledger Live from the App Store and update the Nano X firmware through Ledger Live on a computer if needed.
Can I pair a Ledger Nano S Plus with Ledger Live on iPhone using Bluetooth?
No. The Nano S Plus does not have Bluetooth. Only the Ledger Nano X and Ledger Stax support Bluetooth connections. If you have a Nano S Plus, you can use it with Ledger Live on a computer through USB, but not wirelessly with an iPhone. If you need iPhone support, use a Nano X or Stax. Trying to pair a Nano S Plus over Bluetooth will not work, so the Bluetooth menu in Ledger Live will not detect it.
How do I remove a saved Ledger from my iPhone’s Bluetooth list and pair it again with Ledger Live?
Open iPhone Settings > Bluetooth. Find your Ledger Nano X or Stax under My Devices. Tap the “i” icon next to it and choose “Forget This Device.” Then turn Bluetooth off and on. Open Ledger Live, wake your Ledger, and enter your PIN on the device. Enable Bluetooth on the Ledger. In Ledger Live, go to the connection screen and select your Ledger when it appears. If it does not appear, close Ledger Live, restart the iPhone, and try again. Pairing from the iPhone Bluetooth list can create a connection that Ledger Live cannot use, so remove that entry and pair inside the app.
Ledger Live has Bluetooth permission on my iPhone, but pairing still fails. What else can I check?
Check these points one by one. Make sure the Ledger device is on and past its PIN screen. Confirm Bluetooth is on in its settings. Confirm the device is not already connected to another phone or computer; Bluetooth pairing often supports one active connection. Move away from microwaves, USB 3.0 hubs, and crowded wireless areas. Update iOS, Ledger Live, and the Ledger firmware. If you use a case or metal object near the phone or Ledger, remove it. In Ledger Live, try “Add a device” instead of selecting an old entry. If nothing works, uninstall Ledger Live, restart the iPhone, reinstall it from the App Store, and restore your accounts by adding them again. Your crypto stays on the Ledger; reinstalling the app does not move funds. If the problem remains, contact Ledger support and share the exact error message, iPhone model, iOS version, Ledger model, and firmware version.
Why does Ledger Live on my iPhone keep saying “Device not found” while my Ledger Nano X is unlocked and nearby?
First, check iPhone permissions. Open Settings > Privacy & Security > Bluetooth and make sure Ledger Live is switched on. Then open Settings > Bluetooth and look for an old entry named Ledger Nano X. If one exists, tap the info icon, choose Forget This Device, and reopen Ledger Live. On the Nano X, enter your PIN, open Settings > General > Bluetooth, and confirm Bluetooth is enabled. If there is a Reset Bluetooth option, use it to clear stored pairings. Force quit Ledger Live, turn iPhone Bluetooth off and on, and restart both the phone and the hardware wallet. Keep the Nano X within a few inches and avoid other Bluetooth devices that may be connected, such as another phone, tablet, or desktop running Ledger Live. Check that Ledger Live is updated from the App Store. If the Nano X firmware is old, update it with Ledger Live on a computer using a USB cable. When you retry, tap Add device in Ledger Live, choose Ledger Nano X, and follow the prompts. If another phone or computer still cannot find the Nano X, the Bluetooth module may need support from Ledger. Never share your recovery phrase with anyone.
I removed my Ledger Nano X from Ledger Live and now it will not pair again. Did I lose my crypto, and how do I add it back?
You did not lose your crypto. Removing the Nano X from Ledger Live or forgetting it in iPhone Bluetooth settings only clears a connection record. Your accounts and funds stay on the blockchain. To add it back, enter your PIN on the Nano X and open Ledger Live on the iPhone. Go to My Ledger, tap Add device, and select Ledger Nano X. If the phone still shows an old pairing, open iPhone Settings > Bluetooth, tap the info icon beside Ledger Nano X, and choose Forget This Device. On the Nano X, open Settings > General > Bluetooth and use Reset Bluetooth if that option appears. Then return to Ledger Live and search again. Do not reset the Nano X unless you have your recovery phrase written down, because a device reset wipes the wallet. Pairing trouble does not require a reset. If the device never appears, test it with another phone or computer. If no device finds it, contact Ledger support. Never type your recovery phrase into the iPhone or any app.