SMS comes with a country code

[torrentss]

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

 

[beartard]

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.

 

[torrentss]

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.

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.

 

[xeye]

isn't it one of the main differences between US and UK firmware?

 

[Mikey]

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

 

[torrentss]

What country are you in?? filling in your profile, would help us without asking question like this.
What firmware are using? stock...modded?

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.

Not sure if this thread helps but take at look HERE

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

 

[N1T15H]

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...

 

[jashsu]

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.

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?

 

[z_rudy]

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.

 

[torrentss]

However, on Android, the problem still persists. More than 1 year later and it's still there, even on Android 2.2.

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.