VaZso

I don't really understand the above. Do you mean to only use a modifier when the remap of that key is not defined (in fn array)?

I am asking because I don't know exactly how this system (Gerrit) work or what related functions it may has. Generally what I wanted is to do something which I can use in a way I would like and what is also suitable for everyone. ...and you are right, what is also interesting would be ctrl, alt and also sym as additional modifiers to reach a maximally custoizable state. ...and I am agree it is not a competition, simply these and additoional features would be really good to have. Also, "custom keymap" option has disabled other options when custom keymap file exists even if i

It is okay if you could keep all "features" and extend them in a way of being more customizable but not restrictive. What should I do with the CR? May I ask you what are you planning to do more detailed?

Isn't it is what I have done here? Okay, currently if does not remap "ctrl" and kernel interface may use a similar method like what "keymap" interface does (so x:y:z), but it remaps fn_l, fn_r, F(x) keys and 0x00 will keep default behaviour. Also, it has an option to remove special behaviour of fn key currently has as opt out, so special key transformations may also be enabled or disabled which could also make stock behaviour possible by disabling it and setting fn_l and fn_r the same as in stock Android.

I find it really interesting...

Yes, but it may really worth a try as it seems it may cause problems. Next time I will start with this.

No, sideloading my own build over my own build. I think it may have caused my problem above as I have forgot to install the recovery what my self-compiled build provided. So official LineageOS 18.1's recovery is currently installed on that device and it can be used to sideload my own build but I could not get it to boot without a factory reset after every new builds I made. So I haven't tought it as a cause but based on your comment I suspect I should also update to that recovery, thanks for the suggestion. I have found after sideloading LineageOS, I have to reboot ba

Do you mean you have used WSL (Windows) environment for compiling and now you would like to move it under VirtualBox and a Ubuntu inside? What do you expect from it? Increase of compiling performance? I would think the very same source tree may should work but I don't know. However, somehow I could not even sideload LineageOS of my own build without doing a factory reset. Do you nhave any ideas what may I have done wrong? I have installed my build, then Magisk and MintTheGapps and did the same thing after sideloading the new build. However, it seemed to have an endless

That is perfect, thank you - I think that is why it can be used in .kcm files as FUNCTION 🙂 ...but that also mean this should be used in .kl, so thanks again. Yes, I have used them for slant arrows. I think no - key 195 and 196 may remain intact (unused) but keyboard driver may report 464, so I should do the map of: key 464 FUNCTION ...at least this is what I thought it would work. In the driver what I am worked on, there is a variable which defines the scancode of each function keys present (so left arrow, right arrow and f(x) key). This variable can be set using

Thanks. I have remembered this comment but not where I have read it. Also, I don't know the exact way of Android to Linux keycode conversation... So, if I understood correctly, the Linux keycode of KEY_FN (434) is passed to the Android keyboard handler which does not have anything associated, so it simply drops it. Using the way described in your code review, if I would define similarly to your "key 154 APP_SWITCH" define, it would associate "key 434" with... something. Should that "something" need to be a deeper defined thing or am I allowed to simply define "key 434

Fine, thanks. My head is not the best as I have slept too few hours (and tomorrow I am going to travel and get up early), but do you know more about the reason why import_report_key() function drops KEY_FN? I have found that issue but forgot to look at it and also it was mentioned here - maybe you or somebody mentioned it a few days ago.

Dear Members, I have tried to do some modifications on Pro1's keyboard driver and settings UI under LineageOS 18.1 For details, please look here: Compiled system can also be downloaded here for a while in case someone would like to try it. Be aware, this is a custom build and it will definitively not work applied on an official LineageOS build without doing a factory reset. The keyboard driver-related changes were pushed here: https://review.lineageos.org/c/LineageOS/android_kernel_fxtec_msm8998/+/315281 UI-related changes were pushed here: https://review.l

