Leaderboard

🙂

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?".

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. 🙂

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, i accidentally swapped the two connectors going into the display unit and powered on the phone. So the display connector was on the front camera connector and vice versa. I did this because i was troubleshooting the display not working, which was mostly a contact issue from dirt in the fpc connectors. It was late and i was getting increasingly stupid 😄 Well now i can't get a picture or any response on the screen anymore and i was wondering if this swappage might have broken something. Before i order a new display i was hoping you guys could tell me if you think that either t