Jump to content

claude0001

Members
 View Profile  See their activity

  • Content Count

    760

  • Joined

  • Last visited

  • Days Won

    108

 Content Type 

Everything posted by claude0001

  1. claude0001
    You must be new here ... Sorry for the pun, but you'll soon learn that f(x)tec is no ordinary business ... 😄
  2. claude0001
    I wouldn't worry about those. My Pro1's (got two of them) and my Pro1-X have had these black spots in the corners of the screen since day one. They haven't worsened over time (we're talking years for my initial Pro1)
  3. claude0001

    Warranty return

    claude0001 replied to tonism's topic in Support

    They have previously stated that they no longer have spare parts for all components of the OG (SD835) Pro1. So, depending on what's broken, they might simply not be able to repair it. I'm just guessing, though. For any other company that wouldn't be a big deal - they'd just send you a completely new phone. In F(x)tec's case you could ask them for a new Pro1-X. However, considering the rate at which they manage to send those out, also that could take a while ... In two years, they managed to get out an estimated couple hundred Pro1-X's into the wild. I.e., on average, they ship ~1 pho
  4. claude0001
    I've just uploaded my latest build of LineageOS16.0 (for SD835 Pro1), dated 20240820, to https://findus.zwergenschaenke.net/~puma/linux.html#lineagepro1 Changes since last month: Includes backported security patches up to the August 2024 Android Security Bulletins. Updates the bundled system WebView to Chromium 127.0.6533.103 (as shipped with official LOS 20 and 21). Have a lot of fun!
  5. claude0001
    I unfortunately have to agree. The aftermarket is flooded with Pro1X's that Expansys sold for 300 $ a piece (that's how I got mine). No one is going to give you 800 bucks for that thing ...
  6. claude0001
    I had this once (after dropping the phone) and solved it by re-seating the screen connectors in the top unit of the phone. Disassembling the top unit is quite easy. I've done it many times. Take a good look at the instructional videos before though.
  7. claude0001
    I cannot reproduce this with my Pro1-X. Not using Termux, though. I'm running Debian 11 in a (rooted) chroot of LOS 20.0 and use ConnectBot as my terminal emulator. Your script works fine (with some trivial changes to match my environment). As, also for you, the keyboard behaves normally in other apps, it seems to me that you are somehow triggering a bug in the terminal emulation of Termux.
  8. claude0001
    I've uploaded my latest build of LineageOS 16.0 for OG Pro1 (SD835) to https://findus.zwergenschaenke.net/~puma/linux.html#lineagepro1 The ROM dated "20240807" gives you backported Android security patches up to the July 2024 ASB. There are no other changes since last time. The full patchlog, documenting all my changes relative to unmodified LOS 16.0 is also available, as usual. Have fun.
  9. claude0001
    <off-topic> In recent (12+) Android versions, you have to disable phantom process culling to run Linux distros in chroots, otherwise the OS will randomly kill your Linux programs. Google thinks this is a feature, but luckily they introduced toggles to switch it off in Android 13 and beyond. Requires some form of root access though. I have Debian 11 running in a chroot of LOS20 on my Pro1-X, so it is technically feasible. Not using it daily though, as I like the OG Pro1 better. </off topic>
  10. claude0001
    I guess this is about a Pro1-X (SD662). I've got the same issues with OpenCamera on LineageOS 20.0: Random hangs during focussing and zooming, which make the app useless for spontaneously taking a picture. Doesn't matter whether one uses OG Camera-API or Camera2-API. The default LineageOS camera app (org.lineageos.aperture) works fine without these issues. It cannot use Camera2-API and I am not sure if one can install it on stock Android, but this does show that the camera is useable in principle (though not of high quality).
  11. claude0001
    That's quite similar experience I had before fixing the antennas of my prawn-x. One one side of my flat calls and data would work, on the other not at all. Can depend on what bands are strongest in different places ... Also in my case, wifi was unaffected and always worked. Its on a separate antenna module.
  12. claude0001
    Supporting what @Hook wrote, and quoting the official LineageOS wiki: Alternative ROMs cannot magically fix problems that reside in the hardware or the binary blobs of the Pro1X. Are you sure WiFi, LTE and GPS worked fine with stock Android?
  13. claude0001
    I'm sure you could ask way more for an OG Pro1 in such good condition. I'd be very much tempted, but i've got a spare prawn already. Would be a pity if yours had to spend its remaining life in a drawer. Hope it will find another loving owner...
  14. claude0001
    I use it for remote-controlling my Pro1. Works well, but the refresh rates are rather low. Obviously, this requires a third device to act as the VNC client between the phone and the external display, so it's certainly no solution for all use cases ... Also, as any mirroring technique based on screengrabbing, it cannot be used to display DRM protected content (Netflix, Prime ...). Luckily the Pro1 has true HDMI ...
  15. claude0001
    Depending on your needs, you might want to add the Izzy repository to F-Droid. It has a lot of interesting open-source stuff that does not (yet) meet the acceptance criteria for the official F-Droid repo. Aurora Store is what you want to be able to install (free) software from the Google Appstore. Some apps (e.g. official Firefox) are not on F-Droid, despite being open source ... Congrats on getting things going at last!
  16. claude0001
    As far as remember, you do have to "accept" the Google terms, even if you skip connecting the device to a Google account. That's probably because the Google Services are already installed in the Stock ROM, whether you want to use them or not. It's been a long time for me though ... That being said, the only point with enabling USB debugging in Stock Android is to trigger that initial reboot to the bootloader, which you can indeed also just do manually with the "Volume Dn + Power" combo. While there really is no special trick about it, let me try a step-by-step: Power off the de
  17. claude0001
    Fully agree. When I first got my Pro1-X, there simply were no Google-free OS options yet. Still, I remember I was able to start the phone without linking it to any Google account.
  18. claude0001
    Correct. The recommendation of backing up your partitions is lore from the early days of the Pro1-X and is largely obsolete now. To my knowledge no one has found a way to actually restore backed-up partition images. In some cases trying to do so seems to actually have caused the very troubles the backups should protect you from. If you want to flash LineageOS: Just look at the instructions at lineageos.org. They are up-to date with all required steps, including unlocking the bootloader and flashing the initial recovery image. My advice is to just follow that guide line-by-line, and t
  19. claude0001
    Just my personal opinion: I wouldn't bother with any derivative distributions and just use upstream official LineageOS. If you use that without GApps, it's pretty close to /e/-OS. The main thing they might have added is disabling AGPS (you decide whether that is a good thing.) The main security (and thus privacy) concerns with the Pro1-X are the ageing Qualcomm binary blobs, taken from Stock Android and stuck in 2022. No open-source project can change anything about that anyway ...
  20. claude0001
    It's not. Just follow the LineageOS wiki precisely. The Pro1X images at lineageos.org are ready-to-run ports of the OS, that support all the Pro1-X's hardware already and are updated OTA once per week (if you let them). No worries. The biggest obstacle can be to find a PC and USB port that supports fastboot reliably. Can be a bit of trial-and-error. This is not specific to the Pro1s though, and you might also just be lucky ...
  21. claude0001
    Building on @Hook's answer: I believe the Pro1-X still always comes with official (i.e. googlified) Android, no matter what OS you ordered. You have to flash a Google-free variant yourself. Take a minute to read about the procedures and options, following the various links on that entry point he posted. You will probably want to flash LineageOS 21. Choose between the official version without GApps or substitutes, or the derivative LineageOS-MicroG. I have always only used the former myself. For guidance, follow the very good instructions on the LineageOS wiki. Once booted, install F-Droid
  22. claude0001
    There has been a lot of restructuring of build-targets in the last three weeks: https://review.lineageos.org/q/project:LineageOS/android_device_fxtec_pro1 I guess with the QPR scheme regressions breaking functionality within one major release have become more likely ...
  23. claude0001
    I've uploaded my latest build of LineageOS 16.0 for Pro1 (SD835) at: http://findus.zwergenschaenke.net/~puma/linux.html#lineagepro1 Go for the ROM dated "20240620". Changes since last month: Include backported Android security patches up to the June 2024 ASB. Update bundled version of WebView to Chromium 125.0.6422.165. As usual, the full patchlog with respect to the unmodified, official LOS 16.0 tree is available at the link above. Have fun.
  24. claude0001
    adb is not supported on the bootloader level. Use fastboot. Step-by-step guides on flashing back to stock are found here: Disclaimer: I have not tested those instructions myself.
  25. claude0001
    For the few remaining fans of Pie, I have just uploaded a new build of my unofficial LineageOS 16.0 for Pro1 (SDS835). At http://findus.zwergenschaenke.net/~puma/linux.html#lineagepro1 go for the ROM dated "20240515". After many months of near-inactivity on my side, this build again introduces significant improvements (or so I think). As usual, it gives you security patches backported from the ASB up to May 2024. Beyond that, I finally upgraded the bundled version of WebView -- which had not been updated in 2 years -- to Chromium 124.0.636.82 (the version used by recent LOS 21).
×
×
  • Create New...

Important Information

Terms

  I accept