Jump to content

Slion

Members
  • Content Count

    1,392
  • Joined

  • Last visited

  • Days Won

    34

Everything posted by Slion

  1. I've implemented a new feature in Lineage OS Pro¹'s keyboard driver to be able to use Fn+Tab as Alt+Tab as this is most convenient for multitasking with two thumbs. This thread is to track that issue specifically so please stay on topic. I'm trying to contribute this back to official Lineage repository. Here is my change request on Gerrit: https://review.lineageos.org/c/LineageOS/android_kernel_fxtec_msm8998/+/315155 There was also a pull request on GitHub but that's just going to be closed as the GitHub repositories are just mirrors I guess: https://github.com/Linea
  2. In my case that did not help. Only capslock toggle would.
  3. Can't enter that mode. Is that a driver feature or virtual keyboard feature?
  4. @claude0001 Is that normal the gapps won't show up with my custom build? Does it needs some proper signing to work?
  5. She is a beauty for her age 😃 She looks a lot like mine, sadly she passed a few years ago, she was over 18 years old.
  6. @VaZso Maybe you are missing some packages (apt-get) and that broke your build in a not obvious way.
  7. That's certainly because of that bug where the custom keymap is not loaded as it should. That ought to be fix. Agreed, just needs to be done and tested carefully. That takes time too. Looks like your build is broken somehow. Mine worked on WSL. Though downloading the blobs had to be done over tcpip with adb as it can't be done over usb. Maybe try using another Linux environment or identify your problem.
  8. Does that break your build? If not I would not worry about it.
  9. 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.
  10. 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.
  11. That's what I was telling you earlier. That's the bug. I came to that same conclusion further up this thread.
  12. 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.
  13. @claude0001 Is that normal the gapps won't show up with my custom build? It needs some proper signing to work?
  14. 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.
  15. 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.
  16. 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.
  17. @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
  18. 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 🤣
  19. @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
  20. There is one on QWERTY. No self respecting French is using QWERTZ 🤣
  21. 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
  22. 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.
×
×
  • Create New...

Important Information

Terms