jun 28, 2010:
device: nexus one. one day old. updated to 2.2 frf50
default android messaging application.
no apps installed.
- 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.
jul 09, 2010:
this just occurred again on frf91. suck.
sms was sent to recipient who there had been no contact with and no threads in messaging.
sep 13, 2010:
this issue is way more widespread than what is respresented here, please review the comments at this page, where users are very detailed in reporting the issues they are experiencing.
my personal experiences:
text being sent to unintended recipient, when responding to an existing conversation(text). unintended recipient is not someone i have ever sent a text to previously. the 2 contacts in question do not have any similarities in the digits of their numbers, other than the area code.
i have 763 messages in my inbox, 782 in the outbox
galaxy s 2.1-update 1
sep 15, 2010:
cross posting with my post from the google help forums:
my steps to replicate are as below.
seems to be pretty consistent that the message sent in step 09 will go to a random contact; in my limited testing, it usually goes to the number involved at steps 05 and 06.
01) stop messaging app.
02) clear messaging app data
03) access messaging app, send messages.
04) establish messages were sent to correct addresses.
05) send message to a number not in your contacts.
06) reply from the number not in your contacts (i haven’t established if this is a required step yet)
07) read reply, don’t delete thread.
08) send sms to your device, from another device that is in your contacts.
09) reply to sms.
10) check message details of your sent message.
11) repeat steps 08-10 a couple of times.
a factor in this, is i think it might only be short numbers that cause this issue.
i’m using my banks automated sms service (880).
this would explain why it happens when people have facebook/twitter sms notifications enabled.
i’ll debug it all properly on the weekend when i have some time.
oct 05, 2010:
this issue is listed as “priority-medium”, i think this is totally wrong. for a phone send messages to the wrong person may be very harmful to the user as a human. this just means the phone cannot be trusted anymore. how to bump up the priority?
oct 05, 2010:
i have experienced this problem a few times. and i do not have facebook or twitter on my phone either. it’s actually a relatively new phone (samsung vibrant). to list this issue as “medium” is a gross understatement. this is much worse than iphone’s drop call problem. and there is no pattern in picking the wrong recipient. i actually think it’s an os lag issue. last time it happened i caught it before it sent the sms (because in my sms window i saw the wrong recipient showing on top, while i was in a thread window with someone else) and i let the phone sit for a few minutes. when i went back to my thread window, the correct recipient name was at the top once again.
dec 23, 2010:
except somewhere along the way, google seems to have forgotten first and foremost android phones need to be phones. and that is why i’m seriously considering making the move to blackberry or windows phone 7. for the last six months now i’ve been dealing with a huge flaw that makes my phone unusable for sms texting. from what i’ve been able to tell using analytics provided by google’s developer site, as many as 77% of android phone users are at risk of having their text messages sent to a random contact.
that sounds unlikely right? i mean you pay upwards of $200 for a smart phone, and next to making phone calls, sending sms text messages is probably the most used feature of the phone. but it’s true, and if you don’t believe me just type “android sms wrong contact” into google’s search engine and see how many hits you get. it’s astounding. it’s happening. and google seems to be ignoring it altogether.