claude0001

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

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 ...

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 ...

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.

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.

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.

In Lineage 16.0, that key combination (Yellow Arrow + Alt) brings up an emoji selector box. Works in all apps I have tested.

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.

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

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.

"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

My latest build (20210815) of LineageOS 16.0, including the 5th August 2021 AOSP patches, is now up.

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

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

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

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.

Have uploaded my latest build (20210718), including the 5th July 2021 AOSP security patches, after flashing it to my own Pro1 without issues.

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

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

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

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.

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 ...

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

*duck* ...

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.