Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


Everything posted by claude0001

  1. In Lineage 16.0, that key combination (Yellow Arrow + Alt) brings up an emoji selector box. Works in all apps I have tested.
  2. 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.
  3. 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
  4. 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.
  5. "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
  6. My latest build (20210815) of LineageOS 16.0, including the 5th August 2021 AOSP patches, is now up.
  7. 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
  8. I too was a die-hard fan of the N900. 🙂 I am quite happy with my hybrid Lineage+Devuan system now, which provides almost everything my N900 could do, but you are right that there are limits (HW accelerated graphics, transparent FS access, ...) because of Android concepts standing in the way. Note that UbuntuTouch comes with very similar limitations: It too is designed primarily as a phone OS and copys some of Andoid's concepts. E.g. apps are individually sandboxed, native "phone" apps and "desktop" Ubuntu software live in separate worlds, the latter running in libertine containers wi
  9. Yes and no. The Pro1 (and, by extrapolation, the future Pro1-X) can be set up as a quite OK always-carry-on GNU/Linux computer. I achieved that using rooted LineageOS + a custom-made Devuan chroot (see this thread for an entry point). Similar results can certainly be obtained using stock Android combined with a solution like Termux if you do not want to root, especially if a Un*x CLI is everything you really need. In fact, if you ordered your Pro1-X with UbuntuTouch you may (hopefully) be good to go pretty much out-of-the-box. None of these solutions breaks the "phone" functions in any wa
  10. Thanks for the suggestion, but no way. I did not install a Google-free LineageOS to then use a Google App that can theoretically record and evaluate everything I type on my phone ... I have given up on that problem for now as it is practically restricted to that one word in K9-Mail, and occurs only with the physical keyboard. Hopefully, K9 will switch to a more modern text input API at some point which should get me rid of this.
  11. Have uploaded my latest build (20210718), including the 5th July 2021 AOSP security patches, after flashing it to my own Pro1 without issues.
  12. The instructions in the LineageOS wiki are really good. Just follow them and make sure not to miss any steps: https://wiki.lineageos.org/devices/pro1/build It is really not that hard. I have been self-building LOS 16.0 without issues for some time now, although I understand next to nothing about the internals of the build system ... Even if you have some Linux running on your main PC already, I strongly suggest to set up a dedicated VM with the latest Ubuntu LTS to stay as close as possible to the recommended environment. Ubuntu Server is sufficient btw. (and much easier on y
  13. That's a known phenomenon. As far I know, there are several ways to fix it, depending on what operating system you run, and whether you are ready to do a full data wipe or not. It's all in this thread: I suggest to contact Dragonbox ( @EvilDragon ), they'll probably know best what to do ... Edit: Dragonbox.de even have note about this on their product page: https://www.dragonbox.de/en/spare-parts-tools/lcds/fx-tec-pro1-replacement-lcd
  14. I'm 100% with you. I remember I uttered that same criticism months ago (though I cannot find the thread anymore): The size of the keyboard feels wrong for me. It is too big for thumb-typing while holding the phone in hand, and too small for 10-finger-typing when putting it on a desk. I, too, could thumb-type much faster on my old N900. For sending the quick text message, I actually rarely use the hardware keyboard. That being said, I also never looked back. The big high-res screen is nice (though not very well suited to watching movies due to the green-tint problem), and there are so
  15. Yes, for me @agent008's entire picture seems blurry. To answer your question: No, I never had this "tilted" focus others have observed and which indeed looks like a misaligned lens to me. My problem seems more like an misbehaviour of the double-action button, where upon pushing the button all the way down, the system changes the focal length once more, instead of just taking the picture. Does not happen all the time, so maybe I'm just pressing the button "wrongly". But I never had that issue with any other camera, so it's annoying enough for me to avoid that button now.
  16. I got many shots like yours when trying to use the double-action (hardware) shutter button: I observed that the camera focuses fine at first (as visible in the viewer) but at the point of pushing the shutter button through, the lens defocussed again. For me, this late defocussing never happens when using the touchscreen ("soft-button") to take pictures (I'm using OpenCamera). So I have pretty much given up on the hardware shutter button for now. Quite sad, as the double-action shutter button was one of the things I liked most about my N900 ...
  17. Unwilling to let go my LineageOS 16.0 setup, I started to compile my own builds some time ago. For the case anyone else still has interest in LineageOS 16.0, I've made them available here: http://findus.zwergenschaenke.net/~puma/linux.html#lineagepro1 As of writing this, the latest image contains the 2021-06-05 AOSP security fixes. I will probably continue to make new builds every month, as long as the sources keep getting patched by the good people at lineageos.org. Although based on the official sources, these builds are "unofficial" in that they are signed with the so-ca
  18. The 2021-06-05 patches have been fully merged into Lineage branches 16.0, 17.1 and 18.1 only today. That was too late for the build bot. It should come next week, I guess.
  19. I get best results when using a Raspberry Pi3 for flashing the Pro1. I had lots of trouble using my normal PCs as well, even though some of them are old pure-USB-2.0 systems. The RPi has a 100% success record up to now. The cable then does not seem to matter much: I have successfully used, both, the official one and some random spare I had lying around. If you have a Raspberry at hand anyway (), just give it a try. The needed Android tools are just an "apt install adb fastboot" away. Edit: Note that the fact that my RPi is version 3 may be important. The Pi3 is the latest versi
  20. In principle, yes. Note, however, that some hardware components are likely to never be supported by open-source drivers within the realistic lifetime of the Pro1. For orientation: The Nokia N900, a relatively popular hacker's phone from 2009 (!), still has only 80-90% of its hardware supported by the mainline Kernel (personal estimate). And that's despite the fact that it originally shipped with an OS that was quite "open" compared to today's Android ...
  21. Well, not quite (as we discussed above). With Lineage you get the Android framework fixes from the AOSP security bulletins, but no patches to the Linux kernel or the binary driver blobs, as these are supposed to be implemented and distributed by the SoC manufacturer. That's what LineageOS calls the "vendor security patch level". As you confirmed yourself, that one is stuck at 04/2020 in LineageOS, too. It must be, as the binary bits are taken directly from Stock.
  22. OK, thanks. I was unsure because, according to this thread, Stock received further updates at least until August last year ... So I get none of these actually included any fixes to the vendor bits. We'll probably have to accept that, I guess ... 😞 Sorry if I am asking obvious things. I was never on Stock, either, so I'm a little disconnected from its development.
  23. Could anyone running the latest Stock look up what its "vendor security patch level" is? I am wondering why my self-built LineageOS (with Android patches from May 2021) indicates a vendor security patch level of "5 April 2020", although I extracted the vendor blobs from a much more recent (Lineage) release. Of course, if even Stock was stuck at that date, this would explain things ... thanks in advance!
  24. Can't wait for Maemo Leste to take over the World. 😉
  • Create New...

Important Information