{"data":{"id":"246686","string_id":"vMFyKPnJ","status":"1","parent_id":"0","slug":"api-reference","order":"8","name":"API Reference","type":"1","cover":"","cover_alt":"","desc":null,"website":"","contact":"","seo_title":"","seo_keyword":"","seo_desc":"","author":"","published_time":"1734000077","add_time":"1733972394","update_time":"1788435685","corp_auth_id":"0","verify_code_auth_id":"0","editor_type":"1","tags":[],"child":[{"id":"246688","string_id":"IhmHZiGC","status":"1","parent_id":"246686","slug":"Introduction","order":"13","name":"Introduction","type":"2","cover":"","cover_alt":"","desc":null,"website":"","contact":"","seo_title":"","seo_keyword":"","seo_desc":"","share_switch":"0","share_code":"","author":"","published_time":"1734000078","add_time":"1733972471","update_time":"1789547295","corp_auth_id":"0","verify_code_auth_id":"0","editor_type":"2","file_type":"","auth_id":"[\"246688\", \"246686\"]","content":{"content_id":"246688","content":"## Preparation\nFirst, you need to go to the console's [\"Automation\" -> \"API\"](https:\/\/my.duoplus.net\/api) menu to obtain the API KEY. Then, use the `DuoPlus-API-Key` in the request header for all API requests to pass in the obtained API KEY.\n\n## Usage Limitations\n\nThe QPS limit for each interface is set to 1.\n\n## Request Domain\nDomain: https:\/\/openapi.duoplus.net\n\n## Request Method\nPOST\n\n## Request Headers\n\n| Parameter | Value | Description |\n| - | - | - |\n| Lang | zh | Set the interface interaction language, supports: zh, zh-TW, en, ru |\n| Content-Type | application\/json | All data is transmitted using JSON |\n| DuoPlus-API-Key | xx-xx-xx | API Key, obtained from the \"Automation\" -> \"[API](https:\/\/my.duoplus.net\/api)\" menu in the console |\n\n## Request Parameters\nUse JSON string to transmit\n```json\n{\"key\":\"value\"}\n```\n\n## Response Parameters\n| Parameter | Type | Description |\n| --- | --- | --- |\n| code | int | Response status code, 200 means normal; 401 requires re-login |\n| data | object | Content body |\n| message | string | Message, usually error information |\n\n## Pagination Description\n#### Pagination Request Parameters\n\n| Parameter | Type | Required | Description |\n| --- | --- | --- | --- |\n| page | int | No | Request page number, defaults to the first page if not provided |\n| pagesize | int | No | Number of items per page, defaults to 10 items\/page if not provided |\n\n#### Pagination Response Parameters\n> The following parameters are within the returned data object. Typically for lists, data contains a list and the following pagination parameters at the same level.\n\n| Parameter | Type | Required | Description |\n| --- | --- | --- | --- |\n| page | int | Yes | Page number |\n| pagesize | int | Yes | Number of items per page |\n| total | int | Yes | Total number of items |\n| total_page | int | Yes | Total number of pages |","pure_content":"Preparation\nFirst, you need to go to the console's \"Automation\" -> \"API\" menu to obtain the API KEY. Then, use the DuoPlus-API-Key in the request header for all API requests to pass in the obtained API KEY.\nUsage Limitations\nThe QPS limit for each interface is set to 1.\nRequest Domain\nDomain: https:\/\/openapi.duoplus.net\nRequest Method\nPOST\nRequest Headers\n\n\n\n Parameter\n Value\n Description\n\n\n\n\n Lang\n zh\n Set the interface interaction language, supports: zh, zh-TW, en, ru\n\n\n Content-Type\n application\/json\n All data is transmitted using JSON\n\n\n DuoPlus-API-Key\n xx-xx-xx\n API Key, obtained from the \"Automation\" -> \"API\" menu in the console\n\n\n\nRequest Parameters\nUse JSON string to transmit\n{\"key\":\"value\"}\n\nResponse Parameters\n\n\n\n Parameter\n Type\n Description\n\n\n\n\n code\n int\n Response status code, 200 means normal; 401 requires re-login\n\n\n data\n object\n Content body\n\n\n message\n string\n Message, usually error information\n\n\n\nPagination Description\nPagination Request Parameters\n\n\n\n Parameter\n Type\n Required\n Description\n\n\n\n\n page\n int\n No\n Request page number, defaults to the first page if not provided\n\n\n pagesize\n int\n No\n Number of items per page, defaults to 10 items\/page if not provided\n\n\n\nPagination Response Parameters\n\nThe following parameters are within the returned data object. Typically for lists, data contains a list and the following pagination parameters at the same level.\n\n\n\n\n Parameter\n Type\n Required\n Description\n\n\n\n\n page\n int\n Yes\n Page number\n\n\n pagesize\n int\n Yes\n Number of items per page\n\n\n total\n int\n Yes\n Total number of items\n\n\n total_page\n int\n Yes\n Total number of pages","is_draft":"0","editor_type":"2","file_path":"","add_time":"1733972471","update_time":"1734079363"},"pure_content":"Preparation\nFirst, you need to go to the console's \"Automation\" -> \"API\" menu to obtain the API KEY. Then, use the DuoPlus-API-Key in the request header for all API requests to pass in the obtained AP"},{"id":"359205","string_id":"QYtnJac7","status":"1","parent_id":"246686","slug":"cloudphone","order":"12","name":"Cloud Phone","type":"1","cover":"","cover_alt":"","desc":"","website":"","contact":"","seo_title":"","seo_keyword":"","seo_desc":"","share_switch":"0","share_code":"","author":"","published_time":"0","add_time":"1741585786","update_time":"1789547295","corp_auth_id":"0","verify_code_auth_id":"0","editor_type":"1","file_type":"","auth_id":"[\"359205\", \"246686\"]","pure_content":""},{"id":"696802","string_id":"8EvzVG2i","status":"1","parent_id":"246686","slug":"8EvzVG2i","order":"11","name":"Subscription Startup","type":"1","cover":"","cover_alt":"","desc":"","website":"","contact":"","seo_title":"","seo_keyword":"","seo_desc":"","share_switch":"0","share_code":"","author":"","published_time":"0","add_time":"1767857763","update_time":"1789547295","corp_auth_id":"0","verify_code_auth_id":"0","editor_type":"1","file_type":"","auth_id":"[\"696802\", \"246686\"]","pure_content":""},{"id":"359208","string_id":"3YNm5PDB","status":"1","parent_id":"246686","slug":"proxy","order":"10","name":"Proxy","type":"1","cover":"","cover_alt":"","desc":"","website":"","contact":"","seo_title":"","seo_keyword":"","seo_desc":"","share_switch":"0","share_code":"","author":"","published_time":"0","add_time":"1741585829","update_time":"1789547295","corp_auth_id":"0","verify_code_auth_id":"0","editor_type":"1","file_type":"","auth_id":"[\"359208\", \"246686\"]","pure_content":""},{"id":"692727","string_id":"4D2HCXVy","status":"1","parent_id":"246686","slug":"4D2HCXVy","order":"9","name":"CloudNumber","type":"1","cover":"","cover_alt":"","desc":"","website":"","contact":"","seo_title":"","seo_keyword":"","seo_desc":"","share_switch":"0","share_code":"","author":"","published_time":"0","add_time":"1767516171","update_time":"1789547295","corp_auth_id":"0","verify_code_auth_id":"0","editor_type":"1","file_type":"","auth_id":"[\"692727\", \"246686\"]","pure_content":""},{"id":"359209","string_id":"WT5xqgRj","status":"1","parent_id":"246686","slug":"group","order":"8","name":"Groups","type":"1","cover":"","cover_alt":"","desc":"","website":"","contact":"","seo_title":"","seo_keyword":"","seo_desc":"","share_switch":"0","share_code":"","author":"","published_time":"0","add_time":"1741585866","update_time":"1789547295","corp_auth_id":"0","verify_code_auth_id":"0","editor_type":"1","file_type":"","auth_id":"[\"359209\", \"246686\"]","pure_content":""},{"id":"359210","string_id":"skqsXJ3N","status":"1","parent_id":"246686","slug":"application","order":"7","name":"Application","type":"1","cover":"","cover_alt":"","desc":"","website":"","contact":"","seo_title":"","seo_keyword":"","seo_desc":"","share_switch":"0","share_code":"","author":"","published_time":"0","add_time":"1741585901","update_time":"1789547295","corp_auth_id":"0","verify_code_auth_id":"0","editor_type":"1","file_type":"","auth_id":"[\"359210\", \"359209\", \"246686\"]","pure_content":""},{"id":"615862","string_id":"av1zmeDR","status":"1","parent_id":"246686","slug":"av1zmeDR","order":"6","name":"Cloud Dirve Management","type":"1","cover":"","cover_alt":"","desc":"","website":"","contact":"","seo_title":"","seo_keyword":"","seo_desc":"","share_switch":"0","share_code":"","author":"","published_time":"1757590685","add_time":"1757590449","update_time":"1789547295","corp_auth_id":"0","verify_code_auth_id":"0","editor_type":"1","file_type":"","auth_id":"[\"615862\", \"246686\"]","pure_content":""},{"id":"680404","string_id":"hO3nyzTq","status":"1","parent_id":"246686","slug":"hO3nyzTq","order":"5","name":"Automation","type":"1","cover":"","cover_alt":"","desc":"","website":"","contact":"","seo_title":"","seo_keyword":"","seo_desc":"","share_switch":"0","share_code":"","author":"","published_time":"1766393803","add_time":"1765954986","update_time":"1789547295","corp_auth_id":"0","verify_code_auth_id":"0","editor_type":"1","file_type":"","auth_id":"[\"680404\", \"246686\"]","pure_content":""},{"id":"739811","string_id":"26sdmTG2","status":"1","parent_id":"246686","slug":"26sdmTG2","order":"4","name":"Team","type":"1","cover":"","cover_alt":"","desc":"","website":"","contact":"","seo_title":"","seo_keyword":"","seo_desc":"","share_switch":"0","share_code":"","author":"","published_time":"0","add_time":"1773136530","update_time":"1789547295","corp_auth_id":"0","verify_code_auth_id":"0","editor_type":"1","file_type":"","auth_id":"[\"739811\", \"246686\"]","pure_content":""},{"id":"632463","string_id":"vzJ9tq2O","status":"1","parent_id":"246686","slug":"How-to-develop-plugin-modules","order":"3","name":"How to develop plug-in modules","type":"2","cover":"","cover_alt":"","desc":null,"website":"","contact":"","seo_title":"","seo_keyword":"","seo_desc":"","share_switch":"0","share_code":"","author":"","published_time":"1760927854","add_time":"1760327840","update_time":"1789547295","corp_auth_id":"0","verify_code_auth_id":"0","editor_type":"2","file_type":"","auth_id":"[\"632463\", \"246686\"]","content":{"content_id":"632463","content":"### Module Plugin Usage Scenarios\n\nPrimarily used to inject custom code into specified applications in the cloud machine, allowing modifications to the Java layer or native layer.\n\n### Supported Features\n\nAutomatic injection of DEX files\n\nAutomatic injection of SO files\n\nBuilt-in Java layer Hook framework: LspLant\n\nBuilt-in native layer Hook framework: Dobby\n\n### Module Example Download\n\n[dplus_demo code](https:\/\/resource-wangsu.helplook.net\/docker_production\/baovvg\/article\/lbACLNnY\/attachments\/dplus_demo.zip)\n[dplus_demo](https:\/\/resource-wangsu.helplook.net\/docker_production\/wkpufm\/article\/KzlnnRh4\/attachments\/dplus_demo.apk)\n\n### Build Environment\n\nThis project currently uses:\n\n- Android Gradle Plugin: 8.6.0\n- Gradle Wrapper: 8.7\n- compileSdk \/ targetSdk: 34\n- minSdk: 29\n- CMake: 3.22.1\n- JDK: **21**\n\n> Important: build this project with **JDK 21**. If you use a newer JDK such as JDK 23, `.\/gradlew assembleDebug` may fail with:\n>\n> `Unsupported class file major version 67`\n\n### Environment Preparation\n\nIt is recommended to open and build this project with Android Studio, and install these components in advance:\n\n- Android SDK Platform 34\n- Android SDK Build-Tools\n- CMake 3.22.1\n- Android NDK\n- JDK 21\n\n### Download and Configure JDK 21\n\n#### Option 1: Download via Android Studio\n\n1. Open Android Studio.\n2. Go to `Settings` \/ `Preferences` -> `Build, Execution, Deployment` -> `Build Tools` -> `Gradle`.\n3. In `Gradle JDK`, select `Download JDK...`.\n4. Choose version `21`, download it, and apply the setting.\n\nIf you only build inside Android Studio, this is the simplest approach.\n\n#### Option 2: Install JDK 21 manually\n\nYou can also install OpenJDK 21 \/ Temurin 21 yourself and configure `JAVA_HOME`.\n\nExample for Linux \/ macOS:\n\n```bash\nexport JAVA_HOME=\/path\/to\/jdk-21\nexport PATH=$JAVA_HOME\/bin:$PATH\n\njava -version\n```\n\nAfter confirming the output contains `21`, run the build command.\n\nIf you use `zsh`, you can append the two environment variable lines above to `~\/.zshrc` to make them persistent.\n\nIf you do not want to change the system default JDK, you can also point Gradle to JDK 21 explicitly. Add this to `~\/.gradle\/gradle.properties` or the project's root `gradle.properties`:\n\n```properties\norg.gradle.java.home=\/path\/to\/jdk-21\n```\n\nThis lets Gradle use JDK 21 even when the terminal default Java version is not 21.\n\n### Build Instructions\n\n#### Build with Android Studio\n\n1. Open the project in Android Studio.\n2. Make sure `Gradle JDK` is set to **JDK 21**.\n3. Wait for Gradle Sync to finish.\n4. Run `Build` -> `Make Project`, or directly build `assembleDebug`.\n\n#### Build from the command line\n\nFirst, make sure the current terminal is using Java 21:\n\n```bash\njava -version\n.\/gradlew -version\n```\n\nThen run:\n\n```bash\n.\/gradlew assembleDebug\n```\n\nAfter a successful build, the APK is generated at:\n\n```bash\napp\/build\/outputs\/apk\/debug\/app-debug.apk\n```\n\n### Common Issue\n\n#### 1. `Unsupported class file major version 67`\n\nCause: Gradle is running with the wrong JDK version, usually JDK 23 instead of JDK 21.\n\nFix:\n\n```bash\nexport JAVA_HOME=\/path\/to\/jdk-21\nexport PATH=$JAVA_HOME\/bin:$PATH\njava -version\n.\/gradlew assembleDebug\n```\n\nIf you build in Android Studio, switch `Gradle JDK` to JDK 21.\n\nIf you keep multiple JDKs installed and do not want to switch frequently, you can also use the `org.gradle.java.home` setting above to pin Gradle to JDK 21.\n\n### Module Installation\n\nOpen the project in Android Studio. After compilation, obtain the module file app-debug.apk.\n\nUpload this file to the cloud machine, for example, to the path \/sdcard\/Download\/app-debug.apk.\n\nUse the following commands for installation and viewing:\n\n```\n\/\/ First connect to the cloud machine\nadb connect xx.xx.xx.xx\n\n\/\/ Enter the cloud machine terminal\nadb shell\n\n\/\/ Then install the module\ndplus install patch:\/sdcard\/Download\/app-debug.apk\n\n\/\/ After successful installation, view the module\ndplus dump\n\n\/\/ Uninstall and delete the module by module name\ndplus uninstall dplus_demo\n```\n\n### Module Development Introduction\n\nThe module source code structure is as shown in the figure below.\n\n![](https:\/\/resource-wangsu.helplook.net\/docker_production\/wkpufm\/article\/Jnu4zw3n\/68ec705330f5a.png)\n\nThe config.json file is used to configure the module.\n\nnative-lib.cpp implements examples of Dobby hooks.\n\nEntry.java serves as the entry point for Java layer hooks.\n\n### Config Configuration Explanation\n\nThis file is primarily used to describe the module and guide the injection process. Sample data is as follows:\n\n```\n{\n \"name\": \"dplus_demo\", \/\/ Module name, used during uninstallation\n \"package\":\"com.example.dplus_demo\", \/\/ Module package name\n \"desc\": \"module\", \/\/ Module description\n \"type\": \"user\", \/\/ Module type, mainly \"system\" or \"user\"\n \"libs\": \"libdplus_demo.so\", \/\/ SO files to inject; can be omitted or configured with multiple entries separated by ';'\n \"pattern\": [\n \"com.android.settings\" \/\/ Package names where the module takes effect\n ]\n}\n```\n\n### Dobby Example\n\nThe following demonstrates a simple hook on the openat function to output logs:\n\n```\nint (*source_openat)(int fd, const char *path, int oflag, int mode) = nullptr;\n\nint MyOpenAt(int fd, const char *pathname, int flags, int mode) {\n LOGI(\"MyOpenAt pathname %s\",pathname);\n return source_openat(fd, pathname, flags, mode);\n}\n\nvoid HookOpenAt() {\n \/\/ Resolve function address\n void *__openat =\n DobbySymbolResolver(\"libc.so\", \"__openat\");\n\n if (__openat == nullptr) {\n LOGI(\"__openat null \");\n return;\n }\n\n LOGI(\"Got __openat address \");\n \n \/\/ Replace original function with Dobby\n if (DobbyHook((void *) __openat,\n (void *) MyOpenAt,\n (void **) &source_openat) == 0) {\n LOGI(\"DobbyHook __openat success\");\n }\n}\n\njint JNICALL JNI_OnLoad(JavaVM *vm, void *reserved) {\n\n LOGI(\"Test JNI_OnLoad starting load\");\n HookOpenAt();\n return JNI_VERSION_1_6;\n}\n\n```\n\n### Java Layer Example\n\nThe `init` function serves as an entry point after the application starts. Execute relevant logic here. The LspLant-related code has been slightly modified, so some classes and functions may not use their original names.\n\n```\npublic class Entry {\n\n public String TAG=\"demo_Entry\";\n\n public void init(Application app){\n DPLog.i(TAG,\"enter init\");\n LSPHelpers.findAndHookMethod(\"java.util.HashMap\", app.getClassLoader(), \"put\",Object.class,Object.class, new LSP_MethodH() {\n @Override\n protected void beforeHookedMethod(MethodHookParam param) throws Throwable {\n super.beforeHookedMethod(param);\n Log.i(TAG,\"enter HashMap.put key:\"+param.args[0]+\",value:\"+param.args[1]);\n }\n\n @Override\n protected void afterHookedMethod(MethodHookParam param) throws Throwable {\n super.afterHookedMethod(param);\n Log.i(TAG,\"leave HashMap.put\");\n }\n });\n }\n\n}\n```\n\n### Effects After Module Injection\n\nThis module tests the Settings application. When the Settings app is closed and reopened, the relevant logs are as shown in the figure below.\n\n![](https:\/\/resource-wangsu.helplook.net\/docker_production\/wkpufm\/article\/Jnu4zw3n\/68ec7375b7f5f.png)","pure_content":"Module Plugin Usage Scenarios\nPrimarily used to inject custom code into specified applications in the cloud machine, allowing modifications to the Java layer or native layer.\nSupported Features\nAutomatic injection of DEX files\nAutomatic injection of SO files\nBuilt-in Java layer Hook framework: LspLant\nBuilt-in native layer Hook framework: Dobby\nModule Example Download\ndplus_demo code\ndplus_demo\nBuild Environment\nThis project currently uses:\n\nAndroid Gradle Plugin: 8.6.0\nGradle Wrapper: 8.7\ncompileSdk \/ targetSdk: 34\nminSdk: 29\nCMake: 3.22.1\nJDK: 21\n\n\n\nImportant: build this project with JDK 21. If you use a newer JDK such as JDK 23, .\/gradlew assembleDebug may fail with:\nUnsupported class file major version 67\n\nEnvironment Preparation\nIt is recommended to open and build this project with Android Studio, and install these components in advance:\n\nAndroid SDK Platform 34\nAndroid SDK Build-Tools\nCMake 3.22.1\nAndroid NDK\nJDK 21\n\nDownload and Configure JDK 21\nOption 1: Download via Android Studio\n\nOpen Android Studio.\nGo to Settings \/ Preferences -> Build, Execution, Deployment -> Build Tools -> Gradle.\nIn Gradle JDK, select Download JDK....\nChoose version 21, download it, and apply the setting.\n\nIf you only build inside Android Studio, this is the simplest approach.\nOption 2: Install JDK 21 manually\nYou can also install OpenJDK 21 \/ Temurin 21 yourself and configure JAVA_HOME.\nExample for Linux \/ macOS:\nexport JAVA_HOME=\/path\/to\/jdk-21\nexport PATH=$JAVA_HOME\/bin:$PATH\n\njava -version\n\nAfter confirming the output contains 21, run the build command.\nIf you use zsh, you can append the two environment variable lines above to ~\/.zshrc to make them persistent.\nIf you do not want to change the system default JDK, you can also point Gradle to JDK 21 explicitly. Add this to ~\/.gradle\/gradle.properties or the project's root gradle.properties:\norg.gradle.java.home=\/path\/to\/jdk-21\n\nThis lets Gradle use JDK 21 even when the terminal default Java version is not 21.\nBuild Instructions\nBuild with Android Studio\n\nOpen the project in Android Studio.\nMake sure Gradle JDK is set to JDK 21.\nWait for Gradle Sync to finish.\nRun Build -> Make Project, or directly build assembleDebug.\n\nBuild from the command line\nFirst, make sure the current terminal is using Java 21:\njava -version\n.\/gradlew -version\n\nThen run:\n.\/gradlew assembleDebug\n\nAfter a successful build, the APK is generated at:\napp\/build\/outputs\/apk\/debug\/app-debug.apk\n\nCommon Issue\n1. Unsupported class file major version 67\nCause: Gradle is running with the wrong JDK version, usually JDK 23 instead of JDK 21.\nFix:\nexport JAVA_HOME=\/path\/to\/jdk-21\nexport PATH=$JAVA_HOME\/bin:$PATH\njava -version\n.\/gradlew assembleDebug\n\nIf you build in Android Studio, switch Gradle JDK to JDK 21.\nIf you keep multiple JDKs installed and do not want to switch frequently, you can also use the org.gradle.java.home setting above to pin Gradle to JDK 21.\nModule Installation\nOpen the project in Android Studio. After compilation, obtain the module file app-debug.apk.\nUpload this file to the cloud machine, for example, to the path \/sdcard\/Download\/app-debug.apk.\nUse the following commands for installation and viewing:\n\/\/ First connect to the cloud machine\nadb connect xx.xx.xx.xx\n\n\/\/ Enter the cloud machine terminal\nadb shell\n\n\/\/ Then install the module\ndplus install patch:\/sdcard\/Download\/app-debug.apk\n\n\/\/ After successful installation, view the module\ndplus dump\n\n\/\/ Uninstall and delete the module by module name\ndplus uninstall dplus_demo\n\nModule Development Introduction\nThe module source code structure is as shown in the figure below.\n\nThe config.json file is used to configure the module.\nnative-lib.cpp implements examples of Dobby hooks.\nEntry.java serves as the entry point for Java layer hooks.\nConfig Configuration Explanation\nThis file is primarily used to describe the module and guide the injection process. Sample data is as follows:\n{\n \"name\": \"dplus_demo\", \/\/ Module name, used during uninstallation\n \"package\":\"com.example.dplus_demo\", \/\/ Module package name\n \"desc\": \"module\", \/\/ Module description\n \"type\": \"user\", \/\/ Module type, mainly \"system\" or \"user\"\n \"libs\": \"libdplus_demo.so\", \/\/ SO files to inject; can be omitted or configured with multiple entries separated by ';'\n \"pattern\": [\n \"com.android.settings\" \/\/ Package names where the module takes effect\n ]\n}\n\nDobby Example\nThe following demonstrates a simple hook on the openat function to output logs:\nint (*source_openat)(int fd, const char *path, int oflag, int mode) = nullptr;\n\nint MyOpenAt(int fd, const char *pathname, int flags, int mode) {\n LOGI(\"MyOpenAt pathname %s\",pathname);\n return source_openat(fd, pathname, flags, mode);\n}\n\nvoid HookOpenAt() {\n \/\/ Resolve function address\n void *__openat =\n DobbySymbolResolver(\"libc.so\", \"__openat\");\n\n if (__openat == nullptr) {\n LOGI(\"__openat null \");\n return;\n }\n\n LOGI(\"Got __openat address \");\n \n \/\/ Replace original function with Dobby\n if (DobbyHook((void *) __openat,\n (void *) MyOpenAt,\n (void **) &source_openat) == 0) {\n LOGI(\"DobbyHook __openat success\");\n }\n}\n\njint JNICALL JNI_OnLoad(JavaVM *vm, void *reserved) {\n\n LOGI(\"Test JNI_OnLoad starting load\");\n HookOpenAt();\n return JNI_VERSION_1_6;\n}\n\n\nJava Layer Example\nThe init function serves as an entry point after the application starts. Execute relevant logic here. The LspLant-related code has been slightly modified, so some classes and functions may not use their original names.\npublic class Entry {\n\n public String TAG=\"demo_Entry\";\n\n public void init(Application app){\n DPLog.i(TAG,\"enter init\");\n LSPHelpers.findAndHookMethod(\"java.util.HashMap\", app.getClassLoader(), \"put\",Object.class,Object.class, new LSP_MethodH() {\n @Override\n protected void beforeHookedMethod(MethodHookParam param) throws Throwable {\n super.beforeHookedMethod(param);\n Log.i(TAG,\"enter HashMap.put key:\"+param.args[0]+\",value:\"+param.args[1]);\n }\n\n @Override\n protected void afterHookedMethod(MethodHookParam param) throws Throwable {\n super.afterHookedMethod(param);\n Log.i(TAG,\"leave HashMap.put\");\n }\n });\n }\n\n}\n\nEffects After Module Injection\nThis module tests the Settings application. When the Settings app is closed and reopened, the relevant logs are as shown in the figure below.","is_draft":"0","editor_type":"2","file_path":"","add_time":"1760327840","update_time":"1776851338"},"pure_content":"Module Plugin Usage Scenarios\nPrimarily used to inject custom code into specified applications in the cloud machine, allowing modifications to the Java layer or native layer.\nSupported Features\nAutoma"},{"id":"607962","string_id":"GcajyAfB","status":"1","parent_id":"246686","slug":"How-to-Pass-Google-Verification","order":"2","name":"How to Pass Google Verification","type":"2","cover":"","cover_alt":"","desc":null,"website":"","contact":"","seo_title":"","seo_keyword":"","seo_desc":"","share_switch":"0","share_code":"","author":"","published_time":"1757052340","add_time":"1756877894","update_time":"1789547295","corp_auth_id":"0","verify_code_auth_id":"0","editor_type":"2","file_type":"","auth_id":"[\"607962\", \"246686\"]","content":{"content_id":"607962","content":"### What is Google Three-Level Verification\n\nGoogle Three-Level Verification typically refers to the device integrity checking mechanism in Google's Play Integrity API, used to verify the integrity of Android devices to ensure the security of both the device and its applications.\n\nThe Play Integrity API evaluates whether a device meets three levels of integrity requirements: **Basic Integrity**, **Device Integrity**, and **Strong Integrity**.\n\n1. Basic Integrity\nThe most fundamental level of integrity check, based on software verification, ensuring the device runs an untampered Android system with no obvious signs of system compromise.\n\n3. Device Integrity\nA stricter check than Basic Integrity, verifying whether the device is Google-certified and running certified Android firmware.\n\n\n5. Strong Integrity\nThe highest level of integrity check, relying on hardware-backed verification (e.g., Trusted Execution Environment, TEE), ensuring the device runs an untampered official Android system.\n\n### Why is Google Verification Necessary?\n\nMost overseas applications use Google's detection methods to verify devices, which reduces development costs for countermeasures and enhances application security. By passing Google\u2019s three-level verification, users can normally use most applications that rely solely on Google\u2019s detection mechanisms.\n\n### How to Check the Current Google Verification Status\n\nYou can test the status by installing apps such as [Play Integrity API Check](https:\/\/play.google.com\/store\/apps\/details?id=gr.nikolasspyr.integritycheck) or [TB Checker](https:\/\/play.google.com\/store\/apps\/details?id=krypton.tbsafetychecker).\n\nThese apps can be searched and installed directly from the platform\u2019s app store. If you encounter crashes, it may be due to an outdated version of the detection app; downloading and installing from Google Play should resolve the issue.\n\nBy default, cloud devices pass Basic Integrity (except for Android 15, which requires keybox.xml to pass verification), as shown in the images below:\n\n![](https:\/\/resource-wangsu.helplook.net\/docker_production\/wkpufm\/article\/hAK8ZvtK\/68b538833bc21.png)\n\n![](https:\/\/resource-wangsu.helplook.net\/docker_production\/wkpufm\/article\/hAK8ZvtK\/68b538c93f46a.png)\n\n### What is keybox.xml\nThe keybox.xml is a file containing device key information, typically associated with the Android device's Trusted Execution Environment (TEE). It stores cryptographic keys (attestation keys) and other metadata used to prove the device\u2019s identity and integrity. It is primarily used to support Strong Integrity checks.\n\nGoogle servers verify the keys and certificates in the keybox.xml to confirm whether the device is unrooted, has a locked bootloader, and is running certified Android firmware.\n\n### How to Obtain keybox.xml\n\nThere are multiple channels to obtain keybox.xml, and the validity of the file varies depending on the source. For instance, publicly available keybox.xml files may have a short validity period due to widespread testing, potentially becoming invalid within days or weeks.\n\n1. For simple self-testing: You can extract it from open-source projects, such as [TrickyStore](https:\/\/github.com\/qwq233\/TrickyStore). After flashing it onto a real device, you can extract the keybox.xml file from the path \/data\/adb\/tricky_store\/keybox.xml for use. Alternatively.\n you can download files provided by certain websites or modules, such as [root.zip](https:\/\/hishi7.fun\/keybox\/root.zip).\n2. For large-scale use: Purchase channels can be found on Telegram.\n3. For stable and large-scale use: Collaborate with phone manufacturers, as their keybox.xml files are more stable and long-lasting.\n\n### How to Pass Google Verification\n\nCurrently, passing the three-level verification requires the use of a keybox.xml certificate file. This certificate needs to be uploaded to the \/data\/misc\/google directory. \n\n![](https:\/\/resource-wangsu.helplook.net\/docker_production\/baovvg\/article\/GcajyAfB\/69fc3e8ae89ad.png)\n\nChange directory\n\n![](https:\/\/resource-wangsu.helplook.net\/docker_production\/baovvg\/article\/GcajyAfB\/69fc3ead94bea.png)\n\nAlternatively, you can upload the file to the specified location using ADB commands:\n```\n# Step 1: Connect to adb, refer to the tutorial: https:\/\/help.duoplus.net\/docs\/adb\nadb connect xx.xx.xx.xx\n# Step 2: Push the 'keybox.xml' file to the cloud phone (ensure the filename is 'keybox.xml')\n## Windows Example\nadb push C:\\Users\\YourUsername\\Documents\\keybox.xml \/data\/misc\/google\/\n## macOS\/Linux Example\nadb push ~\/tools\/android\/google\/keybox.xml \/data\/misc\/google\/\n# Step 3: Restart the cloud phone, refer to:https:\/\/help.duoplus.net\/docs\/Restart\n```\n\nAfter rebooting the cloud device, check again to see the results, as shown below:\n\n![](https:\/\/resource-wangsu.helplook.net\/docker_production\/wkpufm\/article\/hAK8ZvtK\/68b53aae97d73.png)\n\n![](https:\/\/resource-wangsu.helplook.net\/docker_production\/wkpufm\/article\/hAK8ZvtK\/68b5407233a3b.png)","pure_content":"What is Google Three-Level Verification\nGoogle Three-Level Verification typically refers to the device integrity checking mechanism in Google's Play Integrity API, used to verify the integrity of Android devices to ensure the security of both the device and its applications.\nThe Play Integrity API evaluates whether a device meets three levels of integrity requirements: Basic Integrity, Device Integrity, and Strong Integrity.\n\n\nBasic Integrity\nThe most fundamental level of integrity check, based on software verification, ensuring the device runs an untampered Android system with no obvious signs of system compromise.\n\n\nDevice Integrity\nA stricter check than Basic Integrity, verifying whether the device is Google-certified and running certified Android firmware.\n\n\nStrong Integrity\nThe highest level of integrity check, relying on hardware-backed verification (e.g., Trusted Execution Environment, TEE), ensuring the device runs an untampered official Android system.\n\n\nWhy is Google Verification Necessary?\nMost overseas applications use Google's detection methods to verify devices, which reduces development costs for countermeasures and enhances application security. By passing Google\u2019s three-level verification, users can normally use most applications that rely solely on Google\u2019s detection mechanisms.\nHow to Check the Current Google Verification Status\nYou can test the status by installing apps such as Play Integrity API Check or TB Checker.\nThese apps can be searched and installed directly from the platform\u2019s app store. If you encounter crashes, it may be due to an outdated version of the detection app; downloading and installing from Google Play should resolve the issue.\nBy default, cloud devices pass Basic Integrity (except for Android 15, which requires keybox.xml to pass verification), as shown in the images below:\n\n\nWhat is keybox.xml\nThe keybox.xml is a file containing device key information, typically associated with the Android device's Trusted Execution Environment (TEE). It stores cryptographic keys (attestation keys) and other metadata used to prove the device\u2019s identity and integrity. It is primarily used to support Strong Integrity checks.\nGoogle servers verify the keys and certificates in the keybox.xml to confirm whether the device is unrooted, has a locked bootloader, and is running certified Android firmware.\nHow to Obtain keybox.xml\nThere are multiple channels to obtain keybox.xml, and the validity of the file varies depending on the source. For instance, publicly available keybox.xml files may have a short validity period due to widespread testing, potentially becoming invalid within days or weeks.\n\nFor simple self-testing: You can extract it from open-source projects, such as TrickyStore. After flashing it onto a real device, you can extract the keybox.xml file from the path \/data\/adb\/tricky_store\/keybox.xml for use. Alternatively.\nyou can download files provided by certain websites or modules, such as root.zip.\nFor large-scale use: Purchase channels can be found on Telegram.\nFor stable and large-scale use: Collaborate with phone manufacturers, as their keybox.xml files are more stable and long-lasting.\n\nHow to Pass Google Verification\nCurrently, passing the three-level verification requires the use of a keybox.xml certificate file. This certificate needs to be uploaded to the \/data\/misc\/google directory.\n\nChange directory\n\nAlternatively, you can upload the file to the specified location using ADB commands:\n# Step 1: Connect to adb, refer to the tutorial: https:\/\/help.duoplus.net\/docs\/adb\nadb connect xx.xx.xx.xx\n# Step 2: Push the 'keybox.xml' file to the cloud phone (ensure the filename is 'keybox.xml')\n## Windows Example\nadb push C:\\Users\\YourUsername\\Documents\\keybox.xml \/data\/misc\/google\/\n## macOS\/Linux Example\nadb push ~\/tools\/android\/google\/keybox.xml \/data\/misc\/google\/\n# Step 3: Restart the cloud phone, refer to:https:\/\/help.duoplus.net\/docs\/Restart\n\nAfter rebooting the cloud device, check again to see the results, as shown below:","is_draft":"0","editor_type":"2","file_path":"","add_time":"1756877894","update_time":"1778138831"},"pure_content":"What is Google Three-Level Verification\nGoogle Three-Level Verification typically refers to the device integrity checking mechanism in Google's Play Integrity API, used to verify the integrity of Andr"},{"id":"368885","string_id":"TiusNsVf","status":"1","parent_id":"246686","slug":"best-practices","order":"1","name":"Best Practices","type":"1","cover":"","cover_alt":"","desc":"","website":"","contact":"","seo_title":"","seo_keyword":"","seo_desc":"","share_switch":"0","share_code":"","author":"","published_time":"0","add_time":"1741851559","update_time":"1789547295","corp_auth_id":"0","verify_code_auth_id":"0","editor_type":"1","file_type":"","auth_id":"[\"368885\", \"246686\"]","pure_content":""},{"id":"949585","string_id":"6ow735Hl","status":"1","parent_id":"246686","slug":"AIControlled-Cloud-Phone-API","order":"0","name":"AI-Controlled Cloud Phone API","type":"2","cover":"","cover_alt":"","desc":null,"website":"","contact":"","seo_title":"","seo_keyword":"","seo_desc":"","share_switch":"0","share_code":"","author":"","published_time":"1790573934","add_time":"1790236052","update_time":"1791949398","corp_auth_id":"0","verify_code_auth_id":"0","editor_type":"2","file_type":"","auth_id":"[\"949585\", \"246686\"]","content":{"content_id":"949585","content":"## DuoPlus Cloud Phone Automation Control API\n> This API provides a service exposed from within the cloud phone; it allows for direct control of the cloud phone and the execution of automated operations, such as: Get the Screen and UI Elements\u3001Tap and Long Press\u3001Text Input and Keyboard\u3001Swipe and Scroll\u3001App and Page Navigation\u3001Wait and Read Elements\u3001etc.\n\nPrerequisites: Get an API Key from Automation > API in the DuoPlus console. The target phone must be running (`status == 1`) with HTTP enabled (`http_status` is `1` or `\"1\"`). If it is stopped, start it in the console or via the platform power-on API; this document does not cover that endpoint. The Gateway uses the same API Key as its Bearer Token. Device-side authentication must be provisioned to match it, or the Gateway may return `401`.\n\n## 1. Get the Cloud Phone IP, Region, and Automation Support Status\n\nBefore calling the HTTP Gateway, use the platform `list` endpoint to obtain the target cloud phone's `ip` and `region`, and confirm that `status == 1` and `http_status` is `1`.\n\n### 1.1 Endpoint\n\n```text\nPOST https:\/\/openapi.duoplus.net\/api\/v1\/cloudPhone\/list\n```\n\nRequest headers:\n\n```http\nContent-Type: application\/json\nLang: zh\nDuoPlus-API-Key: \n```\n\n### 1.2 Request Parameters\n\nQuery by exact cloud phone ID:\n\n```json\n{\n \"image_id\": [\"IMAGE_ID\"],\n \"page\": 1,\n \"pagesize\": 100\n}\n```\n\nYou can also query by name:\n\n```json\n{\n \"name\": \"phone-name\",\n \"page\": 1,\n \"pagesize\": 100\n}\n```\n\n| Parameter | Required | Description |\n|---|---:|---|\n| `page` | No | Page number, starting at `1`; defaults to page 1 |\n| `pagesize` | No | Number of items per page; maximum `100`, default `10` |\n| `image_id` | No | Array of cloud phone IDs; an exact ID is recommended |\n| `name` | No | Cloud phone name; names may not be unique |\n| `link_status` | No | Array of connection statuses |\n| `group_id` | No | Group ID |\n| `proxy_id` | No | Proxy ID |\n\n### 1.3 Response Fields Required for Automation\n\nExample response envelope:\n\n```json\n{\n \"code\": 200,\n \"message\": \"success\",\n \"data\": {\n \"list\": [\n {\n \"id\": \"IMAGE_ID\",\n \"name\": \"phone-name\",\n \"status\": 1,\n \"ip\": \"10.0.0.10\",\n \"region\": \"sg\",\n \"http_status\": 1\n }\n ],\n \"total_page\": 1\n }\n}\n```\n\n> This example shows only the fields needed for automation. The server may return additional device information.\n\n| Field | Purpose |\n|---|---|\n| `data.list[].id` | Cloud phone ID, used to confirm that the correct device was selected |\n| `data.list[].status` | `1` means the cloud phone is running; handle other states first |\n| `data.list[].ip` | Value of the Gateway `CloudIP` request header |\n| `data.list[].region` | Value of the Gateway `Region` request header; use the selected phone's returned value |\n| `data.list[].http_status` | `1`\/`\"1\"` means HTTP is enabled; `0`\/`\"0\"` means it is disabled |\n| `data.total_page` | Total number of pages; iterate through all pages when not querying by exact ID |\n\nSuccess requires both a successful HTTP request and a top-level response `code == 200`.\n\n### 1.4 cURL Example\n\n```bash\ncurl -sS 'https:\/\/openapi.duoplus.net\/api\/v1\/cloudPhone\/list' \\\n -H 'Content-Type: application\/json' \\\n -H 'Lang: zh' \\\n -H \"DuoPlus-API-Key: $DUOPLUS_API_KEY\" \\\n --data '{\"image_id\":[\"IMAGE_ID\"],\"page\":1,\"pagesize\":100}'\n```\n\nVerify the matching item's `id`, then extract:\n\n```text\nCloudIP = matched_phone.ip\nRegion = matched_phone.region\n```\n\nCall the automation Gateway only when `status == 1` and `String(http_status) == \"1\"`. A nonempty `ip` does not mean automation is enabled. When searching by name, read every page indicated by `total_page`; use the ID to resolve duplicate names. The platform OpenAPI limit is 1 QPS per endpoint, including pagination requests.\n\n## 2. Automation Endpoint\n\nSend all automation operations to:\n\n```text\nPOST https:\/\/agent-gateway.duoplus.net\/agent-command\n```\n\n```http\nContent-Type: application\/json\nAuthorization: Bearer \nRegion: \nCloudIP: \n```\n\n| Header | Description |\n|---|---|\n| `Authorization` | Gateway authentication, in the form `Bearer ` |\n| `Region` | The target phone's `region` returned by `list` |\n| `CloudIP` | Cloud phone private IP address |\n\nThe cloud phone must be running with HTTP enabled. If the Gateway returns `401`, check the API Key and device authentication configuration rather than retrying blindly. Replace the example region and IP in the Section 13 cURL commands with the values returned for the target phone.\n\n## 3. Common Request Model\n\n| `operation` | Purpose |\n|---|---|\n| `health` | Check Gateway\/backend health |\n| `ready` | Check whether the automation executor is ready |\n| `submit` | Get the screen\/UI or perform a UI action |\n| `query` | Query a retained command result |\n| `stop` | Stop a running or stuck task |\n\nGeneral request for an action:\n\n```json\n{\n \"operation\": \"submit\",\n \"command_id\": \"click-element-1730000000000-a1b2c3d4\",\n \"task_id\": \"click-element-task-1730000000000-a1b2c3d4\",\n \"action\": \"execute\",\n \"payload\": {\n \"task_type\": \"ai\",\n \"task_id\": \"click-element-task-1730000000000-a1b2c3d4\",\n \"action\": \"execute\",\n \"action_name\": \"CLICK_ELEMENT\",\n \"params\": {\n \"text\": \"Search\",\n \"wait_after\": 500\n }\n }\n}\n```\n\n- `command_id` and `task_id` should be unique.\n- Use uppercase action names for `action_name`.\n- Put action parameters in `payload.params`.\n- You may add a Unix timestamp in milliseconds as a top-level `deadline_at`.\n- A synchronous action can take up to approximately 300 seconds; set the client timeout to approximately 310 seconds.\n\nThe `params` for any action may include:\n\n| Parameter | Description |\n|---|---|\n| `wait_before` | Delay before the action, in milliseconds |\n| `wait_after` | Delay after the action, in milliseconds; `500-1500` is recommended for navigation\/loading |\n\n## 4. Health and Readiness Checks\n\nHealth check:\n\n```json\n{\"operation\":\"health\"}\n```\n\nReadiness check:\n\n```json\n{\"operation\":\"ready\"}\n```\n\nThe executor is ready when the response has `executor == \"ready\"` or `ready == true`. On `503` or `NOT_READY`, continue polling within the startup timeout.\n\n## 5. Get the Screen and UI Elements\n\n### 5.1 Request\n\n```json\n{\n \"operation\": \"submit\",\n \"command_id\": \"ui-state-1730000000000-a1b2c3d4\",\n \"task_id\": \"ui-state-task-1730000000000-a1b2c3d4\",\n \"action\": \"get_ui_state\",\n \"payload\": {\n \"task_type\": \"ai\",\n \"task_id\": \"ui-state-task-1730000000000-a1b2c3d4\",\n \"action\": \"get_ui_state\",\n \"lang\": \"zh\"\n }\n}\n```\n\n### 5.2 Parse the Response\n\n`result_json` is a JSON string and must be parsed separately:\n\n```javascript\nconst outer = await response.json();\nconst result = JSON.parse(outer.result_json);\n```\n\nThe parsed object may contain:\n\n- `success`: whether the action succeeded;\n- a UI element tree, used to locate controls by text, resource ID, content description, and other attributes;\n- `screenshot`: a Base64-encoded image of the current screen.\n\nDecode the screenshot:\n\n```javascript\nconst encoded = result.screenshot.replace(\/^data:[^,]+,\/, \"\");\nconst bytes = Buffer.from(encoded, \"base64\");\n```\n\nRead the UI before the first action. Read it again after every click, input, swipe, or navigation action to verify the actual screen change.\n\n## 6. Tap and Long Press\n\n### 6.1 Tap an Element: `CLICK_ELEMENT`\n\n```json\n{\"text\":\"Continue\",\"wait_after\":800}\n```\n\n| Parameter | Description |\n|---|---|\n| `resource_id` | Android resource ID; usually the most stable selector |\n| `content_desc` | Accessibility content description |\n| `text` | Displayed element text |\n| `class_name` | Android view class name |\n| `element_order` | Zero-based index when multiple elements match |\n\n```json\n{\"resource_id\":\"com.example:id\/login\"}\n```\n\n```json\n{\"content_desc\":\"Search\"}\n```\n\n```json\n{\"text\":\"Item\",\"element_order\":1}\n```\n\nPrefer `resource_id`, then `content_desc`\/`text`, then coordinates.\n\n### 6.2 Long Press an Element: `LONG_ELEMENT`\n\n```json\n{\"text\":\"Message\",\"duration\":1200}\n```\n\nUse the same selector fields as `CLICK_ELEMENT`. `duration` is in milliseconds.\n\n### 6.3 Coordinate Actions\n\nTap with `CLICK_COORDINATE`:\n\n```json\n{\"x\":500,\"y\":420,\"wait_after\":500}\n```\n\nLong press with `LONG_COORDINATE`:\n\n```json\n{\"x\":500,\"y\":420,\"duration\":1200}\n```\n\nDouble tap with `DOUBLE_TAP_COORDINATE`:\n\n```json\n{\"x\":500,\"y\":420}\n```\n\nCoordinates are relative values in the range `0..1000`, with `(0,0)` at the top left and `(1000,1000)` at the bottom right:\n\n```text\nrelative_x = round(pixel_x \/ screenshot_width * 1000)\nrelative_y = round(pixel_y \/ screenshot_height * 1000)\n```\n\nTake a fresh screenshot immediately before a coordinate action and use the target's center. Do not reuse old coordinates after a page transition or rotation.\n\n## 7. Text Input and Keyboard\n\n### 7.1 Enter Text: `INPUT_CONTENT`\n\n```json\n{\"content\":\"hello world\",\"clear_first\":true}\n```\n\nFocus the input field first: get the UI, tap the input field, call `INPUT_CONTENT`, send Enter if needed, and get the UI again to verify the result.\n\n### 7.2 Keyboard: `KEYBOARD_OPERATION`\n\n```json\n{\"key\":\"enter\"}\n```\n\nSupported keys: `enter`, `delete`, `tab`, `escape`, and `space`.\n\n## 8. Swipe and Scroll\n\nAction name: `SLIDE_PAGE`.\n\nDefault gesture:\n\n```json\n{\"direction\":\"up\",\"wait_after\":600}\n```\n\nSupported directions: `up`, `down`, `left`, and `right`. To scroll down through content, swipe your finger upward and use `up`.\n\nCustom gesture path:\n\n```json\n{\n \"direction\": \"up\",\n \"start_x\": 520,\n \"start_y\": 780,\n \"end_x\": 500,\n \"end_y\": 260,\n \"wait_after\": 600\n}\n```\n\nTry the default gesture first and reread the screen after every swipe. If it has no effect, adjust the path slightly; generally try the same target no more than three times.\n\n## 9. App and Page Navigation\n\nOpen an app with `OPEN_APP`:\n\n```json\n{\"package_name\":\"com.android.settings\",\"wait_after\":1200}\n```\n\nGo to the home screen with `GO_TO_HOME`:\n\n```json\n{}\n```\n\nGo back with `PAGE_BACK`:\n\n```json\n{}\n```\n\n## 10. Wait and Read Elements\n\nWait a fixed duration with `WAIT_TIME`:\n\n```json\n{\"wait_time\":1500}\n```\n\nWait for an element with `WAIT_FOR_SELECTOR`:\n\n```json\n{\"resource_id\":\"com.example:id\/result\",\"timeout\":15}\n```\n\nOr:\n\n```json\n{\"text\":\"Completed\",\"timeout\":10}\n```\n\n`timeout` defaults to 10 seconds.\n\nRead the text of one element with `GET_SINGLE_ELEMENT_TEXT`:\n\n```json\n{\"resource_id\":\"com.example:id\/title\"}\n```\n\nYou can use selector fields such as `text`, `resource_id`, and `class_name`.\n\n## 11. Query Results and Stop Tasks\n\nQuery a command result:\n\n```json\n{\"operation\":\"query\",\"command_id\":\"\"}\n```\n\nStop a stuck task:\n\n```json\n{\n \"operation\": \"stop\",\n \"command_id\": \"stop-1730000000000-a1b2c3d4\",\n \"task_id\": \"\",\n \"reason\": \"operation timeout\"\n}\n```\n\nUse `stop` only for long-running or stuck tasks, not for operations that have completed normally.\n\n## 12. Determine Success\n\nFor a `submit` UI action, HTTP `200` alone does not indicate success. All of the following must hold:\n\n1. The HTTP request succeeds.\n2. The outer response has `state == \"SUCCEEDED\"`.\n3. After parsing, `result_json.success == true`.\n4. A fresh UI read shows the expected screen state.\n\n```javascript\nconst outer = await response.json();\nif (outer.state !== \"SUCCEEDED\") throw new Error(\"Gateway command failed\");\n\nconst result = JSON.parse(outer.result_json);\nif (result.success !== true) throw new Error(\"UI action failed\");\n\n\/\/ Call get_ui_state again to verify the actual UI result.\n```\n\n## 13. Complete cURL Examples\n\n### 13.1 Get the Current Screen\n\n```bash\ncurl -sS 'https:\/\/agent-gateway.duoplus.net\/agent-command' \\\n -H 'Content-Type: application\/json' \\\n -H \"Authorization: Bearer $DUOPLUS_API_KEY\" \\\n -H \"Region: $DUOPLUS_REGION\" \\\n -H \"CloudIP: $DUOPLUS_CLOUD_IP\" \\\n --data '{\n \"operation\":\"submit\",\n \"command_id\":\"ui-state-UNIQUE_ID\",\n \"task_id\":\"ui-state-task-UNIQUE_ID\",\n \"action\":\"get_ui_state\",\n \"payload\":{\n \"task_type\":\"ai\",\n \"task_id\":\"ui-state-task-UNIQUE_ID\",\n \"action\":\"get_ui_state\",\n \"lang\":\"zh\"\n }\n }'\n```\n\n### 13.2 Tap an Element\n\n```bash\ncurl -sS 'https:\/\/agent-gateway.duoplus.net\/agent-command' \\\n -H 'Content-Type: application\/json' \\\n -H \"Authorization: Bearer $DUOPLUS_API_KEY\" \\\n -H \"Region: $DUOPLUS_REGION\" \\\n -H \"CloudIP: $DUOPLUS_CLOUD_IP\" \\\n --data '{\n \"operation\":\"submit\",\n \"command_id\":\"click-UNIQUE_ID\",\n \"task_id\":\"click-task-UNIQUE_ID\",\n \"action\":\"execute\",\n \"payload\":{\n \"task_type\":\"ai\",\n \"task_id\":\"click-task-UNIQUE_ID\",\n \"action\":\"execute\",\n \"action_name\":\"CLICK_ELEMENT\",\n \"params\":{\"text\":\"Continue\",\"wait_after\":800}\n }\n }'\n```\n\nBefore running the Section 13 examples, set `DUOPLUS_API_KEY`, `DUOPLUS_REGION`, and `DUOPLUS_CLOUD_IP`. Replace every occurrence of `UNIQUE_ID` with a fresh unique value for each request; the top-level and `payload` `task_id` values must match within one request. These commands use Bash syntax; PowerShell environment variable syntax differs.\n\n## 14. Automation Recommendations\n\n- Read the UI before each action, then read it again and verify the result afterward.\n- Prefer element selectors. Use coordinates for WebViews, Canvas content, or controls that cannot be identified.\n- Add approximately `500-1500 ms` of `wait_after` for navigation or loading actions.\n- Retry the same approach no more than three times. If nothing changes, switch selectors, coordinates, or navigation methods.\n- Pause for user input before CAPTCHAs, payments, account recovery, or destructive confirmations.\n- A screenshot shows what happened; it does not by itself prove that the task is complete.\n\n\n## 15. Execute a Shell Command\n\nAction name: `SHELL_COMMAND`.\n\nThis action executes one non-interactive shell command on the target cloud phone. When the command\nsucceeds, its captured standard output is returned in `result_json.result_text`. Typical uses include\nreading system properties, querying installed packages, and running reviewed device-maintenance\ncommands.\n\n### 15.1 Parameters\n\nParameter | Required | Description\n--- | --- | ---\n`command` | Yes | Non-empty shell command to execute\n`need_screenshot` | No | Whether to return a screenshot after execution; defaults to `true`. Use `false` for commands that do not change visible UI state\n`wait_before` | No | Delay before execution, in milliseconds\n`wait_after` | No | Delay after execution, in milliseconds\n\nExample parameters:\n\n```json\n{\n \"command\": \"getprop ro.build.version.release\",\n \"need_screenshot\": false\n}\n```\n\nThe device executor waits approximately 20 seconds for one shell command. This timeout cannot be\nchanged through the request. Do not submit interactive commands, persistent foreground processes,\nor commands that cannot finish within the timeout.\n\n### 15.2 Complete Request\n\n```bash\nUNIQUE_ID=\"$(date +%s%3N)-$RANDOM\"\n\ncurl --max-time 30 -sS \\\n 'https:\/\/agent-gateway.duoplus.net\/agent-command' \\\n -H 'Content-Type: application\/json' \\\n -H \"Authorization: Bearer $DUOPLUS_API_KEY\" \\\n -H \"Region: $DUOPLUS_REGION\" \\\n -H \"CloudIP: $DUOPLUS_CLOUD_IP\" \\\n --data \"{\n \\\"operation\\\": \\\"submit\\\",\n \\\"command_id\\\": \\\"shell-${UNIQUE_ID}\\\",\n \\\"task_id\\\": \\\"shell-task-${UNIQUE_ID}\\\",\n \\\"action\\\": \\\"execute\\\",\n \\\"payload\\\": {\n \\\"task_type\\\": \\\"ai\\\",\n \\\"task_id\\\": \\\"shell-task-${UNIQUE_ID}\\\",\n \\\"action\\\": \\\"execute\\\",\n \\\"action_name\\\": \\\"SHELL_COMMAND\\\",\n \\\"params\\\": {\n \\\"command\\\": \\\"getprop ro.build.version.release\\\",\n \\\"need_screenshot\\\": false\n }\n }\n }\"\n```\n\nGenerate new `command_id` and `task_id` values for every request. Within one request, the top-level\n`task_id` and `payload.task_id` must be identical.\n\n### 15.3 Response and Command Output\n\nThe Gateway synchronously returns the terminal command state. Example outer response:\n\n```json\n{\n \"command_id\": \"shell-1730000000000-1234\",\n \"task_id\": \"shell-task-1730000000000-1234\",\n \"state\": \"SUCCEEDED\",\n \"success\": true,\n \"message\": \"Execute shell command: getprop ro.build.version.release - Success\",\n \"result_json\": \"{\\\"task_id\\\":\\\"shell-task-1730000000000-1234\\\",\\\"success\\\":true,\\\"message\\\":\\\"Execute shell command: getprop ro.build.version.release - Success\\\",\\\"result_text\\\":\\\"15\\\\n\\\",\\\"screenshot\\\":\\\"\\\",\\\"current_app\\\":\\\"\\\"}\"\n}\n```\n\n`result_json` is a JSON string and must be parsed separately:\n\n```javascript\nconst outer = await response.json();\nif (outer.state !== \"SUCCEEDED\" || outer.success !== true) {\n throw new Error(outer.message || \"Shell command failed\");\n}\n\nconst result = JSON.parse(outer.result_json);\nif (result.success !== true) {\n throw new Error(result.message || \"Shell command failed\");\n}\n\nconsole.log(result.result_text); \/\/ Captured stdout for a successful command\n```\n\nSuccess requires all of the following:\n\n1. The HTTP request succeeds.\n2. The outer response has `state == \"SUCCEEDED\"`.\n3. The outer response has `success == true`.\n4. The parsed `result_json` has `success == true`.\n\n`result_text` is guaranteed only for standard output captured from a successful command. Do not\ndepend on it for stderr when a command fails; use `success` and `message` to determine the outcome.\nAvoid commands with unbounded output because the result must fit within the Gateway and Binder\nresponse-size limits.\n\n### 15.4 Security Requirements\n\n`SHELL_COMMAND` is a privileged, high-risk capability. Callers must follow these rules:\n\n- Treat a Gateway API Key that permits shell execution as a high-sensitivity credential. Never put\n it in logs, frontend code, or a public repository.\n- Execute only commands reviewed or allowlisted by the caller. Never concatenate user input,\n webpage content, model output, or other untrusted data directly into a command.\n- The command runs with the permissions available to the device automation executor. These\n permissions may vary by system image and must not be assumed to be an ordinary app sandbox.\n- Require explicit user confirmation before deleting files, changing system configuration,\n stopping system services, installing or removing applications, or restarting the device.\n- Do not use this endpoint to read, return, or log passwords, tokens, cookies, private keys, or\n other sensitive data.\n- Set `\"need_screenshot\": false` by default. Request a screenshot only when visible UI verification\n is necessary.\n\nThe backend should apply a dedicated permission scope, audit logging, rate limiting, and a command\nallowlist to `SHELL_COMMAND` instead of relying only on the general Gateway Bearer Token.\n\n### 15.5 Gateway Priority and Platform API Fallback\n\nWhen a caller supports both Gateway `SHELL_COMMAND` and the platform\n`POST \/api\/v1\/cloudPhone\/command` endpoint, it must use the Gateway first. Consider the platform\nendpoint only when Gateway routing is unavailable, the executor remains unavailable after the normal\nreadiness timeout, or the Gateway has returned a confirmed failure.\n\nA timeout or connection loss after Gateway submission does not prove that the command was not\nexecuted. Query the Gateway with the original `command_id` before considering a fallback. If the\nfinal state remains unknown, only read-only or idempotent commands may be considered safe to retry.\nStop and report an unknown outcome for state-changing or non-idempotent commands to prevent duplicate\nside effects.\n\nThe platform command value must not include an `adb shell` prefix, and the platform endpoint only\nguarantees commands that finish within approximately 10 seconds. See\n[Execute the ADB command](https:\/\/help.duoplus.net\/docs\/execute-the-adb-command\/) for its complete\nrequest and response contract.\n\n## 16. Source\n\n- DuoPlus AI Skill: \n- Platform OpenAPI introduction: \n- Cloud phone list API: ","pure_content":"DuoPlus Cloud Phone Automation Control API\n\nThis API provides a service exposed from within the cloud phone; it allows for direct control of the cloud phone and the execution of automated operations, such as: Get the Screen and UI Elements\u3001Tap and Long Press\u3001Text Input and Keyboard\u3001Swipe and Scroll\u3001App and Page Navigation\u3001Wait and Read Elements\u3001etc.\n\nPrerequisites: Get an API Key from Automation > API in the DuoPlus console. The target phone must be running (status == 1) with HTTP enabled (http_status is 1 or \"1\"). If it is stopped, start it in the console or via the platform power-on API; this document does not cover that endpoint. The Gateway uses the same API Key as its Bearer Token. Device-side authentication must be provisioned to match it, or the Gateway may return 401.\n1. Get the Cloud Phone IP, Region, and Automation Support Status\nBefore calling the HTTP Gateway, use the platform list endpoint to obtain the target cloud phone's ip and region, and confirm that status == 1 and http_status is 1.\n1.1 Endpoint\nPOST https:\/\/openapi.duoplus.net\/api\/v1\/cloudPhone\/list\n\nRequest headers:\nContent-Type: application\/json\nLang: zh\nDuoPlus-API-Key: \n\n1.2 Request Parameters\nQuery by exact cloud phone ID:\n{\n \"image_id\": [\"IMAGE_ID\"],\n \"page\": 1,\n \"pagesize\": 100\n}\n\nYou can also query by name:\n{\n \"name\": \"phone-name\",\n \"page\": 1,\n \"pagesize\": 100\n}\n\n\n\n\n Parameter\n Required\n Description\n\n\n\n\n page\n No\n Page number, starting at 1; defaults to page 1\n\n\n pagesize\n No\n Number of items per page; maximum 100, default 10\n\n\n image_id\n No\n Array of cloud phone IDs; an exact ID is recommended\n\n\n name\n No\n Cloud phone name; names may not be unique\n\n\n link_status\n No\n Array of connection statuses\n\n\n group_id\n No\n Group ID\n\n\n proxy_id\n No\n Proxy ID\n\n\n\n1.3 Response Fields Required for Automation\nExample response envelope:\n{\n \"code\": 200,\n \"message\": \"success\",\n \"data\": {\n \"list\": [\n {\n \"id\": \"IMAGE_ID\",\n \"name\": \"phone-name\",\n \"status\": 1,\n \"ip\": \"10.0.0.10\",\n \"region\": \"sg\",\n \"http_status\": 1\n }\n ],\n \"total_page\": 1\n }\n}\n\n\nThis example shows only the fields needed for automation. The server may return additional device information.\n\n\n\n\n Field\n Purpose\n\n\n\n\n data.list[].id\n Cloud phone ID, used to confirm that the correct device was selected\n\n\n data.list[].status\n 1 means the cloud phone is running; handle other states first\n\n\n data.list[].ip\n Value of the Gateway CloudIP request header\n\n\n data.list[].region\n Value of the Gateway Region request header; use the selected phone's returned value\n\n\n data.list[].http_status\n 1\/\"1\" means HTTP is enabled; 0\/\"0\" means it is disabled\n\n\n data.total_page\n Total number of pages; iterate through all pages when not querying by exact ID\n\n\n\nSuccess requires both a successful HTTP request and a top-level response code == 200.\n1.4 cURL Example\ncurl -sS 'https:\/\/openapi.duoplus.net\/api\/v1\/cloudPhone\/list' \\\n -H 'Content-Type: application\/json' \\\n -H 'Lang: zh' \\\n -H \"DuoPlus-API-Key: $DUOPLUS_API_KEY\" \\\n --data '{\"image_id\":[\"IMAGE_ID\"],\"page\":1,\"pagesize\":100}'\n\nVerify the matching item's id, then extract:\nCloudIP = matched_phone.ip\nRegion = matched_phone.region\n\nCall the automation Gateway only when status == 1 and String(http_status) == \"1\". A nonempty ip does not mean automation is enabled. When searching by name, read every page indicated by total_page; use the ID to resolve duplicate names. The platform OpenAPI limit is 1 QPS per endpoint, including pagination requests.\n2. Automation Endpoint\nSend all automation operations to:\nPOST https:\/\/agent-gateway.duoplus.net\/agent-command\n\nContent-Type: application\/json\nAuthorization: Bearer \nRegion: \nCloudIP: \n\n\n\n\n Header\n Description\n\n\n\n\n Authorization\n Gateway authentication, in the form Bearer\n\n\n Region\n The target phone's region returned by list\n\n\n CloudIP\n Cloud phone private IP address\n\n\n\nThe cloud phone must be running with HTTP enabled. If the Gateway returns 401, check the API Key and device authentication configuration rather than retrying blindly. Replace the example region and IP in the Section 13 cURL commands with the values returned for the target phone.\n3. Common Request Model\n\n\n\n operation\n Purpose\n\n\n\n\n health\n Check Gateway\/backend health\n\n\n ready\n Check whether the automation executor is ready\n\n\n submit\n Get the screen\/UI or perform a UI action\n\n\n query\n Query a retained command result\n\n\n stop\n Stop a running or stuck task\n\n\n\nGeneral request for an action:\n{\n \"operation\": \"submit\",\n \"command_id\": \"click-element-1730000000000-a1b2c3d4\",\n \"task_id\": \"click-element-task-1730000000000-a1b2c3d4\",\n \"action\": \"execute\",\n \"payload\": {\n \"task_type\": \"ai\",\n \"task_id\": \"click-element-task-1730000000000-a1b2c3d4\",\n \"action\": \"execute\",\n \"action_name\": \"CLICK_ELEMENT\",\n \"params\": {\n \"text\": \"Search\",\n \"wait_after\": 500\n }\n }\n}\n\n\n\ncommand_id and task_id should be unique.\nUse uppercase action names for action_name.\nPut action parameters in payload.params.\nYou may add a Unix timestamp in milliseconds as a top-level deadline_at.\nA synchronous action can take up to approximately 300 seconds; set the client timeout to approximately 310 seconds.\n\nThe params for any action may include:\n\n\n\n Parameter\n Description\n\n\n\n\n wait_before\n Delay before the action, in milliseconds\n\n\n wait_after\n Delay after the action, in milliseconds; 500-1500 is recommended for navigation\/loading\n\n\n\n4. Health and Readiness Checks\nHealth check:\n{\"operation\":\"health\"}\n\nReadiness check:\n{\"operation\":\"ready\"}\n\nThe executor is ready when the response has executor == \"ready\" or ready == true. On 503 or NOT_READY, continue polling within the startup timeout.\n5. Get the Screen and UI Elements\n5.1 Request\n{\n \"operation\": \"submit\",\n \"command_id\": \"ui-state-1730000000000-a1b2c3d4\",\n \"task_id\": \"ui-state-task-1730000000000-a1b2c3d4\",\n \"action\": \"get_ui_state\",\n \"payload\": {\n \"task_type\": \"ai\",\n \"task_id\": \"ui-state-task-1730000000000-a1b2c3d4\",\n \"action\": \"get_ui_state\",\n \"lang\": \"zh\"\n }\n}\n\n5.2 Parse the Response\nresult_json is a JSON string and must be parsed separately:\nconst outer = await response.json();\nconst result = JSON.parse(outer.result_json);\n\nThe parsed object may contain:\n\n\nsuccess: whether the action succeeded;\na UI element tree, used to locate controls by text, resource ID, content description, and other attributes;\n\nscreenshot: a Base64-encoded image of the current screen.\n\nDecode the screenshot:\nconst encoded = result.screenshot.replace(\/^data:[^,]+,\/, \"\");\nconst bytes = Buffer.from(encoded, \"base64\");\n\nRead the UI before the first action. Read it again after every click, input, swipe, or navigation action to verify the actual screen change.\n6. Tap and Long Press\n6.1 Tap an Element: CLICK_ELEMENT\n{\"text\":\"Continue\",\"wait_after\":800}\n\n\n\n\n Parameter\n Description\n\n\n\n\n resource_id\n Android resource ID; usually the most stable selector\n\n\n content_desc\n Accessibility content description\n\n\n text\n Displayed element text\n\n\n class_name\n Android view class name\n\n\n element_order\n Zero-based index when multiple elements match\n\n\n\n{\"resource_id\":\"com.example:id\/login\"}\n\n{\"content_desc\":\"Search\"}\n\n{\"text\":\"Item\",\"element_order\":1}\n\nPrefer resource_id, then content_desc\/text, then coordinates.\n6.2 Long Press an Element: LONG_ELEMENT\n{\"text\":\"Message\",\"duration\":1200}\n\nUse the same selector fields as CLICK_ELEMENT. duration is in milliseconds.\n6.3 Coordinate Actions\nTap with CLICK_COORDINATE:\n{\"x\":500,\"y\":420,\"wait_after\":500}\n\nLong press with LONG_COORDINATE:\n{\"x\":500,\"y\":420,\"duration\":1200}\n\nDouble tap with DOUBLE_TAP_COORDINATE:\n{\"x\":500,\"y\":420}\n\nCoordinates are relative values in the range 0..1000, with (0,0) at the top left and (1000,1000) at the bottom right:\nrelative_x = round(pixel_x \/ screenshot_width * 1000)\nrelative_y = round(pixel_y \/ screenshot_height * 1000)\n\nTake a fresh screenshot immediately before a coordinate action and use the target's center. Do not reuse old coordinates after a page transition or rotation.\n7. Text Input and Keyboard\n7.1 Enter Text: INPUT_CONTENT\n{\"content\":\"hello world\",\"clear_first\":true}\n\nFocus the input field first: get the UI, tap the input field, call INPUT_CONTENT, send Enter if needed, and get the UI again to verify the result.\n7.2 Keyboard: KEYBOARD_OPERATION\n{\"key\":\"enter\"}\n\nSupported keys: enter, delete, tab, escape, and space.\n8. Swipe and Scroll\nAction name: SLIDE_PAGE.\nDefault gesture:\n{\"direction\":\"up\",\"wait_after\":600}\n\nSupported directions: up, down, left, and right. To scroll down through content, swipe your finger upward and use up.\nCustom gesture path:\n{\n \"direction\": \"up\",\n \"start_x\": 520,\n \"start_y\": 780,\n \"end_x\": 500,\n \"end_y\": 260,\n \"wait_after\": 600\n}\n\nTry the default gesture first and reread the screen after every swipe. If it has no effect, adjust the path slightly; generally try the same target no more than three times.\n9. App and Page Navigation\nOpen an app with OPEN_APP:\n{\"package_name\":\"com.android.settings\",\"wait_after\":1200}\n\nGo to the home screen with GO_TO_HOME:\n{}\n\nGo back with PAGE_BACK:\n{}\n\n10. Wait and Read Elements\nWait a fixed duration with WAIT_TIME:\n{\"wait_time\":1500}\n\nWait for an element with WAIT_FOR_SELECTOR:\n{\"resource_id\":\"com.example:id\/result\",\"timeout\":15}\n\nOr:\n{\"text\":\"Completed\",\"timeout\":10}\n\ntimeout defaults to 10 seconds.\nRead the text of one element with GET_SINGLE_ELEMENT_TEXT:\n{\"resource_id\":\"com.example:id\/title\"}\n\nYou can use selector fields such as text, resource_id, and class_name.\n11. Query Results and Stop Tasks\nQuery a command result:\n{\"operation\":\"query\",\"command_id\":\"\"}\n\nStop a stuck task:\n{\n \"operation\": \"stop\",\n \"command_id\": \"stop-1730000000000-a1b2c3d4\",\n \"task_id\": \"\",\n \"reason\": \"operation timeout\"\n}\n\nUse stop only for long-running or stuck tasks, not for operations that have completed normally.\n12. Determine Success\nFor a submit UI action, HTTP 200 alone does not indicate success. All of the following must hold:\n\nThe HTTP request succeeds.\nThe outer response has state == \"SUCCEEDED\".\nAfter parsing, result_json.success == true.\nA fresh UI read shows the expected screen state.\n\nconst outer = await response.json();\nif (outer.state !== \"SUCCEEDED\") throw new Error(\"Gateway command failed\");\n\nconst result = JSON.parse(outer.result_json);\nif (result.success !== true) throw new Error(\"UI action failed\");\n\n\/\/ Call get_ui_state again to verify the actual UI result.\n\n13. Complete cURL Examples\n13.1 Get the Current Screen\ncurl -sS 'https:\/\/agent-gateway.duoplus.net\/agent-command' \\\n -H 'Content-Type: application\/json' \\\n -H \"Authorization: Bearer $DUOPLUS_API_KEY\" \\\n -H \"Region: $DUOPLUS_REGION\" \\\n -H \"CloudIP: $DUOPLUS_CLOUD_IP\" \\\n --data '{\n \"operation\":\"submit\",\n \"command_id\":\"ui-state-UNIQUE_ID\",\n \"task_id\":\"ui-state-task-UNIQUE_ID\",\n \"action\":\"get_ui_state\",\n \"payload\":{\n \"task_type\":\"ai\",\n \"task_id\":\"ui-state-task-UNIQUE_ID\",\n \"action\":\"get_ui_state\",\n \"lang\":\"zh\"\n }\n }'\n\n13.2 Tap an Element\ncurl -sS 'https:\/\/agent-gateway.duoplus.net\/agent-command' \\\n -H 'Content-Type: application\/json' \\\n -H \"Authorization: Bearer $DUOPLUS_API_KEY\" \\\n -H \"Region: $DUOPLUS_REGION\" \\\n -H \"CloudIP: $DUOPLUS_CLOUD_IP\" \\\n --data '{\n \"operation\":\"submit\",\n \"command_id\":\"click-UNIQUE_ID\",\n \"task_id\":\"click-task-UNIQUE_ID\",\n \"action\":\"execute\",\n \"payload\":{\n \"task_type\":\"ai\",\n \"task_id\":\"click-task-UNIQUE_ID\",\n \"action\":\"execute\",\n \"action_name\":\"CLICK_ELEMENT\",\n \"params\":{\"text\":\"Continue\",\"wait_after\":800}\n }\n }'\n\nBefore running the Section 13 examples, set DUOPLUS_API_KEY, DUOPLUS_REGION, and DUOPLUS_CLOUD_IP. Replace every occurrence of UNIQUE_ID with a fresh unique value for each request; the top-level and payload task_id values must match within one request. These commands use Bash syntax; PowerShell environment variable syntax differs.\n14. Automation Recommendations\n\nRead the UI before each action, then read it again and verify the result afterward.\nPrefer element selectors. Use coordinates for WebViews, Canvas content, or controls that cannot be identified.\nAdd approximately 500-1500 ms of wait_after for navigation or loading actions.\nRetry the same approach no more than three times. If nothing changes, switch selectors, coordinates, or navigation methods.\nPause for user input before CAPTCHAs, payments, account recovery, or destructive confirmations.\nA screenshot shows what happened; it does not by itself prove that the task is complete.\n\n15. Execute a Shell Command\nAction name: SHELL_COMMAND.\nThis action executes one non-interactive shell command on the target cloud phone. When the command\nsucceeds, its captured standard output is returned in result_json.result_text. Typical uses include\nreading system properties, querying installed packages, and running reviewed device-maintenance\ncommands.\n15.1 Parameters\n\n\n\n Parameter\n Required\n Description\n\n\n\n\n command\n Yes\n Non-empty shell command to execute\n\n\n need_screenshot\n No\n Whether to return a screenshot after execution; defaults to true. Use false for commands that do not change visible UI state\n\n\n wait_before\n No\n Delay before execution, in milliseconds\n\n\n wait_after\n No\n Delay after execution, in milliseconds\n\n\n\nExample parameters:\n{\n \"command\": \"getprop ro.build.version.release\",\n \"need_screenshot\": false\n}\n\nThe device executor waits approximately 20 seconds for one shell command. This timeout cannot be\nchanged through the request. Do not submit interactive commands, persistent foreground processes,\nor commands that cannot finish within the timeout.\n15.2 Complete Request\nUNIQUE_ID=\"$(date +%s%3N)-$RANDOM\"\n\ncurl --max-time 30 -sS \\\n 'https:\/\/agent-gateway.duoplus.net\/agent-command' \\\n -H 'Content-Type: application\/json' \\\n -H \"Authorization: Bearer $DUOPLUS_API_KEY\" \\\n -H \"Region: $DUOPLUS_REGION\" \\\n -H \"CloudIP: $DUOPLUS_CLOUD_IP\" \\\n --data \"{\n \\\"operation\\\": \\\"submit\\\",\n \\\"command_id\\\": \\\"shell-${UNIQUE_ID}\\\",\n \\\"task_id\\\": \\\"shell-task-${UNIQUE_ID}\\\",\n \\\"action\\\": \\\"execute\\\",\n \\\"payload\\\": {\n \\\"task_type\\\": \\\"ai\\\",\n \\\"task_id\\\": \\\"shell-task-${UNIQUE_ID}\\\",\n \\\"action\\\": \\\"execute\\\",\n \\\"action_name\\\": \\\"SHELL_COMMAND\\\",\n \\\"params\\\": {\n \\\"command\\\": \\\"getprop ro.build.version.release\\\",\n \\\"need_screenshot\\\": false\n }\n }\n }\"\n\nGenerate new command_id and task_id values for every request. Within one request, the top-level\ntask_id and payload.task_id must be identical.\n15.3 Response and Command Output\nThe Gateway synchronously returns the terminal command state. Example outer response:\n{\n \"command_id\": \"shell-1730000000000-1234\",\n \"task_id\": \"shell-task-1730000000000-1234\",\n \"state\": \"SUCCEEDED\",\n \"success\": true,\n \"message\": \"Execute shell command: getprop ro.build.version.release - Success\",\n \"result_json\": \"{\\\"task_id\\\":\\\"shell-task-1730000000000-1234\\\",\\\"success\\\":true,\\\"message\\\":\\\"Execute shell command: getprop ro.build.version.release - Success\\\",\\\"result_text\\\":\\\"15\\\\n\\\",\\\"screenshot\\\":\\\"\\\",\\\"current_app\\\":\\\"\\\"}\"\n}\n\nresult_json is a JSON string and must be parsed separately:\nconst outer = await response.json();\nif (outer.state !== \"SUCCEEDED\" || outer.success !== true) {\n throw new Error(outer.message || \"Shell command failed\");\n}\n\nconst result = JSON.parse(outer.result_json);\nif (result.success !== true) {\n throw new Error(result.message || \"Shell command failed\");\n}\n\nconsole.log(result.result_text); \/\/ Captured stdout for a successful command\n\nSuccess requires all of the following:\n\nThe HTTP request succeeds.\nThe outer response has state == \"SUCCEEDED\".\nThe outer response has success == true.\nThe parsed result_json has success == true.\n\nresult_text is guaranteed only for standard output captured from a successful command. Do not\ndepend on it for stderr when a command fails; use success and message to determine the outcome.\nAvoid commands with unbounded output because the result must fit within the Gateway and Binder\nresponse-size limits.\n15.4 Security Requirements\nSHELL_COMMAND is a privileged, high-risk capability. Callers must follow these rules:\n\nTreat a Gateway API Key that permits shell execution as a high-sensitivity credential. Never put\nit in logs, frontend code, or a public repository.\nExecute only commands reviewed or allowlisted by the caller. Never concatenate user input,\nwebpage content, model output, or other untrusted data directly into a command.\nThe command runs with the permissions available to the device automation executor. These\npermissions may vary by system image and must not be assumed to be an ordinary app sandbox.\nRequire explicit user confirmation before deleting files, changing system configuration,\nstopping system services, installing or removing applications, or restarting the device.\nDo not use this endpoint to read, return, or log passwords, tokens, cookies, private keys, or\nother sensitive data.\nSet \"need_screenshot\": false by default. Request a screenshot only when visible UI verification\nis necessary.\n\nThe backend should apply a dedicated permission scope, audit logging, rate limiting, and a command\nallowlist to SHELL_COMMAND instead of relying only on the general Gateway Bearer Token.\n15.5 Gateway Priority and Platform API Fallback\nWhen a caller supports both Gateway SHELL_COMMAND and the platform\nPOST \/api\/v1\/cloudPhone\/command endpoint, it must use the Gateway first. Consider the platform\nendpoint only when Gateway routing is unavailable, the executor remains unavailable after the normal\nreadiness timeout, or the Gateway has returned a confirmed failure.\nA timeout or connection loss after Gateway submission does not prove that the command was not\nexecuted. Query the Gateway with the original command_id before considering a fallback. If the\nfinal state remains unknown, only read-only or idempotent commands may be considered safe to retry.\nStop and report an unknown outcome for state-changing or non-idempotent commands to prevent duplicate\nside effects.\nThe platform command value must not include an adb shell prefix, and the platform endpoint only\nguarantees commands that finish within approximately 10 seconds. See\nExecute the ADB command for its complete\nrequest and response contract.\n16. Source\n\nDuoPlus AI Skill: https:\/\/clawhub.ai\/duoplusofficial\/skills\/duoplus-ai\n\nPlatform OpenAPI introduction: https:\/\/help.duoplus.net\/docs\/Introduction\n\nCloud phone list API: https:\/\/help.duoplus.net\/docs\/cloud-phone-list","is_draft":"0","editor_type":"2","file_path":"","add_time":"1790236052","update_time":"1791949397"},"pure_content":"DuoPlus Cloud Phone Automation Control API\n\nThis API provides a service exposed from within the cloud phone; it allows for direct control of the cloud phone and the execution of automated operations,"}],"content":{"icon":"\/docker_production\/baovvg\/content_icon\/vMFyKPnJ?rand=661374829","desc":"","content_id":"246686","add_time":"1733972394","update_time":"1734015502","content":"","is_traffic_less":"0","file_type":""},"hot_list":[],"user_read_num":"0","is_auth":"0"},"msg":"Success","code":200}