Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


Posts posted by claude0001

  1. 6 hours ago, VaZso said:

    Right, but they planned that Pro1-X will be 100% identical to Pro1 inside

    That's a good point. You are right that the Pro1 could -- technically at least -- have had the upgrade to the Pro1X's Android 10 for "free" if the SoC thing had not happened.

    However, it is also true that updates of stock Android 9 stopped long before the mainboard change. As far as I know, they ran into trouble with their contractor making the OS, independent of the other issues with the SoC manufacturer. Let's hope they (and we) will have more luck with the Pro1X ... 

    • Like 4
  2. 2 hours ago, VaZso said:

    I think at the beginning, they wanted to do it differently but a lot of things have happened.

    I do not know from personal experience, but people close to the Lineage porting effort have hinted F(x)tec at least suspected they would not be able keep an official Android OS afloat -- long before the 835 thing happened. Seems like keeping a certified Android OS up-to-date is not so cheap after all, let alone porting newer Android major releases to the device ... 

  3. I cannot really comment on the state of the stock Android OS as I have been on Lineage since day one. However, especially those who jumped-off stock only recently seem to not look back at all. Considering how unhappy you seem to be with your stock Android 9, I'd suggest you just give Lineage (or some derivative) a chance.

    I think it is by now clear that F(x)tec more or less intended the Pro1 to be used with alternative ROMs. Yes, I fully agree that they should have either stated this more clearly from the beginning, or properly supported the original OS their phone was delivered with. But I think that ship has sailed.

    The good news is that your Pro1 is probably quite easy to sell even at full purchasing price, if its hardware is in decent condition ... 😉 

  4. 18 hours ago, Hook said:

    Wait. What? We have to convince our spouse??

    I know you are joking, but I meant that quite seriously.

    My wife brings home half of the family income, but, for some reason, I thought I need a phone that is 10x more expensive than hers (while having worse audio quality 😉 ). Of course I explained to her why I wanted that Pro1 so badly before throwing all that money at a company that, even then, I was not sure would be able to deliver at all. If you manage your entire household from a common financial pool, it is imho a question of mutual respect to discuss major expenses prior to engagement -- especially if they are about what most people will see as a luxury item ... 

    Back on topic: I think F(x)tec have shown that, with the Pro1, they can fulfil the demand of a certain niche marked. However, we have also seen that, already now, they are plagued by problems typical for a small-volume manufacturer: uncertain supply chains, lacking quality assurance, need to source second-choice hardware (uncalibrated screens).

    If, by trying to include too many fancy new ideas (adaptive keyboards), F(x)tec push the price of the individual device further up, their already niche marked will shrink, which will further aggravate their problems. So I think this is really not the way to go.

    Rather, they should build on what they have achieved, and incrementally improve the (after all) successful concept of a smartphone the Pro1 is. That's what the big players, mostly, do too.  

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

    [...] and should be solved also on Pro1 [...]

    You are right, but let's not further misuse this thread for discussing known issues of the original Pro1 (again).

    Lineage may be able to fix a few more things on the Pro1, but I think we have to accept the fact that, from F(x)tec's perspective, that one is done. Any software issues related to the binary blobs will not be fixed. Imho, we will be lucky to even get spare parts for components unique to the Pro1.

    Let's see how the Pro1-X comes out and how long F(x)tec plan to keep it available for purchase. If it improves on some of the issues already in the first production batch, and if they are willing to keep fixing remaining bugs in later batches, the Pro1-X may end up having a quite long product life before a Pro2 becomes necessary.

    • Like 2
  6. I very much enjoy the discussions here, and hope that also F(x)tec uses them for inspiration on future projects.

    But considering the features of a hypothetical Pro2, I think we should also be realistic: The Pro1/Pro1-X are very expensive phones even without including exotic technologies like e-ink-keyboards. I think 1000 €/$ are a magical landmark, where even enthusiastic keyboard-phone lovers will have a hard time convincing their spouses that they really need that device.  

    A Pro2 should probably focus on getting an up-to-date flagship SoC and improve on the known shortcomings of its predecessor(s). For the Pro1 those are (imho and in order of decreasing severity): main camera quality, keyboard quirks, telephony audio quality, and wifi signal strength. Possibly, the Pro1-X will improve significantly on some of these points, so that it should serve as the new benchmark for an all-out re-implementation of the concept.

    • Like 3
  7. Some time ago, I recommended Devuan as my GNU/Linux distribution of choice for installation in a chroot of LineageOS.

    Today, I wanted to upgrade my xrdp-pulseaudio modules (providing seamless sound forwarding to Android when using my X11 desktop) and found out that installing them on Devuan is not possible in a straightforward way using the tools provided on neutrinolabs' GitHub repo.

    The reason is that the drivers need to be compiled against the pulseaudio sources matching the version of each respective distribution. On Devuan, the command:

    # sudo apt build-dep pulseaudio

    fails, probably because of some unresolvable (and likely unnecessary) dependencies on systemd.

    So how to proceed? Disregarding the (non-)dependence of some packages on systemd, Devuan 3 (which I use) is binary-compatible with upstream Debian 10. So, if I had an ARM64 version of the latter, I could build the drivers and just copy them over to my Devuan 3 system.

    Luckily, there is schroot. It allows to seamlessly install and use a a foreign Linux distribution within one’s main OS. We install a minimal Debian 10 ('buster') system in an directory /var/chroot/buster. Note that all this will (temporarily) require at least ~1 GB of SD card space, make sure you have enough.

    # sudo apt install debootstrap schroot
    # sudo mkdir /var/chroot/buster
    # sudo debootstrap buster /var/chroot/buster http://deb.debian.org/debian

    After that, create the config file for the new distribution in /etc/schroot/chroot.d/buster.conf:

    description=Vanilla Debian 10 'buster' for package compilation

    Enter your new Debian 10 system as root:

    # schroot -c buster -u root

    install sudo in Debian 10:

    > apt install sudo 

    Then, edit the the sudoers file in the chroot

    > visudo

    adding a line like


    Save the sudoers file, exit the schroot and re-enter as regular user

    > exit
    # schroot -c buster

    For clarity, we use "#" to symbolize the Devuan 3 CLI prompt, and ">" for that of the Debian 10 'guest OS'.

    And, yes, we are in fact running a Debian 10 inside a chroot of a Devuan 3 which is, itself, running in a chroot of LineageOS. If you are not confused at this point, consider yourself hardcore. If you are, do not worry, we hold you. Either way, take a minute to meditate on the fact that the concepts taking us this far in 2022 were developed ~42 years ago in UNIX v7.

    Install the minimally necessary dev tools in the schroot:

    > sudo apt install build-essential dpkg-dev libpulse-dev git autoconf libtool

    Get the pulseaudio sources for Debian 10:

    > sudo echo "deb-src http://deb.debian.org/debian buster main" >> /etc/apt/sources.list
    > sudo apt update
    > cd ~
    > apt source pulseaudio

    Get the build dependencies for pulseaudio (as we are in vanilla Debian 10, this should work now):

    > sudo apt build-dep pulseaudio

    Configure the pulseaudio sources:

    > cd pulseaudio-XX.Y 
    > ./configure

    Clone the GIT repo with the xrdp driver sources:

    > cd ~
    > git clone https://github.com/neutrinolabs/pulseaudio-module-xrdp.git

    Compile the driver modules:

    > cd pulseaudio-module-xrdp
    > ./bootstrap && ./configure PULSE_DIR=~/pulseaudio-XX.Y
    > make

    Of course, running the provided “make install”-script from within the Debian 10 chroot does not make sense, as that would install the drivers only in the Debian 10 'guest', but not in the Devuan 3 'host', which is what we want. Either leave the schroot and run the installer script in Devuan 3, or just copy the drivers to /usr/lib/pulse-XX.Y/modules/ and configure pulseaudio manually, which is what I do. The compiled .so’s are in ~/pulseaudio-modules-xrdp/src/.libs/ .

    After successful compilation and driver installation, you may delete the Debian 10 schroot in /var/chroot/buster to free up some SD card space. You might also choose to keep it around as a dedicated building environment, allowing you to (re-)compile more stuff without polluting your 'main' distribution with hundreds of dev packages.

    Have fun!

    • Like 2
    • Thanks 2
  8. 7 minutes ago, VaZso said:

    I think if you may connect a wired mouse to the phone using an OTG conversion then you can give input pattern using a mouse pointer.

    Yes, just tested that: USB mouse works for pattern-based unlocking, even if one connects the mouse only while the phone is already locked.

    Bluetooth mouse could work, if it is already paired with the device and BT is switched on. Otherwise probably not ...

    • Like 1
    • Thanks 1
  9. 1 hour ago, toast said:

    Seems like (not very surprising) /e/OS came out on top, followed by LineageOS

    Thanks for sharing this article.

    Note that the comparison is quite unfair with respect to LineageOS in that, in this study, the LOS device had GApps installed, which then -- unsurprisingly -- phone home to Google in the same way they do when installed on a commercial AndroidOS. The Lineage Project does not ship GApps in their ROMs -- users have to install them separately (and willingly) from a 3rd-party source after flashing the OS.

    I think it is safe to assume that a LineageOS with MicroG (as also used by /e/) or a vanilla LineageOS (with neither GApps nor MicroG installed) would come out essentially on par with /e/ in this study.

    • Like 5
  10. 14 hours ago, manjaro said:

    I did not want to totally dismiss what has been done with Ubuntu Touch. I can see that a lot of work has been put into it. I just think, and this has happened to me in my career, the target and goal were off the mark. They are trying to meet Apple in terms of GUI standards, it appears. There is no way that will come to pass. Apple is vertically integrated whereas Ubuntu Touch would need to adapt to whatever hardware it gets installed onto.

    That could not be more true.

    Canonical (at the time they still backed the project) would have liked us to think about Ubuntu Touch and the Ubuntu distribution for PCs as two flavours of the same OS -- as in iOS vs. MacOS. Many users unaware of technical details may believe that to this date.

    The truth is, for all but a few exotic devices (like the PinePhone), Ubuntu Touch does not even use an Ubuntu Linux kernel! It bundles a minimal version of the device-vendor supplied Android system, including its kernel and driver blobs. It then uses compatibility layers (libhybris) to interface the AndroidOS (bionic) from the Ubuntu userspace (GNU). As a consequence, only apps specifically developed against libhybris can take advantage of all Android APIs, while standard programs developed for the desktop arm64 Ubuntu distribution are limited in their system calls to what the vendor kernel allows directly. That's the reason why, e.g., X11 programs running in Libertine containers cannot have hardware accelerated graphics.

    To my knowledge, the limitations one encounters when running standard Unix software on Ubuntu Touch are identical when compared to running the same software in a chroot of Android. I hence gave up on waiting for Ubuntu Touch to mature and settled for a chroot-on-Lineage solution with my Pro1. That way, I have the best (or close to) of both worlds: a fully-functional Android smartphone environment plus a Debian desktop distribution for doing serious work.

    I agree that having a native GNU/Linux system would be preferable, but the Pro1 is not that kind of device. Neither will be the Pro1X.   

    • Like 1
    • Thanks 1
  11. After reading a little, I am under the impression that /e/ is indeed more about the default software distribution than about the underlying OS. Not to turn down that effort -- sane defaults that just work out of the box are certainly a good thing.

    I'll keep using vanilla Lineage (without Gapps or MicroG) for now. The Aurora store also displays tracker information from Exodus btw. But most of my apps are from F-Droid anyway...

    Thanks for sharing.

    • Like 2
  12. 13 hours ago, manjaro said:

    No way to install common unix software like curl. W - T - F

    I believe you have fundamentally wrong expectations regarding Ubuntu Touch. It is not designed as a traditional Unix, but as a smartphone OS, sharing quite a few concepts with Android. This includes app confinement (sandboxing), which actively breaks core Unix philosophy, as data "belonging" to one program purposedly cannot be easily picked up by another.

    Installing a true Unix environment on UbuntuTouch is possible, but involves quite similar techniques than doing the same on Android, the difference being that with UbuntuTouch you use an LXC container while on Android we rely on traditional chroot'ing. 

    If you seek a "standard" GNU/Linux OS for phones, your Manjaro on PinePhone was actually a much better bet. Sailfish may be the closest you can get with standard Android-devices (like the Pro1).

    I agree with @EskeRahn that this discussion has little to do with the Pro1(X).

    • Like 1
  13. 54 minutes ago, daniel.schaaaf said:

    In case you have root, you can take a look at /sys/class/power_supply/...

    For those with GNU/Linux-chroots: UPower provides a friendly interface to display the information from that sysfs tree. E.g.

    rostkatze:~ # upower -e
    rostkatze:~ # upower -i /org/freedesktop/UPower/devices/battery_bms
      native-path:          bms
      power supply:         yes
      updated:              Mon 03 Jan 2022 11:14:56 CET (72 seconds ago)
      has history:          yes
      has statistics:       yes
        present:             yes
        rechargeable:        yes
        state:               discharging
        warning-level:       none
        energy:              9.7981 Wh
        energy-empty:        0 Wh
        energy-full:         12.7248 Wh
        energy-full-design:  12.6632 Wh
        energy-rate:         0.146093 W
        voltage:             4.07616 V
        time to empty:       2.8 days
        percentage:          77%
        temperature:         21 degrees C
        capacity:            100%
        icon-name:          'battery-full-symbolic'
      History (rate):
        1641204896  0.146   discharging

    Root is still needed of course.

    • Like 2
  14. 8 hours ago, Slion said:

    There are some BLOBs for proprietary device drivers which are closed source but others such as the keyboard driver have actually been opened source.

    The point is that the major components that make the SoC useful as a phone are closed-source, like on any typical Android device using similar SoCs.

    As a consequence, all projects of using a fully open-source Linux OS on the Pro1 are just proofs-of-principle that, while academically interesting, are so far from prime-time that the last Pro1 will likely have gone the way of all silicon before they mature to the point of becoming practically useful. Do not get me wrong: this is not an unusual situation. Practically all Android devices depend on these proprietary blobs, as we both know. As of today, a manufacturer has to go through significant lengths to make a truly open-source phone. FxTec chose not to do that, and I do not blame them for it. All I say is they could have stated this more clearly when that whole "Linux-enabled-keyboard-phone" thing took off.

    I agree that open-sourcing the driver for the Pro1's keyboard was certainly a good thing.

    • Like 1
  15. 3 hours ago, lawliett said:

    I feel the Pro1 is better because it tries to do one thing well (thumb typing) rather than trying to do two things sub-optimally (touch typing and thumb typing).

    Actually, I find the Pro1 is too large for comfortable thumb-typing. Travel of the thumbs is too long for some keys when holding the phone by the keyboard. From other discussions here, I know that I am not alone with this opinion. I certainly could thumb-type much faster on my good old N900 -- though I must admit that I neither miss the small screen size of the latter, nor the absence of many special keys the Pro1 has ... 

    I can well imagine that the PlanetComputers keyboard is even much less comfortable to thumb-type on, but -- in all fairness -- I do not think that was the design goal of that device.

    • Like 1
  16. On 6/22/2021 at 8:15 PM, claude0001 said:

    For the case anyone else still has interest in LineageOS 16.0, I've made them available here:


    Build 20211219, with the December AOSP security fixes, is available at the above link.

    Full list of local mods with respect to upstream Lineage-16.0 tree:

    Have fun.

    • Like 5
  17. 13 hours ago, eldarion said:

    I'm an evil-mode user actually. The problem with thumb typing is some key combinations require a lot of travel and leaving the home row. On a planet keyboard you can easily do C-x one handed but with the pro1 keyboard it's not really possible.

    Tbh, I never did things like C-x C-s single-handed, even with a full-size PC keyboard: I hit one of the Ctrl keys with one hand, and the letter key with the other.

    Anyway, after years of using it intensely, I have almost stopped using emacs for various reasons. Also vi, I use only for minor editing of shell scripts or config files. For any serious amount of coding, it has been Kate for a while now. Mainly old age I guess 🙂. But its Windows-style shortcuts do work quite well on the Pro1, too. (And, of course, it's got a vim input mode, just for you 😉 ).

    Back on topic: Of course, the Pro1 keyboard is not perfect, and cannot compete with that of Planet Computers.

    However, I like the basic idea of the Pro1: A no-compromise standard Android phone that can "just run" all those everyday apps made for touch-only operation (let's face it),  with the added option to flip-out the built-in keyboard, when needed.

    To be perfectly honest, I hardly use the keyboard for operating Android apps. Most are optimised for portrait and just inconvenient to use in landscape orientation anyway. But when using my GNU/Linux chroot, the keyboard shines! It allows me to transform my phone into a full-featured (albeit small) Unix workstation, with a hw keyboard that has all the important keys for coding and does not require an (additional) software keypad covering large parts of the X11 or terminal screen. Sure, given the small size, I would not want to work like that for hours. But, somehow, it feels good to know my phone can do (almost) anything my Linux PC can, if I happen to be far from the latter ... 😎  

    • Like 2
  18. 3 hours ago, eldarion said:

    I had a pro1 I gave away and emacs was unusable there too. Even something as simple as C-x C-c is difficult for me.

    While I do not use emacs much anymore, I do not perceive C-x C-c as a problem on the Pro1. Emacs is certainly much more useful on the Pro1 than it used to be on the N900, which had its single Ctrl key awkwardly placed in the top left corner and no hardware Esc key at all ...

    But we can agree to disagree: Vim is much better at thumb-typing anyway -- both on the N900 and the Pro1. *duck* 😉

    • Haha 2
  19. 18 hours ago, mv said:

    as I will wait for 4G to be developed first since my carrier is restricting more and more

    I was not aware 4G was not working in SFOS anymore. It is said to have worked even on the very earliest releases (end 2019 - mid 2020) according to this post [maemo.org]. What happened? With 3G getting shut down everywhere, this indeed disqualifies SFOS as a daily driver for a lot of people.

    With news like this, and the development of UBTouch also stalling, it seems like Lineage/AOSP-ROMs are indeed all we are left with for the original Pro1. 😞

  20. 4 hours ago, Rob. S. said:

    Personally, I'm mostly ok now after setting it to 32.

    Yes, that LOS option is a blessing. I also ended up with a value of 32.

    I found the "pointer location" debugging function (settings > system > developer options > pointer location) useful for optimising the width of the unsensitive edge.

    • Like 1
  21. Calm down people. It's a minuscule company, making infinitesimal numbers of phones. You must be quite new around here for assuming they will be on time. They have never been. 🙂

    Still, they have shown that they love their project and do everything in their power to deliver to their customers.

    The original Pro1 was delayed by months. But many (probably most?) eventually got their phones, including myself. Please just try to chill.

    • Like 2
    • Thanks 3
  22. On 11/17/2021 at 9:26 AM, VaZso said:

    Anyway, does its RJ45 work under Android?

    In case that function is really important to you, I have got this one:

    UGREEN USB C Hub Ethernet with 4K 60Hz HDMI USB C Adapter LAN with HDMI, RJ45, 100W PD, SD/microSD, 2 USB 3.0

    (though I remember buying it at lower price than 50 €). All features of that hub work in LineageOS 16.0 and I thus would expect them to work in 18.1, too.

    That said, performance-wise, the Ethernet adapter does not even remotely reach the advertised 1 Gbit/s: using iperf3 I measure ~150 Mbit/s up and ~230 MBit/s down. On the same network, with the same peer, I easily get 300-400 MBit/s via the Pro1's WiFi ... 🤨

    I do not care about that function much. I got the device for the SD-card reader (backups, backups, backups!), which works well, even with two cards inserted simultaneously.

    The HDMI-Out (including sound) actually also worked in LOS 16.0 as long as I remember. Must have been some regression, if that wasn't the case for 18.1 shortly ago.

    • Thanks 2
  • Create New...

Important Information