search

anssih / finqwerty

Keyboard layouts for Android phones with physical keyboards
Apache License 2.0
19 stars 11 forks source link

No Polish diacritic signs with the Polish layout #17

Open marmistrz opened 4 years ago

marmistrz commented 4 years ago

OS: LineageOS 16.0, test16 Source: self built Version: 1.5.4 Device: F(x)tec Pro1

I enabled the Polish layout for F(x)tec Pro1 provided by FinQwerty, but I can't input any diacritic signs.

I tried the following matrix of keys (yellow fn, alt, ctrl, sym, fn+shift) + (x, l) and (ź, ł) or its uppercase counterpart was not produced in any case. Moreover, alt+s produces ß instead of ś.

I attached the compiled kcm from my build. It looks like the diacritic signs are produced if fn is used, however fn+e = e, fn + l = ? on my device. Maybe the culprit here is the way how LineageOS handles the fn key?

cc @Derecho @tdm

Derecho commented 4 years ago

Hi @marmistrz . In the latest testbuilds of LOS, the keyboard driver has had some serious modifications. The layout as is part of finqwerty covers the earlier keyboard driver (which is also used by stock android on the phone). Unfortunately, in the current state, this layout cannot apply. With testbuild 16 of LOS what you can do is pick the stock "Polish" layout from Android itself, and then you can enter polish characters by using Sym as AltGr. This is not very convenient for a lot of the characters unfortunately, and I've been inquiring about options to improve on this. You'll be able to find more up to date information on this in the LOS topic on the Pro1 forums.

anssih commented 2 years ago

I'm sorry about the delay in response.

What does KeyEvent Display show for the modifier keys (Alt, Sym, yellow-arrow, ctrl) under LineageOS? Scancode is the most interesting bit of info, but other shown info may be helpful is too.

marmistrz commented 2 years ago

I'm sorry about the delay in response.

What does KeyEvent Display show for the modifier keys (Alt, Sym, yellow-arrow, ctrl) under LineageOS? Scancode is the most interesting bit of info, but other shown info may be helpful is too.

My Pro1 is currently broken. I'll reply when it's fixed. Please ping me if I don't get back to you until the end of Oct.