EskeRahn

I think we are very few users left here, so would be pure luck if some with the same problem spotted your post...

Have you tried going back to 22.1? I would not be surprised if there are more regressions with 22.2...

As I understood it one of the reasons for the Pro1X sort of 'reinventing the wheel' was that those that swindled FxTec where the ones with almost all the drawings and source code. I could be mistaken though.

(Still no 23.0 for Pro1, so likely not going to happen, and as 22.2 is borked use 22.1 or earlier)

For me the answer where mechanic, a case. I originally experimented with a classic protective case covering the bottom part, and that solved the fingerprint problems as you do not accidentally touch through a cut-out in the frame. I shortly after switched to a flip case opening like a Japanese book. We got an extremely long thread on cases where I posted multiple images years back. Also made a post on by own blog here. The links to where I bought the many different base-models are most likely all long dead though.

Ah thanks for the info! I optimistically tried 22.2 again (20251011), still not working VoLTE not supported, 😠 (expecting the 23 I thought this might be the last 22.2, so wanted to test before 23) So going back on 22.1 (20250405)- where VoLTE works ☺️

As LOS 23.0 is now available for the Pro1X (see this), we can expect it for the Pro1 as well in a few days. Will try it ASAP and report back, if it is as useful as 22.1 or as useless as 22.2.

It will wipe it, sorry.

Strange as it may sound, the connection of fastboot is more picky than adb. Usually an older pc, a usb hub or a Linux OS seems to fix it. I primarily see the issues with Windows pc with an USB3 port. I got the issue on mine too, but even a USB3 port on a thunderbolt docking works. As an old tech guy it oozes of handshaking issues, that is a bug in the driver for Windows means it can not correctly handle if things goes too fast, and an usb2 port or a hub is enough overhead for handshaking to work...

I previously tried to report a bug - and frankly I do not want to to try that again. With neither calls on 4G nor multilingual keyboard working, and combined with ridiculous stamina, It is unusable as a daily driver for me anyway. for 22.1 it is only the keyboard that is messed up. And has been since perhaps 20.1 or even older. So more reporting the state here so others do not waste their time with it, than actually expecting anyone that can fix it to read it here,

I optimistically tried 22.2 again (20250913), still not working VoLTE not supported, 😠 So back on 22.1 - where VoLTE works ☺️

I wish I had an answer for you for what is going on. I have no idea on how the legal construction/status is, and if any assets are left at all. The fxtec site has for long just redirected to some 'placeholder'-page, but some deep links (including this community) is still kept alive (AFAIK). I have no idea who is paying for them staying alive. I'm not sure if it was this thread or another, but a year or two back, some dug up info on the company from some official British site, and the company was still alive back then.

AFAIK stuff like flex-cables are custom, so highly unlikely to find. Best chance is to find a specimen with another bug and cannibalise it for the needed parts.

There can be some apps that will not work on Lineage - or rather the problem is not really lineage, but that they expect the phone to be locked, to reduce the risk of malware stealing your login.

Spotted a more important bug that could be related with the battery waste as we discussed earlier. With the same sim in the same phone at the same location, and set for LTE only, here VoLTE works just fine on 22.1, but not at all on 22.2. So 22.2 CERTAINLY introduced some important bug in handling of carriers and bands (the sim is TDC in Denmark).