Jump to content

claude0001

Members
  • Content Count

    408
  • Joined

  • Last visited

  • Days Won

    50

Everything posted by claude0001

  1. 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?
  2. @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.
  3. 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
  4. 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.
  5. 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
  6. 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 ... 😄
  7. 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.
  8. 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).
  9. 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
  10. 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.
  11. 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
  12. 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
  13. 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
  14. 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 ...
  15. 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 ...
  16. 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.
  17. 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.
  18. 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.
  19. In Lineage 16.0, that key combination (Yellow Arrow + Alt) brings up an emoji selector box. Works in all apps I have tested.
  20. fastboot is extremely picky about the USB connection. Try different ports and cables. If you are on Windows some missing USB driver required by fastboot (but not by adb) could also be the issue (source). I have no Windows so I can't help much with that. I have found a Raspberry Pi (3) to be the most stable solution for flashing my Pro1. It never had any connection issues (as opposed to my PCs) and adb and fastboot are trivial to install using the Raspbian package management.
  21. Short answer: Why not? 🙂 Long answer: I have set up a quite complex system with LOS 16 and a GNU/Linux (Devuan) running in a chroot, with multiple partitions, automatically starting servers, and shared data folders. To realise that, I use all kinds of tricks to work around Android restrictions. I fear that at least some of these hacks would not work on more recent releases because of changes in the Android security mechanisms. So I would probably have to learn new ways, which is bad because I'm lazy ... 🙂 LOS 16 has a nicely-integrated and low-profile root-management solution
  22. Related to the other (LOS 18.1) thread, @EskeRahn mentioned: I have my 20210815 LOS 16.0 build running on my Pro1 since yesterday. Just checked: Charging works as expected both "fast" (from the wall plug) and "slow" (from my PCs USB port). It was not below 50% before I did the test, though.
  23. "Mainline" refers to using the upstream Linux kernel with open-source drivers. That's what I think Mobian does. To this date (and to my knowledge), there is no OS for the Pro1 that uses upstream Linux. All available systems use the vendor-supplied Linux kernel of Android 9 ("4.4.153-perf+") with the proprietary (and closed-source) device drivers. That includes UbuntuTouch and SailfishOS! The latter actually run a slimmed-down version of Android 9 in a container and access the hardware via Android compatibility layers (libhybris). I suspect the situation will be quite similar for the Pro1
  24. My latest build (20210815) of LineageOS 16.0, including the 5th August 2021 AOSP patches, is now up.
  25. Well, in that case there is really no need to go for a Pro1(X). The built-in keyboard is pretty much the defining feature of the device. If you're going to use a separate keyboard anyway, you'll find devices that are cheaper while having better mainline Linux support. Running GNU/Linux in a [ch,p]root of Android takes care of that. Networking is managed by Android and just works (tm) in the chroot system. For Termux, there are even extensions to use the Android location services from within GNU/Linux-programs. But, yes, UbuntuTouch can also be a solution (although GPS does not seem to
×
×
  • Create New...

Important Information

Terms