[Q] A contact bug on 2.2 froyo. - General Topics

Hi, I just realized there is a minor bug with android contacts.
Chinese mobile phone number, no matter whether it is wcdma, cdma, cdma2000 or gsm, are consisted of 11 digits. If I have two contacts with last 8 digits identical, then no matter I am calling out or receiving calls, the name appears on the screen were exactly the same despite the first 3 digits are different.
Making an example, if person A's mobile number is 13912345678 (number begins with 13 is a typical GSM number) and saved in my contacts, and I am calling 18912345678 (which is a WCDMA number), person A's number will appears on screen instead of the name of the latter.
Furthermore, if you click person A's name in your address book, a notification will pops out saying that you have two people having the same number and suggest you to merge these two guys.
Based on discussion from Chinese android forums, an guess of the theory behind this phenomenon is the phone only distinguish people from their last 8 digits of their numbers. Therefore, the address book might works fine within those countries who have less than 8 digits for their mobile numbers, but this cause troubles for people who have a number that is more than eight digits.
Anyone have idea how to fix this?
Cheers,
and by the way, please excuse my poor English

Related

Contacts not recognized while calling

Hello!
I have quite a strange problem. It appeared after I updated my Polaris to Windows 6.1 and the radio to the newest one. In general, I am really satisfied with the new sys, however there is one problem: telephone calls are not recognized basing on the contact list (which I imported using sprite backup).
It means that even though I have e.g. PersonX with telephone number 1234567 in my contacts, when I receive a call from him there appears the telephone number only (it is not changed into the "PersonX"). Have any of you ever had such a situation? I would be grateful for any suggestions how to solve it...
Best regards,
Theriel
Do You have only one contact with the same number? Not doubled - one in Phonebook and second with the same number on SIM?
Or if you have same contact under different names with the some number two or more times...
Joe Pesci with number +1-555-5555 and
Joe's house with number +1-555-555 and
Pesci, Joe with number +1-555-555
will confuse any mobile phone, and device will write only number. Check toroughly your contacts for duplicate numbers...
Nope, they are not doubled, and there are no contacts on the SIM. There is however another difference that appeared (I do not know if it has anything to do with the problem but...): previously I had all the contacts in the form:
"Johnson, Mike".
Now I have everything in the form "Johnson Mike" - there is no comma. But I am not sure if it tells you anything (maybe just a cosmetic change between roms?)
What is interesting - I can normally call using the contacts list (even from the "Phone" window) - they appear there properly.

[Q] Caller ID Madness

Hi folks,
I am trying to figure out the best way to store numbers in the phone app.
I usually store the number as 01234567890 with the leading zero so that I can call the number from anywhere in the country.
The network operator sometimes sends the caller ID as +11234567890 which is the international format. Windows phone fails to match this with the contact in my phonebook. I want it to match only the last ten digits of the number. My old dumbphone was doing this straight out of the box.
Am I missing something or does the Windows Phone 7 phone app just not support this?
Best Regards,
Gowtham
If you're in the US (I assume so, since you have country code of 1) then you might as well just store the number with the leading 1 (or +1 if it's really needed, but it shouldn't be). I have some number stored without the area code, some with area code but no country code, and some with both, and it seems to work out. A leading 0 is probably confusing the phone though.
I am based out of India at the moment. It is standard procedure to put in a 0 to call mobile phones located in a different state in our country.
After a soft reset and sync, my phone seems to function properly for now.
I'll post updates if I discover anything else.

[Q] 7 digit dialing?

