Auto unlock screen in my car

[czed]

Hi,

How to unlock the screen of a Samsung S22 without being root according to Tasker profile? Maybe with AutoInput ?

When I start my car, I programmed Tasker to play music and depending on the time of day, launches Waze with a route to avoid traffic jams and possibly other apps.

On my Galaxy S22 the Smart Lock function does not work like on my old phone because the screen remains locked until you unlock it once in the car. And with the screen locked most of the time apps won't launch.

Thanks

PS: I can unlock the screen every time in the car but the idea is that everything starts automatically...

[jmjc...@gmail.com]

You can use AutoInput to unlock your phone by entering the PIN automatically.

[Soudane GMTA]

On Wednesday, February 1, 2023 at 8:33:18 PM UTC-5 jmjc...@gmail.com wrote:

You can use AutoInput to unlock your phone by entering the PIN automatically.

I've been desperately trying to get some sort of auto-unlocking working on my phone, and I have never been able to figure out how to get Tasker and AutoInput working together to automatically unlock my device. I've tried to enter a PIN for PIN unlocking and a password for password unlocking, but the fact that the device starts out locked has always gotten in the way, during every attempt I've undertaken.

Do you or anyone have any working examples of how to accomplish this?

My device is a Pixel 5 running crDroid-v7.25 (Android 11), in case that that makes any difference. And I'm running the latest Tasker beta and the latest AutoInput.

Thank you in advance!

[Soudane GMTA]

PS: To be clear, it seems like the AutoInput commands do not run when the screen is locked.  So using AutoInput to enter text (for a password unlock) or using AutoInput to issue screen touches (for a PIN unlock) do not work on the screen with the unlock dialog.

Is there some way to get AutoInput to still perform these functions when the screen is locked?

[Soudane GMTA]

Oh!!! I figured out how to get this to work!!!

I set up a password lock, and instead of using AutoInput, I used Tasker's Type action to send the password unlock string. The unlock window accepted it!

I also have my device set up to accept the unlock string without any following "enter" command, which makes this even easier.  My crDroid OS allows this option, and GravityBox offers this no-enter-needed-after-password-entry option, also.

Anyway, this solves a long-standing problem for me.  I want to use Google Pay on my device, but I always want to use Swipe Lock. Google, in its infinite "wisdom" (ha ha!) periodically queries my device to see whether locking is enabled (password, PIN, or fingerprint locking). If not, it notifies my payment services (in my case, my banks because I use the banks' debit cards) that my device is unlocked, and my banks then disable my debit card from being usable under Google Pay. This has occurred for three different banks, as well as for PayPal when I tried it.

But by using this method that I just outlined, I can simulate Swipe Lock by detecting that my device is locked (via Logcat Entry), by detecting that the screen was swiped (also via Logcat Entry), and then by using Tasker's Type action to send the unlock string. And this way, Google Pay continues to see that my device is locked, and it then keeps my payment methods active.

I am very, very happy that Tasker offers Logcat Entry !  It's a great feature, and it has helped to solve a few recent issues for me!

[Soudane GMTA]

More detail: in my case, the Logcat Entry match which I am using to trigger the sending of the password string (via the Type action) is for Component=KeyGuardViewMediator and Filter=~RhandleKeyguardDoneDrawing .  This might vary for different devices and OS versions, so you might need to use the magnifying glass on the "Component" line of the Logcat Entry action to search for the appropriate logcat string to match on.

[JAY 9]

thanks for sharing, great tip