Usage guide

1. Click Connect ▾ → Connect to a device…
2. Under How is it connected? pick USB, Network (IP and port) or Remote (a device on another PC's adb server).
3. Hit Connect — a device tab opens with Terminal, Logcat, Files, Device Control, Apps, Phone and Webcam.

Attached devices also appear under Connected in the left sidebar — double-click any to open it. For Wi-Fi use Connect ▾ → Discover Wi-Fi devices or Pair device (Android 11+), or switch a USB device with More ▾ → Go wireless (USB → Wi-Fi).

1. Open a device → Terminal tab → type. The boxed banner at the top shows the connection, device type, Android version, CPU and serial. The Android shell runs on a device terminal, so ping and logcat | grep show their output as it comes and programs that ask for input (read, su) work. Full-screen programs (top, vi, less) redraw in place and get every key. Colour is kept for what matters: the words that say what happened (a red Permission denied or not found, an amber Warning, a green Success) and logcat's warning and error lines; the prompt is one quiet colour and everything else stays plain.
2. Right-click for Copy / Paste / Send key / Save full output to file…; Stop (Ctrl+C) stops whatever is running and keeps the shell (ping prints its summary); a command that ignores it is ended by reopening the shell in the same folder. A− / A+ resize every terminal together (12 pt by default).
3. Click PowerShell or CMD in the switcher for a Windows shell with TurboADB's adb first on PATH and ANDROID_SERIAL set — Python, Git and where work like in a normal console, and Stop works like Ctrl+C in a console window: the command stops and the shell keeps its folder and variables (a program that answers Ctrl+C, such as a python prompt, keeps running; a shell still waiting for an answer three seconds later gets a fresh shell in the same folder). Inside an adb shell typed there, Stop stops only the device command and keeps you in adb shell; if the command ignores it, Stop again reopens adb shell in the same folder.

1. Open the Logcat tab, pick the level and how much history to include (Live from now, Last 1,000 + live, …) and optionally Tag(s) (comma-separated) or an App (package name or PID, Android 7+).
2. Press Start (or the Crashes preset). Type a regex in Filter to hide non-matching lines (it ignores case unless Aa is on, and searches the whole capture), or in Highlight (e.g. error|anr|crash) to mark matches in-line without hiding the rest.
3. Save… writes the complete log to a .log file.

Files tab → This PC and Device side by side → select files and press Push or Pull, or drag and drop (also from Explorer). New folder, New file, Open, Edit (F4), Copy / Paste, Rename (F2) and Delete work in both panes.

Double-click (or Enter) opens a file in its app on this PC: pictures in Photos, videos in Media Player, text in Notepad, or any app you pick with Open with…. A device file opens as a copy, and each time you save it there it goes back to the device (TurboADB asks first if the device file changed meanwhile). Programs are never started; scripts and files no app opens go to the built-in editor, which asks the same before it saves over a device file that changed since you opened it.

Drag beside the names to select a block, Ctrl+A for all, Enter to open, Backspace to go up. Delete sends local files to the Recycle Bin, Shift+Delete deletes for good. A PC file or folder whose name ends in a dot or a space (made by WSL, Git Bash or a Linux drive) is left alone, with a message saying why. If the device refuses a change, TurboADB offers adb root, disable-verity and remount, then tries again.

Apps tab → Install APK(s)…, or filter the list (Third-party only) and pick a package for Start, Stop, Clear data or Uninstall.

Device Control tab → the Device controls panel beside the screen: Navigation, Media & volume, Quick settings (Wi-Fi, Bluetooth, Mobile data, Airplane mode, Hotspot), Screen & power, Apps & web and Keyboard.

1. Open the device's Device Control tab (or use Screen ▾ at the right end of the section tabs).
2. Pick a display, then Start screen (inside the tab) or Separate window. Click the screen to type on it with your PC keyboard.
3. Options holds audio, Compatibility mode (IVI / automotive) for stubborn head units, the keyboard mode, Device camera (Back / Front), Manage displays… and All displays.
4. Record… records without restarting the live view; Maximize view and Hide controls give the screen more room (Show controls works while maximized too). The controls sit beside the screen or below it, whichever shows the screen larger.
5. On cars (and any device with several displays) the IVI Displays tab shows every display side by side, each with its own Start / Stop and Back, Home, Recents, volume, power and screenshot buttons. Every display starts stopped (opening the tab or a rescan never starts one): start the ones you need, or Start all to start them one after another. Maximize shows a single display (Esc restores); Start all, Stop all and Rescan are at the top.
6. If scrcpy can't run on a build, Settings → scrcpy → Screen renderer → ADB screencap shows the screen through adb screencap — slower, but touch, drag, scroll and typing still work.

The display picker lists every display with its name and size as soon as the device connects — TurboADB asks Android over adb, so connecting never starts scrcpy on its own.

Screenshot at the right end of the section tabs; Record… in the Device Control screen toolbar. With the screen live, a second, windowless recorder runs beside it and saves a playable MP4. Closing TurboADB while a recording runs or is still being saved waits for it: a dialog names the file, and Close without saving is the way out.

1. Choose Tools ▾ → Open host webcam (or View → Open webcam (host camera)) — it opens as a standalone tab, no device needed. Every device also has its own Webcam tab. Source = Local — this PC.
2. Click Scan cameras (the first time, ffmpeg is fetched once, ~160 MB → ~/.turboadb/ffmpeg), pick a camera, resolution and frame rate.
3. Press Start camera. Then Snapshot, Record (clean H.264 MP4), Pause, Rotate, Flip, and View: Fit · Fill · Stretch.

No camera listed over RDP? Enable camera redirection in the RDP client (Local Resources → More… → Cameras), turn on Windows camera privacy, and close any app already using it.

1. Set Source = Remote — Windows PC and enter the RDP host, User, Domain and Password.
2. Scan cameras, then Start camera — TurboADB uses the same WinRM/NTLM path as deploy-serve to launch ffmpeg on the remote and stream its camera back over a direct TCP socket. Each stream uses a port of its own (28100–28115): open that range in a firewall between the PCs to view more than one.

The target needs WinRM on (Enable-PSRemoting -Force) and the account a local admin. ffmpeg is downloaded onto the remote automatically on first use (or drop ffmpeg.exe in %USERPROFILE%\.turboadb\ffmpeg\). The host / user / domain are remembered and the password is kept in the Windows Credential vault, never in a file. A physical USB camera works headlessly; a camera redirected into an RDP session is only visible inside it. Record encodes on this PC, and offers the one-time ffmpeg download when this PC has none.

The webcam is a desktop feature (not an adb device op, so there's no CLI / Python call). Bring your own ffmpeg via Settings → ffmpeg path for offline use.

1. Open the device's Phone tab. The pill shows Idle, Ringing or In call, and Checking… while the device does not answer (it is rebooting or unplugged): the page loads again once the device is back.
2. Type a number or use the keypad (hold 0 for +), then Call, End or Answer. Open in dialler (or Enter) only opens the device dialler pre-filled. While the pill shows Idle, End sends nothing.
3. Switch between Recent calls and Messages. Call back fills the dialler; Compose in Messages opens a draft on the device, where you press Send.

On a head unit without a phone the tab checks what the device has and says so calmly: no telephony, no call history, and — when there's no standard phone app — an Open … button for the device's own phone app instead of a dialler that can't work.

More ▾ → Root and mount at the right end of the section tabs.

Connect ▾ → Connect to a device… → Remote; enter that PC's host, then Scan devices there and pick the device.

ADB server ▾ → Share THIS PC's devices… (Start once or Start + run at login; opening the firewall needs Administrator, and sharing ends on a warning when the firewall may keep other machines out). To undo it, ADB server ▾ → Stop sharing & remove auto-start — stops sharing and removes both the login launcher and the SYSTEM startup task. Removing that task needs Administrator too: TurboADB says so when it is still installed.

The shared adb server has no password: anyone who can reach its port can control the devices. The firewall rules therefore apply on Domain and Private networks only; on a network Windows calls Public nobody can connect until you make it Private. Stopping sharing deletes the rules again.

ADB server ▾ → Deploy to remote machine(s) (RDP / WinRM)… → enter host(s) + admin credentials → Test connection → Deploy.

• Themes — Graphite / Porcelain by default, plus Black / White, Slate / Mist, Night / Paper and Mocha / Latte, all soft on the eyes. The top-bar sun or moon switches between your last dark and last light theme; its arrow, the Themes menu and Settings → Themes pick any theme directly.
• Split view — More ▾ → Split view shows Terminal, Device Control, Files and Logcat side by side, stacked or in a grid.
• Maximize view and Hide controls in Device Control give the screen the whole window; ‹ or Ctrl+B hides the device list.
• Notifications — a small toast for every action and a red popup with a sound and Copy for errors. The log panel icon opens the filterable log (Normal, Verbose, Warnings + Errors, Errors only).
• Settings — Appearance, Tools (adb / scrcpy / ffmpeg paths), scrcpy video and audio, Logcat, Themes and Startup.
• Menu bar extras — export / import saved targets (File) and Run a command on ALL devices… (Device).

Tools ▾ → Check for updates… updates TurboADB from PyPI, refreshes adb/scrcpy, and restarts. The standalone Windows app and a source checkout, which pip cannot update, are told when a newer version is out and how to get it. Tools ▾ → Download and reinstall ADB and scrcpy… refreshes only the tools.