Home > Tips and Tricks

Smart Lock not working after March update: How to Fix

In this guide, we will make you aware of a potential workaround that should help you rectify the Smart Lock not working issue after installing the March update. While having a lock screen password/pin/fingerprint is always recommended, however, in some cases, it might prove to be an annoyance if you are constantly locking/unlocking your device and are currently in a trusted/safe location. This is where the Smart Lock feature comes in handy.

smart lock not working

It beholds three handy functionalities- On Body Detection, Trusted Place, and Trusted devices. So if your device is currently with you [such as in your pocket], at your home, or close to your secondary device [such as your smartwatch], then in all these cases, you could instruct the OS not to lock your device. However, as of late, users have reported that the Smart Lock is not working on their devices as all these three features have suddenly gone missing.

smart lock not working

The issue first came to light right after users installed the March update and have been bugging the users ever since. Moreover, apart from the Pixel devices, many Samsung device owners are also reportedly facing the same issue, so it’s more widespread than initially anticipated, with that said, there does exist a nifty workaround that should help you rectify this issue. So without further ado, let’s check it out.

Fix Smart Lock not working after the March update

smart lock not working

In order to rectify this issue, all you need to do is simply disable and then re-enable Smart Lock from the Trust Agents section. Here’s how it could be done:

  1. Head over to Settings > Security and Privacy > More Security Settings
  2. Then go to Trusted Agents and disable the toggle next to Smart Lock.
  3. Now go to Smart Lock and all its features will be back, up and running. smart lock not working

That’s it. These were the steps to fix the issue of Smart Lock not working after installing the March update. As far as the official stance on this matter is concerned, the developers are yet to acknowledge this issue, let alone give out any ETA for the rollout of a fix. As and when any of these two things happen, we will update this guide accordingly. In the meantime, the aforementioned workarounds are your best bet.


Share: