Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


Everything posted by claude0001

  1. I guess you are in the US. US carriers seem to be problematic in general as they do not "know" the Pro1. Similar problems might arise with the Pro1X. I cannot help personally, but there is another thread dedicated to US network acceptance.
  2. The PinePhone is much better suited for running upstream Linux and GNU/Linux distributions targeting phones. As such, it is a very interesting project. I was close to ordering it several times, and do not know how long I will still be able to resist ... 🙂 However, its specs are quite low compared to the Pro1 or Pro1X. When it comes to CPU, RAM, or display resolution, the PinePhone's usefulness as a "laptop replacement" may thus be limited, despite its more GNU/Linux-friendly architecture.
  3. I had seen that video before and agree that it is impressive. The ability to use XWayland on Sailfish makes it definitely more responsive than my XRDP-based solution on LineageOS, where the remote desktop connection does add some graphics overhead. HDMI-out works on Android (9), but only mirrors the phone screen, so it does not really give you that "convergence" feeling. I can achieve the latter by using a remote (e.g. Windows-) PC to log into my Pro1. Then the PC displays my Devuan desktop while the phone screen is free for using Android apps in parallel. As the RDP decoding is then done
  4. The AOSP security bulletins are here: https://source.android.com/security/bulletin Everything since April 2020 is unpatched in stock Android 9. LineageOS picks up the open-source patches from the security bulletins, but can't do so for the (closed-source) Qualcomm fixes, which would have to be implemented by the device manufacturer. That's why a recent LineageOS will display an "Android security patch level" of "5 April 2022", while the "Vendor security patch level" is stuck at "5 April 2020" on Lineage, too.
  5. In that thread already linked above, @Zahkc and @order#10248 explained how the a/b partitioning scheme of the (original) Pro1 can be used for dual-booting UbuntuTouch and LineageOS. As the procedure is pretty generic, I suspect this might work with any a/b device. The major usability issue I see with such a setup (without ever trying it out) is that upgrades -- necessarily -- must be tricky, and that data sharing between the two OS's can be cumbersome as both use app confinement and fight about file ownerships. If your use case has changed toward requiring Android compatibility, I wo
  6. Interesting discussion. What I have observed with some WiFi's run by shopping malls is that they block price-comparison websites. <conspiracy> So maybe the have an interest in locking your out of your mobile network ... 🕵️‍♂️ </conspiracy> On a more serious note, in my daily life, I lack mobile network just too often. I travel by train a lot, and there are still too many uncovered areas in the open countryside. At my working place there is practically no chance of having mobile data at all (radiation protection walls). So I rely on local WiFi's even for phone calls much of th
  7. No offense, but that does not seem very practical to me. The only network you can trust on that level is one you configured yourself. For most users, that would mean to connect their Pro1 to the Internet only at home. At that point it is not really a mobile device anymore ... We do agree that banking is best done at home anyway. I use only my PCs and separate hardware tokens for that. In fact, by relying on security of a single system (the phone), most banking apps undermine the very principle of two-factor authentication which lies in using two independent devices that are air-gapped fro
  8. I am not sure if "recycling" an old Android device to run any Linux home servers is worth the trouble, considering how cheap and powerful RaspberryPis (or similar single board computers) have become. They provide a full-featured and well-supported GNU/Linux environment, with Docker just an "apt install" away. With Android chroots, you'll always be on your own to solve any issues emerging (trust me on that 😉 ). I do not know about Docker on Android. Yes, it seems like a lot depends on what your kernel provides. I would guess that installing everything manually in a chroot should always be
  9. Uploaded my latest build, dated 20220411. It contains the security patches backported by LOS from the 5 March 2022 ASB. I bumped the security string locally to reflect this. Otherwise, no changes from the last release. The full list of mods with respect to upstream is available at the link above.
  10. I probably shouldn't have hijacked this thread for advertising Debian-on-Android containers/chroots. While I love to have that possibility with my Pro1, and use it every day, this is technically not comparable to running a foreign OS on the device. What we actually do, is just run a second userland on the existing Android Linux kernel, which is rather trivial and probably considered "cheating" by the authors of Project Renegade. 🙂 The cool thing about Project Renegade is that it can run Windows ARM (or an upstream Linux kernel and OS!) natively on the mobile device. Technically, t
  11. I see and fully support your point that aggressive ranting about F(x)tec, as is popular on the IGG forum, does not help anyone and certainly will not lead to better communication. However, what you are insinuating is also wrong: customers should not need to be "friends" with companies they do business with in order to get support queries answered. Anyway, your "system" is not scalable: if we all had personal ties with the guys at F(x)tec, their mailboxes would be flooded with cat pictures in addition to our user requests. I do not see how that would improve responsiveness ... 😉
  12. On Linux, there are tons of solutions for running x86(-64) code on aarch64 efficiently. Besides traditional qemu, there are new projects like FEX and Box86/64 that, reportedly, can do amazing things. However, most of the time, emulation is just not necessary. Linux has supported ARM for so long that every major distribution has an aarch64 branch containing (almost 😉 ) all the software you will ever need ...
  13. I had heard of it. Technically, it looks like an awesome project. The only reason I did not dig deeper is that I am no Windows person, full stop. I achieved my (Linux) laptop experience with the Pro1 quite some time ago and and have been a happy camper since. The big advantage of a Linux desktop is that it can run in parallel with Android (using the same Kernel) so that you do not sacrifice any "smartphone" use cases in favour of running the desktop OS. I do envy them for their accelerated 3D graphics though, which is not at all possible with my solution as of today. 😞
  14. @fxtec-preorder-47xx, you are right in your criticism of F(x)tec not updating their website (again). However, there is little we here can do to change that. What we can do is keep up a respectful way of writing to each other inspite of our common disappointment about what is happening. Please think about it.
  15. Sorry, but this is not true. You quoted a post of @VaZso, and then responded with the opening sentence "Don't you think ...". I am ready to believe you did not mean to address your rant at @VaZso, and that the impression of you doing so just resulted from a careless writing style of yours. However, this interpretation is all but "obvious" and, even if true, would still call for an apology. In other news, all-caps are usually considered equivalent to shouting, for which there is also no need here. Even if we all frustrated about manufacturing delays and F(x)tec's communication skills
  16. @Dean you accidentially posted in a forum aiming at constructive discussions. The place you are looking for is the IGG comments section. Your useless ranting will blend in nicely over there.
  17. Happens to me too. First time it drove me nuts. I think I hit that poor, inncocent Caps-key pretty bad. 😳
  18. @daniel.schaaaf and @VaZso: I think we already discussed that elsewhere, right? I have not found any switch to enable or disable sticky shift. Interestingly, I found that the feature does not work in all apps: On my setup, "typical" smartphone apps like messengers and firefox tend to have it enabled, while more advanced things like terminal emulators and text editors usually don't. Seems like apps can choose to support that accessibility feature or not.
  19. As @Jacob_S point out, all editions of LineageOS for the original Pro1 have the sticky-shift feature enabled. We do not know about the successor Pro1-X yet (Pro1 is no longer available). I might add that, because of the large size of the Pro1, I find it is not practically possible to use the keyboard while holding the phone single-handedly -- with or without sticky shift. You'll still have to put it on a table when typing with one hand.
  20. I'm not downplaying the known bad communication skills of F(x)tec, but this fact alone would have led other manufacturers to say: "Well you broke it, and, after that, you probably made things worse by exchanging parts yourself. Our <shiny-new-successor-product> is superior to your broken phone anyway, consider buying that as a replacement. Otherwise, please don't bother us anymore."
  21. Interesting. I wasn't aware there were file types one could not send via bluetooth. But you are right: shell scripts are not accepted for me either. Not that I use BT file transfer much (ssh rules!), but I might still include this in my next ROM, too. Thanks for sharing.
  22. Thanks for sharing. Few would think about the SD card being the reason for the long boot time. Good luck with your next card. I've had a Sandisk Extreme 256 GB almost since day one. I run my GNU/Linux chroot on it (which certainly causes above-average disk-I/O) and it still hasn't failed me.
  23. No, I think it won't. UbuntuTouch for the Pro1 (and for the Pro1-X, as far as I know) is a hybris port, meaning it does not actually use it own Linux kernel. It re-uses the kernel of the original AndroidOS that came with the device (together with other core parts of Android). That basic support for the Pro1 is in mainline now, is certainly a good thing in itself. But right now it allows not much more than booting to a terminal. There is no support for any advanced hardware that one needs for the device to fulifil its purpose as a phone. It may be an interesting starting point for new
  24. In LineageOS 16.0 this works: long-pressing any accentable character on the hardware keyboard (e.g. 'a') brings up a selector box allowing you to pick any accented variant ('à', 'á', 'â', 'ä', ...) using the touchscreen. The box looks a bit rustic, like using a design from previous Android versions, but it works. Not sure about the later Lineage versions 17.1 and 18.1. Note that this is for the original Pro1 only. We still know nothing about software for the new Pro1-X. The LineageOS ports for the Pro1 will no longer work because of the different SoC. A new port will be necessary and prob
  • Create New...

Important Information