Summary: | Clipboard from platform to OS doesn't work 100% of the time | ||
---|---|---|---|
Product: | [Applications] kdeconnect | Reporter: | bstallman99 <bstallman99> |
Component: | common | Assignee: | Albert Vaca Cintora <albertvaka> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | alteahandle-kde, andre.vmatos, AndyKluger, jmprieto, kde, lee295012, leftcrane, mail, maiphi.public, nicolas.fella, simon, tonymt00 |
Priority: | NOR | ||
Version: | 1.3.2 | ||
Target Milestone: | --- | ||
Platform: | Android | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
bstallman99@gmail.com
2019-07-26 22:04:06 UTC
I do have the same problem now since updating to Android 10 on my Pixel 2. SOFTWARE/OS VERSIONS Android: 10 QP1A.190711.020 Linux/KDE Plasma: 5.2.11-050211-generic (available in About System) KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.61.0 Qt Version: 5.12.3 TL;DR Android sucks Android Q doesn't allow apps to access the clipboard when running in the background. https://www.xda-developers.com/android-q-blocks-background-clipboard-access/ Is it possible for the KDE android app the ask for admin app permissions on Android from now on and utilize it? I don't think that helps us in any way here Same here Pixel 2 after Android 10 Copy on KDE Neon desktop, phone receives and makes pastable. Copy on the phone and desktop receives nothing. Very frustrating when someone sends you a link. This looks to be related to: https://www.reddit.com/r/kde/comments/d0esn4/kdeconnect_clipboard_sharing_not_working_with/ https://github.com/andyholmes/gnome-shell-extension-gsconnect/issues/702 https://github.com/andyholmes/gnome-shell-extension-gsconnect/issues/732 Looks like its being looked at in: https://invent.kde.org/kde/kdeconnect-android/issues/5 Intriguingly the Join developer has found a way around it: https://joaoapps.com/AutoApps/Help/Info/com.joaomgcd.join/android_10_read_logs.html *** Bug 411526 has been marked as a duplicate of this bug. *** *** This bug has been marked as a duplicate of bug 420198 *** |