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?
Hello, I have only had my touch pro a few days and when I try to access my voicemail I get to the part to enter my pin, then it tells me "first new message..." and then it hangs up. Is this a known issue? I tried searching the forum and in fact all of google, but nothing.
Any ideas?
I've had the same issue here in the Netherlands.
Disconnect when I called my own VM, also a disconnect when I tried to leave a message at a friend.
Both are in the TMobile network.
Just tried it again, but it workes ok now
solved
I figured it out for my phone. When I put my sim card in, the phone auto detects settings for sms, mms, data and voicemail. Here in Canada, providers have several different voicemail retrieval numbers and the phone autodetected the wrong one. I thought that since it did work at least somewhat, that the number was not the issue.
Contact your service provider and make sure your phone didn't choose the wrong retrieval number too
Really strange. I suddenly lost the ability to send SMS messages. I can still receive them, and I can still send MMS, pictures...etc., but NOT SMS.
This has happened before once on my Nexus One, I went into messaging, opened settings, and there was an option for "Service Center number" or something similar...I was then able to input the SMSC # "12063130004" and all was well.
However, in Gingerbread on the nexus S, there is no such option under messaging settings
I tried *#*#info#*#* as well, went to the SMSC box which was blank, entered "+12063130004", then clicked update...but I keep getting "Update Error".
I'm not sure if this matters or not, but when I choose "Refresh" to the right of the blank SMSC box, instead of obtaining the correct telephone number, I get "00".
If anyone has encountered this, or has any other possible ideas...I'm all for it. I've tried some basic stuff, cycling battery, restoring from nandroid...even flashing a stock 2.3.1 and unrooting/unlocking the Nexus S, and I am still stuck, totally unable to send an SMS. Please help!
SMS seems good on my end :/ maybe just an issue in your area?
slowz3r said:
SMS seems good on my end :/ maybe just an issue in your area?
Click to expand...
Click to collapse
Possibly, thanks for checking. I wish there was a way to manually enter a SMS service number in messaging settings like in previous android versions. I was thinking maybe for some reason my SIM card is too old, and suddenly decided to not be recognized properly. Looks like I'll be going to t-mobile tomorrow,
May wanna give them a call. going into a store they wont be able to help you
I've found that the primary merit to taking my phone to T-Mobile when it's messed up is so the guy behind the counter has to go through the list of things you already tried that the phone support agent is required to tell you to try again instead of having to do it myself. At least I can check out some cool phones and accessories while I wait. >.>
slowz3r said:
May wanna give them a call. going into a store they wont be able to help you
Click to expand...
Click to collapse
I spoke to a lovely Tmobile rep. She lead me through troubleshooting, except it was for Froyo, not gingerbread. When I brought this to her attention, and reminded her this was a nexus s, she connected me to samsung , and the call never went through.
Could a 5 year old SIM card magically stop working properly for SMS?
mprziv said:
I spoke to a lovely Tmobile rep. She lead me through troubleshooting, except it was for Froyo, not gingerbread. When I brought this to her attention, and reminded her this was a nexus s, she connected me to samsung , and the call never went through.
Could a 5 year old SIM card magically stop working properly for SMS?
Click to expand...
Click to collapse
honestly tell them you have an extremely old SIM and they will give u a free new one...if it deosnt help. then hell you got a free sim
Yeah. Unfortunately, since the Nexus S isn't supported by T-Mobile, giving you a new SIM card is about all they'll probably do, unless you're lucky and get a rep who's actually tech savvy.
zorak950 said:
Yeah. Unfortunately, since the Nexus S isn't supported by T-Mobile, giving you a new SIM card is about all they'll probably do, unless you're lucky and get a rep who's actually tech savvy.
Click to expand...
Click to collapse
The @Tmobile twitter is way handy and the reps who run that, are actual engineers so send them a tweet
This could be many things... does the Nexus S not have the ability to do the *#*#4636#*#*?
That is the code on every Android phone (save a very few POS) to get into the "engineering" menu. Select "phone" from that menu, then scroll to the bottom and bingo, SMS service center number entry... first hit refresh to see what is shows, if not correct delete, enter in the correct one, then update.
If the phone doesn't have the *#*#4636#*#* menu, not sure... perhaps your SIM doesn't have the SMS service center # saved to it anymore? New SIM would correct that, or putting your sim in an basic phone, then changing the service center # on that phone would put it back on the SIM.
Also, have you tried texting yourself to make sure it isn't a cross carrier issue? I know Verizon, for example, doesn't play very nicely with other carriers (actually all carriers prioritize in network traffic over cross carrier traffic, but Verizon seems to be especially bad in my experiences).
(FYI, I was looking through as I am thinking about getting a Nexus S and saw this thread, and couldn't help but toss in a word or two given I sell cell phones and have to deal with things like this all day).
mprziv said:
Really strange. I suddenly lost the ability to send SMS messages. I can still receive them, and I can still send MMS, pictures...etc., but NOT SMS.
This has happened before once on my Nexus One, I went into messaging, opened settings, and there was an option for "Service Center number" or something similar...I was then able to input the SMSC # "12063130004" and all was well.
However, in Gingerbread on the nexus S, there is no such option under messaging settings
I tried *#*#info#*#* as well, went to the SMSC box which was blank, entered "+12063130004", then clicked update...but I keep getting "Update Error".
I'm not sure if this matters or not, but when I choose "Refresh" to the right of the blank SMSC box, instead of obtaining the correct telephone number, I get "00".
If anyone has encountered this, or has any other possible ideas...I'm all for it. I've tried some basic stuff, cycling battery, restoring from nandroid...even flashing a stock 2.3.1 and unrooting/unlocking the Nexus S, and I am still stuck, totally unable to send an SMS. Please help!
Click to expand...
Click to collapse
I have the exact same issue.Stock phone with Mobilicity. I don't know what their service number is.
Went in to T-mobile store today, got a new sim...everything is working properly now.
mprziv said:
Went in to T-mobile store today, got a new sim...everything is working properly now.
Click to expand...
Click to collapse
did you pay for it or was it free?
slowz3r said:
did you pay for it or was it free?
Click to expand...
Click to collapse
Since when has anyone ever charged for SIM cards?
zorak950 said:
Since when has anyone ever charged for SIM cards?
Click to expand...
Click to collapse
Last i checked its like 30 bucks to replace a SIM from tmo.
slowz3r said:
Last i checked its like 30 bucks to replace a SIM from tmo.
Click to expand...
Click to collapse
Huh. I've never known T-Mobile to charge to replace a SIM card that needed replacing, whether due to its being outdated or simply worn out. Maybe I just got lucky.
zorak950 said:
Huh. I've never known T-Mobile to charge to replace a SIM card that needed replacing, whether due to its being outdated or simply worn out. Maybe I just got lucky.
Click to expand...
Click to collapse
last i went was because i needed a replacement sim cuz my phone wouldnt pick up 3g and called a rep and said he put a note on my account so i can run into a store and get a free sim
SMSC Update Error - Solved
I had the same problem - but found a way to solve it without replacing sim.
What you need to do is to insert the sim into an older phone and update message central number from there.
I fixed it using a nokia 3210 - after having tried using an n95 with no success.
While trying to figure out what was wrong i tested with another sim also - and when reading out the SMSC from the *#*#info#*#*-menu i found that the number is stored in some strangely obfuscated way.
Here is how it stores number for two of norways major operators:
Netcom: +4792001000 - shows as 06917429000100
Telenor: +4790002100 - shows as 06917409001200
What the first 4 digits are for, i'm not sure, perhaps a code for '+' but whats interesting is the last 10 digits - they are basically swapped around in pairs of two.
I tried inputting the digits for the other central in this manner, and sure enough - it saved ok!
Hope this help someone
grab another phone and put your SIM card in it
then try to send a SMS
see if that works properly or not.
if that works, then it might be a SNS setting issues
if the SIM card does not send SMS on another phone, then you'll need to swap your SIM card with a new one.
I had the exact same problem just few weeks ago
mprziv said:
Really strange. I suddenly lost the ability to send SMS messages. I can still receive them, and I can still send MMS, pictures...etc., but NOT SMS.
This has happened before once on my Nexus One, I went into messaging, opened settings, and there was an option for "Service Center number" or something similar...I was then able to input the SMSC # "12063130004" and all was well.
However, in Gingerbread on the nexus S, there is no such option under messaging settings
I tried *#*#info#*#* as well, went to the SMSC box which was blank, entered "+12063130004", then clicked update...but I keep getting "Update Error".
I'm not sure if this matters or not, but when I choose "Refresh" to the right of the blank SMSC box, instead of obtaining the correct telephone number, I get "00".
If anyone has encountered this, or has any other possible ideas...I'm all for it. I've tried some basic stuff, cycling battery, restoring from nandroid...even flashing a stock 2.3.1 and unrooting/unlocking the Nexus S, and I am still stuck, totally unable to send an SMS. Please help!
Click to expand...
Click to collapse
a one-phone solution from www google com tw/support/forum/p/Google+Mobile/thread?tid=078232a74455bbf0&hl=en
Code:
OK, I managed to fix this. I'll post the answer because this was buried deep and is a pain.
Answer is here:
http://forum.xda-developers.com/archive/index.php/t-926771.html
The relevant text is below. One thing I'd say is that the link is a bit vague on how to do the conversion. You need to put your SMSC number in the page, clear the rest of the info and press convert. You then need to ignore the numbers after 11.
For example, my vodafone +447785016005 goes to 0791447758100650110000910000AA00, which shortens to 079144775810065011. Go to the *#*#4636#*#* menu and put that in SMSC and hit update. Messages now send!!!. Hopefully I can save someone else the grief I've had all day...
"
to update the SMSC in android,
the number first need to be encoded
please use below url to encode the SMSC
http://www.twit88.com/home/utility/sms-pdu-encode-decode
for example, if your SMSC is number is +4531300000,
after encode, it is 0691541303000011
put this in the info page, and it will work.
"
I have searched and searched for how to get to the programming menu for the DROID X.
We bought this phone from a guy that flashed it to Metro PCS and it worked perfect.
We want to use it for Metro as well. But for some reason the workers say they need a programming code for it because it's not one of their own phones. We tried telling the worker the model number because I guess sometimes you can get the code from the M#, but it didn't work. I have searched online that you can do ##PROGRAM and then send, then 000000, but the only screen we had was the "Touch the Droid to activate" and it has Emergency call and Change language at the bottom. We tried typing ##PROGRAM 000000 in the E. Call but it just tells us it's not an emergency number.
Since we've called the MetroPCS customer service, the first time, we couldn't get the ESN, because the MEID HEX isn't behind the battery, so that worker did us no good. Then we rebooted the phone and it actually came up past the "Click the Droid to activate" screen and we're actually at a home screen now, but with no service and etc. We talked to another worker and we got disconnected. The third worker supposedly set up our account and gave us a phone number but couldn't program because the model number wouldn't work. IDK.
All I want is the programming menu code, so they can fully activate the phone. I'm sorry if this is confusing, it was very confusing to us too!
Sorry this is so long, I thought maybe more details is better than too little details. Thanks for whoever replies.
Sara
EDIT:: Since we have been able to get to the homescreen somehow, I guess we could try doing ##PROGRAM on the normal dial pad, but my boyfriend has the phone so I will wait for him to come over. I also have seen that on some Droid X's the ##PROGRAM doesn't work and just dials the number because of some ROM. Will I have that problem since the phone is flashed over to Metro?
Droid X
I had same issue, if the phone is waiting for network program and you can't do anything but press a green droid then you can't enter ##program.. Once the phone is one with metro you can then enter the ##program and 000000 .. I just did that here.
Phone has to be activated before you can enter.. Is what I found.
hope I helped
wholesale - florida .com
Mark
MikeB89 said:
I have searched and searched for how to get to the programming menu for the DROID X.
We bought this phone from a guy that flashed it to Metro PCS and it worked perfect.
We want to use it for Metro as well. But for some reason the workers say they need a programming code for it because it's not one of their own phones. We tried telling the worker the model number because I guess sometimes you can get the code from the M#, but it didn't work. I have searched online that you can do ##PROGRAM and then send, then 000000, but the only screen we had was the "Touch the Droid to activate" and it has Emergency call and Change language at the bottom. We tried typing ##PROGRAM 000000 in the E. Call but it just tells us it's not an emergency number.
Since we've called the MetroPCS customer service, the first time, we couldn't get the ESN, because the MEID HEX isn't behind the battery, so that worker did us no good. Then we rebooted the phone and it actually came up past the "Click the Droid to activate" screen and we're actually at a home screen now, but with no service and etc. We talked to another worker and we got disconnected. The third worker supposedly set up our account and gave us a phone number but couldn't program because the model number wouldn't work. IDK.
All I want is the programming menu code, so they can fully activate the phone. I'm sorry if this is confusing, it was very confusing to us too!
Sorry this is so long, I thought maybe more details is better than too little details. Thanks for whoever replies.
Sara
EDIT:: Since we have been able to get to the homescreen somehow, I guess we could try doing ##PROGRAM on the normal dial pad, but my boyfriend has the phone so I will wait for him to come over. I also have seen that on some Droid X's the ##PROGRAM doesn't work and just dials the number because of some ROM. Will I have that problem since the phone is flashed over to Metro?
Click to expand...
Click to collapse
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.