EskeRahn

The tap sensitive margins have to be programmed correctly. If you ask WHY the screens comes with some other default - I have no idea....

Caps also. Ought to toggle on&off

On the USB/port see this https://community.fxtec.com/topic/3556-usb-port-on-replacement-of-the-port-on-the-board/

Uh, sad that it is the same connector. It will be a pure guess from me what could be damaged as it could have short circuited 'anything'. So what could be damaged could range anywhere between nothing and (almost) everything. You could try to connect an external display with a usb to Hdmi-adapter. If that does not work it is likely a lot that is not working.

Note that there definitely ARE some odd bugs in the battery handling of Lineage/AICP. Just got the below 'warning' (seen similar before) ...Of course if you extrapolate the roughly three percent points lost over three minutes, it is strictly correct, that it will run out soon, but still a rather pointless 'warning': Dividing two small numbers with high inaccuracy leaves a pretty useless estimate of the slope. It should be over at the least ten minutes, to have any validity. And NOT shortly after unplug, where the battery usually drops its voltage slightly without any active

Smoothly installed aicp_pro1_r-16.1-WEEKLY-20220518.zip on May 5 security patch and open_gapps-arm64-11.0-pico-20220503.zip using adb sideload Known keyboard bug still there (see lineage thread) Note that the signature when downloaded as a zip is not accepted, so the loader on the phone asks you "...install anyway?".

Nope, flashing was done with the same bat-file I use each time, and this includes booting. Note that other GApps where still there - so pretty weird. And the phone was practically empty, so that was not the case either. Note that I did NOT make a factory reset when going from 18 to 19, AND that switch included being forced to switch from OpenGapps to MiindTheGapps - so that could be the real cause. (I was quite surprised that the Gapps-switch worked in the first place)

this is a gt1x driver for android, that might be interesting https://github.com/goodix/gt1x_driver_generic

The "gt1x" could well indicate x is to be replaces with some digits, According to this, at the least a gt1151 exists, so that might be a relevant guess? Have we got any good images of the print that might help? We expect a minor square chip like on this image. ADD a little more googling indicates that a gt1143 and gt1152 also exists

Important detail on a great trick. Thanks both of you.

Just retried this at 44%. and was not able to trigger it. So we still lacks a secure way to reproduce the bug.

(lineage-19.1-20220516-nightly-pro1-signed.zip on May 5 security patch installed smoothly using adb sideload and MindTheGapps-12.1.0-arm64-20220416_174313) EDIT: Warning the Android Market (AKA "play store") is gone! I tried to do the flashing again - same result. I re-installed last weeks 20220509 - requiring a factory reset, and got it back EDIT II: Re-install of today's 0516 on the freshly factory reset did not remove it again. So everything is working - loosing everything by the factory reset obviously.......

Oh! I was unaware - maybe he isn't then?

Though you see this on a Pro1, it is almost certainly an app issue, so you should try a forum for the app in question, as it is likely to also be there on other landscape devices. e.g. tablets or phones like the Cosmo and AstroGlide.

Smoothly installed aicp_pro1_r-16.1-WEEKLY-20220511.zip on March 5 security patch and open_gapps-arm64-11.0-pico-20220503.zip using adb sideload Known keyboard bug still there (see lineage thread) Note that the security update date is still stuck on March? Note that the signature when downloaded as a zip is not accepted, so the loader on the phone asks you "...install anyway?".

(lineage-19.1-20220509-nightly-pro1-signed.zip on April 5 security patch installed smoothly using adb sideload and MindTheGapps-12.1.0-arm64-20220416_174313)

Let us tag @Erik to so if he can get the page corrected.

Yup. I guess the reasson is that it require more skills to change only the display, than the whole frame. So better to sell the more expensive option than having people destroy the phone. And it could also be that the wholesale price difference is outweighed by the price of a technician, so it might also be cheaper for their warranty to change the larger part. ..obviously an argumentation that only make sense if they are able to source the parts

I do not know, but let us tag @Erik here. If not him, I hope he can arrange the needed connection.

I'm pretty sure that if AT&T sent FxTec a request for a device for testing, then FxTec wold be rather likely to be accomodating.

Is the pcb a plain old two sided or multi layer print? In the later case it can be hard to spot/fix, without a diagram, It might only leave a slight miscolurisation around an area where the fault is internally. But tiny lane, tiny burn, tiny spot...

Smoothly installed aicp_pro1_r-16.1-WEEKLY-20220504.zip on March 5 security patch and open_gapps-arm64-11.0-pico-20220503.zip using adb sideload Known keyboard bug still there (see lineage thread) Note that the security update date is still stuck on March?

Try an external hub also! It helped here using the front USB on a Lenovo Thunderbolt-4 docking.

But there have not been an update to 20200825, so even if OTA was up, that would not offer anything newer.

I'm a little confused here. Why do you need the OTA update? Isn't the issue fixed with flashing newest stock directly? Do it need to be flashing an older version with successive OTA update to be fixed?