All Activity

To make sure what is going on you will need to do as follow to narrow down the issue Wipe the phone with a factory reset, without restoring anything. If the problem persists, you got a faulty unit, that need to be serviced. Else, restore everything. Turn off automatic backup (to avoid destroying your backup) Uninstall some apps See if/that the problem persist If it does back to 5 If it does not, you know the culprit is among the ones you knocked out last Restore everything, end remove these apps only You could also do it the other way r

There are Pros and Cons of LineageOS, but I doubt t will fix what you are reporting, if it was a general problem common among other Android users we would have known, so at mentioned in the other thread, you either got a faulty unit, or some apps that causes havoc. So wiping the phone with a factory reset and no added apps is the first step.

More stuffs are working now. I have submitted patches to Linux Kernel Mailing List which may get picked up soon by the maintainers. Thanks @zstas for their work on postmarketOS 🙂

I have Pro1 so I don't have experience of Pro1-X. But I know that devs have fixed many issues on LOS. For example, the fingerprint bug that you have faced on stock is fixed on LOS (also in stock beta firmware). https://xdaforums.com/t/official-lineageos-20-for-pro1-x.4543997/page-7#post-88614419 Pro1 has (or had) an issue where phone rebooted for unknown reason. People were guessing that the reason was related to specific network band or WiFI connection. I faced that issues about 5 to 6 times during one year so it was not that common. People reported that issue was fixed in LOS. I do

I am having issues with my battery draining fast and my device turning off as I mentioned in my previous question. I am using the basic Android 11 OS, will flashing Lineage OS solve these issues? (I have flashed other phones with CM OS in the past, so flashing itself is not difficult.)

Getting the drivers working is always pain in the ass. Once that is resolved everything else is easier. Great that you were able get it working! Here is a video of the installation of fastboot drivers. It is for Xperia XA2 when I flashed Sailfish X to it but same idea works for other devices on Windows 10. Unfortunately, it is in Finnish but maybe someone can find it helpful.

Thanks all for your replies, I have now fixed the problem and the fastboot flashing lock is now working. From the devices page selecting the trouble shouter from the device properties, then going to the device driver tab selecting update and forcing a windows update to start, then selecting the optional drivers in windows update found the Google android driver, installed and now its working 🙂 Regards David

....The driver is ancient:

I see it like this in adb And like this in fastboot I have never heard of "Kedacom" BTW

Yes waited for the phone to respond with the boot loader menu then entered the fastboot flashing lock then nothing else happens no phone menu change

It is an older PC originally on Win 7 no USB 3 ports. It looks like a driver problem , I've now identified from the open USP devices & printers, The phone when initially plugged in to the USB port reports as BENGAL-IDP with no errors reported after entering adb reboot bootloader it changes and reports as ANDROID with status of Driver is unavailable Running the trouble fixer has not fixed the missing driver......

PS I assume that you await the boot of "adb reboot bootloader" to finish, ending in the bootloader menu, right?

That "fastboot devices" returns without even waiting is the expected behaviour if it does not see any device in fastboot mode. It only shows a result if the device is in fastboot mode (shows the bootloader menu). Is the hub USB 3? If so try something inferior(!) Try from an old PC, a linux PC or with an old usb 2 hub. From other threads this seems to hit 'newer' pc's with windows andd usb 3.0. So an old pc with usb 2.0 is likely to do the trick.

Hi FlyingAntero, After entering:- PS C:\Users\Fxtec> adb reboot bootloader PS C:\Users\Fxtec> fastboot devices PS C:\Users\Fxtec> It returns immediately to the command prompt, not reporting any information. So where from & how do I install the fastboot drivers you mentioned ? Thanks EskeRahn, There is no differance connecting by a hub or with shorter or longer USB cables, I'm using the supplied Pro1 USB cable

Hi @Demati, I have given up on the Pro1X and sold it, so no new info, and just a hazy memory of what I did a year and a 1/2 ago! I can say that in my step (2), if you follow the second link to the instructions, where the first bit of the read me guides “you can download the ready-made artifacts from GitLab: take the latest archive, unpack the artifacts.zip” So click on the archive link just above here, and it is in this artifacts.zip from the latest job, that you will find the recovery.img (I think from memory - I haven’t downloaded and verified). Once you have the recovery.im

@Justindo you have any updated procedures to accomplish this? Step 1 is easy enough but I cannot find the recovery image you are linking to in step 2.

Here are couple teardown guides fro Pro1 but might be useful for Pro1-X also. pro1disassembly.pdf (official service manual) https://github.com/imax9000/fxtec-pro1-teardown (made by user) https://fccid.io/2AUCLQX1000/Internal-Photos/internal-Photos-4458278 (prototype unit) Also, the vimeo account of F(x)tec has some useful videos: https://vimeo.com/user124749107 Lastly, here are couple photos taken by me when I changed the usb board (Pro1).

Thanx. Looks like the plug is solded only and it wouldn't make too much noises if the plug was torn of itself. Guess the board itself is loose. Those wholes look like it's screwed to the frame. Any chance those screws where torn of the thread ? Unfortunately the disassemble video does not supply too much detailed looks into the inside.

Fairphone similar to FxTec also offers several OS for your device (and they preinstall for you). The surprising part is how easy it is do disassemble the whole thing as it was meant to do so. In the end Fairphone is what Pro 1X should be, just missing the keyboard. And it has this really big screen. Maybe we should ask them to add a slider too. 🤔

Apart from driver, It COULD also be a connection issue, as fastboot is more picky than ADB... You could try to connect through a hub, as direct connection to newer pc's USB 3 ports have caused me problems with fastboot. I do not know why a hub helps here, but my guess is that it adds som lag in the connection, that makes fastboot more happy. I had issues with a Lenovo laptop, but using a USB 3 port on Lenovo 'docking' connected via Thunderbolt 4, make it work. I also experimented with an ancient cheap (usb 1?) hub, and it worked, but things got extremely slow, so flashing took sor

Most likely you are missing fastboot drivers. When you are in fastboot mode what does it say when you type "fastboot devices"? Is the phone recognized like in ADB mode?

@Hook I don't play games on this device, and I don't watch much YouTube. The device wasn't even hot when it turned off.

Current info for anyone else following this thread for battery replacement info: I contacted Fxtec through this form https://www.fxtec.com/contact-us about getting a replacement battery. They just got back to me and said that they have no more replacement parts available. (They didn't mention if this was temporary or permanent. But, at the very least, it's going to be hard to come by official batteries for now.) My battery has started swelling, so I will probably have to dig back through this thread to figure out which 3rd party battery is "close enough" and then do the soldering nece

Hi I'm having a problem performing the lock in adb Everything works as per the Pro1-X OEM Lock - User Manual Until I perform the actual lock command then nothing further happens , I don't get the screen on my Pro1 to confirm the lock, it remains in the boot loader screen The USB connection is disconnected on entering the lock command in adb I have a Dell Precision running Windows 10 See below PowerShell text:- I'm guessing something still needs to be installed for this process to work ? Can some one advise what I'm missing or need to do to get the Lock t

Also, would help to know how you are using. If doing a lot of graphic intensive gaming or long periods of video, it is likely to heat up.