
Gyth
-
Content Count
5 -
Joined
-
Last visited
Posts posted by Gyth
-
-
53 minutes ago, Jacob_S said:
By uninstalling Fxservice. But basically it is enough if you turn off accessibility services. Maybe you have some other apps using them?
Or another possible cause:
Under Settings>System>Language and Input>Language you can set the system language. But there is a seperate option under Settings>System>Language and Input>Physical Keyboard>Builtin Keyboard, that manages the keyboard outputs. It has to be set to German for the outputs to match the print of the QWERTZ model.
Hmm doesn't seem to work for me.
I got no Fxservice installed and all the other settings are set accordingly. And it all used to work until like late August or something. Strange..
Edit: I found it! KDEconnect was the culprit!
Sadly it is one of my most used apps, so I have now to fiddle around with it to make my phone and my Linux machine keep communicating nicely with each other in the future
-
1
-
3
-
-
6 hours ago, VaZso said:
Theoretically, the driver was designed in a way it should reflect the written texts of the QWERTZ unit (also for non-standard places), so I would think it should basically work out of the box when you also select German layout in Android.
However, to activate custom keymap function of GUI, you should place your custom keymap file here: /data/system/keyboard/keymap
It has a format of
0:0000:0000
1:0024:1024
2:0031:1032
...etc...The first part is the physical position of a key (reflect to physical wiring), the second part is the normal function of it and the third part is the key's yellow arrow function.
The kernel module's interface is located at /sys/bus/i2c/drivers/aw9523b/6-0058/keymap
If you open that virtual file for reading then it will print out the actual keyboard mapping.Practically most of the keys can be redefined this way but currently there is no option at GUI interface to load that file, so it should be manually placed (see above) either using root access or through adb commands...
As of now I didn't root the phone. So it seems like I have to do it with adb. Is there a package to sideload for that or how would I best tackle the problem?
-
7 hours ago, Jacob_S said:
What symbols do you get, if you try to type the Umlauts? I had the problem, that I had Fxservice installed on LineageOS 18.1, which triggered the bug with accessibilty services and prevented the German layout to be used. So instead I was getting [ and similar symbols instead. Could that be your problem?
Yes it sounds exactly like your previous problem! ü = " [ " "ö = " ; " "ä =" ' "
How did you fix it? It
-
On 3/25/2021 at 8:26 PM, Kaali said:
On my device this "custom keymap" option is greyed out. Is there a way to get the FINqwerty finnish for physical qwertz layout to work on LoS17.1? It was such a perfected layout and the only thing i miss from the stock. LoS Finnish layout's fn combinations doesn't match the print and it is sometimes very annoying.
Edit: Un-Edited
It is exactly the same for me. Just greyish and preventing me to get it back to function again like it had before.
Is the problem that there is no custom keymap installed/activated? How do I do it?
My GPS and everything else is working perfectly normal, though.
Edit: I am on the newest Release of 19.1 LineageOS (November 29) and just want to type German Umlauts with the German keymap
QWERTZ User Layout Setup
in How Tos
Posted
I use KDEconnect mainly for remote-controlling my PC when I am laying in bed being lazy but when the task is not big enough to bother using VNC or SSH. So for switching tracks, fast forwarding shows, controlling mouse and keyboard. So Warpinator wouldn't be an option.
However, I found a way to fix the kdeconnect problem without uninstalling it.
Just install kdeconnect, set it up with all rights enabled it asks for and then as a final step go to accessibility and remove the rights. You'll end up with a perfectly functioning kdeconnect integration and working hardware keyboard as well.
It is funny how long this bothered me and how easy it would have been to fix.