Is anyone else having issues with the wrong name being displayed in the notification bar and/or the message thread?
Sent from my SGH-T959 using XDA App
Actually it happened just one time. showed the wrong name in the thread on the top. Rebooted and it fixed itself. No clue why or how but hasn't happened ever since
Sent from my SGH-T959 using XDA App
I have rebooted multiple times. Plus it has occurred when my phone was unrooted and now that it is rooted.
Sent from my SGH-T959 using XDA App
Try clearing the cache for the messaging app.
Sent from my Vibrant using the XDA app.
Typos, incorrect words, gibberish, and other nonsense brought to you courtesy of Swype.
I had it happen quite frequently with one particular friend's name and photo appearing. Upon investigation, I discovered that friend's Facebook account listed a blank phone number and was linked to my own entries. The blank number apparently matched a variety of non-standard SMS numbers including those long numbers used for email-to-SMS. Unlinking and removing his Facebook entry solved the problem until he fixed it on his end. Might be something to look for.
Happened to me on stock and earlier lag fixes, hasn't happened since I had to reflash and installed new lag fix.
Solution? Delete that persons inbox, it always happened when high volume of texts would come. Then, I'd see two identical names threads in my inbox, one would be obviously for the wrong person. What's sad is that if you go and kill messaging via task killer, it fixes itself, but then it starts sending texts to wrong people, very annoying.
Sent from my SGH-T959 using XDA App
Any fix for this guys?
Yeah this has happened to me twice. I remember I was sending a video to my gf and it accidentally sent it to someone else. Or at least it looked like it went to someone else because the name was different. Thankfully they didn't receive it because it was a private video kind of haha.
I usually delete the 200+ text message threads and it fixes this issue.
Raceves said:
Yeah this has happened to me twice. I remember I was sending a video to my gf and it accidentally sent it to someone else. Or at least it looked like it went to someone else because the name was different. Thankfully they didn't receive it because it was a private video kind of haha.
I usually delete the 200+ text message threads and it fixes this issue.
Click to expand...
Click to collapse
But there's an option to have it auto delete when it reaches 200 messages per thread.
Sent from my SGH-T959 using XDA App
This problem seems to be an Android problem and not one specifically associated with the Vibrant.
There's a long discussion going on here: (sorry, I'm a new user and can't post URLs. So, add "www" to the following) : .google.com/support/forum/p/android/thread?tid=345259e6d424bad3&hl=en
Perhaps someone with some more experience with the code behind the standard messaging app can take a look and help figure out what's going on.
My "work around" has been to use a 3rd party SMS tool (e.g., Handcent) rather than the Android messaging app. The problem has not repeated for me using the 3rd party tool.
Related
When you have a text log with the original person? I have noticed it shows up in the notification tray under 1 name and then under the actual msg app its to the right person but it makes me scared at times who the last txt REALLY went too..
In the stock messaging app (all I use) Ill start a txt conversation with person x then down the line it'll send the next to person y... idk if it was a confusion between the linked fbook accounts but it almost got me in trouble so now for safety sake I dont have fbook linked to contacts...
Anyone notice this or is it just me?
Sorry to hear this. If its the same two contacts each time, I'd suspect your two contacts may have automatically linked or merged phone numbers. Inspect each one's details for the other's phone number. For example, I found that two contacts who shared the same email were merged, completely deleting one's name entirely.
I'm using Handcent myself so not sure if this would be related, but I've found that text messages received from one particular number (my bank's alerts) always appear as another contact (a friend) in the initial pop-up alert but then appear correctly in Handcent's actual message threads. I've since swapped and rebuilt the handset to no avail. This issue remains a mystery.
Sent from my SGH-T959 using XDA App
not the same contact. Thats what I originally thought it was something merged weird but its random. so I am not too sure but it makes me whery what I send to certain ppl. For some reason im friends with enemies of the other friend so saying 1 thing starts a fight btwn the 2.. lol I cant win.
same problem, HTC EVO, seems like it goes to a random person, facebook contact or not.
This is a huge problem and is related to the Android platform, not just the Vibrant. You can find more information in the following two links:
1. www.google.com.vn/support/forum/p/android/thread?tid=345259e6d424bad3&hl=en
2. http://code.google.com/p/android/issues/detail?id=9392
The best thinking that we have on the problem so far is that it is in the ComposeMessageActivity.java file. But it would be great to get more eyes looking over the code to try to get this one licked.
Note: A 3rd party app may make the situation better, but will not resolve it. Best solution is that if you receive a text or e-mail message (or anything that plays with the notification bar or takes focus from what you're typing), quit your message and start over.
This scares the hell out of me. Is there any specific instance when this always happens?
Strange, never had this problem and I've been using Android since the G1. There must be something you are doing or a setting you have that specifically triggers it.
There's nothing related to Facebook - I don't have anything linked on my phone. And I never had this issue on my G1, but I also didn't start screwing with the Vibrant until recently, so it's not something I'm "doing" - it's happened within weeks of getting the Vibrant on launch day.
It can be quite scary. Luckily my friends getting msgs meant for my wife hasn't bit me in the ass yet. But if it ever gets mixed up going to a female friend, I could see this not working out in my best interests, ya know?
-bZj
I've had the same problem on my vibrant and my g1. What I've noticed is that if I send a nescafe to person A then receive a message from person B and access that message by using the notification bar and answer person B, the message can go to person A (the last person I sent to.) I've found that if I remember to not use the notification bar and only access messaging by using the icon, I haven't had the problem. Not the best solution but at least it seems to work.
This could be bad
This could be bad especially if you have more than one girlfriend
Omg glad im not the only one. Had to couch it one night cuz of this issue. Now i only text my girl from my phone. Everyone else i text through gv lol.
I use the notification bar all the time and occasionally reply to the weekend person but that's just because I didn't press on the right notification...
yea i had this happen to me as well. luckily or unluckily a txt i was sending to a girl whom i was fooling around with got sent to a girl i had just met 3 days prior. after that needless to say she wouldnt talk to me waa waaa. it was prob a random bug introduced in earlier builds.. say around a month and a half ago. oh yea i had about 12 threads running around 50 a piece.. maybe that had something to do with that and maybe the random stuttering of the vibrant when too many programs are running. Havent had that happen again thankfully but one would have to say.. slow down on the texting sometimes lol
vinnydakid said:
This scares the hell out of me. Is there any specific instance when this always happens?
Click to expand...
Click to collapse
The evidence seems to suggest that the problem is in the ComposeMessageActivity.java file, which means it is not SMS Client related. Said differently, using a 3rd party SMS client might reduce the likelihood of the problem but does not eliminate it.
Now, to answer your question. It seems like the problem happens when multiple threads or events happen when using SMS. For example, it might happen when you are editing a message and when you receive a SMS text message. (It is more likely if you use the notification bar to pull down the message rather than navigating to it in the SMS client.) The good news is that people are trying to reliably reproduce the problem so that we can troubleshoot and fix the problem. (See my earlier post in this thread for a link of those discussions).
kangxi said:
Strange, never had this problem and I've been using Android since the G1. There must be something you are doing or a setting you have that specifically triggers it.
Click to expand...
Click to collapse
Based on the review of the code, one fix seems to have been made to the 2.2 code branch. However, people using 2.2 have indicated that they are still experiencing the problem. The problem is in the library. However, there is a very unique set of circumstances that have to occur before you see the problem. It's quite possible that people who haven't seen this problem yet just use the UI in such a way that the problem doesn't show up.
98classic said:
Omg glad im not the only one. Had to couch it one night cuz of this issue. Now i only text my girl from my phone. Everyone else i text through gv lol.
Click to expand...
Click to collapse
i second that. this glitch can be nasty. hopefully it will be addressed soon. GV for the win.
I have the same issue here. It will show one name but have a conversation for another, or the name and the convo are right, but the picture is wrong.
I think I found a solution to the thing. Been getting it a LOT and pissed me off on more than a single occasion.
So. If you are talking to someone and SUDDENLY receive a text message from that person but when you open it, it changes the name of the contact to someone else or ....I guess everyone who has experienced it KNOWS what it looks like. So when you GET IT, open it, then CLOSE the whole messaging app. Then restart it and it should fix itself and be back to texting the right person. If it doesn't (or if you want to be on the safe side), kill the messaging app with a task killer or task manager and restart it.
This has fixed it recently for me. Had it happen a total of about 15 times, with me finding and using the trick about the latest 5 times and it worked every time.
Note that I AM running Bionix Fusion 1.0 with Voodoo if that makes any bit of a difference.
I am having trouble text messaging my mom because the phone is adding +1 to the beginning of her phone number. The text message never goes thru. When I send the text message by typing in the number it sends fine.the problem is only when I select the contact from list. The contact list does not have the +1 in it so I don't know where it is coming from
Sent from my SCH-I500 using XDA App
Yea, i actually sat on the phone with verizon tech support for 2+ hours while they debugged this issue, turns out for some reason the +1 breaks it.. they never gave me an explanation, only a fix. Take the +1 out of the contact and make sure its saved and synced, you also need to nuke your message history after making the change or new messages will still have the +1 in front of them.
-Zetas
I tried taking it out of the contact # and killed the message history but still not working
Sent from my SCH-I500 using XDA App
I have the same problem...I don't get why this phone was released with so many bugs....I'm about to go get an Incredible
I had the same issue and was waiting for someone else to have this problem too. Removing the +1 on your phone contacts won't sync it completely it seems so once google syncs on your phone again the +1 will return. So what I ended up having to do is going on gmail on my pc and deleting all the +1 contacts in there. That did the trick right away. Hope this helps
Sent from my SCH-I500 using XDA App
I tried clearing my contact and messaging data and now I lost all my contacts and I can't re sync then from facebook or google
Sent from my SCH-I500 using XDA App
Sounds like you don't have a clue about what you are doing my friend
Sent from my SCH-I500 using XDA App
Its not that...iv tried everything to fix it..even completely erased all contacts and added just the problem number and still doesn't work...cleared all recent info and sms removed sync completely...nothing works
Sent from my SCH-I500 using XDA App
same thing happened to me (sending a text to AT&T) - had to remove the 1 from all my contacts via GMAIL.
Now fixed
Strange. I don't have any issues like this.
I did have the same issue as the op described, but I think the ota update fixed it or the clean rom posted in the development forum corrected the messaging app. It definitly has something to do with the messaging app since when I installed handcent sms all my messages worked without the +1 being added.
Sent from my SCH-I500 using XDA App
I had the same problem and fixed mine..here are the steps I took.
Log into Gmail on your computer, go through all your contacts and take out the +1 as well as the dashes 123-456-7890 to 1234567890 and save that. I then did a factory reset for my phone. Everything works great now.
I think when you have a GSM service they use the + symbol
I had this same problem. When I got my phone the text messaging was working just fine. Couple days later no one was getting my text. So I went down to the store and they did everything they could do and I finally figured out it was the +1 in the numbers.
I switched over from a G1 on T-Mobile, so GSM can use +1 but it seems Verizon or CDMA has a problem with it.
I went through all my contacts, got rid of the +1. Yet when I'd send a message through the default sms app the moment they replied back it would automatically add the +1 again. So the only solution I found was that I had to use a different SMS app. I went with Handcent.
Im more concerned why you have the country code in your contacts list anyway? Ever since I had my first phone years ago manuals said not to put the country code in your contacts list for domestic contacts. Ive never had a problem.
Sent from my SCH-I500 using XDA App
i tried everything... the only thing that fixed it for me was a complete factory reset
iifuzz said:
Its not that...iv tried everything to fix it..even completely erased all contacts and added just the problem number and still doesn't work...cleared all recent info and sms removed sync completely...nothing works
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
I had an sms issue I have been trying to resolve for weeks. Spent three hours with tech support troubleshooting, and finally determined something in the hardware. Took it in for a replacement. My g/f has the same phone, and no issues.
I wish verizon (or Samsung?) would fix this!
broncobiker said:
Im more concerned why you have the country code in your contacts list anyway? Ever since I had my first phone years ago manuals said not to put the country code in your contacts list for domestic contacts. Ive never had a problem.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
When traveling internationally, it's a royal PIA when your US & Canada contact records don't include the country code and you're trying to place a call to north america... When I go overseas, I use an unlocked GSM android phone, and I would like to load my US contacts via Google in a usable format (10 digit numbers aren't usable from abroad).
This is a Verizon-Samsung bug - removing the country code from all US contact records is a work-around (not a fix!). My previous Verizon phones (mostly old Windows mobile handsets) had no trouble sending texts to US mobiles using the international standard country code prefix.
I just loaded up the leaked froyo modem, kernel and rom (EB01, EB16 & superclean 2.6 voodoo respectively), and unfortunately I see this issue persists...
Can anyone tell me if any of the verizon Android handsets from HTC or motorola share this flaw?
Thanks!
Hey guys, I wanted to see if any fellow vibrant uses have been getting this.
This is the second time this has happened to me. Just out of no where I will launch my sms application (handcent) and the all of my texts are gone, like magic....
I have done alot of looking and found out that this is an old problem that is general for any android user. Wanted to see if anyone know the solution to what is causing this.
Sent from my SGH-T959 using XDA App
This just happened to me recently. I also use handcent. I dont know if this is the case for you, but I am a packrat, so I had a lot of messages.
I think the limit of SMS messages that can be stored on the phone is 5,000. The only thing that didnt make any sense is that not ALL of my messages were gone, I had 8 left from a recent conversation. I cant explain why they werent deleted...
We can start narrowing things down though. If you dont think you reached the phones limit, then maybe it is a Handcent bug, or a bug with TouchWiz.
it use to happen to me before when i had i believe was the mytouch slide at that time but i cant recall. and yes it happened when i had over 3000+ for my GF and like around 200 for other people! Now i usually just get to 600 or less and delete it and start over. I use the stock sms app btw and have no problems at all.
It happened to me too, not the first or second time it have always happened from the start. I don't use handcent, everything is untouched with no root.
Sent from my SGH-T959 using XDA App
Hmmm...a few people claim that this stopped after they uninstalled the antivirus app. However, I never used this app so it can't mean that. On top of that, many claim that this was due to 3rd party app. That wouldn't make any sence because if uninstalling different apps will fix it.
A few also mentioned that installing the sms back up also stopped the problem. It was also mentioned that handcent has an update coming that said they would fix it but that was almost a year ago. I couldn't find anything on the handcent website that fixed the issue. A lot of android users have the same issue as us on their forum. There are at least 10+ posts on this topic, non with a solution....
Sent from my SGH-T959 using XDA App
Have you removed the settings to delete old messages when limits are reached?
or have u edited those settings in the messaging app?
That's the first thing I checked
it's unchecked, no limits and no deleting if old text messages. Here's the thing, even if that was enabled, it would only delete after reaching the limit and keep it at that. What happened was that all the text messages just disappeared...
Sent from my SGH-T959 using XDA App
This used to happen to me on the G1 on occasion. I got around the issue by using the CyanogenMod Messaging application and setting the auto-delete limit to 200 messages per person, and using the free SMS Backup application to export all SMS messages to a label Gmail as they're received. I'm still using the same solution on the Vibrant, and I've had no problems since.
I didn't think that cyanogenmod is available for the samsung vibrant yet...or am i missing something?
Sent from my SGH-T959 using XDA App
DynamicXL said:
I didn't think that cyanogenmod is available for the samsung vibrant yet...or am i missing something?
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
The CyanogenMod 5 (Android 2.1) Messaging app can be installed over the Vibrant's Messaging app just fine. Download a CM5.0.8 ROM for the Nexus One and install the Messaging.APK found in \system\data. :]
I'll give it a shot and see how it goes.
Sent from my SGH-T959 using XDA App
I've been reading about this bug for awhile now and it finally hit me. What happens is if contact A sends you a txt message and you respond. The message thread will show that your response went to contact A, but the reality is that A may not have received the response, however C,D,E,F, Z,Y and X did! It seems to be totally random, will happen regardless of the SMS app or ROM you use and can be quite dangerous. This bug renders my N1 virtually useless. Anyone else experience this or has an update on the fix for this dangerous bug?
I recommend anyone with an Android phone to be use extreme caution when sending txts or mms messages as you never know who may actually get it
Have read about it, but it's never happened to me.
Can you reproduce the bug reliably?
Can you dump the logs (/proc/kmsg and logcat, or bugreport) immediately after it happens?
Any pattern connecting recipient A and the rest?
Nightmare!
Sent from my Nexus One using XDA App
How come that not even one person from those reporting having "this bug", wants to help find out, what it is? Very interesting.
I have found that using handcent resolves this problem for me.
Sent from my Nexus One using XDA App
My wife have experienced the problem twice with Galaxy S, I haven't have similar troubles with my N1, although every now and then it takes time for some messages to go through. That is probably due the carrier, not the device.
Sent from my Nexus One using XDA App
The only trouble with messaging i have is that sometimes when i select to open the thread at the top of the list, the one at the very bottom of the screen opens. Frustrating!!!
cymru said:
The only trouble with messaging i have is that sometimes when i select to open the thread at the top of the list, the one at the very bottom of the screen opens. Frustrating!!!
Click to expand...
Click to collapse
I have this too in a pre 6.1 nightly...
But it's not the first time i hear the bug that SMS are sent to everyone, so it definitely exist
Sent from my Nexus One using XDA App
I saw the "reports" on the net popping up once in a huge while, but I never saw anyone that would report this bug and actually try to solve it, or assist anyone in solving it. Doesn't look like a normal bug report to me, and doesn't look like there is a bug. I know over 15 people with all kinds of Android, at least 6 with Nexus, and it never happened to anyone. The "bug" looks very fishy.
Jack_R1 said:
I saw the "reports" on the net popping up once in a huge while, but I never saw anyone that would report this bug and actually try to solve it, or assist anyone in solving it. Doesn't look like a normal bug report to me, and doesn't look like there is a bug. I know over 15 people with all kinds of Android, at least 6 with Nexus, and it never happened to anyone. The "bug" looks very fishy.
Click to expand...
Click to collapse
I can assure it is a bug and a major one. It is well documented if you google it. It appears to be across many different hardware platforms and therefore is most likely a source code issue written incorrectly in the android OS. And just because the 15 people you know aren't having the issue does not mean the rest of the world isn't. This is my 3rd android phone and this is the only one that does it and from I've been reading there are many others who are also having this random issue...I assure you, this isn't something that someone can do by mistake or accident...
In that case, if it's so well documented, how come that nobody has ever assisted anyone else in debugging it, yourself included?
It's happened to me.
I receive certain friend's facebook updates as sms. One time I got the facebook sms. I closed it then replied to another friend's sms. Guess what happened.... what I sent to my friend got sent as a comment to my friend's facebook status.
Looking back at the sms log, I definately wrote my reply to my friend, not the facebook sms, but somehow it was replied to the facebook sms.
This bug has been around since Android existed.
There's really no way to debug this I don't think, unless you only have a few contacts that will text u if you write something weird... cuz having a phone full if phone numbers, your text can be sent to any number, even non mobile phones, you wont know since you thought u texted the right person.
Sent from my Nexus One
There's a ton of ways to debug everything, including even specifically modified SMS app for dumping debug data - it's an open OS, yes? If I got some beta application versions for debugging from app devs to test things, I'm sure Google wouldn't do less to debug it.
For starters, the next SMS I'll check the records in kernel log and see if there's any useful data to start from there.
Jack_R1 said:
In that case, if it's so well documented, how come that nobody has ever assisted anyone else in debugging it, yourself included?
Click to expand...
Click to collapse
Well I think you bring up two entirely non-related issues... First, if you google it, you will find a vast amount of people all having that same issue, which in my mind establishes the "well documented" part of my statement. Secondly, as far as me or anyone else participating in debugging, I would love to, but it's a little out of my sphere of knowledge. If you could give me a little insight into what needs to be done, I would be more than happy to do what I can to help solve the problem. This $500 phone is totally useless to me if I can't be certain who will be receiving my txt messages. Mainly, I've been waiting and watching in the hopes that google would get involved and resolve this issue without my having to get involved. It would appear that this goes back a considerable amount of time.
Can you list out a step by step process to go about this so that all who are having this issue can also participate? What should be my next step
To even try to start with debug, you have to have a rooted phone.
The useful place to look at would be /proc/kmsg. The question is - how much data it contains after sending sms. I didn't try to dump it after SMSing yet, didn't have time for it. I'll try to find time over the weekend.
If it won't contain enough data, modification in SMS application is needed, to dump the data there to help with debug. This is much harder for me, because I'm not an app dev, and I'll have a hard time trying to find and understand the relevant data structures to dump there. Basically, when you hit "reply", some kind of indicator of current SMS thread needs to be dumped, and everything else that might result in wrong number being selected - all the chain that determines the number that the SMS goes to. Then, once the SMS was sent to wrong recipient, the info needs to be dumped and checked.
The later part is "slightly" beyond my skills. It requires knowledge of SMS application and its data structures.
It obviously happens only to those that have their Facebook contacts integrated, so the mechanisms that take care of joined contacts might be something to look at.
It never happened to me, and I've sent 12000 sms from my Nexus. Try using Handcent until this is officially fixed. Handcent is free and many people say it's not affected by the bug.
Jack_R1 said:
To even try to start with debug, you have to have a rooted phone.
The useful place to look at would be /proc/kmsg. The question is - how much data it contains after sending sms. I didn't try to dump it after SMSing yet, didn't have time for it. I'll try to find time over the weekend.
If it won't contain enough data, modification in SMS application is needed, to dump the data there to help with debug. This is much harder for me, because I'm not an app dev, and I'll have a hard time trying to find and understand the relevant data structures to dump there. Basically, when you hit "reply", some kind of indicator of current SMS thread needs to be dumped, and everything else that might result in wrong number being selected - all the chain that determines the number that the SMS goes to. Then, once the SMS was sent to wrong recipient, the info needs to be dumped and checked.
The later part is "slightly" beyond my skills. It requires knowledge of SMS application and its data structures.
It obviously happens only to those that have their Facebook contacts integrated, so the mechanisms that take care of joined contacts might be something to look at.
Click to expand...
Click to collapse
This is why I haven't, as you say, participate in resolving the issue...the level of of debugging required to get to the source of the problem is deeper than a non-developer like myself can go. And for the record, this is NOT related to the facebook app in anyway as I do not even have that app installed. This is 100% an Android code issue...
Are all your contacts Gmail-synced contacts?
Does it happen frequently enough to try to debug?
This is what happens with my N1:
I get a new text message, alerted in my notification bar
Rather than open it from the notification bar, I open the messaging app and tap the first message (just a habit, I guess)
The ninth message opens instead of the first one
I'm not sure if this happens every single time, but it does happen frequently.
I'm wondering if it might be a bug in CyanogenMod instead, I've only started noticing it recently.
PS: I do not have a Facebook account nor any accounts synced with it. The only contacts I sync are my Google contacts.
Whole message threads seem to have vanished on me...did reboot this morning but still that shouldn't be happening
I have never had this happen to me; make sure you don't have any settings enables to delete them enabled though.
Sent from my Nexus One using XDA Premium App
Two questions:
1) yes, there are settings to delete messages after a certain time / amount...check text message settings.
2) have you ever texted someone to their email address or had someone text you from their email address? This creates a pretty bad bug in Android before 2.3.
I am not seeing g any settings for texts that says when to delete them or not...either way though I doubt that would be it ABC the phone and rom were like brand new