Bug 438126 - KDE Connect enabled via Android’s accessibility service overrides external keyboard layouts
Summary: KDE Connect enabled via Android’s accessibility service overrides external ke...
Status: RESOLVED WORKSFORME
Alias: None
Product: kdeconnect
Classification: Applications
Component: android-application (other bugs)
Version First Reported In: unspecified
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Albert Vaca Cintora
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-06-05 16:19 UTC by Maximilian Böhm
Modified: 2024-09-04 03:47 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Maximilian Böhm 2021-06-05 16:19:37 UTC
I have enabled KDE Connect in my Galaxy Tab S7+’s accessibility services to be able to use the remote keyboard feature PC → Android device. But enabling this seems to override the layout of my German external keyboard to an American one (no ÄÖÜß, but still normal German location of Z/Y). This happens on bluetooth keyboards as well as with my "Galaxy Book Cover Keyboard", which is using a physical connection.

Android 11, security patch level May 2021, KDE Connect 1.17.0 via F-Droid.
Comment 1 Zachariah Anderson 2021-11-24 17:44:11 UTC
Confirming this issue exists, and adding additional info. As far as I can tell this is a bug with Android 11's accessibility services. I discovered this issue also effects game controllers, causing all inputs from any hardware to declare there origin as a 'Virtual' device with vendor and device ids only showing 0000. This broke compatibility with any game that uses controller specific profiles, or has multiplayer.

I don't know if this bug is still present in Android 12, but if so it may need addressing in KDE Connect.

To recreate the issue, and confirm it, enable the KDE Connect accessibility service, and test a controller with a gamepad tester app. You should see device: Virtual instead of the controllers original identifier. 

The keyboard defaults to American as the input subsystem loads the Virtual device with Androids default keymap.
Comment 2 cwo 2024-08-05 21:02:46 UTC
Thank you for the bug report!

I was not able to replicate this using the current version of KDE Connect (24.05) and a Galaxy tablet (Android 14) with a Targus bluetooth keyboard - even with accessibility services on, the keyboard keeps its layout.

(It's not quite perfect; while the virtual keyboard is set to the KDE remote keyboard, the layout of the external keyboard can't be changed using the built-in shortcut, it stays at the most recently selected layout until a different virtual keyboard is selected).

Is this still an issue for you? If so, could you add some information regarding your setup (e.g. Android versions, keyboard model, etc.)
Comment 3 Bug Janitor Service 2024-08-20 03:47:24 UTC
🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME.

For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging.

Thank you for helping us make KDE software even better for everyone!
Comment 4 Bug Janitor Service 2024-09-04 03:47:20 UTC
🐛🧹 This bug has been in NEEDSINFO status with no change for at least 30 days. Closing as RESOLVED WORKSFORME.