Slion

My Lineage OS build has been running for some time already and so far so good, I reckon it should complete. I was investigating how to debug that keyboard kernel driver and it seems pretty easy. It turns out all those printk calls land in logcat, it's therefore easy to inspect them in Android Studio for instance and debug the driver. Seems like they are all prefixed with aw9523b so you can use that to filter your logs. That means that providing that my build works and that I can deploy it I reckon I should be able to tweak our keyboard driver. @claude0001 I have one conce

Did the same: https://slions.net/resources/fx-qwerty.7/

Actually the driver source code it says: * Note that there are two each of the shift, ctrl, and alt keys, but * each pair are driven by a single gpio. Thus, left and right cannot * be distinguished for these keys.

Interesting, complete with a guide to enable OTA...

That's what I feared… ho well we'll make do with that then.

I could overcome the case sensitivity issues even when trying to build from a Windows mount but there was another failure shortly afterward that you can't avoid apparently. I'll make another attempt with WSL this time from an actual ext4 file system rather than from a Windows mount. Apparently that should work: https://www.xda-developers.com/how-to-build-lineageos-on-windows-10-using-wsl-2/ https://github.com/microsoft/WSL/issues/7283

Seems to work fine as I went to bed but it did not work in the morning anymore.

I wonder how many of you guys there are. Hope they are going to ship your Pro1X first.

That's an acceptable outcome 😁 failure is always an option!

I'm still hoping I won't have to. Why make it easy when you can make it complicated 😁 Trying to fix that case sensitivity issue… I already had WSL setup so could not bother setting up another linux env. I want my brunch 🍳

Not very far: lol

I just kicked off my first Lineage OS build 🥳 I'm attempting this on Windows using WSL, so far so good, let's see how far it goes…

I'm currently busy setting up my Lineage OS build environment. I'm more then happy to take on your feedback. And yes I still think the way forward is to provide more layout in the kernel so that there is something for everyone including crazy remappers like you and me. Here are the layout I envision, keep the current ones with silent Fn: qwerty qwertz Improved layout with non silent Fn and possibly Meta key, thus providing application level with as much modifiers as possible: qwerty-ex qwertz-ex @EskeRahn @Waxberry or @Erik Do you recall which keys are actually

I have a feeling @VaZso is trying to get qwertz keymap to work with a qwerty keyboard and that somehow won't work as he would expect but that's actually not a bug. You are saying it works fine on your qwertz so I think we are good there.

@VaZso Some keys are hardwired but it seems like you mean more like hardcoded.

Is it not? I don't get why it would not. Not much of a bug then after all...

I can reproduce your issue on qwertz layout with qwerty keyboard. Sounds like a mapping bug in that array indeed. It just goes to show how little testing LOS as had on Pro1. You should open a bug on GitLab about that one issue. Keep it focused and short.

@VaZso You lost me. Which problem are you trying to solve?

Nope that won't work either somehow whenever you enable custom keymap the destination keymap is filled with the default driver keymap that's it.

I could get it working by modifying the destination keymap directly: /sys/devices/soc/c17a000.i2c/i2c-6/6-0058/keymap Somehow that guy gets overwritten with the default mapping whenever I toggle the custom keymap settings option. I wonder if your source keymap should contain all keys? However that trick with alt+tab just won't work as it then goes in task switcher and just exit it when you release. I'm back thinking how I could improve the driver.

Did anyone get custom keymap working on the latest release?

Tried adjusting file permissions and ownership to something that made sense, still no joy.

Ok so I tried to enable that keymap thing, the UI sees it cause it is enabled but it looks like it has no effect. Was first trying to add just the remap I mentioned above then also the space power thing from the code sample. None are working… Am I missing something?

@Sean McCreary Thanks a lot for your great description of that system. The actual parsing of the keymap files is done there: https://github.com/LineageOS/android_kernel_fxtec_msm8998/blob/lineage-18.1/drivers/input/keyboard/qx1000.c#L917 In that aw9523b_store_keymap function. In there you can see that the parsed keymap is put directly in the mapping array. Therefore you can use modifiers for your keys using the following constants: #define KF_SHIFT 0x8000 #define KF_CTRL 0x4000 #define KF_ALT 0x2000 #define KF_ALTGR 0x1000 I'm

@VaZso I did not read all that last big chunk of text. However some of it gave me an idea. It looks like ATM we have like two profiles QWERTY and QWERTZ. I wonder if we could modify the driver to add more profiles QWERTY and QWERTZ variant that would be compatibly with stock so that FinQwerty and other mods would work the same. I would probably also add another profile that's improved on stock. If this is doable I guess we would have good chances to get those changes committed to the official LOS repository. I'm currently downloading the whole LOS source code to inspect it a