Troubleshooting

Android clipboard not syncing? How to fix it

By Intelligentia Studios, the maker of MyClippy · Published 21 September 2026 · Updated 28 September 2026

Test each direction separately. If computer → phone works but phone → computer doesn’t, the network is fine and Android copy capture is the problem: since Android 10, apps can’t read the clipboard in the background unless they are the keyboard or the app in focus. If neither direction works, fix device discovery first: same Wi-Fi, no guest isolation or VPN, and local-network access allowed.

The 30-second test that narrows it down

A connected status confirms that apps can see one another; it does not establish that a source app exposed its copied text. Keep the test simple and avoid passwords or private messages.

On the computer, copy “Desktop test — green tree” and paste it on the phone.
On the phone, copy “Phone test — blue sky” from a harmless text field and paste it on the computer.
Note which direction failed, the phone model, Android version and source app. Keep private clipboard contents out of any bug report.

Find your symptom

Android clipboard sync symptoms, causes and fixes
Symptom	Most likely cause	What to do
Computer → phone works; phone → computer doesn’t	Android automatic copy isn’t set up, or its Accessibility service was turned off	Turn on both the in-app consent and the Accessibility service, then copy fresh text. Or use Share → MyClippy.
Neither direction works	The devices can’t reach each other	Same Wi-Fi, not a guest network; allow local-network access and Private firewall access; pause any VPN.
The first copy after restarting the phone is missing	It was copied before MyClippy reconnected	Open MyClippy, wait for Connected, then copy again.
Some copies arrive, others don’t, or the wrong one wins	Device clocks differ	Turn on automatic date and time on every device.
Copies from one app never arrive	That app’s copy action isn’t detected, or it marks the clip sensitive	Use Share → MyClippy for that app. Sensitive clips are skipped by design.
Long text doesn’t arrive	It is over the 32,768-byte limit	Send shorter text; emoji and many scripts use several bytes per character.
Works for a while, then stops in the background	Battery or background restrictions	Reopen MyClippy; check that its ongoing notification is still present.

The restart and clock rows are problems we reproduced in our own device tests.

Only Android → computer fails

Android’s developer documentation says that unless an app is the default keyboard or the app in focus, it cannot access clipboard data on Android 10 or higher. Being online or showing a notification doesn’t change that.

For MyClippy, the in-app consent and the Android Accessibility service are separate steps, and both must be on. Resume sync and copy something fresh; an earlier copy won’t be resent. Compare a simple text selection with the app where the failure happens. Why Android needs this permission.

Other tools handle the same restriction differently: KDE Connect asks you to tap “Send clipboard” on Android 10 and later, and SwiftKey’s cloud clipboard works only while you type with SwiftKey.

Neither direction works

Open MyClippy on at least one Mac or Windows computer and on the phone, and confirm sync is resumed. Both must be on the same trusted private network. Guest Wi-Fi or router client isolation can stop devices on the same network name from reaching each other.

Allow local-network access when macOS or Android 17 asks, and allow MyClippy on Private networks in Windows Firewall. A VPN can also block local discovery. Keep your usual protections on; on a work network where discovery is blocked, use an approved transfer method instead.

After changing networks, wait for the apps to find each other again and copy something new. MyClippy deliberately doesn’t resend old clipboard contents just because it reconnected.

It works until the phone restarts or locks

In our tests, a copy made on the Mac while the phone was locked was ready to paste after unlocking, and copies made after unlocking arrived normally. After a full reboot, however, the first Android copy made before MyClippy reconnected was lost; a fresh copy after it connected worked.

Long idle periods and manufacturer battery restrictions may also interrupt background operation. Note whether receiving still works, whether the Accessibility service is still on, and which app supplied the text.

Report a problem

Email intelligentiastudios@gmail.com with the device model, Android, macOS or Windows version, MyClippy version, the direction that failed and steps using harmless text. Don’t include clipboard contents or screenshots of private conversations. See Support.

Frequently asked questions

Why can’t Android apps read my clipboard in the background?

Android 10 restricted clipboard access for privacy: an app can read the clipboard only when it is the default keyboard or the app in focus. Clipboard sync apps work around this with a keyboard, a manual send button, or an Accessibility service.

I turned on the Accessibility service. Why doesn’t Android → computer work?

MyClippy also needs its in-app consent: tap Set up automatic copy and agree to the disclosure. Both the consent and the Android service must be on. Then copy fresh text, because earlier copies aren’t sent.

Why did my first copy after restarting my phone not arrive?

It was copied before MyClippy had reconnected to your computer, and the current pilot doesn’t queue copies made before it connects. Open MyClippy, wait for Connected, and copy again.

Can I use clipboard sync on public or office Wi-Fi?

Not MyClippy’s pilot. Any MyClippy installation that can reach the network can join, so use it only on a private network where you trust everyone.

Sources and current requirements

Product capabilities and platform requirements can change. This page describes a local pilot, not a guarantee of compatibility with every phone or source app. Spotted something out of date? Email intelligentiastudios@gmail.com.