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.
"
[HOW-TO] Reenter your lost SMSC number
Fix not sent SMS messagesHey, you just flashed an ICS ROM and found out that you can't send SMS messages anymore? You flashed back to Gingerbread and it did not help?
In this case probably your SMSC number has been deleted. I've had that problem too and found several webpages that said "Do this", "Do that" and finally you shall enter your SMSC number and tap on update. Well, indeed that's basicly it, but there's one problem: You will get an update error, because you can't simply enter "+4912345..." into the little box.
"But how can I update my SMSC number?"
Well, for this you have to do a little step before you can do that. The number has to be converted into the PDU format. To do that go to this page: http://www.twit88.com/home/utility/sms-pdu-encode-decode and look for "String sms message". There is a little editbox which says: "SMSC +019000001". Enter your own SMSC number here and klick on "Convert" below. The big textbox "Hexadecimal PDU Message" will update and will show something similar like this:
Code:
AT+CMGW=24
[U][B]0791349124722037[/B][/U]11000A9210299232900000AA0CC8F71D14969741F977FD07
The first 16 numbers which are underlined are your converted smsc number.
"All right and were shall I enter it?"
Open your phone app and enter "*#*#4636#*#*" after that a new window will open. Select "Phone Information" and scroll down. There will be a little box "SMSC ". Enter your converted SMSC number (in this example: 0791349124722037) and tap on the left button which says "Update".
"That's all?"
Yes you're done, but how about leaving a little comment?
I have created this thread because while searching with google I have found tons of websites that did not mention the PDU conversion and so I have thought it is good to have it here...
Reserved. Just in case...
thanks... worked great for me... nice guide.
Hello, I tried following your guide, but I have not solved the problem of sending MMS. But now I can not set the old SMSC number. Can you help?
EDIT: Thanks, but I solved by putting the SIM in an old phone and restore code SMSC.
Excuse my English.
I dont have a galaxy but i keep running into this issue.
Plus im on sprint, and when i go into the phone to update the SMSC number i keep getting update error.
I have been searching but i can not find anything that has helped.
Taraen said:
[HOW-TO] Reenter your lost SMSC number
Fix not sent SMS messagesHey, you just flashed an ICS ROM and found out that you can't send SMS messages anymore? You flashed back to Gingerbread and it did not help?
In this case probably your SMSC number has been deleted. I've had that problem too and found several webpages that said "Do this", "Do that" and finally you shall enter your SMSC number and tap on update. Well, indeed that's basicly it, but there's one problem: You will get an update error, because you can't simply enter "+4912345..." into the little box.
"But how can I update my SMSC number?"
Well, for this you have to do a little step before you can do that. The number has to be converted into the PDU format. To do that go to this page: http://www.twit88.com/home/utility/sms-pdu-encode-decode and look for "String sms message". There is a little editbox which says: "SMSC +019000001". Enter your own SMSC number here and klick on "Convert" below. The big textbox "Hexadecimal PDU Message" will update and will show something similar like this:
Code:
AT+CMGW=24
[U][B]0791349124722037[/B][/U]11000A9210299232900000AA0CC8F71D14969741F977FD07
The first 16 numbers which are underlined are your converted smsc number.
"All right and were shall I enter it?"
Open your phone app and enter "*#*#4636#*#*" after that a new window will open. Select "Phone Information" and scroll down. There will be a little box "SMSC ". Enter your converted SMSC number (in this example: 0791349124722037) and tap on the left button which says "Update".
"That's all?"
Yes you're done, but how about leaving a little comment?
I have created this thread because while searching with google I have found tons of websites that did not mention the PDU conversion and so I have thought it is good to have it here...
Click to expand...
Click to collapse
Thank you so much i was pulling my hair out over this. I had the message center number but had no idea about the PDU conversion. It's also worth noting that you can check the PDU is correct by pasting the first 16 characters into "Hexadecimal PDU message"(its ABOVE the smsc box) and pressing convert. It will convert it back and you should see your message centre number you entered down in the SMSC box in the "Readable PDU message" box. If not, you've copied the wrong digits. It's Best to copy ONLY the first 16 chars as you are checking only your SMSC.
Dude Thanks so much for this, Vodafone have been trying to figure this out and knew nothing about the conversion and then tell me my phones broken !!! Shows you how much they know !!! Much Appreciated my friend really good help !!
Problem
This doesn't work for me. Maybe because i am in Greece. Maybe i have to change the Receiver on this page.I don't know, help me
Try using GoSMS. Go to Settings > Advanced > Enable customized SMSC number and put your carrier's SMSC number in. Did the trick for me and it even sticks after uninstalling GoSMS!
May Be this will work
Hi Guys, Using a SAMSUNG GALAXY NEXUS in INDIA and faced the same problem from last two days....
I came across another thread for the same problem, followed their steps and there it is.... My SMS service was back to normal.
Might prove to be helpful to those guys for whom it didn't work
http://forum.xda-developers.com/showthread.php?t=1916507
Regards,
PPK
Galaxy Grand Duos (GT-I9082) on CM11
Hi Buddy,
Many thanks for this thread.
I tried the steps but didn't help me on my Samsung Galaxy Grand Duos (GT-I9082) upgraded to CM 11-20141008 build.
Neither settings are not stored nor after updating the code SMS sending works.
I have verified the SMSC no.
Request priority advice.
[This is my only work and R&D phone, need to get functionality up soon to avoid awkward situation]
//RK
SMSC code
RamakantSingh said:
Hi Buddy,
Many thanks for this thread.
I tried the steps but didn't help me on my Samsung Galaxy Grand Duos (GT-I9082) upgraded to CM 11-20141008 build.
Neither settings are not stored nor after updating the code SMS sending works.
I have verified the SMSC no.
Request priority advice.
[This is my only work and R&D phone, need to get functionality up soon to avoid awkward situation]
//RK
Click to expand...
Click to collapse
Friends,
I got the issue fixed.
The SMSC code is to be entered in the PDU encoder as + Country Code & SMSC number e.g. +91991xxxxxxx in the box under header "String sms message". Select 7bit "Alphabet size". Remove the text message . Thereafter hit "Submit" button. The hexadecimal PDU message created will be something like "AT+CMGW=8
0791198922700800110000910000AA00".
Use first (from left) eleven (11) digits from this code and enter in the phone.
Many Thanks for support and guidance by all and most importantly this site for rescue.
Regards,
//Ramakant
All of these advice on smsc is wrong. All you do, is enter the damn smsc number in quotes, PDU is not necessary at all.
Taraen said:
[HOW-TO] Reenter your lost SMSC number
Fix not sent SMS messagesHey, you just flashed an ICS ROM and found out that you can't send SMS messages anymore? You flashed back to Gingerbread and it did not help?
In this case probably your SMSC number has been deleted. I've had that problem too and found several webpages that said "Do this", "Do that" and finally you shall enter your SMSC number and tap on update. Well, indeed that's basicly it, but there's one problem: You will get an update error, because you can't simply enter "+4912345..." into the little box.
"But how can I update my SMSC number?"
Well, for this you have to do a little step before you can do that. The number has to be converted into the PDU format. To do that go to this page: http://www.twit88.com/home/utility/sms-pdu-encode-decode and look for "String sms message". There is a little editbox which says: "SMSC +019000001". Enter your own SMSC number here and klick on "Convert" below. The big textbox "Hexadecimal PDU Message" will update and will show something similar like this:
Code:
AT+CMGW=24
[U][B]0791349124722037[/B][/U]11000A9210299232900000AA0CC8F71D14969741F977FD07
The first 16 numbers which are underlined are your converted smsc number.
"All right and were shall I enter it?"
Open your phone app and enter "*#*#4636#*#*" after that a new window will open. Select "Phone Information" and scroll down. There will be a little box "SMSC ". Enter your converted SMSC number (in this example: 0791349124722037) and tap on the left button which says "Update".
"That's all?"
Yes you're done, but how about leaving a little comment?
I have created this thread because while searching with google I have found tons of websites that did not mention the PDU conversion and so I have thought it is good to have it here...
Click to expand...
Click to collapse
Dude near 2 hours on the phone with str8 talk and countless days past since I've searched n searched... I would lick your nut sack if I didn't like ***** so much...my comment will probably be deleted. But in any case to ANYONE THAT CANT USE THE *#*#4636#*#* OR THAT DOESNT HAVE THE MESSGAE CENTER NUMBER IN THEIR SETTINGS IN THE MESSAGE APP THEN FEAR NOT BC ITS IN your network mode settings I tried several codes none took me there. So I download force LTE from the play store or anyone of them will do that I've used... and that big ass SMSC that says updated refresh well that's it it's right there. And I'm supposed to know alot about phones and computers but this gave me nightmares....anyways thank you to the o.p. who probably won't see this anyways but your method needs updated a tad. With a 3rd option to find that setting. Jus download an app for LTE switching from Google or apkpure or wherever. Thank you thank you thank you!!!
Hi all,
I wanted to create a dedicated thread to what have been scatteredly reported by other users in various generic threads when unlocking the Kyocera Brigadier. Mine is rooted (4.4.2, software version 1.102VZ, Kernel 3.4.0-g42c25d8, Build #KOTH49H) with a T-Mobile plan. The original carrier for the device was Verizon. I applied that trick to unlock APN settings. It worked pretty well (I've used kingroot instead of debloater). The Data (4G LTE) is now blazing fast and I can receive call and text messages. However, I can't make outgoing call/text. Below are some details:
Outgoing call: The phone application continuously indicates "CALLING..." but it is stuck there. If this is the first call after a reboot I also have the message "Error while searching for network". Then, I try to tap the "End Call" button but that do not close the phone app. The only way to unfreeze the app is to wait for an incoming call. About 1 restart out of 10 gives the error message "Unfortunately the process com.android.phone has stopped".
Outgoing text message: I systematically get the Error "Cause Code 0"
A factory reset do not solve the issue.
I would be very gratefull if a pro could help.
Not getting a lot of help on this, eh? I have the same problem with mine, I wish I had done more research before I bought the phone. I guess all I can do now is put the paperweight back in the box until either someone makes a rom for it or i figure out how to do it.
is your 4g lte is t-mobile's or else? what band is t-mobile's 4g?
did you try 3g or global and tested call/sms?
im outside usa my local sim is working on 3g out/coming calls and sms are fine but no 4g yet....
i hope someone will help you
I am on the Rogers network in Ontario, Canada. Wireless internet works perfectly, I get 4g, and can receive calls and texts, but I am unable to send either. Rogers was no help, they said it was a software issue. Downloading different phone and texting apps did nothing. The bloody wireless companies locking phones down is a complete pain in the ass.
grimy55 said:
Hi all,
I wanted to create a dedicated thread to what have been scatteredly reported by other users in various generic threads when unlocking the Kyocera Brigadier. Mine is rooted (4.4.2, software version 1.102VZ, Kernel 3.4.0-g42c25d8, Build #KOTH49H) with a T-Mobile plan. The original carrier for the device was Verizon. I applied that trick to unlock APN settings. It worked pretty well (I've used kingroot instead of debloater). The Data (4G LTE) is now blazing fast and I can receive call and text messages. However, I can't make outgoing call/text. Below are some details:
Outgoing call: The phone application continuously indicates "CALLING..." but it is stuck there. If this is the first call after a reboot I also have the message "Error while searching for network". Then, I try to tap the "End Call" button but that do not close the phone app. The only way to unfreeze the app is to wait for an incoming call. About 1 restart out of 10 gives the error message "Unfortunately the process com.android.phone has stopped".
Outgoing text message: I systematically get the Error "Cause Code 0"
A factory reset do not solve the issue.
I would be very gratefull if a pro could help.
Click to expand...
Click to collapse
mine only got 3g from celcom malaysia prepaid,but can use all that feature,only need to unlock that 4g,tried many method but still cant do 4g
Problems Handling Phone Calls (Call Waiting, 3 way, etc.) Verizon S5 on AT&T Network
recently bought a used Verizon Galaxy S5 (SM-G900V). It came with the lollipop OS. My service provider is H2O wireless (on the AT&T Network. From the outset, I had problems with phone calls, text messaging.
1. When I'm in a call, I'm not able to dial (Like to enter numbers for automated systems).
*I solved this one by going to:
settings>applications>call>
Scroll down to DTMF tones and change setting to long.
2. When I'm in a call, I'm not able to click over to calls on call waiting. When I do try to click over, I still hear the original call for a few seconds and then both calls drop and I get an error message that says "no sim or invalid sim". If I don't answer the call, both calls drop and I get the same message. The same thing happens if a try to make a 3 way call.
3. If someone calls me and I try to call them back, the call redirects to turn it into an international call and the call doesn't go through.
*I solved this using an app called prefixer
4. If I try to text message someone who called me, I get an error message back saying the phone number is invalid.
I figured I would have to root my phone to be able to make some custom changes. I first had to downgrade to kitkat (android 4.4.2) and root it and then upgrade with root using some very helpful posts and resources found on this site (thanks). When I downgraded, problems 1 and 2 went away (for number 1, I had to change my network mode, but that solution didn't work when I went back to lollipop). After upgrading beack to lollipop, all of these problems were there, though I was able to resolve 2 of them, the other 2 are problematic.
I think theres a problem with the way the phone is handling the AT&T network signal since they have a different type of network from verizon but i don't know.
I'm will in try to install a custom ROM, change settings in service mode, etc. I just haven't come accross any info to point me towards the right instructions. Alternatively, I may trade or sell this phone ant get an AT&T based phone. What do you suggest?