Related
hi, ive been using super hero beta 2 and until yesterday i had no problems. but all of a sudden, every time i got a text, the most recent received message would be put before all of the messages i sent. so in the message thread, the received messages are in order but all together at the top of the thread. my sent messages are in order but all at the bottom of the thread. the messages arent in order of the conversation. its really annoying to always have to scroll up to find what someone has sent me.
i didnt think much of it because i figure a wipe would fix it. today, i wiped and installed the new jacman rom and am still having the same exact problem.
is anyone else having this problem? does anyone know how to fix it? thanks!
this has been an issue for a few people, if t-mobile is doing tower work in your area it will screw with stuff like timestamps(are those correct for both incoming and outgoing?) and order of messages
Are you using the stock messaging or chomp sms? I used to have this same problem with chomp, then I upgraded to JF 1.5 and didn't need chomp anymore. Stock messaging has never done this thus far, but I know how annoying it is.
My nstive messaging app is doing that! It was frustrating as hell I did a wipe, flashed a different Hero rom, and still. I downloaded Chomp it has no issues....its the message app that is doing it to me
I have never had this issue before (except a brief trial of chomp) and then 2 days ago it started happening to me from my gf's phone to mine. I have seen it on a Hero build, a Rogers build, Ion build, and now The Dudes Rogers build. Next step im going to check the clock on her phone and see if that may be part of the issue or something.
The only time I've ever seen this problem is when two texts are sent/received within the same minute, and they would be grouped similar to that. So, for example, if someone sends me two texts within a minute, and I reply twice to those messages, and they would group similar to the original poster.
Have we tried rebooting? Is this present across multiple SMS threads? Using simple stock firmware/messaging app, or even going as far as installing a new messanging app amd seeing those results?
In all honesty, Hero is no where near perfect right now and probably won't be for a long while. It was never meant to go on the G1 so we can't expect perfect results just yet. Try using a different ROM, and see what results you get.
What I think you might want to try first, however, is to not use network provided values for the clock. Try using the phone's clock values. You can change this in Settings->Date and Time. Erase all threads, and chat away. Let me know the results.
@brandenk
I've been using TheDude's build for over 2 months now, and I've never experienced problems like this. If this is so common place across all these builds, have you seen the same results on a stock build?
birkholze said:
is anyone else having this problem? does anyone know how to fix it? thanks!
Click to expand...
Click to collapse
My GF's G1 started having messages appear out of order a couple/few days ago as well. I'm in the Orlando area. I figured it's T-Mobile screwing with the configuration of their messaging servers as someone mentioned earlier. Hopefully it clears up soon.
Time fixes everything
the problem was happening with the stock messaging app. just appeared out of no where. it doesnt even happen on every conversation, it happens to the three or so i text most often. my time stamps in the messages are correct, the other person's messages usually have a pattern of being 4 exactly 4 hours behind, but some times they just get jumbled with random time stamps.
i tried the date & time thing then a restart and im still having the same problem..
Same thing keeps happening to me, I am on the Super Hero v2 build and it also happened to me on the v1 beta build.
I switched back to ION yesterday and it stopped...and switched back and it started instantly again...Coincidence ?
Everyone is saying it's happening on every build, but I have only experienced it on Hero.
More info
Apparently, as far as my GF has noticed, it is only happening with MY messages to her, not other contacts. I've got Sprint, she's obviously on T-Mobile. Anyone else notice if it's only from certain (non-T-Mobile) customers? I suspect it's a particular SMS exchange server screwing up the timestamps.
When I had this problem it was from a tmobile number(one of my faves) and a verizon number so I'm not sure that its carrier related
I've had two episodes where I sent a SMS to my dad, and the SMS shows up in the list of messages sendt to my sister -> My sister got the SMS.
Another example: I sent a SMS to my friend, and it shows up in the list of messages to my uncle. My friend answered the message.
Anyone else experienced something similar?
Is there a fix?
Can't say that I've ever had that happened unless I mistakeningly sent it to the wrong person. Human error rather than device error.
I'm sure you uncle must have enjoyed the message.
Have you thought that maybe your numbers are messed up?? Or maybe all your contacts are switching with each other to mess you up.
Yep, chedked the numbers. This is definately a device error.
I had this self same problem yesterday! I thought it was me.
I sent an SMS to a friend called 'Ross', it showed up as Ross in the 'To' field but when I went into my sent messages it had gone to a friend called Robert. This occurred twice - but hasn't with subsequent messages.
Weirdest thing isn't it?
Now, how do we go about fixing this?
z0nic said:
Weirdest thing isn't it?
Now, how do we go about fixing this?
Click to expand...
Click to collapse
You need to email HTC support like with any issues / bugs you find or they will never know about them. Then hope they bring out a software fix. If we don't tell them, they will think its only a handful of people and not bother to do anything.
Also make sure your contacts' numbers are correct.
I have had the same problem, but the message hasn't actually been sent to the wrong person. It seems that it gets confused about who the person is. In my example the person I texted began with Dan and the second Theresa, so not next to each other in contacts. Theresa didn't say she had received something from me.
Same problem here
I did report this to HTC along with not getting sms and getting multiple of the same sms. All they suggested I do is a hard reset (already done) which did not change anything. Not very happy with them they didn't day it was a software fault or a fix was coming
They gave me the same response (although I only reported not getting all messages). If the hard reset didn't work they said to get the phone replaced. Its definitely a software fault so I am not replacing it, seeing as others have had issues with dead pixels etc...
It's only a display problem, you just close messages then reopen it, or go to the messages tab of the contact you sent the text to then click on the message and it'll correct the names.
I've had a similar issue once! Strange experience: I actually thought I had sent all kinds of SMS-es to the wrong person ;-)
In my case the names changed back automatically after about 30 bewildering seconds. Never had an issue since.
I have uninstalled Handcent SMS that caused several conflicts on my Hero, inclusing SMS-es not arriving at all. I might have had the 'wrong name' issue when I had Hancent installed. Don't really remember.
hey guys, with every build of android i've tried with the vogue, sometimes an sms comes in with Anonymous as the sender's name/number. There is no sender info there at all, so I just have to guess who sent it. Has anyone else encountered this problem? Thanks so much in advance
EDIT: We(Sjs01) have narrowed it down and discovered that it is a problem when using an Airave. If we turn off the airave or leave it's coverage messages come in with the contact name like normal. Great catch sjs01! So, we are hoping a dev could look at this to see if there may be a fix for it. Thanks!
Leukay said:
hey guys, with every build of android i've tried with the vogue, sometimes an sms comes in with Anonymous as the sender's name/number. There is no sender info there at all, so I just have to guess who sent it. Has anyone else encountered this problem? Thanks so much in advance
Click to expand...
Click to collapse
I've tried nearly every build, and I have never once had this error. I send around 5000 txts a month.
scizzle said:
I've tried nearly every build, and I have never once had this error. I send around 5000 txts a month.
Click to expand...
Click to collapse
Yeah, it's really odd, I can't find anyone with the same issue at all
EDIT: It has become more and more frequent. About 1 in every 15 texts actually display the sender's name/number. Hmmmmmm...
What is your carrier? I have mine on sprint with 1.5 standard system from the vogue-android proj page.
I seem to have hit or miss text message receiving and havent pinpointed the issue with sending SMS to a "CONTACTS" cell number. Basically I cant reply to a text or 'send' to a contact's SMS/mobile number, They never get it. If i send it using raw digits they do.
Was kind of curious about your experience there.
kkruse said:
What is your carrier? I have mine on sprint with 1.5 standard system from the vogue-android proj page.
I seem to have hit or miss text message receiving and havent pinpointed the issue with sending SMS to a "CONTACTS" cell number. Basically I cant reply to a text or 'send' to a contact's SMS/mobile number, They never get it. If i send it using raw digits they do.
Was kind of curious about your experience there.
Click to expand...
Click to collapse
I'm on sprint, "dzo booting" the donut build here: http://forum.xda-developers.com/showthread.php?t=591104 But I've had this problem with every build I try, even when running from the SD. And regarding your issue, I can send to a contact name and they receive it every time, but it's when they reply to me, it comes in as "Anonymous" and I cant reply to it. Also, I just did a test, and even when the number isn't in my contacts, it comes up as Anonymous.
Leukay said:
I'm on sprint, "dzo booting" the donut build here: http://forum.xda-developers.com/showthread.php?t=591104 But I've had this problem with every build I try, even when running from the SD. And regarding your issue, I can send to a contact name and they receive it every time, but it's when they reply to me, it comes in as "Anonymous" and I cant reply to it. Also, I just did a test, and even when the number isn't in my contacts, it comes up as Anonymous.
Click to expand...
Click to collapse
How do you have the numbers saved in your contact list? I had issues before with sending SMS and found that I needed to remove the leading +1 from all the numbers I had stored. One I had them all setup as (area-code) XXX-XXXX then my SMS was working great again.
stickus said:
How do you have the numbers saved in your contact list? I had issues before with sending SMS and found that I needed to remove the leading +1 from all the numbers I had stored. One I had them all setup as (area-code) XXX-XXXX then my SMS was working great again.
Click to expand...
Click to collapse
Yeah, I heard about that, so I tried it, but none of the numbers have the 1 at the beginning. I deleted the contact, re-entered them, everything. I had to flash back to WM (poo) because it got to the point that every SMS that I received was from "Anonymous." Ugh I can't be the only person that's ever had this problem can I? lol
i've read just about every thread on android, and don't recall seeing this problem. i used to have a problem with missing incoming sms (people would send to me, and I would never receive them), but it seems to have fixed itself - coincidentally around the time I stopped using compcache, don't know if it had anything to do with it.
sorry, i've got nothing for you. i'm sure you have already tried deleting all files from your SD card and putting fresh stuff.
I am also having this problem, the text almost never comes in the persons name, I have tried the fixes in this thread with no success.
Sjs01 said:
I am also having this problem, the text almost never comes in the persons name, I have tried the fixes in this thread with no success.
Click to expand...
Click to collapse
I'm not the only one!!! Yess!!!
Now, how to fix it. Since nobody seems to even know about this problem, let alone how to fix it, I'm just going to ask some questions.
What COULD be causing it. It can't be the system, because it happens with every build I try.
Sjs01 said:
I am also having this problem, the text almost never comes in the persons name, I have tried the fixes in this thread with no success.
Click to expand...
Click to collapse
Interesting issue,
If you guys could do this that would be great.
connect your phone to your linux (or windows if you're not using the latest nand boot files)
at shell do ./adb logcat -b radio > radiolog.txt
have someone send you a txt who regularly comes up as unknown
ctrl c in your terminal window to end the logcat, and post the radiolog.txt,
We can look over your log and see what may be causing it, if it's RIL related you will have to wait for vilord to impliment a needed change, however because so many people aren't having the issue it may take a while.
Hope this helps
I'm using the same version (http://forum.xda-developers.com/showthread.php?t=591104), booting from nand, and having this exact issue.
I'd try to use adb to see the log but there is an issue using windows adb with nand flashed android.
Im having trouble trying to create the logcat, but I've made an interesting discovery. I tried out HeroZenMagic--102309--system.sqsh rom the host site where they are keeping the old hero builds, and with that build pretty much every sms came through with the contact name. That got me thinking, all of the older builds seem to work just fine, its just the newer ones. And the problem with that is, they are much less advanced and more sluggish. Maybe this information can help? The build can be downloaded here: http://www.mediafire.com/?sharekey=aa29b5ef55091cf1c79b87b207592a1c3574eefa2a593379ce018c8114394287 Try it out and see if your results are the same, and if so, maybe we can figure something out!
mssmison said:
Interesting issue,
If you guys could do this that would be great.
connect your phone to your linux (or windows if you're not using the latest nand boot files)
at shell do ./adb logcat -b radio > radiolog.txt
have someone send you a txt who regularly comes up as unknown
ctrl c in your terminal window to end the logcat, and post the radiolog.txt,
We can look over your log and see what may be causing it, if it's RIL related you will have to wait for vilord to impliment a needed change, however because so many people aren't having the issue it may take a while.
Hope this helps
Click to expand...
Click to collapse
I'm not actually booting from nand, I'm just have been using haret to boot up android. I was also having some trouble creating a logcat but I think I managed to get one that I think has what you need. If something is wrong with it let me know and I'll try to get a better one. I would try to make it write a radiolog.txt but it wouldn't work. So I ended up just copying what was in cmd and pasting it into a notepad and just saving it.
Leukay said:
Im having trouble trying to create the logcat, but I've made an interesting discovery. I tried out HeroZenMagic--102309--system.sqsh rom the host site where they are keeping the old hero builds, and with that build pretty much every sms came through with the contact name. That got me thinking, all of the older builds seem to work just fine, its just the newer ones. And the problem with that is, they are much less advanced and more sluggish. Maybe this information can help? The build can be downloaded here: http://www.mediafire.com/?sharekey=aa29b5ef55091cf1c79b87b207592a1c3574eefa2a593379ce018c8114394287 Try it out and see if your results are the same, and if so, maybe we can figure something out!
Click to expand...
Click to collapse
I'll have to try this and let you know, but I can't tonight. When I used to use the older builds normally my texts would come in fine, but texts from other sprint customers would almost always be anonymous, but now it's with almost everyone.
Leukay said:
I'm on sprint, "dzo booting" the donut build here: http://forum.xda-developers.com/showthread.php?t=591104 But I've had this problem with every build I try, even when running from the SD. And regarding your issue, I can send to a contact name and they receive it every time, but it's when they reply to me, it comes in as "Anonymous" and I cant reply to it. Also, I just did a test, and even when the number isn't in my contacts, it comes up as Anonymous.
Click to expand...
Click to collapse
I think I may have figured out the issue (at least my issue), Leukay, do you by chance have an Airwave? I am on Sprint and had realized that, for the most part, whenever I would go out of my house the texts would start coming in with the actual name/number, but when I would go back into my house my texts started coming from "Anonymous" again. So tonight I went down and unplugged my Airwave, sure enough the texts started coming in as the actual name and number again. So if you do have an Airwave you should probably try to unplug it and see if the texts start coming from the right numbers.
Sjs01 said:
I think I may have figured out the issue (at least my issue), Leukay, do you by chance have an Airwave? I am on Sprint and had realized that, for the most part, whenever I would go out of my house the texts would start coming in with the actual name/number, but when I would go back into my house my texts started coming from "Anonymous" again. So tonight I went down and unplugged my Airwave, sure enough the texts started coming in as the actual name and number again. So if you do have an Airwave you should probably try to unplug it and see if the texts start coming from the right numbers.
Click to expand...
Click to collapse
As a matter of fact, I do have an Airave. I try that today and post later today! thanks for the tip
EDIT: That completely gets rid of the problem! The only problem is I need the airave to make calls in my house. Hopefully the devs can figure out why the airave produces this problem
I have an Airwave too. I guess that's definitely the problem. Can't disconnect it though cause I won't have any service in my house.
Leukay said:
As a matter of fact, I do have an Airave. I try that today and post later today! thanks for the tip
EDIT: That completely gets rid of the problem! The only problem is I need the airave to make calls in my house. Hopefully the devs can figure out why the airave produces this problem
Click to expand...
Click to collapse
I know how you feel if I don't have my airwave I can barely get a signal in my house. I guess we can just hope the devs can fix this. But they're really busy so I'm not expecting it anytime soon.
Do we have a way to force roam in android?
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.
Here's a weird one. I just found out one of my contacts hasn't been getting my texts for the last 2 weeks. I still receive his but can't send even though I do get a sent verification.
I can send to everyone else w/ no prob & he receives texts from others with no problem too.
I D/L'ed & used handcent for a while & then uninstalled it... Could that be it? WTH happened?!?!
Thanks for the help.
(Rooted JI6 never flashed)
hellcatrydr said:
Here's a weird one. I just found out one of my contacts hasn't been getting my texts for the last 2 weeks. I still receive his but can't send even though I do get a sent verification.
I can send to everyone else w/ no prob & he receives texts from others with no problem too.
I D/L'ed & used handcent for a while & then uninstalled it... Could that be it? WTH happened?!?!
Thanks for the help.
(Rooted JI6 never flashed)
Click to expand...
Click to collapse
might be a weird question,but what phone does you friend have?
me and my friend had the same problem..i wasnt receiving his text,but he was receiving mine.
There are a few bugs in the messaging app. In your case, it sounds like your friend's phone number / name has become associated with a different phone number (within the messaging cache). So, even though your display will show your friend's name, that's not where the messages will be sent.
Try to delete all of your threads and then reboot the phone. If that doesn't work, try clearing the data for the messaging app and then reboot your phone. That should do it. If that doesn't work, you can take the most drastic step, which is to do a factory reset, but then you'll need to do a restore of your apps and other data that would get wiped out.
Secondarily, there's a slightly different bug that could be happening (one that is much more rare than the first) - which is that your friend's phone number is the same, except for the area code, as someone else in your contact list. The messaging app only looks at the last 7 digits to determine a match for the phone number, so 415-123-1234 will match 310-123-1234. This one is much more rare, but that's another possibility.
BTW, these problems are internal to a specific Android class, so it doesn't matter whether you use Handcent or the stock messaging app.
Hope this helps.