USB Android control
Let a bot inspect and operate a physically connected Android phone.
GlinkBot can expose a USB-connected Android device through its Phone Harness skill. A supported agent can inspect the screen, open apps, tap, type, swipe, scroll, and capture screenshots.
Requirements
- A physical Android device connected over USB
- USB debugging enabled on the device
- The computer trusted from the device's debugging prompt
- The packaged Android platform tools or a compatible local ADB installation
Phone access is a separate capability from desktop computer use. Keep the device unlocked and visible while testing, and review actions that may send messages, change accounts, or expose private content.
Screen and lock
A bot can turn the screen on and off. It never unlocks a PIN, pattern, or password lock: it asks you to unlock the phone.
Typing other languages
The bot types letters, digits, spaces, and _.,@- through Android's own input. For other text, such as Chinese, emoji, or +, install ADBKeyBoard on the phone and choose it as the keyboard. ADBKeyBoard shows no on-screen keyboard, so switch back to your usual keyboard when you type on the phone yourself. It also takes typing from any app on the phone, not only from GlinkBot, so use it only on a phone whose apps you trust.
With ADBKeyBoard 2.0 or later chosen as the keyboard, the bot can also empty a field before it types, for example to replace the words in a search box. It taps the field first. With another keyboard it has to remove old text one character at a time.
Some apps draw their own text box and do not tell the keyboard what it holds. The bot cannot empty such a box, so check the screen after it types there. ADBKeyBoard's older APK also restarts when asked to; the builds on its release page (v2.4-dev and newer) check for this.
GlinkBot documentation, reviewed for the 0.0.4 codebase. Public download availability can differ. Licenses and acknowledgments.