BenchFleet

Appearance

Published

Use a phone you rent elsewhere ​

If you already get time on a phone in another cloud, the Hub can control it like any phone of yours: watch it, take it over, run workflows and let an AI agent use it. The only thing the cloud must give you is an ADB connection.

Many cloud services do not. A service that only shows the phone in a web page, or only lets you type a few allowed commands, cannot be added. Check its own documentation for "ADB" first.

The general way ​

  1. In the other cloud, start a phone and turn its ADB connection on. It will show either an address (HOST:PORT) or a small program to run on your computer, which then prints a local address such as localhost:7000.
  2. If there is a program, run it and leave it open.
  3. In the app: Fleet → Add phone → By address. Paste the address, or the whole adb connect HOST:PORT line the service gave you, and press Connect.
  4. The phone appears on the Fleet page. A phone behind a local address often has no serial number of its own; it then waits in the list of waiting phones as No serial number, and Give it an identity lets the Hub recognise it. The address can change every session, so you may do this again next time.
  5. When you finish, disconnect in the other cloud. The phone stays in your list as offline.

Close other adb users first. The Hub runs its own adb server on the usual port (5037). Android Studio, other phone-mirroring tools and the other cloud's own tools may start a second one and fight for it. Close them, or let them use the Hub's.

Allow automation on the phone as usual (open it → Details → Automation) before workflows and AI can act on it. See Connecting phones.

Keep it private. ADB gives full control of a phone. Never open an address to the whole internet; use the other cloud's own allow-list or key where it has one. The Hub only connects out to the address you give it.

Samsung Remote Test Lab ​

Samsung's free lab lets you reserve real Galaxy phones, and its Remote Debug Bridge (rdb) makes a reserved phone appear to your computer as if it were plugged in. Steps, from Samsung's guide:

  1. In the Remote Test Lab web client, reserve a phone, then choose Remote Debug Bridge → Connect. If rdb is not installed, download it from the pop-up and run it (rdb.exe on Windows).
  2. Press Connect in the rdb window; it changes to Disconnect when the link is up. Keep the window open.
  3. If a RSA dialog appears on the phone's screen, press Allow.
  4. Samsung says the phone then appears in Android Studio and to adb on your computer.

What we have not tested. Samsung's page does not show an adb connect address, and we have not yet run this with a Samsung account. If the phone is a normal adb device on your computer, the Hub's adb server should list it on its own (it uses the same default adb port); if it does not appear within a minute, close other adb programs and restart the Hub's adb from System. Free credits and session length change; look in your Samsung account.

Google Android Device Streaming ​

Android Device Streaming (part of Android Studio, using Firebase) gives you real Pixel and partner phones for a limited time each month, then billed by Google. Per Google's page:

  1. You need a Firebase project and a role that allows it (Editor or Owner, or the Firebase Test Lab Direct Access Admin role).
  2. Reserve and connect to a phone from Android Studio's Device Manager, or from the command line with android device remote.
  3. Once connected, Google says any tool that uses ADB works against the phone over an "ADB over SSL" connection.
  4. When you finish, choose Return and Erase Device to stop the clock.

What we have not tested. Google's page does not list the connection steps, ports or certificate setup, so we cannot say which address to give the Hub, or whether the phone shows up in the Hub's adb server without more setup. We have not tried it. If you do, tell us what worked.

Other clouds ​

Any cloud that gives you an ADB address or a tunnel program works the same way as in The general way. We have not tested each one and do not list them here. The same rules apply as on your own phones: human-only checks such as CAPTCHAs and sign-in codes stop and wait for you, and the app does not help hide that a phone is virtual or run many accounts.