News for hackers. Stuff that matters.
Re:Android Oreo by pjmlp on Monday August 21, 2017 @03:50PM (#15067268)
As I commented in another HN story, I don't believe OEMs and telecom operators will release updates, if Google doesn't force them to do so.

They already admitted on the ADB Podcast that they don't want to remove the ability for OEMs and mobile operators to customize their forks of Android.

We will still be forced to buy new devices even if they are VTS certified.

Re:Android Oreo by dcomp on Monday August 21, 2017 @04:12PM (#15067453)
> VTS certified

If it passed VTS it should be able to run AOSP. The new CTS will be an AOSP System image running their VTS passing "drivers".

Even if your vendor doesn't push any updates. At least you should be able to run a number of newer versions of AOSP as long as Android doesn't deprecate those VTS drivers.

Re:Android Oreo by bitmapbrother on Monday August 21, 2017 @05:11PM (#15067891)
Providing your bootloader can be unlocked, of course.
Re:Android Oreo by nicpottier on Monday August 21, 2017 @09:30PM (#15069077)
You've said this in a few different places, do you have a source for that? You are saying you could load AOSP on an S9 regardless of what Samsung does?

If so, this is indeed huge, but I have some serious doubts about it, perhaps because I have felt so very burned by Android so many times in this respect on anything but Nexus devices.

Re:Android Oreo by Natanael_L on Tuesday August 22, 2017 @04:17AM (#15070545)
Maybe - the bootloader must allow you to run that AOSP ROM, which only is possible if the bootloader isn't locked. Lots of OEM:s lock their bootloaders. But otherwise, yes, there's nothing else stopping you.
Re:Android Oreo by Mindwipe on Wednesday August 23, 2017 @05:12AM (#15079815)
There are a bunch of things potentially stopping you in practice. The HAL isn't a total wall, and I expect to see many OEMs go around it in some places, either due to incompetence, the HAL being inflexible, or timescales.

So even in situations where you can install such a ROM, there's very little guarantee key bits of hardware will operate properly. Any non-standard hardware/hardware feature is also fairly likely to break.

Re:Android Oreo by pjmlp on Monday August 21, 2017 @04:35PM (#15067642)
Usually common users don't flash their devices and that is what matters for the Android dashboard.
Re:Android Oreo by fulafel on Tuesday August 22, 2017 @12:13AM (#15069639)
How in practice would you go about putting AOSP on a device without the vendor cooperating? Is there some kind of secure boot system that always accepts AOSP images?
Re:Android Oreo by jiggunjer on Tuesday August 22, 2017 @07:20AM (#15071314)
I think the idea is that they cooperate once, and then Google promises to stop breaking the HAL interface for x years at the cost of increasing their development difficulty.
Re:Android Oreo by yjftsjthsd-h on Tuesday August 22, 2017 @07:37AM (#15071390)
You would still have to jump through hoops to boot a new ROM, but when you did it would actually work rather than having some drivers missing.
Re:Android Oreo by kevincox on Monday August 21, 2017 @04:12PM (#15067455)
The sad thing is that it shouldn't be on Google to force them. It should be Google to enable them and the users to "force" them.

They have argably been enabled for a while, but Treble is making it even easier. Hopefully this pushes the needle over the line for at least some OEMs/teclos.

Re:Android Oreo by pjmlp on Monday August 21, 2017 @04:36PM (#15067651)
In Germany there are quite a few stores still selling budget Android 4.4 and 5.1 devices, which people keep on buying.
Re:Android Oreo by mobilio on Monday August 21, 2017 @04:40PM (#15067688)
Same is in Bulgaria. And when you ask them "Hey actual version is 7.0. Why you use outdated OS with vulnerability? How you buy that devices?" They told "I have seen 7.0 there was nothing new."

But no one want to get computer with Windows 95 (or 98) anymore. Just Android 4.4 is "OK".

Re:Android Oreo by cosarara97 on Monday August 21, 2017 @07:55PM (#15068748)
There are no cheap windows 95 computers where everything works on the market. Android 4.4 does do everything people need (like running whatsapp), and the devices are out there to buy.

Security vulnerabilities? Nobody was ever affected by those (at least in the social circles of the people buying the devices), so why should they care?

Re:Android Oreo by dep_b on Tuesday August 22, 2017 @09:32AM (#15072172)
Tons of sites full of "amateur porn" think you shouldn't worry either. Who cares if all of your pictures are freely available to anyone on the planet, right?
Re:Android Oreo by jfim on Tuesday August 22, 2017 @01:54AM (#15070067)
> But no one want to get computer with Windows 95 (or 98) anymore. Just Android 4.4 is "OK".

They should do a yearly release (eg. Android 2018). Then at the store when they display phones, they'd have to write "Android 2013" instead of "Android 4.4 KitKat."

Re:Android Oreo by eicossa on Tuesday August 22, 2017 @03:23AM (#15070370)
Doing yearly releases is such an obviously great idea that there must be a big reason why they are NOT doing it.
Re:Android Oreo by Angostura on Monday August 21, 2017 @06:36PM (#15068339)
In the UK last year, I bought a Samsung android tablet for the kid (my first Android device). It was running 4 and I ass7med Samsung would have an upgrade available. Ha! No chance.
Re:Android Oreo by hesarenu on Tuesday August 22, 2017 @01:13AM (#15069886)
You can get a Nougat device for as low as Rs 3500($55) in India. Which would be considered low end mobile.
Re:Android Oreo by cakedoggie on Monday August 21, 2017 @07:49PM (#15068721)
It seems people have made their choice they don't care. If they cared about updates they wouldn't be buying Android.
Re:Android Oreo by remir on Monday August 21, 2017 @09:56PM (#15069175)
You're thinking like a technical person. Aunt Susan doesn't know her phone is an Android phone. In her mind, it's a Samsung phone. It's not a question of not caring, she simply doesn't know.
Re:Android Oreo by fauigerzigerk on Tuesday August 22, 2017 @06:46AM (#15071137)
There is such a thing as not knowing because you don't care, and I wouldn't even say that it's irrational. There's simply too much to know and care about in the world, so you have to be selective and event driven.
Re:Android Oreo by pjmlp on Tuesday August 22, 2017 @01:59AM (#15070093)
Some of them do care, but with an average salary of 500 euros or less, they have better things to do with the money than spending on iPhones.

The only viable alternative was Windows Phone, but that is gone now.

Re:Android Oreo by fauigerzigerk on Tuesday August 22, 2017 @06:37AM (#15071104)
That is very true, and I have to say it's disappointing and baffling how Microsoft dropped the ball on this one.

Microsoft are the only ones who ever managed to make the separation between OS vendor and hardware vendors work (at least on the PC side). They are sorely missed in the mobile space.

Re:Android Oreo by flukus on Monday August 21, 2017 @09:38PM (#15069113)
They didn't choose, they just didn't know.

This is why software/hardware needs best before dates.

Re:Android Oreo by ClassyJacket on Monday August 21, 2017 @08:00PM (#15068768)
I agree. There are two parts to the Android update problem. I'd wager OEMs having no motivation to release updates is bigger than them having no ability.
Re:Android Oreo by BinaryIdiot on Monday August 21, 2017 @04:06PM (#15067405)
I completely agree. It's good they broke it apart to make updates, in theory, easier but after working for a company that modified software that was delivered to them and then reshipped elsewhere it really never mattered how module the original was; the updates still go through the same channels, testing, etc and the OEMs will likely want to modify things not as cleanly separated (an API design never passes its production usage without warts).

I doubt we'll see much change. I hope it'll make it slightly faster but without an agreement with OEMs that has teeth forcing them to be more expedient I can't see this getting much better.