Repository navigation
Connection
How the app talks to the Flipper: the two transports, remembered devices, several Flippers at once, automatic connection, and what keeps the link alive. The first connection step by step is in Getting Started.
| Bluetooth | USB cable | |
|---|---|---|
| Platforms | All | Android, macOS, Windows, Linux |
| Setup | Pair once; the Flipper shows a PIN | Plug in, no pairing |
| Speed | Enough for everyday use | Much faster: firmware installs, big file transfers |
| Needs on the Flipper | Bluetooth on in Settings → Bluetooth | Main menu, no app holding the USB port |
| Not available over it | Command line | — |
Both links drive the same screens: device info, archive, file manager, apps, remote control. The badge next to the device name in the header shows which link is active, BLE or USB. Flipper apps that take over one of the two ports are listed in Getting Started.
After a successful Bluetooth connection the Flipper is remembered and listed under Search on the home screen, newest first. The list keeps the last eight devices.

- Tap a remembered device to connect. The app first looks for it among the devices the system already knows, without a scan, and scans for up to eight seconds only if it is not there.
- ✕ forgets it in the app. The Bluetooth pairing itself stays in the system and on the Flipper; to remove that as well, forget the Flipper in the system Bluetooth settings and on the Flipper in Settings → Bluetooth → Forget all paired devices.
- USB is never remembered. A cable is an explicit action: a plugged-in Flipper is listed while it is plugged in and disappears with the cable.
Every connection is a session, and connecting to another device does not close the previous one. You can hold a second Flipper, or the same Flipper over the other transport, and switch between them instantly.

- One session is Active: every screen of the app works with it.
- The others show Connected — tap to switch. Switching only reroutes the app to the other session, nothing is reconnected, so it is immediate.
- The link-off icon on the right disconnects that session. Disconnecting the active one makes the most recently used remaining session active.
Set in Settings → Device.

| Setting | Default | What it does |
|---|---|---|
| USB auto-connect | off | Connect to a Flipper as soon as it is plugged in with a cable |
| Bluetooth auto-connect | on | Connect to the last remembered device when it is in range. On start the app checks the devices the system knows, then scans once for eight seconds |
| Sync time on start | on | Send the phone clock to the Flipper once it is connected |
The rules when both transports are enabled:
- A plugged-in USB Flipper always wins: the cable is an explicit action.
- With no cable, the last remembered Bluetooth device connects.
- An unknown Bluetooth device never connects on its own.
- A device you disconnected by hand is left alone until it goes away and comes back, or until you tap it.
If the link dies on its own, the Flipper went out of range or rebooted, the session reconnects in place: same device, and every request that was waiting in the queue is kept. Only the commands whose state on the Flipper died with the link fail. When the link keeps dying right after connecting, the app stops retrying and waits for you to connect by hand.
While the app is in the background, or its window is not focused on desktop, a link that stays down shows a Connection Lost notification. It is removed as soon as the device is back.
- Android. A foreground service holds the link while the screen is off or another app is in front; it shows the permanent Connected to notification Android requires. The service asks once for the notifications permission and for the battery optimization exemption, see Permissions. The session lives with the app process, not with the screen: leaving the app and coming back continues the same connection. Android only lets the service start while the app is on screen, so a link established in the background is protected the moment the app returns to the front.
- iOS. No service; the link is kept by the system's Bluetooth background task together with the GPS and internet the app proxies to the Flipper. Still in beta.
- Desktop. Nothing is suspended. Hiding the window to the tray keeps the link.
A failed connection shows a dialog that names the cause: pairing out of date, pairing not completed, Bluetooth unavailable, too many paired devices, connection in progress, device not reachable, connection failed. Each is explained with its fix in Error Codes.
Next: Device for device info, firmware updates and repair from DFU mode.
Releases · Issues · Unleashed firmware · Telegram · Discord
Using the app
Reference