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.
"
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
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.
Data, and texting works just fine. I switched to cricket, and up until about 5 pm yesterday calls worked fine, then by 8pm I noticed it wasn't working because I tried to call someone. I didn't do anything modifications during this time. I've since put the sim in s different phone and it still doesn't make calls but data and texting works. I've factory reset and started from scratch, still doesn't work. Changed sim slot, nothing. If anyone has any ides. I've called cricket already and they've escalated the issue but I won't here from them til Monday the earliest. Thank God for those text and call apps. I can make calls with them. I can also make calls with FreedomPop sim. I've attached a log that has me attempting several calls in it. I just don't know what I'm looking at. Any help would be greatly appreciated. And I also checked apn settings several times.
mortrackz said:
Data, and texting works just fine. I switched to cricket, and up until about 5 pm yesterday calls worked fine, then by 8pm I noticed it wasn't working because I tried to call someone. I didn't do anything modifications during this time. I've since put the sim in s different phone and it still doesn't make calls but data and texting works. I've factory reset and started from scratch, still doesn't work. Changed sim slot, nothing. If anyone has any ides. I've called cricket already and they've escalated the issue but I won't here from them til Monday the earliest. Thank God for those text and call apps. I can make calls with them. I can also make calls with FreedomPop sim. I've attached a log that has me attempting several calls in it. I just don't know what I'm looking at. Any help would be greatly appreciated. And I also checked apn settings several times.
Click to expand...
Click to collapse
Soooo the issue is with the SIM and not the phone... This forum cant really help with that issue.