Pushing a security update requires collaboration from the chipset designer, phone maker, and mobile network operator, at minimum. It remains to be seen how it pans out, but ultimately Fuscia could be the solution that we were never able to solve for android/linux.

I’ve long wished that google would use its muscle to rectify the situation somehow. The manufacturers consider planned obsolescence a “feature”, so they’re not too bothered and Linux devs don’t want to provide long term ABIs. It’s a another case of nothing getting fixed because we have different parties blaming each other while allowing android consumers to suffer the consequences. This comes down to the lack of ABI combined with the dependence on long term drivers.

It is extremely unfortunate that android has never managed to beat the hardware & OS compatibility issues. Solving either of these would effectively solve the problem. The app support problem faced by users is a consequence of both incompatibilities.

Google determines when to break OS & software compatibility, meanwhile it is the manufacturers who determine when to break hardware & OS compatibility. I think we need to distinguish between the notion of hardware & OS compatibility with OS & software compatibility especially since in the case of android it involves different parties. Then again, their OS was not up to modern standards. In a hindsight, Windows Phone supporting only a single chipset was the better decision. And sometimes those are no longer around (remember TI OMAP fiasco?). It is more like lack of foresight: it is Linux, all should be easy, right, … right?

Ti 84 emulator for iphone