Ghost inputs on FP4

Help Fairphone 4
178

Got also ghost inputs -.-
somtimes the problem can be triggered by knocking on the back of the device… so i could get some logcat output… mainly these two messages are displayed:

I OpenGLRenderer: Davey! duration=9222227043626ms; Flags=0, FrameTimelineVsyncId=13195876, IntendedVsync=1144993216635316, Vsync=1144993216635316, InputEventId=1072054124, HandleInputStart=1144993232648529, AnimationStart=1144993232846186, PerformTraversalsStart=1144993232861550, DrawStart=1144993233243686, FrameDeadline=1144993249968648, FrameInterval=1144993232641134, FrameStartTime=16666666, SyncQueued=1144993233511863, SyncStart=1144993244738686, IssueDrawCommandsStart=1144993245925404, SwapBuffers=1144993259628842, FrameCompleted=9223372036854775807, DequeueBufferDuration=5826302, QueueBufferDuration=794792, GpuCompleted=9223372036854775807, SwapBuffersCompleted=1144993261164884, DisplayPresentTime=0,

The ms are great :wink: 292 years >.<
I get this Message every time when i touch the screen… So it just might be a result of the ghost touch event

This is the other one… which might be more relevant…

W InputReader: Received unexpected event (0x35, 0x226) for slot 1 with tracking id 29871
W InputReader: Received unexpected event (0x36, 0x75e) for slot 1 with tracking id 29871
W InputReader: Received unexpected event (0x35, 0x224) for slot 0 with tracking id 29877
W InputReader: Received unexpected event (0x36, 0x580) for slot 0 with tracking id 29877
W InputReader: Received unexpected event (0x35, 0x222) for slot 2 with tracking id 29874
W InputReader: Received unexpected event (0x36, 0x308) for slot 2 with tracking id 29874
W InputReader: Received unexpected event (0x35, 0x21f) for slot 0 with tracking id 29881
W InputReader: Received unexpected event (0x36, 0x1c9) for slot 0 with tracking id 29881
W InputReader: Received unexpected event (0x35, 0x223) for slot 2 with tracking id 29882
W InputReader: Received unexpected event (0x36, 0x294) for slot 2 with tracking id 29882
W InputReader: Received unexpected event (0x35, 0x21e) for slot 2 with tracking id 29884
W InputReader: Received unexpected event (0x36, 0x103) for slot 2 with tracking id 29884

Anyone has the same logs?
People without this problem does the Davey! message also show for you?

179

I am familiar with Pointer Location. But I didn’t use them in the video.

180

where do i activate/see the logs? maybe i find something interesting going through them

181

Can you try this out? Inputs just around the cable would seem acceptable and somehow expectable to me. If the known vertical pattern occurs instead, this would hint to problems with the grounding of the display, at leqst in my eyes.

182

You can use apps like GitHub - darshanparajuli/LogcatReader: A simple app for viewing logs on an android device. (filter function is a bit buggy, it combines all the entries with an “OR” condition, so you can’t filter for more than one tag at once) or access logcat via adb.

At least these occur on my phone plentyfully without any ghost touches.

1 Like
183

Now, I offered a ticket by the support. My Question: Is it normal that no confirmation email comes. One has the feeling that the support ticket is sent to nirvana.

1 Like
184

you should receive an automatic mail with ticket number. As long as you received that, patience is the key😉

1 Like
185

@Martin_1964 : with activating the pointing indication as described in my previous post your video would get much more useful for us…

186

Ok, I make it again with it.

1 Like
187

The same problem occurred for me within a week of return from repair. Got a replacement phone and will have to return the old one, I’m assuming for further research.

So sit tight and hope that they can come up with an easy fix for the people that are comfortable doing it themselves.

188

Having the same issue. Anyone tried hans_de_vries method and having success?

189

Hello Sahazo,

Answer 2: The sticker can be attached to the screen. When you dismount the screen and flip it around you will see a black sticker on the screen. This is the location where the connecter will house when mounted.

Answer 3: The sticker can easily be removed in case of a warranty claim. No problem at all

1 Like
190

It is now 2 months ago that I performed my fix. The ghosting has never returned. I also am able to make the screen respond when I hover with the usb-charger cable above the screen but I do not get ghosting effects but more effects like you have when you use your finger. In other words, no ghosting effects or flickering of the screen but normal behaviour.

2 Likes
191

Some alternative to the sticker to put more pressure on the display connector:
I used a thin rubber mat from an old IR remote control and cut out a very small piece that I put on top of the connector before remounting the display. This should also not move at vibrations and is still thin and elastic enough.
Fingers crossed that it will do the trick this time.

3 Likes
192

I mainly had this problem when my phone was cold and I had a warm hand on the side of the screen. Last week i dropped it and the screen protector cracked and it got worse. When I received a new protector I took the chance to reattach the screen connector inside and thickened the foam pad with two patches of insulation tape to increase the pressure. No ghost inputs for the last two days!

2 Likes
193

Hi all!

Thanks for writing about your issues here! Just adding briefly to the conversation that I have the same problem with vertical lines of ghost touching in the centre of the screen. Bought the phone in November and the ghost touches started to occur and have gradually become worse during the last few weeks. I have contacted support of course.

1 Like
194

Dear FP community,

Since fairly recently I noticed a strange issue with my FP4 I would like to know what to do about.
Sometimes when I am writing a message, my FP4 starts scrolling up (or down) or typing seemingly random letters, without me touching the screen.
So far, the only thing that works is locking and unlocking the screen, shaking or restarting the device.
What could this be? And what can I do?

Thanks in advance for any help :slight_smile:

195

I moved your post here, please read above

1 Like
196

Same thing here. Random calls included :grimacing: i do have a small crack in the display, but i wonder if thats the problem (after seeing this topic )…

197

Hey dzwietering, after 6 days still no ghosts? The connector seems to be the mainsource of those problems.