Samsung Galaxy S10 fingerprint sensor slow? Try this tip
NOTICE: We’ve created an archive of all major developments related to the Samsung Galaxy S10 lineup. We are continuously updating that page with latest S10e/S10/S10+ news so that you don’t need to search for information related to the device on a daily basis. Head here to access that page.
In October 2019 reports of a serious fingerprint glitch on Samsung Galaxy S10, Galaxy S10+ and Galaxy Note 10 smartphones started doing rounds, forcing Samsung to respond by promising to fix the issue via a software update.
A hotfix was released, but the usual delay in rolling out OTA updates meant that some banks could not take any chances, thus disabling the use of a fingerprint for authenticating transactions on the S10.
While stories of this fingerprint bug have since died, multiple Galaxy S10 users have been experiencing a slow fingerprint sensor since upgrading their phones to the latest One UI 2.0 based on Android 10.
Rather than respond immediately and unlock the phone, sometimes it takes multiple tries to get the sensor to scan the fingerprint, something that is pretty annoying. On the brighter side, there is a workaround for this issue.
In case the “keep your finger on the sensor a little longer” error message keeps popping up, you might just be doing it a little too fast. Try resting your finger on the sensor for about 1/3 of a second and it should work, just like it did for many others in this Reddit thread.
The Galaxy S10 has only received one software update since switching to Android 10, but it seems there weren’t any significant improvements to the fingerprint scanner. Maybe in the next update? No one knows, but we will let you know if it does include fingerprint improvements.
PiunikaWeb started as purely an investigative tech journalism website with main focus on ‘breaking’ or ‘exclusive’ news. In no time, our stories got picked up by the likes of Forbes, Foxnews, Gizmodo, TechCrunch, Engadget, The Verge, Macrumors, and many others. Want to know more about us? Head here.