Leaderboard

You are right we should not jump to the conclusion but it certinly sounds like a reasonable explanation why it is working for some and not for others. And on this one I wonder what havoc that could make, depending on where it 'lands'?. It does not have to be a 0 to 3.8V short circuit to cause trouble, could be 'anywhere' exposed.

This sounds like a very important find. I marked your post as recommended, and would love to hear some official comment on this. @Casey perhaps? At the least that could explain why some sees this issue and some not, as it thus seems to be related to specimens, and errors in assembly (and QC).

What an interesting turn of events. Way to go, @claude0001 If this is indeed the solution, there is absolutely no way I could do it myself. I couldn't solder two telephone wires together, let alone parts/wires of a circuit board, etc. I SUPPOSE that fxtec might take on the repair as warranty work, if only because said work would produce a phone (the original idea) rather than a pda/hpc that many folks are currently sentenced to.

Let's not jump to conclusions prematurely. I had opened the Pro1-X multiple times, so I cannot exclude that I broke these contacts off myself. One I definitely did, as noted above. That's also the reason why I did not try to make a warranty claim out of this. Then again, two of the connectors seem to really have disappeared, so maybe they were missing from the start indeed. For sure the Pro1-X had its connection issues since the first time I put a SIM in it. Lets see if others affected by the issue find the courage to open their devices, and discover similar problems. Indeed,

Wow... I suspected something like this. I'm not sure why there's glue for those contacts on the board, but they should be soldered as well. To me this means soldering wasn't great (or non existent!) to begin with and will induce all sorts of noise for cellular and wifi signal inside the phone to begin with. This will definitely cause all sort of connectivity issues and explains why some was never able to use it properly with their provider or wifi and others could.

unbelievable ! you did it ! Fxtec lack engineers like you. If my pro1x ever comes one day.... ...but however thank you ! 🙂

So, it appears that I was able to repair my Pro1-X's radios. Previously, telephony and mobile data wouldn't work for me, as documented earlier in this thread. WiFi, Bluetooth and GPS had always worked perfectly. It turned out that my Pro1X was missing most of its "antenna" connector springs. My main antenna (aka. USB) board was missing two of its three connectors, and the last one broke off while I was diagnosing the problem. See picture attached. It appears these things are really fragile. Also my "diversity" antenna board was missing one connector, which I found rattling in a

@claude0001 👍 Fully agree!

(lineage-20.0-20231111-nightly-pro1-signed.zip on Oct 6 security patch installed smoothly (*) using adb sideload and MindTheGapps-13.0.0-arm64-20230808_213316) (Did another one OTA, worked smooth too)

I missed to celebrate the 4th anniversary in September...

in precisely 1 month i wil commemorate my 3 year order status . it wil be a special day

You could try an email: info@fxtec.com or: https://www.fxtec.com/smartphones/contact-us Or try getting hold of @Casey: https://community.fxtec.com/profile/8723-casey/

https://9to5linux.com/ubuntu-touch-ota-3-out-now-with-ota-support-for-pinephone-and-pinetab-devices

The one workaround I've found for my old Pro1 with LineageOS which has the same problem is to use the 'Rotation Control Pro' app which I already had installed anyway. I disabled 'per app settings' and now I manually switch between portrait and landscape with the app's controls.

@MonCon I've experienced a "battery depletion event" once with the Prawn-X. As documented here: The battery voltage, as measured with an external voltmeter, was "0.000 V" indeed. So booting into whatever runlevel of Android would not have been physically possible any more. In that situation, the only way forward is to charge the battery using some external power supply, as documented in my post above. I guess this is also what F(x)tec are doing if you send in your device for repair.

Contrary to popular belief, that setting cannot protect you from the battery depletion bug. As @Sean McCreary clarified in some other thread, Android devices are not really "off" during "off-mode-charging". The charging screen is just a different runlevel of the operating system. The bottom line is that the Pro1X's Linux kernel has to be up and running in order to actively switch the power source from the battery to the USB charger. That won't happen "on its own". So also with off-mode-charging enabled, there has to be enough remaining battery juice for an initial boot of the OS, oth

Lineage-20.0-20231106-nightly-pro1x with Oct 6th security patch installed smoothly via OTA. MindTheGapps13, and root was maintained.

I got my device today and was attempting to enable offline charging through bootloader. What I ended up doing was booting in FFBM and now the device is stuck on the Fxtec Pro 1 X logo. I can turn it off and on but it stays on the logo. Is there an easy fix for me to get back to bootloader/start up the phone? EDIT: I solved it myself by pressing volume and power buttons long enough.

In my experience, generally red is +ve and black is -ve. I'd check the polarity with a voltmeter before connecting them.

I think @Hook previously had this problem before and found a work around. During the call, try to on/off speaker and see if your voice returns to normal.

f(x)tec is an unlucky company. Just when their DeckHD got a bit of exposure and somewhat good reviews, Valve went and announced OLED SteamDecks today with a 90Hz display. Same resolution, but considering DeckHD required BIOS updates, their sales will probably plummet almost to zero. If my Pro1x with QWERTZ hasn't been produced yet, the little hope I had about it being cross-financed by DeckHD is now dead too.

I'm having a problem when making calls on my Pro-1X. During a call, my voice cuts off sporadically. I can hear the other person just fine, however. This happens even when I have full service strength, and the problem tends to get worse as the call goes on. Phone Info O.S.: Android 11 (reinstalled after I had trouble with Lineage, if that makes any difference) Country: United States Service Provider: Consumer Cellular What I've Tried I can use the S.I.M. card in my old phone without issue. I've double checked my A.P.N. settings. I've used the voice r