Original topic:

Galaxy M42 5G Fingerprint sensor issue after OneUI 5/Android 13 update

(Topic created on: 12-21-2022 11:12 PM)
1090 Views
Mr_Ravi_G
Active Level 1
Options
Galaxy M
My Galaxy M42 5G Fingerprint sensor doesn't respond when display turns off (not instantly after screen off , but after some time , no response of Fingerprint) after OneUI 5 or Android 13 update ( updated in December,2022), i have enabled and disabled the Fingerprint sensor Respond function in settings, but nothing happened.

I have also tried by factory reset and start all ne and updated , but still issue persists.

Samsung should include the patch for this issue in a security update or so.
7 Comments
cs_member8
Moderator
Moderator
Options
Galaxy M

Dear Samsung Customer,

Greetings from Samsung Customer Support!

We acknowledge your query and apologize for the inconvenience caused to you and will surely assist you regarding the same and please follow the easy troubleshooting steps which might help to solve the issue.

When you scan your fingerprints on the device, be aware of the following conditions that may affect the feature’s performance:

• The fingerprint recognition sensor recognizes fingerprints. Ensure that the fingerprint recognition sensor is not scratched or damaged by metal objects, such as coins, keys, and necklaces.

• The screen protector supplied with the device may cause the fingerprint recognition sensor to malfunction. Remove the screen protector to improve fingerprint sensitivity.

• Ensure that the fingerprint recognition area and your fingers are clean and dry.

• The device may not recognize fingerprints that are affected by wrinkles or scars.

• The device may not recognize fingerprints from small or thin fingers.

• If you bend your finger or use a fingertip, the device may not recognize your fingerprints. Make sure to cover the entire fingerprint recognition sensor with your finger.

• To improve recognition performance, register fingerprints of the hand used most often to perform tasks on the device.

• In dry environments, static electricity can build up in the device. Avoid using this feature in dry environments or before using the feature, discharge static electricity by touching a metal object.
Note: You should make sure to use the highest central parts of fingerprint or the most curved part of fingerprint when you register or scan fingerprint

In case the issue still occurs. Please register your concern in Samsung Members Application (Open Samsung Members Application > Get help > Send Feedback > Error report).

Thank you for writing to us.
Warm Regards,
Samsung Customer Support.

0 Likes
FieldField
Beginner Level 2
Galaxy M

I have the same "fingerprint problem".

After upgrading both of my Galaxy A53 5G and Galaxy A71 to Android 13, when my phone was  in standby status, I can't unlock my phone with my fingerprint directly, I have to "wake up " my phone until the screen turn on, then I unlock my phone with my fingerprint. 

I upgraded my A53 5g first, after around ten days, I upgraded my A71. Unfortunately, my A71 got the same problem to my A53 5g. 

I can ensure that this problem happened after my phones upgrading to Android 13.

I used the same screen protector before upgrading to Android 13 and there is no problem with unlocking my phones with fingerprint. 

Please help.

 

 

Mr_Ravi_G
Active Level 1
Galaxy M
I'm also facing the same issue , Even now after a month Samsung hasn't patched it in January security patch update
Mr_Ravi_G
Active Level 1
Galaxy M
Issue still persists, my problem is not of Fingerprint recognition, it's actually absence of one-click response that shows Fingerprint icon in display.
This happens randomly, when phone is not accessed for some hours.
But i didn't faced this problem before Android 13 Update.This problem arises just after updating to Android 13/One UI 5
Mr_Ravi_G
Active Level 1
Galaxy M
Also the Fingerprint icon displayed on lock screen doesn't get vanished/fade off , as it normally does , while i connect phone to charging.

This problem i also faced only after updating to Android 13/One UI 5

Please report this to Technical team , so that it can be patched through an update.
Mr_Ravi_G
Active Level 1
Galaxy M
I'm also a Engineer, so i know very well that it's a Bug in System update ( of Android 13) that's causing this issue.
Mr_Ravi_G
Active Level 1
Galaxy M
Even now after a month Samsung hasn't patched it in January security patch update