SUMMARY I'm using KDE Connect on Kubuntu 19.10 and the Clipboard extension only shares the clipboard contents from the PC to the phone. Whenever I copy something on my android phone the computer doesn't pick it up. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 19.10 KDE Plasma Version: Plasma 5.16.5 KDE Frameworks Version: 5.62.0 Qt Version: 5.12.4 ADDITIONAL INFORMATION Android version 10 (OxygenOS OP6T_O2_Beta_30)
I cannot confirm it. Have it ever work for you?
It did never work, neither on my PC nor on my Laptop. Also reinstalling KDE connect on my phone or trying it on another network did not resolve the problem.
Are you using any Privacy app, which manages the permission to read the clipboard?
Hi Bennet, I did some debugging on the version of the app that is currently available on GitHub. When I set a breakpoint in the file "ClipboardPlugin.java" at line 68 it breaks as expected when copying something on my desktop PC. However a breakpoint at line 70 in "ClipboardListener.java" should be triggered whenever I copy something on my phone. This does not happen. I strongly believe that this problem is caused by the way Android handles clipboard access permissions as of version 10(see: https://developer.android.com/about/versions/10/privacy/changes#clipboard-data). I also tried copying something into the phones clipboard while KDE Connect had focus by altering a part of the apps source code. This content was indeed transfered to my computer just fine. Do You think I should file a bug report on GitHub or am I missing something super obvious in my phone's settings?
Edit: I do not use any 3rd-party privacy or antivirus software etc.
EditEdit: Possibly mixed up the lines, I meant line 74 in ClipboardListener.java
I can confirm same behavior on Fedora 31 with gsconnect and pixel2-xl on android 10 However,I can confirm taht it used to work for me when my phone was on Android 8 It worked too on Android 9 Android 10 update broke the clipboard from phone to pc
Good to see that you found the exact line of code causing the problem, but I´m not really into Development. I just can point you to https://community.kde.org/Get_Involved/development.
I've been chatting with the devs and it turns out that this problem is a well known issue on Android 10. Currently there doesn't seem to be an adequate workaround yet. Let's hope for the best!
*** This bug has been marked as a duplicate of bug 407837 ***