Related
I have an original ROM O2 (UK) XDA2. Last night, for the first time, I tried the poxy MMS thing. Someone sent me one which worked fine (eventually) and his number came through in the international format, i.e. +447123456789. I clicked reply and sent him a video back. It didn't arrive. (But I bet I still got charged for it :roll: )
When I clicked to reply to the incoming MMS, the number that was in the 'To:' box was 447123456789, in international format, but without the +, similar to what happens when selecting contacts for the SMS 'To:' field. So, I did some experimentation.
I discovered that MMS don't get sent if the phone number doesn't have the leading zero (for the UK market). International-number formats don't work, even if the number has the + at the beginning. So, if someone sends you an MMS and their number comes through in international format, you can't simply reply to it without editing the number to UK format.
Does anyone know whether any work has been done on this issue for the new official ROM update? Either to rework the number so it's correct to the international format, or to allow incorrect numbers to get through the system to the recipient even if it's in international format but without the +?
As far as I recall, numbers sent to sms recipients, keep the + bit in them (this is under the NEW ROM - for the older ROM you have to enter the plus yourself, depending on how you searched and entered the contact).
But for MMS, the + sign seems to be truncated when sending a message (again, this is under the new rom, but I recall this is the case from the older rom too???).
Nevertheless, the message still gets sent with it truncated though.
So if it was still in your Outbox, then the number format is NOT the problem, but a network one instead.
This is confirmable by the fact that if the + sign WAS the problem, the message would STILL have attempted to send, but you would have then got an error message instead.
This strongly leads me to believe that your problem, is a Network or GPRS one.
Certainly NOT a number format issue.
If the numbers are not of the right format, the symptom would manifest itself in the message trying to send, then an error message being shown.
Not what you have.
i did have this problem when replying or selecting a number from contacts to send a message too, it always don't include + sign even if its included in the contacts, the only 2 work arounds i found to solve this problem is either add 00 instead of + for me it was a night mare since all my numbers are stored in international format even local ones for raoming needs so the other option to avoid it is the type the name in the TO field & an auto continue will show you a list of contacts with the matching letters then choose it from their, only then it will send it correctly even it it has +, i think its an RSU issue or maybe Rom country selection issue because i noticed when it fails to send a message it reputs the contry code like the following +44207 wil be something like 44244207 & no matter where i searched to find where the hell it brings this original country code i couldn't find it
Rabia.
The + sign being omitted is a known bug on earlier ROM versions.
The latest ROM fixes this.
But this doesn't have any bearing on the OP's problem, in that for MMS, the software seems to drop the + in the address field anyway, but still manages to get through fine.
And if the problem WAS one of the number format, this would be shown in the form of an error message saying the message could not be delivered.
As the OP is not getting this, and the message seems to be just sitting in his Outbox, I suspect a completely different problem perhaps.
i have worked with operators because of my business nature & from my understanding also that someoperators will recognize the international codes without even 00 or + & some will not so here you go i got multiple problems to contibute in this :shock:
Shadamehr said:
As the OP is not getting this, and the message seems to be just sitting in his Outbox, I suspect a completely different problem perhaps.
Click to expand...
Click to collapse
No no, perhaps I didn't explain properly. As far as the XDA2 is concerned, the message has gone, but it never arrives at the destination. So the network is losing the MMS because it's not properly addressed, but it's only incorrectly addressed because of the MMS software on the XDA2.
Hope that clarifies it.
It would have done mate, were it not for the fact that as far as SMS at least are concerned, if you send a text to a number that is not valid, or incorrectly formed or laid out, you get an error message to tell you, and you say you are not getting an error message.
So let me test this with MMS and get back to you. If it generates an error message, then it shows it is not a number issue.
Er I CAN'T test it as such mate...
Becuase just as I thought, and mentioned in my posts, when I go into the contacts list to choose a recipient for an MMS, they ALL have the + sign removed from them.
My own number shows (changed slightly of course) as:
447866123456;
In the "To Phone" field.
But if I send, it gets through fine. As it does with other numbers.
Which was exactly my point - that with the MMS Software (and this does NOT apply to the SMS application, which is very different), the numbers always have the + sign stripped out of them, but they still send.
So if your numbers appear as 447899123456 etc then if you are in the UK there is no reason why they should not get sent, as I already said based on number format, as this is exactly what happens anyway.
The only thing I can then offer, if you are in the UK, is that you check your regional settings etc on the xda.
Failing that, then maybe its time for that ROM upgrade?
Strange one.
I figured it was a network problem, but wondered whether the source of the problem (i.e. the fact that the MMS Composer application screws up the number for me) had been fixed in the ROM update.
MMS msgs which don't have the + in front of the international code don't get through for me, and I can't send them with the + in front because the MMS Composer app strips it off, even when I add it manually to the number to which I'm replying. So all numbers must be of the national format, i.e. 07123456789 and I can't send MMS abroad.
So, has this 'bug' been fixed in the new ROM update?
sublimatica said:
I figured it was a network problem, but wondered whether the source of the problem (i.e. the fact that the MMS Composer application screws up the number for me) had been fixed in the ROM update.
MMS msgs which don't have the + in front of the international code don't get through for me, and I can't send them with the + in front because the MMS Composer app strips it off, even when I add it manually to the number to which I'm replying. So all numbers must be of the national format, i.e. 07123456789 and I can't send MMS abroad.
So, has this 'bug' been fixed in the new ROM update?
Click to expand...
Click to collapse
NO mate - because as I indicated, it is NOT a bug.
Whilst the MMS Software strips the + sign on the display, it must still SEND to the number with the + in, becuase all of mine get through, whereas, an SMS without the plus, as seen by the bug in SMS software that IS fixed in the new ROM, does NOT get through.
Let me make it clear, as I have obviously not in my last three posts...
There MUST be something else giving you trouble.
Becuase for me, saying it for the third time, with the + sign not shown, it STILL works. And I am in the UK just like you.
Shadamehr said:
...as I indicated, it is NOT a bug.
Click to expand...
Click to collapse
Please put your arrogance to one side for a moment, and stop SHOUTING certain words at me. There is a bug. The MMS software removes the + from the number for international-format numbers, even if I type it in manually to the number before sending. This is a bug. OK? :roll:
Shadamehr said:
Whilst the MMS Software strips the + sign on the display, it must still SEND to the number with the + in, becuase all of mine get through, whereas, an SMS without the plus, as seen by the bug in SMS software that IS fixed in the new ROM, does NOT get through.
Let me make it clear, as I have obviously not in my last three posts...
There MUST be something else giving you trouble.
Click to expand...
Click to collapse
I don't care about this. My testing has revealed one simple fact, as I keep trying to explain: when the phone number is in UK-format, with a leading zero, my MMS get through. When it's in a broken international number format, they don't. I want the software to send them with a correct international-format number so that they work. Thus, my question is: has the bug in the MMS Composer software which strips the + from international numbers been fixed with the new ROM update? (If you read above, you'll notice that this was the question I first asked... :roll: )
Shadamehr said:
Becuase for me, saying it for the third time, with the + sign not shown, it STILL works. And I am in the UK just like you.
Click to expand...
Click to collapse
Yes, but according to your profile, you're with Orange. I'm with O2, and they don't work. No error messages, no failure reports, nothing. Just silence. Can you please just believe me, or do you want to come to my house and I'll demonstrate to you?
I appreciate your attempts to help, but if I had wanted someone to treat me like an idiot I'd have asked for that. OK?
sublimatica said:
Shadamehr said:
...as I indicated, it is NOT a bug.
Click to expand...
Click to collapse
Please put your arrogance to one side for a moment, and stop SHOUTING certain words at me. There is a bug. The MMS software removes the + from the number for international-format numbers, even if I type it in manually to the number before sending. This is a bug. OK? :roll:
Click to expand...
Click to collapse
I'm SHOUTING cos you keep missing it. And now for the FOURTH time - it is NOT a BUG per se - got that - I'll say it again - NOT a bug per se, because having looked on a friend's XDA2, it does this for ALL, and yet works on his too. I'm sorry for shouting. If you LISTEN however, I can refrain from shouting. Let me be absolutely utterly and abundantly clear - I have no doubt you have a clear issue. What I am SHOUTING, and yet you keep ignoring, is that I am trying to tell you that the MMS Composer stripping the + sign out, is NOT the answer to your problems alone. Can I make that any clearer?
Shadamehr said:
Whilst the MMS Software strips the + sign on the display, it must still SEND to the number with the + in, becuase all of mine get through, whereas, an SMS without the plus, as seen by the bug in SMS software that IS fixed in the new ROM, does NOT get through.
Let me make it clear, as I have obviously not in my last three posts...
There MUST be something else giving you trouble.
Click to expand...
Click to collapse
sublimatica said:
I don't care about this. My testing has revealed one simple fact, as I keep trying to explain: when the phone number is in UK-format, with a leading zero, my MMS get through. When it's in a broken international number format, they don't. I want the software to send them with a correct international-format number so that they work. Thus, my question is: has the bug in the MMS Composer software which strips the + from international numbers been fixed with the new ROM update? (If you read above, you'll notice that this was the question I first asked... :roll: )
Click to expand...
Click to collapse
I DID notice it first time. You just didn't seem to see my answer for the THIRD time. Let me go one bette for you, I cannot answer the question as you phrase it, because, as I have said, it is NOT NOT NOT NOT NOT a bug, so how can I say if a bug has been fixed, if it is not a bug? Moreover, never mind the ROM update, I have downloaded and installed version 1.6.0.9 of the Arcsoft MMS software, and this is still there BY DESIGN - the ROM Update version is only to 1.6.0.8 - so TWO version updates do not alter this behaviour - which I would have expected if this was a bug.
(And as an aside, if you want me to send you a copy of the latest version, even newer that the ROM Update one, I happily will)
Shadamehr said:
Becuase for me, saying it for the third time, with the + sign not shown, it STILL works. And I am in the UK just like you.
Click to expand...
Click to collapse
sublimatica said:
Yes, but according to your profile, you're with Orange. I'm with O2, and they don't work. No error messages, no failure reports, nothing. Just silence. Can you please just believe me, or do you want to come to my house and I'll demonstrate to you?
Click to expand...
Click to collapse
I have an O2 SIM too, or in between your attempts to keep correcting me, did you not think I would try it? And as I also indicated, my mate has an O2 XDA2, and his works too. Not sure his ROM version though.
sublimatica said:
I appreciate your attempts to help, but if I had wanted someone to treat me like an idiot I'd have asked for that. OK?
Click to expand...
Click to collapse
When people keep constantly ignoring what people are pointing out to them, and better yet, even criticising them for SHOUTING becuase they are still being ignored, I COULD offer that tis is indeed exactly what you have asked for.
But in actual fact, i am very keen to try and help you, so I won't stoop down.
Once again, not knowing if you have already checked or not, can I suggest you check your regional settings.
Also, something else I noticed, is that using Outlook 2003, if I enter a number on the phone, the way I used to do it was like:
+44 191 460 1234 (for landline numbers with the gaps in just as you see them)
And +44 7899 123 456 for mobile numbers, again with the gaps just as you see them.
This nevertheless, still worked fine for SMS, and MMS.
Now that my trial of Outlook 2003 has ended, and I have re-installed Outlook XP, the earlier version, I now find, no matter what I do, that if I enter a number in the manner I prefer as above, onto the phone, when it syncs with Outlook, they appear as 44 (191) 460 1234 or 44 7899 123 456 in Outlook, and the same when sync'ed back to the phone, yet they still work.
Let me be absolutely clear however, the single only purpose for my post, which, in effect I am now saying for the fifth time, is that to the very best of my knowledge, and despite what you repeatedly think, and as backed up by testing with my O2 sim, and on a friend's phone, that as far as ArcSoft MMS composer is concerned, the appearance of numbers in the program's contacts list with the leading + stripped, whilst looking problematic, is actually NOT a bug, and for the rest of us, seems to work fine regardless.
I say nothing more than that.
Forget it. Can't even be bothered to read all that arrogance.
Do these forums have an ignore function?
Right then. Let me summarise, if only to give you an opportunity to shout at me again (even though I've been listening carefully all the way through this painful process). (I hope you're not a teacher.)
When I create an MMS using a number in the international format with a + at the beginning, the MMS Composer helpfully removes the + from the front of the number when I click to send it.
This 'special behaviour' of MMS Composer in stripping out the + symbol is not a bug. I'm not sure what one should call this, but you are absolutely clear that it's not a bug. It must be by design, huh? (Why would they design it this way, I wonder?)
Anyway, MMS messages sent by me in this way don't arrive at the destination. I get no error messages. As far as my machine is concerned, they have gone.
When you do the same thing, your messages get through.
You can't tell me why, or offer any useful suggestions for circumventing this problem. You can only keep repeating that I don't have a problem, this is a network feature, and that you're bored of telling me this.
Well thanks for your contributions.
Can anyone else help me with something useful?
(Shadamehr - keep quiet here. I don't need any more input from you right now.)
sublimatica said:
Right then. Let me summarise, if only to give you an opportunity to shout at me again (even though I've been listening carefully all the way through this painful process). (I hope you're not a teacher.)
Click to expand...
Click to collapse
You may have been listening - it's hellish clear you haven't been taking it in though.
sublimatica said:
When I create an MMS using a number in the international format with a + at the beginning, the MMS Composer helpfully removes the + from the front of the number when I click to send it.
Click to expand...
Click to collapse
Yes
sublimatica said:
This 'special behaviour' of MMS Composer in stripping out the + symbol is not a bug. I'm not sure what one should call this, but you are absolutely clear that it's not a bug. It must be by design, huh? (Why would they design it this way, I wonder?)
Click to expand...
Click to collapse
No idea, and I fully concur its daft - never once argued with you there.
sublimatica said:
Anyway, MMS messages sent by me in this way don't arrive at the destination. I get no error messages. As far as my machine is concerned, they have gone.
When you do the same thing, your messages get through.
Click to expand...
Click to collapse
Yes - exactly so.
sublimatica said:
You can't tell me why, or offer any useful suggestions for circumventing this problem. You can only keep repeating that I don't have a problem, this is a network feature, and that you're bored of telling me this.
Click to expand...
Click to collapse
Completely untrue you arrogant idiot - if nothing else I have indicated regional settings on the xda2 as one area to investigate, and written at length about the strange behaviour different from Outlook 2002/XP to Outlook 2003 - your arrogance and sheer falsitudes seem to know no bounds. It might not have been much, but it was a clear attempt to try to help. For Christ's sake, you'd think I was getting PAID for trying to help you, and not giving up of my time and effort for free to seek to help a fellow user.
Like I said, you arrogant swine - are you for real? And where the hell did I say you don't have a problem? You have an absolutely genuine one. All I ever said was that the MMS software stripping the + out is not the be all and end all cause of your problems. A fact which still holds true, and in its very own right is a VERY helpful piece of advice or information for you.
I am trying to tell you that what you see happen in terms of the MMS software stripping out the + sign is a situation that seems inherint for all UK users, and yet doesn't stop other people sending.
How the hell can you overlook that key fact, and tell me it's not an important piece of information for you or again overlook the fact that I am TRYING to help you?
On the contrary, I mentioned this way back in my first attempt to help you, but you completely overlooked it, and now have dug a fairly large hole for yourself, now that this fact is starting to sink in with you.
But instead of letting me take the shovel off you, and instead give you a (freely profered) helping hand out of the hole, you can do nothing but attack me, for trying to help you, and dig that hole much deeper for yourself.
I have done nothing but try and help, came out with a key piece of information, and came back time and time again to try and help more, and all you can do is treat me like cr*p. ? ? ? ! ! !
Well bonny lad, frankly, you are the biggest t*sser I have had the misfortune to come across, and if you think I'll hang around here for you to attack me more when I repeatedly give up my time to try and HELP you, you really do have another thing coming.
You can well and truly go to hell mate.
You sad sad soul
sublimatica said:
Well thanks for your contributions.
Can anyone else help me with something useful?
(Shadamehr - keep quiet here. I don't need any more input from you right now.)
Click to expand...
Click to collapse
Who the hell do you thnk you are to tell me that?
My advice to any would be helper to you now would be:
"Don't bother - you'll make time and effort to try and help him, and he'll treat you like a piece of cr*p for your reward"
Honestly - what colour is the sky on the planet where you live?
Get a life, and then look back at this event in embarresment. You should hang your head in shame.
:lol: :lol: :lol: Like I said, I didn't actually need any more input from you, Shademehr, but thanks for the laugh anyway.
Sensible suggestions from knowledgeable users on ways to solve my MMS problems (as opposed to just telling me the problem is unique and vaguely waving me in the direction of regional settings :roll: ) are still welcome - thanks in advance.
sublimatica said:
:lol: :lol: :lol: Like I said, I didn't actually need any more input from you, Shademehr, but thanks for the laugh anyway.
Sensible suggestions from knowledgeable users on ways to solve my MMS problems (as opposed to just telling me the problem is unique and vaguely waving me in the direction of regional settings :roll: ) are still welcome - thanks in advance.
Click to expand...
Click to collapse
You utterly arrogant moronic b*stard.
I've spent god only knows how long trying to help you, and offering to send you updated versions of the software to try out and see if that helps, and all you can do is take the p*ss and find it funny and say what a LAUGH it has been for you?
And then ask if ANYONE ELSE wants to try and help you too?
You think they want the p*ss taken out of them once they have spent ages trying to help you too?
Your not of this planet sunshine.
Thanks for the message saying "thanks for all the time you spent trying to help me shadamehr".
As if.
You f*cking d*ckhead - what an ungrateful arrogant b*stard.
Good luck. You're gonna need it.
mms problems
i am frightened to say this now, but..... i appear to have the same problem, the msg appears to leave me ok, it just never arrives. i havent managed to send any mms for the past month - 6 weeks since i changed from Nokia 6600 to XDA II.
Please don't be frightened, David - I'm not that bad, honest! :lol:
I discovered while testing again the other day that SMS messages don't get through for me either unless the number is perfectly correct (i.e. with the + included if in international format), so what I'm experiencing isn't limited to MMS. I guess it must be a network limitation.
I'm sure that other people reported that SMS do get through without the + attached when this bug first came to light last year. At least with SMS I get a warning that the message couldn't be sent.
I rarely close threads, but this one is closed.
I'm very busy this weekend, and have no time to read this whole thread to see who did what to whom.
Past experience has shown that text-based forums are not a good place to express feelings of anger and frustration. Please all realise that no matter how well we're doing presently, a community such as this is always more brittle and fragile than you'd expect.
Love, Peace & Happyness,
Peter
( dig it! dig it! )
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?
Hi everyone,
hoping that someone may be able to help me.
about 6 weeks after i got my phone i started having problems where in conversation mode i would reply to a message and it would go to another person in my address book (ususally the last person i had text'd). it wouldn't happen all the time but randomly.
I was on t-mobile but i upgraded the ROM (now 1.66) and tried doing a few hard resets. the phone would be ok for a little while then the problem would start again. because the phone is now past its month i can only get a repair. t-mobile don't know that i have upgraded the rom (i had to use hspl to do it) and htc said because i have upgraded the rom i've now voided my warranty.
anyone heard of any fixes or am i stuck with a phone that doesn't work so great for the next 15 months? (i've had the phone now 4 months and have been trying to deal with this problem for about 2.5 months now)
i've probably left out some vital information, if so my apologies.
thanks.
edit - if you have a moment to spare, could you test for this bug. DeadVirus has suggested a way to recreate a problem (post #14) that is being experienced by a few. thank you.
try flashing a 2.01 or higher ROM.
It was this problem which made me sell my HD2. I have only seen two other people, including yourself, report the issue here. Changing ROMs didn't seem to help, although I didn't try 2>
thanks both for your suggestions.
Can I ask sunking, why you didn't think of going down the repair or replace route?
I'm considering removing the flashed rom and seeing what t-mobile can do.
jeane said:
thanks both for your suggestions.
Can I ask sunking, why you didn't think of going down the repair or replace route?
I'm considering removing the flashed rom and seeing what t-mobile can do.
Click to expand...
Click to collapse
I did, the handset was replaced three times but to be fair the SMS misdirection bug was so random and intermittent that although it hadn't shown up on the third handset, by this time I had lost all faith in the device. The volume was extremely loud anyway, even on the minimum setting so I returned the handset. It's a shame because I do miss that screen and the browsing capabilities.
I have this problem too! Any solution? It's anoying!!!
the only work around i have read that works is to just text from traditional mode. it's ugly and the spoilt child in me doesn't want to accept that but it's a short term fix.
have you spoken to htc? when i called them, they said they were unaware of such a problem.
jeane said:
the only work around i have read that works is to just text from traditional mode. it's ugly and the spoilt child in me doesn't want to accept that but it's a short term fix.
have you spoken to htc? when i called them, they said they were unaware of such a problem.
Click to expand...
Click to collapse
I've just sent them an e-mail.
I hope this gets fixed soon!
WOW!!! that is worse than the msgs act. not being sent..it really is. i havent had this prob as yet (touch wood)...as much as i love this phone but that could have been the final straw for me to dump it.
I had the same problem. Phone is crap (firmware) in my opinion, I'm sure the fanboys on here will disagree.
One thing that I had notice, there are two registry values, LatestPhoneNumer and SelectedPhoneNumber in [HKLM\Software\HTC\HTCMessaging\Menu]. When the phone is about to send a message to the wrong number (you can check by doing "Menu->Send options" on while writing the sms), the SelectedPhoneNumber is with the wrong phone number, while the LatestPhoneNumber is with the correct one...
I think that the fact that SelectedPhoneNumber storing the wrong number is causing this stupid problem.
DeadVirus said:
One thing that I had notice, there are two registry values, LatestPhoneNumer and SelectedPhoneNumber in [HKLM\Software\HTC\HTCMessaging\Menu]. When the phone is about to send a message to the wrong number (you can check by doing "Menu->Send options" on while writing the sms), the SelectedPhoneNumber is with the wrong phone number, while the LatestPhoneNumber is with the correct one...
I think that the fact that SelectedPhoneNumber storing the wrong number is causing this stupid problem.
Click to expand...
Click to collapse
i think you've definitely pin pointed the place where the problem is occuring. would you mind if i copied your message to send to htc?
i wouldn't mind if i needed to check before each text but where is Send Options? are you in conversation or traditional mode? have you already typed a message. i can't seem to find it under menu. all i get is insert, quick text, delete, discard, text size, recipient phone number (which is greyed out in conversation mode) and all messages.
sorry for the stupid question.
if you can solve this i'll name my first born after you. that's right, i'll name them deadvirus.
jeane said:
i think you've definitely pin pointed the place where the problem is occuring. would you mind if i copied your message to send to htc?
Click to expand...
Click to collapse
I have already sent a mail to HTC, but you can do the same (more people, faster fix).
jeane said:
i wouldn't mind if i needed to check before each text but where is Send Options? are you in conversation or traditional mode? have you already typed a message. i can't seem to find it under menu. all i get is insert, quick text, delete, discard, text size, recipient phone number (which is greyed out in conversation mode) and all messages.
sorry for the stupid question.
Click to expand...
Click to collapse
Sorry, it is "recipient phone number" and only works if you are in threaded mode (sometimes). I've translated it from my language and I thought that it was Send Options... sorry.
jeane said:
if you can solve this i'll name my first born after you. that's right, i'll name them deadvirus.
Click to expand...
Click to collapse
Don't do that! Poor kid! XD
workaround?
I think I have found a workaround!!! It seems that if you use the Back hard button to get out of the contact message conversation window, the problem does not occur!
So, I think that the problem can be reproduced by doing the following (only in threaded mode):
1 - Open the Messages inbox;
2 - Open one contact and tap on the write area;
3 - Tap on Menu then Recipient phone number and check if the correct number is selected (It should show a small ball on the right side of the number). If the option is grey then wait a second and try again. If it's still grey it means that the contact only has one number associated and it is the one that is used for the next sms.
4 - Tap on Menu then All Messages;
5 - Open another contact (different from the first) and tap the write area);
6 - Tap on Menu then Recipient phone number and check the number. If there is no green ball (and the option is not greyed out) it's the bug!
You can do all the steps above, but using the Back hard button instead of the All Messages screen button (in step 4) to check if the workaround really works.
Give some feedback please...
EDIT: Using the Back Key also seems to solve the other bug about sms being loaded in background and covering the writing area!
No one can test this?
sorry dv, i wasn't notified of a response to the thread.
ummm... i'm trying to reproduce the problem but it is not happening for me. recipient phone number is always greyed out for me.
i suspect the problem occurs for me when there is a lag when switching between recipients on screen. it's like the information isn't re-written in the registry (as you suggested earlier).
my latest with htc is that i have been instructed by the email support to call htc helpline. will call next week and let you know.
jeane said:
sorry dv, i wasn't notified of a response to the thread.
ummm... i'm trying to reproduce the problem but it is not happening for me. recipient phone number is always greyed out for me.
i suspect the problem occurs for me when there is a lag when switching between recipients on screen. it's like the information isn't re-written in the registry (as you suggested earlier).
my latest with htc is that i have been instructed by the email support to call htc helpline. will call next week and let you know.
Click to expand...
Click to collapse
Sometimes I have to open "Menu" two or three times before the option appears available...
DeadVirus said:
Sometimes I have to open "Menu" two or three times before the option appears available...
Click to expand...
Click to collapse
no, even trying a few times, it remains greyed out.
i have recently deleted all my messages. i remember it happens when i have a few hundred messages saved. do you think that may have something to so with it? perhaps a regular deletion might avoid it having a conniption?
jeane said:
no, even trying a few times, it remains greyed out.
i have recently deleted all my messages. i remember it happens when i have a few hundred messages saved. do you think that may have something to so with it? perhaps a regular deletion might avoid it having a conniption?
Click to expand...
Click to collapse
I don't think so... I have had it with a few messages in the box...
Have you tried to test it with two contacts with more than one number each?
DeadVirus said:
I don't think so... I have had it with a few messages in the box...
Have you tried to test it with two contacts with more than one number each?
Click to expand...
Click to collapse
no, i'm afraid don't have any contacts with multiple numbers attached to their names.
Hi there,
Not sure if this is the right place to be asking this question but i'll give it a try.
I am running handcent on my incredible for handling my sms, I have this odd problem where handcent just stopped recognizing messages from one of my contacts. Is there anyway to get it to start recognizing it again?
This happened to me back in june and I ended up resetting the phone to get it back working again. I really don't want to do that. My phone isn't rooted or anything so everything on it is stock. any suggestions would be great.
I had a similar issue once and it was caused by the area code. I didn't have it listed as part of the number for my contact, IIRC.
rfarrah said:
I had a similar issue once and it was caused by the area code. I didn't have it listed as part of the number for my contact, IIRC.
Click to expand...
Click to collapse
I do have the area code listed, i also tried deleting the contact from my phone and recreate it.
Could you have possibly "blacklisted" the contact? If so, none of the SMS's will show up in the main screen until you Check off "Show Blacklist" in settings under Security and Privacy.
That's what it was. i have not idea how he got on my black list, looks like i had a few other contacts black listed as well. Figures it was something so simple.
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.