Hi guys,
I have a shindy new Xoom, and it's great– except for one thing. Here in Indonesia the network is set up for mobile phones, not tablets. You need to prepay 3G credit, then top up as required. That's fine, excerpt the only way to check your credit is by calling *888# to your provider. Then you get a pop-up message back with the answer (by the way, Zooms receive these just fine). But without a dialer, how can I call the number?
Any ideas gratefully accepted.
Cheers,
Mike
,
Related
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?
Hi guys, I',m brazilian and I brought a AT&T Incite from the US, unlocked. Slipped in my "Oi" brazilian SIM and it worked. Made calls, got messages but my own messages wouldn't go through, as well as the Wi-Fi connection, which would connect but wouldn't effectively work.
It is definetly unlocked, considering my SIM card is up and running, making and receiving calls (receiving SMS too), but it appears that the AT&T software is preventing me from using some of the key functions of my phone such as texting and using Wi-Fi connections.
Anyone knows what can I do to solve it, please??? Thanks a lot.
Help, plz!!!
I'm a Soldier stationed in Honduras but temporarily deployed to Haiti. My wife is back at my original home station in the U.S. She is still on AT&T and while in Honduras, I was with Tigo. While on Tigo, we could both send and receive phone calls and texts just fine. I just recently arrived in Haiti and picked up Digicel service. I have local and international money on my account. I have not changed my wife's contact number in any way, however now, she can receive my calls but we can't receive eachother's texts.
I've given her my number which is:
011 509 (xxxxxxxx)
In Honduras, with Tigo, it always worked when I would call/text using:
001(803)(xxxxxxx)
I've heard some others say that I could use the plus (+) sign making my call look like:
+1(803)(xxxxxxx)
I can't always call, so we rely on texts quite often. We have both sent texts to eachother with no avail. I don't know what else to do. Please help!
King
Found out how my wife can text me. She uses +509xxxxyyyy and it works perfectly. She still cannot receive my texts using the two methods in the original post above. I erased her number from my contacts and had her call me. It showed up as +1803xxxyyyy so I saved that number and tried to send a text but ended with the same result. I am being charged for each attempt.
I understand now that different carriers may require different country inputs of country codes. I don't understand why digicel will not allow me to send out a text when it is included in the pre-paid service and I have international time loaded as well as local.
Anyone? I've hit a road block and I'm out of ideas. Please help.
I searched this, and was surprised not to find any threads on this topic, as I'm sure it has been answered already, but anyways...
I'm travelling in the US for the next 2 weeks, and I want to avoid roaming charges on my cellphone. I do have wifi where I am, and I want to know if there's any way that I can use this to avoid roaming charges.
I know there are SMS apps that send texts over your data connection, and I just wanted to see if this would help me evade roaming charges.
On a side note, if anyone knows, does rogers charge roaming on incoming and outgoing, or just outgoing?
And, can I get both my incoming and outgoing to come through wifi?
Thanks in advance
Just wanted to bump this one up as I would really prefer to know the answer soon
I have textplus on my phone and that does allow me to send messages through wifi and I can also receive them. When I send a message it uses a really funny number (like 1001-2223202) But you select a name to be shown when the person receives the message. Also if you want to receive a message the sender has to reply to the funny number not your typical cell number, If the sender send you a message and you donèt have wifi on, the message shows up the next time you open the app.
Hope this helps....
I dont know why your are going out of your service area but another option is to pick up a SIM card for a local network when your away. You can get a cheap SIM and get a pay and talk type plan while your in that area, this way you can make local calls and message without worrying.
I guess it all depends on you situation.
Google voice works.
Sent from my Vibrant using xda app
@designerfx
I don't have an american number to tie Google Voice to, so I can't use it as it is exclusively for the states.
@hipditch
Thanks, I'll try that. I'm out of my service area because I'm on vacation
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.