You are right, it could be done in a bit more beautiful look or even provide an additional "very special area" another button. However, I am not familiar with Android programming so I am not prepared to do something like this. I was happy to make it work the way similarly that of existing options. However, for most users, there is no need of entering advanced settings, so I hope it should not be a really big problem as it also works the same way as before without doing any modifications on these options. Also, others may also use it as a base and do further modifications - I am

Yes, it seems to be yet to done.

I have uploaded temporarily the update file here. @EskeRahn, @Slion and others who may have chance for it - could you please try it and tell me if you find anything which could be improved? Edit: Naturally, additional layouts (key arrangement) can also be applied more easily.

I have made a lot of keyboard-related changes on the code, now I will try to summarize them. Also, I have tried to reach a state what probably all of us may find useful and also original working can be kept in case someone does not need additional features at all. Driver-related changes I have initialized some additional virtual nodes of keyboard driver's kernel module where driver's behaviour can be changed. Some additional settings were necessary to make them accessible to system UI. Also, I have borrowed some of the ideas like what @Sean McCreary has already done. Th

As far as I can see, it supports multiple flags (but currently FN is not among them) and somehow it does not automatically load custom keymap, it can only loaded through the kernel module interface. Also, it needs root access.

Nothing really special, it tries to use fn + mostly non-alphanumeric characters, so USA layout of [];'\/-= are all need to be used together with a modifier. The solution in keyboard driver uses another layer of emulated keypresses with the help of an array containing these keys. (So it can also say you pressed ctrl+c when fn+k was pressed and alt+j when fn+a was pressed or even ctrl+alt+z when you press fn+r where fn is the slant arrow.) This array was filled with really mixed AltGr, Shift or none additions of the base keypresses. As there are no modifiers applied or if there is,

Honesty I don't know what is this layout good for a QWERTZ unit. I gave up on finding out if it has any real value as it does not really seem to be usable at all for me (not only that one button)... Currently I am working on a modification of keyboard driver and settings UI which will allow us to set a lot of features and setting up also slant arrow and F(x) key as any modifiers (basically anything) and even unexposed mode, so I would like it to fit for all use cases... Basically kernel interface is actually working, menu items are there with appropriate options, I still have to lo

Right, this also works here (that was I ran into).

I have experienced it again on LineageOS today. CapsLock was off and it has started writing capitals. Changing CapsLock state had no offect but pressing and releasing shift had - it stopped doing it after I have pressed it once. I don't know if it missed a release state or what happened anyway but here is official LineageOs 18.1 running on previous build (not the actual latest).

Thank you. 18 years are pretty good which is only possible if her health is good and also her owner takes car of her. Sad she has passed but I think she had a good / valuable life. My cat is really clever and patient (as she was in her entire life) and her eyes, ears and brain are still healthy. She had an accident with my dog years ago and her spine has injured majbe around 6-7 years ago or so and sometimes she limping for one of her rear legs, but sometimes it can not really seen depending on maybe a bad jump. She don't really jumps anymore (only when it is necessary), but

Yes, it is. Maybe something does not run or not in the right time... Right. Also it checks for the existence of custom keymap file, and if so, it disables keyboard-related options (so not only if it was enabled, but also if it exists). I think it was in use during testing and didn't really take much attention otherwise. No, everything was fine except the filesystem. It checks for a directory using a method which is not supported under certain filesystems (but only a few). Now it compiles since about 3 hours I think, so it will go through if it does not run out of sp

I think it has something to do with my local filesystem which I think it may not support "d_type == DT_DIR" check which the utility would use... It seems to get a bit complicated... :S I will probably have to make a filesystem in a file of maybe around 200GB, mounting it as a loop and starting it over again... my SSD will be "very happy" after I go through it... What is the final size of LineageOS after a finished compile?

I feel a bit better as I have created a keymap file which I can load through kernel driver, however, I had to rewrite .kcm file to use AltGr instead of fn and also use AltGr in keymap file because keyboard driver currently does not support passing "FN" as function key. However, my custom layout works that way. It is still not a final solution as somehow it does not load it upon boot (I have to run it manually) and a rootless solution would be much better. Anyway, I have looked into the code and adding some options to advanced keyboard settings or adding physical layouts are seem