User guide

This guide sits on the same site as the project home page. Below are the three main tabs—Terminal, File Explorer, and Screen Control—plus how to point Adbnik at adb and scrcpy on your machine.

ADB and scrcpy on your PC

Adbnik does not ship adb or scrcpy. You install them yourself (or unpack portable builds into a folder you control). The app only needs to know how to run those two programs.

1. Check PATH first. Open a normal command prompt or terminal on this PC and run adb version and scrcpy --version. If both print version text, you can leave the path fields empty in File → Preferences inside Adbnik.
2. Use a standard install. A common setup is Google’s platform-tools zip (contains adb) and the official scrcpy release for your OS. Install or unzip them wherever you like, then either add that folder to the system PATH or continue to the next step.
3. Set full paths in Preferences. If you do not want to change PATH, open File → Preferences in Adbnik. For ADB, browse to the real executable (on Windows often adb.exe inside platform-tools). For scrcpy, browse to scrcpy or scrcpy.exe from your scrcpy folder. Save. The status line at the bottom of the main window shows which paths are active after a restart or refresh.
4. Portable “bundle” folder. Some people keep a single directory (USB stick, network drive, or C:\Tools\android) with platform-tools and scrcpy next to each other or in subfolders. There is nothing special to “register”—copy the files in, then in Preferences point ADB at that folder’s adb and scrcpy at that build’s scrcpy binary. Same dialog as above.
5. SSH is separate: Adbnik calls your system ssh client. Install OpenSSH or Git’s SSH as you normally would; path issues are handled the same way as in any other terminal app.

From the running app you can also open Help → User guide (or the website links in Help → About) to return here.