SUMMARY For sometime now I have been unable to use the Remote input feature of KDE connect in conjunction Google voice typing from my phone. In the past this was a reliable method of speech to text for Linux so that the impaired could write documents without difficultly. Currently any attempt to do so appears to simply never be transmitted to the PC other forms of Remote input (remote mouse and typing via the standard phone keyboard) appear to function normally STEPS TO REPRODUCE 1.Install and pair KDE connect on a PC and Android phone. 2. Open anything that can accept text on a pc and switch to Google voice typing inside of remote input on the KDE connect Android app. 3. Speak to the phone with a test phrase of your choice OBSERVED RESULT Google Voice typing appears to function yet the spoken phrase does not appear on the pc. EXPECTED RESULT the spoken phrase does not appear on the pc. SOFTWARE/OS VERSIONS Windows: Windows 11 macOS: Linux/KDE Plasma: 5.17.5-gentoo-x86_64 (available in About System) KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.93.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION Android Phones used for testing Samsung Galaxy A01 SM-A015V Android 11 Samsung Galaxy A03s SM-A037U Android 11 Google Pixel 4 XL Android 12 Note: I do not have regular access to this one borrowed it to check if this was Samsung specific KDE Connect App Version 1.19.1 I have marked this as major due to its impact on overall accessibility as well existence across multiple platforms please change if required
my apologies i ment for EXPECTED RESULT to say the spoken phrase appears on the pc tho i suppose this shows why this is a problem
Does the "compose send" feature work for you? (KDE Connect app -> Remote input -> Click the icon with a pencil -> Use voice typing -> Click icon to send the text buffer to PC)
Thank you using "compose send" does alleviate the issue quite a bit restoring my ability to dictate on an X 11 session and on Windows. The icon the is a bit difficult to see due to its size hence why I never noticed it before but it is functional. However it is worth noting using "compose send" as a workaround does not appear to function under a Wayland session demonstrating issues similar to those first reported after hitting send. This is potentially problematic for the future
Thanks. For the Wayland issue, maybe you can see also Bug 444583 and Bug 448604, and file a new bug if needed. *** This bug has been marked as a duplicate of bug 365305 ***