Hardware

Apple Watch: ghost touches are a problem that has not yet been solved

Apple Watch: ghost touches are a problem that has not yet been solved

That of the “ghost touches” there remains an annoying problem with some Apple Watches that the Cupertino company apparently hasn’t solved it yet. The latter is aware of this, as confirmed by a note sent to authorized service providers in February, but it is still working on a remedy.

In the aforementioned note, Apple stated that it had learned of the numerous reports from users in possession of Apple Watch Series 9 and Ultra 2 and invited the assistance centers to do not replace affected units. The reason? With a software update the problem would be solved, so a change was not necessary.

Ghost Touches on Apple Watch? Here is the solution suggested by Apple

An update arrives in these hours, but it is not the one that users were hoping for. In a new note sent this week to the same suppliers (shared on the web by the account @StelleFudge su X), Apple has revealed that the ghost taps bug actually affects also the Series 7, the Series 8 and the first generation Ultra.

However, although several months have now passed since the first communication on the matter, even today those who provide authorized assistance do not have to replace the device but – while waiting for new software – must simply invite the user to restart his wearable. To do this, just press and hold the side button and the Digital Crown at the same time for at least 10 seconds until the Apple logo appears.

The phantom touch problem is now for months a nuisance for several users who own an Apple Watch (from Series 7 onwards). According to what we read on the support forum and on Apple’s Reddit page, for some the made-in-Cupertino wearable would have even become unusable.

«A few days ago my Ultra 2 was “possessed”. When I woke up, the display said “incorrect passcode, try again in 3 hours”. Blame the phantom touches, and in the meantime he wasn’t responding to my commands. I couldn’t turn it off, so I had to force restart it. Not that this solved the problem.», is one of the comments.

Leave a Reply

Your email address will not be published. Required fields are marked *