Use the Stax Screen as Evidence, Not Decoration
If Stax is not showing in a Ledger Live Bluetooth scan, establish its operational state through the device controls. The app is now Ledger Wallet. A visible screen image is not the same observation as an unlocked dashboard ready for the requested interaction.
Check power, unlock Stax and inspect Bluetooth from its touchscreen Settings. Do not apply a Nano X button sequence. The Stax model specifications and current model guide are the references for this hardware.
Identify the Scanner You Are Actually Using
Open the supported mobile application and its Stax connection flow. A phone’s saved Bluetooth devices are not a fresh app discovery result. Likewise, the dedicated desktop client’s USB workflow should not be judged by whether a mobile Bluetooth scanner is present.
Record the screen and exact message. A device absent from discovery differs from one selected successfully but failing during confirmation. Keeping that distinction prevents a completed scan from being described as not detected later.
Make the Phone’s Access Test Specific
On iPhone, inspect the app’s Bluetooth privacy authorization separately from the radio switch. Apple’s Bluetooth permission guide explains that boundary. If the app entry is absent, use the feature that requests access and observe whether iOS presents it.
On Android, follow the discovery permissions appropriate to the OS and app version. Do not copy an iPhone menu path or enable unrelated capabilities. A camera grant for QR import cannot stand in for the permission needed for a hardware scan.
Remove Extra Participants From the Attempt
Keep the prepared Stax near one intended phone. Finish another phone’s ordinary active device session and close competing wallet clients. Start a single app-led search with both displays visible, rather than creating several requests and guessing which one belongs to Stax.
Read shortened or customized names carefully. A different label is something to inspect, not a reason to trust an unknown peer or overlook your own device automatically. When a code exchange follows, compare all digits before confirming.
Use the Changed Result to Choose the Next Step
- If Stax appears after access is granted, continue the model’s pairing flow.
- If it appears but cannot pair, preserve the confirmation-stage error.
- If the scan stays empty, report the prepared device and permission state.
- If the app can use Stax but data remains stale, investigate that later request.
For an indicated stale association, use Ledger’s touchscreen connection guidance and the current repair procedure. Stax’s scoped Bluetooth pairing removal must not be replaced by a factory reset.
A second compatible phone can provide a controlled comparison if ordinary setup is idle. Do not move an actively progressing Ledger OS installation between hosts to conduct that experiment. Preserve the update or resolve its explicit failed state under Stax-specific instructions.
If Stax becomes visible only after waking and unlocking it, preserve that result. It is more specific than claiming the phone’s Bluetooth was repaired, and it gives a useful readiness check for the next ordinary session.
Stax Scan Questions
Is charging enough to establish availability?
Power is one condition. The device’s lock and radio state, phone permission and app workflow still matter. Record each observation instead of assuming a lit or recognizable screen proves the whole session.
Should I reinstall because no result appears?
Locate the discovery boundary first. App removal can discard useful local records without changing Stax readiness or a denied permission. Use broader repair only for a relevant documented reason.
Do account balances prove Stax is connected?
No. Public history may remain visible without hardware. Verify an intended live device response, and keep recovery words outside both phone inputs and support reports.
Comments are closed