Ledger Live iOS Bluetooth Not Connecting: Checking the device in Bluetooth settings

Fix Ledger Live iOS Bluetooth Connection Issues starts with two checks that remove most false alarms: confirm the wallet carries a short-range radio, and confirm the phone still grants the companion app permission to use it. This page covers which models hold that transceiver, how the handshake is negotiated, which dropouts repeat, and a five-step verification route that rebuilds a pairing without touching the recovery phrase.

How the companion app negotiates a wireless link with a hardware wallet

The phone app asks the operating system for radio permission, scans for the wallet’s advertised name, then opens an encrypted session keyed to that device. The wallet shows a code or name on its own screen and waits for the user to confirm it, which proves both radios are talking to the same physical unit.

The permission gate the handset operating system controls

Apple’s phone system hands radio access to apps as a per-app toggle, and a declined prompt is remembered until someone re-enables it. If the prompt was dismissed during the first launch, the app never receives scan results, so the wallet list stays empty even though the hardware is powered on and advertising. The toggle usually survives ordinary restarts but can be reset by a full system restore or by deleting and reinstalling the app, which is why a fresh install sometimes restores a list that looked broken.

Pairing records the app keeps for each wallet

A completed handshake writes a small identity record on the phone side, tying the wallet’s serial number to a saved key. That record is what lets later launches reconnect without another confirmation screen. When it goes stale, typically after firmware is applied or after a different handset pairs with the same wallet, the app still lists the device but aborts silently at the handshake. Deleting the record and pairing again is the standard correction, because the wallet keeps no memory of which handset it once trusted.

What the wallet screen shows during a handshake

The device screen is the only trustworthy indicator of pairing state: an idle dashboard means the radio is off or asleep, a pairing prompt means the handshake reached the device, and a spinning or absent indicator means the phone never completed its half. A prompt that appears and vanishes within seconds points at a timeout on the phone side rather than a fault inside the wallet. Keeping the unit unlocked and on that screen removes the most common false alarm.

Which wallet models support a wireless link, and when does it apply?

Three current units carry a short-range radio: Nano X, Stax, and Flex. Nano S and Nano S Plus are cable-only, so no phone-side change will make them appear in the app’s scan list; they work with the desktop program instead. Wireless pairing therefore applies only when the unit itself has the transceiver built in.

Models with a radio and models without

Radio presence is fixed at manufacture and cannot be added by software. Nano X, Stax, and Flex contain a low-energy transceiver plus a battery, which is why they can be carried and used away from a computer. Nano S and Nano S Plus ship without that transceiver and draw power from the cable; an app on a phone will never detect them no matter how many times the scan restarts. Reading the model name printed on the back settles the question before any troubleshooting begins.

When a cable is the better route

A desk-bound workflow suits a cable: long firmware operations, large account restores, and any session where the phone battery is low or the radio environment is congested. Cable sessions also skip the on-device confirmation that every fresh wireless launch requires. For someone managing several accounts with a laptop open, the wired path removes an entire class of pairing faults, while the radio remains the only option for spending from a phone away from a desk.

Pairing routes compared by model and platform

Route choice depends on the radio inside the unit, not on app settings. A model with a transceiver pairs directly to a handset or runs over a cable to a computer; a model without one reaches only the desktop program, and no menu change alters that.

Each row below is a hardware model, and the columns record whether a wireless link exists, whether a wired link exists, and the practical limit that decides between them. Capabilities are properties of the hardware, while supported app releases and firmware windows are published on the official source.

A radio model suits spending from a phone away from a desk, with the confirmation step accepted on each launch. A cable-only model suits a workflow that lives on a laptop, where a transceiver buys nothing and adds a battery to recharge. The exception runs the other way for a traveller who owns only a cable-only unit: a laptop plus cable stays the sole route, and no app release changes that.

Why cable-only models never appear in the scan list

A scan list is built from radio advertisements, and a unit with no transceiver emits none. The app therefore shows nothing for Nano S or Nano S Plus, and repeated scans, reinstalls, or permission toggles cannot produce a result. Owners sometimes read the empty list as a broken app, then wipe the device; the empty list is correct behaviour for that hardware. Confirming the model name on the back of the unit is the only test required.

When a radio model still refuses to pair

Even with a transceiver, Nano X or Stax can fail if the phone holds a stale record for the same serial number, if another handset paired most recently, or if the battery is nearly empty. Each of these produces the same symptom, a wallet visible in the list that will not complete a handshake, so the order matters: remove the old record first, charge the unit, then pair once. A wallet that pairs cleanly with a second handset proves the hardware is sound.

Why a paired wallet keeps dropping, and which mistakes cause it

