Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


Posts posted by claude0001

  1. 21 minutes ago, marmistrz said:

    I'll check if it helps, thanks! Is there any reason why some of these changes are not in the official LineageOS? The relevant file is https://github.com/LineageOS/android_device_fxtec_pro1/blob/lineage-18.1/configs/gps/gps.conf

    I think some things regarding AGPS are left blank on purpose in LineageOS, as using such services potentially reveals your location to the server operators, which may be seen as a privacy issue.

    Even disregarding this, from what I read on the internet, the optimum settings depend on what region of the world you are in. So maybe there is no one-size-fits-all config anyway.

    I found this config on some German Android user-forum and did not really check if it is truly optimal. The new settings certainly helped (a lot) in my case, but you may find even better ones for Poland by experimenting a little ...

    Hope it will help.

    • Like 1
  2. In LineageOS 16 I could vastly improve the locking speed by the following edits in /system/vendor/etc/gps.conf:


    I am also in Europe (Germany) and at times could not get a fix at all (even after waiting for hours) with the default settings of LineageOS 16. Since I made that edit, GPS fixes are very fast.

    Note that the "INTERMEDIATE_POS" bit is optional: It causes the location service to report even very early position estimates based on mobile network towers only. That estimate can however be wrong by many kilometers, so not all people like it. I find the option helpful if you travel a lot and often switch on the GPS very far from the last fix.

    As you may have guessed, you need root access for this hack. Also, remember that you need to remount / read-writable temporarily. The config will probably not survive OTA updates, so better make a backup once you have found a setting that works for you. 

    • Like 3
  3. 3 minutes ago, VaZso said:

    I am satisfied with its camera but only with a GCam port...

    Yes, I believe you. Let's not go over this again. 🙂

    GCam is not compatible with a Google-free LineageOS, and certainly even less with SailfishOS and UbuntuTouch. It is simply not an option for many people, plus, it does not support the shutter button which was supposed to be one of the outstanding features of the Pro1.

    The camera should make good pictures reliably, irrespective of the backend software used. But, sadly, it doesn't.

    • Like 1
  4. 6 hours ago, EskeRahn said:

    Being a bit evil, following the link the second image seems to tell us that we would better ALSO have a real camera...  👼😈

    Well, honestly, the crappiness ... ahem ... loveable peculiarities of the Pro1's camera got me back to carrying my DSLR along more often, too ... 🤔

    • Haha 3
  5. 2 hours ago, npatel1050 said:

    As it sits right now, the pro1 is one of the thickest, heaviest, and bulkiest phones on the market. Using a 6 inch screen doesn't help that agenda

    I agree that the Pro1 is bulky compared to other modern phones.

    But to be fair one must also say that the big size helps in all kinds of business use-cases (which are a main selling point of the phone): When coding, emailing or word processing, the huge screen allows to display a lot of content at acceptable font sizes, which certainly increases productivity. Also, as @lawliett already mentioned, running desktop Linux apps in a chroot is much more pleasant with a big display.

    As much as I loved my N900, I certainly do not miss its tiny screen. 🙂

    • Like 2
  6. 1 hour ago, Hook said:

    But this, in my experience, is how most ROM developers work.  Once they move on to the next version, they drop all support for the previous versions.

    I did not think that was the problem here.

    If LineageOS 16 and 17.1 still had the Pro1 as build target in their config, the build system would continue to spit out new builds every week. In that process, upstream patches like AOSP security fixes (which are not device-specific) would be included automatically and not require any manual intervention by a device maintainer.

    At least this is how I understood things work. Someone with more knowledge about the LineageOS build process may correct me.

    I thought the problem here was simply to save resources on the build farm by allowing only one official LOS version per device.

    • Like 1
  7. 3 hours ago, Slion said:

    It looks like the LOS team is just pumping out builds with no dev actually caring and using them.

    Let me try to rephrase that in a more optimistic way: They are very enthusiastic about porting the latest-and-greatest release to the Pro1. 🙂

    The real problem is that, as soon as a new release (here 18.1) is declared "official", the previous one (17.1) stops receiving upstream patches. De-facto, releases are dropped from support at the very moment they have matured ...

    Effectively, users have only this choice: 

    1.  Either stay on an older, stable, and nicely de-bugged LOS port that does however no longer receive upstream AOSP fixes.    
    2.  Or change horses every few months by dirty-flashing to the next major release. This way one has the latest Android security patches at the cost of running an OS that is never feature-stable, plus the hazards related to dirty flashing ...

    Yes, this is insane. But seemingly it is LineageOS policy that each device is allowed only one "active" LOS version.

    For sure, I am happy to have a local copy of the last build of @tdm's LineageOS 16 ...

    • Like 4
  8. 3 hours ago, raymo said:

    This is the problem : I can't ask you for a noob tutorial, I guess your time is precious.
    But I don't know how attacking the problem yet...Any advice will be much appreciate in order to get on the way. Whatever thank you so much for the share !

    If you just want to run a few Linux programs, something like Termux and AnLinux is definitely the easiest way to start. I have never used those Apps, though, so I cannot help with specific questions about them.

    For advanced stuff, like the above, a "hand-made" chroot (with root access to Android/Lineage) will probably always be superior to (non-root) in-App solutions.

    Setting up your own Linux chroot on Android is actually not that hard provided you have some experience with Linux. The real problem is that the required information is scattered all over the internet. Also, some things change with every Android/Lineage release, so How-To's from a few years ago may no longer be fully applicable today. I included a few useful links as well as my chroot autostart script in a previous post about my set-up. However, much information about fine-tuning I did is not in there, either.

    For these reasons, I actually did plan to make a tutorial at some point -- also as a guide to myself should I ever need to reinstall. Once I have written things up, I will post a link here.

    • Like 2
    • Thanks 2
  9. 13 hours ago, EskeRahn said:

    (note there is a new  0405 18.1 build already)

    As I wrote above, 17.1 no longer has the Pro1 as build target, so there will be no more (official) updates for it. See https://www.lineageoslog.com/17.1/pro1

    12 hours ago, Rob. S. said:

    That would explain @ivoanjo's experience with 18.1. I'll be staying on 17.1 for a bit longer, then, I suppose. 

    ... and that is exactly why the older, stable versions should keep building, at least on monthly basis so they keep receiving the upstream security fixes in AOSP.

    Every upgrade that changes APIs or other major parts of an OS is potentially disruptive for the already-installed base. That is why professional distributions keep their "stable" branches alive as long as upstream fixes can be picked-up with reasonable effort.  

    • Like 3
    • Thanks 1
    • Sad 1
  10. 21 hours ago, __fastcall said:

    Attached a photo, this is basically the best I could get out of the phone today..

    Looking at your picture, I notice that the lower right corner is actually sharp: that wall socket seems to be quite nicely in focus. The rest of the picture obviously isn't -- even though there are many objects at roughly the same distance from the lens than the wall socket.

    Also the upper half of the shelf exhibits some very strange ("wavy") perspective distortion.

    This looks like an optical problem. Like a misalignment between lens and sensor or so. Sadly, I do not think this can be corrected for in software. @Jacob_S posted similarly distorted pictures earlier in this thread. Maybe they have found out more about the problem by now ...

    Edit: Just realised @Rob. S. have come to the same conclusion about your picture. I can only agree with them.

    • Like 2
  11. As much as I enjoy the fact that LineageOS on the Pro1 seems to be alive and well, I am puzzled by the practice of removing previous major releases from the build systems as soon as a new version is made.

    In November, LOS 16 stopped receiving upstream updates (in favour of 17.1) just a few months after I had installed and -- quite heavily -- configured it.

    Now, 5 months (!) later, 17.1 disappeared from the build targets for the Pro1 at the very moment 18.1 came around the corner.

    I understand that a community project may need to save computing ressources on the build farms. Still, people accustomed to "serious" operating systems can only be irritated by this ridiculously short obsolescence half-live.

    Maybe I am just old. On (all of) my PCs, I professionally use Debian 8 ('jessie') almost 6 years after its release in 2015: It is still receiving security updates (and will continue to do so until mid-2022) although two major Debian releases have superseded it since ... As I consider my Pro1 a 'real' computer, designed for business tasks, I tend to compare it to such systems.

    Of course, a lively community -- keen on bringing in the latest and greatest upstream features -- is nice, as it makes the OS attractive for switchers or those who enjoy living on the bleeding edge. But maybe there are more than just a few people (like myself) who would like to set-up their (Lineage) phones once-and-for-all and then just use (!) them for some time without needing to go through any major (and potentially disruptive) upgrades? Those would certainly profit if old versions were kept building (automatically) for some time. Doesn't need to be 7 years like for Debian, but maybe more than 5 months would be possible? 

    Edit: Sorry for the rant. I very much like my LineageOS (16, still), please no one get me wrong.

    • Like 4
    • Thanks 2
  12. 11 hours ago, SteffenWi said:

    Oh and I can't set up a SSH server in Ubuntu Touch because I would have to copy my public key over aaand as I said I can't copy any files.

    Setting up the ssh server seems a bit tricky in UBports indeed. The official docs -- which your certainly know already -- list several ways of transferring the key.

    I am no UbuntuTouch user, but basically, one encounters the same problems when setting up the SSH server in LineageOS. There, the easiest way (for me) was to grab the required public keys from the PC to the phone using Lineage's built-in SSH client (as opposed to pushing the files to the phone, which requires a working SSH server in the first place). Not sure if Ubuntu includes an SSH client out-of-the box, but if not, I would assume that should be easy to fix.

    Don't give up on SSH! Once you get it running, it will be nothing short of a swiss army knife when it comes to accessing your phone's shell or filesystems (and more!) from outside. I actually have two SSH servers running simultaneously on my Pro1: One from my Debian chroot (used for everyday work on the phone), and the native SSH server of LineageOS for accessing its Android root shell. 

    • Like 1
  13. Update: I can now run the X.org X11 server inside my Devuan chroot. Yes, the real thing, not TigerVNC or TightVNC.

    The nice thing with X.org is that I can use it with xorgxrdp in the chroot and connect to my Linux distro via a much better-performing (native) RDP connection as compared to using VNC as backend for XRDP. I still use the Microsoft Remote Desktop 8 App combined with the default xrdp-0.9.9 shipping with Devuan 3/Debian 10.

    As far as I can see, one can find no information on how to do this on the internet. Either it is really tricky and I am a genius, or no one cares about it ... difficult to say. 🙂

    So, how to do it? The critical point with the xorgxrdp module for X.org is that it absolutely requires System-V-style shared-memory access. The Android Linux kernel does not provide that, as Google invented their own implentation of shared memory (/dev/ashmem) long ago.

    So, the first step is to bind-mount /dev/ashmem to your Linux chroot, by having something like this in your chroot setup script (of course this requires root-access to your phone):

    # Script to set up the Debian/Devuan chroot environment on boot of LineageOS
    export ROOT=/data/DEBIAN
    mount -o bind /dev/ashmem $ROOT/dev/ashmem

    Having /dev/ashmem available to your Linux distribution is not enough, though, as GNU/Linux shared-memory calls are not compatible with that interface out-of-the-box. Luckily, some awesome people have made android-shmem, a library translating Sys-V-shared-memory-calls to Android-shared-memory-calls. You need to compile that library inside your chroot and then preload it previously to running any program depending on Sys-V-style shared memory, as explained on the GitHub page.

    For xorgxrdp to work, one needs two things:

    XRDP needs to be started with android-shmem preloaded. In Devuan 3, I do this by having the following edit in "/etc/rc5.d/S12xrdp":

    # enable Sys-V shared memory access on Android kernel
    export LD_PRELOAD="/usr/local/bin/libandroid-shmem-aarch64.so" 

    X.org must be started via a wrapper script, also preloading the android-shmem library:

    # Wrapper script for Xorg when called from XRDP.
    # Makes sure the 'android-shmem' library is preloaded before execution so that
    # SYS-V-style shared memory calls will work on Android kernel. 
    origparams="[email protected]"
    exec env LD_PRELOAD="/usr/local/bin/libandroid-shmem-aarch64.so" /usr/lib/xorg/Xorg $origparams

    On Debian/Devuan, most likely, you will want to configure /etc/xrdp/sesman.ini to lauch that wrapper script instead of X.org directly.

    Attachment: MS Remote Desktop showing an xorgxrdp session on my Pro1 with a youtube browser window (with audio streaming via XRDP) and a simultaneous glxgears benchmark.  




    • Like 2
    • Thanks 7
  14. 6 hours ago, benoitjeffrey said:

    I shattered a screen with a closed flip case, it won't protect the left side of the phone at all.

    Personally I really enjoy the 3d printed case from @LIMA but I'm looking closely for the one from @ubuntuscofieldand @belletrist

    Those 3d printed case can protect the phone way better than a flip case

    Of course, an unlucky hit can get through the unprotected side of a flap case. My main point is that the case (any case for what matters) reduces the chance the Pro1 will slip out of your hand in the first place. As a bonus, a flap case also removes the need for a screen protector sticker.

    As much as I enjoy enthusiast projects, the 3D-printed cases I have seen so far (from pictures only, of course) look a bit awkward. They are certainly perfectly functional, but aesthetically not very appealing (to me at least).

    No hard feelings, but for now I will stick with my flap case ...

    • Like 3
  15. 53 minutes ago, EskeRahn said:

    The most protective -yet still usable- solution is a screen protector and a flip case.


    I do not have a screen protector, but I decided for a flip case on day one. The Pro1's surface finish is nice but it enables the phone to slip out of your hand far too easily ...  

    • Like 1
    • Thanks 1
  16. 3 minutes ago, Rob. S. said:

    A black spot of 3mm diameter, after dropping the phone, hitting a wooden floor hard with the display facing downwards. Doesn't make the phone unusable, but at some point I'll want to replace the screen. Already bought two, one for spares...

    Ouch. I feel your pain.

    Maybe I should invest in a spare too as long as they are easily available. Is the Elephone U spare part on AliExpress the known-good screen for the Pro1?

  17. 2 hours ago, Rob. S. said:

    I'm about to replace my screen as well and I have asked for the APK, too.

    I remember you got your device only a month ago or so. What's wrong with your screen? Just asking ...

    About that APK for installing the required firmware: Is it (legally?) impossible to put that up somewhere for public download? It will certainly be of interest to many sooner or later. People replacing their screens will typically want to avoid reflashing their phones to stock and back just to get the replacement screen working.

    • Like 2
  18. 10 hours ago, EskeRahn said:

    (on the VoLTE availability confusion see this thread)

    Wow, what a mess, indeed.

    From the other thread, I get that those who do not see the "Enhanced 4G LTE Mode" switch have VoLTE disabled anyway (because their OS, or their carrier, or both do not support it). So, according to @Rob. S.'s hypothesis, they should not encounter the loudness bug in the first place. However, @pistikem seems to have the bug despite not having VoLTE. Are we on the wrong track after all?

  19. 3 hours ago, pistikem said:

    i don't seem to have this feature : "4G calling"  (HD voice aka wideband audio)

    In my LineageOS 16 it is called "Enhanced 4G LTE Mode" and is only visible in the "Advanced" settings under "Mobile Network".

    I do not think it is specific to LineageOS. As far as I know, the option used to be called "VoLTE" or "HD voice" in previous Android versions. But seemingly the switch controls more than just Voice-over-LTE nowadays: If I switch it off, also "Carrier video calls" get disabled. Potentially, you might loose other useful things like conference calls -- not sure about that, though (and too lazy to test). VoLTE is also said to use less power compared to 2G/3G calling, so if you do a lot of voice calls you may see decreased battery life.

    I'll leave it on for now, as I did not suffer from the loudness problem yet ...

  20. 15 hours ago, Rud said:

    Since the early 2000's I always wanted phones to move towards a min laptop ...

    Well, me too, and that is exactly how I use my Pro1. Not with Ubuntu, though.

    My point is that, for a phone to work as a miniature "laptop", all the functionality must be there in principle without carrying external devices along. For that is what a laptop is: a standalone all-in-one machine that has all required peripherals built-in. That you can extend functionality by plugging even more stuff into the device is a bonus, not a requirement.

    This does however not seem to be what the OP have in mind: they seem to refer to the so-called "convergence" mode of operation, where the phone is an ordinary phone (with ordinary phone apps) when held in hand, and transforms into a desktop (not laptop!) PC only when connected to a USB dock with mouse, keyboard and screen.

    Yes, that may seems like a cool feature at first. But I still cannot see many practical applications for it. If I simply want/need to carry my own small "docking" Linux PC along, but do not require it to work stand-alone when on-the-go, this can be accomplished in a (much) cheaper, easier, and arguably better way using a Raspberry Pi: Thanks to hardware support -- which Ubuntu's Libertine (like all chroot/container solutions on Android kernels) does not have -- a recent Raspberry is in fact more performant at running desktop Linux apps than a Pro1. Sad but unfortunately true 🙂

    • Like 1
  21. Am I the only one who came here directly from an N900?

    I learned about the Pro1 on the maemo.org forum, where it was discussed as the spiritual successor of the N900 (and N950 for those who were lucky enough to have one of those).

    I (like others) used the N900 well beyond its time, as it was the only true Unix(-like) phone for years. I invested quite some time into setting up my Pro1 in a way that it can compete with the N900 in terms of usefulness as a Unix workstation. And while I have come quite far in that project, it is clear that I still do not have control of the system on a level similar to the N900 ... Maybe I should have gone for SailfishOS instead of a Lineage/Linux-Chroot setup after all ...

    • Like 1
  22. I must say that I really do not understand your question.

    The whole point of a laptop is that it does not rely on an external display, mouse and keyboard.

    I believe the whole convergence thing in phones is much overrated. In my world, whenever I am close to a monitor, mouse, and keyboard, a PC is most likely attached to those anyway. There is simply no need to bring my own (less powerful) computer to them to be productive.

    IMHO, a portable computing device makes sense only if it is self-sufficient: It's task is to allow you to be productive precisely in the case you are far from any supporting infrastructure. E.g., my Pro1 allows me to do my computing tasks when I am in the middle of nowhere, using its built-in screen and keyboard. When I am at home or at work, it obviously cannot compete with the full-size workstations I have available there ...

    • Thanks 1
  23. 23 hours ago, _DW_ said:

    Mine fast charges from my USB-C port on my laptop (Same port used to dock laptop and charge @ 230w) wonder my your think pad doesn't?

    I's an X250. It has traditional USB-3.0 ports, not USB-C, both on the laptop as well as on the dock. That's probably why it (luckily 🙂) does not fast charge.


    • Like 1
  24. 4 hours ago, SteffenWi said:

    Also this guy says that the port was done by FxTec, not by the Ubuntu Touch community

    To be honest, it never became clear to me what development model they had in mind for the Pro1 -- for any OS, actually. That comment is from February, so it likely already refers to the Pro1-X project anyway (which initially was compatible to the Pro1).

    Sadly, among the three "big" community OS's for the Pro1, Ubuntu seems to have fallen behind by quite some amount over the course of last year. According to the experience reported by @Raksura in this thread, it was still very far from a "daily-driver" level of usability in December. One has to compare that with the progress made by LineageOS (fully production-grade) and Sailfish (at least perfectly useable, with some quite cool features) in that same year.

    In developing Ubuntu further, F(x)tec will obviously need to focus on the (new) Pro1-X now, as Ubuntu (with desktop-mode) seems to have been a killer feature for many backers. And once Pro1-X's start to hit the market in significant numbers, also community support will likely shift to the newer device, which has many advantages from a developer point of view (long remaining EOL, newer Linux Kernel, in the long term: larger installed base ...).

    So, I fear that, if Ubuntu for the original Pro1 does not learn to fly in 2021, it probably never will ... 😞 

  • Create New...

Important Information