Hooray! Since yesterday when the entire internet (or at least a few hundred – thousand – million people who’re on Android) rallied behind making the Android SMS Bug a thing of the past by dropping a gigantic amount of clicks on the 9392 SMS BUG thread in the Google Android code complaint department. In the time between then and now, the thread went from medium priority up to CRITICAL! This is totally rockin since this problem has been on the books since way back in June, 2010.
This doesn’t mean that the problem will be fixed instantly, of course, but it certainly puts it higher on the list of “to-do” items for the Android fixers at Google. Just to make sure it stays up there at the top, keep on clicking!
All you’ve got to do is log into your Google account and head over to the 9392 SMS BUG thread, go down to the bottom, and hit the “Vote for this issue and get email change notifications” button. Let’s get it fixed!
Eric Schmidt said, ‘Andy (Rubin), tell your guys to set that SMS thing to ‘Critical’; that’ll shut ’em up.’ and then laughed and laughed and laughed.
Someone over at Android guys made a good point about this. Currently there are just over 4,000 users staring/ following the problem report on the Google code page. That number is just over one percent of the daily activations of Google devices. And the number of actual reports of the problem occurring is less than half that. Maybe the reason this has not been a critical matter until now, is simply because Google cannot recreate the issue. Honestly I have sent text messages to the wrong person many times, and didn’t realize it till much later. True to human nature we never want to believe we are the flaw in the system. It seems to me that most of these occurrences are probably user error, sure there is probably a few that are interface issues with other apps (or god forbid, the carriers, lol). Google has gotten a lot right with Android, it just seems to me this would something they would have caught before now. True Android uses and fans out there, don’t go flood Google with reports of this happening just because you’re worried about it happening to you. If it happens then report it. Personally in a year of owning the Nexus one it never happened to me, so think before you jump on the media band wagon.
Kyle K.
Sent From My Google Nexus One
Starting from the result obtained by this post, I would like to publicize another big bug that google seems to ignore. Is the lack of the support for proxy (also authenticated) on the wifi. Is a huge lack for the use of an Android smartphone in a working environment. Please vote this bug: http://code.google.com/p/android/issues/detail?id=1273
Marco,
Support for proxy is available if your able/ willing to root or at least change some aspects of the OS. I’m running an English translation of MIUI and there is WIFI proxy support. Best place to search for support on this would be the XDA forums.
Yes Kyle, I already knew. But in order to spread the use of the OS also in the “professional world”, I don’t think that rooting the OS can be taken into account as a valid option.
While you’re campaigning for users to star various bugs you might point out to them:
1. By all means hit the star, but we don’t need 1000 posts in 24 hours saying “this is important” that do nothing but obscure the 5 posts in the conversation that actually contain useful information.
2. Users ought to be grateful that they are even allowed to see Android bug reports let alone comment on them. This is a great thing about the open-source processes. Most phone vendors have just as many bugs for their operating systems, but you’d never know since they don’t let the whole world look at them. When open-source becomes a source of competitive disadvantage because of bad press the solution will be to stop publicizing bug reports, which is bad for everybody.
3. You might want to educate your reader on USEFUL things they can post – like REPRODUCIBLE scenarios. Step 1, open a text window, step two, click on this, and so on. Something that makes the bug happen EVERY time. When given something like this a developer can usually fix almost any problem. “This is important” and “this seems to happen when I’m drunk sending 3000 texts in 15 minutes” doesn’t really help them much.
As reporters you are part of the community as well. By all means be critical – that’s your job. However, if you’re going to rally crowds of people to do something maybe you can get them to do something besides just whine. That’s what open-source is all about. Sure, not everybody understands Java, and that is fine. However, that doesn’t mean they can’t contribute.
Surely the random sending of an SMS to the wrong recipient is far less of a problem than the much more serious one of not receiving an SMS at all as a result of another long term bug that tells your carrier you have received the message but fails to store and you have no idea that you were ever sent it.
For more info see: http://code.google.com/p/android/issues/detail?id=4991
Android has many bugs regarding SMS. There’s almost two years old bug regarding, that Android doesn’t read delivery notifications right.
More info: http://code.google.com/p/android/issues/detail?id=2305
The saddest part is that fix was commited short after bug report, but google wouldn’t even care to merge it into mainstream…
“As reporters you are part of the community as well. By all means be critical – that’s your job. However, if you’re going to rally crowds of people to do something maybe you can get them to do something besides just whine. That’s what open-source is all about. Sure, not everybody understands Java, and that is fine. However, that doesn’t mean they can’t contribute.”
Well played, Richo, well played.
Google Should have never let this get out of hand. If it wants to be supirior to apples OS. instead of moving on to a new version .how About fixing the current one
Just because it gets fixed in the AOSP code doesn’t mean every Android device will get the fix. =)
Just install Handcent and move on…