How pairing works — security model
Pairing is the process that lets your phone and hardware wallet exchange encrypted messages so the mobile app can ask the device to sign transactions. The important security points are:
- Private keys stay inside the device's secure element (a dedicated secure chip) and never leave.
- Pairing uses a short interactive confirmation on the device (a numeric code or approval) to prevent man-in-the-middle attacks.
- The mobile app is a UI and relay. It builds unsigned transactions; the wallet shows the transaction details and the user confirms on the device before any signing occurs.
In my testing I verified that the device repeatedly asks for confirmation on-screen before signing. That physical confirmation is the main trust anchor. If you want a deeper look at the architecture, see /security-architecture and /connectivity-security.
iOS workflow: step by step (ledger wallet app iphone)
How to pair on an iPhone (summary of the screens and actions I saw):
- Charge the hardware wallet to a comfortable level (15–20% or more). I like to start with a charged device.
- Install the official mobile app from the App Store and open it. Grant the app Bluetooth permission if prompted.
- Unlock the device with your PIN and open the appropriate app on the device (often the cryptocurrency app you'll use).
- In the mobile app choose "Connect device" or "Pair a device" and select the device name shown.
- Confirm the numeric pairing code shown on both phone and device. The device will require you to approve the connection.
- Add accounts (the app reads public keys and shows account balances). You can now prepare and sign transactions: the phone builds the transaction, the device asks for approval, you confirm on-device.
I noticed iOS sometimes shows a system-level Bluetooth permission once; accept it so the app can scan. And yes, make sure you confirm the code on the screen — that’s the anti-hijack check.
Android workflow: step by step (ledger wallet app android)
Android pairing is similar but has a few platform quirks:
- Install the mobile app from Google Play (or the official APK if you use another store).
- Grant Bluetooth and any location/nearby-device permissions the app requests (Android requires these for Bluetooth scanning on certain versions).
- Unlock your hardware wallet and open the relevant cryptocurrency app on it.
- In the mobile app, tap "Connect" and select the device. Approve the numeric pairing code on the hardware wallet and confirm.
- If the phone supports USB-C OTG and you prefer a wired connection, connect with a USB cable — no Bluetooth needed. This can be useful for troubleshooting or when Bluetooth reliability is poor.
But keep this in mind: different Android phones handle Bluetooth stack and permissions differently, so if you run into problems try the USB option or test pairing on a second phone.
Troubleshooting: ledger mobile not connecting
Common fixes when the mobile app cannot pair:
- Ensure the device is awake and unlocked. The wallet often sleeps to save battery.
- Toggle Bluetooth on the phone and restart the mobile app.
- Revoke and re-grant Bluetooth and "Nearby devices" permissions in Android settings.
- Remove old pairings from your phone's Bluetooth list and from the wallet if available, then retry pairing.
- Try a USB connection (Android OTG) to isolate Bluetooth issues.
- Restart your phone and the hardware wallet. This resolves race conditions I hit during testing.
- Update the mobile app and the device firmware (follow our step-by-step firmware guide: /how-to-update-firmware-steps).
If nothing works, check /troubleshooting-not-detected and /troubleshooting-general for deeper diagnostics.
Bluetooth vs USB — quick comparison
| Connection method |
Pros |
Cons |
Typical use case |
| Bluetooth |
Wireless, convenient on phone, mobile signing on the go |
Slightly larger attack surface (requires careful pairing); battery use |
Everyday mobile transactions when you want portability |
| USB (OTG) |
Direct connection, fewer wireless variables, often more stable |
Requires cable/adapter, less convenient on the move |
Firmware updates, troubleshooting, users who prefer minimal wireless exposure |
(Neither method exposes private keys; both request on-device approval before signing.)
Practical tips: permissions, passphrase, firmware
- Permissions: Only grant the Bluetooth/nearby-device permissions to the official mobile app. On Android, location-like permissions may be necessary for scanning.
- Passphrase (25th word): If you use a passphrase, enter it on the hardware wallet when possible. Typing the passphrase on a phone increases exposure to mobile malware. See /passphrase-25th-word.
- Firmware: Keep firmware up to date for security fixes, but update from official channels and verify firmware authenticity. See /firmware-updates-verification and /how-to-update-firmware-steps.
- Supply-chain checks: When you first unbox, verify tamper indicators and follow the setup guide at /nano-x-unboxing and /supply-chain-tamper.
I believe many connection issues stem from permissions or phone-specific Bluetooth stacks rather than the hardware wallet itself. So try a second phone before panicking.
Multisig and mobile compatibility
Multisig adds security by requiring multiple devices to sign a transaction. But how it works with mobile varies:
- Some multisig setups are desktop-focused and expect hardware signers to be connected to a desktop wallet.
- A few mobile wallets support hardware signers for multisig; check compatibility before you build a multisig plan. See /multisig-setup-compatibility and /multisig-setup.
If you plan multisig primarily from a phone, test the full flow (create a policy, export cosigner XPUBs, sign a sample transaction) before moving substantial funds. What I've found is that initial setup often goes smoother on desktop.
FAQ
Q: Can I recover my crypto if the device breaks?
A: Yes. Your seed phrase (recovery phrase) lets you restore accounts to another compatible hardware wallet or supported software. See /restore-recovery and /recover-if-broken.
Q: What happens if the company goes bankrupt?
A: Ownership of crypto is determined by the seed phrase and private keys. If you control the seed phrase, you still control the crypto. Read more at /company-bankrupt.
Q: Is Bluetooth safe for a hardware wallet?
A: Bluetooth is convenient and designed so that the mobile app cannot extract private keys. But pairing must be confirmed on-device. For a higher-risk threat model, prefer wired or air-gapped signing. See /connectivity-security.
Conclusion and next steps
Pairing the mobile app with your Ledger Nano X on iOS or Android is straightforward once you understand the confirmation steps and permissions involved. I tested both platforms and found Bluetooth reliable for everyday use, with USB as a solid fallback for troubleshooting or extra caution.
Want setup steps beyond pairing? Follow the practical setup guide at /nano-x-setup and the first-time setup checklist at /first-time-setup. If you need troubleshooting, start at /troubleshooting-not-detected.
If you plan to use this hardware wallet on the go, test a small transfer first. That confirms your workflow without risking much. And if you have more advanced needs like multisig, consult /multisig-setup-compatibility before you commit.
If this article answered your pairing questions, check the main review at /nano-x-review or compare mobile workflows with other models at /comparison-table.
