A clipboard manager that does not use Accessibility

Android 10 is why this question exists

Google stopped background clipboard access so apps could not silently harvest what you copy. A clipboard manager without Accessibility has to pick a legal path: a custom keyboard, reading the clip while the app is visible, share targets, and manual add.

Soloclip is those four paths. Play disclosure matches the code. There is no Accessibility service for capture.

What you give up, on purpose

You do not get a silent log of every copy while Instagram is open and Gboard is up. You get a tool you can explain on a Data safety form. For many people that is the reason to install it.

Set up capture without Accessibility

The onboarding keyboard page is the important one. Enable Soloclip as an input method, then switch to it when you want history to catch the copy or when you want to insert.

1. Skip any Accessibility promptSoloclip does not ask for it and does not need it.
2. Enable the Soloclip keyboardSystem settings → keyboards. This is an Input Method, the supported way to read and insert clipboard-related text.
3. Or share text inShare → Soloclip from a browser or notes app.
4. Or add a clip manuallyThe Add clip button on History.
5. Or open the app after a copyWhen Soloclip is in focus it can read the current clip. It will not poll in the background.

No Accessibility FAQ

Why do other apps need Accessibility for clipboard?

Background apps cannot read the clipboard on Android 10+. Accessibility is the workaround many developers picked.

Is the Soloclip keyboard a keylogger?

No. It is an insert panel for clips you already saved, plus capture while it is the selected IME. It does not record keys from Gboard.

Will I miss copies while Gboard is showing?

You can miss copies if Soloclip is not the IME and the app is not focused. Share-in and manual add cover those. The product does not lie about that.