New issue with unlocking my Samsung phone via phone link app on PC

Hi all,

Just re-read all the comments, and although people have mentioned submitting a feedback request, nobody shared a link to it so we can upvote it.

So, here's the link to the feedback request (Microsoft has turned it into a "collection", which is what they do when people submit a bunch of the same feedback as different requests): https://aka.ms/AAnzhzi

Go upvote it. It currently has 180 upvotes, which isn't going to get any attention.

The bad news is that there's an official response on that feedback blaming the problem on "security" in Android 13.

There is a simple solution to this very annoying problem.

On the phone:

Settings

Lock screen

Smart lock

Enter pin

Trusted devices

Add trusted device

Select the PC you connect to

Now you will never see this annoying and ridiculous screen again when you try to open an app. Instead you will just see a button that says "unlock", and when you click it the app will open as it should. When you are done with the app, you will notice the screen on your phone is still on, but it will time out with whatever you have it set to, and turn back off as usual.

Hope this helps.

Hey, Sean.

Appreciate the effort to assist, but I've seen the 'trusted device' recommendation before.

My problem is that this (evidently) requires the remote device to be connected to phone via bluetooth.

My phone will be in other room, connected via wifi to same gateway as computer, so bluetooth won't work for me.

I think the REAL answer to be that:

MS recognize that some portion of their phone link user community are forced to revert to previous version app version & deny auto-update to approximate truly functional capability.

Then, to get FULL function, someone at MS connect with the Samsung guys, who seem to have buggered the service on (at least) their S22 line, then have them agree to modified service or client so that we get FULL function back (a la returning 'swipe to unlock' and stabilizing the messaging interface so that we don't get all these seemingly random 'cannot send' when responding to, or creating, message(s))

You need to turn off automatic updates on your phone. This problem is caused by the update from Google Store. My phone automatically downloaded update from Google Play and I could not unlock the phone again. I had to turn off auto updates, uninstall app and set it all up again. Phonelink update from Samsung Galaxy Store does not cause this problem.

When you uninstall it, it will revert to original version. You wont be able to completely remove it (although this is still possible to do with ADB). Then reconnect your phone and see if it works. Then update the app through Samsung store. It works for me. I did not try to install update from Google Store.

Thanks Sumit - I've submitted the issue. I'm just waiting for the feedback to show up and then I'll share it to Twitter.