How to fix Phantom wallet not detecting my Ledger via Bluetooth?

Understanding Phantom Wallet and Ledger Bluetooth Pairing

1. Phantom Wallet is a Solana-native browser extension and mobile application designed for managing SPL tokens, interacting with dApps, and signing transactions securely. It supports hardware wallet integration, including Ledger devices, via Bluetooth on iOS and Android platforms.

2. Ledger devices rely on Bluetooth Low Energy (BLE) to communicate with mobile wallets. Unlike USB connections, BLE requires precise timing synchronization, proximity, and uncluttered 2.4 GHz radio conditions—factors that directly impact Phantom’s ability to detect the device.

3. Phantom does not support Bluetooth pairing on desktop browsers; this functionality is restricted to its official iOS and Android apps. Attempting to pair via Chrome or Edge extensions will result in immediate detection failure.

4. The Ledger must be running firmware version 2.1.0 or higher and have the Solana app installed and open. Older firmware versions lack required BLE advertising packets necessary for Phantom handshake initiation.

5. Phantom uses a proprietary BLE service UUID (0000fff0-0000-1000-8000-00805f9b34fb) and expects specific GATT characteristics during discovery. Any deviation—such as custom firmware forks or modified bootloader behavior—breaks the handshake protocol silently.

Common Detection Failures and Root Causes

1. Bluetooth scanning is disabled in Phantom’s app permissions. On iOS, users must grant “Bluetooth” under Settings > Privacy & Security > Bluetooth. On Android, location permission is also required for BLE scanning—even though no GPS data is used—due to Android’s legacy BLE policy enforcement.

2. Ledger is stuck in bootloader mode instead of application mode. When powered on, the device displays “Bootloader” rather than “Solana”, preventing it from broadcasting the correct BLE service advertisement.

3. Phantom’s internal BLE cache retains stale device entries. If a previous pairing attempt failed mid-handshake, cached bonding information may block subsequent discovery attempts until manually cleared.

4. Interference from other BLE peripherals is frequent in dense environments. Smartwatches, wireless earbuds, and nearby mobile wallets actively scanning for hardware devices can saturate the BLE inquiry window, causing Phantom to miss Ledger’s advertising interval.

5. Ledger’s Bluetooth stack enters low-power sleep after 60 seconds of inactivity. If Phantom initiates scanning after this timeout—and before the user manually wakes the device—the Ledger remains invisible until physically interacted with.

Step-by-Step Device-Level Recovery

1. Power cycle both devices: Turn off Ledger completely by holding both side buttons for 10 seconds until screen blanks, then restart. Force-quit Phantom app and relaunch it—not just swipe away, but use app manager to terminate background processes.

2. Enable Ledger Bluetooth explicitly: Navigate to Settings > Connectivity > Bluetooth on the Ledger device and toggle it ON. Confirm “Bluetooth enabled” appears on screen. Do not skip this step—even if previously enabled.

3. Open Solana app on Ledger before launching Phantom. The app must be active and displaying the Solana home screen. Phantom only detects Ledger when the Solana app is foregrounded and responsive.

4. Initiate pairing from Phantom: Tap “Connect Wallet” > “Ledger” > “Continue”. Wait at least 90 seconds without touching either device. Phantom performs three sequential scan windows; premature interaction disrupts the third window where most successful detections occur.

5. Reset Ledger Bluetooth bonding: In Ledger Live desktop app, go to Manager > Settings > Reset Bluetooth pairing. This clears all stored keys and forces fresh key exchange during next Phantom handshake.

Network and Firmware Validation Checks

1. Verify Ledger firmware version using Ledger Live. Versions prior to 2.1.0 do not expose required BLE descriptors. If outdated, update firmware before attempting Phantom pairing—never skip this verification.

2. Confirm Solana app version is 2.2.1 or later. Earlier versions omit critical BLE packet signing fields, resulting in silent rejection during Phantom’s authentication phase.

3. Check Phantom app version in App Store or Play Store. Build numbers below 2.17.0 contain known race conditions in BLE GATT descriptor enumeration, leading to inconsistent device visibility.

4. Disable all other BLE-enabled apps on the phone temporarily—including Ledger Live mobile, MetaMask Mobile, and Trezor Suite. Concurrent BLE scans interfere with Phantom’s dedicated inquiry slot allocation.

5. Test with another compatible phone if available. This isolates whether the issue resides in Phantom’s local BLE stack implementation or environmental RF constraints unique to the primary device.

Frequently Asked Questions

Q: Does Phantom support Ledger Nano X via Bluetooth on iPad?Phantom does not support iPadOS for Ledger Bluetooth pairing. The iOS app binary is compiled exclusively for iPhone architecture and lacks iPad-optimized BLE stack bindings. iPad users must connect via USB-C to Lightning adapter or use web-based signing workflows.

Q: Why does Phantom show “No Ledger devices found” even when Ledger Live detects the device?Ledger Live uses a different BLE service UUID and GATT structure for management functions. Phantom communicates exclusively through the Solana-specific BLE interface, which remains inactive unless the Solana app is open and foregrounded on the Ledger.

Q: Can I use Phantom with Ledger Stax via Bluetooth?No. Ledger Stax does not expose BLE interfaces for third-party wallet integrations. Its Bluetooth stack is reserved solely for Ledger Live synchronization and firmware updates. Phantom cannot establish a secure channel with Stax devices under any configuration.

Q: Is there a way to force Phantom to re-scan without restarting the app?Yes. Swipe down on the Phantom wallet connection screen to trigger manual refresh. This bypasses cached scan results and initiates a new BLE inquiry cycle with updated timing parameters.