3 ms·
If I'm reading this right, this means that the fix for the problem in 2.2 was supposed to come in 2.3, but maybe will now come in 2.4. Except that, going with
by Lewisham 16y ago
If I'm reading this right, this means that the fix for the problem in 2.2 was supposed to come in 2.3, but maybe will now come in 2.4.
Except that, going with how Android upgrades have gone so far, most users on 2.2 will never see 2.3. Why is Google not pushing security updates free from carrier/manufacturer control? This is pretty terrible.
- bryanlarsen 16y agoMy interpretation is that there is a partial but insufficient fix in 2.3.
- mdwrigh2 16y agoI believe they're attempting to do this by separating some of the apps from the Android framework so that they can update them independently. Unfortunately, since Android is just so different from device to device, it'd be incredibly difficult to make a single change that can be given to all devices. And there was a partial fix for this in 2.3 as the other poster has correctly noted, and Google believed they had fixed it, but it turns out that it is still exploitable.