Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


Everything posted by claude0001

  1. 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
  2. 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. 🙂
  3. Never retreat, never surrender! The true spirit of a Spartan. Go, @Slion!
  4. 😄 We'll never fix that bug, I guess ... Keep going!
  5. 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.
  6. 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
  7. 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.
  8. 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?
  9. @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.
  10. 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
  11. 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.
  12. 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
  13. 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 ... 😄
  14. 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.
  15. 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).
  16. 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
  17. 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.
  18. Everything you write is correct @VaZso. However, I also feel Fxtec could have stressed more clearly that, while they offer an unlocked phone, they choose not to follow an open-hardware approach. As far as I know, they never did that, probably in order not to damp too much the early enthusiasm in the community. Instead, they emphasized a lot the "other OS" option of the Pro1 (which, actually, means just "easy access to the bootloader"). They do so even more with the Pro1-X. Combined with the fact that even people with much experience in running Linux on servers and desktops often know litt
  19. Do not get me wrong: There is work being done on mainlining the Pro1 (see e.g. this). The people doing that work deserve all our respect. Its also nice that Fxtec provide devices to the devs for reverse-engineering (they plan to do that also for the Pro1X). But make no mistake: All we have up to now is proofs-of-concept. It would take a long time before any mainline kernel could be used for running the Pro1 in a practical way (i.e. such that it could actually be used as a mobile phone!). In fact, experience tells that this can easily take so long that the hardware becomes obsolete before
  20. Up to now there is no Linux distribution that can run natively on the Pro1. The problem is that mainline Linux support for the Pro1 (and even more for the Pro1X) is in a quite early stage, so using an upstream Linux kernel on the device is not practically possible. Unfortunately not. Ubuntu Touch (like SailfishOS) works by running a slimmed-down version of Android 9 (including the vendor-provided Kernel and closed-source driver binaries) under the hood. It then accesses the hardware functions via an Android compatibility layer (hybris). That way, only (GNU/)Linux apps specifically-writ
  21. Thanks for the explanation. That sounds plausible. Still, for many PC systems (think: laptops) there is no easy way for the user to (temporarily) decrease the amount of devices on the bus. So, effectively, randomly trying different ports/devices is still the only option ...
  22. You are absolutely right! I also use the AOSP keyboard and I can indeed enable/disable the emoji selector using that setting, though I think it was enabled by default in my LOS 16. @Noob: Something to check, maybe ...
  23. As I say: RPis are cheap and work well for me. I keep one around just for the purpose of flashing my Pro1 . I would avoid Model 4, though as that has different USB (3.0) hardware.
  24. If by "stability" you mean that of the connection: I think the problem is mainly the USB hardware, not the OS of the PC. I think in any Debian-based Linux distribution you can install the Android tools using a simple sudo apt install adb fastboot that would include Ubuntu, too.
  25. Sorry, I do not know anything about that. I am no Android power-user, I just want the OS to run the few apps I need to make it through the day. LOS 16 fulfils that requirement. I compile the upstream LOS 16 sources following the instructions in the LineageOS wiki. The only modification I do locally is to enable AGPS.
  • Create New...

Important Information