Separate Foreground Pairing From Background Continuity
When Ledger Live Android Bluetooth disconnects in the background, first establish whether the connection works while the app remains visible. The application is now Ledger Wallet. A successful foreground session followed by a disconnect after switching apps is a different problem from a device that never appears in discovery.
Keep the timing precise: another app opened, the screen locked, the phone entered battery-saving mode or the Ledger itself locked. None of those observations alone proves that Android killed the application.
Reproduce the Boundary With a Nonfinancial Task
Use a supported Bluetooth Ledger model nearby and available for the app. Complete the normal app-led connection, then note whether an ordinary read-only device action works. Do not create a payment just to monitor Bluetooth behavior.
When no signing or progressing Ledger OS installation is active, compare one short foreground session with the ordinary background action that previously triggered the problem. Record whether the app closes, returns to its local lock, loses the hardware session or only needs to reconnect. Those are different results.
Inspect the App’s Battery Treatment
Check the phone manufacturer’s current per-app battery controls. Restriction names and behavior vary across Android versions and brands. If the app is explicitly restricted, assess whether a targeted change is appropriate for the expected foreground workflow, then compare the same task again.
On Samsung, the application-management documentation distinguishes sleeping and deep-sleeping behavior. Do not disable battery controls for every app or assume that a never-sleeping exception guarantees an indefinitely connected Ledger.
Keep Permission and Hardware State in View
Confirm the Bluetooth-related permission still matches the current app and Android release. Google’s permission guidance shows how to inspect app access on Pixel; other manufacturers can place the controls elsewhere.
Also inspect the Ledger’s own power, lock and Bluetooth state. A phone cannot maintain a usable session with unavailable hardware merely by changing battery optimization. Another phone or application using the same Ledger can introduce a separate session conflict.
Resume the Intended Operation Deliberately
Return to the app and reconnect through its normal flow when required. A persistent all-day Bluetooth connection is not the success criterion for every wallet task. The relevant result is that the supported operation can complete with the expected hardware confirmations.
If the app disappeared after transaction approval, inspect the real hash or provider order before retrying. A lost radio session cannot establish that a signed action was cancelled. If firmware installation is progressing, keep the supported update session stable rather than intentionally locking the phone as a test.
Notification permission is another separate setting. A visible or missing notification does not by itself prove that the operating system preserved a Bluetooth session. Record the actual app and hardware behavior after returning to the foreground. Do not grant notification or location access solely to make an unrelated battery warning disappear without a documented connection to the task.
Background-Bluetooth Questions
Does an app lock mean the Ledger disconnected?
A local privacy lock and a hardware session are separate states. Describe the prompt and test the supported reconnection after unlocking the app, without entering the Ledger PIN into the phone.
Should I clear Bluetooth pairings first?
Not when initial pairing works and the fault occurs only after a specific background transition. Identify that boundary before using any model-specific stale-pairing procedure. Never factory-reset the wallet for an Android app-management symptom.
What should support know?
Provide phone and OS details, app release, Ledger model, permission and battery settings, and the exact trigger. Use the official app from Ledger’s download links, and keep recovery words and device PINs outside logs.