Why Your Clipboard App Stopped Saving Automatically

If you have used Android for a few years, you remember clipboard managers that quietly captured everything you copied. Then, at some point, they became unreliable: sometimes a copy showed up, usually it did not, and the app kept a notification running for nothing. The reviews on those apps are full of one line — "it worked, now it doesn't".

Nothing broke. Android changed the rules.

The restriction, plainly

Since Android 10, an app can read the clipboard only while it is the app in the foreground (or while it is the active input method). An app sitting in the background — even one with a persistent notification and a foreground service — gets nothing back when it asks for the clipboard. Google made the change for an obvious reason: the clipboard is where passwords, one-time codes, card numbers and addresses pass through, and any installed app could previously read all of it.

The consequence for clipboard managers is total. There is no permission you can grant to restore the old behaviour, no setting hidden in developer options, and no battery-optimisation tweak that helps. If an app promises automatic capture, it is doing something else.

What the "something else" usually is

Most apps that still advertise automatic saving use the accessibility service. That API exists for screen readers: it can inspect what is on screen, follow what you focus, and it runs all the time. Used for clipboard capture, it is an enormous permission for a small job, and it comes with real costs — battery drain in reviews, extra scrutiny in Google Play policy, and a system warning telling you the app can observe your actions.

Some apps use a keyboard instead. A custom keyboard is allowed to read the clipboard because it has input focus, which is why keyboard-based clipboard features work. That is a fair approach if you were going to change keyboards anyway, and a heavy one if you were not.

And some apps still ask you to run ADB commands from a computer to grant a special permission. That works until the next reboot or OS update, which is exactly what those reviews say.

The four routes that work today

A clipboard manager that respects the restriction saves at the moments you are already in front of it. In practice there are four, and together they cover almost everything:

Opening the app. The app is in the foreground, so it can read the clipboard. Open it and your last copy is stored. This is the fallback that always works.
The text selection menu. Long-press text in any app and the selection toolbar appears — Copy, Share, and any app that registers itself there. Picking the clipboard app saves the text without even copying it. This is the fastest route and almost nobody knows it exists.
A widget, a quick settings tile or a notification button. Tapping one of these briefly brings a tiny transparent screen to the foreground, which is enough to read the clipboard and save. From your side it looks like a one-tap save with a toast.
The share sheet. Share text to the clipboard app from a browser, a chat app or a document. Good for links and long passages.

Why this is not actually worse

Automatic capture sounds better than it was. It also saved every one-time code, every password you pasted, and every piece of junk you copied by accident, which is why so many people complain their clipboard list is full of noise. Deciding what gets saved with a single tap gives you a list you can actually read a week later.

The practical difference is the interface, not the mechanism. If saving is one tap and pasting is one tap from a widget, you stop noticing the restriction at all.

A quick test before you install anything

Does the store listing explain how saving works? An app that hides the restriction will surprise you later.
Does it require the accessibility service to function at all, or only for an optional feature?
Is there a widget or tile? Without one, the only route left is opening the app.
Do recent reviews say "stopped working"? That is the signature of a workaround that broke.

Clipdeck takes the honest route: no accessibility service, no fake background capture, and all four save routes above, with a widget and a quick settings tile so saving and pasting are each one tap.