You must log in or register to comment.
Android’s new in-call protections1 provide an additional layer of defense, preventing you from taking risky security actions during a call like:
- Sideloading an app for the first time from a web browser, messaging app or other source – which may not have been vetted for security and privacy by Google.
Because Play Store has a history of being a haven for only the most secure of apps… 🙄🙄🙄
In order to provide you with better security, Google is required to know everything about you at all times. The shareholders demand it…smh
I’m nearly 100% certain that absolutely none of these protections work on AOSP. Only if you consent to be spied on by Google, does this stuff work. Even the advanced data protection stuff which lets you automatically have your phone reboot and stuff like that is only available through the Google settings which would require a Google Android device and not AOSP. This is a nothing burger.
So I should not use aosp, because that is rather insecure?
You would know if you were using AOSP.
If you’re using AOSP, there’s a damn good chance that you understand security and what to be doing and what not to be doing.
If that is not you, then I would say no, you probably shouldn’t be using AOSP.
Making it difficult to use accessibility services was the things that made me decide I was done with Android phones.
That’s a really interesting set of protections: they’re targeting categories of scams and trying to prevent them.
I can see that causing a lot of problems for people walking relatives through legit tech support, but if it prevent vulnerable people from getting scammed, that may be worth it.
