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

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.

Related

T-Mobile UK Users - Important Information re Voicemail Issue

Anyone using, or planning to use, the HTC Touch Cruise on the UK T-Mobile network will very probably need to do a special setup on their device to get voicemail access working properly.
The symptom is that your callers will be able to leave you voicemail messages but you will not be able to pick them up from your phone. When you get a voicemail message you will get the notification but when you press the soft key to access voicemail it will dial the number but you will then get an error message saying "access to this number is barred" and the system will hang up on you.
If you try accessing voicemail by holding down the "1" key or by explicitly dialing the voicemail access number retrieved from the network (probably of the form "+44050<your mobile number minus the leading zero>" or ""+44068<your mobile number minus the leading zero>") you will get the same message. Dialing 222 will work but will also initiate a voicemail setup message each time and however many times you switch your phone on and off to reload the voicemail settings from the network it still won't work.
I just spent 2 days with the very helpful T-Mobile support to sort this out, ultimately getting escalated up two levels in the technical support group, until I got someone who recognised the problem.
The issue is simple to resolve. The problem is that the format of the voicemail access number that the T-Mobile UK network pushes down to the handset is incompatible with the HTC software on the Touch Cruise (and maybe other devices too). The thing the software doesn't like is the "+" at the beginning.
To fix it go to the Settings/Personal/Phone application and click the second tab ("Services"). Now select "Voice Mail and Text Messages" and click "Get Settings...". You should now see a screen with two access numbers populated, one for voicemail and the other for text messages. Both will probably start with "+44". The text message access number is OK so don't mess with that but the voicemail access number won't work with the UK network. Simply replace the "+" with "00" and click OK and then your voicemail should work as you expect.
I haven't tried accessing voicemail outside the UK so it is possible that the above might break your access when roaming and you might need to edit back the "+" when travelling. I'd be interested in knowing if anyone has any experience with non-UK access and a "0044..." setting rather than the default "+44...", does it dial the UK access number OK?
(Actually, I never looked at the mechanics of accessing voicemail outside the UK, does it still dial the UK number or does the host network automatically push an alternate local access number to your phone when you register with the network?)
- Julian
Nice on Julian. I bought an Orbit 2 on O2, but my number doesn't transfer to O2 for few days yet, so have been using my T-Mobile SIM, and also experiencing this problem.
Thanks for sharing the tip!
I'm on UK T-Mob Web&Walk. Switched the +44 entry to 0044...but my TC then coundn't send texts. Switched it back and fortunately can still access voicemail as well as send texts. Strange.
I'm with T-mobile running an old T-mobile sim card on my new TC, when first called voice mail it gave me a long introduction then said "turn of your mobile off and on again to not get this messages again", I turned TC to "air plain mode" back to on mode and everything was cool from there on.
It seems that not everyone have that problem OR T-mobile has sort out that problem after Julian told them about the problem. In any case, thanks Julian to share this with us.
PS (today after reading this post is the first time that I use voice mail with my new TC)
Similar problem on WM 6.5 Asus Crystal
I had exactly this problem with T-Mobile and WM 6.5.
T-Mobile technical support was excellent, ringing back on several occasions to ensure that the problem was fixed, even though my handset is not a supported model. Once I was put through to 2nd layer support they fixed it in seconds.
In a nutshell, if you text and voice service centre numbers begin with a +44......, change them to 0044......
This did not happen on my XDA Exec WM5.0, so appears to be a new thing in WM6.5?

+(country code) (number) does not work with Softbank in Japan

Hi all,
I am sure I am not the first one with this problem, but I could not find any posts via the search.
I recently moved to Japan, and of course took my european Touch Pro (GSM/UMTS).
My company provided me a Softbank USIM card (with a low end standard phone which is good for nothing other than making calls).
Of course I put the USIM into my TP, as I can sync my business contacts to it using active sync (which is obvuiously not possible with the low end phone with came with the USIm card).
Now I am facing the problem, that Softbank in Japan seems not to support "+" infront of country code, so if I dial a number sync with international format (e.g. +49 511 7788855), I end up getting some announcement from Softbank, that my call could not be progressed.
After playing around, I found out I need to dial 010 49 511 7788855 to get through.
Of course I have no interest in manually changing all my synced contacts to this format, especially as it will not work as soon as I leave Japan for a business trip.
The next problem is, that for dialing local Japanese numbers (contry code +81), not even the 010 prefix does the trick. In case of local numbers I really have to dial without any country code like:
080 3456789 works
010 81 80 3456789 does not work
+81 80 3456789 does not work
As you can imagine, this situation is everything else but satisfying.
No wI am looking for any kind of propper solution (which does not include entering three different formats of phone numbers for each of my contacts).
I hoped the would be a small program that can automatically replace "+" by "010" and "+81" by "0".
If I rember correctly, I had a similar option in one of my previous HTC phones, but can not rember, which software was offering it, and can not find any similar option in my current TP ROM.
Anyone has an idea how to solve this?
Thanks and regards,
Check under Start > Settings > Phone > Services and see if you have a Plus Code Dialing option. If so, you should be able to choose Get Settings and change the code accordingly.
010 is only for international dialing, so local numbers should be stored as local numbers without "+".
Thanks, but in settings -> phone -> services I only have:
call barring
caller id
call forwarding
call waiting
voice mail and text messages
Regarding local phone numbers:
The problem is, that I sync my phone with our company exchange address book. The phone number format is stadard with +country code local number, I can not change that.
I mean, in Europe it is no problem to dial a number with the country code of the country you are currently in. The call will still get through.
I can not understand why Japan (or at least Softbank) does not support the same.
SoftBank (or other japanese mobile companies) simply DO NOT support this, for the reasons only they know. Its too bad, i am also from europe, and that + dialing is really benri thing. wherever you go, you dail your contacts exactly the same way, but not in japan.
Its plain STUPID if you ask me.
of course it is stupid, but I doubt the japanese mobile phone provider will change it when I complain to them.
It should be easier to find a work around.
As I said, there was an option or software in one of my previous HTC devices, where I could choose to replace + by 00.
That makes me think the + could also be replaced by 010, no?
The solution is called MagiCall.
Works perfectly.

[Q] HTC 8X caller ID issue

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.

country code causing text messages to fail

HI everyone.
Sorry for the second post in a few days, but this is an annoying issue
I have a verizon galaxy s6, and I am currently living in Belgium, using belgian sim (carrier BASE). I don't think this issue is unique to the country or the carrier.
The problem I am having is that when I receive a text message from a belgian number, the number that shows on my phone has the country code: +32 xx xxx xxxx. I can get text messages like this, but when I try to reply, the message fails. (this has happened on every number ive tried to respond to.) The only way I can get my texts to send is by making the number into a new contact, and removing the +32 country code. The same goes for when i'm trying to call, I have to remove the country code, if I keep it, the call fails. I've tried turning on and off assisted dialing, and I did a factory reset on my phone. Ive tried dialing US numbers and they have also failed, so it's not forcing the +1 country code on my numbers while calling either.
This is a huge pain, because it forces me to make a new contact for every single new number, even if its not a number I need/want to keep, and go in and adjust it manually.
Thanks for the help, it's very appreciated.
I have the same issue in Albania...i belive you ! It's a very a anoying matter , from that moment i have editet all the numbers i frequently call or text..!
chpv said:
HI everyone.
Sorry for the second post in a few days, but this is an annoying issue
I have a verizon galaxy s6, and I am currently living in Belgium, using belgian sim (carrier BASE). I don't think this issue is unique to the country or the carrier.
The problem I am having is that when I receive a text message from a belgian number, the number that shows on my phone has the country code: +32 xx xxx xxxx. I can get text messages like this, but when I try to reply, the message fails. (this has happened on every number ive tried to respond to.) The only way I can get my texts to send is by making the number into a new contact, and removing the +32 country code. The same goes for when i'm trying to call, I have to remove the country code, if I keep it, the call fails. I've tried turning on and off assisted dialing, and I did a factory reset on my phone. Ive tried dialing US numbers and they have also failed, so it's not forcing the +1 country code on my numbers while calling either.
This is a huge pain, because it forces me to make a new contact for every single new number, even if its not a number I need/want to keep, and go in and adjust it manually.
Thanks for the help, it's very appreciated.
Click to expand...
Click to collapse
Hi, I'm from Argentina and have had the same issue with sms. In my case, I was able to send sms but cannot reply because the messages comes with +54 (My country Code) before the line number. After 2 weeks claiming to the carrier (Personal), the problem was fixed changing the SIM CARD for a new one. I Hope this can be helpful for you.
Regards.
Martin

some phone callers are always reaching disconnected message to my phone

I am looking for some information regarding a problem I am experiencing with my phone, I have 3 questions regarding it. I have stated them at the end of this lengthy post.
My phone is zte grand x2 model z850 and android build is 5.1, carrier is pcmobile in Canada.
The problem is that my android phone seems to work OK and receives calls correctly, but my doctor office, hospial booking office, and phones belonging to my workplace receive a tone followed by some type of reaching a disconnected number. My phone calling log shows no record of calls being received to phone.
The troubleshooting steps are sent email to pcmobile and received response to do a battery reset, pull out battery and sim card for at least one minute and reinstall. If it doesn't work call their customer support and get put through to tech support.
That did not work. Call to the tech support says that all 0:00 second calls end in response to some type of code (mentioned a specific code but I forget) and that it means my phone is responsible. She said android phones allow for rejecting calls based on various categories like toll free originating and such. And that the phones calls not getting through likely belong to a category I have blocked. She mentions just goto phone menu, settings, and something like call block, call reject and I will most likely find something there. If that doesn't work to do a backup and factory reset. To do that she says I need to call zte for help as she isn't allowed to help with it.
My zte phone interface only shows call barring settings with a few things like all incoming or incoming roaming, outgoing or outgoing roaming and that is it.
However it is possible that I came across via a web search a USSD code to ban telemarketers and used it. I just don't no what code it was or even if I did such a thing.
Anyway I called back their customer service to maybe get further help and had specific phone numbers and times of calls that were rejected by disconnected number messages from my workplace. To see if the problem could be isolated at my phone as a reason or maybe in the network somewhere. And was also wanting to know how I can unset the call reject if I have no interface to do it or undo it. Maybe even get confirmation that the noted calls are actually making it to my phone or getting dropped in the network. The new customer support first asked if it was a ported number and since it was, he checked with someone to see if it was a problem. The porting people said all calls were routed correctly through to my phone, but the customer support guy said there was no way to verify if my specific noted calls were included.
He mentions their tech support did not help with actual phone troubles, but he suggested I get another sim card and phone and use them in varios combinations with my phone and sim to get the working/ not working situations and isolate the problem. This I have not done yet as it seems like a lot of expense and jumping through hoops trying to fix a problem that seems like it should be able to be verified in a phone setting log somehow. He refused to put me through to tech support when I said I wanted him to anyway.
My emails with zte have them requesting I do a backup and factory reset, if that doesn't work then try a new sim card, if that doesn't work then book my phone for a repair with them.
So my question number 1 is:
Is there a USSD code that allows me to see settings or logs of such a call reject being used. I have tried *35**# which is supposed to show "incoming call barring" and it responds "Call barring Service has been disabled." My phone user interface doesn't provide for this as best as I can tell.
My question number 2 is:
What is the USSD code that I might have used to try and reject telemarketers which might issue tones that might indicate a disconnected number. I'm thinking this is the most likely reason for my troubles. I have been unsuccessful google searching for what I may have done. I find info on various USSD codes at this forum and elsewhere. But I'm not finding anything specific to help. I thought the *35**# would have helped but it doesn't. It is very possible I did do something like this with a USSD code which is causing my trouble.
.
Part 2 of this question is what would be the USSD codes to see the status or to unset such a thing.
My question number 3:
If there is no way to set status or see the status of call barring and rejecting logs or settings of the phone. If I do a phone reset, how is it possible that it could be the sim card instead. Does the sim card actually store call rejecting and barring settings as well.
Part of troubleshooting this involves me contacting third parties such as work, doctor, or hospital and asking them to try and call me and if not successful contact me someway else and tell me it was unsuccessful. I really doubt any of them want to do this for me more than once or twice. So I'm trying to gather info and limit my number of attempts. It would be real useful to be able to look up logs or settings somehow.
Would anyone know if the effect of *77 being used is that the caller experiences reaching a disconnected number. Or what do they usually experience.
In web searching possible codes I may have used, I came across the *77 code to reject anonymous callers. The *87 would be to unreject such a setting. Is there a method to check the current setting of either on or off somehow.
I am unable to test the specific phones getting the message of reaching a disconnected number. I will however have better access to one of the phones in three weeks time to see if *87 fixes my troubles.

Categories

Resources