Leaderboard

Users on other devices reported problems with the touchscreen after this change when using certain apps. Consequently, it has been pulled for now :-( If we can fix the problems with the touchscreen, it will be resubmitted and merged again. This means next week's build will have the old bug. If this will cause you problems, please don't update until the August security patches have been merged. With luck we will have a fix by then :-)

Thanks a lot! Yes, I read the new changelog and I won´t update my system 🙂

FYI, this change was merged and has been pulled due to problems it can cause with the touchscreen and certain apps. If we can fix the touchscreen issues, it will be resubmitted and merged again.

Things are getting more and more complicated in that regard. A number of apps don't work on a rooted device, and I fear they're getting more. Now some of them will work with MagiskHide, but some won't. On the other hand, some apps don't even work on an unrooted, alternative Android like LineageOS. They might explicitly check for a non-stock ROM, or they might check for an unlocked bootloader. Depending on how they do it, you might be out of luck whether you're rooted or not. With one important app (VPN identity token) which didn't run on the unrooted LOS that I had been using I was l

From what I've read here, the driver does get updated with a stock reflash plus going through all OTA stock updates, as one of them includes the driver update. It would seem that Fxtec needed to apply the changes themselves because from some point on the displays they received (whether in production or for their repair units) were of the variation that needed them...

In Denmark it is one year full warranty, and the second year you have to prove it was the manufacturers fault. (That is why planned obsolescence is not uncommon to kick in shortly after the second year)

It is certainly not an easy road for a small company being swindled like they were. I'm amazed they got the stamina to push on, and did not just close their business. And indeed if they are so unlucky as to be flooded with warranty requests it might be very hard for them to fulfil what they legally are obliged to. So a big thumbs up from me for their will to fight, And fingers crossed on the road ahead being more smooth,

Eastern Canada. I've gotten the initial response back from f(x)tec support and they've confirmed that I am still covered, so now just going over some basic troubleshooting with them. Here's hoping!

In EU, a minimum warranty of 2 years is mandatory, regardless of what the seller or manufacturer says. See here : https://europa.eu/youreurope/business/dealing-with-customers/consumer-contracts-guarantees/consumer-guarantees/index_en.htm

How can it be out of warranty? All Pro1s are still under 2 years since they were shipped. They could decide the initial drop was at fault and say it isn't a covered by the warranty, but the warranty should still be in effect.

https://www.xda-developers.com/android-12-killing-native-sip-calling/ With that being said, SIP calling account support is getting killed off. OP might want to start looking at alternatives.

I haven't had a response on my RMA request either (week ago).

Aaaargh!!!! Mine also just stopped working. Well, the screen stopped working. I assume there is something wrong with the flat cable and/ or connectors. When connected to an USB C screen I do get an output. But the LED on the display won't light up. And I don't have a spare Pro1 😢 . Well this will be interesting then. Which one will be delivered earlier, my repaired Pro1 or my Pro1x 🤨. And Tuesday I was planning a road trip 😒. @ archseraphim please do keep us posted...