PowerClicker App Closes Unexpectedly
Some Android devices restrict background apps to save power.
To prevent PowerClicker from being affected, disable battery optimization for the app in your Android device settings.
Scenario Controller Disappears
The Scenario Controller may become hidden if:
- You manually hide it using the X button.
- The app unexpectedly closes.
How to Restore the Scenario Controller
- Open the PowerClicker app.
- Go to the Scenario List screen.
- Tap “Start Service” to display the controller.
⚠ Note: The Scenario Controller will not be displayed if no scenarios exist.
If the Controller Still Does Not Appear
If “Start Service” or “Reset Controller Position” does not work:
- Open Android settings.
- Go to Accessibility settings.
- Find PowerClicker and turn “Use Service” OFF.
- Turn “Use Service” ON again.
- This should restore the Scenario Controller.
Cannot Use Other Apps While PowerClicker is Running
Some apps restrict usage when an auto-clicker app like PowerClicker is active.
This is due to Android and app-specific restrictions, and it cannot be bypassed.
To use such apps while PowerClicker is installed:
- Temporarily disable permissions for PowerClicker.
- Follow the instructions on Start PowerClicker and turn “Use Service” OFF.
- To re-enable PowerClicker, turn “Use Service” ON again.
Duration and Wait Time Do Not Work as Set
If tap duration or wait time is too short, Android may not process it correctly, causing delays.
Try adjusting the time settings as needed.
Unable to Detect Screen Elements
In some apps—especially games where the entire screen is rendered as a single image—PowerClicker’s screen element detection may not be available.
Additionally, some apps and screens use a component called a WebView to display web content. Elements displayed inside a WebView behave differently from regular buttons or text, and the information retrieved through Android’s accessibility features may be inaccurate.
In particular, the following limitations may occur:
- The detected element’s position may not match its actual on-screen position
- Scrolling or zooming can cause detection to misalign with the visible content
- Even fixed-position elements (such as floating buttons) may appear to shift positions
These issues are due to limitations in the Android system and cannot be fully controlled by the app.
PowerClicker is designed to work as accurately as possible even in such cases, but please understand that perfect detection accuracy cannot be guaranteed.
If detection is difficult, we recommend specifying the element by its visible text (e.g., "OK") to improve stability.
Text Is Not Entered When Using "Enter Text" or "Enter Text into Detected Screen Element"
In some cases, the "Enter Text" or "Enter Text into Detected Screen Element" step may not work as expected, and text may not be entered into the intended field. The following issues have been identified as common causes:
- The element currently in focus may not actually be a real text input field.
Even if it visually appears to be focused, the actual focused element may be something else. In such cases, the text input step alone may not successfully input text.
- Some apps restrict text input unless a specific screen element is in focus.
In these cases, the target element must first be properly focused before text input can succeed.
If you encounter this issue, try using the following combination of steps: Screen Element Detection → Detected Target Tap → Enter Text into Detected Screen Element. This approach may allow the text input to succeed.
Recommended Steps:
- Use "Screen Element Detection" and enable "Restrict to elements that support text input" to select the correct input field.
- In the screen element detection step, configure the success action to "Detected Target Tap". (This is the default setting if not changed.)
- Add a "Enter Text into Detected Screen Element" step after the tap step and enter the desired text.
- (Optional) After the text input step, add a step that taps somewhere outside the input field or taps a specific button to close the keyboard if needed.
Disable Screenshot Permission Dialog for Image/Text Detection
Android requires user permission each time the screen is captured.
This cannot be bypassed due to Android’s system restrictions.
Image/Text Detection Fails Completely
Some apps restrict screen reading, preventing PowerClicker from detecting content.
To check:
- Take a screenshot using Android’s screenshot feature.
- If the target area is blacked out, the app is blocking screen reading.
In such cases, image and text detection will not work.
Image/Text Detection is Slow
Detection processes can be resource-intensive. Try the following to improve performance:
- Limit Detection Area
If you know where the target image appears, set a detection range instead of scanning the entire screen.
- Use Scaling to Reduce Size
Large detection areas take longer. Try reducing the image size using scaling settings.
Image Detection Fails
If the scale of the detection image and the actual screen image is too different, detection may fail.
Try adjusting the scale of the detection image to match the screen.
Text Detection Fails
If the text on the screen is too small, detection may be less accurate.
Try increasing the scaling level to enlarge the text for better recognition.
However, higher scaling may increase processing time. To optimize performance, consider limiting the detection area to reduce processing load.