Leaderboard

Calm down people. It's a minuscule company, making infinitesimal numbers of phones. You must be quite new around here for assuming they will be on time. They have never been. 🙂 Still, they have shown that they love their project and do everything in their power to deliver to their customers. The original Pro1 was delayed by months. But many (probably most?) eventually got their phones, including myself. Please just try to chill.

"fastboot devices" command at first didn't work with default drivers (yellow caution triangle over 'Android') but then I manually set Android to use the Google USB driver and then selected that it be seen as the Android Bootloader Interface (only possible using the DISK method and 'All Devices'). Now fastboot devices sees the device. WOOOOOOOOOOO

By the way, to me it seems some (if not most or even all) of the cheap screens which come through Aliexpress have a minor flaw in that the lower (seen in portrait orientation) two corners of the screen are not fully active, a small outermost part is blackened. While some of us might not even notice let alone care (only some sellers even mention this), it's something the manufacturer might not want to accept. And screens without such small faults might indeed be difficult to get for anyone at this point, not just FxTec.

On asking when my device was likely to ship, I received this response on 18/11/2021: Thank you for reaching out, we expect deliveries to be fulfilled by the end of this month - worse case December. Sorry to not having a specific ETA for you. Keep a look out for our news and updates specially on Indiegogo.

In case that function is really important to you, I have got this one: UGREEN USB C Hub Ethernet with 4K 60Hz HDMI USB C Adapter LAN with HDMI, RJ45, 100W PD, SD/microSD, 2 USB 3.0 (though I remember buying it at lower price than 50 €). All features of that hub work in LineageOS 16.0 and I thus would expect them to work in 18.1, too. That said, performance-wise, the Ethernet adapter does not even remotely reach the advertised 1 Gbit/s: using iperf3 I measure ~150 Mbit/s up and ~230 MBit/s down. On the same network, with the same peer, I easily get 300-400 MBit/s via the Pro1's W

Correct me, if I'm wrong, but isn't it expected, that the device doesn't show up under adb devices as soon as you rebooted into fastboot mode? At least it was that way for me today and I was still able to flash the latest Lineage version. Didn't have to unlock the bootloader as I did that previously, but the instruction here https://wiki.lineageos.org/devices/pro1/install only uses adb to get to fastboot mode and continues with fastboot commands.

I'm almost certain you meant 2020. 😋

Untrue. Mine was always locked.

Most people never had to. The Pro1 comes with the bootloader unlocked.

Aah. Okay ... well, I'll stay relaxed and take it as a lovable character trait of the device and still change the case 🙂

When assigning a driver manually, try to select All Devices and then "Have disk" and browse for "android_winusb" that was downloaded. Having better luck with this now.... will update but laptop at 10% battery.

I have had the same problem for a few days. Sometimes it seems to me that the leather / fabric cover is statically charging the display and causing the effect. When you slide it out of the case, the typing starts. Strange... 😕

This forum has a search function. Entering "fingerprint reader" returns the above thread as well as at least one other. That said, according to the answers in the linked thread, it seems to be a hardware issue.

Something that might be interesting: I also had the issue with blurred images at far distances. Fascinatingly, after updating the device from LOS 16 to 18 (Android 9 to 11), the camera works fine again. I don't know the exact version I was running at but if you're encountering the same problem maybe a software update can help... Obviously, Android 11 brings new problems since apps aren't adapted to it yet.

Hi! This is driving me crazy for two days now. I cannot seem to get an ADB connection during the Fastboot screen. The bootloader is locked and I want to flash a new image (magisk) to unlock it. I can only communicate with the phone when it has booted into Android and is detected with ADB devices. I've installed Android Studio tools with even the Pie (9) stuff and Google USB drivers. As soon as I restart it into the bootloader screen, Windows sees it as 'Android' in Device Manager instead of QX1000 and it has the yellow caution symbol. I cannot get it to have the r

That's the "android_winusb" I mentioned. Only got through it it by using the Select Disk method.

No luck yet Still undetected by ADB. Just getting different things to show up in Device Manager... Starting to wonder if I shouldn't use a Windows 7 device to do what needs to be done. Updating to 11 I would rather avoid since you mentioned that doesn't help. But really it should work on Windows 10. This is ridiculous. How is everyone else unlocking their bootloader?

My four months old Fxtec Pro 1 (qwerty) started act funny last week. Fingerprint reader gets very hot and stopped working. The reader is hot ecery time I try to use it. I tried to restore factory settings, but it didn't help. The phone does get kind of warm when charged with the fast charger. Faulty battery?