3 ms·
Kernel ABI is not the dominant part of the problem. The stagefright debacle didn't have anything to do with the kernel or Linux ABIs. libstagefight is Android'
by fulafel 10y ago
Kernel ABI is not the dominant part of the problem.
The stagefright debacle didn't have anything to do with the kernel or Linux ABIs. libstagefight is Android's own userspace library.
Quadrooter was kind of related to ABIs in that it was inside Qualcomm's driver, but it would still have been trivial for vendors to just pop in a patched driver from Qualcomm and release a software update. They do all have systems ready for making software updates, since phones ~always get OTAs early in their lifetimes. A stable kernel ABI (so all vendors could have samed the same binary of the fixed driver) would not have made this significantly easier.
The main problem is lack of product liability cases due to lack of high profile really bad things happening (malicious worm epidemic etc). If consumers demanded (and won) their money back from phone vendors due to security incidents, diligence wrt updates would get written into contracts between operators, phone vendors, SoC providers etc and it would work.