Jump to content

claude0001

Members
  • Content Count

    554
  • Joined

  • Last visited

  • Days Won

    66

Everything posted by claude0001

  1. Do not worry, has happened to me once on LOS 16, too. I did not reasearch the issue, though. Just rebooted. 🤗
  2. 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.
  3. 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 ...
  4. 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.
  5. 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
  6. 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.
  7. 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.
  8. Did you migrate to "testing" keys as I explained (or tried to) here:
  9. 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
  10. 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. 🙂
  11. Never retreat, never surrender! The true spirit of a Spartan. Go, @Slion!
  12. 😄 We'll never fix that bug, I guess ... Keep going!
  13. 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.
  14. 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
  15. 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.
  16. No, I have QWERTZ. And when I hit "[" ("slantedarrow + i") on the keyboard, I indeed get a "[" on screen. I repeat: does this not work for you?
  17. @VaZso, I'm also lost. So, what you say is when you type "slantarrow + i" on your QWERTZ keyboard, you get a "]" instead of a "[" (as yellow-labeled on the keycap)? That's not the case in LOS 16.0. I can type all yellow symbols as printed on the keyboard. So better do not blame @tdm too much.
  18. Sorry, @VaZso, I probably misunderstood. I'm not pushing anyone to do anything. You and Slion seemed to have quite specific ideas what changes in the keyboard code could be test-implemented to see if that would improve things for you. I fear either you find a LOS 18.1 dev who is willing to make those test-builds for you, or you will have to build yourself. The latter process is explained in a very comprehensive and fool-proof (looking at myself 🙂 ) way on the Lineage Wiki. Getting the latest device-specific code for the Pro1 into your build environment is automated by the "breakfa
  19. Going back without wiping should be possible by following the key-migration procedure "backwards", as also described under https://wiki.lineageos.org/signing_builds.html#using-a-script, followed by re-flashing the official recovery and system. Never did that though.
  20. I can confirm that the description is very good. I've been using it to build my own LineageOS 16.0 for some time now, and it worked at the first try! Even if you have some Linux machine around already, I recommend to set-up a dedicated VM with the latest Ubuntu LTS, so as to stick to the recommended building environment as closely as possible. Indeed, because the code is signed, I do not think that replacing only parts of the system is easily feasible if you are currently using an official Lineage build. To replace your official LOS 18.1 with your self-built experimental versions
  21. The link above contains all gesture navigation features in Pie (link). Actually, the more I experiment with it, the more I like the new mode, might just keep it ... 😄
  22. The traditional nav-bar then gets replaced by a single "pill" icon and occasionally appearing (probably context-sensitive) thin arrows to help transitioning to the new interface. I can well imagine that in Android 10, more features were introduced, but basic stuff like e.g. fast task switching by swiping the bottom of the screen works.
  23. Unless you mean something completely different, gesture navigation is available in Pie (and thus in LOS 16.0): Settings > System > Advanced > Gestures > Swipe up on Home Button See: https://www.androidcentral.com/how-enable-android-p-gesture-navigation-system I did enable it for both tests (though I do not use it normally).
  24. On LineageOS 16.0 (build date: 20210815): Can't reproduce #3873 Dragging left-right always switches tasks, flinging to the top closes them. Both in landscape and portrait, irrespective whether keyboard is open or closed -- though open keyboard forces landscape for me, don't know if this can be disabled (would anyone want that?). Can't reproduce #3874 with gesture navigation enabled, opening the gitlab.com search box in the described way does not open an empty nav bar. Firefox here, not Chrome (as in the report). But as you initially wrote it happens in all browsers ... As
  25. More precisely: "Based on the non-kernel-parts of Mobian + Android 9 and Hybris". It is true that some Pro1-specific work (obviously no Pro1X yet) is going on there, thanks for the heads-up. But for the reasons discussed above it still relies on Android 9 and is thus probably not what @shane was expecting.
×
×
  • Create New...

Important Information

Terms