While I agree with you, the first step for user centric Android flavors regarding security is to support relocking the bootloader, with a custom (preferably the user’s own) digital signature. As long as we dont have that, an attacker could flash or just boot a custom bootloader through fastboot that does its own thing.
However that doesn’t really depend on Android system developers, I think, as the problem arises from the inferiority of almost every phone’s bootloader (chain) (because most phones does not support setting up a custom signature for bootloader verification), and probably that can only be reasonably solved by device manufacturers, because as I understand, bootloaders do a lot of heavily device specific things, so there cant really be a common (primary) bootloader, and making one for each phone is a lot of work that also involves lots of reverse engineering, and maybe the early bootloaders cant even be overwritten on some phones…
Lol, who wants these anyways. One more reason not to use google play services. (Though I have google play services on this phone.)
Automatic AI-powered screen lock for when your phone is snatched.
Theft Detection Lock is a powerful new feature that uses Google AI to sense if someone snatches your phone from your hand and tries to run, bike or drive away. If a common motion associated with theft is detected, your phone screen quickly locks – which helps keep thieves from easily accessing your data.
Theft Detection Lock is a powerful new feature that uses Google AI to sense if someone snatches your phone from your hand and tries to run, bike or drive away. If a common motion associated with theft is detected, your phone screen quickly locks – which helps keep thieves from easily accessing your data.
Why would we need AI for that? That just makes the function unpredictable. There must be a real solution to detecting this.
Not just marketing, that’s the term it’s always been called. Plug a bunch of parameters into a non-deterministic model and you’ve got an AI, at least by what seems to be the common definition of the term.
“AI” used to mean “whatever we don’t fully understand yet”. A lot of processes have walked the path from “fantasy” to “AI” to “algorithm”. Doesn’t need to be non-deterministic, the original tic-tac-toe playing software was “AI” at the time.
Until we get some AGI, the term “AI” will remain a moving technological target, and a static marketing target.
It isn’t clear which of these features use Google servers and which ones don’t. The “Find My Device” definitely does, and has no place in AOSP. If they’re actually using AI to compare phone state with some tracked “habitual” behavior, it may also have no place in AOSP, but who knows.
Many of these are Google Play Services features, so it won’t be available to users open-source Android flavors that are google-free.
Which is a fraction of a fraction of Android users.
I’m all for de Googling if that’s what tickles your fancy, but ask anyone on the street and they’ll have no idea what you’re talking about
Edit: This also allows Google to push some of these features to older devices which may not ever see another system update
In that blog post, google does not commit to open sourcing these play services features, to integrate in future system upgrade.
I would love to be proven wrong.
Yep, no one claimed otherwise.
While I agree with you, the first step for user centric Android flavors regarding security is to support relocking the bootloader, with a custom (preferably the user’s own) digital signature. As long as we dont have that, an attacker could flash or just boot a custom bootloader through fastboot that does its own thing.
However that doesn’t really depend on Android system developers, I think, as the problem arises from the inferiority of almost every phone’s bootloader (chain) (because most phones does not support setting up a custom signature for bootloader verification), and probably that can only be reasonably solved by device manufacturers, because as I understand, bootloaders do a lot of heavily device specific things, so there cant really be a common (primary) bootloader, and making one for each phone is a lot of work that also involves lots of reverse engineering, and maybe the early bootloaders cant even be overwritten on some phones…
It’s kind of both Google’s and manufacturers responsibility. Google has made available a Dynamic System Updates feature:
https://source.android.com/docs/core/ota/dynamic-system-updates
https://developer.android.com/topic/dsu
…but it requires manufacturer support to allow adding custom keys.
Hmm, this is interesting, it looks like if it was a multiboot solution
Lol, who wants these anyways. One more reason not to use google play services. (Though I have google play services on this phone.)
One good thing you could try is use this app:
Find My Device
Why would we need AI for that? That just makes the function unpredictable. There must be a real solution to detecting this.
The real solution is, a heuristic analysis of the phone’s gyroscope and accelerometer data.
Marketing calls that, “AI”.
Not just marketing, that’s the term it’s always been called. Plug a bunch of parameters into a non-deterministic model and you’ve got an AI, at least by what seems to be the common definition of the term.
“AI” used to mean “whatever we don’t fully understand yet”. A lot of processes have walked the path from “fantasy” to “AI” to “algorithm”. Doesn’t need to be non-deterministic, the original tic-tac-toe playing software was “AI” at the time.
Until we get some AGI, the term “AI” will remain a moving technological target, and a static marketing target.
“Common motion associated with theft” – so how long until this starts locking legit users out of their own devices?
That’s my concern too. They should have baked those into AOSP making it available for all ROMS.
It isn’t clear which of these features use Google servers and which ones don’t. The “Find My Device” definitely does, and has no place in AOSP. If they’re actually using AI to compare phone state with some tracked “habitual” behavior, it may also have no place in AOSP, but who knows.