Dropouts come from four repeatable causes: a revoked permission after a system update, a stale identity record on the phone, a depleted battery that cannot sustain the radio, and a second handset claiming the same wallet. None of them indicates a damaged device, and none requires erasing the wallet.

Stale identity records that block a fresh handshake

An identity record binds one handset to one serial number. Apply new firmware, restore a phone from a backup, or pair the same wallet with a tablet, and the stored key no longer matches what the device expects, so the handshake aborts after the scan succeeds. The symptom is a unit that appears instantly and then fails. Removing the saved entry inside the app and forgetting the device in the system radio settings clears both halves; leaving either half behind reproduces the fault.

Radio contention with other accessories and apps

The 2.4 GHz band is shared with earbuds, keyboards, trackers, and Wi-Fi access points, and congestion shows up as intermittent rather than total failure. Sessions that drop when the phone sits in a pocket but hold when it lies beside the wallet point at interference or range instead of software. Moving a metre away from a crowded desk, closing other radio-heavy apps, and keeping the wallet screen facing the phone are cheap tests before any deeper repair.

Prompts that time out before confirmation

Every wireless launch on a phone asks the user to confirm on the device, and that prompt expires after a short window. If the wallet is locked, asleep, or lying face down, the confirmation never lands and the app reports a failure that looks like a dropped link. Unlocking the unit first and then starting the scan from the app reverses the order and removes the timeout. This per-session step is also why phone-based use feels slower than a cable.

How do you verify and restore a stable pairing without wiping the wallet?

Five checks restore a stalled pairing without touching the recovery phrase: confirm the model, confirm the phone permission, delete the stale record on both sides, pair once with the device awake, then prove the link survives a lock and unlock. None of these steps erases keys, and none requires reinstalling the app.

Step 1: Check the model name on the device

Read the model name printed on the back of the wallet and confirm it carries a short-range radio. A cable-only unit will never appear in a phone scan, so identifying it first prevents a pointless repair sequence.

Step 2: Confirm the app still holds radio permission

Open the phone’s settings, find the companion app, and check that radio access is enabled. A system update or a restored backup can revoke that permission silently, and the app then scans without ever receiving results.

Step 3: Delete the saved pairing on both sides

Remove the wallet’s entry inside the app, then open the phone’s radio settings and forget the device. Stale records exist in both places, and clearing only one leaves half a handshake that fails again within a session.

Step 4: Pair once with the wallet unlocked

Unlock the wallet with its PIN, keep its screen lit on the pairing view, and start the scan from the app. The confirmation prompt expires quickly, so the device must be awake before the scan begins rather than after.

Step 5: Verify the link survives a lock cycle

Lock the phone, unlock it, and reopen the app to see whether the wallet reconnects without a fresh confirmation. A reconnect that survives this cycle confirms the record was written correctly; a repeat prompt means the pairing must be cleared and rebuilt.

What changes between firmware and phone system releases?

Two schedules govern whether a pairing still works: the wallet’s firmware and the phone’s operating system. Apple ships system updates on its own cadence, the manufacturer publishes device firmware separately, and either can invalidate a saved record. Current supported versions and release notes are published on the manufacturer’s official pages and can change without notice.

How a system update can revoke permission silently

A major phone system release sometimes resets per-app radio permissions or changes how background scans are throttled, so an app that worked before an update stops seeing devices. The change is invisible inside the app; only the system settings screen shows that the toggle has moved to off. Re-enabling it restores scanning, though the first launch afterwards still needs a fresh confirmation on the device. Background scan limits can also delay discovery, which is why an open app finds hardware faster than a backgrounded one.

What firmware notes change about pairing behaviour

Firmware revisions adjust the radio stack, the confirmation timeout, and how the device advertises its name, so a handset that paired under an older build can fail under a newer one until the saved record is rebuilt. Release notes state which revisions address radio stability, and those are the pages to read before blaming the phone. Applying firmware always requires a cable on the models that accept it, which is a separate session from pairing.

Common beliefs that lead to an unnecessary reset

Two beliefs cause most avoidable damage: that a failed pairing means the wallet is corrupted, and that restoring the recovery phrase is a normal repair step. Neither holds. Pairing data lives on the phone, not inside the device’s keys, so clearing it changes nothing about the funds. Typing a recovery phrase is only necessary when hardware is lost or wiped, and a single mistyped word restores an empty account instead of the original one.

Confirm iPhone or iPad Bluetooth Settings Show Ledger Nano X

Open Settings, go to Privacy & Security, tap the short-range radio permission, and confirm the toggle for your wallet app is green; then open that app’s device list and verify Nano X shows as Paired, not merely seen earlier.

