The issue only happens while I activate 'Enhanced 4G LTE Mode'. If a Caller doesn't use VoLTE or has extension numbers, Call log is misrecorded. It records caller's number + my number(2~3times). if caller's number is 12345678 and my number is 87654321 then, Call log records this to 123456788765432187654321(too long...) so Contacts cannot match the numbers. Some devices or other builds of Custom OS(include LinageOS, ArrowOS) have the same issue even in Incoming call info. This make hard to verify the caller.
The issue has been a long time in Korea. I think It only happens in Korea. Because I didn't find the info about this in forums outside of Korea. but In Korea. It is popular.
The issue is never happened in commercial roms(MIUI, OneUI, etc...) but, Many of AOSP based roms have the issue. I tested 7~8 custom roms that can be found in XDA. but even CAF version of Pixel Experience has the issue. So It is a AOSP bug rather than Linage's. But I hope This would be fix in ArrowOS
ex) Korean telecom vendors are SKT, KT, and LGT
Related
Hi,
I bought a T-Mobile HTC 8X in the US, unlocked it and brought it back with me to Israel. Now, when Israeli contacts call me, their numbers appear as (for example) 050 555 5555. When they text me, the number shows up as +97250 555 5555. For some reason the phone isn't able to tell that those two are the same number. I couldn't find anything while looking through the settings. I tried playing around with regions and all and came up with nothing. My old AT&T Focus had no issues and my dad's British 8S is working fine as well.
If I remember correctly, In WP7 deivces there's a registry setting which allows to control how many digits from the right identify the number as unique. However, I couldn't find a registry editor for the 8X (is there any?) so that information won't help me right now.
So now, my caller ID function sucks and the only way to actually ID contacts is to save 2 numbers for each one... really frustrating.
Does anyone know how to fix this?
Thanks!
Eyal
HTC support emailed back
And after sending them my IMEI they said that unfortunately there's nothing they can do and T-Mobile phones show that symptom in places like Israel and Europe.
So, it's either selling it on ebay or waiting for a registry editor or flashing it with a new ROM somehow. Option #1 seems like the most realistic one at the moment. This really sux.
Eyal
eyal453 said:
Hi,
I bought a T-Mobile HTC 8X in the US, unlocked it and brought it back with me to Israel. Now, when Israeli contacts call me, their numbers appear as (for example) 050 555 5555. When they text me, the number shows up as +97250 555 5555. For some reason the phone isn't able to tell that those two are the same number. I couldn't find anything while looking through the settings. I tried playing around with regions and all and came up with nothing. My old AT&T Focus had no issues and my dad's British 8S is working fine as well.
If I remember correctly, In WP7 deivces there's a registry setting which allows to control how many digits from the right identify the number as unique. However, I couldn't find a registry editor for the 8X (is there any?) so that information won't help me right now.
So now, my caller ID function sucks and the only way to actually ID contacts is to save 2 numbers for each one... really frustrating.
Does anyone know how to fix this?
Thanks!
Eyal
Click to expand...
Click to collapse
Actually, if I remember correctly from my previous experience with unlocked phones, most true Caller-ID (where the phone can identify who is calling even if they AREN'T in your Contacts list) requires XML code embedded in the phone (somewhere, don't ask me where) by the provider. Some providers use the same frameworks, so it's possible to get it working from network to network, but in most cases no.
I've never seen a situation tho, where it couldn't pick up the name from the Contacts list, based on the number coming in. I seem to remember you can turn on a feature called "International Dialing Help" that might bring them both together. OR put the entire phone number in your contacts. (As it is displayed when it comes in on Text).
drtolson said:
Actually, if I remember correctly from my previous experience with unlocked phones, most true Caller-ID (where the phone can identify who is calling even if they AREN'T in your Contacts list) requires XML code embedded in the phone (somewhere, don't ask me where) by the provider. Some providers use the same frameworks, so it's possible to get it working from network to network, but in most cases no.
I've never seen a situation tho, where it couldn't pick up the name from the Contacts list, based on the number coming in. I seem to remember you can turn on a feature called "International Dialing Help" that might bring them both together. OR put the entire phone number in your contacts. (As it is displayed when it comes in on Text).
Click to expand...
Click to collapse
I tried saving the entire number, but because local Israeli numbers get an extra "0" the phone is not able to ID them. Local call comes in as 050-5555555. SMS, like an intl. call, comes in as +97250-5555555. The "International Dialing Help" really helps when you're dialing. I thought it would fix the caller-id issue but it doesn't.
I spoke with HTC and with WP8 support on twitter. It's a known issue for T-mo phones and according to WP8 support, it has been forwarded to the appropriate team which probably means it'll be fixed in months to come. Until then, the only option is to get the phone flashed by one of the Israeli carriers with the Israeli version of the OS.
Let's say I have a fixed line phone, say 2xxxxxxx1. I have set this phone to forward all calls to my Moto G, say 9xxxxxxxx2. Now whenever I receive a call that was forwarded, I see two numbers in the caller Id. Say the original caller was 9xxxxxxxx3, then I see the caller id as 9xxxxxxxx32xxxxxxx1, i.e. the actual caller's number, appended by the number that forwarded the call to me.
I understand this can be a great feature to know the actual caller and the forwarder. But, it does not go well with the contacts and apps like True Caller. Also It becomes a pain to quickly save the received call to contacts.
Is there a way I could completely get rid of the forwarder's details from the caller id? Does it happen on all android phones? Is it specific to Moto G, or the OS it is running? Can it be carrier specific? Does anybody know an app that could override the default phone app and provides what I want?
PS: I am having a Moto G Dual Sim in India, running one SIM on Loop carrier, same issue when I tried a Tata carrier. The fixed land line that forwards to my Moto G is run by MTNL
original post: http://android.stackexchange.com/questions/65917/caller-id-for-forwarded-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.
Hey guys,
i have been searching everywhere for this but I haven't found solution, perhaps some of you guys might know something about this.
I have a Galaxy S6 920K, it is a Korean model which I am using in Canada as I bought it used here on craigslist. My issue is that no matter what rom including stock I have, no matter what CSC I have. The call waiting doesn't work, for example I am on call # 1 with someone and someone else, caller # 2 calls me, the call # 1 will disconnect while caller # 2 will have a regular ringing, but I never receive call from caller # 2 unless he leaves voicemail which I get notified. While caller # 2 is calling, the initial call # 1 disconnects automatically, hence I get disconnect from call # 1 and I don't even know I had call # 2.
As a temporary solution, I have disabled call waiting so that way my calls don't disconnect while someone else is trying to call me.
Conference call is same, if I am on call and want to add someone else, as soon as I dial the new number to add and call, the call would disconnect and while the initial caller will get that "hold" tone and I never get to speak to caller # 1 unless he disconnects and I/him calls me back.
1. The features are included in my plan, so it's not a provider issue.
2. I tried with friend's simcard who is with different provider and had the same issue
3. I know like many features are different in Korea, such as Shutter sound cannot be turned off on Korean phones, so I am not sure if these non-callwaiting/conferece features are due to restricted MODEM of this phone. I can't change modem to other modems as it gives me unknown baseband
Thank you for your help, looking forward for some explanation or solution
Anyone?
I got exactly the same problem with S8+ I bought in S.Korea and using in Israel. Have you had any success resolving this issue?
i have same issue in s8+ rom in g920k s6
No I didnt, I disabled call waiting from the phone so my calls don't connect, waiting for S9 to upgrade. Must be Korean phone issue
Your plan from carrier allows this feature? And try a different ROM.
godkingofcanada said:
Your plan from carrier allows this feature? And try a different ROM.
Click to expand...
Click to collapse
It works in different phone and have changed various CSC and ROMs but to no avail.
mrdigit420 said:
It works in different phone and have changed various CSC and ROMs but to no avail.
Click to expand...
Click to collapse
Run it and let the error occur with catalog running so we can see the errors as they occur
godkingofcanada said:
Run it and let the error occur with catalog running so we can see the errors as they occur
Click to expand...
Click to collapse
Catalog? Also I don't get any errors the call just hangs up itself
Hi, was anyone able to solve this issue? Seems like this is the problem with all South Korean Samsung Galaxy phone models. Has anyone tried replacing the dialer? did it work for anyone?
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?