I have a Samsung Galaxy S2 which i am having a really irritating SMs problem with.
My dad lives in Cyprus, when he sends me an SMS i can not reply, when i try it just says 'sending' then 'failed' . In order to get the text SMS to send to him i have to delete the message thread, then start a new message and it will send. Now if he then replies, i will need to delete the message thread again in order to be able to send him a new message.
I do not have this issue with any other contacts that i am aware. The only difference with my dad is that he lives abroad in Cyprus, and all my other contacts are here in the UK. Has anyone else had this issue? Know what causes it? I have deleted and recreated the contact but still the same.
Many thanks.
Do you have your dad's number stored in contacts with country code or not ? I was on the verge of smashing my phone when i was abroad, trying to call persons in my native country and i couldn't because i didn't have numbers stored with country code. Maybe that's your issue too
I think the problem is related to what SMS server your dad is using, I had same issue with my X-girls phone, no one could direct reply to SMS...
Hi, thanks for the replies.
Sp1tfire, i have changed the number configuration around several times, all with no success.
Fritz, this sounds plausible, however this would surely affect other phones replying? I don't have this issue when using my iphone 4 so it only happens from the Galaxy2 at the minute. I will try and use a colleagues Android phone to text him and test it.
Somehow you, or TSP (Telephone Service provider), have inserted a sms mail server address that is not valid.
here in my country, there has been scams, "cheaper SMS, enter this server setting" and stuff like that, so there is a setting on you phone that is wrong.
FRlTZ said:
Somehow you, or TSP (Telephone Service provider), have inserted a sms mail server address that is not valid.
here in my country, there has been scams, "cheaper SMS, enter this server setting" and stuff like that, so there is a setting on you phone that is wrong.
Click to expand...
Click to collapse
Can't be cause of settings, if he can actually send new sms to that number, but he can't reply from the received sms. His settings are correct as long as he can send sms. Must be something else. Are you using default sms app or a third party software ?
Sp1tfire said:
Can't be cause of settings, if he can actually send new sms to that number, but he can't reply from the received sms. His settings are correct as long as he can send sms. Must be something else. Are you using default sms app or a third party software ?
Click to expand...
Click to collapse
I am using the stock SMS app. I have just wiped the phone and installed the KF2 firmware. Going to see if that helps.
Sp1tfire, thats right, i can only reply to him when i delete the existing thread. I can however send new SMS to him no problem, so long as the thread is deleted before hand. Very frustrating as i lose the history every time.
Update, exactly the same on KF2 Firmware.
Ok, so i tried with a friends HTC desire and he has the same issue. also found my brother who has an iphone 3gs is unable to reply to my Dads number. So at least know its no longer just my phone and that it must be something the other end. Many thanks for the help.
Same problem here
When I reply to my girl it says: failed, when i delete the whole thread it goes.
It's only when I text her, all the other contact go fine
On my old sgs I had it to, but only on stock, when I was on CM7 it was OK.
Cant imagine that its something with the other phone i'm sending it to though
Sp1tfire said:
Can't be cause of settings, if he can actually send new sms to that number, but he can't reply from the received sms. His settings are correct as long as he can send sms. Must be something else. Are you using default sms app or a third party software ?
Click to expand...
Click to collapse
I remember in all the previous phones I've had, there's been a setting in the SMSC Settings allowing the user to specify whether or not to "Reply using the same SMSC" (or something along those lines).
If the option is ticked, the phone attempts to reply to the message through the SMSC that the text originally came from (rather than the one set in your handset).
The cause of the error may be because the SMSC overseas does not recognise your phone/SIM and therefore won't allow the replying message to go through.
And perhaps this may explain why deleting the whole thread and restarting a brand new message works - that is, the new message will go through the SMSC that is set in your phone for your own network.
Although, I've had a look through the settings in my SGS2 and can't seem to find that setting anywhere... (doesnt mean it's not there - it could just be that I don't know my phone well enough because I've only had it for a few days ).
I think your dad's SMS configuration settings is forcing you (or any other person he is sending an SMS to) to reply through his operators message centre
Ask him to check his sms settings and disable any such message centre settings from his side. This should solve the problem.
Sent from my GT-I9100 using XDA App
Related
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.
There has been instances where I have sent a message, the message is reported as sent, but the other party does not receive it. This not only happens on the default messaging app but also in Go SMS. This happened on my old ROMS and ever since I've did several wipes and installing new roms but the problem still remains. Is there any way to solve this problem? Is this a problem with my phone then?
Currently on KH3 modem, CheckRom V4, Siyah 2.6.1.
as the problem was there in your older roms too, there seems to be some problem with your network provider, better call them and check your reply center number
bala_gamer said:
as the problem was there in your older roms too, there seems to be some problem with your network provider, better call them and check your reply center number
Click to expand...
Click to collapse
It's unlikely to be the fault of my carrier since thousands of others use it with no problems. Unless my carrier just dislikes the SGS2? Well I'd give them a call tomorrow probably but what does this reply center number do actually?
aqualeris said:
It's unlikely to be the fault of my carrier since thousands of others use it with no problems. Unless my carrier just dislikes the SGS2? Well I'd give them a call tomorrow probably but what does this reply center number do actually?
Click to expand...
Click to collapse
He wasn't saying it's your carrier's fault specifically; but that your phone may be missing the Message Center number in the Messaging app's settings, or the number may be incorrect. The Message Center is how SMS/MMS messages get routed.
Open your Messaging app, go Settings, scroll down to "Message Center". (May be spelled "Message Centre"). If this is blank, then you won't be able to send or receive SMS or MMS messages. Likewise, it may NOT be blank, but it COULD have an incorrect number for your carrier. You should call your carrier and find out what your carrier's Message Center number is and enter it here.
Agree its usually message centre problem try your networks help pages for settings .
jje
Hi,
I recently helped a colleague purchase a Galaxy SIII phone here in China, Guangzhou and made sure I checked the phone over completely before I purchased it.
I've done a search on the forums and check out anything that may be similar, but to no avail.
The problem is:
The phone will not receive any text messages, or at least they don't go through to the messaging app.
Text messages were being received normally for around a week
I disabled a bunch of pre-installed Chinese crap that is unfortunately not un-installable as it's baked into the ROM
It happened once, so I factory reset it, and then tested it. The text messages worked fine
I then disabled the Chinese stuff once again and installed Skype. Just to be sure, I sent more test text messages, and they were all received fine.
Around one week later, here we are, she says that text messages are not being received again.
All other functions of the phone are working. Internet / Edge network, sending texts, Play store, everything. Just not the receiving of texts!
I'm fairly confused as to this behaviour, particularly as it seems the text messages are working for a time limited period.
I had some inklings of what it could be:
- The SIII takes a micro-sim, the shop "manually" chopped the SIM using a cutter. Could this have damaged the SIM and caused this behaviour?
- The phone itself is faulty
- Something is up with the China Mobile settings / network and she needs to call them.
What would be your diagnosis, ideas, solutions XDA'ers?
Further information of any kind is, of course, available on request.
**** My ideas for a fix ****
Root the bastard and get a standard UK ROM on the phone to see if it works. However, I have some concerns. Years ago, when I bought my first HTC desire, when I rooted and put a UK ROM on it, I discovered that my phone was an imported Thai version of the phone and almost bricked it into a reboot loop as the phone didn't like a different regions ROM being loaded on.
I had to go through a convoluted process of making a specially edited SD-card to fool the phone into accepting different ROMS. Is this the case with the Galaxy SIII or have times moved on to more sophisticated means?
Thanks.
GJO
Have you try other messaging apps like Hancent SMS or Go SMS to confirm that msg service is not working?
Or maybe the CSC is causing the problem?
Sent from my GT-I9300 using xda app-developers app
Open the stock messaging app. In its menu go to settings. Check that there is a number recorded under message centre. If not use Google to find the number for the carrier you are with and enter it.
I'm on an unrooted phone with a stock Rom and twice messaging has stopped working. The cause was that this number had spontaneously disappeared.
Sent from my GT-I9300 using Tapatalk 2
Ok, I've tried:
- alternative messaging apps, and they're not picking it up either.
- the message centre number.
When you say CSC? You mean the carrier code? It was bought in China and fitted with a Chinese ROM, but I'll look at the ROM settings and see what it is.
Thanks.
U dial *#1234# then you can see your csc
CSC – (Consumer Software Customization) Refers to the specific country or carriers for that said firmware is being build.
This where it contains the default settings of each specific geographical region, carrier network providers and network data connections.
Sent from my GT-I9300 using xda app-developers app
I am having this problem. It was all working fine then suddenly it stopped. I don't know what could be the cause but I fooled around with the settings, deleted old text messages and then suddenly I received dozens of text messages.
It's like my phone isn't trying to receive any text messages. It can send text messages out but it won't receive any.
I am using Omega 31.1.
Can someone help me out please?
SlimJ87D said:
I am having this problem. It was all working fine then suddenly it stopped. I don't know what could be the cause but I fooled around with the settings, deleted old text messages and then suddenly I received dozens of text messages.
It's like my phone isn't trying to receive any text messages. It can send text messages out but it won't receive any.
I am using Omega 31.1.
Can someone help me out please?
Click to expand...
Click to collapse
I am having this exact same issue. Did you figure out how to resolve yours?
How did you guys resolve this issue?
war eagle said:
How did you guys resolve this issue?
Click to expand...
Click to collapse
I had the same issue,
I changed the Network options from gsm only to "Auto" mode, and apparently it worked for me.
I'm having trouble with my phone's messaging. I can send texts fine, but I can't send any group messages or MMS messages. I've tried unrooting, updating to the newest OTA update, using a third party texting app, and replacing the SIM card. Nothing works. I can't send or receive group messages or attachments. I tried Go SMS Pro, and when I tried to send group messages, it failed, then sent the message individually to each person. When I tried sending a picture, it said the service was not activated on the network.
This got me thinking it might be something with our texting plan, but everyone else in my family can send and receive group messages and attachments without problems. So it's a problem with my phone only. Does anyone have suggestions?
M0rtiferrimus said:
I'm having trouble with my phone's messaging. I can send texts fine, but I can't send any group messages or MMS messages. I've tried unrooting, updating to the newest OTA update, using a third party texting app, and replacing the SIM card. Nothing works. I can't send or receive group messages or attachments. I tried Go SMS Pro, and when I tried to send group messages, it failed, then sent the message individually to each person. When I tried sending a picture, it said the service was not activated on the network.
This got me thinking it might be something with our texting plan, but everyone else in my family can send and receive group messages and attachments without problems. So it's a problem with my phone only. Does anyone have suggestions?
Click to expand...
Click to collapse
might try going into your setting and unchecking fastboot .. read somewhere that worked for others ... good luck
Nope, that didn't work, either before or after a reboot. Any other suggestions?
Had a similar issue. I don't know if its because I'm still locked and unrooted but I recieved an error code when I would try to send messages. I actually had to get o the phone with Big Red and they had reconnect me to another network connection of some sorts. Weird.
Sent from my HTC6435LVW using xda app-developers app
Sorry, what do you mean you had to "get o the phone with Big Red"? You had to carry it back to Verizon?
M0rtiferrimus said:
Sorry, what do you mean you had to "get o the phone with Big Red"? You had to carry it back to Verizon?
Click to expand...
Click to collapse
He missed a 'n', he got on the phone with big red. Aka he called Verizon.
Sent from my HTC6435LVW using xda app-developers app
This has been solved. I switched my number in January, and the service had been disabled then. I was able to get into a live chat with a vzw customer support guy, and he was helpful enough not only to fix MMS, but also group messaging on my phone. It took a couple of hours after trying in vain to put a password in over the phone, but contacting Verizon is the only way to fix this. If you have rooted your phone (as I had previously), and you still have that ugly "tampered" or "relocked" message at the top of the bootloader, Verizon's live chat system is probably your best bet. Even if you haven't rooted your phone, live chat may be faster. You can skip the "reboot, reset, ask other employees for help" routine you'll probably go through if you go to a physical location.
I think I have the same problem too..
When I'm sending a group message .. one of or two of the messages wont send
I have used a variety of wifi texting services like Heywire, Textfree, etc. The problem is that I am assigned a new number. I don't have data, so even though I might explain to people to text me on my mobile carrier's number (I get free incoming) so that I can receive it wherever I am, they always end up getting confused and texting my wifi texting number and then wonder why I don't receive it right away (because I might not be connected to wifi when they send it).
I need an app that can text over wifi (so I can avoid charges) but uses MY phone number. Even if it doesn't actually use my phone number, I don't care. But as long as it forces the person getting the message to reply back to my mobile carrier number.
I tried mysms, as well as ChompSms, etc; but they all charge to send over wifi to users that don't have the app. And What'sApp and others like it forces the end user to also have the app.
The fact that there are apps like mysms and ChompSms that send sms messages over wifi with your own phone number to anyone that can receive sms shows that it's possible.
Does anyone know of a COMPLETELY FREE one?
Oh, and about mysms. It syncs everything together and just fine, for free. I am talking about purely wifi texting (NOT through my carrier... my carrier charges me 10 cents per outgoing text; incoming is free). Here is what I did to try and set it up.
Settings > Websms connectors
Chose: Mysms out
brought to Google Play Store, downloaded Mysms out connector.
Opened Mysms again
Went back to Settings > Websms connectors
Chose: Mysms out
Checked off "Enable mysms out"
Then I went to create a new message to someone, and tried to choose the "Mysms out" option, but it's always greyed out.
Do I need to add credits? Is that why it's grayed out? If I click on "current text rates" in the mysms out settings, it says "The current global text rate is $0.12 (international only).
I took that to mean that the US and Canada is free and that if I was to send texts internationally it would cost 12 cents.
I just want something that is free for basic texting in the US and Canada.
I tried using Beetalk too, but a) I don't understand how to send an sms in the app AT ALL, and b) I downloaded the Beetalk connector for for mysms's websms to send an sms through it (supposedly it will use my mobile number but through wifi only?) but I can't figure out how to sign in. Nothing will work.
For example, when I "sign up" in the Beetalk app, I enter my phone number and my name (which then is my username?) and it sends a confirmation number via text to my phone. I enter the confirmation number and then it logs me in. But in Mysms, I check it off to enable it, and then attempt to enter my username (at least what I think is my username?) and then I've tried the confirmation number as the password, my "BeeTalk ID" as my password... I have no idea. How do I know my username and password? BeeTalk doesn't even require a password. I tried logging out and then clicking "Log on", but then it gets me to do the process over again; phone number, name, confirmation number; then logs me in.
I am SO confused! Any ideas? I tried contacting the developers, but no response to my problems yet.
Can't do it
Found my answer for mysms. No texting to Canadian and American numbers: mysms.com/en/mysmsout
Any ideas on what else I can do?