Hacker News Reader

Comment by DiabloD3 | Hacker News Reader

It has been quoted by Google developers on why Nexus 5 fell off the support track so early, around the same time Nexus 4 did: it took a herculean effort to get the binary drivers to even remotely work right on Android 6 due to being unable to drag in newer kernels.

This is partially why Treble is being worked on, to just completely disconnect the actual Linux-based HAL from "the OS", thus trying to negate a lot of the oblate stupidity from vendors like Qualcomm and have a shim in-between your actual phone, and Android itself, in hopes to fix stuff.

We seriously need more phone SoC vendors.

View on HN

That is just an excuse from Google that many blindly accept.

First, of all there are legal obligations known as contracts. If Google was serious about Nexus 5 support from OEMs, it would have had contract in place that would assure the necessary support regardless of what OEMs would decide.

Secondly, Treble is yet another solution that will die, because Google, again, decided to leave to OEMs the task of delivering Treble updates, without any kind of legal obligation.

Additionally Android devices that get upgraded to Oreo aren't obliged to be fully Treble compliant, only the ones released with Oreo.

So, many new devices planned to be released in 2018, are based on Android 7.0.

> First, of all there are legal obligations known as contracts.

That kind if snark is unnecessary and degrades the conversation.

> If Google was serious about Nexus 5 support from OEMs, it would have had contract in place that would assure the necessary support regardless of what OEMs would decide.

I'm not sure who you are referring to with "OEM" here, but Google took on the responsibility of maintaining the OS images for the Nexus devices, not the companies they contracted to build them.

> That kind if snark is unnecessary and degrades the conversation.

May be, but apparently discussions about Android's and OEMs usually leads to hand waving regarding the legal options available to Google, if they really cared about enforcing updates.

> I'm not sure who you are referring to with "OEM" here, but Google took on the responsibility of maintaining the OS images for the Nexus devices, not the companies they contracted to build them.

Like the customers they have abandoned after TI cut down support on their chipsets?

Had Google taken the legal requirements to enforce TI to maintain support or face monetary sanctions for the three years it was supposed to take place, this would not have happened as it did.

It always circles down to how much Google cares.

LineageOS (ex-CyanogenMod)'s flavour of Android 7 works just fine [1] on Nexus 5.

On the other hand - yes, hammerhead is stuck on Linux kernel 3.4, which is no longer maintained, and current best effort to forward-port to mainline kernel [2] is far from complete.

Among other things this means that there is no workaround for Meltdown on this hardware, which it is likely vulnerable to. [3]

[1] https://download.lineageos.org/hammerhead

[2] https://wiki.postmarketos.org/wiki/Google_Nexus_5_(lg-hammer...

[3] "11 stage integer pipeline with 3-way decode and 4-way out-of-order speculative issue superscalar execution" - from https://en.wikipedia.org/wiki/Krait_(CPU)

How am I running Oreo on my Nexus 5 with lineage os?

Reply on news.ycombinator.com