Leaderboard

I haven't experienced this problem, and I don't think anything we changed in the May 16th build would cause this. I talked to a MindTheGapps maintainer, and he has seen this sort of problem if the device isn't rebooted (to recovery) between sideloading LineageOS and MindTheGapps, or if there isn't enough available space on the device. Are either of these a possible cause in your case?

That was what we were starting with. 🙂 An I2C chip has an address which used for communication and usually devices have pre-programmed address or addresses. For example, address may be selected using one or more pins at the IC or it may also be a setting. In a few cases (specific circuits) also a custom address can be given. This case we have an address of 0x14 and also found a 0x5D address is an option (above in this thread). I have looked in other model numbers like gt1151 which had a different set of I2C addresses which may have a reason or at least it is not the same IC

Another option would be to find I2C line of touch controller (physically), attach a logical analyzer, then let stock OS boot and analyze its initial communication during boot process. 🙂

You are right and it seems the manufacturer of touch screen controller is correct but the actual model is basically seems to be different. This document states "GT928 has 2 sets of slave address 0xBA/0xBB & 0x28/29" but we have address 0x14 with an alternate address of 0x5D which is different than what is written in this document. However, it may be a very similar command what we need or (considering it is the same manufacturer) it may also happen to be the same, however, I would not try it. I have only found it described as "gt1x" but a better model name may help and a pdf whi

I'd also like the original APK/set of files used to fix the edge issue in 17.1. Let me share my experience and research here: 1. When flashing to stock to resolve the issue, having the phone actually boot up the most recent update is necessary. Otherwise the fix does not work. I know this because I tried flashing an old version of stock and installing the stock OTA updates via the normal (booted!) route. The issue did not go away at any point during this. I then flashed the non OTA 2020-08-25 stock version again and let it boot. Only then was the issue resolved. 2. Given that th

Hi, pressing the phone turned out to have solved the problem, but not until I rebooted the phone.

Before disassembling, try applying good pressure to the marked position on the phone's back cover, that can put the connector back into place; for me, it has done the trick several times now (see also here) and so far I didn't have to do the disassembly at all (as to not adorn myself with borrowed plumes, the original image in this case is from androidauthority.com, I've just added the mark):