Leaderboard

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

Either this or someone (FxTec maybe) will be selling a working replacement screen 😜

Lineage purges old builds as they do not want to promote the use of outdated (and thus unsecure) roms. It is however totally possible to build all supported branches (16.0, 17.1, 18.1, 19.1) yourself, in which case the latest security patches from the upstream Android project get included automatically. Such builds are then "unofficial" in that they are not signed with the keys of the Lineage project, but otherwise they are based on the same source code. @daniel.schaaaf maintains an unofficial lineage-17.1 rom for the pro1. See this thread. Myself, I maintain an unofficial lineage-16

Still, my data will be lost. In such case, I will endure the annoyance of broken screen for now and wait for some less invasive solution to this problem

Though you have to flash to stock to fix, you are not stuck at stock! You must boot once into stock, to the language selection, but it will still work after flashing to e.g. Lineage.

I once found an issue with the forum and contacted Fxtec support about it, which was for once responsive and helpful, if I remember correctly (it's been a while)...

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.

Caps also. Ought to toggle on&off

🙂

I agree with you. They aren't really going to give us the time of day without some serious planning and trick cards. As far as attorneys go, there are enough people concerned with this even outside PKB community that want the same phone freedom. Crowd funding could go a very long way in hiring an incredible attorney to build a solid case for us. Prior to getting to that point, we are working on solving negotiations ourselves. Identifying members that have close family or friends on the inside at at&t or Verizon, learning through them how everything works so that we can make more thor

Decided to upgrade now because i must at somepoint anyway. First impressions are good, everything seems to work with magisk v24.3 and MindTheGapps. The extra dim mode is very very welcome with the pro1, now i can finally get the screen brightness to a reasonable level in dark.

Beloved community, here it is: Another up-to-date outdated ROM to satisfy your custom ROM fetish. LineageOS 17.1 JeBB "A noble spirit embiggens the smallest man!" is (so far) a slightly modified build that will be updated in irregular intervals. Future builds may contain additional fixes, or I may attempt to fix things with a Magisk module ... "may" is the important word here 😉 This build can be installed from scratch like any LineageOS build (LineageOS Wiki). Dirty-flashing from the last official LineageOS 17.1 is possible, but the official signature keys have to be exch

I tried several times over the last couple of days to reset my forum password, and the email never came. Fortunately I eventually remembered my password, hence this post, but it seems that is broken. Could someone investigate it?

Yes, it is. Actually my saga is longer and more convoluted. I had a cracked screen. Installed a new one like I did last year. Touch wouldn't work at all (like last time). Not only the edges but no touch is registered. I then went back to stock to see if the touch issue would be fixed. No dice. Plugged in a keyboard and mouse and tried to set up the stock firmware because I read that an OTA update might for stock solve the touch issue -- read it here: However, stock would show 'no updates'. But when configuring the device I realised that Google asked me to confirm on my other devices

Please let us know if your charging problems change when running LineageOS 19. The official procedure for opening a bug report (at https://wiki.lineageos.org/how-to/bugreport) is still the best way we have to track problems, so please open one if you have new info to report. As far as we have been able to tell, the charging issue is triggered as the device ages, and two LineageOS developers have now reported similar problems. This is difficult to nail down however, as there are no new Pro1s being made that might be free from charging trouble with the latest software. However, our oldest d