Authorization Methods Overview
Why Authorization?
After authorization, the following functions can be achieved:
- Apps can auto-start with accessibility, avoiding manual activation each time;
- After authorizing screenshot permissions, the "Screenshot Request" window no longer pops up;
- Combined with system auto-start and anti-background mechanisms, can automatically recover after being killed by the system;
- Even if the device restarts, it can automatically resume operation as long as it's connected to the network.
👉 In other words, authorization enables true "unattended automation" for Apps.
Even if you use HID mode (no need for accessibility auto-start), you still need to authorize screenshot permissions to achieve screen casting or image script functions.
Therefore—unless you only need semi-automatic operation, authorization is a necessary step.
Additionally, except for the PC Authorization Tool which only supports authorizing Cloud Control App,
the other 4 authorization methods can authorize any application (including your packaged custom App).
Validity Period After Authorization
- Permanently valid after authorization, even if:
- Restarting the App;
- Restarting the device;
- Reconnecting to the network after disconnection;
Authorization will still automatically recover without needing to operate again.
- If uninstalling Cloud Control App, authorization will automatically become invalid, ensuring security and device integrity.
- Supports multi-device mutual authorization and self-authorization:
💻 Computer ↔ Phone 📱 Phone ↔ Phone 🤖 Phone ↔ Itself
Flexible adaptation to multi-scenario authorization requirements.
After authorization is completed, you can safely turn off the "Developer Options" function that was enabled for authorization.
Turning it off will not affect the authorization effect, nor will it cause the authorization to become invalid.
1. PC Authorization Tool
💡 Suitable for Windows 8 / 10 / 11 system users. Simplest operation, best compatibility, supports over 90% of Android devices.
📦 Authorization Target: Only supports Cloud Control App (if you need to authorize other Apps, please choose any other solution below)
✅ Advantages: Simplest operation, high success rate
❌ Limitations: Requires computer and data cable connection
2. OTG-USB Cross-device
💡 Suitable for no computer environment (such as going out or mobile office) using another phone to complete authorization.
📦 Authorization Target: Cloud Control App and any other App
✅ Advantages: No computer needed, portable and flexible
❌ Limitations: Requires two phones + adapter supporting OTG
3. WiFi Wireless Debugging
💡 Recommended for cloud phones, emulators, virtual machines, motherboard devices and Android 11+ real devices.
📦 Authorization Target: Cloud Control App and any other App
✅ Advantages: Wireless authorization, supports remote centralized management
❌ Limitations: Requires same local network or port 5555 already opened
4. Shizuku
💡 Suitable for users without Root, but with developer permissions.
📦 Authorization Target: Cloud Control App and any other App
✅ Advantages: No Root needed, safe and stable
❌ Limitations: First-time Shizuku configuration operation is relatively complex
5. Root
💡 Suitable for devices that have obtained Root permissions (cloud phones, emulators, virtual machines, etc.).
📦 Authorization Target: Cloud Control App and any other App ✅ Advantages: Stable and thorough, supports multi-app authorization
❌ Limitations: Requires Root, high operation threshold
Authorization Methods Comparison Table
| Authorization Method | Requires Computer | Requires Root | Can Authorize Any App | Stability | Difficulty |
|---|---|---|---|---|---|
| PC Authorization Tool | ✅ Yes | ❌ No | ❌ No | ⭐⭐⭐⭐⭐ | ⭐ |
| OTG-USB Cross-device | ❌ No | ❌ No | ✅ Yes | ⭐⭐⭐⭐ | ⭐⭐ |
| WiFi Wireless Debugging | ❌ No | ❌ No | ✅ Yes | ⭐⭐⭐ | ⭐⭐ |
| Shizuku | ❌ No | ❌ No | ✅ Yes | ⭐⭐⭐ | ⭐⭐⭐ |
| Root | ❌ No | ✅ Yes | ✅ Yes | ⭐⭐⭐⭐ | ⭐⭐⭐ |
✅ Recommended Priority:
- Have computer → PC Authorization Tool
- No computer → OTG-USB Cross-device method
- Motherboard device → WiFi Debugging method
- Cloud phone / Virtual machine / Emulator → WiFi or Root method
- Advanced users → Shizuku method