Define What a Completed Stax Session Should Show
Ledger Live iPhone Stax Bluetooth setup is complete only when the intended app can use the Stax in your hand. The app is now Ledger Wallet. A saved Bluetooth name is useful context, but an actual hardware response provides better evidence than a remembered accessory or an already loaded portfolio.
Plan three observations: the iPhone discovers your prepared Stax, both devices complete the matching pairing exchange when required and the app finishes an intended device action. Account inclusion can then be checked separately.
Prepare the Touchscreen Without Changing Wallet Identity
Power and unlock Stax using its own controls. From its dashboard, inspect Settings and Bluetooth. Ledger’s touchscreen connection guide is the relevant model reference; a Nano X sequence involving two buttons is inappropriate for Stax.
If Stax already controls accounts, retain that initialized configuration. If it is genuinely new hardware, follow its official initialization and offline-backup process. Pairing a phone is not a substitute for completing those hardware setup responsibilities.
Make the Phone Request Identifiable
Use the official current mobile app and select Stax in its device connection flow. Enable the iPhone radio and the app’s separate Bluetooth access. Apple’s permission documentation explains why the radio alone does not authorize every app.
Keep another phone from actively using Stax during this first attempt. Read the discovered label against the device you prepared, including any shortened or customized name. Do not interpret the first nearby result as your hardware without checking the ensuing interaction.
Complete the Exchange on Both Devices
When new pairing codes appear, compare the complete values before approving. Continue using the requested iPhone and Stax confirmations. If one code differs or the request was not initiated by you, cancel rather than treating the mismatch as a harmless setup detail.
A valid existing association may connect without repeating the original code. Judge that case by a real app operation instead of erasing a working relationship just to reproduce a first-time screen.
Verify Hardware Response, Then the Account View
Use a relevant nonfinancial device action, such as the supported management or receiving-address verification flow. Inspect the Stax display and confirm that the expected request appears. Bluetooth success does not mean every desktop integration or provider feature exists in the mobile app.
Add the intended supported blockchain accounts with the correct wallet configuration. Compare the network and known public history. A token’s symbol or an old nickname alone is insufficient to distinguish accounts on different chains.
If association repair is required, consult current Bluetooth troubleshooting. Stax pairing removal is a Bluetooth-settings action, distinct from factory reset. Coordinate relevant phone and app records as directed rather than deleting the whole account profile.
Keep a brief note of the selected Stax label and completed task. If a later app session fails, that record distinguishes an interrupted reconnection from setup that never reached the hardware-response stage in the first place.
Stax iPhone Setup Questions
Can I pair during a Ledger OS installation?
Leave progressing hardware maintenance undisturbed on its supported host. New pairing attempts, app deletion and connection changes wait until the installation is appropriately complete or its explicit failure has been handled.
Why is an old balance visible before Stax connects?
The interface can retain public account information. That does not prove a present hardware session or authorize a transaction. Use the expected Stax response as the connection evidence.
Will another iPhone require recovery words?
Connecting the existing configured device uses its normal supported workflow. Do not type backup words into the phone or photograph them for setup support. Keep them offline and separate from account labels and Bluetooth records.
Comments are closed