Leaderboard

How (and why) would they do that? The Pro1 and Pro1X are the same phone. None of the OSs are going to require the additional memory.

The hardware is (nearly) the same, we will all benefit from porting efforts :).

Today a year has passed since I ordered my Pro1 (Qwertz).

I think the Tech Bundle is aimed at non-warranty repairs-- battery reaching EOL and breaking the screen, neither of which would be covered under warranty, not screen repairs for faulty QC or defect, which would be covered under warranty and they would supply the replacement screen.

That would be exactly what I need! I'm actually on rooted LineageOS, mind to share the driver and the instruction? Thanks in advantage!

So that should be part of the initial flash image(s) which they shared here in a place which is not OS related. If it is only about sensitivity and there is no other information can be obtained from the display, then a general solution (which work with all of these displays) is not easy. Maybe this was one of the reasons they starting to use another display (manufacturer?) in the past.

I'm not sure if it's for newer systems, as the driver is dated from 2019. Maybe it was too sensitive for the screens they got while it works fine with the ones that have a bit more insensitive edges? I don't have an older display here so I can't test right now if it still works. It probably works but might react even more to edge taps than the current one. Probably not a problem if you're using LineageOS or AICP, as there you can set you own margin, but that's just my guess. I'm not using stock, but I don't think it will break SafetyNet. To me it sounds like it's installed inside t

So, if I understand well, it is really a modified touchscreen driver. That means they may also include it in newer systems (like when they upgrade to Android 10) and also Lineage OS may use the other driver as well. Anyway, does this modified touch screen driver backwards compatible with "old" displays? That would be mandatory for the above. Also, do these instructions break SafetyNet or such things in (stock) Android?

Thanks - the screen was fine. I had 20 of those, so I could test a few 😉 But an update: A fellow member sent me the instructions and files he received from F(X)Tec - and it worked fine! And the best thing is: It's really painless if you have a rooted OS. No debug firmware needed, no reflash, no wiping of data. Just one single APK, a firmware file and access via adb to change some permissions for the touchscreen driver files. So if anyone has the same issues: With a rooted OS, it takes 2 minutes to fix it 😄

@EvilDragon take a look at this comment and the video I uploaded in the comment after it - I think it may be similar to what you say you're experiencing? This was purely a hardware issue with that particular screen replacement - the next one I got was much better.