This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Replacement with updated screen - Touch issues working randomly specially on corners

Hello, I'm opening a new Thread because the other one was closed, not sure why as it could be helpfull for both, users that have the same issue and Garmin to investigate the case.

As I said I have my third unit. This last one comes with 86.04 Screen version, so from the garmin forums this will not present the previous "delamination" screen issue.

But there is a random issue with the "screen touchs" that does not happens with old screen. Those are random bugs in detecting screen "touches" , and the obvious answer is that does not work well.

As the other thread open by describes:

https://forums.garmin.com/sports-fitness/cycling/f/edge-1030/161204/replacement-with-updated-screen---corner-of-touchscreen-not-working-1-2-of-the-time

Running the touchscreen test reveals the errors. The more important for me is that those errors are *random*, what means that either is very very slow to detect "touches" sometimes on some parts of the screen, or on others sometimes some touches or gestures does not work at all. As an example Yesterday I was unable to open the top-down menu to access to settings and I have to restart de device for get it working again, but after reboot works ok.  There is some point that almost allways fail for me, and is when you have finish your training. After stopping and recording the session, the resume screen appears and I was not able to push "X" or "Ok, verification mark" after about 10-15 seconds, and this is maintaning the finger on the screen for 3 seconds aprox.

So as a resume, sometimes in some screens touches works, whether some others on the exact same screens in other moment in time  or other screens doesn't.The nature of the bug is random.

As this issue does not allways affect to same part of the screen, I think is not related with the screen itself (the touch layer of the screen), and seems much more related to:

1. the Screen Driver Itself (perhaps the driver change with the screen, better Garmin to confirm this point)

2. Or some ramdom communication issues (sould be somewhere in the devive logs) between the motherboard and the new screen.

3. There is a third posiblitiy that is that the Screen itself is maltfunctioning, what is also even possible....

On my Third device (second replacement), I do not want to change it again unless the third screen (new one 86.04) was faulty again...

@Garmin, could you have a look please.

@People, please those with new screens with this kind of vehaviour add posts to this thread to provide more information to help Garmin to pin point better what the issue is to help them solve it (if possible).

Regards,

   Manuel.

  • I currently have two 86.04 units and I replaced my first exchange due to this issue. Both screens on the new units are not perfect as if you re-run the block test enough times, you will get 1 or 2 blocks near the edge that cannot be pushed. Most of the time the block test works perfectly.

    In actual usage though the units are fine and I've not had a scenario where a ui element remains dead to touch. The first 86.04 unit I received however was quite bad and the screen would go dead affecting certain usage cases, notably the right bottom corner of the widget loop.

    If yours is anything like in that video than it should be replaced again as mine are alright, even though you have to be slower with your inputs than a smartphone it should still work 98% of the time for you.

  • Thanks Rob, I would wait to see if with some updates get fixed, if not I would try to replace my unit again.... This is a pain in the a**.

    I do not understand why Garmin is not testing properly the units with the new screen. My impresion is that the 1030 unit never works 100% fine.

    Problems with the remote, then with potenciometer values, mobile bluetooth, sreen delamination, then new screen with touches issues...

    Let's see...