05
Jan
android-logo

About a week ago, Engadget ran an article covering two bugs in Android's Messaging app:

  • The first involves an issue where users are directed to a different thread than the one they selected from the notifications bar or the main screen of the SMS app
  • The second occurs when users are directed to the right thread but end up having their messages sent to a different person than the one involved in the thread

Shortly after, Google changed the bug's priority from "medium" to "critical" on the bugs Google Code page to show that the company cares.

Now, an official Google rep has reached out to perturbed users on the Google Code forums:

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.

Excellent - here's hoping that Google will manages to push a fix out shortly.

Source: Google Code via BGR

Jaroslav Stekl
Jaroslav Stekl is a tech enthusiast whose favorite gadgets almost always happen to be the latest Android devices. When he's not writing for Android Police, he's probably hiking, camping, or canoeing. He is also an aspiring coffee aficionado and an avid moviegoer.

  • johnny99

    How are they going to release this bug fix? As part of Android 2.4? I'm having doubts that my Droid will ever see Android 2.3.

  • erik

    Your right, the droid will never see an official 2.3 ota.

  • tony

    I'm just waiting for 2.3 for my g2

  • bruce77064

    So that is what happened a few nights ago when I sent my boss the following message, "I love you Baby" lol I hope they fix this soon. Can you say "awkward?" lmao. I had some fast explaining to do, his wife was right next to him when he received the message, he didn't have my name programmed in his contacts.

  • Deon

    Didn't know about this bug. But I to wonder how they're going to release this bug fix, in the next complete release of Android, or will it be some kind of update pushed by the market (would be the best/easiest way to do it). If they push it to the carriers it'll take the carriers forever to push it to our phones. This needs to be deployed asap. Maybe if they publish the changelog or what they did, Cyanogen and his team can update CM 6.x and/or CM 7 to include this fix.

  • OFI

    How about fixing the damn bug that puts txt replies in the wrong order if you reply too quickly :-/

  • http://robert.aitchison.org Robert Aitchison

    When the OG Droid was released, it did have 2.0, but 2.0 was Eclair, not Donut:

    1.5 Cupcake
    1.6 Donut
    2.0 & 2.1 Eclair
    2.2 "FroYo" (always hated that name)
    2.3 Gingerbread

    There are also rumors that 2.4 will keep the Gingerbread name.

  • clear

    What about the issue of people losing ALL their text messages?

  • Angry Fran

    or the one where the timestamp says "sent at 930" and you get it on your phone at 10.
    idiots. nokia managed to have sms's working for 15 years, learn a lesson kids.
    it's not a network problem, the forums are abuzz with the issue. SIGH. bit challenging to make a competitive phone is it?

  • Mike

    This happens quite often on my Thunderbolt...both issues.

    I'll select a thread on th etop of my list and some random one near the bottom will populate the screen.

    AND I will be in a thread texting back and forth, then inexlicably when I hit send to a message it will back out of that thread and send it to someone else randomly in my thread list...

    NOT GOOD!!!!!!!!

  • Chuck

    I have found texts being sent to people other than the thread you have replied on happens when an incoming message hits precisely when you hit "send". The message gets sent to the person on the bottom of your text list at the time. Happens exactly this way every time.

    The opening of a thread other than the one selected happens one of the following happens. 1) You receive a text precisely the same time you "tap" the intended thread to open it. 2) You send a text, return to list and open another unread before the previous text has finished sending.

    I can make this happen every time - although the timing of incoming can't be predicted EXACTLY as you "tap" another message. This is the only problem I foresee but I'm sure the pro's can make it happen.

  • john

    Sms bug still alive. HTC desire, froyo. Two conversation threads open, A, B.. Reply to A went to B, but showed as sent to A. Only when message details checked does it show that tx went to wrong contact. Very dangerous!!! Total deal breaker for android. 23/8/11

Quantcast