Android Debug Bridge
Android Debug Bridge (ADB) is a command-line tool in Android SDK Platform Tools. It lets a computer communicate with an Android phone, tablet or emulator over a USB or network connection.
Quick answer
ADB lets you install an app, read device logs, copy files or open a shell on a connected device. Run adb devices to see which connections your computer knows about. On a GeeLark cloud phone, match the address shown in the profile to a listed connection, then use its full serial with adb -s to target that phone.
How ADB connects to Android
When you type an ADB command, the client on your computer passes it to a local ADB server. That server keeps track of device connections and communicates with a process called adbd on each device. A USB phone, a local emulator and a remote cloud phone can all appear in the same list. Android’s ADB reference
If an app closes when you attach a video on a GeeLark cloud phone, you can reproduce the problem on that phone and read its Android logs with logcat from your workstation. If your goal is to repeat the same taps across several cloud phones, GeeLark’s Synchronizer can mirror those actions from a main window. GeeLark’s guide to Android app automation
How GeeLark connects a cloud phone to ADB
In GeeLark, ADB access is a setting on each cloud phone profile. With ADB enabled and the phone running, open the link icon in its window to see the current connection address and code. Connect to that address from your workstation, then log in on the same connection using the profile’s code. Keep the code out of shared logs. GeeLark ADB connection guide
A script can look up those details by GeeLark cloud phone ID using geelark-cli phone adb get-info --ids "PHONE_ID". With the API, find the result for the requested ID and check its own code is 0 and that ip, port and the connection code (pwd) are present on that same row. Keep pwd private when handling or logging the response. A successful request can contain a failed result for one phone. The full address, including the port, is the ADB serial to match in adb devices. GeeLark CLI reference · Get ADB information
Which phone receives the test build?
Suppose phone A holds a baseline build and phone B needs a test APK. In this example, GeeLark shows 192.0.2.10:41001 for A and 192.0.2.10:41002 for B. The port distinguishes them. In adb devices, find the one row that matches B’s full address. Check that the row is marked device, then complete glogin on that serial using B’s current connection code. If login fails after a restart, retrieve B’s current details and authenticate again before proceeding. The first command below checks that the shell on B returns the expected marker.
For a first install of a test-only APK on B, use B’s verified serial and the application ID you expect the APK to contain. Replace the example values with your own.
serial='192.0.2.10:41002'
app_id='com.example.testapp'
probe=$(adb -s "$serial" shell echo GEELARK_READY) &&
[ "$probe" = GEELARK_READY ] &&
install_result=$(adb -s "$serial" install -t ./test-build.apk) &&
printf '%s\n' "$install_result" | grep -Ex 'Success[[:space:]]*' &&
paths=$(adb -s "$serial" shell pm path "$app_id") &&
printf '%s\n' "$paths" | grep -E '^package:/.+\.apk[[:space:]]*$'
The package check runs only after the installer exits successfully and reports Success. The whole snippet succeeds only if the query also exits successfully and returns an APK path for the expected application ID on B. An older copy can still have a path after a failed install. To verify the release, compare the installed versionCode with the expected value. Builds that share a version code need a separate build identifier. Android package manager reference
Frequently asked questions
Final takeaway
Start with the GeeLark profile for the phone you intend to test. Once its current address matches a connected ADB serial, use that serial for the action and the result check. For your first connection, follow the GeeLark ADB setup guide.
Image to video

