Android: how to better take care of users

Question

Android: how to better take care of users

kristate opened this issue 7 years ago · 10 comments

I foresee that Android is going to be a huge problem, mainly due to the severity of the issue and also the continued lack of support for devices from OEMs. We are already seeing some poor choices such as Tesco deciding not to patch Hudl.

I am going to start an Android specific page of information regarding each of the devices.

What is the latest from team Android?

Thanks again to everyone for their support!

Answer 1 · 2017-10-18T15:21:44.000Z

Added Android page here: ANDROID.md

Answer 2 · 2017-10-18T15:34:13.000Z

Cool.
Google said they are working on a security update and getting it to major vendors.

source: CNET

Answer 3 · 2017-10-18T15:59:49.000Z

Just committed a super update for Android -- but the database seems to be too big for Github to view in one page, so perhaps it might be wise to split it up alphabetically...

Answer 4 · 2017-10-18T16:25:59.000Z

Yep, much better. The H section is pretty long.

Answer 5 · 2017-10-18T16:34:55.000Z

@kristate
Missing:
| Philips | Screeneo Smart LED Projector | HDP1690/F7 |
Product page

Answer 6 · 2017-10-18T16:38:55.000Z

@zeadope It's 1:38am here in Japan -- if you can give me a PR I will merge it.

Need to get some rest :)

Thanks!

Answer 7 · 2017-10-26T06:38:47.000Z

I have not found confirmation anywhere that Android below 6.0 is not affected by the vulnerability.

Can anyone confirm?

Answer 8 · 2017-10-26T07:30:52.000Z

IMHO Android below 6.0 is affected but it's not likely it will get any update.

Answer 9 · 2017-10-26T09:21:09.000Z

Why would Android 6 not be affected?

Answer 10 · 2017-10-26T09:38:41.000Z

The Android picture is also complicated by the many custom ROMs. I've been out of the XDA rat race for awhile now, but each of those will need patching. At first I dismissed them figuring the more-technical userbase probably knows they need it, but we do list non-commercial things like DD-WRT, so I figured I'd throw it out there.

Another twist is that (in the US at least) carriers rather than manufacturers are often responsible for patching devices. I realize carrier-specifics are represented here as different models, but for ease-of-consumption it might be helpful to add a carrier column. (Further complicating this are the contract-only budget carriers who piggyback on someone else's network...)

The scope of this problem is pretty staggering.