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! )
Hi all,
I've got this problem on my Dev Phone 1 - the "From" number of any SMS I receive has a form of "+<countrycode><operatorcode><number>", instead of just "<operatorcode><number>" or "<number>". It doesn't get looked up in an address book because of this.
I've never had this problem with any other phone, and it's really annoying - most of the time I have no idea who sent me a message.
Thanks in advance
I'm not sure about the dev phone in particular, but T-Mobile has always recommended storing contacts in that format. Google may have taken the hint from them when they spec'd the OS. In that sense, it might not be a bug, but a feature.
beartard said:
I'm not sure about the dev phone in particular, but T-Mobile has always recommended storing contacts in that format. Google may have taken the hint from them when they spec'd the OS. In that sense, it might not be a bug, but a feature.
Click to expand...
Click to collapse
Thanks for replying.
Well, I tried storing the number with +<countrycode>. The result is that SMS senders are looked up correctly, but the incoming call caller doesn't get looked up now. So, it's "either SMS sender name, or Caller name" situation.
I tried it with sim cards from two operators (with different callers / senders), same results.
isn't it one of the main differences between US and UK firmware?
torrentss:
What country are you in?? filling in your profile, would help us without asking question like this.
What firmware are using? stock...modded?
Not sure if this thread helps but take at look HERE
Mikey1022 said:
What country are you in?? filling in your profile, would help us without asking question like this.
What firmware are using? stock...modded?
Click to expand...
Click to collapse
Sorry about that. It's Georgia (country, not the state), the operators are Geocell and Magti. I'm using stock adp1 firmware.
Maybe it has to do with operators using different formats for calls and SMSes.
The calling numbers are in 8<operatorcode><number> format, but SMSes come from +995<operatorcode><number> (I forgot about the leading 8 in the original post, sorry).
Note that my previous phone (Nokia N73), and every other phone I've used, and all of my friends' phones have absolutely no problems with that.
Mikey1022 said:
Not sure if this thread helps but take at look HERE
Click to expand...
Click to collapse
Thanks for the link.
The only place I could find a setting for a country was in google account settings (timezone and an optional country field). Didn't make any difference (I did a sync and reboot).
I found this link, but I'm not sure if it's related - maybe just an old Windows Mobile issue.
http://forum.xda-developers.com/showthread.php?t=344287
Thanks
very annoying
hi,
am having the same problem in here ...
sms'es include country code in the FROM field, whilst calls do not !
as a result if I want to have a contact to be rocognised to calls and sms, i need to add two entries - 1st with his number only, 2nd -> with the country code - ....
is there a way ( reg hack ) to make the phone remove the country code when receiving an sms, or the other way round ...
i have had no problems with nokia and SE phones before ... sms would still contain country codes, but for these phones , these two numbers would still be recognized and treated conveniently...
torrentss said:
Well, I tried storing the number with +<countrycode>. The result is that SMS senders are looked up correctly, but the incoming call caller doesn't get looked up now. So, it's "either SMS sender name, or Caller name" situation.
Click to expand...
Click to collapse
All my contacts are stored as +<country><number> and I have not had a problem with incoming calls not being identified. I am in the US using T-Mo. Phone also properly identified calls when I was using a different sim overseas. Looks like ymmv?
It was fixable in WM by going editing the registry key: HKLM\ControlPanel\Phone\CallIdMatch and changing the value to something like 7 or 6 instead of 8. Later on, HTC made it automatic by either grabbing the value from the provider or having a DB of presets for each country.
However, on Android, the problem still persists. More than 1 year later and it's still there, even on Android 2.2.
z_rudy said:
However, on Android, the problem still persists. More than 1 year later and it's still there, even on Android 2.2.
Click to expand...
Click to collapse
Actually, I haven't had this problem for quite some time now (I'm on cyanogen 1.6 now). Fixed some time when I switched to JF or Cyanogen, don't remember exactly.
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
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?
Hey guys, just like the SMS-time delay, my phone always says: PAYPHONE when I receive a call... I think it's Rogers' problem as well, but I don't know how to fix this... Anyone know how to fix this?
Thanks!
Gjm127 said:
Hey guys, just like the SMS-time delay, my phone always says: PAYPHONE when I receive a call... I think it's Rogers' problem as well, but I don't know how to fix this... Anyone know how to fix this?
Thanks!
Click to expand...
Click to collapse
I had the SMS issue, but someone on here pointed me to SMS Time Fix in the market which fixed it. It's a Rogers issue.
I am also getting Pay Phones (a call from Bell, and a call from Purolator). Maybe they throw in Pay Phone if it's unknown or blocked?
scorneil said:
I had the SMS issue, but someone on here pointed me to SMS Time Fix in the market which fixed it. It's a Rogers issue.
I am also getting Pay Phones (a call from Bell, and a call from Purolator). Maybe they throw in Pay Phone if it's unknown or blocked?
Click to expand...
Click to collapse
i realized it shows Pay Phone when the caller is NOT on the same carrier as me (ex: bell, telus, koodo...). I don't know how to fix this...
please if anyone has a solution to this, it would reaaally be appreciated! I can't see who's calling me!!
Gjm127 said:
please if anyone has a solution to this, it would reaaally be appreciated! I can't see how's calling me!!
Click to expand...
Click to collapse
I had the same issue with Rogers, there are two ways of solving it:
1) If you have an iPhone Value Pack, change it to a Generic Smartphone Value Pack.
2) If you have Name Display + Call Display, get rid of Name Display.
That should fix it.
SMS, I haven't figured out yet.
See the following thread for more information about why you get "Payphone" displayed all the time.
Pay Phone being displayed when receiving calls
As for the SMS issue, that is a Rogers/Fido problem wherein the SMS time stamp is offset by 4 or 5 hours. This is an issue when you use a non-Rogers phone as it will not have the fix for the offset.
Download SMS Time Fix from the market and set the offset correctly and it'll show the time stamp correctly!
Thanks a bunch guys, you were right on everything! Why is it that Rogers has this SMS delay? Btw, if I kill the SMS time-fix app, does it still do the job? Does it eat up too much space?
Gjm127 said:
Thanks a bunch guys, you were right on everything!
Click to expand...
Click to collapse
The Pay Phone on call display has been covered, but to sum it up it's an issue related to the fact that Rogers has NAME and number for call display, so when the name info comes across the phone, it doesn't understand so it simply displays Pay Phone instead of the number calling. Getting name display excluded from your package fixes the issue and call display works normally.
Why is it that Rogers has this SMS delay?
Click to expand...
Click to collapse
I don't know, but I'm guessing it has something to do with UTC timezone and their network.
Btw, if I kill the SMS time-fix app, does it still do the job? Does it eat up too much space?
Click to expand...
Click to collapse
The SMS Time Fix app by Matthew Precious is very small and uses almost no resources. If you kill the app it won't be running, so it can't fix the timestamp of messages when they arrive.
bfksc said:
The Pay Phone on call display has been covered, but to sum it up it's an issue related to the fact that Rogers has NAME and number for call display, so when the name info comes across the phone, it doesn't understand so it simply displays Pay Phone instead of the number calling. Getting name display excluded from your package fixes the issue and call display works normally.
I don't know, but I'm guessing it has something to do with UTC timezone and their network.
The SMS Time Fix app by Matthew Precious is very small and uses almost no resources. If you kill the app it won't be running, so it can't fix the timestamp of messages when they arrive.
Click to expand...
Click to collapse
Rogers technical support knows all about the name feature, they will quickly remove it for you if you call in. Mine is now working, no more Pay Phone.
whats a payphone
Would replacing the dialer with a 3rd party app from the market have any affect on this?
darklipslide said:
Would replacing the dialer with a 3rd party app from the market have any affect on this?
Click to expand...
Click to collapse
I've tried but it didn't resolve the issue.
Had this problem as well and I just fixed it by canceling name display. Another xda win
Sent from my Motorola Olympus
ChongoDroid said:
Had this problem as well and I just fixed it by canceling name display. Another xda win
Sent from my Motorola Olympus
Click to expand...
Click to collapse
I was considering cancelling name display but at the same time an update from motorola could be rolling out sooner than later, and I'd hate to mess around with my account for nothing