All Activity

I have a F(x)tec Pro-1 X QX1050 It boots to I believe the fastboot screen. I've tried each of the options - Start, restart bootloader, recovery mode, Boot to FFBM and Boot to QMMI. Each option just essentiallyh reboots the phone back to that screen. It's not recognzied via ADB Devices Any suggestions on what else to try? Tried a few cables, a few computers. Thanks.

By me it is display problem - i have installed my old display with bad black corners and all is working...so thats relative good. I am now inside searching on internet for display without bad corners.

The same thing happened to my Pro1 about a month before the end of its 2 year warranty. Replacing the screen didn't fix it, so it isn't the screen or at least not entirely. Luckily this was 2021 and FxTec accepted it for warranty repair. I had to wait 6 months until they got their Pro1 parts shipments. Unfortunately, I didn't ask what the exact problem was and what they did to fix it. I was just happy to get my phone back 6 months later. It has never reoccurred.

** not fixable - touch is dead 😞

I have now crazy problem with my display (pro1-not X). On classic phones will it be for 99% mechanical/water damage problem. Yesterday my phone was out of battery...only 4%batt. I was inside tipping message when my display starts to self press random touch pressing. Pressing and pressing until powering off - out of battery. ( This same problem was on old motorola phones - low battery = problem with digitizer, bad charger = problem with digitizer) Ok phone was charged to full...but problem still. So i have removed display from frame - all dust etc i have cleaned an

Interesting, I *think* but do not know that it means does not work correctly. The trouble is, to test it, I would need to replace the screen, and I'd rather not. Lol. But you raise a good possibility. If I ever have a screen fail on my Pro1x, I will test.

Does not work you mean cannot be installed or cannot work correctly? ...i can test to edit apk for newer api support. BUT first - have you tested apk sideload from pc? Test this: adb install --bypass-low-target-sdk-block path/to/PACKAGE.apk EDIT - adb install is working on los22.2. If apk runs correctly i am not sure

Today, I found a solution, for my Pro1, for my situation (Germany). I switch from the network-type: LTE/WCDMA to global. I didn´t change following settings: Wifi-Telefone (off), VoLTE (on) And now, I can hear the call ring 🤗 (LineageOS 22.2)

Lineage-22.2-20250414-NIGHTLY-pro1x with April 1st security patch installed smoothly via OTA. MindTheGapps15, and root was maintained. Notes: I encountered no problems after the OTA going from 22.1 to 22.2. I use Magisk, but only as SU, I don't use any Magisk modules. Also, since I update OTA, I don't flash newer packages of MindTheGapps. My contention is, that since Google updates both the Gapps and Play services, there is no need to flash the newer MTG packages unless you are moving to a new full version of Lineage (new version of Android) that can't be installed OTA. I don't k

Thanks. Yes I know that. But the doc linked above lists almost nothing for the new 22.2 branch (yet?), while there are quite specific instructions for 22.1, that's why I asked about that one. As I am routinely self-building, I feel confident to compile any of the officially-supported branches and thus think I do not depend on the pre-made ROMs from the LOS build farm. However, I hesitate to ditch one of my working installs just to find out that AVF has simply not been ported (or may not be possible at all) for the Pro1 ...

22.2 is the newest on the Pro1, and most likely on Pro1X on next release in a few days. I have no idea on how to check if it got "AVF" or not..... But if you could guide... ADD: I tried on un-rooted Pro1 to check if I could see a folder "/apex/com.android.virt/bin" also just "/apex" And it reports that it does not exists (and not merely that I do not have the permisions to see it"

(lineage-22.2-20250412-nightly-pro1-signed.zip on April 5 security patch installed smoothly using adb sideload and MindTheGapps-15.0.0-arm64-20250214_082511) And we still can only select one keyboard layout, so no easy layout switching, for multilingual usage.

Lineage-22.2-20250412-nightly-pro1-signed.zip on April 5 (2025) security patch, installed smoothly using OTA BUT I have a bootloop. I think it´s because one of my activated modules in Magisk. UPDATE-1: The problem is: Iconify v.7.2.0 Not the app itself, it is one of my settings, like different colors, different lock clock, etc. (Perhaps, because I import my last settings for LineageOS 22.1 ?!) UPDATE-2: I have touchschreen issues with activate app called "Round Screen Corners & Hide Notch" v.1.2.9. Not the whole screen, but most of them. But no issues when I swipe thro

Has anyone tried running a GNU/Linux distro through AVF in recent versions of LineageOS? As can be seen from my signature, I am running old(er) versions of LOS on my Pro1(X)'s. The main reason for this is that I have relatively complex Linux-in-rooted-chroot setups in place, that are notoriously difficult to migrate to different Android releases. AVF introduced in Android 14 and 15 could be a game-changer for me as it - theoretically - enables official support of Linux-Distros in containers, potentially making my hand-made solutions obsolete. However, it is not clear to me if AV

Lineage-22.1-20250407-NIGHTLY-pro1x with March 1st security patch installed smoothly via OTA. MindTheGapps15, and root was maintained.

(lineage-22.1-20250405-nightly-pro1-signed.zip on March 1 security patch installed smoothly using adb sideload and MindTheGapps-15.0.0-arm64-20250214_082511) And we still can only select one keyboard layout, so no easy layout switching, for multilingual usage.

Lineage-22.1-20250331-NIGHTLY-pro1x with March 1st security patch installed smoothly via OTA. MindTheGapps15, and root was maintained.

Lineage-22.1-20250329-nightly-pro1-signed.zip on March 1 (2025) security patch, installed smoothly using OTA (til now not updated to 22.2)

(lineage-22.1-20250329-nightly-pro1-signed.zip on March 1 security patch installed smoothly using adb sideload and MindTheGapps-15.0.0-arm64-20250214_082511) And we still can only select one keyboard layout, so no easy layout switching, for multilingual usage.

Hello All, I got mine just last year ! Crazy story ! In the meanwhile i went ahead and got a oneplus 11 for myself. Other and switching it on and surfing with it for at most an hour or two , the phone is un used. I have the original packing too. Will welcome offers Pointless selling it cor a song ! Cheers KC

I am sure people tried their luck on the Pro1X. I just wanted to say that the app warns about having been built for an older Android version on LOS 17.1 (Android 10) too, and still works as intended.

The main problem for the Pro1x is that the app doesn't work on any version of Android after Android 10 (Lineage 17) and the Pro1x doesn't have any options older than Android 11.

Oh indeed this is also simpler for Pro1, but would be really great if it also worked for pro1X, where there are no known fix at all (except using a Pro1 to do it)

Sorry to disappoint you, I own the older Pro1 model. I edited my posting accordingly. Maybe I misunderstood what I read in this thread. I got the impression that even for the Pro1 we would have to re-flash Android, and I was excited to see that the app was able to flash the display directly on a running LOS.

This is very interesting, and seems a LOT easier than flashing to stock on a Pro1. But I lack one crucial detail, did you do this on a Pro1 or a Pro1X. It would be SO great if you provided a method for finally doing this on a Pro1X, as this has previously not been known (previously the trick was to mount the display on an a mule Pro1, and flash that to stock, and then move the display back)