I'm on the AT&T network and can't send texts anymore after flashing to ICS. I can make calls and use my data plan but am unable to send SMS for some reason. I've tried almost every APN setting recommended by others and still nothing. Does anyone have any suggestions or has had a similar problem that they resolved?
rev3la7ion said:
I'm on the AT&T network and can't send texts anymore after flashing to ICS. I can make calls and use my data plan but am unable to send SMS for some reason. I've tried almost every APN setting recommended by others and still nothing. Does anyone have any suggestions or has had a similar problem that they resolved?
Click to expand...
Click to collapse
Correction. I can receive text messages but not send them.
*UPDATE 9/11*
So I found out the issue is related to the Message Center which you can access from "Messaging" -> hit the option button -> Settings.
After flashing to ICS I noticed that this option has been removed so I can't edit the message center. Are there any ICS or JB ROMs that still have this option available to the user? I need to change the message center number back to what it needs to be in order to send SMS texts.
27 views and no responses? Anyone?
After a BUNCH of research I finally found out how to fix this. Instead of posting a to the thread I found (since I'm still under 10 posts) I will post my copied instructions.
Go to google and search for your SMS center number which should be based on the carrier you have.
Next, go to twit88.com/home/utility/sms-pdu-encode-decode
Scroll down to where you see SMSC, Receiver, and Alphabet size.
Put in the entire SMSC number, including the + sign into the box, leave receiver blank, change the Alphabet size to 8, and delete whatever is in the message box under Alphabet and hit Convert.
Now, on your phone go to the Phone info menu described above and scroll to the bottom and find the SMSC field.
Enter the first 16 numbers into that field and hit update.
Reboot your phone and you can now send SMS.
This fix is for people who have the proper modems flashed on there phones and can still receive texts but not send them.
Related
Hi! I'm using the stock sms app. I have had zero trouble before with messages, but a couple of days ago my messages wouldn't just get sent. I can receive fine, but afted sending an error only pops up saying message not sent. I believe this is some sort of problem with my smsc number, because when I use Go SMS and type in my smsc number manually, I can send messages fine. Calls and internet are working.
When I call *#*#4636#*#* and go to phone information, the smsc box is empty and if I hit update, it just comes up with an error.
I think I accidently pressed update before this problem came up and the box said 00. Any help would be very much appreciated because I prefer the stock sms app to 3rd party ones.
Lookinen said:
Hi! I'm using the stock sms app. I have had zero trouble before with messages, but a couple of days ago my messages wouldn't just get sent. I can receive fine, but afted sending an error only pops up saying message not sent. I believe this is some sort of problem with my smsc number, because when I use Go SMS and type in my smsc number manually, I can send messages fine. Calls and internet are working.
When I call *#*#4636#*#* and go to phone information, the smsc box is empty and if I hit update, it just comes up with an error.
I think I accidently pressed update before this problem came up and the box said 00. Any help would be very much appreciated because I prefer the stock sms app to 3rd party ones.
Click to expand...
Click to collapse
I'm not sure if that is the problem, as my smsc field is empty and I'm not experiencing the same issue. What is your preferred network type?
WCDMA Only, but it seems I got it fixed. I didn't reaize that I had to encode the sms centers number. Working now
Hello
Since "some time", I cannot send SMS text messages from my Nexus S with stock ICS 4.0.3 and also not with CyanogenMod 9 v4.0.3 Alfa 20p1. When I try to send a SMS to whatever number, it takes some time (round about 10 seconds) and then I see a red exclamation mark (!) and get a message in the status bar "Message not sent"
My provider (Sunrise in Switzerland) tells me, that they even haven't seen any signs of me trying to send a text message and told me, to make sure that the correct SMS service center (SMSC) number is entered.
As there's no way in ICS to "easily" enter the SMSC, I "dialed" *#*#4636#*#*, went to "Phone Information", scrolled down to SMSC and entered "+41765980000" (without the ", of course *G*). I then pushed "Update", BUT…
BUT then, the field where I entered the number: update error
When I insert this SIM card in a simple, "ancient", non-smartphone Nokia mobile phone, I see that this number is stored on the SIM card and I can send SMS just fine.
Well………
What to do to be able to send SMS text messages again?
Dunno if it's important, but I can receive text messages just fine.
Thanks,
Alexander
I had this same problem last week, and had to encode the SMSC number to get it to work.
I followed the recommendations at http://forum.xda-developers.com/archive/index.php/t-926771.html and got it working.
what Baldar538 said!
I used that same thread posted above the first time. It was not a fun thing, it was easier to just get my girlfriends phone, and copy hers since she has a nexus s to.
Balder538,
thanks to your heads up, I revisted that page and, more importantly, the "Online PDU Encoder and Decoder" listed there and got it to work.
The encoder encoded my "+41765980000" to "07911467950800F0110000910000AA00". Entering 07911467950800F0 worked then just fine.
I can now send SMS again - yeah!
Thanks again,
Alexander
Thanks to Baldar538 for the link to the answer to my problem as well.
For those of you on Koodo, the SMSC phone number for Koodo is 16475800172. But it has to be encoded before it can be put into the SMSC field in the 4636 menu.
After it is encoded, only the first 16 characters are used from the encoded string.
Sooo... If you want to turn the SMS back on for your Koodo phone, put the following numbers in the SMSC field and press the "Update" button.
07916174850071F2
Worked for me.
Here i fix my sms sending problem in moto g4 plus
hello guys. just follow this steps-
●Remove your sim from this phone
●insert/put in other phone
●try to send message any one
●if failed then go to setting and set sms service centre no.
●And after the proccesr try to send message it will be success in another phone
●and last put your sim in ur moto g4 plus and send msg ..now u able to send msgs ?
I use my device for work. I coordinate/schedule jobs in which there are many people who can work certain slots. So, I'll send out one text message to about 75-84 individuals. Then the ones who can work reply. Later, I send out another mass SMS advising of remaining slots to be filled.
My issue is this. In the Android code a section checks for the number of text messages send within the last hour. If you exceed 100 messages - then, Android throws an error for every message afterwards within that hour and the user has to select "OK" to send an SMS. So, at times I have to sit there and select "OK" over and over again for several minutes while the over limit SMS's are sent....
I found an old record on how to fix this issue here.
However, this APPEARS to be an old solution. I was unable to find this setting or the table "gservices" in "/data/data/com.android.providers.settings/databases/settings.db
Does anyone know where this was moved or how to change this setting?
My device is a an LTE Galaxy Nexus.
I'm running AOKP-build 33. But, I would think this setting would be generic to all of the current ICS ROMs.
Thanks for any advice.
BTW - I found some very old posts related to this same issue. Note:
1) Using an app will not address this issue (I use Chomp SMS) as this is coded within Android.
2) Google Voice will not work as it doesn't recognize "groups" for the "to" box.
3) Pulling the battery will just prevent all the texts from going out.
I'm just hoping someone knows where the file/code is located that I need to modify.
All other suggestions will not resolve this issue.
I had this experienced with three different JB roms today. I can send mms (pics) but I can't send plain text messages.
I get the "message not sent" error.
I did a complete wipe, etc. before installing each rom. Any suggestions?
dogg409 said:
I had this experienced with three different JB roms today. I can send mms (pics) but I can't send plain text messages.
I get the "message not sent" error.
I did a complete wipe, etc. before installing each rom. Any suggestions?
Click to expand...
Click to collapse
Does this happen with all text messages, or only ones that go really long?
Have you checked to make sure your APN settings are correct?
[APN][AT&T][MMS][HSPA+] Single APN for HSPA+ Speeds AND MMS - (Updated 8/21)
Ryo Misaki said:
Does this happen with all text messages, or only ones that go really long?
Have you checked to make sure your APN settings are correct?
[APN][AT&T][MMS][HSPA+] Single APN for HSPA+ Speeds AND MMS - (Updated 8/21)
Click to expand...
Click to collapse
It happens with all sms....even when I send "hi" to myself.
dogg409 said:
It happens with all sms....even when I send "hi" to myself.
Click to expand...
Click to collapse
Odd... Did you check the APN?
Ryo Misaki said:
Odd... Did you check the APN?
Click to expand...
Click to collapse
Yeah, I tried and no luck.....I am dumbfounded.
Ive been getting a weird message.. something like
"Android services has noticed you are sending a large number of SMS messages. Do you want to continue" Then it has 2 options..
Allow or Deny..
After it pops up the first time, it comes back after every 2 or 3 messages sent..
Its powered by Jellybeaned AOKP!
I found out some of the ported ROMs removed the message center option entirely under "Messaging" -> Option key -> "Settings". There should be a "Message Center" option which you should set to +13123149810. Since it's been removed from a couple ROMs sending SMS messages will not work. Anyone know of a ROM that still has this option?
rev3la7ion said:
I found out some of the ported ROMs removed the message center option entirely under "Messaging" -> Option key -> "Settings". There should be a "Message Center" option which you should set to +13123149810. Since it's been removed from a couple ROMs sending SMS messages will not work. Anyone know of a ROM that still has this option?
Click to expand...
Click to collapse
Scratch that I found out that from ICS and up they got rid of that option and replaced it with SMS Center which you can get to by opening the phone dialer and typing in *#*#4636#*#* and selecting -> Phone info.
Go to google and search for your SMS center number which should be based on the carrier you have.
Next, go to twit88.com/home/utility/sms-pdu-encode-decode
Scroll down to where you see SMSC, Receiver, and Alphabet size.
Put in the entire SMSC number, including the + sign into the box, leave receiver blank, change the Alphabet size to 8, and delete whatever is in the message box under Alphabet and hit Convert.
Now, on your phone go to the Phone info menu described above and scroll to the bottom and find the SMSC field.
Enter the first 16 numbers into that field and hit update.
Reboot your phone and you can now send SMS.
This fix is for people who have the proper modems flashed on there phones and can still receive texts but not send them.
I have an HTC One S with T-Mobile USA which I've rooted and onto which I've installed CyanogenMod 10.2. Everything is working great except for one thing... I can receive text messages but cannot send them! I've scoured the forums for an answer and I've gone through this process:
- Dialed *#*#4636#*#*
- Went to SMSC option and pressed "Refresh" to display the SMSC number +12063130004
- Pressed Update
And then nothing happens...
I've read that once you click Update, it's supposed to take about ten minutes or so to reconnect the number with your service, but pressing Update just doesn't do anything. I even tried using the PDU number instead and that gave me "update error" in the blank space.
I'm at a loss here. What am I missing?
UPDATE: MMS works but SMS doesn't. This narrows things down slightly.
did you ever fix the problem because i have it now as well