Many users have taken to online forums to voice their complaints about the Galaxy S10 fingerprint sensor issues. They feel that the in-display fingerprint sensor on the Galaxy S10 and Galaxy S10+ isn’t as good as it should be. Bear in mind that this appears to be a polarizing topic because others feel that it does its job very well.
Samsung has acknowledged that some users have been complaining about the need for improvements. The company has confirmed that the fingerprint sensor’s performance will continue to be improved through future software updates.
Firmware updates to address Galaxy S10 fingerprint sensor issues
The very first firmware update for the Galaxy S10 did bring improvements for the fingerprint sensor. A Samsung official said that the update improved the accuracy of the in-display sensor and that “we will continue providing updates to make the scanner work better.”
It was also pointed out that the fingerprint sensor may not work well on some occasions. You could face accuracy issues if you’re in a very dry environment, the skin on your finger is really dry or if there’s a cut or scratch on your fingerprint. Some of our colleagues find that to be true. Simply keeping your hands moisturized makes a noticeable difference.
The Galaxy S10 is Samsung’s first flagship smartphone with an ultrasonic fingerprint sensor. It’s faster and more accurate than the optical sensors found in other smartphones. The sensor uses a high frequency ultrasonic sound to effectively create a detailed image of the fingerprint.
You will find an improvement in the accuracy once you have used the device for a couple of weeks even if it feels that the Galaxy S10 fingerprint sensor issues are really serious right out of the box. Some of our colleagues also feel that the ultrasonic sensor works very well and that all this fuss is for nothing. What camp are you in? Let us know in the comments below.
The post Galaxy S10 fingerprint sensor issues to be addressed in future updates appeared first on SamMobile.
from SamMobile https://ift.tt/2JcA8kq
via IFTTT
0 comments: