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.
I was all set to finally take the plunge and sign a contract with Sprint for the new Hero - just waiting for my prepaid cellphone account to run out of money. Now more and more reports have started coming in about the Sprint Hero and its issues with losing SMS, and possible MMS too. Some sauces:
Engadget's questioning > and the scary responses: http://www.engadget.com/2009/10/26/htc-hero-having-intermittent-text-messaging-problems/
Sprint Community's ongoing thead: http://community.sprint.com/baw/thread/22913?tstart=0
SprintUser.com's ongoing thead (there are many): http://www.sprintusers.com/forum/showthread.php?t=195769
Slightly older but still the same problem from here from XDA: http://forum.xda-developers.com/showthread.php?t=572134
A few observations (feel free to add your own):
-UK/GSM Hero users are experiencing this, though to a much lesser extent
-A common, but not completely sweeping assessment is that affected users are using task killer programs or did at one time, even before a hard reset
-Soft resets tend to help the problem, though only temporarily (for some)
-People are getting the same issues on brand new phones that they exchanged for old ones.
Any thoughts? Do you have any personal experiences with this? I'm hoping to hold out till HTC/Sprint releases a patch or some sort of announcement about this problem but in the meantime, what has your experience, as a CDMA/Sprint Hero user, been like in regards to losing/delayed SMS and MMS messages?
From my experiance running Hero on the G1 lost text messages were due to the messeges app failing due to many things running and causing it to crash.
I can't speak for the sprint Hero, though I have not experienced any lost text messages I am aware of.
Maybe its a network issue?
I actually experienced it once. From what it appears, I downloaded a task manager and selected to kill all running apps. After I rebooted my phone though I have yet to experience any text message loses. Originally I was blaming it on a 3rd party messaging service, however now I really think it was as a result of killing the messaging app. This happened about a week and a half ago and so far *knocks on wood* have not experienced any other issues. Aside from that, I still love my hero. I honestly think that it is the best phone I have ever owned.
My biggest issue with SMS messages is that I've had up to a 3-4 minute delay between the timestamp on the message and when i get the notification. But AFAIK, I haven't lost any messages.
I think its a great phone so far. If Android keeps picking up as it appears to be, I think it can trump apple and iphone.
I have not lost any texts. I tested with texts to and from different carriers and area codes. I have not run any task killers. For what it's worth, I have not had any of the battery problems that people have run into either.
i had lost all of my SMS messages on my Sprint Hero after i installed Handcent SMS and used it for a couple days ( which so happened to be exactly a week after i bought the phone the messages were gone)
your sms's are still there, but they are in your messenger app, handcent doesn't access stuff that's already there, just the new stuff comming in. I don't belive it's possible to import the sms's that are already there, or at least there's not a known procedure on how to do so.
you can access them if you pull up your original messenger app, just no way to import/export. Sorry, probably not the answer you were looking for, but it is the correct one.
I had this problem when I first got my Hero, no text messages were being received, third party SMS app or not. My Hero said 'with Google' on the back. I exchanged it for one that just says 'htc', haven't had the problem since.
im worried
ive had the phone for 2 weeks.three days later i got the dreaded calls from friends and girlfriend that i havent been answering back to text. ive installed handcent sms and smstomailbox. from then on the problem has stopped.although i have sent myself some text and im yet to receive them no one has told me they cannot contact me. i just moved to sprint because i recently got a job as an assistant. my boss contacts me strictly through text. (you can imagine the magnitude of this issue) after all the forums ive read, i dont know what to do regarding this. my 30 days is almost up. i cant imagine a patch is not already on the works, but ive read this has been a known problem for some time. with Htc pumping out phones by the dozen and 1.6. / 2.0 updates taking the spotlight, i wonder if i should return my phone. the phone is real nice and i dont want a flimsy pre. seems too much stress for a device you pay good money for.i have the sprint hero with the "with google" in the back. seems like a bad time to get a phone with sprint since theres no news on wether this phone will be upgradeable or patched and the other phones are going to get upgraded soon. (HD2)
!!!
on another thread someone posted that the problem had been acknowledged . the post pointed to a flaw in the sms app that did not send a "memory full" notification back to the sms database server. so it seems theres a limit to the sms app capacity and it kinda locks down or something along those lines. lol (sorry ill post the link when i find it again) in other news 2.0 is coming to the hero. so i guess ill deal with the issues till then.
I purchased a Hero on launch day [early run device, without 'with Google' branding, only 'HTC' on the back cover] and quickly encountered the intermittent text message delivery debacle.
Bottom line, there were extended periods of time in which text messages being sent to me were simply not appearing on my phone. [Side note, this includes individuals both on and off the Sprint Network.] Turning the phone off and on usually alleviated the non-delivery / appearance problem but any messages sent during that time were gone. There was no flood of messages post restart.
I should note that on two occasions I did notice that I had received a text in the top notification bar but when I opened the Messaging App, the text was no where to be found.
It appears that the messages may indeed have been delievered... but the app is 'eating' them, so to speak. This *could* explain why on Sprint's end, everything looks fine on the network... or so I was told, which I believe.
My temp solution, as advised by forum / discussion posts by other Hero users was to install an alt Messaging App [I used Handcent SMS] and use this rather than the stock Messaging app. Additionally, I added 'SMS To Mail Lite' which forwarded a copy of my incoming texts to an email address. I experienced no intermittent outages / delivery failures / abductions at all. Both Handcent and the email inbox matched. While this 'worked' I was unable to replicate the bug but since I was using Handcent this might have been why.
Later, after spending some time on the phone w/Sprint Advanced Tech Support, they determined it was not a network issue and was due to the phone itself [as their system showed all my messages being delivered]. They set up a trouble ticket and I was able to swap my Hero for a new one at my local store. Caveat, I was still under the 30 day trial which made things much easier when I got to the store.
I was told by Advanced Tech Support that HTC has recognized this intermittent text delivery issue and they are working on a solution. I only mention 'Advanced' b/c the first individual I spoke with from regular Text Messaging Support had zero knowledge of this issue and was quick to deny any problems whatsoever. No one at the store knew anything about it either, but I wasn't expecting it. So if you speak with anyone at Sprint, expect that they might not know yet and be nice. You might even get a replacement phone.
Currently, I'm still using Handcent and really like it. Tried ChompSMS but just prefer the other. They're on par w/one another so be sure to check them both out if you prefer to go this route. Also, I used the 'My Backup Pro' app to restore my new phone to the original configuration. Certainly worth the $5.
Hope this helps.
I got my phone and am quite happy with it so far. I am on the Rogers network in Canada. Everything works great except that incoming msg are showing up 5 hours behind on the time stamp which throws off my sms threads as my msg time stamp correct on the way out.
So if I sent a msg at 9PM and they reply it shows there reply the same day but at 4PM of the same day? Any ideas why this is happening? It's happening from any number I get a txt from.
Thanks
Anyone having this issue or is it just me? I know this has been an issue in the past on various WM units but I'm not sure what the fix is with 6.5?
Anyone help please?
Hi.
Not sure how this connects to your problem, but usually (always) when i send text messages everything is datestamped correctly.
But when I use Phonelog to log my calls to calendar it is 5 hours off.
I have been bugging the developer for years now. But I am the only one who this happens too.
sad face.
My timestamps are exactly 5 hours behind. What developer are you trying to reach? What do you think the issue is? I think it must be a WM 6.5 issue or an network time issue? I've read about this before with other devices, just not 6.5 devices yet.
Anyone?
I'll do some more google research.
This app.
Every update he makes it still is 5 hours off.
Maybe u could give this app a try.
Great app. Barely works when it;s 5 hours off every time...
http://www.infinityball.com/phonelog
Somewhere there is a post on his site with me asking him to fix it.
It would be cool if there was a solution for all of us.
No other app does the funky time stamping...
Maybe this link will help you:
http://forum.xda-developers.com/showthread.php?t=527587
i dont have timezone diff but i got this issue
1st sms (i send him) my time show 12.00
2nd sms (his replY) his time show 11.50 on my mobile
mea his sms is infront of my sms as i only can sort by time or by name
end up if i sort the thread by using "sort by time" the whole thread went message..
as u know which is my send sms with his sms reply
no fix for this?
Got a friend from Starhub who had this issue on his Treo Pro. I'm not certain if the fault lies with Starhub or WM!
cannot be network as this is very standard.....
sms time stamp should use mobile owner time as timestamp..
i dont have this issue when i use on htc diamond
banton56 said:
I got my phone and am quite happy with it so far. I am on the Rogers network in Canada. Everything works great except that incoming msg are showing up 5 hours behind on the time stamp which throws off my sms threads as my msg time stamp correct on the way out.
So if I sent a msg at 9PM and they reply it shows there reply the same day but at 4PM of the same day? Any ideas why this is happening? It's happening from any number I get a txt from.
Thanks
Click to expand...
Click to collapse
Hey, I have the exact problem, I am also using Rogers, and I also got the 5 hrs off. That makes all the msg received on the top.
Hope someone could help.
try this
it may work
Usually...
More often than not, SMS time stamping issues are something to do with the network provider BUT sometimes, it can be how the phone's SMS software is talking to the network provider.
I had a Nokia N96 be +6hrs out while a Samsung with exactly the same SIM card in it and thus on exactly the same network/account setup etc, the time stamping was perfectly correct.
I updated the ROM on the Nokia to a newer version and the time stamping was perfect again.
I highly recommend anyone experiencing SMS time stamping issues to apply the HTC SMS hotfix that became available in the past few days.
i applied the latest HTC sms hotfix but it dont work for me..
already email HTC to see they have any suggestion a not.
my friend clock is faster/slower than my by few min but it euff to mass up the whole chat as u dunno which is your ans with his reply... (to what i know is basic on friend mobile clock not the network as i tested with 2 mobile)
but it actually shouldn't work in this way as it should basic on our clock to go
i had email to HTC and herre is their reply (i havent try yet.. later than try)
Thank you for contacting HTC.
With regards to your query, please be advised to try:
1) Go from settings->menu->all settings->connections->connection setup->select country and operator->ok to reconfigurate the SIM card service
2) press call key->menu->options->band->select the network connection type and GSM/UTMS mode according to the network provider's settings
If still no avail, we are quite sorry that you will have to backup all the personal data you have on your device though synchronisation or backup tool and perform a hard reset to re-install the whole system for your phone.
After a hard reset, the device is restored to its default settings-the way it was when you first purchased it and turned it on. Any programs you installed, data you entered, and settings you customized on your device will be lost. Only Windows Mobile software and other pre-installed programs will remain
To perform hard reset,
setttings->menu->(all)settings->system tab->clear storage
Thank you for your continuous support of our products and services. Should you require further assistance, please do not hesitate to contact us again.
We look forward to be of service to you again.
Best regards.
HTC
Hotline: 1800 238 7788
Service Hours : 8 am - 8 pm, Monday - Saturday (except Public Holidays)
i tested.. it not working
i give up.. i decide to disable htc messages
im also on Rogers with the HD2 but i found a fix for this.
I was having my SMS come in with -5 hours on them as well, but after applying this registry change everything is working out (You also need to Soft Reset before the changes kick in)
Just edit the registry and set the value to 0
HKLM\Software\OEM\PhoneSetting\TrustTimeZoneField = 0x00000000(0)
Sorry i cant find the original thread where I got this fix, so dont account me for the credit!
Hope this helps!
**EDIT
i found the thread, it was in the Kaiser forum:
http://forum.xda-developers.com/showthread.php?t=374956&page=15
Thanks/Credits to Dangerously.
Talking to HTC support by e-mail is like talking to babies or monkeys. I recently tried to report 3 bugs, the answer I got back was ridiculous, the support person obviously was not able to read, only giving one-line answers, that were totally beside the point. Replying did not make it better. Maybe they are using children in the countryside in China posting random standardized answers.
I have since sold my HD2 because without reliable SMS I cannot conduct business, and a company that are so incompentent that you cannot even file bug reports is not worth any of your money.
Also, the description to the SMS "fix" that has been published on their website, completely ignoring to tell what problems it fixes, makes me think they have employed some pretty incompetent people. Any company with the slightest bit of self respect knows that when they issue a patch of fix, they must tell what was wrong and what it fixes.
i dont have -5hr but the timestamp which send by friend is not match with me.. it seen like all reply sms from frienz are using their mobile timestamp rather than my...
Bakedbread said:
im also on Rogers with the HD2 but i found a fix for this.
I was having my SMS come in with -5 hours on them as well, but after applying this registry change everything is working out (You also need to Soft Reset before the changes kick in)
Just edit the registry and set the value to 0
HKLM\Software\OEM\PhoneSetting\TrustTimeZoneField = 0x00000000(0)
Sorry i cant find the original thread where I got this fix, so dont account me for the credit!
Hope this helps!
**EDIT
i found the thread, it was in the Kaiser forum:
http://forum.xda-developers.com/showthread.php?t=374956&page=15
Thanks/Credits to Dangerously.
Click to expand...
Click to collapse
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'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.