Quick answer
How do you connect ADB to a cloud phone?
Install Android SDK Platform-Tools, then run adb connect host:port with the host and port of your cloud phone, and check that adb devices -l lists it as device. On a Droidkeep phone the host and port arrive in your Support ticket, and ADB is included on all 3 sizes. No USB cable and no adb tcpip step are needed.
In brief
- Tool:
adbfrom Android SDK Platform-Tools, current version from developer.android.com. - Command:
adb connect host:port; the phone already listens, soadb tcpip 5555is skipped. - Check:
adb devices -lmust show the statedevice. - Several devices: add
-s host:portto every command. - Done:
adb disconnect host:port.
How do you connect, step by step?
Six steps, all from the Android Debug Bridge documentation. Replace host:port with the values posted with your phone.
Install Platform-Tools
Download SDK Platform-Tools for Windows, macOS or Linux from developer.android.com, unzip it, and add the folder to your PATH. Android Studio users already have it in
android_sdk/platform-tools/.Find the host and port
Open Support in the Droidkeep client area and open the ticket with your phone's access details. Copy the ADB host and port.
Connect
Run
adb connect host:port. The first command also starts the local ADB server on port 5037.Check the state
Run
adb devices -l. The linehost:port devicemeans the phone answers.offlinemeans it does not.Send commands
Run
adb -s host:port shellfor a shell, oradb -s host:port install app.apkfor an app. With one device only,-scan be left out.Disconnect
Run
adb disconnect host:portwhen you are done. The phone keeps running.
adb connect host:port
adb devices -l
adb -s host:port shell pm list packages -3
adb -s host:port install app.apk
adb disconnect host:portWhat do the ADB errors mean and how do you fix them?
Most failures are a wrong host or port, a stale ADB server, or more than one device. The fixes below follow the ADB documentation.
| What you see | Usual cause | Fix |
|---|---|---|
failed to connect to host:port | Wrong host or port, or the rental has ended | Copy both again from the ticket; check that the rental has not ended |
State offline | The phone does not answer ADB | adb disconnect host:port, then adb connect host:port |
| Still offline after reconnecting | A stale local ADB server | adb kill-server, then connect again |
more than one device/emulator | A USB phone or emulator is also connected | Add -s host:port to the command |
adb: command not found | Platform-Tools not on the PATH | Add the platform-tools folder to PATH, or run adb from it |
| Offline for more than a few minutes | A problem on the phone side | Open a ticket in Support with the time (UTC) and the message |
Why is there no adb tcpip step?
Because a cloud phone already listens for ADB on the network. On a phone at home, the Android documentation has you plug in a USB cable, run adb tcpip 5555 and only then adb connect. That step switches the phone's ADB daemon from USB to TCP/IP.
A Droidkeep phone is delivered with ADB on a network port, so you go straight to adb connect. ADB over the network on every plan: adb connect to the host and port shown with your phone, then adb install, adb shell, scrcpy or Appium.
How do you keep the connection safe?
Treat the host and port like a password. Anyone who can connect can install apps and read files on the phone. Keep the values out of public repositories, screenshots and chats. Run adb disconnect host:port when you stop working.
The ADB cloud phone page lists what ADB can and cannot do on a Droidkeep phone. Root is not included.
What should you do next?
Mirror the screen, install an app, or start testing.
- Mirror the phone with scrcpy to see and control it from your desktop.
- Install an APK with
adb install. - Connect to your phone explains where the access details sit in the client area.
Droidkeep checked 8 cloud phone price pages on 16 November 2026: GeeLark was the only one to list ADB, from its Base plan.
ADB connection questions
Which port does a Droidkeep phone use for ADB?
The one posted with your phone. It is not always 5555, so always copy it from the ticket.
Do I need adb pair?
No. adb pair is for Wireless debugging on a phone you hold. A Droidkeep phone takes adb connect directly.
Does the connection survive my computer sleeping?
Often not. Run adb connect host:port again after sleep; the phone itself kept running.
Can I use ADB from a server instead of my laptop?
Yes. Install Platform-Tools on the server and run the same commands there.
Does disconnecting stop the phone?
No. adb disconnect only closes your link. The phone keeps running 24 hours a day for the whole rental, whether or not a screen is open; apps stay where you left them.
Verdict
- Two commands do the job:
adb connect host:port, thenadb devices -lto confirm the statedevice. - When it fails, reconnect, then
adb kill-server, then open a ticket with the time and the message.
Sources (2)
- Android Debug Bridge (adb) — Android Developers (read 2026-11-16)
- SDK Platform-Tools release notes — Android Developers (read 2026-11-16)
Get a phone with ADB
ADB over the network on every Droidkeep plan, from $0.09 a day.