Permission transparency
How Phone Operator works
Phone Operator works without root on Android 8+. Its Accessibility Service executes only user-configured gestures after you start them. The overlay is used for controls and markers, so you can position an action and keep Start, Pause, and Stop available above the target app.
Phone Operator does not collect, store, or upload screen content. Action positions, timing, ranges, and saved scripts remain on the device. Review the full privacy policy before enabling permissions.
Start deliberately
Practical steps
- 1Open Phone Operator visiblyStart setup from the app while it is on screen. Read the Accessibility disclosure before opening Android settings.
- 2Enable gesture accessUnder Accessibility, find downloaded or installed services, select Phone Operator, and enable it only after reviewing the system warning.
- 3Allow the floating controllerGrant Display over other apps so the controller and action markers can remain visible above the target app.
- 4Run one finite testPlace one tap on a harmless stable control, choose a slow interval and small repeat count, then start while the floating controller is visible.
Android 16 behavior
Keep the overlay visible before starting from the background
Android 16 tightens foreground-service behavior. For apps that rely on the system overlay permission, a background foreground-service start generally requires an overlay window to be visibly present unless another documented exemption applies. This is different from merely having Display over other apps enabled in Settings.
Use Phone Operator's visible app or floating controller to begin a supervised run. If the controller disappeared, return to Phone Operator and restore it instead of repeatedly trying to start from a hidden background state.
Four independent checks
Identify which Android control interrupted the run
Accessibility Service dispatches the configured gesture. Display over other apps shows the controller and markers. A foreground-service notification makes ongoing work visible to the user. Screen timeout and battery management can still lock the display or restrict background activity. One enabled control does not prove the others are working.
When a run stops, note whether the controller vanished, gestures stopped while it remained visible, the screen locked, or the target app changed state. Reproduce one short test before changing any battery setting, then adjust only the app-specific control that matches the observed failure.
Check one variable at a time
Troubleshooting
- Controller is missing after switching apps: recheck Display over other apps and reopen the floating controller from Phone Operator.
- Controller remains visible but taps stop: confirm Phone Operator is still enabled under Accessibility, then run one slow finite tap.
- Android reports that background start is restricted: bring Phone Operator or its visible overlay to the foreground before starting again.
- Run stops when the display turns off: increase system screen timeout temporarily; Phone Operator does not silently change that setting.
- Run stops only after several minutes: reproduce it twice before reviewing the app-specific battery setting.
- Markers move or land on the wrong control after rotation or a layout change: stop and reposition them before continuing.
Safety boundary
Use automation responsibly
Android 16 restrictions are security and power boundaries, not obstacles to bypass. Keep every run visible, user-started, supervised, and easy to stop.
Do not automate payment, purchase, transfer, account-security, privacy-consent, or CAPTCHA screens. Do not use Phone Operator for fake engagement, cheating, bypassing safeguards, or any action that violates the rules of the target app. Stop whenever the screen is different from the one you tested.
Common questions
Questions about set up an auto clicker on android 16
Does an auto clicker still work on Android 16?
Yes, when the app is compatible and you deliberately enable its Accessibility Service and overlay. Start from a visible app or controller and test one action before a longer run.
Is overlay permission alone enough?
No. The permission allows an overlay, but Android 16 background-start behavior can depend on an overlay actually being visible. Accessibility, screen timeout, and battery controls remain separate.
Should I disable all battery protection?
No. First identify and reproduce the exact interruption, then change only the smallest app-specific setting needed for the supervised task.
Device-maker documentation