kcm file not taken into account #8
Comments
|
Do you see the physical keyboard in the android settings ? Can you change its keymap to another (a system one) ? |
|
Thank you for the fast reply.
I can switch to english and the keyboard will be "qwerty" and switch to
french and the keyboard will be "azerty". Yet, with "french bépo", the
keyboard is in "qwerty".
I will get some screenshots and a more detailed explanation of what I
tried so that you have a more precise picture.
|
|
Can you grep your logcat (ideally from boot) for KeyCharacterMap, KeyLayoutMap and Keyboard ? Something like this: adb logcat | grep -E 'KeyCharacterMap|KeyLayoutMap|Keyboard'Since the key character map is of type "Overlay", your base keyboard layout should be qwerty (what's in |
|
I did a test on a more recent Android version, and it still works properly. I'll try to upload updated instructions. |
|
I have updated https://bepo.fr/wiki/BepoAndroid with new screenshots. |
|
Thank you for helping me untangle this issue. First, the result of logcat when plugging the keyboard Then, let me show you what I can see when trying to use the bépo layout.
I change the layout from this To this
When I type «bépo», I get this Then, I tried using a French layout.
When I type "bépo", I get this That sounds promising, but in fact it is very limited, and I cannot use accented characters, "é" gives "2" and "S-é" gives "@", like in a qwerty layout. To me, this is a hint that some new layout was use, but not some new key character map. Anyway, I switched back to "French (bépo)" and tried to configure the virtual keyboards as well. I selected the AOSP keyboard Then configured it in the settings
So that in the end it shows this But still no luck The virtual keyboard shows bépo, but the hardware one still shows "qwer" when pressing "bépo". At that point, I run logcat again, out of curiosity I get this There is a message telling that some KeyboardLayoutSet was fallen back to QWERTY. What do you think about this? Googling it did not help me. In your examples, you use the GBoard virtual keyboard, so I gave it a go, hoping that it might unlock something somehow (looks like a desperate move to me :-)). Its settings look like this
I did not find any settings to use bépo in this keyboard. Yet, even in azerty, the physical keyboard still writes "qwer". At that point, I run logcat again, just in case. It shows more things, but nothing useful I would say. Do you have any idea of what I could try next? |
|
Just a quick check: when you select AZERTY, can you type accents properly ? |
|
No I cannot. The 1234567890 row behaves like in qwerty.
|
|
Interesting. It might be a bug in your Android distribution. I recommend you report it to LineageOS. A few things to check:
Otherwise the bépo key character map cannot work. |
|
Anisse Astier ***@***.***> writes:
Interesting. It might be a bug in your Android distribution. I recommend you report it to LineageOS. A few things to check:
I fear this is not possible, as whyred is not supported anymore.
- has Generic.kl been modified from the original AOSP version: https://cs.android.com/android/platform/superproject/main/+/main:frameworks/base/data/keyboards/Generic.kl
They are a few minor differences, but nothing alarming. (see attached diff)
- is the AZERTY keymap the same as in the AOSP
version: https://cs.android.com/android/platform/superproject/main/+/main:frameworks/base/packages/InputDevices/res/raw/keyboard_layout_french.kcm
There are no files called keyboard_layout_XX.kcm in my phone.
I tried
$ find /data -name 'keyboard_layout*kcm'
and
$ find /system -name 'keyboard_layout*kcm'
I tried downloading keyboard_layout_french.kcm and putting it into
/system/usr/keychars/, but it did not change anything.
Otherwise the bépo key character map cannot work.
Do you think it might be related to the fact there are no kcm files
anywhere in the phone?
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I've been using bepo-android for a long time now.
In a device I recently owned though, it does not work. It is a redmi note 5 (whyred) with the last official lineage os 18 before it became unmaintained (taken from https://xdaforums.com/t/rom-r-official-lineageos-18-1-for-xiaomi-redmi-note-5-pro-whyred.4109253/page-63).
Actually, I think this is not an issue of bepo-android, because whatever content I put in /system/usr/keychars/Vendor_1e54_Product_2030.kcm (I have a TypeMatrix keyboard), the kcm content is not taken into account.
But, even though it is not an issue with bepo-android, I'm asking if you have an idea of how I could investigate this issue.
I'm sure the kcm is correctly read, because logcat tells me so
12-13 17:05:16.134 2217 2326 I EventHub: New device: id=43, fd=330, path='/dev/input/event10', name='TypeMatrix.com USB Keyboard', classes=0x80000121, configuration='', keyLayout='/system/usr/keylayout/Vendor_1e54_Product_2030.kl', keyCharacterMap='/system/usr/keychars/Vendor_1e54_Product_2030.kcm', builtinKeyboard=false,I created the .kl and the .kcm files copying the Generic ones and tried to edit them afterwards.
I fell back adding some bindings in the .kl file, but, as you suggested a long time ago in your post (https://anisse.astier.eu/bepo-android.html), this is barely usable.
I wrote my notes in https://konubinix.eu/braindump/posts/4a6b0994-30f4-47d9-bb80-8dec73b4c0c2/?title=android_11_key_character_map_vs_keylayout_vs_whyred_to_use_bepo.
The text was updated successfully, but these errors were encountered: