VaZso

Basically kernel is the same as in stock, some kernel modules may be different. So this is probably in higher level, however, I did not have to reboot phone for charging yet.

I have ordered one - better to have more than having none of a keyboard phone. 😄

Also stock only had it since its last update... Heat helps disassembling screen's frame, so yes.

Wow, it shows the usual problem these displays have. However, as far as I see, they seem to be a bit worse than usual, maybe that is why the cheaper price - but at least the seller shows it.

It should work for Pro1. These displays usually have some smaller or bigger black spots mostly at one or two corners, otherwise I have replaced my screen to one of them... three times. First was a short-life unit because of insufficient glue (only two-side glue what was provided), second last more than original and third is the current one...

I expect it is somewhat usable by now or at least to the state an update may put it to a more polished state (but I don't know the actual progress). On the other hand, as @Hook wrote, they had some problems with contractor (I don't know how good their relation was and when it went wrong). Also, they had to pay for developing Pro1-X which was an unexpected change and improving the system but keeping as Google certified would also require additional money...

I think sooner or later it should have, the state of LineageOS development at shipping is another question... I unsure if I switch from Pro1 to Pro1X for a while but it may also depend if they have improved design flaws and kernel-related bugfixes of Pro1... so improved call quality at opposite side, correct speaker of handsfree mode, ability to record unfiltered audio for example. ...but Pro1's camera is really good using appropriate software - Pro1X's camera has better resolution but I hope it will also have software which provides good photo quality (better or at least of Pro1'

Anyway, does anyone have the solution which worked under LineageOS17.1? I am curious how it looked like...

Right, currently there is no solution. Anyway, I would love to see that thing which has worked on LineageOS17.1 in a hope it may add some idea or just a clue how it worked on older OS and maybe what it done but I never had that tool or anything...

It is not a firmware problem but a setting of display's touch controller which is currently set differently in available replacement displays than original Pro1 displays. Currently no LineageOS versions which modifies this setting. Maybe gt1x driver should be modified to check against these registers on driver initialization and modify it if it differs from stock values... or we should find a way to do it very early at boot... ...but it has to be done yet...

I don't think a simple APK may do it. Anyway, I have tried to experiment a little bit (see display thread mentioned by @EskeRahn), but I don't really know much about Android working and how it may be consulted to release touch panel. I was able to unbind it (it stopped working under system) but still I could not reach hardware yet. However, I have only tried to write a C code (basically for Linux)... okay, and i2cdetect. 🙂 We have a potentially good data sheet for its touch controller which has two registers what we need to modify, so the job seems to be clear but we would nee

Usually setting up SPF / DKIM / DMARC combo help about this problem as Gmail can be really problematic and handling those messages as potential spam which should be whitelisted. Setting up SPF is the easiest one(only affects DNS), DKIM needs some configuring at mail server (like exim / postfix) and DMARC is also a simple record in DNS. It worth setting these up as usually Gmail hates other service providers and even can cause problems with correct settings... An incorrectly set sender may also check silly things anyway (like blacklists, IP ranges). 🙂

Basically Gmail is very picky about these settings and I have registered this forum using my Gmail address (although SPAM filtering is practically disabled) - so it went through. I haven't checked if SPF record was set correctly. Anyway, SPF is a setting of DNS record for allowed IP addresses (as sender), another option is a DKIM record which is basically a signature all e-mails should have and there is a DMARC record (for reports) and basically Gmail like these settings... although it may be possible to send an e-mail without them, it may be harder. 🙂 Additional problem could be i

I don't know who is responsible... Anyway, you may also look at spam folder or at advertisement / promotions on Gmail. I have just checked it and recovery e-mail has arrived for me.

If we had a pinout then we may have some guess but everything may happen without knowing it... I may try to replace a screen anyway and hope it will do something. I think what I have ordered should be good but I did not have time to experiment with it since it has arrived last week (my original connector is still soldered on the beard). Here it is: Anyway, the first thing I would try is still the screen replacement. Maybe looking at the keyboard's behaviour could be still checked... Edit: I mean connector #7. Edit2: I may check if closing / opening keybo

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

Okay, so Pro1's touch controller seems to be model GT911, PDF attached. ...or at least it mentions our 0x5D and 0x14 addresses which is a calming fact... ...and yes, it also has 0x805B and 0x805C registers for setting blank area. These are R/W values, so it is recommended to read before writing and also reading stock values of Pro1 would be interesting. Also touch/release levels may be set differently anyway. 🙂 GT911 Programming Guide_v0.1.pdf

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

Another official update about manufacturing has been begun at here:

You can only purchase it together with screen, so search for a replacement screen (like screen for Elephone U Pro). (Touch is integral part of screen itself.)

The cable is basically visible, look at the photo below: The ribbon cable circled with "1." is the potential cause of the problem. The green cable is the cable of display and the black on the right is the touch cable. These cables may break by moving but most probably their connection to the display "glass" can release caused by movement.

My theory is that part (a wide ribbon cable at the bottom of display in portrait orientation) is start to move when glue of the display starts to release - only a slight moving of the display in its frame may sooner or later break that ribbon cable or glass-to-ribbon connection may releases which can cause touch or display-related issues. So a theoretically non-moving cable can start moving if display start to detach from its frame.

They have posted another update here:

It sounds strange... like there was already a contact problem somewhere... That case I would not really think a short-circuit caused during disassembly... That would be good, maybe you will notice something.