I find since the 2.1 update (Rogers/x10a) a lot of my SMS are not going through. I keep getting the "message not sent" notification. (THIS IS NOT THE SAME AS 160+ CHARACTERS PROBLEM)
Am I the only one with this problem since the update? If so, hopefully I can get a new phone from Rogers
Have tried the *#*#4636#*#* and looked at the SMSC. Is always blank. Even when SMS is working.
Help?
EDIT: The problem here is Task Killers (ATK, for me). If Auto Kill is set to Aggressive it interfere's with sending SMS. If set to Safe there is no problem whatsoever.
i have the same problem
my rogers canada x10a also has a tiny bit of trouble sending sms messages after the update. i was considering reflashing because of it. i have found that every time i try to send a message that it has to split in to more than one message it fails.
hope this might aid in diagnosis with someone that knows more about this issue.
i haven't tried to play with it enough to recreate the problem consistently but if their standard character cap is different that could cause problems i suppose.
Edit:
i just attempted to recreate my problem for sake of being constructive.
for curiosity sake i went into the 4636 menu first. i should have done this after.
my smsc was also blank so i hit refresh and the field populated with: "+17057969300",145
that doesnt make a lot of sense to me looking like a phone number with too many digits. i dont know what the 145 was about either
i then went on to send a text message to myself starting with 140 chars then 144, 145, 146, 150, 160, and 180
it did warn me after 150 that i was sending 2 sms messages but they all worked
results: inconclusive
gooph said:
my rogers canada x10a also has a tiny bit of trouble sending sms messages after the update. i was considering reflashing because of it. i have found that every time i try to send a message that it has to split in to more than one message it fails.
hope this might aid in diagnosis with someone that knows more about this issue.
i haven't tried to play with it enough to recreate the problem consistently but if their standard character cap is different that could cause problems i suppose.
Edit:
i just attempted to recreate my problem for sake of being constructive.
for curiosity sake i went into the 4636 menu first. i should have done this after.
my smsc was also blank so i hit refresh and the field populated with: "+17057969300",145
that doesnt make a lot of sense to me looking like a phone number with too many digits. i dont know what the 145 was about either
i then went on to send a text message to myself starting with 140 chars then 144, 145, 146, 150, 160, and 180
it did warn me after 150 that i was sending 2 sms messages but they all worked
results: inconclusive
Click to expand...
Click to collapse
Your problem could be because you're with a different carrier. Bell? I know bell has capped at 150 characters I believe. Also, if you are on a different carrier I'm assuming the SMSC are different.
However, I am able to send SMS over 160 characters. Never had a problem with that. It's more of an annoyance. 1/15-20 of my messages doesn't go through. It's just bloody annoying.
paulsandhu said:
Your problem could be because you're with a different carrier. Bell? I know bell has capped at 150 characters I believe. Also, if you are on a different carrier I'm assuming the SMSC are different.
However, I am able to send SMS over 160 characters. Never had a problem with that. It's more of an annoyance. 1/15-20 of my messages doesn't go through. It's just bloody annoying.
Click to expand...
Click to collapse
I have to apologize. i just haven't changed that in my account here yet. i just switched from bell to rogers.
also:
all the random test messages i sent to myself before i posted that worked but i still am having problems sending 2+ sms messages to other people consistently.
I think this issue is related to Rogers' crappy network. Everyone I know on Rogers right now (in London Ont at least) is experiencing the same problem regardless of the device they're using. Damn you ROBBERS!!
I'm having this problem since I updated to 2.1, I can't send more than 160 characters in SMS. If it's more than 160 it fails to send it. Is there any solution to this? TIA
gooph said:
i just attempted to recreate my problem for sake of being constructive.
for curiosity sake i went into the 4636 menu first. i should have done this after.
my smsc was also blank so i hit refresh and the field populated with: "+17057969300",145
that doesnt make a lot of sense to me looking like a phone number with too many digits. i dont know what the 145 was about either
i then went on to send a text message to myself starting with 140 chars then 144, 145, 146, 150, 160, and 180
it did warn me after 150 that i was sending 2 sms messages but they all worked
results: inconclusive
Click to expand...
Click to collapse
THANX I have had problems with sending large (above 160) sms's, after update to 2.1, but then i saw this, and gave it a try, and it worked, so for all others, try the 4636 menu, and hit refresh, helped for me
But But ..........after reboot the same problem again...........grrrr, then what to do!!!???
I know all providers have **** networks but I don't think that this is the problem. Since 1.6 I've NEVER experienced this issue with SMS. But dropped calls and **** reception? Yes.
I don't know if this is a firmware issue or not. Im thinking it is.
This is happening to many people in the UK too since the 2.1 update. So it's certainly not exclusive to your operator but something cocked up in the update.
I even had this problem on 1.6, it happens mainly between me and my girlfriend. Its a nightmare. Sometimes all is ok and others just won't send and sometimes it sends when it says can not send so god knows!!
Sent from my X10i using XDA App
**** sony ericsson .. and rogers
Hi all. I live in Denmark and have the same problem. I amusing CHOMPsms an belived that it was the app that was The problem but i dont think anymore. I can't enter that menu 4636. Help!
Regards Allan
Sent from my X10i using XDA App
I too had this problem on O2 Ireland after the 2.1 Android update.
Simple answer to the problem is that the update screws up one or two lines in the APN on the phone. All you should need to do to sort this out is find out your carriers APN settings and manually input them. As soon as I did this all worked beautifully.
Settings > Wireless & Networks > Mobile Networks > Access Point Names > "Carrier Name" (Internet)
Change this and in theory you should be working again.
DBSS said:
I too had this problem on O2 Ireland after the 2.1 Android update.
Simple answer to the problem is that the update screws up one or two lines in the APN on the phone. All you should need to do to sort this out is find out your carriers APN settings and manually input them. As soon as I did this all worked beautifully.
Settings > Wireless & Networks > Mobile Networks > Access Point Names > "Carrier Name" (Internet)
Change this and in theory you should be working again.
Click to expand...
Click to collapse
But doesn't this only affect the internet usage on the phone? I don't believe this is the same as the SMSC.
On another note, I happened to remove HTC Keyboard from my device as I thought this might be affecting the performance some how. And I don't know if it is a coincidence but my problem is gone.
Also, I noticed with the HTC Keyboard sometimes when I would send a message, the actual message would still be written on the "type message here" field.
2 birds, one stone ???
paulsandhu said:
But doesn't this only affect the internet usage on the phone? I don't believe this is the same as the SMSC.
On another note, I happened to remove HTC Keyboard from my device as I thought this might be affecting the performance some how. And I don't know if it is a coincidence but my problem is gone.
Also, I noticed with the HTC Keyboard sometimes when I would send a message, the actual message would still be written on the "type message here" field.
2 birds, one stone ???
Click to expand...
Click to collapse
If you delete the 145 in smsc and the , you Can send 2 messages but not 3 in one continous SMS. Do not go back when you have done it go directly to the homescreen. By the way I'm also from Denmark... Fu.... S/E
lucifax said:
If you delete the 145 in smsc and the , you Can send 2 messages but not 3 in one continous SMS. Do not go back when you have done it go directly to the homescreen. By the way I'm also from Denmark... Fu.... S/E
Click to expand...
Click to collapse
Hi
My problem was not sending SMS over 160 characters... It was sending them period. I would constantly get "Message not sent" notifications.
I realized the problem. It's not HTC Keyboard, but Advanced Task Killer. I had the setting for Auto Kill frequency set to aggressive. This somehow interfered with sending SMS for my phone. I set it to Safe and it is fine. But if I switch back to Aggressive there is problems.
Hey guys. I'm having a little big problem with messaging on the Vibrant.
When I send SMS to someone, it only sends half of it and some weird square symbols.
Let me try to explain. I'm on threaded view on the Messaging app, and it shows the balloon with the message and "more...". I can click there to read the full message.
The issue is, the person I sent it will only receive the SMS up to that point, followed by some weird squares. I believe it shows this when i try to write more than 80 ~ 85 characters, way lower than the usual 160 limit for SMS. I don't get the More... for incoming SMS, and I receive them full. It only cuts in half the ones I send.
I was on stock ROM, upgraded to JI6 to see if it was fixed but still getting the same issue.
Any ideas why I'm getting this? It's so weird...
Thanks for your attention!
EDIT: As a friend advised me, changing the alphabet to GSM instead of Unicode fixed it. Thanks anyway!
Has anyone been able to successfully send Japanese characters in an SMS using their Atrix?
I've tried 3 or so different IMEs (Simeji, MultiLing, and something else), with no luck. The characters appear and enter fine, but when I hit send, nothing happens...
Also, the characters appear fine in gchat, and emails and such, and are able to send just fine. The only problem is in sending SMS.
I doubt it's AT&T, as the iphone can send and receive said emails, and a buddy of mine is using an HTC EVO, and he is able to send and receive using the same IME (MultiLing) that I'm using... I can even receive his texts in Japanese.
Upon further research, I came up with a thread on code.google.com http://code.google.com/p/android/issues/detail?id=3393 . A random fellow (in post 55) stated that he fixed it by changing the input mode in Messaging-->Settings--> Input Mode to Automatic (or Unicode)...
Now, the Atrix doesn't have a setting for this in the settings menu. Does anyone know if there is a secret registry setting where this could be toggled?
Anything helps!
Thanks,
-Casey
It's AT&T. They strip bits so that all that gets sent are the lower 7 bits. Pointing to e-mail doesn't apply, as that's a completely different protocol (SMS is the only one piggybacking directly on GSM).
If you take your current phone over to Japan, you'll magically find that you can start receiving texts in Japanese... until you go back to AT&T.
Have fun!
not the case my friend sent me a text in japanese because i am japanese cant read or speak it since i was born here in the states but i used google translate figured out what he said and replied in japanese if u long press the translation it copies and simply paste in text
My Galaxy Note II can receive and send phone calls, I can use data over the 3 network and I can receive texts, but I cannot SEND texts.
My Note II is rooted, unlocked and running Jelly beans rom V5 on the 3 network in Scotland on a pay as you go SIM card. The SIM card works in my other UK phone (unlocked Nexus S), i.e. I can send texts when it's in the Nexus.
I have never been able to send texts with the 3 SIM card in the Note II, (as in this isn't something that was working and stopped, it never worked). My note II was able to send texts when it was on the Verizon SIM in the states.
After I send a text, the "view message info" screen show it as sending to a +44 number and says sent. Several hours later (after the recipient in question never receives the text) I get a text from +441144 (then recipients number) with a message stating " Your text - to - speech message to 01144 (number of recipient) has been rejected by recipient phone."
Calling my +44 contacts works just fine.
I have no idea how to fix this issue. Does anyone have any ideas/ similar issues with their Verizon note II abroad ?
Thank you for your help and time
Using rooted Verizon phone to text on UK three network
I had the exact same problem, three network, using a Verizon S3 with synergy ROM and a hacked APN (as Verizon would not allow APN to be added), I guess you figured that bit out? Using APN Manager Pro running as a system app as set by Titanium Backup Pro.
You also have to make sure you have all the right APN settings, this was done to make DATA work on the phone.
Now the problem you describe is exactly what we had, it's the format of your phone numbers in your contact list, for UK numbers while in the UK, you DO NOT use the +44 or 44... just enter the number as normal 0745 xxx xxx etc... and that fixes the problem. Btw It's quicker to log into your gmail account and edit all of your phone numbers in there, presuming you use Gmail to sync your contacts and not verizon backup as that won't work over here when off their network.
This does cause another problem though, if you happen to use Viber, then viber will not see the contact, so what you do for that is add ANOTHER entry in the same contact, so I use the WORK field, and you enter +44 745 ... you must have the + in there and you must drop the zero, this way normal text works using the MOBILE entry in UK format, and Viber can see the contact in thge WORK entry... all appears to work doing this.
I know it's off topic and you may not use viber, but if you do, then your USA contacts would have to change your phone book entry to +44 745 xxxxxx again including the + and international country code and they can then see you as a viber contact. To see my USA contacts I changed my entries to +1 xxx xxx xxxx, so an orlando number might be +1 407-999-9999 then Viber can see the contact, just use multiple entries within the same contact, there are plenty of fields available.
Hope all of this helps, took some time to figure it all out
Mark
Melian06 said:
My Galaxy Note II can receive and send phone calls, I can use data over the 3 network and I can receive texts, but I cannot SEND texts.
My Note II is rooted, unlocked and running Jelly beans rom V5 on the 3 network in Scotland on a pay as you go SIM card. The SIM card works in my other UK phone (unlocked Nexus S), i.e. I can send texts when it's in the Nexus.
I have never been able to send texts with the 3 SIM card in the Note II, (as in this isn't something that was working and stopped, it never worked). My note II was able to send texts when it was on the Verizon SIM in the states.
After I send a text, the "view message info" screen show it as sending to a +44 number and says sent. Several hours later (after the recipient in question never receives the text) I get a text from +441144 (then recipients number) with a message stating " Your text - to - speech message to 01144 (number of recipient) has been rejected by recipient phone."
Calling my +44 contacts works just fine.
I have no idea how to fix this issue. Does anyone have any ideas/ similar issues with their Verizon note II abroad ?
Thank you for your help and time
Click to expand...
Click to collapse
I'm having this problem too, on a Samsung Galaxy Stratosphere 2 that I imported from America (it's got a slide-out keyboard, we don't have them over here), also rooted and running on the three network.
I've changed all my +447 contacts to 07 but texts only send successfully when I start a new conversation and pick the 07 recipient. When they text me back the number at the top changes to +447 again and I can't reply without starting a new conversation.
Any tips?
possible workaround
I've installed Handcent to replace the stock sms app and it seems to be working well so far. As far as I can tell, replies are successful and the number doesn't default to +44
So I'm running the latest official cyanogenmod snapshot (2014-11-12 m12). Everything's been working great, except that half the time it doesn't send my texts.
I haven't had any problems receiving SMS or MMS, but after sending one text I lose the ability to send more (only tried sending SMS tho).
By default I use Textra, but the problem affects any texting app. For example, I just switched to the stock Messaging app and sent 3 test SMS texts... Only the first one sent. The other two got "Error: -1" under Details.
Another thing to note is that I don't get wireless signal in some areas that I used to... Normally I'm in Global Mode and switching to other modes doesn't seem to help.
Any ideas? Thanks in advance.