[POLL] Have you seen the "SMS Bug"?

[Jerry Hildenbrand]

a1Will I Am's comment on the blog post about the SMS Bug (read that here, then here) brings up an excellent point.

We need a poll to determine how widespread this one really is. While not scientific, it can be helpful, so vote in the poll, and discuss below. Keep it friendly please

[Jerry Hildenbrand]

I voted No. I can't get it to happen. I do however, believe it exists.

[Thrab]

With how few people have ever reported this and the fact that it unreproducible one really has to wonder if it is not user error. I voted no rather than option four just to give them the benefit of the doubt.

[snobum]

The only problem I've had has been that some messages SHOW as being sent to someone else, but the person I wanted to send it to responds so it must have gone out correctly. I don't know of any that went to the wrong person.

BTW I have an EVO

[igotsanevo4g]

Yeah it happens on my stock evo, and on any rom I use.
I hit the top text and itll bring me too the bottom, or ill send one and itll go to a completely different person.

One time i told my boss to stop jacking off on accident, i meant to send it to a friend that was running late. Yeah, that went over REAL well especially when i cant reproduce the bug to show him.

And i really dont like Chomp or handcent. I want my damn stock messaging app.

[Slashdpc]

Can one of the responses be "What SMS bug? I use Google Voice" because that's my answer.

[Thrab]

I am not sure if people have thought of this already but is there a particular carrier this happens on more than others? I am not intimate with SMS implementations but maybe it is really carrier side? Is there some type of confirmation response to the device when you successfully send an SMS and it has a return number then Android files it under a specific thread? Just a random thought.

[_Zguy__]

Have seen contact names switched on feeds about 5 times for 5 seconds then went back to normal
But none of this bug

[DenverRalphy]

From what I've been able to piece apart from all the talk about this, I think the test should be as this...

User A should start to compose a SMS to User B. User C composes and sends a SMS to User A, and it is received by User A before he sends his composed message to User B. User A then sends his message, and see who receives it even though it was intended for User B. (it's a lot simpler than it reads lol)

My theory is that an SMS that is being composed is having it's recipient changed when an incoming SMS interrupts it.

After picking apart all the reports on various sites, that's how I see it happening. Personally, I think it's an issue of having more than one sms messenger on your device, or a SMS widget, and they're conflicting with each other.

Anybody able to replicate the bug should list the following items...

• Which SMS client it affects
• List all SMS clients installed on the device
• List any/all widgets installed that are even remotely related to SMS
• Device used
• OS version
• UI (sense, motoblur etc)
• Any activity on the device within the previous 20 minutes (a bit long, but hey, who knows)

The key is finding a common denominator.

[edit] Another thought just occurred to me. Verify whether there are any unsent Drafts (text messages composed, but not sent for whatever reason).

[Blayze04]

Mine happens about 2-3 times a day on my Nexus One. It also happens on my girlfriends Samsung captivate.