Jump to content

claude0001

Members
  • Content Count

    403
  • Joined

  • Last visited

  • Days Won

    50

Posts posted by claude0001

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

    I uploaded my latest LOS 16.0 ROM, dated 20220530.

    It contains the 5 April 2022 AOSP fixes. There are no other changes since my last build above. As usual, a tar.gz with all my local mods with respect to the official lineage-16.0 sources is also available.

    I had originally intended to skip the April patchlevel, and jump directly to May 2022. Unfortunately, there seem to be problems with the May patches for some other device, hence they have not been merged into the official tree yet ...

    • Thanks 1
  2. 9 hours ago, silversolver said:

    Anyone have a link to the last 17.1 for Pro1 that still works?

    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.0 as documented in this other thread, if you prefer to stay on 16.0.

    Both roms are quite up-to-date with the latest Android security patches, though I must admit I haven't had time yet to build mine with the May 2022 AOSP patches. They also include a few improvements related to the keyboard driver we backported from 18.1.

    • Thanks 1
  3. 2 hours ago, kashif said:

    it works fine with pro1 and i get very good speed as well.

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

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

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

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

    was hoping to format it to ext4 as well

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

    • Like 3
  7. 2 hours ago, toast said:

    Also, does the FAT32-only apply to all available ROMs, or only stock Android?

    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 ext3/4 SD partitions normally from standard Android apps once I identified them as "portable storage" upon first detection. However, this may have changed in later versions.

    As for the I/O-performance of the reader, I do not know, neither for my Pro1 nor for the Pro1X.

    • Thanks 1
  8. 12 hours ago, EskeRahn said:

    ...I wish they would offer the usb-board as a spare, e.g. on IGG, I would certainly buy some, as this always is a vulnerable part of any phone expected to have a long life.

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

    • Like 2
  9. 2 hours ago, matf said:

    I've tried that on SFOS too to cope with the lack of video out, but (1) performance was bad,

    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 take me directly to the Devuan CLI.

    2 hours ago, matf said:

    tinkerers have found ways to use the proprietary Android compatibility on the community port

    I had heard of that, and it may work in some use cases. Overall, I think the Android compatibility layer has harmed SailfishOS more than help it. Regarding the web-browser, too many user requests have been answered by "well, just install Android Firefox". That cannot be the solution for what is (today) one of the most important applicatons of an operating system.

    • Like 1
  10. 12 minutes ago, raymo said:

    what about PinePhone 64 and his additionnal keyboard

    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.

    • Thanks 2
  11. 7 hours ago, matf said:

    I am not objective, but I recommend [...]

    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 by the PC, performance is even better than when using Microsofts crappy RDP app on the Pro1 itself ... 😄

    I love the concept of SailfishOS which is much closer to a "desktop" GNU/Linux system and reminds me of Maemo5. Sadly, it seemed to have had some problems of late (GPS, LTE), and generally suffers from bad native software support (last time I tried, the built-in web browser was just catastrophic). I therefore doubt that I will ever switch with my Pro1. Having all that evil Android app ecosystem at hand does have some practical advantages ...

    • Like 1
    • Thanks 1
  12. 10 hours ago, OKSun said:

    I am still unclear what these security updates include. What security aspects are they improving? Should we be worried?

    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.

    • Thanks 3
  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 would advise you to give up on UbuntuTouch altogether. Technically, there is nothing UbuntuTouch can do that LineageOS can't, including running GNU/Linux software. Of course, there may be more "philosophical" reasons to continue to support UBPorts... 😉

    • Thanks 2
  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 the time. To be honest, I never worried much about it ...

    4 hours ago, Rob. S. said:

    But I guess that's what VPNs are for...

    Hmm ... not so sure about that. It is true that an (encrypted) VPN would protect you from a malicious WiFi admin overhearing your communications. But that can be achieved with any kind of end-to-end encryption, as is standard on the Internet nowadays. Protocols like https can safely be used even on a fully unencrypted WiFi from that point of view.

    What I thought we were discussing here is the (theoretical) possibility of the WiFi access point exploiting some vulnerability in your unpatched phone OS to get access to your device. I do not think that can be excluded via the use of VPN. After all, a VPN is just a virtual (tunnel) interface that relies on an existing physical network connection underneath. So, obviously, the latter has to be established normally before the TUN interface can be installed. In order to be accepted on the typical (semi-)public WiFi, you have to register by accessing a web interface controlling the AP. In theory, that would probably be enough to exploit some vulnerability e.g. in your web browser (apparently my LineageOS always uses the built-in browser for that, even though Firefox is set as default).  

  15. 2 hours ago, EskeRahn said:

    my 'Paranoia' never would let me connect my device to a net where I do not feel they are suitable secured behind firewalls. And thus never in any circumstances to a public WiFi.

    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 from one another.  

    • Like 1
  16. 47 minutes ago, savvy said:

    Not sure if you ever tried but have you successfully run docker inside your Chroot distro ?

    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 possible somehow. But I have no experience with those servers you want to set up. 

     

  17. 1 hour ago, raymo said:

    having a pro1 with a linux container ...

    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, that's very impressive. The practical usefulness is probably limited, though, as you'll hardly be able to use the device as a phone while running Windows or a desktop Linux distribution. I do not know, if dual-booting with Android would be feasible.

    • Like 1
  18. 8 hours ago, sequestris said:

    These people are my friends.

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

    • Like 1
    • Haha 2
  19. 6 hours ago, ToniCipriani said:

    They also have the advantage of having x86 emulation

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

     

  20. On 4/3/2022 at 8:17 PM, ToniCipriani said:

    Anyone heard of this?

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

    • Like 2
×
×
  • Create New...

Important Information

Terms