Fingerprint unlock vs Pattern/Pin/Password Unlock

[PHenriqueF]

I always unlock with the fingerprint, so I want to know if (and when) the device was unlocked via pattern/pin/password.
I know it would be easier just to change the password, but it would create questions in my family as why I did that.
Currently I did it with Bixby Routines (which has fingerprint unlock trigger). It shows a notification that is read by MD. But it's kinda unreliable due to some false positives.
So, I wanted to see if there's a way to differentiate the unlock methods in MD.
Thanks a lot!

 

[Snurre]

I don't think it's possible
But you could make a macro that log's when the screen is unlocked, then you should just remember when it was your self that logged in
Or maybe it's possible with logcat, don't know

 

[dsnz]

I always unlock with the fingerprint, so I want to know if (and when) the device was unlocked via pattern/pin/password.
I know it would be easier just to change the password, but it would create questions in my family as why I did that.
Currently I did it with Bixby Routines (which has fingerprint unlock trigger). It shows a notification that is read by MD. But it's kinda unreliable due to some false positives.
So, I wanted to see if there's a way to differentiate the unlock methods in MD.
Thanks a lot!

the question is .. why your solution is unreliable, and especially has false positives (in one's mind the most common possible issue would be missed notifications)
perhaps we could solve this

 

[PHenriqueF]

That's my macro. I'm not good at programming and deciding var names lol
But if you find any mistake in code flow, id love to know any critics

 

[Snurre]

As I read it, everytime you use Fingerprint you clear the stringTimeTracker, so when you want to check it's empty
And if there's several unlocks it only shows the last one because you set the same var
I think something like this could work, it might


Then you can check your user log

 

[dsnz]

I agree that something is not ok
I don't understand what you do with dates/times (and why) because the image hides some configuration details
but one thing is obvious
you check only by trigger, ie. unlock trugger (by any means) and Bixby notification trigger
however usually one trigger suffices to run your macro, whichever fires first
so, this means you must check for the correct situation explicitly and by a single if/else only, ie. if there is Bixby notification then .. else ..
(and not by "if trigger fired" combinations; the screen will be unlocked always so need not be checked)