Jump to content

claude0001

Members
  • Content Count

    403
  • Joined

  • Last visited

  • Days Won

    50

Everything posted by claude0001

  1. 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 co
  2. 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
  3. 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.
  4. Thanks for this heads-up. Out of curiosity: What are the differences between /e/ and plain LineageOS without Gapps? LineageOS MicroG has been available for a while (and is not classified as "beta").
  5. 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 traditio
  6. For those with GNU/Linux-chroots: UPower provides a friendly interface to display the information from that sysfs tree. E.g. rostkatze:~ # upower -e /org/freedesktop/UPower/devices/battery_battery /org/freedesktop/UPower/devices/line_power_dc /org/freedesktop/UPower/devices/battery_main /org/freedesktop/UPower/devices/line_power_pc_port /org/freedesktop/UPower/devices/line_power_usb /org/freedesktop/UPower/devices/battery_bm
  7. 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 o
  8. 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 o
  9. 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: Modified gps.conf which (for me) enables the Pro1 to get its initial fix much faster. Corrected QoS powerhint signals. Backport from Lineage 18.1. Keyboard driver: Enable high keycodes Backport from Lineage 18.1. Keyboard driver: Fn-Tab acts as Alt-Tab. Cherry-picked from an experimental patch proposed by @Slion against LOS 18.1. Was never merged into any official distribution. Keyboard: Prevent unwanted mu
  10. 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 P
  11. 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* 😉
  12. 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. 😞
  13. 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.
  14. 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.
  15. 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 W
  16. Actually, there is a (vendor) tool to flash the screen firmware without reinstalling the OS. However, it is made for Android 9 and, while it seems to work in LOS 16.0, it has been found to not work on 18.1. See this post by @Rob. S. and subsequent ones.
  17. Sigh ... Both the Pro1 and the Pro1X are designed as certified Android phones. Besides having an easily unlockable bootloader, there is nothing "open" about them. Yes, the community has been able to port LineageOS, UnbuntuTouch and SailfishOS. Like for a myriad of other phones, that is possible because all three of these systems rely on the original Android core OS of the devices. The Pro1(X) being "Linux" phones is a misconception on the side of the media that F(x)tec never openly corrected. Probably as they expected to profit from the resulting (though unjustified) enthusiasm in th
  18. In LOS 16.0 /system is no mountpoint. It is a regular folder under /. Do not know about Android 11. Anyway, my gps.conf is actually at /vendor/etc/gps.conf (with /vendor being the mountpoint of /dev/block/sde36 in my case). /system/vendor is just a symlink to there. Remember that, even with root access, you cannot easily write to those system folders as they are mounted read-only. You have to first do adb root adb remount (after enabling adb of course). Then you sould be able to edit every system file from a root CLI. The remounting is not persistent. At the next boot everyth
  19. My LOS 16.0 build 20211111 is available for download. It contains the "5th November" AOSP security fixes. Meanwhile, my version has diverged somewhat from the official code. As of today, my tree contains the following local patches: Modified gps.conf which enables the Pro1 to get its initial fix much faster (for me at least). Corrected QoS powerhint signals (backported from Lineage 18.1). Keyboard driver: Enable high keycodes (backported from Lineage 18.1). Keyboard driver: Enable Fn-Tab to (really) act like Alt-Tab. Cherry-picked from an experimental patch propose
  20. This is a user forum, and the problem seems to be between F(x)tec and US network carriers. While it would indeed be good to read an official statement by F(x)tec on this issue, this is usually not the place they publish such things. Of the users around here, @Hook seems to be most experienced with the Verizon compatibility problem, and their opinion (which you probably have read already) seems clear to me: No, the (original) Pro1 cannot be expected to work with that carrier. For the (future) Pro1X, we do not know yet.
  21. As I say, I have no personal experience here. But scrolling up that other thread I linked, one gets the impression that texting is indeed most sensitively affected by whatever changes in authentication that provider (Verizon) have rolled-out over the last year or so. The US marked seems to be quite different from the European one when it comes to vendor lock-in/lock-out. See also this thread for more bad news on the topic. I feel like I can give no better advice than to seek help from other US forum users who have gone through the same troubles. Edit: In fact, if it is true that US c
  22. I am not from the US, so I can only forward what US users have reported here: https://community.fxtec.com/topic/2133-fxtec-on-verizon/?do=findComment&comment=59026 It seems like some US carriers have started to no longer accept the Pro1 in their networks some time ago. Maybe try to PN the people in the above linked thread for possible solutions.
  23. This. I backported that patch to my LOS 16.0 yesterday and have yet to experience an unwanted double keystroke. Good work, people!
  24. I fully agree personally, though I understand the disappointment of those who bought a (quite expensive) original Pro1 expecting regular minor and major updates of the operating system it shipped with, which IS the official Android OS, not some open-source fork of it. Obviously, they have to focus all in-house effort on the Pro1-X now. However, I hope that, now that they are actively participating in alternative-OS development, also the original Pro1 will keep getting some love in the long run. E.g., I still hope for a useable UbuntuTouch port for the 835-Pro1.
  25. When I still had an official LineageOS, I was applying every weekly OTA and "su" would be preserved reliably. I never disabled encryption. Those were the days of AddonSU though, which was officially supported by LOS. Always remember that Magisk is a third-party tool before blaming the OS for it to stop working for some reason. Today I run my own builds which I install via sideload. This requires "su" to be reinstalled at every update ... one gets used to it. At this point, I would not prefer one ROM over another just for its ability to maintain root across updates. Let's face it: us roote
×
×
  • Create New...

Important Information

Terms