If the app is absent from that permission screen, launch the companion software once, keep Nano X unlocked and within a few centimeters, and return to the same menu. Apple’s mobile system lists an app there only after it has asked for the radio permission, so an empty entry usually means the request never reached the operating system.

Check the Control Center tile before blaming the hardware wallet: the radio antenna icon must be white, not crossed out or grey. On iPads with a Magic Keyboard, the same tile can be hidden in the expanded status menu, so swipe down from the top-right corner and look for the antenna glyph. Then open Settings > [radio] and confirm the switch is on. A stale pairing record can also block a fresh handshake: tap the information icon beside Nano X, choose Forget This Device, restart both the tablet or phone and the wallet, then pair again from inside the companion app.

After re-pairing, the device list should show Nano X as active within ten seconds; if it remains idle, toggle the system radio off and on once.

Permission alone does not guarantee a stable link. The app must also hold background refresh rights if you expect the wallet to stay reachable when the screen locks. Go to Settings > General > Background App Refresh, find the companion software, and enable it. On iPads managed by a school or employer, a configuration profile can remove that switch entirely; in that case, the restriction is set by the administrator, not by the wallet.

Version drift explains many false negatives: an older app build may not recognize the current firmware’s advertising name. Confirm the app and the Nano X firmware are on versions published on the manufacturer’s official support page, then repeat the permission and pairing checks. Do not rely on a third-party listing for version numbers.

If the permission toggle is green, the app appears under Background App Refresh, and the device list still lacks Nano X, isolate the phone or tablet from other nearby accessories. Switch off unused wireless peripherals, move away from crowded USB hubs and microwave ovens, and test in a different room. Interference affects the shared short-range band used by the wallet’s radio. When the entry finally appears, rename it to a unique label, so future checks distinguish it from a second Nano X or a friend’s device. If nothing changes after two clean pairing attempts, the remaining variables are the wallet’s battery level, the app’s cache, and the radio module itself; those require hardware service or a cache reset described by the vendor.

Q&A:

My Ledger Nano X pairs with my iPhone, but Ledger Live keeps dropping the connection. What should I try?

First, close other wallet apps that may hold the Bluetooth link. Keep the Nano X unlocked and near the phone. In Ledger Live, go to Settings > My Ledger, remove the device, then pair it again. In iOS Settings > Bluetooth, tap the i beside your Nano X and choose Forget This Device. Turn Bluetooth off and back on, restart the iPhone, and open Ledger Live. If it still drops, update Ledger Live and the Nano X firmware. Also check that the Nano X battery is not empty. A low battery can cause the link to stop.

Ledger Live says Bluetooth is disabled on iOS, but Bluetooth is on in Settings. Why does that happen?

This can happen if Ledger Live lacks permission to use Bluetooth or if the app is in a bad state. Open iPhone Settings > Ledger Live and make sure Bluetooth is toggled on. Then force close Ledger Live and reopen it. If that does not help, restart the iPhone. Some users also need to turn Bluetooth off and on in Control Center or Settings. If the message stays, delete and reinstall Ledger Live, then restore your accounts from a backup or add them again. Never enter your recovery phrase into any app or website.

Can I use Ledger Live on iPhone with a Ledger Nano S or Nano S Plus over Bluetooth?

No. Ledger Nano S and Nano S Plus do not have Bluetooth. For iPhone, you need a Bluetooth-enabled Ledger device, such as Ledger Nano X. If you have a Nano S or Nano S Plus, use a computer with a USB cable and Ledger Live for desktop.

I paired my Ledger Nano X with my iPad, and now my iPhone cannot find it. How do I fix that?

A Nano X can keep a Bluetooth link with only one host at a time. On the iPad or other phone, open Bluetooth settings, find the Nano X, and forget or unpair it. Turn Bluetooth off on that device. On the iPhone, open Settings > Bluetooth, forget the Nano X if it is listed, then turn Bluetooth off and on. Open Ledger Live, choose to pair a new device, and follow the prompts. Keep the Nano X unlocked and close to the iPhone during pairing. If the iPhone still does not see it, restart both devices and try again.

After an iOS update, Ledger Live will not connect to my Nano X at all. What else can I check?

Check app and firmware versions first. Update Ledger Live from the App Store, then connect the Nano X to a computer and update its firmware through Ledger Live desktop. On the iPhone, check Settings > Privacy & Security > Bluetooth and confirm Ledger Live is allowed. Remove the Nano X from Ledger Live, forget it in iOS Bluetooth, restart the phone, and pair again. If you use a case with metal or a magnetic part, remove it, because it can block the signal. Test with another iPhone or Android phone if you can. When none of these steps work, open a ticket with Ledger support and include your app version, iOS version, device model, and the exact error text.