December 31, 2010. Most people were trying to figure out how to celebrate New Years Eve, a few fireworks, a little drinking, maybe a kiss, but a few well known bloggers were more concerned about one thing: Issue 9392 on the Google Code Android project page. The issue has been going on now for about six months, first reported by a Nexus One user on June 28:
Device: Nexus One. One day old. Updated to 2.2 FRF50 Default Android Messaging Application. No apps installed. Messaging. - Send SMS message to RecipientA. - Message appears to be successfully sent to RecipientA. - RecipientX receives message. - 'View Message Details' in RecipientA thread, shows 'To' field as being RecipientX's MSISDN (phone number). Has occurred multiple times on this device now. Interestingly, has never occured on my other Nexus running the same FRF50 build.
Issue 9392 has had 1200 comments in the last six months, many from the last few days since the story first made its rounds on December 31, but has always carried a “Priority-Medium” status. Users commenting they are ready to drop Android if SMS does not work properly, or some wondering if, as of January 1st, the status has now been moved to “Priority-Critical” as seen by the tweet above from @Justin_C_Ellis. Head over to the issue page on Google Code and check it out for yourself, all it took was one blogger in the wee hours of the morning and two others reiterating his story to rally a war cry in the community, “Hey, Google! FIX IT!!!!”
According to the public poll on the Hardware 2.0 blog, only about 26% of people who responded have experienced the issue. I have not experienced it myself, that I am aware of (knock on wood), but I do hope now that the status has changed to critical, it will be taken a little more seriously. I first came across this issue when a friend brought it up on their Motorola Droid and a quick Google Search pulled up a few hits. I was surprised to learn on Friday while catching up on some tech news that it is still an issue. If there is one thing we can take away from all of this, it’s that Google does listen to the community, and if enough people report having the issue, its status may get moved up the chain. There is still no official word from Google, but you can bet the community will stay on top of this.
Have you experienced this issue or does it make you afraid to text outside of Google Voice? Sound off in the comments below and let us know!
Sourece: ZDNET, BGR, EngadgetMobile
