-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Boot image improvements for keyboard support #28
Comments
As for the F and Sym keys, those are defined here I believe (for lineage, but that dtsi should also be used for sfos somewhere) https://github.com/tdm/android_kernel_idealte_msm8998/blob/lineage-16.0/arch/arm/boot/dts/qcom/msm8998-qrd-skuk-QX1000.dtsi#L422 |
From Discord:
|
Simultaneous key presses are now implemented thanks to @netman69 and @NotKit (and maybe others too):
I think The F(x) key is supposed to be LEFTMETA in |
Is all this ok now and can be closed @Kabouik ? |
I think it would still be good to have the About sticky modifiers, I don't know if that would be easily doable. On the one hand, some users would surely prefer it from what I heard of different chat channels, but on the other hand the keyboard works quite well now thanks to @netman69's multiple keypresses. About dead keys, it's hard for me to understand what's wrong. I opened a couple issues about it on TJC on this topic but failed to really narrow down where the issue stems from. When using a xkb variant with dead keys (for instance the last one in the First and second paragraphs are mostly kernel improvements, and the third paragraph may be deemed out of scope, so maybe you would prefer if we close the issue here and I post this somewhere else? Let me know. |
BTW, I already mapped the F(x) key to the home button action, which i think is pretty useful |
That may be a feature that I did not notice yet because I'm still in 3.3 at the moment. It's fixed at kernel level, correct? I could flash just the new kernel without upgrading to 3.4 yet. What are the keycode and keysym you associated with the key to make it show home? |
No, its just a simple config, so you could enable it on your build, see 7297042 The Fx key emits a leftmeta event, so i map it to the home event instead. |
Hum, could you please share your kernel version? My |
You can use evdev_trace -t to trace key events from sailfish |
That is great, thank you. Turns out those my Those are probably related to XWayland more than the port itself. So leaving this issue open depends on whether sticky keys and dead keys/compose are in scope for the port. |
xev
],Toggle SFOS virtual keyboard with Sym key; could be used in combination with special vkb layouts from Openrepos, like just some special characters, just text prediction if xt9 is installed, emoji keyboard, etc. — this one might be difficult since I assume it would also need some coding to make SFOS recognize the keycode and toggle the virtual keyboard.[Probably not going to happen, the Sym key will probably be used as a more convenient key for/
and?
on first and second levels.]Any other ideas?
Additionally, it seems dead keys do not work in SFOS, but they do work in Ubuntu chroot, so I guess it is not a problem with the kernel nor the xkb layout, but rather a SFOS limitation. I'm leaving it here just in case.
The text was updated successfully, but these errors were encountered: