Feature Request

[Kira255]

As you all may have noticed, sometimes fingerprint don't work as it requires pattern or password to be entered for security reasons every 72 hours.

 At that time the fingerprint sensor don't even activate screen and in case of in display fingerprint scanners, symbol for fingerprint is not even shown.

 It should be more like screen should turn on and ask for pattern or password, instead of us pressing the power button to turn on screen, swiping and then entering password.

 This little improvement will increase experience a lot.

 If you agree please like it so Samsung will hear us and add this change in future updates.

[ŠůmèəȚ]

Turn on Double tap.to Turn on/off screen.

And you won't need to press the power button.

[Kira255]

Yeah i know that, and use that too.
But won't it be better if fingerprint remains on and pressing it asks for password directly?

[ŠůmèəȚ]

Well ,

This is a policy enforced by Android OS (Google). Samsung is not forcing it.

Here are the guidelines of Android OS:

If you choose biometrics recognition, which includes using Fingerprints or Facial recognition to unlock your phone, the screen which requests your PIN, Pattern or Password may still appear instead of Fingerprints or Facial recognition in some cases according to the policy of Android OS.

1. If you have used and unlocked the device using Biometrics including Fingerprints or Facial recognition in the past 24 hours.

2. If 4 hours pass without an additional unlock operation after unlocking your device using Fingerprints or Facial recognition.

3. If 72 hours pass after unlocking your device using a PIN, Pattern or Password while fingerprint is set as screen lock type.

Additionally, you can only use a PIN, Pattern or Password to unlock the screen after restarting the device or when you don’t use the device for more than 24 hours.

Official Article:
https://www.samsung.com/levant/support/mobile-devices/how-to-use-and-set-up-fingerprint-recognition-...

Talking from Software Coding perspective:

If there is already a source code to put the Fingerprint sensor in disabled state until password is provided, there is no way to add another source code to make the sensor enabled and show the icon. It will create conflict in the code.

[Kira255]

Yes i know its a security feature.
And i am not asking Samsung to remove it but just make entering password easy by a second.

Also it will not create conflict in code as its a rather simple change. I know because i am a Software Developer myself.
If there were no issues with using bank apps with modded OS, i would have updated it myself.

Also thank you for replying. It will help increase reach on my post.

[ŠůmèəȚ]

Cool.

I am also a software developer.
I think you are not considering the calling of sensor in the code, when it is in the disabled state.

To call the sensor, you will have to enable it. This is where it will show a conflict.

Moreover,
Hypothetically, if it is possible.

Someone, will come and say , why it is showing Fingerprint icon when it needs password.
😂😂

[Kira255]

The best approach would be to give a setting option in good lock so anyone who want it can enable it.

And best approach would be if that feature is enabled then the fingerprint disable function is not executed.

And directly go to authentication where instead of matching with stored fingerprints it should skip to password screen directly if 72 hours have passed

This way normal people won't complaint too 😂😂

[ŠůmèəȚ]

Don't you think doing any of that is a violation of Google Android OS security policies.

It is an open Source Code for non profit Custom Roms.

But companies who are commercially using these have to imply with keeping the sensor disabled if any of those 3 parameters met.

[Kira255]

https://source.android.com/docs/security/features/biometric/measure#biometric-classes

Well it only mentions to fallback on primary authentication and don't mention explicitly that fingerprint should be disabled.

As fingerprint will only be used to turn on screen and land at primary authentication page, so it should not be a violation !!

Man didn't expect to have a tech discussion on this app 😂😂

[ŠůmèəȚ]

I am sorry 😂
I got carried away with that kind of discussion.

I still disagree 😂
But it is okay. We should not discuss code debugging here.

Peace ✌️
(Nice discussion, by the way)