Jump to content

claude0001

Members
  • Content Count

    401
  • Joined

  • Last visited

  • Days Won

    49

claude0001 last won the day on May 6

claude0001 had the most liked content!

Community Reputation

704 Excellent

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Lineage purges old builds as they do not want to promote the use of outdated (and thus unsecure) roms. It is however totally possible to build all supported branches (16.0, 17.1, 18.1, 19.1) yourself, in which case the latest security patches from the upstream Android project get included automatically. Such builds are then "unofficial" in that they are not signed with the keys of the Lineage project, but otherwise they are based on the same source code. @daniel.schaaaf maintains an unofficial lineage-17.1 rom for the pro1. See this thread. Myself, I maintain an unofficial lineage-16
  2. Interesting. Did you actually measure the data rate? As I wrote above, I am stuck to around 200 Mbit/s with my UGreen ethernet, which is slower than the Pro1's wifi (but of course still fine for all everyday tasks).
  3. LineageOS 16.0 is basically Android Pie with the proprietary Google stuff removed. The Linux kernel is identical to the one shipping with the Pro1's Android OS. As it is the kernel that is doing all the hardware support, I would thus assume that a device that works in LOS 16 should work in Stock Android, too. But, no, I haven't tested it. Sorry.
  4. I have got this combined card-reader, USB-hub, HDMI-adapter, and ethernet card: https://www.amazon.de/-/en/gp/product/B093FKT9BF/ref=ppx_yo_dt_b_asin_title_o00_s00?ie=UTF8&psc=1 All features of that hub work out-of-the-box in LineageOS (16.0 over here, still). That said, performance-wise, the Ethernet adapter does not even remotely reach the advertised 1 Gbit/s: iperf3 measures ~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 ...
  5. Be aware that, as part of its security concept, Android runs every app under a different UID. As a consequence, with an ext4 FS, data sharing across apps can be difficult unless they use the common GIDs (media_rw, etc.) foreseen to that effect. In the past, many people used FAT-formatted SD-cards to circumvent that restriction, taking advantage of the fact that FAT simply does not know about UNIX file permissions. I do not know if this affects your use case(s).
  6. I do not know about stock Android, but on LIneageOS (16.0) I have two partitions on my SD-card: one formated as ext4 and one as ext3, and both just work. I did the formatting externally using a PC. The same card can also be accessed via an external (USB) card reader connected to the Pro1, so this is independent of the built-in reader. At least on the low level, I think the kernel supports all filesystems it is aware of, irrespective of the specific block device. Of course, how Android treats a partition on the high-level may be a different story. On my Lineage 16 (Android 9), I can use my
  7. This. I recall they designed the Pro1 specifically to have the USB port on a dedicated board (and thus easily replaceable) as the USB socket was a well-known weak point of the N900 (where it was directly soldered to the mainboard). But without spare parts, that design effort was futile at best ...
  8. Probably depends on what you compare to. Intuitively, it seems clear to me that rendering on a remote client must have better performance compared to running the client on the localhost. Anyway, most of the time, I use my Devuan chroot remotely via SSH. While LineageOS has its own SSH server, I agree that its CLI is much too crippled for daily use. I thus configured Devuan's SSH server to listen to the default port 22 of the Pro1, while relocating LineageOS's SSHD to port 222. That way, the latter can still be used for specific (root access) tasks to LineageOS, but "normal" SSH logins tak
  9. 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.
  10. 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.
  11. 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
  12. 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.
  13. 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
  14. 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
  15. 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
×
×
  • Create New...

Important Information

Terms