Slion

Does that break your build? If not I would not worry about it.

I understand your concerns but: 1. Those functions are marked inline if the compiler does its job there will be no actual function call. 2. Even if they are not inlined there well be absolutely no impact whatsoever. It's not like they are being called 1000 times a second. Even that would not be a problem though. Thanks for the code review though, I appreciate the effort.

Would be nice to find a way to reproduce this so that we can get it fixed. Was just trying to reproduce after reboot but no joy so far.

That's what I was telling you earlier. That's the bug. I came to that same conclusion further up this thread.

Did you guy ever get stuck in a mode where capslock is inverted? Like when capslock is on you get lowercase and when it is off you get uppercase. I'm testing my modified driver but I'm pretty sure I did not do break that as I did not touch handling of shifts or caps.

@claude0001 Is that normal the gapps won't show up with my custom build? It needs some proper signing to work?

Is there a way to adjust Home and Task switcher gesture sensitivity? In the settings you can adjust back gesture sensitivity for left and right edges but I would like to lower the sensitivity of the swipe from bottom gesture. When in landscape with keyboard open it triggers way too easily. I'm guessing this was never tuned to be used in landscape.

I wonder if it depends on your virtual keyboard app. Right now I could get it to show up with the default keyboard. I'm pretty sure earlier it did not work with AnySoftKeyboad.

I wonder if this could be related: https://review.lineageos.org/c/LineageOS/android_device_fxtec_pro1/+/314887 Maybe there is a fix coming up.

@Sean McCreary I've created a kernel pull request though I'm pretty sure that's not supposed to be happening on github but somewhere in Lineage gerrit. I have to take a look at the contribution process: https://github.com/LineageOS/android_kernel_fxtec_msm8998/pull/1

Though I used it for years, old AZERTY really sucks. However I'm a big fan of the new AZERTY standards and have converted most of my keyboards. They are so convenient for international French like myself you can easily type in most every European language without having to look up ASCII codes 😁 Shame that nobody seems interested in adopting the new standards. French people are creature of habits and do get stuck in their old ways even though they don't make sense… so it seems 🤣

@VaZso To come back to my questions it seems your answers are as follow: Which hardware keyboard do you have? Qwertz Which keymap are you trying to use? Qwertz Which layout do you want to use? English US Which languages do you want to type in? Hungarian Your configuration is convoluted because you are trying to use the qwertz keymap together with a qwerty layout. For some keys the keymap makes the assumption that you are using the matching layout notably when the Fn key is issuing logical modifiers when associated with another key. My advise for the time being i

There is one on QWERTY. No self respecting French is using QWERTZ 🤣

I guess you won't those issues until you start using it as daily driver which is not my case. It's also off topic on that thread. @EskeRahn you could move that somewhere. @Noob consider reporting that issue there: https://gitlab.com/LineageOS/issues/android/-/issues?scope=all&state=opened&label_name[]=device%3Apro1

The later, just driver tweaks.

We ought to fix that, kinda useful I find.

I'm not sure we understand each other. Keymap: is the driver scancode mapping you have two option qwerty and qwertz you should set it to match your actual hardware. Layout: is the android setting, french, us international, german, english and so on. Look back at the questions I was asking and try to answer them again.

Again AltGr is Sym

Does anyone knows why alt does not bring up the emoji keyboard on LOS like it did on stock?

@VaZso I was like you when I first looked at the LOS keyboard driver seeing how it was not compatible with stock. However I see now that stock was really broken and that's why solutions like FinQwerty was needed. Now LOS driver fixed that by being compatible with Android built-in layouts so solution like FinQwerty are not so obviously needed now. Which hardware keyboard do you have? Qwerty or Qwertz? Which keymap are you trying to use? Qwerty or Qwertz? Which layout do you want to use? US international? Which languages do you want to type in?

I already have a first draft of that nf+tab as alt+tab feature. It should have no impact on the rest of the driver functionality. Only thing it does is let you use fn+tab exactly as alt+tab.

No it does not, I'm not sure how you are reading this from that code sample. That code is responsible for releasing a forced AltGr modifier. Modifiers are said to be forced when they are applied by the driver as part of the defined keymap as opposed to being applied because the user actually pushed that modifier key. This driver can generate logical modifiers input that do not correspond to physical modifiers input. I believe this was done for improved app and layout compatibility and mostly used by the QWERTZ keymap. So when you press Fn you will never get a key event at the application

I do understand AltGr, I use a French keyboard 🙂 RightAlt is AltGr and is mapped to Sym in our driver, key index 24 in the default keymap arrays. You can try it together with US international layout on your QWERTY keyboard it works as it should.

Nothing new here I was doing that back in 99 already 😁😇

You misunderstand me. I was talking about the custom scancode keymap from keyboard advanced settings, not the kcm files.