DuoPlus CloudPhone Agent

Control and automate DuoPlus cloud phones using ADB broadcast commands.

For more information, visit DuoPlus Official Website.

Connecting Devices

Wireless Connection

CODEBLOCK0

All subsequent commands use -s <DEVICE_ID> to target a specific device.

Common Workflows

Launching an App

CODEBLOCK1

Analyzing the UI

Dump and pull the UI hierarchy to find element coordinates and attributes:

adb -s <DEVICE_ID> shell uiautomator dump /sdcard/view.xml && adb -s <DEVICE_ID> pull /sdcard/view.xml ./view.xml

Then grep for text or resource IDs to find bounds="[x1,y1][x2,y2]".

Interacting with Elements

All interactions are sent via the helper script as JSON commands:

• - Tap coordinate: INLINECODE2
• Tap element by text: INLINECODE3

- Optional params: resource_id, class_name, content_desc, element_order (0-based index)

• - Long press: INLINECODE8
• Double tap: INLINECODE9
• Type text: INLINECODE10

- Must tap the input field first to focus it

• - Keyboard key: INLINECODE11

- Supported keys: enter, delete, tab, escape, space

• - Swipe: INLINECODE12

- direction: up/down/left/right (required). Coordinates are optional.

• - Home: INLINECODE14
• Back: INLINECODE15
• Wait: INLINECODE16
• Wait for element: INLINECODE17
• End task (only when stuck): INLINECODE18

All action commands are fire-and-forget — they do NOT return results. Take a screenshot after each action to verify.

Visual Verification

Take a screenshot, compress with cwebp, and pull to local for analysis:
CODEBLOCK3

If cwebp is not available, use the PNG directly.

How Commands Work (Internal)

Commands are sent as Base64-encoded JSON via ADB broadcast. The helper script scripts/send_command.sh handles this automatically:

CODEBLOCK4

The script builds the full payload (tasktype, taskid, md5, etc.), Base64-encodes it, and sends via:
CODEBLOCK5

Typical Workflow

CODEBLOCK6

Tips

• - Coordinates: The coordinate system is 0-1000 relative (top-left=0,0, bottom-right=1000,1000), NOT pixels.
• Element matching: Use CLICKELEMENT (by text) when possible; fall back to CLICKCOORDINATE when text matching fails.
• Input: Must tap the input field first (CLICKCOORDINATE or CLICKELEMENT) to focus, then INPUTCONTENT.
• Submit: After typing, use KEYBOARDOPERATION(key="enter") to submit.
• Wait: Use sleep 1-3 between commands to allow the UI to update. Do NOT use shell sleep on the device.
• Swipe coordinates: Must use irregular integers, avoid round numbers (500, 800). Vary coordinates between consecutive swipes.