Background Monitoring Unstable
Use this page when copied content appears only sometimes, stops after the screen locks, or stops after the app is killed.
First isolate the layer
- Copy a short unique text on the source device.
- Check whether it appears in local Clip History.
- If it does not appear locally, this is a capture/background issue.
- If it appears locally but not on another device, use Sync failed.
Common causes
- Clipboard monitoring permission is missing or revoked.
- Android accessibility / Shizuku / root path is not active when required.
- Battery optimization kills the service.
- Notification permission or foreground service behavior is blocked.
- The app was force-stopped by the OS or vendor security software.
- The copied content matches a filter rule.
Checklist
1
Update Octoclip
Background behavior receives frequent compatibility fixes. Retest on the latest version.
2
Confirm local capture first
Do not debug sync until the source device records the clip locally.
3
Check permissions
Review clipboard, accessibility, notification, local network, and any platform-specific permissions used by your setup.
4
Check battery and background restrictions
Allow Octoclip to run in the background and disable aggressive battery optimization for testing.
5
Test plain text
Use short plain text before testing images, files, or OTP extraction.
When to contact support
Send platform, OS version, Octoclip version, monitoring path, reproduction steps, whether local history records the clip, and relevant logs. Do not include sensitive clipboard content.
Was this page helpful?