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 just requested to unlock my phone, its alredy paid off, I contacted the customer service and I received an email for the unlocking instructions, I opened the app and clicked permanent unlock, but it says Device Failed to unlock. Then I noticed the emei # on my email is wrong, the last digit was "0", I went to check my actual emei and its almost correct but the last digit is "5". I went to my online tmo account and there is an emei on the device and the last digit is also "0".
Does the emei's # automatically displayed on their site? Or the CS representative have to enter it manually? Or they just scan it?
Just call, they will unlock it within an hour. For me also the app did not work.
As for the IMEI that is odd indeed, get it sorted with support.
They said they can only unlock 1 phone a year?? Coz i got my m8 unlocked last September.
If you have other family members on your account, switch the phone to their number and after 45 days they should unlock, then switch back.
Hi guys, i have two G860p and tried to unlock them for using in New Zealand
Both of them running android 5.0 and i used the idoneapps to unlock it
For the FIRST one, the phone got signal, can send text, use 3G data, make phone call BUT ONLY UNABLE TO RECEIVE phone call. There is always an error of "Unfortunately the process com.android.phone has stopped" when other people call me. I did factory reset and used the another unlock method - bring back to 4.4.4 and unlock by SU.apk (http://forum.xda-developers.com/spr...sim-unlocking-sprint-galaxy-s5-g900p-t3085624) but it still has the same issue. After that i dialed ##72786## to bring the phone back to original setting to find another solution. One day after that, i realize that i didn't enable the GCF after unlock the phone and tried to do it immediately with the hope that it will solve my issue. Unfortunately, the issue still happen and i also have a new trouble with handset free activation.
Interestingly, for the second one, i just need to enable GCF after using the idone apps and it works perfectly. In fact, it has no issue with receiving phone call like the first one.
So, anybody understand what happen with my first phone after dial ##72786##, how can i get rid of handset free activation and unlock my phone like the second one. In fact, i have tried to flash the orginal room, factory reset, etc, but the handset free activation still appear and unable to receiving phone call after unlock as well.
oh, another information is my first phone has clean ESN and is not blacklisted