Jump to content

claude0001

Members
  • Content Count

    408
  • Joined

  • Last visited

  • Days Won

    50

Everything posted by claude0001

  1. I agree. The point is to comfortably switch apps while keeping your thumbs on both sides of the keyboard and not having to use the touch screen. Yes. I had added back the "+" manually and it is building now ... 60% and going strong. I expect a flashable LOS 16.0 with Fn-Tab functionality in 2 hours or so ... πŸ™‚
  2. @Slion, I think you introduced a typo in the latest revision of the patch. Build fails with ../../../../../../kernel/fxtec/msm8998/drivers/input/keyboard/qx1000.c:1709:41: error: expected ';' after expression size = sizeof(struct gpio_keys_drvdata) ^ I think that line should stay like in the original code: size = sizeof(struct gpio_keys_drvdata) + pdata->nbuttons * sizeof(struct gpio_button_data); You probably deleted the "+" by accident in the latest edit.
  3. Works for me with AOSP keyboard on LOS 16.0. Others report it also works on LOS 18.1. So maybe the feature can be switched on/off somewhere. Do not know where, though ...
  4. The patch (patchset 6) applied cleanly against my LOS 16.0 tree. Just started the build ...
  5. We'll see. I think the proposed behaviour is definitely useful. If the patch does not apply cleanly, I'll try to backport it. If all goes well, I'll start a LOS 16 build with your new driver code in the evening and will report tomorrow.
  6. That would make a lot of sense, indeed. If the patch gets accepted in the kernel branch, would it be in effect for all LOS branches (16.0, 17.1, and 18.1), or just for 18.1? I could test against 16.0 by applying the patch to my local copy of 16.0. Should I?
  7. I should add that this does not work in all apps. E.g. sticky shift works in Firefox, K9-Mail and 1+Term, but e.g. not in ConnectBot or CollaboraOffice. So probably Apps can opt-in and out of that feature.
  8. No idea. I use the normal AOSP keyboard shipping with LOS 16. I suspected it was a feature of the latter, but at first sight I can't find any setting related to that. When I hit-and-release "Shift" once (without any other button), I enter "normal-sticky" shift, i.e. the next letter is capitalized, the following ones are lower case again. This is a quite common accessibility feature to enable use of a keyboard with a single finger (for e.g. disabled people). Hitting "Shift" twice makes capitalization "super-sticky" for me, meaning all letters are entered as capitals until "Shift" is p
  9. That's different. When you write all caps irrespective of the CapsLock state, you are in "Super-Sticky-Shift" mode. One enters that by hitting Shift twice (without pressing any other key). Disable by one more Shift press. That's a feature, not a bug, I guess. πŸ™‚ The phenomenon @Slion mentioned is an inversion of CapsLock. I.e. with LED on you type minor letters, with LED off capitals.
  10. Why am I not surprised you are using a different filesystem than everyone else? πŸ˜‰ Good luck with the new build!
  11. Do not worry, has happened to me once on LOS 16, too. I did not reasearch the issue, though. Just rebooted. πŸ€—
  12. I was not aware Gapps could not be installed on a custom build. I have no Gapps, though, so I am the wrong person to ask. The only additional zip I sideload is Addonsu, and that works normally.
  13. You are probably determined to do it your way, which is fine. However, did you even consider to just use the provided QWERTZ layout as it is? All the special characters in your example sentence can be typed using the standard layout in LOS 16.0. "ΓΆ" is available as a key of its own. "Γ­", "Γ©", and "Γ‘" can be typed using the dead-key function of "Β΄" (i.e. "Β΄" followed by "i", "e", or "a"). Just sayin' ... Typing french is indeed more complicated, as only "Β΄" and "Λ‹" have a dead-key function (on LOS 16, that is), not "^", which is a pity ...
  14. That works on LOS 16. That was discussed a few days ago. Seemingly the emoji palette is not enabled by default on LOS 18.1. It is a setting of AOSP keyboard.
  15. As far as I know, the driver in Lineage has been made different from the one in Stock for a purpose. And it has worked quite well for many people across 3 Lineage releases now. You seem to have a very specific use-case (that I still do not understand), which is totally fine. But please do not blame everyone else for being happy with things as they are. If you propose changes, please do not look only at your special case. Not that I understand much of the discussion, but the suggestion of @Slionto add one or more additional keyboard profiles to fulfill your needs seems reasonable and would
  16. Do what you think is right for you. I suggest to just set up a virtual machine with Ubuntu LTS. It works. Running Ubuntu (or whatever other distribution relying on systemd) in a chroot is not trivial by first priciples of systemd.
  17. OK, if you wipe it should boot. Somehow the equivalent of: "Nuke the entire site from orbit!" Obviously the only way to teach 'em manners ... That it takes ages after a flash is normal ... or, at least, I got used to it.
  18. Did you migrate to "testing" keys as I explained (or tried to) here:
  19. First things first: Congratulations! You have just build your own operating system for your phone. May zombie-apocalypse come, you will be among those who rebuild the world. Time to open a beer or something. It's interesting that you have a much more powerful CPU than mine but still get similar build-time (all assuming the amount of code is similar from LOS 16 to LOS 18). Mine is an ageing Core-i3 3220T, with only 3 of its 4 (hyperthreaded) cores assigned to the VM. It is my home server, which I use because its the only machine that runs 24/7 anyway. And, as the server does many othe
  20. No idea, honestly. I build only once per month and wipe everything in-between as I am limited in disk-space. I had a build fail once due to it running out of space after I did not clean out the previous one ... A fresh sync-and-build takes 10 ... 12 h for me (3 VM cores, 6 GB RAM), approx. 4 h of which it spends downloading all the stuff (100 Mbit/s). I honestly do not care about the speed. I start things in the evening and have my image when I wake up in the morning. πŸ™‚
  21. Never retreat, never surrender! The true spirit of a Spartan. Go, @Slion!
  22. πŸ˜„ We'll never fix that bug, I guess ... Keep going!
  23. lol. Seriously. As I said, fire-up a VirtualBox (or whatever hypervisor you prefer) and install Ubuntu LTS in it. Make sure to assign enough disk space, 200 GB is absolute minimum. Much more is needed if you want to make several builds in a row (much faster) whitout wiping everything in-between.
  24. I most probably simply do not understand enough about how re-mapping works since I have never done that. But from a dummy user perspective: When (on LOS 16, qwertz variant with qwertz layout) I type "slantedarrow + i" (which is the key labelled "[" in yellow), I indeed obtain a "[" character on screen. According to @VaZso's research, I would expect to get the neighboring "]", but I don't. In Android Apps, all yellow-symbol keys work as expected for me. That said, I have had issues forwarding those to remote servers using many VNC client apps. So maybe at some level there are bugs, ev
  25. I maybe too tired to understand the motivation behind this. But I do get now you discovered a bug which is not apparent if one uses QWERTZ-layout-on-QWERTZ-variant and/or does not use custom keymaps? If so, the bug should be present since LOS 16 indeed, as the respective code in qx1000.c looks identical.
×
×
  • Create New...

Important Information

Terms