Fairphone 2: Crazy touch inputs (touchscreen issue) - workaround (for some): increase touch & hold delay

My Backup Phone is a “Samsung Galaxy S2” and it fits all my needs. With lineagos (Android 7.1) it has newer Software than Fairphone it self.
I know not every one has so simple needs for a phone like me. In My Opinion Fairphone fits every need except the needs for high availability. And that’s the Problem here.

It’s still a backup phone and better than nothing :wink: .
If you need an immediate replacement in case your phone breaks, which can happen at any given time, you may of course rely on any set of other people (family/ friends/ phone vendor) and if this fails be very angry about the result, or you may take matters in your own hands from the start and organize yourself a backup phone for your basic needs. There’s a choice.

1 Like

I agree 100% with you. My FP2’s screen is getting crazy this week, after loosing part of touch ability. This is my second screen, the first one was replaced after roughly a year, and now it fails again. I’m lucky because my micro module is still working, and the third phone case is still OK… :confused:
I knew what I did by buying a Fairphone, but I thought that it was more sustainable to buy a FP2’s to replace my non working phone… And now I have an useless FP2 and no backup phone. I seriously think to buy a new phone that will stand more than a year… To be more sustainable than 1 FP2, 3 cases and 3 screens I consumed :sob:

The good news is: Displays are back in stock.
The bad news is (from an email from support"

Due to technical difficulties with upgrading the return portal we are unable to proceed right now. But we’re working hard on it and we will get back to you as soon as we have approved your return request.

I’m sorry for the inconvenience and thank you for your patience.

@fairphone support: This isn’t funny anymore, I am waiting for this display (and this is the second time) for ~2 months now

The first post mentions that one should “try to reduce the static/friction and see if it makes a difference.” Can someone tell me how to achieve this?

To fix the swapped buttons again at the frame doesn’t work with my slim case. It comes off again when I open the case. What can I do not to get lost of the buttons and fix it again at the frame?
The story before: Some month ago I got a warranty slim case and used it since than without problems. But nowadays - meanwhile switched some weeks ago from Open OS to LOS - problems arouse with flickering screens, jumping from app to app, making the phone unusable. I calibrated the proximity sensor, cleaned the screen contacts, but all that didn’t help. So I swapped the on/off button with the camera button and it seems, that it helps.

Since I handle the #austrianfairphoners#groupbuy’s and #spareparts stock I already had many slim cases in my hands and switched many buttons too. Usually it’s not a problem, but there was one case where the button wouldn’t stick when switched.
I guess one could try to tinker with the size of the hole on the rubber-strip. Otherwise all you can probably do is contact support. If the case causes reboots with non-switched buttons and switching buttons doesn’t work properly you’re more than entitled to a replacement.

4 Likes

Thank you! I will do it.

1 Like

Hi.
FYI, I have had a slim case for 2 months now. I didn’t change the buttons but everything works fine.
One could understand from this thread that one should change the buttons, but it is worth trying without doing it first.

You are right, I did that for six month, bat than I had to change, surprisingly.

Yesterday evening I ran into the same issue again, so the switching of buttons didn’t help in the end in this case.
My impression is, that the problem lies at the on/off button itself, not at the switch at the slim case. This as well does explain, why this issue happened half a year after assembling the new slim case. I raised a request, wrote that and asked for repair. My FP2 has been delivered at the 20. Jan. 2015, 23 month ago. Probably a lot of phones has been delivered at that time, so I have to be very patient to get this issue solved.

If you take the cover and rim off, does the power button on the phone seem stuck?
Why would you think it’s the button at all if it happened half a year after you got the slim case?
Have you looked at other possible reasons (#rebootsguide) like a misfitting battery (solved with a little paper strip to press the battery against the contacts).

Yes, I did. The difference is, that I don’t have reboots, I have this flickering of the screen with changing picture sizes and starting lots of apps, which makes it impossible to put in a PIN code i. e., also without case around the phone.

Does this happen while the phone is charging?

@urs_lesse: Doesn’t matter, whether it is charging or not, no difference.

1 Like

Oops, I totally missed that. I moved this whole conversation accordingly.
Please check out the tips in the first post.

PS: I just updated the first post with additional info from the official troubleshooting tool.

Hi,
I work with the latest version of FairphoneOpen (thanks God, the version of April 1st become a new one), but a few hours age, when I activated the scrren the phone hat automatic input, very fast and did not stop.
So I shut it down and restarted it. When activating the SIM card there came automatic input, too and just in time I stoppen the Phone by removing the battery so that I could avoid the third false input.
In this state I cannot operate the phone.
Does anyone knows a reason on, more important, whot to do to come to a working phone?

I moved your post here, please have a look at the first post for a start.

The screen test worked fine.
at the moment I cant even save data, because the phone works from itself with no input by me, it goes into the flight modus automatically.
Saving data is not possible, because I cannot chose MTP in the USB-mode.
I fooled around pressing some buttons and tapping the screen, just now the screen showed
"System UI" was closed
I hope, you will find a solution for this problem, I saw none so far

Did you follow the second post? This one is the first …