Image Script Permission Conflicts

Problem Overview

When image scripts and system screenshot permissions (such as cloud control screen casting or other screenshot applications) are used simultaneously, the following issues may occur:

• Screenshot Failure - Unable to obtain screen images
• Permission Conflicts - Multiple applications competing for screenshot permissions
• Functional Abnormalities - Unstable screen casting or script execution

Root Cause

System Screenshot Channel Exclusivity: Android system screenshot permissions can only be occupied by one application at a time and cannot be shared among multiple applications.
System screenshot methods require applying for screenshot permissions, which conflicts with cloud control's remote screen casting permissions.

💡 If only running scripts without screen casting, you can use system screenshot permission method, which is fast and performance stable
System Screenshot API Documentation

Solutions

Solution 1: Avoid Permission Conflicts

1. Single Application Principle
   • Ensure only one application uses system screenshot permissions at a time
   • Pause other screenshot applications when image scripts are running
2. Permission Management
   • Reasonably arrange usage periods for scripts and screen casting
   • Avoid concurrent use of screenshot-related functions

Solution 2: Alternative Screenshot Methods (Recommended)

Based on your enabled automation mode, choose the following screenshot solutions with better compatibility:

HID Screenshot

Features: Good compatibility, relatively slow speed

Accessibility Screenshot

Features: Relatively slow speed

Digital Assistant Screenshot (Recommended)

Features: System-level permissions, high stability, fast speed

ADB Screenshot

Features: Fast speed, supports special pages

Root Screenshot

Features: Highest permissions, fully compatible

Solution Comparison

Best Practice Recommendations

1. With ADB/Root permissions: Use ADB screenshot for easy debugging and rapid iteration
2. Without ADB permissions: Recommended digital assistant screenshot, balancing speed and stability
3. Performance priority: Except for HID and accessibility screenshots, other methods are close to system screenshot speed

Core Advantages

• Zero Conflict: All alternative solutions do not occupy system screenshot channels
• Full Compatibility: Can perfectly coexist with cloud control screen casting functions
• Special Support: Supports application interfaces that restrict screenshots such as password pages, payment pages
• Excellent Performance: Most solutions have speed comparable to system screenshots

⚡ Important Note: It is recommended to choose appropriate alternative screenshot solutions at the beginning of the project to avoid debugging costs caused by permission conflicts later.