Post reply

The message has the following error or errors that must be corrected before continuing:: Warning: this topic has not been posted in for at least 120 days.
Unless you're sure you want to reply, please consider starting a new topic.

Name
Email
Subject
Message icon

Other options

Return to this topic
Don't use smileys

Verification:

Please leave this box empty:

Shortcuts: ALT+S post or ALT+P preview

Topic summary

Posted by Craig Ward

- November 16, 2017, 02:31:58

Unfortunately, being more restrictive is one of the ways that they can combat the claims of Android's poor security in comparison to iOS.

I'd prefer if the approach was to separate the security update service in a way that allows Google to distribute security patches directly. It would need to be done in a way that didn't affect manufacturers customisations so as to not need their involvement. This way manufacturer involvement would only be needed for version updates (e.g. 7.0 to 7.1).

However, I imagine that this is very difficult (or near impossible?) to implement, which will be why they're going after the things they can change more immediately.

Posted by SeranAntares

- November 14, 2017, 23:43:31

So more restrictions? Feels like Google wants to have Android like Apple does with iOS (be quite restricted).

Posted by Redaktion

- November 14, 2017, 22:13:39

The next stage of Google's push to improve Android security is putting a spotlight on applications which misuse accessibility features to add functionality that wasn't expressely designed to improve use for people with disabilities. Some popular apps affected include LastPass, Cerberus, and Tasker.

https://www.notebookcheck.net/Google-s-new-security-policy-on-accessibility-features-will-limit-or-remove-hundreds-of-good-useful-apps.263722.0.html