Oh my goodness. As you might already know, we’ve been keeping our eyes on the developing story surrounding the SMS bug that’s been bugging people for several months now. It’s been coming to a bit of a head very recently, as evidenced in this Rally post, this Critical update, and this possibly fix. Now there’s an official response from Google on the issue. It contains such epic passages as “two distinct situations” and of course, everyone’s favorite: “we have fixes for both of them.”
Even though this response basically says that they’re saying to users just stop being so stupid and be patient, we’re still working on it, it is encouraging to hear any response at all. Google is notorious for working WITH people rather than IN SPITE of them, so hold your hands up high and rejoice because the end is near! Read the whole response here:
Thanks to everyone for your patience while we’ve been investigating these reports. As it turns out, we believe there are two distinct situations being discussed on this issue chain. Fortunately, we have fixes for both of them.
When some users tap to open a message in the Messaging application, they’re seeing a different message appear instead. We don’t believe this issue is affecting many users, but we’ve developed a fix that we’re preparing to deploy. Of course, double-checking the displayed message before hitting “Send” will prevent any messages from being sent to the wrong recipients. We’ve found in testing this issue, it is more likely to occur if you tap on a message before the Messaging app is fully loaded, so we recommend waiting for all the elements to load before clicking on the message you want to display.
Separately, some users have reported that their SMS messages are being delivered to the wrong people. It took us some time to reproduce this issue, as it appears that it’s only occurring very rarely. Even so, we’ve now managed to both reproduce it and develop a fix that we will deploy.
While we don’t anticipate any persistent problems, we’ll continue to investigate in case we come up with additional ways to trigger these bugs. Thanks again for helping us improve Android.
[Via Android Issue 9392]
How do I get them to resolve the duplicate issue ?
Sign in to your Google account and check out that link – if your issue isn’t resolved by the measures written about here, you might wanna start a whole new issue thread.
Also, this is a message for everyone: feel free to ask any and all questions about your devices in the Android Community Forums http://androidcommunity.com/forums/ lots of people to hang out with and chat and figure stuff out with there!
Hope google will solve this issue soon.
Is it true that when a Operating System adds “safeguards” it’s a layer of code that slows down device response time? Sure seems to work that way in every day life.. like the enhanced “safeguards” at airports.