My cell phone operator is Vodafone hungary, but when I'm getting an incoming call, the system can not identify the caller from the contacts database.
My business gsm subscription has a problem. Incoming number format is "006" First 0 is flagged to "not grouped call". Second and third number is long distance prefix. In contacts, I store numbers in the international format (+36xxxxxxx). When I'm receiving an incoming call, it displays the caller's number (006xxxxxx), but not the caller's name!
With an another SIM card (another operator), it works well. It displays incoming number as (+36xxxxxx) or (06xxxxxx) (note: long distance prefix is 06-area code-phone number in hungary) and it indentifies the correct name!
Another cell phones such as Nokia, SonyErcisson, works well cause they are identifying the caller from the last 7 number. When first two number is 00 it does not indentifying my callers! I'm quite sad about this. Can anybody help me please?
Can anybody help me please?
Related
Hello everyone, I installed RUU_Excalibur_WM61_Kavana_080408_WWE on my phone and it is workig great. The problem I am having is that in my country phone numbers consist of only 8 digits fotmated XXXXXXXX or XXXX-XXXX y my contacts list BUT when someone calls me his/her name does not come up, instead I get for example: (XXX)XXX-XX because the caller ID format seems to be (XXX)XXX-XXXX (expecting an area code) So I never get to se de name of the caller, instead I get a poorly readable number. How can I fix this?
TIA!
LOL, Try Moving to America, where we use these style phone numbers!
TheMasta said:
Hello everyone, I installed RUU_Excalibur_WM61_Kavana_080408_WWE on my phone and it is workig great. The problem I am having is that in my country phone numbers consist of only 8 digits fotmated XXXXXXXX or XXXX-XXXX y my contacts list BUT when someone calls me his/her name does not come up, instead I get for example: (XXX)XXX-XX because the caller ID format seems to be (XXX)XXX-XXXX (expecting an area code) So I never get to se de name of the caller, instead I get a poorly readable number. How can I fix this?
TIA!
Click to expand...
Click to collapse
TheMasta said:
Hello everyone, I installed RUU_Excalibur_WM61_Kavana_080408_WWE on my phone and it is workig great. The problem I am having is that in my country phone numbers consist of only 8 digits fotmated XXXXXXXX or XXXX-XXXX y my contacts list BUT when someone calls me his/her name does not come up, instead I get for example: (XXX)XXX-XX because the caller ID format seems to be (XXX)XXX-XXXX (expecting an area code) So I never get to se de name of the caller, instead I get a poorly readable number. How can I fix this?
TIA!
Click to expand...
Click to collapse
Did you try changing your Regional Settings to match the country you're in ?
Store all phone numbers in international "+" format
The key is to store all your numbers in full international format.
+CCCAANNNNNNNNNN
where CCC is the country code, AA is the area code (omiting any leading zeros in most countries) and NNNNNNNNNN is the local phone number.
For ease of use in your address book, you can space the digits out, or add parentheses or dashes, as these are ignored at dialing/matching time. It makes the numbers easier to read.
Eg. +CCC-AA-NNNNN-NNNNN, +CCC (AA) NNNNN-NNNNN would be treated the same.
All GSM phones receive the complete international designation phone numbers on incoming calls - so it will match on the full number always.
Based on your SIM, and your country's dialing rules built into the SIM, it will also match on numbers that have no country code, but have a complete local area code (including leading zero if appropriate) and complete number. This is to allow it to match on non mobile phone originated calls. I believe it will assume your local country code based on your SIM, and apply the appropriate zero stripping rules to the received caller ID to create a fully qualified international number to match on.
This also takes all the guess work out of making calls should you ever roam into another country. For example, if you live in the USA and store a number for Ireland as 01135312345678 - this will work from the USA. But, if you travel to Ireland, where the international access code is not 011 - but rather 00 - that number will fail. Storing the numbers with the "+" prefix instead of the local international access prefix allows the SIM card to do the work. The SIM card registers on the roaming provider's nerwork, and "asks" that network how to dial a "+".
Finally, the presentation of the number on screen is just a factor of the application that is displaying it. If you use the international format for your numbers, they will successfully match, and will display the number in the format in which you have stored them in your address book. If they don't match, they will display using the default number interpreting logic of whatever ROM you have loaded. For most of us here, that would be the Brighpoint USA ROM or the T-Mobile ROM - both of which try to format numbers as USA style AAA-XXX-NNNN
Hope this helps
Thank you, I entered +COUNTRY_CODE in the phone settings call options and it is working now.
Thanks a lot!!
TheMasta said:
Thank you, I entered +COUNTRY_CODE in the phone settings call options and it is working now.
Thanks a lot!!
Click to expand...
Click to collapse
How to go the phone settings call option
Solved.
Hi,
Is there a way to have the incoming call display identify which number of a contact is calling - for example, I have two numbers in the same contact for someone, mobile and work. When she calls, it just says the person's name and photo , rather than Name - Work or Name- Mobile.
Short of splitting it into two separate contacts, do you know if displaying the 'type' (or number) is possible?
Thanks
It is showing the number for me. I have some contacts with 3 or 4 numbers in them.
People, here's the thing.
Here in Brazil, when a call is received, the caller number is sent to the phone in this format:
0 + area code (two digits) + caller number (eight digits)
For example, 0219236XXXX
My Galaxy Nexus gets this number and shows it in this format:
(21)9236-XXXX
This is one of the brazilian ways to present a phone number here, "(" + area code with two digits+ ")" + four digits + "-" + four digits. There are others, for example without the parenthesis (like this: 21 9236-XXXX).
The problem is that when I enter the call log to return a call, if I return it from an incoming call register, it works fine. But if I return it from an outgoing call register, the call is not complete because the number is not recognized.
It's hard to explain, I'll try to illustrate with steps.
- I receive a call from 0219236XXXX
- My Galaxy Nexus call log shows:
(21)9236-XXXX "call received" (a small blue arrow pointing down left)
- I enter call log and press that "call received" register
- The phone dials (21)9236-XXXX and the call is completed
- My Galaxy Nexus call log now shows:
(21)9236-XXXX "call made" (a green blue arrow pointing up right)
(21)9236-XXXX "call received" (a small blue arrow pointing down left)
- I enter call log and press the "call made" register
- The phone dials (21)9236-XXXX and the number is not recognized.
- But if I press the "call received" register, the number is recognized and the call is completed.
See what I mean? I guess that in an incoming call, the first '0' (zero) is there, but it's hidden. So when I dial from the incoming call register, although the number is shown (21)9236-XXXX, the dialed number is 0219236XXXX, which is a correct number to the network.
But when I dial from the outgoing call register, the number is shown (21)9236-XXXX and the dialed number is 219236XXXX. The '0' (zero) is discarded. Because of that missing '0' (zero), the number is not recognized by the network.
I don't know if this is a problem only with brazilian phone number format, or if it happens in other countries also.
Is there a way to fix this? Because of it, most of the times I have to edit the number before calling it.
Bump!
Anyone?
i don't know about in brazil,
here in uk, it works with no problem. it even tell you where the area of the number is from.
for example i just received a unknown insurrance call from
01515246303
it show in the call log
0151 524 6303
Liverpool
and i can dial back with no problem.
qwerp_ said:
i don't know about in brazil,
here in uk, it works with no problem. it even tell you where the area of the number is from.
for example i just received a unknown insurrance call from
01515246303
it show in the call log
0151 524 6303
Liverpool
and i can dial back with no problem.
Click to expand...
Click to collapse
Have you tried dialing back from the outgoing call register?
Phantom1275 said:
Have you tried dialing back from the outgoing call register?
Click to expand...
Click to collapse
yes, it dials with the 0 with it.
I have the same problem, nexus in Vivo carrier, everytime i try to dial last call it wont recognize the number, then i have to edit the number, its really annoying.
Yes i have a similar problem
Here is what i have noticed
Im in oman, country code +968, when im in my home country and dial a call to uae, +971 567 897070, the dialer shows 056 7897070.
What i think happens is as follows,
Since the location setting if english uk, the phone formats the numbers as per uk formatting. They use 10 digits as their numbers.
The ics reads and displays numbers in UK first every where. Im ginger bread, that formatting used to happen only while entering the phone number in the dialer, but it would read and display more than 10 digits while on the same UK setting.
My advice for the brazilian numbers, is change ur location to uk from usa if you are using english.
I hope they fix this bug
Sent from my Galaxy Nexus using XDA App
Number formatting problem
in iran my galaxy nexus have problem with number formatting too.
sometimes seprate the number (this format: +98 123 456 7890 or 0123 456 7890)*
but sometimes auto format not work (this format: +981234567890 or 01234567890)
or only seprate -with country code- numbers.
important, when i saved a number with one of formats and then my phone automatically changed his formatting to other format then my numbers shows like unsaved numbers (without name) in log, callin and text.
text, log, dial pad and new cantact page have this problem.
Y sgn automatically change formatting?
how i can solve it?
after resetting, default format is the first one (*).
Hi,
After I installed KingSense Custom ROM there is a strange problem which I couldn't solved.
Eg: If make a call from another mobile to SIM one " If that contact saved as 077XXXX21 " then its shows that exact contact on the screen. but If I make a call to SIM2 from same mobile since it has saved as "077XXXX21" it doeasn't shows exact person and it shows the incoming call as unknown ( 77XXXX21 ). which shows contact no without "0". Therefore I have to save 077XXXX21 and 77XXXX21 under same contact to receive calls from same person to any SIM to show the specific contact.
Earlier if I receive calls as +9477XXXX21 , 077XXXX21 or 77XXXX21 it showed the specific contact when receiving the call to either SIM 1 or SIM2.
What is the problem? Thanks
Hi All!
I have an OP3 device and I have an issue with caller ID to recognize my contacts saved.
I'm using the device in Argentina, and Argentina operators uses an additional prefix ("9") between country code and area code to indicate that the number is a cell phone.
Example: +54 9 11 4653 8373
This prefix is used to get a call to cell network. It is used to call from outside Argentina. So if you are in US, you must use the 9 prefix to make the call.
However, this prefix is not mandatory to make local call in Argentina and the operators remove the prefix "9" in the caller ID information when you receive an incomming call.
That is my problem!... the caller ID provided is: +54 11 4653 8373, but I have a lot contacts saved with the 9 prefix because I travel usually to outside Argentina. The result: No contact name information provided at incomming call...
I contacted my operator and Oneplus. It seems to be an issue with the original rom lunched with the OP3, because using the same operator in IOS device or Windows Phone device.
Any idea? suggestion or workaround?... I read some information about Android under Samsung device where this issue can be solved modifying the total bits to recognize in the caller ID...Is possible to make something similar process in OP3?
Thanks!
Add both versions of the number for all applicable contacts
have you found a solution to this? i'm on oneplus 5 and still happens, it didn't happen on my lg.
Saludos
danielg77 said:
Hi All!
I have an OP3 device and I have an issue with caller ID to recognize my contacts saved.
I'm using the device in Argentina, and Argentina operators uses an additional prefix ("9") between country code and area code to indicate that the number is a cell phone.
Example: +54 9 11 4653 8373
This prefix is used to get a call to cell network. It is used to call from outside Argentina. So if you are in US, you must use the 9 prefix to make the call.
However, this prefix is not mandatory to make local call in Argentina and the operators remove the prefix "9" in the caller ID information when you receive an incomming call.
That is my problem!... the caller ID provided is: +54 11 4653 8373, but I have a lot contacts saved with the 9 prefix because I travel usually to outside Argentina. The result: No contact name information provided at incomming call...
I contacted my operator and Oneplus. It seems to be an issue with the original rom lunched with the OP3, because using the same operator in IOS device or Windows Phone device.
Any idea? suggestion or workaround?... I read some information about Android under Samsung device where this issue can be solved modifying the total bits to recognize in the caller ID...Is possible to make something similar process in OP3?
Thanks!
Click to expand...
Click to collapse
Exactly the problem with my OP5T.
But I'm from Brazil and we use a two digits operator to call to outside of my local area.
Then my contacts are saved like this: 0 41 31 90000-0000 where 41 is the operator code.
If I receive a call the number identifier shows 031900000000 (without 41) and the name is not recognized.
Is it an OxygenOS problem, isn't it? Because I never had this kind of problem before.