Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 04/21/2022 in Posts

  1. The 20200825 update is linked in the update of first post of this thread: Here is the direct link to the download: https://drive.google.com/file/d/1lEc-ummPsamKDWHpoJP6YJcH6IYS4abe/view I don't know about the OTA service in the stock Android 9 ROM, but I believe it was set up (and the updates were handled by) a contractor that is (I believe) is no longer handling things for FxTec (another reason for no further updates). They have said the Pro1x updates will be handled by Google OTA, so the Pro1x should fare better. F(x) Tec has definitely not gone out of business.
    3 points
  2. AT&T shut my Pro1 off in late Aug of 2021 after sending me a bunch of text messages and a junk LG as a replacement. It was reporting as 4G or 4GLTE and HD voice right up until they turned it off... Went into a Verizon store in Kalamazoo, MI and transferred my number that I've had for 25 years... They used an older Google Pixel 3 or 4 they had in back and a new SIM card to activate the new account. After getting it all working on the Pixel, we moved the SIM to the PRO1, changed the settings in the dialer and I've had no issues since... I've replaced the screen 3 times, and
    3 points
  3. Ok guys big thanks, this clarify lots of things for me. 👍 So I would just continue using the Archlinux container, who cover all my need at this moment. Big hug to SDRausty who created the install script in termux. The GUI isn't perfect maybe as I use Xserver XSDL apk. I spend a lot of time to configure xfce using pro1's native resolution and the touchscreen mouse is sometime a bit wonky, easily compensated by the pro1's keyboard In my opinion. But I can use the archlinux CLI without limitation in termux, and it's very practical when dealing with openoffice, weird file extension t
    2 points
  4. 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
    1 point
  5. We have a great GPS application with offline support and it supports OSM, but indeed it is difficult to get a GPS fix in SailfishOS since the Mozilla location thingie has been discontinued (very long and how long it'll take is hard to predict). Android apps can be run with compatiblity layers: either the official one (proprietary and not available for community ports normally, but tinkerers found ways to use it if they had a paid licence aside from the port) or Waydroid (free and open source). They have some limitations which usually are related to hardware access (camera, BT) or apps that hav
    1 point
  6. Update to April 20, with March 5 security patch using OTA went smoothly. Known keyboard bug still there (see lineage thread) (The download stage is substantially faster than LineageOS, But the stage after download and install called "Finalising package installation" is surprising slow though - like it is on LineageOS)
    1 point
  7. Ha, I've tried that on SFOS too to cope with the lack of video out, but (1) performance was bad, and (2) I thought it beat the point anyway since a computer is needed (even if it can be a low cost one such as an SBC, in that case I'm probably better off booting Linux from it directly). Interesting to hear that performance was better in your case with a different setup. As for the native ecosystem, there are indeed both pros and cons with SailfishOS. Having many GNU/Linux tools and a terminal with full access to the system out of the box is great for instance, but indeed it's hard to find
    1 point
  8. 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.
    1 point
  9. You might want to get acquainted with XPrivacyLUA, which can restrict what information an app gets. E.g. my banking apps are not allowed to execute shell commands. When they ask "which su", XPL intercepts and replies "[empty]". This way the app does not know that it can't execute shell commands because it gets a valid reply from XPL, but the app won't see su either. The "only" problem is that you need ... Magisk with Riru and EdExposed or LSPosed. Down the rabbit hole, never to see the light of day again. Magisk reached its EOL, Riru is a mess, and Android (including LOS!) is getting more
    1 point
×
×
  • Create New...

Important Information

Terms