View Poll Results: Have you experienced the "SMS Bug"?

Voters
413. You may not vote on this poll
  • Yes

    110 26.63%
  • No

    269 65.13%
  • Maybe -- something weird has happened (explain in the comments, please)

    22 5.33%
  • It doesn't exist, user error FTW

    12 2.91%
Page 1 of 4 1234 LastLast
Results 1 to 25 of 95
Like Tree1Likes
  1. Thread Author  Thread Author    #1  

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

    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
    ಠ_ಠ
    제리
  2. Thread Author  Thread Author    #2  

    Default

    I voted No. I can't get it to happen. I do however, believe it exists.
    ಠ_ಠ
    제리
  3. #3  
    stevemobs's Avatar

    Posts
    20 Posts
    Global Posts
    21 Global Posts

    Default

    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.
  4. #4  
    snobum's Avatar

    Posts
    29 Posts
    Global Posts
    32 Global Posts

    Default

    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
  5. #5  
    igotsanevo4g's Avatar
    Retired Moderator

    Posts
    3,558 Posts
    Global Posts
    3,549 Global Posts
    ROM
    Ice Cream Sandwich

    Default

    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.
    Some say the glass is half empty. Some say its half full. I say, "Are you going to drink that?"
  6. #6  
    Slashdpc's Avatar

    Posts
    21 Posts
    Global Posts
    35 Global Posts
    ROM
    CyanogenMod 6.1.2

    Default

    Can one of the responses be "What SMS bug? I use Google Voice" because that's my answer.
    10:15 philnickinson: Thanks, everybody. You all kick serious ***.


    Follow me on Twitter!
  7. #7  
    stevemobs's Avatar

    Posts
    20 Posts
    Global Posts
    21 Global Posts

    Default

    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.
  8. #8  

    Default

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

    Default

    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).
    Last edited by DenverRalphy; 01-02-2011 at 09:03 PM.
    "Some see the glass as half-empty, some see the glass as half-full. I see the glass as too big."
    - George Carlin
  10. #10  

    Default

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

    Default

    Hasn't happened yet. Unless people just haven't been telling me about it.

    Sent from my PC36100 using Tapatalk
  12. #12  

    Default

    I have only experienced it 1 time on my Epic. A friend of mine texted me and when I replied, it went to my wife who was sitting right next to me. When I looked on my phone it said it was sent to my friend, but he didn't get it.

    Epic is completely stock.
  13. #13  

    Default

    I dont think ive experienced it fully on my captivate. Ive had a different name at the top of the screen but hit sent anyways. after i send then i go back to home and click on the messages icon and look to see who it sent to. it always sends to right person but sometimes it says someone different. hasn't happened for like 3 days now. Stock phone with no sideloading.
  14. #14  

    Default

    Happened to me for the first time ever this weekend, before I ever found out about all the articles online. Droid Incredible.
  15. #15  
    Salacon's Avatar

    Posts
    106 Posts
    Global Posts
    134 Global Posts
    ROM
    Stock 4.1.1 and 4.2

    Default

    I voted "Maybe..." because I don't know if this counts: I've run into an issue where if I have multiple threads going, I will click on someone's but it opens someone else's. I always double check the name of the thread I'm in now, just to be sure. But it doesn't always happen.

    I've never experienced sending a text to someone but it being received by someone else, though. At least not as far as I know.
    "My work is not a piece of writing designed to meet the taste of an immediate public, but was done to last forever." - Thucydides, ancient Greek historian
  16. #16  

    Default

    I voted maybe. I have sent text messages in the past to one person to have someone else receive it. This has happened three times I can think of but I always assumed it was user error, me not paying attention to what I was doing. I will however pay much closer attention in the future.
    Don't mess with me, I haven't had my Tratonin yet.
  17. #17  

    Default

    Nope, although to be fair, I've sent a whole, what, 10 text message this past year... (well, I've been using google voice a lot lately to ping)
  18. #18  

    Default Not on my phone

    I've never seen this happen on my phone (rooted EVO using stock HTC Messaging app). The only time I've seen this was on my wife's samsung feature phone. She tried to reply to a text from her friend and it ended up in my inbox. I wonder if it's a carrier problem.
  19. #19  
    YourMobileGuru's Avatar
    Formerly VZWRocks

    Posts
    2,634 Posts
    Global Posts
    4,271 Global Posts
    ROM
    what's wrong with stock?

    Default

    Quote Originally Posted by DenverRalphy View Post
    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).
    This only effects the stock Android client, if the bug even exists at all which the fact that it can not be reproduced by Google and most others when they try lends to significant doubt.

    If Google is reading this I have a quick solution for you: scrap the stock client (it sucks anyway) buy Handcent and rename it messaging then bundle it on the stock roms. Problem fixed.
    Android is all about Personal Choice: Droid RAZR HD, Droid DNA, SGSIII, SG Note 2, HTC One X+, Galaxy Nexus, Nexus4... Hating is so Apple... we're better than that!

    Correcting Some of the Shared Everything Misinformation * My Phone Collection

    PSA - Verizon Galaxy Nexus Signal Strength Comparison
  20. #20  

    Default

    It has happened some four-five times on my Galaxy S (International version).

    I have, however, found a workaround for this, which I am sure most of you also have: See who you are texting. If it's the wrong contact, kill the Messaging app using ATK or some such app. Reload Messaging app and you will send the text to the right contact now. It's annoying to do this every time it happens, but it works for me. And has made me a lot more careful when it comes to texting.

    Has anyone also noticed wrong missed call notifications? I have had at least two missed call notifications from people who never called me. So I am guessing someone else called me and I got the wrong contact in my call log. Hasn't happened in a long while again.

    There are many issues with Android's native SMS app. Twice over the period of seven months since I have shifted to Android, my SMS inbox has been wiped clean with no trace of old texts. It happened once when I was using Handcent. I thought it may be Handcent's error and uninstalled it. But it happened again on the stock SMS app. Anyone else facing this issue? Would really like your help on how to retrieve the SMSes.
  21. #21  

    Default

    Quote Originally Posted by VZWRocks View Post
    This only effects the stock Android client, if the bug even exists at all which the fact that it can not be reproduced by Google and most others when they try lends to significant doubt.
    What about the people with Sense phones that seem to experience it?

    I don't, though. Rooted Desire running Sense 2.2.
  22. #22  
    YourMobileGuru's Avatar
    Formerly VZWRocks

    Posts
    2,634 Posts
    Global Posts
    4,271 Global Posts
    ROM
    what's wrong with stock?

    Default

    Quote Originally Posted by IceBone View Post
    What about the people with Sense phones that seem to experience it?

    I don't, though. Rooted Desire running Sense 2.2.
    If you read Jerry's original article from a couple days ago he is clear that the bug they are talking about is specific to the Stock client and does not effect other clients.

    My personal belief is that if indeed there is a bug it isn't responsible for all of the things that people report, many of them are user error amplified by the placebo effect (people think there is bug, therefor when they mess up they assume it is a bug).

    I've never had it but at the same time I haven't used the stock clients siince the moto droid. I long ago switched to hand-cent on all of my phones inducing the DInc (Sense) and Facinate (Galazy S).
    Android is all about Personal Choice: Droid RAZR HD, Droid DNA, SGSIII, SG Note 2, HTC One X+, Galaxy Nexus, Nexus4... Hating is so Apple... we're better than that!

    Correcting Some of the Shared Everything Misinformation * My Phone Collection

    PSA - Verizon Galaxy Nexus Signal Strength Comparison
  23. #23  
    dannychaos's Avatar
    High Five Champion

    Posts
    205 Posts
    ROM
    CM9 Nightlies

    Default

    I have a jacked up HTC Droid Eris and thankfully I have not experienced the bug nor any of my friends with Android phones. I also too believe that there is a problem and should geylt fixed quickly.
  24. #24  

    Default

    I have not experienced this issue at all, however I haven't actively tried to recreate it either.

    I use Handcent on my Droid 2 running Froyo NOT rooted.
    Last edited by dousenator; 01-03-2011 at 08:42 AM.
  25. #25  

    Default

    OK what happens for me very specific...

    I will select a thread in SMS to respond to, and sometimes the phone (I have an HTC EVO running baked snack 1.8 with the stock SMS app) will select a DIFFERENT thread, and if I do not notice, then I will have typed out a message and it goes to the wrong recipient.

    If, however, I DO notice which thread is brought up (about 1 in 10 misses, and it's not just fat fingers, it's a thread from MUCH lower down in the list, not next to the one I intended to select) and I bring up the correct one, it sends to the intended recipient correctly.

    Hope this helps.

    YES - this exactly.
    Quote Originally Posted by Salacon View Post
    ...I've run into an issue where if I have multiple threads going, I will click on someone's but it opens someone else's. I always double check the name of the thread I'm in now, just to be sure. But it doesn't always happen.

    I've never experienced sending a text to someone but it being received by someone else, though. At least not as far as I know.
    Sprint Galaxy S3 - rooted but still stock for now.
    Nook Color running CM7
    JVH1982 likes this.
Page 1 of 4 1234 LastLast

Posting Permissions

B