Jump to content

claude0001

Members
  • Content Count

    518
  • Joined

  • Last visited

  • Days Won

    58

Everything posted by claude0001

  1. 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
  2. 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
  3. 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
  4. 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.
  5. 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
  6. 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.
  7. This. I backported that patch to my LOS 16.0 yesterday and have yet to experience an unwanted double keystroke. Good work, people!
  8. 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.
  9. 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
  10. Uploaded my LOS 16.0 build dated 20211017. AOSP patchlevel of October 2021. Contains a version of @Slion's experimental "Fn-Tab-as-Alt-Tab" mod as discussed above.
  11. Guys ... you do need to clean your gear from time to time! 😄 Ever heard of this (famously quoted in Kubrick's "Full Metal Jacket")? Different device, same approach. 😉
  12. This. That's also the most annoying issue I have with my flap case, which otherwise serves me well (see earlier in this thread). The strap is somehow always in the way, especially when taking pictures in landscape orientation. When opening the flap by 360° it is possible to get the strap magnet to attach itself to the flap "in reverse", which gets both out of the way. But you obviously can't take pictures in that configuration. What's more: in my case the magnet of the strap is exposed (i.e. not embedded in the leather, like in yours). Believe it or not, it has left scratches on the
  13. I am ready to help, but I would first need to know what you are failing at ... Please have a look at this post, and try to understand it, following the links I provided. The first step is to prepare an SD-card with a partition containing the GNU/Linux distribution. This is best done from an existing (x86) Linux-PC using qemu as described in the first link of my post. As most modern Linux distros are based on systemd (which cannot run in an Android chroot), I suggest Devuan which uses traditional System-V init. It is possible to change the init system also in vanilla Debian, but that
  14. You are right. But @Dyna Smart do not provide much details in their report: Replaced themselves or by FxTec? Source of the replacement screen? Installed OS? My experience is that, in lack of more information, you never know what people understand by "not working at all", especially when they are at a certain level of frustration. Hell: I myself have sometimes said my Pro1's camera was "not f**ing working at all!", although this is objectively far from true ... 😉
  15. In case you replaced yourself: most spare parts now seem to require a firmware update for the touch function to work correctly. See this thread and the possible solutions discussed therein.
  16. Termux is a nice project and has some interesting features. But as an in-app solution, I guess it will always be somewhat limited. That is why I decided to install everything from scratch by myself. Note that, in the beginning, I also knew nothing about chrooting Linux distros on phones: the Pro1 is my first Android device. Do not give up! The reward for all the work and learning is that I have now a GNU/Linux distro running really in parallel to LineageOS, which allows me to use the Pro1 like an actual PC, while neither disturbing the Android environment nor depending on it in any way (e
  17. Nice job! Always good to see I am not the only one using the Pro1 as an actual computer ... 😎 By using XRDP as a wrapper around VNC, you can forward sound from the VNC session to an RDP client (I recommend MS Remote Desktop 8 as it seems to work best with the Pro1's keyboard). This way you do not need a separate XServer on Android, and the Linux session can run in the background when disconnected. I gave an overview about such a setup in another thread. I do not use termux, but I guess it cannot install XRDP and the required PulseAudio drivers for you. You'll have to do that yourself f
  18. Oh, I did read that. As I did read all the other announcements since 2019. I guess, for those who have followed FxTec's path for so long, there are only to possible outcomes: you become either a pessimist or a believer. 😉
  19. With all due respect: I think no one here ever got their phone within 3 months. Even if mass production restarts in November, FxTec will be busy for months serving all the Pro1-X backers (and probably quite a few remaining Pro1 orders). If you haven't pre-ordered a Pro1-X already, I do not think there is any hope to get it in the first half of 2022.
  20. Confirmed on LOS 16.0: With NFC switched-off, no clicking when recording from the 3.5-mm-jack. Thanks for sharing!
  21. No, don't think so. Also the device-specific code has distinct branches for 16.0, 17.1, and 18.1. That patch of @tdm is proposed against 18.1. So if it is accepted, it will be only in there. Currently the driver in 18.1 is still (almost?) the same as in 16.0 and 17.1 so backporting the patch to your local 17.1 tree should be trivial. That may change in the future, as there are several proposals for improving the keyboard driver in 18.1. I am loosely following that development, but almost certainly will not backport everything to 16.0, as I am in fact quite happy with the current
  22. Try to be optimistic. Money is not everything. I paid my Pro1 (without the "X") also more than a year before I finally got it. Now that I have a real keyboard phone, I congratulate myself for the decision to preorder every day.
  23. Build 20210922 is available. It includes the September 5 AOSP security fixes. As of this release, the build includes a backported patch, originally made by @Slion for LOS 18.1, which allows one to use "Fn-Tab" and "Alt-Tab" equivalently for switching Apps (see this thread). I find that feature really useful when holding the Pro1 by the keyboard. I have used that modified keyboard driver for weeks without issues. Still, be warned that this code has not been merged into any official LOS branch yet, and should thus be considered experimental. Edit: I think I should clarify:
  24. While I agree with most of your ideas, I think that ship has sailed. According to the last update from Fxtec, they should be in the protoyping phase by now. Even small changes to the hardware would likely introduce large delays at this point. As @VaZso pointed out, that's especially true for the Fn key which is wired differently than "normal" keys. So it is not only a matter of changing the printing on the caps. That said, I would not worry too much. My experience is that typing on the phone and on the PC "feels" so different that it does not help to have identical layouts for the symbols
×
×
  • Create New...

Important Information

Terms