Leaderboard

I see. I might try an older stock then, if OTA is still up i might be lucky. If I understand this correctly, if the freshly flashed 20200825 ROM doesn't do the touch margin adjustment, neither would an OTA update from an earlier version – and you might be having a completely different problem. "Screen completely unresponsive, 100% not working" would also make it seem so. But just to be sure, did you actually boot the 2020825 stock ROM after flashing it? It needs to start up once to do the touch margin adjustment trick.

I think Windows makes it harder. 🙂 Your problem may be potentially related to the USB port you use. Try to find a port which does not have other devices attached as EDL is really picky for timings. Edit: I mean in your computer there are USB HUBs which have more or less devices attached and usually not all ports on your PC are connected to the same root HUB. Devices connected to a root HUB (like internal web camera, WLAN or other components) may generate interrupts which delays communication with the phone and may cause update process running into an error.

I have checked and "CONFIG_GTP_AUTO_UPDATE" is not set in config (LOS 18.1)... ...however, as far as I know, SailfishOS also uses stock Android kernel just like how LOS does, so I don't really understand why this option would be enabled under SailfishOS. However, at least the proper firmware is there and somewhere there should be a solution to access display's firmware...

It seems SailfishOS community has found a solution here : https://cassandraasaservice.github.io/#maintenance But I guess it won't work with LOS.

I noticed this too today, iirc that bug was originally introduced in a update to LOS18.1 as it wasnt there in the beginning. Can't remember which one though. Interesting, did you use device fingerprint from another device? That is definitely not recommended as it can lead to all kind of problems. There is a working fingerprint from the stock firmware for the pro1 in the MagiskHidePropsConfig fingerprint list which is only one that one should use with pro1.

@agent008 I have never heard of an OTA being needed or used if the 20200825 version of stock was flashed. It should have the fix. There was a file floating around with files from BOE that could fix the margins of the new display on Lineage 16-17, but I suspect, as @Rob. S. suggested, you are dealing with a different problem. Last November, my original, factory installed screen stopped responding to any touch. I checked the connections. They seemed good. So I had a local shop that is very good replace the screen with a new AlieExpress screen. Still, no response to touch. That tends t

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

Okay, so it seems 0x14 is the default address for gt1x touch panel instead of 0x5D, see here: So basically gt1x codes which use address 0x5d seem to speak about the same thing.

Anyway, device 0x58 is in use by aw9523b which basically is the keyboard, 0x28 is used by nq-nci which is the NFC controller, 0x08 is used by i2c-pmic, there is a 0x38 which is used by fts, 0x4a which is used by mxt-ts and 0x14 which is used by gt1x module. So it seems touch panel is connected to bus i2c-7 at address 0x14.

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

I just removed the usb c connector and put some small wires from GND/VBAT to the outside through the USB connector hole. Luckily at work we have all the necessary tools. At some point i guess ill solder a new usb c port. For now i'm absolutely statisfied charging it on my bench PSU. Constant current until 4.2 volts and then constant voltage, right? Again im very happy that this phone is so serviceable.

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?

Hmmm it sounds littlebit hard to remote help you. For me it looks like display touch problem. Because i have not hear about fully not working touch...have you visually checked display unit ?...then all flex cables and connectors? Here can be problems with touch ... but problems like shifted touch, no touch on edges etc. about keyboard it looks like hw problem too - was keyboard water spilled?...how about connector? ...will be needed more informations about your phone

Hello, i have writen small tutorial here ....or you can order whole bottom board directly from fxtec...but it will be long waiting for it. Directly charging battery is not good idea...you can littlebit charge it with laboratory power supply , but is needed to watch whole charging process. Fx dont have qi charging. Water inside connector is problem, but it is not whole problem - you must open phone and clean all an resolder all visually coroded parts.

This is HIGHLY unlikely that it should be hardware, as we have not seen the same reported on any devices with stock Android, but multiple with Lineage/AICP. Note that there are TWO different bugs. One where it completely ignores it being connected to a charger - and that can easily be hardware. One were the battery is neither charged nor discharged, but the device is power from the charger. The second is a functionality that is GREAT to prevent over-charging a battery, the problem is that it kicks in way too soon, under seemingly random conditions. I tried the described un

A wish: When password is required (e.g. after a boot), it would be great if opening the keyboard also did what swipe up do, so we can start typing the password immediately. Though this in theory is a general LineageOS request, the usage is currently very much limited to the Pro1, and perhaps a few others....

Bad news, the charging bug is still there on 19.1 😞 Here stuck at 30% for 3h

Google pay working here with magisk v24.3 for some time already and works on LOS 19.1 too. -Zygisk mode on -Enforce denylist -Put com.google.android.gms and com.google.android.gms.unstable to denylist under google play services. You might need to check show system apps from the denylist donfiguration settings -You manually need to download and install MagiskHidePropsConfig and do the edit device fingerprint, probably no need to do this if you upgrade from v23 and have already done this. -make sure play store says device certified, if not try clearing play store and pla

A little more on battery. As said earlier generally as lenient as 18.1 There was an odd pull just around the April/May shift though (the timestamps in the images are CET w DST), The phone lay idle on the desk all day: So I guess it was Google or some other bad guys monthly collecting stolen data?