## An observation about the new Chrome OS Smart-Lock and Instant Tethering features.

I own a Samsung Galaxy S9 smart-phone, and an Asus Flip C213 Chromebook. And, two relatively new features which Google rolled out are:

• Smart-Lock: The ability to unlock the Chromebook, using the presence of the phone, and
• Instant Tethering: It has always been possible to activate the Mobile Hot-Spot feature of the phone, assuming that a user has a plan that includes tethering, and then to connect the Chromebook (or other device) to it, in the form of a mobile, Wi-Fi Access Point. But, with Instant Tethering, the availability of the phone as a tether is supposed to be more quickly visible from the Chromebook, and theoretically, accessible with a single click.

What some people have reported is, that this feature does not always work 100%, even though the procedure was followed, which my readers can find in many other places on the Web, to set up the feature. I recently experienced as well that, on my first try, these two features were not working at all, when the Chrome OS version on my Chromebook was ’80.x’. Yet, even during the interval of my trials, an update to the Chrome OS version had presented itself, to version ’81.y’. And since the update, the features seem to work 50% of the time.

There was an additional step which can be taken, but should not be 100% necessary in this case, and which I took, which is outlined in this article:

https://www.howtogeek.com/fyi/chrome-os-instant-tethering-comes-to-more-android-phones-heres-how-to-do-it/

I will explain below, Why I changed the flag under:

chrome://flags/#instant-tethering

From ‘Default’, to ‘Enabled’. A reboot was required…

One reason these features may still not work 100% for me, could be the possibility of the phone going into ‘Deep Sleep’…

(Updated 12/08/2020, 10h30… )

## Smart Unlock Getting Smarter

In This Posting, I had reported to the readers, that Google Smart Lock was working for me, except for the fact that I had made a silly usage error. Well there is a component to Smart Lock, which updates itself from Google Play, and which states the Security Policy in greater detail, than the programming itself, that may not get any update until the user upgrades to a higher version of Android.

In fact, I would not rule out the possibility that this Security Policy could be personalized whenever it updates, which could lead some users to anxiety. In reality, if there is a policy update that prevents our device from just unlocking, this should be nothing to get anxious about.

It was never a part of the system, that if a Trust Condition is met – even fully – our phone is guaranteed to unlock by itself. Sometimes, even though the condition is met, mine does not unlock, once or twice. And when that happens, this has its reason for being, and may just be because Google thinks I need the extra protection.

After all, incorrectly unlocking once, can be much more devastating that incorrectly not unlocking, because in the latter case, the regular measures to unlock the phone still work. I am assuming the same holds true for the reader.

But just recently I noticed that my phone was not unlocking anymore when I was at home. It had done so before but then just stopped. There are a number of reasons why this can happen. For example, Google might replace our own definition of our home address – which looks like just a random address on their servers – with our official address. And then one thing which can go wrong, is that our official address might not be positioned exactly, where our GPS etc. places us. My phone often thinks it is located just outside my window, on the opposite side of my building, from where the street address is located…

Yet, there are certain errors which will not just go away, until they are specifically corrected by a human being. And so I went after this recent issue.

(Edit 07/13/2016 : ) I had tried to solve this problem, by accessing the fact that my phone is synced with two GMail identities, but that only one of them had a Home Address set. I set the Home Address of my second GMail, to be the same as the first.

What resulted, was that the automatic unlocking started to work again – for one day. Then, it stopped working again.

I can only interpret this in one way. Apparently, Google servers determine that my Home Address, an apartment building, is not secure. There could be other people who look – according to the GPS – as though in the same place as me, but may not be. Google took a full day to determine this a second time, for the second entry.

This strikes me as good software.

Dirk

## Google Smart Lock Working Properly After All

One of the features which Android offers, is called “Smart Lock”. It means that as soon as some trust condition is met – in my case, as long as I am at home – I can bypass the default unlock method, and just swipe to unlock my phone.

But there was a time, when I thought this feature was not working properly. This idea was due to a simple user error on my part.

When Android shows us its swipe-to-unlock screen, it has animated ripples of water seemingly flowing along it, and in the case of my phone, displays 3 small icons along the bottom. Two of those are features which I can generally use without unlocking the phone, while the one in the middle is just a ‘lock-icon’.

What I did not know until recently, was the fact that it is a mistake, if we try to drag that lock-icon in the middle away from itself, to unlock the phone. That exact motion is acknowledged by a growing, light semicircle which appears around the lock-icon, and acts to lock the phone.

In order to unlock this screen, we need to start at a random position – such as where the animated ripples show – and just swipe straight upward.

I guess that it was silly of me, not to know how to work the standard swipe-to-unlock screen of Android. But if I am going to make mistakes, those will be stupid ones. I think that any phone thief, would already know how this screen works…

And my Smart Lock feature was always ready and willing to work with me, even though I had actually disabled it at one point in time.

Dirk