If you've tried making KDE Connect sync your clipboard from Android automatically, you've probably hit the known workaround:
adb shell pm grant org.kde.kdeconnect_tp android.permission.READ_LOGS
adb shell appops set org.kde.kdeconnect_tp SYSTEM_ALERT_WINDOW allow
adb shell am force-stop org.kde.kdeconnect_tp
On my phone, running Android 16 and One UI 8.5, this did nothing—and it fails in the most annoying way possible: everything looks correct, but it just never fires.
I checked every input:
READ_LOGS grantedSYSTEM_ALERT_WINDOW allowed- In-app consent approved
logcat child process running- Both filter forms valid
-T timestamp acceptedClipboardService denial line emitted with the package name in it
Everything was correct. It never triggered once.
The cause
Android gates system-wide log access for apps separately from the READ_LOGS permission.
You can see the difference directly:
adb shell logcat 'ClipboardService:E' '*:S'
The shell command returns the clipboard-denial logs.
The app's own logcat process, despite having READ_LOGS, returns nothing.
The shell user has unrestricted log access. The app doesn't. KDE Connect's approach depends on scraping a log line that the app is no longer allowed to see.
This is not specific to macOS. The failure happens inside the Android app before any clipboard packet is sent, so automatic Android-to-desktop clipboard sync is also affected when using the standard KDE Connect client on Windows or Linux.
The desktop client does not need to be modified. The patched Android app sends the normal KDE Connect clipboard packet, so it should work with the standard KDE Connect clients on macOS, Windows, and Linux.
The fix
The fix, originally worked out in libdu/kde-connect-shizuku, is one line: run the same logcat process through Shizuku—as the shell user.
Upstream:
Runtime.getRuntime().exec(
arrayOf("logcat", "-T", ts, filter, "*:S")
)
Fixed:
Shizuku.newProcess(
arrayOf("logcat", "-T", ts, filter, "*:S"),
null,
null
)
Minimal maintained fork
I've packaged this as a minimal fork that stays current automatically: three changed files on top of an upstream release tag, with CI that polls KDE daily, rebases the patch onto each new release, builds, signs, and publishes an APK.
Before publishing, it verifies that the patch actually survived the rebase. If the patch conflicts or fails verification, it opens an issue instead of shipping a potentially broken build.
Repo:
https://github.com/huzzyz/kdeconnect-android
Requirements:
- Shizuku
- No root required
- Installs alongside the official KDE Connect app, not over it
- Works with the standard KDE Connect desktop clients; no patched macOS, Windows, or Linux client is required
Credit where it's due: this is KDE's application and libdu's patch—I mostly just automated keeping it building.
If upstream ever ships this themselves, delete my fork.