This guide explains how to connect a hardware wallet to iOS and Android phones, what permissions mobile companion apps typically request, and how to keep long-term holdings safe while using a phone. I write from hands-on testing and real use: I set up hardware wallets with phones across multiple OS versions. What I've found is that the process is straightforward if you follow the checklist, but subtle permission or cable issues are common.
If you want the companion app itself, start with the official companion app download and install guide: /ledger-live-download-install.
There are three common ways a hardware wallet talks to a phone:
All three approaches can be secure if you understand trade-offs. Bluetooth is convenient for daily use. USB-C minimizes the attack surface because there's no radio. Air-gapped is the most conservative for cold storage.
How to connect your hardware wallet to an iPhone (step by step):
In my testing, pairing usually takes less than a minute on iOS. But if you see a persistent pairing failure, check that the phone's Bluetooth is not blocked by a VPN or device policy.
Android gives two practical options: USB-C direct connection or Bluetooth. Which to use depends on your phone and threat model.
USB‑C (recommended for many advanced users):
Bluetooth pairing on Android:
If you use a phone with USB-C, this often avoids additional permissions required for BLE scanning. I believe USB-C connections are slightly simpler to audit because there's no radio involved, but either method can be secure.
If you need cable tips, see the USB cable pairing guide: /usb-cables-pairing.
Mobile apps request permissions so they can discover and talk to the hardware wallet. Typical permissions include:
Grant the minimum permissions needed and revoke them when not in use (you can revoke in OS settings). Why trust this? Because the hardware wallet performs private key operations inside the device (secure element), and the companion app only sends unsigned transactions to the device for on-device signing.
But remember: if the mobile app or phone is compromised, screen prompts and physical confirmation on the hardware wallet are your last line of defense.
Firmware keeps the device secure and adds coin support. Always verify firmware updates within the official companion app and check the device screen before approving any update. (The device should display the update details.) See the firmware verification guide: /firmware-updates-and-verification.
Supply-chain attacks are rare but real. If you buy a used device, restore from a new device and perform a factory reset where possible. I recommend reviewing the device authenticity and where-to-buy guidance here: /buying-supply-chain-safety.
And remember to check simple things first — cable orientation, battery charge on the phone, or airplane mode.
Passphrase (the optional 25th word) can dramatically increase security by creating an extra hidden account. But it also adds complexity: if you forget the passphrase, recovery is impossible. I strongly suggest practicing passphrase usage with a small test amount before putting large sums behind it. See /passphrase-usage-risks and /seed-phrase-basics.
Air-gapped signing (QR workflows or offline computers) removes radio and cable pathways entirely. If your threat model includes compromised phones, consider air-gapped signing for large long-term holdings.
Multi-signature setups split control across multiple devices or people. For long-term self-custody this can be better than a single-device root. The trade-off is operational complexity. If you are curious, the multisig setup guide is here: /multisig-setup-ledger.
| Connection type | Pros | Cons | Best for |
|---|---|---|---|
| Bluetooth | Convenient, wireless daily use | Radio surface increases attack surface vs cable | daily transactions, mobile wallets |
| USB‑C / wired | Minimal surface, easier troubleshooting | Needs cable/adapters | power users, firmware installs |
| Air‑gapped | Highest isolation | More steps and hardware | cold storage, large holdings |
Q: Can I recover my crypto if the device breaks? A: Yes — with your seed phrase (recovery phrase) and, if used, the passphrase. Practice a full recovery on a spare device before you need it. See /restore-recover-failure and /seed-phrase-basics.
Q: What happens if the company behind my hardware wallet goes bankrupt? A: Your private keys live with you. Provided the recovery standard (BIP-39 or SLIP-39) remains supported, you can restore to another compatible hardware wallet or software that supports the same derivation paths. Read about business risk here: /company-bankruptcy-and-business-risk.
Q: Is Bluetooth safe for a hardware wallet? A: Bluetooth has a larger attack surface than a cable, but when pairing codes are verified on the device (and the device uses a secure element), risk is low for typical users. For very large holdings or high-risk users, prefer USB‑C or air-gapped workflows.
Mobile setup for hardware wallets works well on both iOS and Android when you follow a careful, step-by-step approach. Verify firmware, confirm pairing codes on-device, and keep your seed phrase offline on a metal backup if you want extreme durability (see /metal-backup-plates).
If you’re ready to continue, start with the companion app install guide and the firmware verification guide: /ledger-live-download-install • /firmware-updates-and-verification. And if you need help troubleshooting a specific connection error, check /troubleshoot-cannot-connect.
Safe setup takes a few extra minutes up front. I believe that small habits — verifying codes, using quality cables, and testing recovery — pay off over years of secure self-custody.