I am a mostly happy user of a FP3 with /e/OS 0.23-20220412177701 (up-to-date) on Android 9. BTW, thanks to the team for all the work.
Mostly happy, because I experience frequent ghost touch. It makes the FP3 sometimes completely unusable. The only way I know to get the control back is to lock the device, wait a few seconds, and unlock it. Even then, sometimes ghost touch starts again after only a few seconds of normal use.
I know many users of FP3 with /e/OS had similar issues a few months back, but a system update was supposed to solve the problem for everyone (the posts are somewhere on this forum… somewhere out of my reach at the moment ). However on my FP3 it obviously did not suffice (still, if memory serves, it was a bit better for some time after that update).
I tried a few months ago to replace the screen protector, that was damaged so maybe responsible, but this had no effect.
What should I do? I was thinking of trying a manual Android upgrade to Android 10 or 11, but I have just read there that an OTA is on the way, and obviously I’d prefer an OTA to a manual upgrade with data loss.
No, not necessary from my part In the past some FP2s showed this problem when being connected to the charger, allegedly resulting from certain cables. But as you said, you rarely use it when charging (which is how I handle this, too ).
Sorry but I do not understand. Why would I need to upgrade to Android 10 or 11 if /e/ updates already include firmware fixes?
fair question - because Fairphone stopped releasing firmware for Android 9 mid-2020. Maybe the fix for ghost touches is in the last package and if /e/ includes this in P builds your issue gets fixed - but there were many more (brightness bug / blank screen, celltower crash,…) and for this you’d need to change major versions
I am not.
I just did a manual upgrade to Android 10, with complete data loss. For the moment (a few hours manually restoring what needed to be restored), I have had no ghost touch. This makes me hopeful! I will let you know in a few days if the issue is indeed solved.