If you're trying to call 911, or you're trying to video an assault... and someone tries to stop you, such as by jostling you or your phone... what's the likelihood that this Private Lock will get in the way of that?

Especially location data. If something like Find My Phone is activated, my immediate bias is to assume Google is taking advantage of this data collection to monitize my data without my consent.

Even on graphene OS, location without GMS is almost unusable.

How much data could it have to look at in the time that someone "snatches" a phone?

> If a common motion associated with theft is detected, your phone screen quickly locks – which helps keep thieves from easily accessing your data.

So it's probably a machine learning model that was trained on motion data of snatches, but it's likely not AI in the sense of LLMs.

But I wonder how many false positives this could yield. For example you are in a hurry and you snatch your phone from a table. How precicesly can this model decide with just motion data, if this was theft or not.

If I snatch a phone from the table (probably already locked?) or drop it, I will suck up the additional login.

I have long thought about the utility of a little locking-beacon. If phone suddenly gets out of range, should auto lock. If only Bluetooth were not so unreliable.

These are two different things, since I do not want my phone to have no lock screen just because my headphones are sitting near it, but if it is unlocked and suddenly my headphones disappear, that would be a useful precaution, even if it doesn't eliminate the risk on its own.

I remember that I used the last option many years ago, as that was really convenient and worked very well. Basically as long as the phone was in your hand or pocket it kept unlocked, but as soon as you laid it on a table it got locked.

But now that fingerprint unlock is a thing, I don't even mind unlocking my phone as it is one fluid motion and happens unconsciously.

There's a saying that when something becomes mainstream it is no longer considered AI. Fun to see that being reversed.

Good heuristics. Also that must not be a mainly downward rapid movement, which probably only means you just dropped your phone.

I mean, most people dropping their phone will be too glad/devastated that the device did/didn't escape harm to bother being annoyed that they have to unlock the screen again.

- Private Lock (source): https://github.com/wesaphzt/privatelock

- Private Lock (F-Droid): https://f-droid.org/en/packages/com.wesaphzt.privatelock/

Gotta admit first thing I would do is stage a theft scenario to see how it works.

I never spend more than 200 euros on a phone and consider them disposable. If I lost my (locked) phone, I'd merely get my (identical) backup phone from home and continue as if nothing happened.

The other downside is false positives or other occasional failure modes. Many such "auto-magic" features choose not to expose any granularity to the user, perhaps because they think it'll make it less "magic" or that a few entirely optional scaling settings in an "advanced" tab will hopelessly confuse users. Too often such "all or nothing" reliance on the infallibility of their magic 'do-the-right-thing' code forces me to entirely turn off what would otherwise have been a useful feature.

For example, we have the greatest opportunity in a generation for someone to build "photoshop for text" i.e. a proper GenAI based LLM tool with similar design choices. LMstudio is the only even close example of this, and they're not getting it in the way that blender does.

For me its car's lane assistant, interfering with driving is big no for me. Asked my father to turn it off on their new mazda 3 too, 99% ok behavior is simply too low, even 99.9% would be.

Otherwise, in city driving, it's like some paranoid front seat passenger grabs the wheel every 30 seconds.

Of course, I always turn these stupid features off but, inexplicably, my wife likes them and keeps turning them back on. So when I happen to drive that car it continues to be a nasty surprise until I remember to turn it off. This also makes a separate UX failure even worse. Settings like seat position, enter/exit behavior, navigation and even entertainment options are stored and recalled in per-driver settings. These per driver settings can also be linked to each key fob. She has her fob and I have mine. Very nice - except these damn driver "assist" features are NOT stored in per-driver settings like they obviously should be!

Damn it, car UX designers - all user options should be stored per driver. It's a few KB for bit flags and single-byte values, it's not like we don't have the storage these days.