Whenver I dial with 7 digits, the phone does not recognize the contact entry. I'm pretty sure that my previous phone (iPhone 4s) would recognize 5551234 as the same as 123 555 1234 and know my contacts name. At least it did with my home area code, probably not for numbers outside my area code.
This phone just calls it unknown. Is there a setting for this I can adjust to dial with 7 digits?
Nope. Sorry
i called tech support about the same thing. I'm coming from t mobile. had to ad my area code to majority of my contacts...sucks. Another thing i miss is t-mobile had caller id with name for numbers not in your contact list. Worked like land line caller id. with ATT we're stuck with just the number It seems like those types of things would be easy to implement features..
nugzo said:
i called tech support about the same thing. I'm coming from t mobile. had to ad my area code to majority of my contacts...sucks. Another thing i miss is t-mobile had caller id with name for numbers not in your contact list. Worked like land line caller id. with ATT we're stuck with just the number It seems like those types of things would be easy to implement features..
Click to expand...
Click to collapse
its the provider issue...
if you put your local tmo sim into your HOX, you could still enjoy the 7 digits calling feature

[Completed] Unwanted texting prefixes and "Yi Dialler" prompts before making calls.

Hello all,
I'm unsure about where to post this issue I am having with my handset. Let me explain a little about what is going on, and maybe someone can redirect me to where I should post the full details and hopefully get some answers
Have a Huawei C8813 Handset from China. It was payment for a computer job I did some time ago. I suspect it was a contract phone of some description, however it was completely wiped when I received it.
I had to perform some build prop edits in order to get it working on 2 Degrees here in New Zealand. These involved (ro.cdma.home.operator.numeric=53024) and other related lines.
The issue I am having at the moment is that when I receive calls from other cellphones in New Zealand, they come through with no International prefix (this is fine, and desired). However text messages I receive from NZ cellphones come through with the International prefix. So if I were to receive a call from 022022022, it would come through as such, but a text message from the same number would appear on my handset as +6422022022. This causes me to attempt to enter both the prefixed and non prefixed numbers into every entry in my address book. Text messages will send fine to either the prefixed or non-prefixed number, but this causes message thread separation (undesired).
Further to this, if I make calls to a non-International-prefixed number (a local New Zealand cellphone) eg 022022022, I get a dialog up titled ""Yi Dialer" (China +86)" with the following options: "Call China (International Roaming Call)", "Call China (**133 call back)", "Call other country", "Call local". Obviously the call goes through fine if I select "Call local". However, if I put the international prefix in front of the number for NZ (+64,) calling a number in NZ, it bypasses "Yi Dialer" altogether and just makes the call eg: +6422022022.
I have searched the internet far and wide and can find very little related to "Yi Dialier" (or "easy dialer" if translated from Chinese). I have checked out all of the stock applications that came with the phone and none appear to be related to dialing.
I am interested in perhaps a build.prop or similar setting that may erase this issue and make the phone believe it is based in New Zealand. As far as I can work out, the handset thinks it is roaming all of the time, when in fact it is not. There is no convincing it of this through regular Android settings with regards to the carrier or cellphone network.
Any help or direction with this would be greatly appreciated. I am happy to provide screenshots and exact build.prop edits I have done to make the phone operate here in NZ.
Thanks in advance,
Mike
MikeNZd4d said:
Hello all,
I'm unsure about where to post this issue I am having with my handset. Let me explain a little about what is going on, and maybe someone can redirect me to where I should post the full details and hopefully get some answers
Have a Huawei C8813 Handset from China. It was payment for a computer job I did some time ago. I suspect it was a contract phone of some description, however it was completely wiped when I received it.
I had to perform some build prop edits in order to get it working on 2 Degrees here in New Zealand. These involved (ro.cdma.home.operator.numeric=53024) and other related lines.
The issue I am having at the moment is that when I receive calls from other cellphones in New Zealand, they come through with no International prefix (this is fine, and desired). However text messages I receive from NZ cellphones come through with the International prefix. So if I were to receive a call from 022022022, it would come through as such, but a text message from the same number would appear on my handset as +6422022022. This causes me to attempt to enter both the prefixed and non prefixed numbers into every entry in my address book. Text messages will send fine to either the prefixed or non-prefixed number, but this causes message thread separation (undesired).
Further to this, if I make calls to a non-International-prefixed number (a local New Zealand cellphone) eg 022022022, I get a dialog up titled ""Yi Dialer" (China +86)" with the following options: "Call China (International Roaming Call)", "Call China (**133 call back)", "Call other country", "Call local". Obviously the call goes through fine if I select "Call local". However, if I put the international prefix in front of the number for NZ (+64,) calling a number in NZ, it bypasses "Yi Dialer" altogether and just makes the call eg: +6422022022.
I have searched the internet far and wide and can find very little related to "Yi Dialier" (or "easy dialer" if translated from Chinese). I have checked out all of the stock applications that came with the phone and none appear to be related to dialing.
I am interested in perhaps a build.prop or similar setting that may erase this issue and make the phone believe it is based in New Zealand. As far as I can work out, the handset thinks it is roaming all of the time, when in fact it is not. There is no convincing it of this through regular Android settings with regards to the carrier or cellphone network.
Any help or direction with this would be greatly appreciated. I am happy to provide screenshots and exact build.prop edits I have done to make the phone operate here in NZ.
Thanks in advance,
Mike
Click to expand...
Click to collapse
Hi, thank you for using XDA assist.
There is a general forum for android here*http://forum.xda-developers.com/android/help*where you can get better help and support if you try to ask over there.*
Good luck.

