Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


Posts posted by claude0001

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

    1 hour ago, _DW_ said:

    But the fact ubuntu touch works means there is a starting point I guess

    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-written using libhybris can have access to all hardware functions (like e.g. GPU acceleration) and subdevices (modem, wifi, GPS, ...).

    Many "real" Linux distributions targeting mobile devices explicitly reject the libhybris approach for various reasons, one of them being that using such workarounds does not help upstream Linux to improve.

    That said, there are ways to use standard Linux distributions (but without their kernels) in a chroot of Android/Lineage. As also in this case, the Android Linux kernel is used, there are limitations regarding hardware access and GPU acceleration. But if those are acceptable, one is able to use almost the entire software ecosystem of the chosen distribution in parallel to Android/Lineage apps. See the linked thread for an entry point on the topic.

    • Like 1
    • Thanks 4
  2. 51 minutes ago, VaZso said:

    So if you (or your PC) share the same BUS between several devices, then it also needs time to serve those devices.
    So it may also add more or less delay to your communication which the device will or will not tolerate.


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

  3. 7 minutes ago, brunoais said:

    Is ubuntu also stable enough for fastboot?

    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.

  4. 17 hours ago, Slion said:

    I'm assuming it still does not have proper dark theme support and built-in gesture navigations which to me are major motivations for switching to LOS

    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.

    • Like 2
  5. 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.

    • Thanks 2
  6. 1 hour ago, Slion said:

    Why do you stick to LOS 16

    Short answer: Why not? 🙂

    Long answer:

    1. 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 ... 🙂
    2. LOS 16 has a nicely-integrated and low-profile root-management solution: addonsu. Not that I distrust the Magisk developers, but I like the idea of not relying on a (imho quite bloated) third-party tool for something as mission- and security-critical as root access. addonsu is not compatible with later Lineage releases -- as far as I know precisely because of said changes in the Android security mechanisms.
    3. Do not forget that also LOS 17.1 and 18.1 are "based" on Android 9 in that they also still use the Linux kernel and vendor driver blobs of Stock. So the advantage of using a more recent version may not be all that big, at least on the low level. In theory, one could even imagine that with the divide between front- and backend software becoming larger, bugs in the drivers could be exposed that never appeared in Android 9.
    4. Last: My LOS 16 is of course not "the same" as stock. I use Lineage because it allows me to have a Google-free phone (no Gapps here!). That was the reason why I installed it in the first place. And as long as it still gets security-patched upstream, I see no reason to switch.

    Do not get me wrong: If LOS 17.1 or 18.1 works well for you, use it and be happy! I just provide my LOS 16 builds to give others the option to keep using it with relative ease, now that the official builds have been disabled. After all, the freedom of choice of your OS was one of the distinctive features of the Pro1 ...

    • Like 3
    • Thanks 3
  7. 17 hours ago, ChillPC said:

    A device with a keyboard running natively linux and having all gsm functionalities, I only found the pro 1(x) for that ^^' Also, Ubuntu Touch would be already enough for me. And Mobian isn't a mainline distro technically speaking.

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

    Again: If running upstream Linux is important to you, the Pro1(X) may not be the device you want.

    17 hours ago, ChillPC said:

    but if a version of the linux kernel is working with the device, next should be too I think.

    You are right in principle. The problem is that we do not have the device drivers open-sourced. As you certainly know, Linux has no stable driver interface by design. That's why we cannot easily compile our random favorite kernel and simply plug-in the vendor-supplied binary blobs (even if that was legal, of which I am not sure).

    Fun fact: With the N900, we have been camping on Kernel 2.6.28 for more than 12 years because some drivers could never be open-sourced by Nokia. 🤣

    17 hours ago, ChillPC said:

    Any old laptop will run linux nicely and the main difference is that phone use an arm ship

    Maybe you are too optimistic indeed. 🙂

    I am no expert, but I think the problem with phones is that there is no standard system architecture like for x86 PCs. That's why OS's need to be specifically adapted to every new SoC, even if the CPU stays the same.

    • Like 3
  8. 22 minutes ago, ChillPC said:

    I wouldn't be too bothered to bring a [...], keyboard [...]

    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.

    22 minutes ago, ChillPC said:

    The only challenge for using linux instead of android is gsm network (which ubuntu touch seems to get right) and maybe gps navigation (I usually use OsmAnd), that's pretty much it.

    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 work yet in the (835-) Pro1 port). In other news: I also like OsmAnd~! 🙂

    22 minutes ago, ChillPC said:

    I also plan to migrate to Mobian as I like to go "Vanilla"

    As far as I can tell, mainline Linux support for the Pro1/Pro1X is still quite far down the road. I would not count on it. Again, I think there are better-suited devices if that is your plan ...

    22 minutes ago, ChillPC said:

    One thing that I hope with linux is that it will not be unusable or a security nightmare in few years like it is with phones not supported by manufacturer anymore.

    Well, actually ... the Pro1 (the original 835 model, again) effectively isn't supported by the manufacturer anymore (last Android 9 update was over a year ago). But that is why we have Lineage ... 😄

    • Like 2
    • Thanks 1
  9. 6 hours ago, VaZso said:

    Although Pro1-X will also come with Ubports, so some kind of a Linux ecosystem will exist, nowadays one have to have an Android phone because of other services, and as it is a very restricted system, it seems for me the very same well-working environment what N900 had is not working anymore if you don't want to bring another device which runs the rest of the applications you need.

    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 with no direct HW access (pretty much as in an Android chroot).

    If you look for an OS similar in architecture to that of the N900, Sailfish is probably your best option, wich I definitely should try at some point. However, Android App support is problematic there, as there is no official support, and I do not know about status of porting to the Pro1-X.

    • Like 4
  10. 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 way.

    That being said, I do not believe any phone can truly replace a laptop. The Pro1's keyboard is not bad, but comparing it to a laptop keyboard is clearly overstretching things. Also, while the Pro1(-X)'s screen is large for a phone and has more than Full-HD pixel resolution, it is still tiny compared to even a typical laptop display -- smaller than my default xterm window size! Even pure terminal tasks would be very tyring for your eyes through a full work day -- let alone using graphical apps intended for desktop displays. 

    My Pro1 works fine as a kind of "emergency" Linux-PC, when I happen to be far from my usual workstations. But to use it as a full replacement, I would need to bring so many peripherals with me (USB-dock, full-size keyboard, mouse, full-size-display) that carrying along my trusted (and much more powerful) X250 seems much easier after all ... 😉     

    • Like 5
  11. 2 hours ago, osmosoom said:

    Use gboard

    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.

  12. 6 hours ago, pebert said:

    can someone help me setting up the development environment for building lineage OS for Pro1?


    The instructions in the LineageOS wiki are really good. Just follow them and make sure not to miss any steps:


    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 your VM), you won't need any GUI tools.

    Make sure to assign enough disk space, though. Although the final ROMs are only ~600 MB, the sources and building process easily consume around 150 GB. The build will fail if it runs out of disk space. CPU and RAM are less critical than the wiki suggests: My VM has only 3 cores and 6 GB. Builds take 10-12 h, including download of the sources over a 100 Mbit/s line.

    • Like 4
    • Thanks 1
  13. 23 minutes ago, fxtec11 said:

    So I bought the replacement screen from DragonBox shop and replaced it. The new screen only seems to register touch press on the flat area and not on the curved part when first pressed. However, if I start the touch on a flat part and move the finde to the edge over the curved part, it is still recognized.

    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

    • Like 1
    • Thanks 1
  14. 52 minutes ago, Noob said:

    I mean, it's so big that I can't reach all the keys with my thumbs keeping my hands in the same place so I have to move my hands left and right like I'm playing a piano, which feels clumsy and increases the risk of dropping it (especially with both hands in the middle of the phone).

    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 many "serious" applications that imho simply do not work with an on-screen keyboard: programming, shell-scripting, remote desktop, etc.. Those are the reasons I got my Pro1 for, not for casual texting.

    • Like 2
  15. 9 hours ago, Jacob_S said:

    Looking at it closer, the left side also seems blurry.

    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.

    • Like 1
    • Thanks 1
  16. 42 minutes ago, agent008 said:

    I never could figure out how to get the camera to focus properly.

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

    • Like 1
    • Thanks 1
  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:


    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-called "test" keys. If you plan to dirty-flash them over an official LOS 16.0 build, you have to first switch keys as explained by @Sean McCreary in this post.

    I dirty-flashed over the last official LOS 16 several weeks ago and am using my builds without any issues since. That being said, the usual disclaimer applies: Flash this at your own risk! These builds may turn your Pro1 into Skynet, kill your pet, or set your house on fire. You have been warned. 🙂

    • Like 4
    • Thanks 4
  • Create New...

Important Information