Make Stax Discoverable Before Changing Wallet Data
If Ledger Stax does not appear in a Ledger Live Bluetooth scan, verify device readiness, phone app access, and the discovery workflow first. The app is now called Ledger Wallet. An empty scan list concerns finding the hardware, not whether its recovery backup matches an account.
Identify whether you are scanning in the mobile app or viewing saved phone settings. The dedicated desktop application does not gain mobile Bluetooth discovery because Stax itself has a radio. Use instructions for the exact host and edition.
Inspect Stax on Its Own Screen
Charge Stax sufficiently, wake it, and unlock it through its touchscreen. Open Settings from the dashboard and check Bluetooth. Do not assume a visible lock-screen image means the device is unlocked and ready for the current interaction.
Ledger’s touchscreen connection instructions describe the Stax pairing flow. Keep the hardware close to the intended phone and close competing device sessions. A second phone already using it is a different variable from a failed Bluetooth radio.
Read the device label carefully. Current firmware behavior can abbreviate default names, so an entry may look shorter than a previous screenshot. A renamed result deserves identification, not automatic trust or automatic rejection based only on lettering.
Check the Phone’s App-Level Discovery Access
On iPhone, review the wallet app’s Bluetooth permission separately from the general radio switch. Apple’s permission guide explains the distinction. On Android, use the discovery permissions relevant to that version and Ledger’s current instructions, rather than applying iPhone menu names universally.
Start the Stax addition flow inside the genuine mobile application. If permission was denied, correct that specific condition and repeat the same scan. More camera or contact access is not a general discovery remedy.
If a permission entry is absent, reach the feature that requests it before assuming installation failed. Record whether the request occurs and whether discovery changes once access is allowed.
Interpret Visibility Separately From Pairing
If Stax appears, select the intended device and inspect both displays for matching pairing information. Cancel a mismatch; the fact that you were trying to make a device visible is not a reason to approve an unexplained peer.
If the phone already remembers Stax but the app still cannot use it, a stale association is one possibility; the saved entry alone does not prove a live app connection. Use Ledger’s model-specific troubleshooting for coordinated record removal if smaller checks fail.
Stax pairing removal uses Settings, Bluetooth, Remove pairing. Do not select factory reset, and do not clear the entire application profile by default. The goal is a coherent connection relationship, not different hardware secrets.
Compare One Supported Environment
Where practical, a scan from another compatible phone can help identify whether the symptom follows the first phone or the hardware conditions. Keep the test deliberate and never import recovery words into software for it. Report models, software versions, permissions, and the first failed stage.
Allow progressing device OS maintenance to finish before restart, host-switch, or pairing experiments. If installation has explicitly failed, follow Stax-specific recovery first; ordinary scanning advice must not interrupt firmware work.
Stax Discovery Questions
Can USB Success Prove Phone Bluetooth Works?
It demonstrates a different transport. Desktop USB and mobile discovery should be tested independently under their respective supported conditions.
Should I Reset Stax to Make It Look New?
No. Preserve the initialized wallet. Pairing state has its own scoped repair, and a factory reset cannot grant a phone app missing discovery permission.
Why Can I Still See the Portfolio?
Public account information may remain loaded without the hardware. Test a device-dependent action after discovery and pairing to confirm the live session.