Having Problems with Carrier Switching?

Starting about 8 weeks ago after owning the phone for more than 2 years, I started missing calls and texts that would only show up after a reboot. People also told me that when they called sometimes, there was no connection and no way to leave a voicemail.
People are usually still 7-digit dialing and texting here. I live in New Mexico and most of the the state is 505 since forever, so people here never think of 10 digit dialing unless it's out of state. After about 5 hours with 2 different Fi tech chats and some research and experimentation, I figured out that when my phone was switching to Sprint, it was getting a "shadow" number with a 214 area code, which is Dallas. When on TMO everything works fine but if it switched to Sprint, I would miss a lot of stuff, and with 7 digit dialing be calling Texas, or sometimes getting notice of an invalid number, and sometimes I couldn't connect to the network at all.
From a reddit thread https://www.reddit.com/r/ProjectFi/c...ile_on_sprint/ that has some other interesting info which seems plausible:
"I think it's because of your Sprint Shadow Number; on Fi, Sprint and US Cellular assign an "invisible" internal number to you so that the towers are able to know who you are, as well as routing your calls properly, among other things. When you dial a 7 digit number, the area code of your phone number is appended to the beginning of the number, that's why they work fine when you dial a local number. However the Sprint number is often times not a local number, and the area code usually differs greatly from that of your actual Fi number, so the 7 digit number is now trying to call somewhere else, probably a number that is invalid."
The codes used to monitor and force a switch to a specific carrier might be google-able, though I haven't found them just yet (I got them from the chat) but using an app called Signal Spy or FiSwitch one can easily monitor and force a switch to a specific carrier without having to memorize and enter the codes, though the codes are available through those apps. Also reading the mountain of reviews you'll see how many people are having problems with Fi carrier switching choices.
I turned off my network reporting in the Fi app and have the Signal Spy app running and so far haven't had any switches to Sprint, though I don't know if that has anything to do with it. I don't know why this just started happening and they couldn't or wouldn't explain it. They just told me, from Bangalore or wherever, to just 10 digit dial, but that doesn't help when people frequently 7-digit dial or text me here. It's New Mexico!
What I've been looking for is a code to lock it on a carrier but haven't figured it out yet, though there to be a possibility here on this page which has a pretty exhaustive list of the codes but none of the codes used through my chat with the Fi tech to reveal connected carrier, change to T-Mobile or Sprint, or repair the network are on any of the lists I've seen so far! They are in those previously mentioned apps, though:
https://mobilespecs.net/phone/codes/...gle_Pixel.html
After 2 years of flawless, stress-free usage and glad to be away from the gouging and control of the major carriers, my Fi bubble has burst. Anybody else having Fi heartburn?

Categories

Resources