Re: Detect failed login attempts

[jmjc...@gmail.com]

Yes, with Logcat Event context.

On Wednesday, February 24, 2021 at 4:15:47 AM UTC+8 Timo wrote:

Is there a way for Tasker to detect failed login attempts using fingerprint?

[João Dias]

Create a new profile with the Logcat Entry event and use the helper to find which log corresponds to the failed login event :) Check this example: https://www.youtube.com/watch?v=2YH0JBSdpNE

Thank you for your contact.

   Join: connect multiple devices (send pushes, remote SMS, notifications) on Android, Windows, Mac, Linux

   Tasker: customize/automate anything on your phone!

   AutoApps: add advanced functionality to Tasker via plugins

     

João Dias

[jmjc...@gmail.com]

It really should work.

When you follow the video, of course you are trying to find failure attempts and therefore, you should use a finger that is not registered on the sensor to create a few failures and then follow by a successful unlock, what logs do you find? There should be a log that records a fingerprint authentication failure. Did you not find such a log? I know there are lots of logs to go through. It is a tedious process. You can try "fingerprint", "authenticate", or "failure" to see if that helps speed up the search process.

I am devcies on A10 and A11 and they all work. What device do you have?

On Friday, February 26, 2021 at 4:43:31 AM UTC+8 Timo wrote:

Hi, 

I did everything like the video, but i am afraid it doesn't work anymore on android 11. What are my other options?

Op woensdag 24 februari 2021 om 20:10:28 UTC+1 schreef joaomgcd:

[jmjc...@gmail.com]

If you have done it correctly, searching for "fingerprint" should return tens of logs, not just a few. Have you used the Logcat Event context before? Have you granted the related permission yet?

On Saturday, February 27, 2021 at 4:19:22 PM UTC+8 Timo wrote:

Thank you for your answer. I have a Galaxy S10, with Android 11 and OneUi 3.0. When i search for fingerprint in logcat (after i locked the device and tried to unlock with non-registered finger), there are some entries like 'should listen for fingerprint', witch are followed by a longer logcat entry. I think that entry is my false finger, but when i select it, it doesn't get triggered.

Op vrijdag 26 februari 2021 om 02:40:03 UTC+1 schreef jmjc...@gmail.com:

[jmjc...@gmail.com]

Do you see entries with the component "FingerprintService"? I believe this is the one on Samsung that handles fingerprints. If you don't see those entries, then something is not working correctly.

On Friday, March 5, 2021 at 12:21:30 AM UTC+8 Timo wrote:

I think i did use it before, to trigger fast charging. It indeed does bring up a lot of entries but the 'should listen for fingerprint' is the repeating one.

Op dinsdag 2 maart 2021 om 02:50:19 UTC+1 schreef jmjc...@gmail.com:

[jmjc...@gmail.com]

It is trial and error. But there should be one that matches your requirements the best. For example, one that says "authenticate" or one that says "fail", "failure" or etc. You have to look at every one of them and make your best judgement. Logs are different for each brand/model, there is no one for all solution. If you take 5-10 minutes to go through all FingerprintService logs, you should find one that works.

On Saturday, March 6, 2021 at 3:44:32 AM UTC+8 Timo wrote:

Hi yes, i see a bunch of 'FingerprintService' listings. But witch should i have?

Op vrijdag 5 maart 2021 om 03:50:47 UTC+1 schreef jmjc...@gmail.com: