Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Well, not for long - it looks like they have a fix: http://code.google.com/p/android/issues/detail?id=9392#c1460


Isn't the situation such that this fix will take a long time to reach some of the users? Sometimes as long as "never"?


Well with a bit of luck it won't be 2.3 only, so yeah but not as likely. And I'm guessing carriers are getting bitched at as well, so they're probably looking into getting this one fixed soon-ish on the phones they "manage".


Maybe the fallout will be a valuable lesson to carriers.

They've (in some cases) loaded phones up with crap, and in so doing made maintenance difficult. Any patch will have to go through their crapification process, and re-testing, leading to customer dissatisfaction.

Depending on how much dissatisfaction the bug causes, and the degree to which people clamor for Android phones anyway, carriers might decide to change their attitudes toward crapware.


There's no reason Google can't through a fixed Mms.apk on the Market and have it on old devices as well.


How does one view the code change associated with this fix?




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: