My wife and I have identical Moto G7 phones. In the last couple of days we've both had problems sending out texts. No problem receiving texts, just sending out.
The texts fail to go out with an error message saying to tap again to try again. But this repeats itself until I turn off the wifi on the phone. Then the text goes out with no problem.
So there seems to be some kind of conflict between data (T-Mobile) and the wlan. This only started recently.
Anyone else see this? Is there a solution?
i have experienced similar issues with the stock google messages app. I hate to say my fix was installing the Verizon messaging app. (I'm on verizon) and it seemed to fix it.
maybeme2 said:
My wife and I have identical Moto G7 phones. In the last couple of days we've both had problems sending out texts. No problem receiving texts, just sending out.
The texts fail to go out with an error message saying to tap again to try again. But this repeats itself until I turn off the wifi on the phone. Then the text goes out with no problem.
So there seems to be some kind of conflict between data (T-Mobile) and the wlan. This only started recently.
Anyone else see this? Is there a solution?
Click to expand...
Click to collapse
I would try a different sms app, I use Pulse
https://play.google.com/store/apps/details?id=xyz.klinker.messenger&hl=en_US
sd_shadow said:
I would try a different sms app, I use Pulse
https://play.google.com/store/apps/details?id=xyz.klinker.messenger&hl=en_US
Click to expand...
Click to collapse
Thanks. Tried Pulse and it does the same thing on both our phones.
It's not the apps. The behavior is new (1 month) and may be a new underlying android or Google services bug. Something todo with the wifi to data handover.
Related
I'm in the UK on O2 and today I sent some SMS and just noticed the last few were stuck at "Sending" and had been that way for hours. I deleted them and tried again. Same problem, regardless of the recipient. So I toggled Airplane mode on/off. Still no luck. So I rebooted. Once the phone came up I got two notifications along the lines of "Unable to send message". I can now send OK.
Now perhaps this was my network playing up but I'd been receiving SMS fine - and making calls - all day. I've never seen this behaviour before and the fact a reboot cleared it makes me wonder if it's a bug with the messaging app.
Has anyone else seen anything like this? Until today I'df been happily sending and receiving SMS with no issues since I got my N4 last Thursday.
rec71 said:
I'm in the UK on O2 and today I sent some SMS and just noticed the last few were stuck at "Sending" and had been that way for hours. I deleted them and tried again. Same problem, regardless of the recipient. So I toggled Airplane mode on/off. Still no luck. So I rebooted. Once the phone came up I got two notifications along the lines of "Unable to send message". I can now send OK.
Now perhaps this was my network playing up but I'd been receiving SMS fine - and making calls - all day. I've never seen this behaviour before and the fact a reboot cleared it makes me wonder if it's a bug with the messaging app.
Has anyone else seen anything like this? Until today I'df been happily sending and receiving SMS with no issues since I got my N4 last Thursday.
Click to expand...
Click to collapse
I'm on AT&T here in the states and I send hundreds of texts a day and have not run into this problem at all. I had one delay with an MMS that sent about an hour after I had initially sent it but other than that, smooth sailing.
rec71 said:
I'm in the UK on O2 and today I sent some SMS and just noticed the last few were stuck at "Sending" and had been that way for hours. I deleted them and tried again. Same problem, regardless of the recipient. So I toggled Airplane mode on/off. Still no luck. So I rebooted. Once the phone came up I got two notifications along the lines of "Unable to send message". I can now send OK.
Now perhaps this was my network playing up but I'd been receiving SMS fine - and making calls - all day. I've never seen this behaviour before and the fact a reboot cleared it makes me wonder if it's a bug with the messaging app.
Has anyone else seen anything like this? Until today I'df been happily sending and receiving SMS with no issues since I got my N4 last Thursday.
Click to expand...
Click to collapse
I ran into the same problem today. Rebooting your phone should get it back working. If not, enter your phone settings by dialing *#*#4636#*#*
Tap on Phone information and scroll down to SMSC:
Click on the Refresh button. You should see a number that looks like this: "+1206XXXX..."
This number is carrier specific.
Me too
rec71 said:
I'm in the UK on O2 and today I sent some SMS and just noticed the last few were stuck at "Sending" and had been that way for hours. I deleted them and tried again. Same problem, regardless of the recipient. So I toggled Airplane mode on/off. Still no luck. So I rebooted. Once the phone came up I got two notifications along the lines of "Unable to send message". I can now send OK.
Now perhaps this was my network playing up but I'd been receiving SMS fine - and making calls - all day. I've never seen this behaviour before and the fact a reboot cleared it makes me wonder if it's a bug with the messaging app.
Has anyone else seen anything like this? Until today I'df been happily sending and receiving SMS with no issues since I got my N4 last Thursday.
Click to expand...
Click to collapse
Me too. Rebooting and updating smsc didn't help. I tried to undo my actions to the extent I could remember but to no avail. For instance, I had disabled various inbuilt services viz. Pinyin, Korean keyboard, cell broadcasting, exchange, email etc. Re-enabled. Zuk. I had uninstalled Contacts+, reinstalled. Again, nada.
But Contacts+ is able to send normal smss. That is definitely intriguing and I would love to figure it out. Can someone assist?
Hi guys.
An issue I noted was that my messages would appear above my friend's messages even though he messaged me first.
Does anyone else have this problem? A reboot seems to temporarily fix it, but I can't seem to pinpoint what exactly causes this. Thanks!
That is a problem that has existed for quite some time. It is something about gtalk displaying messages ordered by received time, but incomming messages use a different time than system time, or something like that. You can check that the messages are sorted by time, but incomming messages have wrong timestamps. It happened to my GFs phone once and the fix was checking (or unchecking) "automatic" in Settings>Date & Time settings. Very weird, I know...
See also https://code.google.com/p/android/issues/detail?id=6434
PS: I don't have a Nexus10 yet, I'm waiting for mine, and never had this problem myself, but I know about this problem on many other phones as you can see in the link above.
garciaw said:
That is a problem that has existed for quite some time. It is something about gtalk displaying messages ordered by received time, but incomming messages use a different time than system time, or something like that. You can check that the messages are sorted by time, but incomming messages have wrong timestamps. It happened to my GFs phone once and the fix was checking (or unchecking) "automatic" in Settings>Date & Time settings. Very weird, I know...
See also https://code.google.com/p/android/issues/detail?id=6434
PS: I don't have a Nexus10 yet, I'm waiting for mine, and never had this problem myself, but I know about this problem on many other phones as you can see in the link above.
Click to expand...
Click to collapse
Never had this problem on my gnex but I thank you.
Had this problem occasionally on my other device as well.
[sent from my nexus 10]
Well as the title says, I've been having issues receiving texts messages on the $30 prepaid plan.
What happens:
-I will randomly not receive a text message, or I will receive it days later(if I turn my phone on after being off all night), or I will receive a message that is one half the current message and one half an old message from days/weeks ago(the are intertwined).
-It happens complete sporadically, no rhyme or reason. It happens at my apartment, while I'm sitting at work, or at the gym. At my lowest signal level I will have 2 bar remaining of "3g" but it's usually around 3 (I'm in Pittsburgh).
What I've tried so far to fix it:
-I had T-mobile swap out for a new sim card.
-I've contacted T-mobile customer service twice. They've "refreshed" my connection to their network, reset my sim, played with my account, etc.
-I'm using Chomp SMS as my messaging app. The issues also occurred when using the stock messaging app.
-I've cleared the cache for both apps.
What I haven't tried and what you may need to know:
-I haven't played with the APN settings all. As far as I know all of those settings are set straight from/by T-mobile.
-I'm not rooted
-I've had this problem intermittently since buying the nexus4 from google in Nov.
-My original nexus 4(which I RMA'ed) also had the problem- looking back I just thought it was the other persons phone. Which makes me believe it's on T-mobiles end, or at least a tweak in an APN setting?
-Zero issues with call clarity, data speeds. All have been perfectly fine.
-It doesn't seem to matter which carrier the person who is sending me the message is on.
Does anyone have any suggestions? Or has anyone else experienced similar issues? I'd like to hope that there's a simple fix that doesn't require me changing to ST and using AT&T but I guess if I have to... I have too. I'm at a complete loss as to what else I could try in order to fix this.
All help, tips, suggestions are welcome. Thank guys!
no44specialk said:
Well as the title says, I've been having issues receiving texts messages on the $30 prepaid plan.
What happens:
-I will randomly not receive a text message, or I will receive it days later(if I turn my phone on after being off all night), or I will receive a message that is one half the current message and one half an old message from days/weeks ago(the are intertwined).
-It happens complete sporadically, no rhyme or reason. It happens at my apartment, while I'm sitting at work, or at the gym. At my lowest signal level I will have 2 bar remaining of "3g" but it's usually around 3 (I'm in Pittsburgh).
What I've tried so far to fix it:
-I had T-mobile swap out for a new sim card.
-I've contacted T-mobile customer service twice. They've "refreshed" my connection to their network, reset my sim, played with my account, etc.
-I'm using Chomp SMS as my messaging app. The issues also occurred when using the stock messaging app.
-I've cleared the cache for both apps.
What I haven't tried and what you may need to know:
-I haven't played with the APN settings all. As far as I know all of those settings are set straight from/by T-mobile.
-I'm not rooted
-I've had this problem intermittently since buying the nexus4 from google in Nov.
-My original nexus 4(which I RMA'ed) also had the problem- looking back I just thought it was the other persons phone. Which makes me believe it's on T-mobiles end, or at least a tweak in an APN setting?
-Zero issues with call clarity, data speeds. All have been perfectly fine.
-It doesn't seem to matter which carrier the person who is sending me the message is on.
Does anyone have any suggestions? Or has anyone else experienced similar issues? I'd like to hope that there's a simple fix that doesn't require me changing to ST and using AT&T but I guess if I have to... I have too. I'm at a complete loss as to what else I could try in order to fix this.
All help, tips, suggestions are welcome. Thank guys!
Click to expand...
Click to collapse
I have had this issue on and off with SMS messages and "Waiting Voice Mail" messages over the years (mostly on pre-smartphones and G1). All you can really do is reboot the phone often (at least once a day). I think it's related to messages sent while your phone has no service, but not 100% sure.
For 3 yrs with a half dozen smartphones I had texting issues with tmo and now on straight talk tmo it is the same thing.
It hasn't been as bad as you seem to have it but there do sometimes seem to be heavy delays.
Has anyone else experienced MMS/SMS sending failures? One day last week I tried sending a MMS to my boyfriend for at least an hour and it kept saying "unable to send retry". I finally gave up, and deleted the message and physically showed him what I was making for dinner later on LOL. Mind you, I had full bars. Now again today I tried sending a regular text message to a friend and same thing, "unable to send retry". At least this time it went through the second try. I never had this issue sitting at the exact same spot ( at work) with my Nexus. I've had other occurrences too and it can get annoying. I am using the default Samsung messenger. Should I download a third party messaging app?
Did you ever fix?
I just started having the same problem with my SMS after the June update. When I try to send a text message it takes a while for it to send or keeps saying "failed to send". Did you ever get it fixed or figure out the problem? If so I am curious as to how.
I have the same failures but only on WiFi. If I turn off WiFi it's not an issue.
Sent from my SAMSUNG-SM-P907A using XDA-Developers mobile app
Yeah I just noticed that too. It only does it when i'm on wi-fi, but it just started doing it after my phone updated with the June security patch. I have always texted while on wi-fi at home and never had a problem until now. Wonder if there's an actual fix where wi-fi doesn't need to be off?
I had the same issue with SMS/MMS on stock app. I called up ATT and they reconnect something, but working fine now
I'm hoping somebody has experienced this before and found a fix and can help me out...
All day I've been struggling to send SMS messages... I'm on 11.0.1.1, magisk rooted, with RICE installed. Everything was working great but today when i woke up, i was unable to send SMS messages...
I'm receiving them, but sometimes they are delayed and i get a few at a time with nothing coming in again for a short time after that, but i've made no changes to my phone in the last 2 days. I've rebooted a few times between then and now (twice yesterday, just because), so i cant really understand why i would just randomly be unable to send text messages or why they are received in bursts like this?
I've gone in and reset my "Wi-Fi, Mobile & Bluetooth" settings from within the reset options, and this appears to fix the issue, but only for a minute or so and suddenly they stop sending again... I thought maybe its the tower, so i used my daughters phone to text my wife and that worked perfectly fine. Immediately before and after, mine wouldnt send.
Any ideas, links, or guidance that might help me figure this out?
Since there's been some updates and no responses to my thread, i wanted to revisit this and see if i'm still the only one on earth with this issue.
The issue seemed to have completely gone away on its own, no idea why or how... But a couple weeks ago i decided to install the update to 11.0.2.2 on my IN11AA. Ever since, my phone will randomly stop receiving SMS messages completely. I can still send, just cant receive. The only way to fix this is to reboot.
Anyone else with this issue? Anyone find a reason for this? A fix perhaps?
PMad said:
Since there's been some updates and no responses to my thread, i wanted to revisit this and see if i'm still the only one on earth with this issue.
The issue seemed to have completely gone away on its own, no idea why or how... But a couple weeks ago i decided to install the update to 11.0.2.2 on my IN11AA. Ever since, my phone will randomly stop receiving SMS messages completely. I can still send, just cant receive. The only way to fix this is to reboot.
Anyone else with this issue? Anyone find a reason for this? A fix perhaps?
Click to expand...
Click to collapse
Seeming this issue doesn't seem to be widespread, could be a carrier side issue?
It's a shame we don't have dual boot capabilities because you could have switched to stock and checked.
Also try a secondary SIM from maybe someone in your household and send using that SIM and see what happens.
I know there are delays after rebooting, I do a lot of magisk module work and every reboot try sending notifications using SMS or some other methods and I get around 3 mins no send or receive but not at the length you do.
LOGMD said:
Seeming this issue doesn't seem to be widespread, could be a carrier side issue?
It's a shame we don't have dual boot capabilities because you could have switched to stock and checked.
Also try a secondary SIM from maybe someone in your household and send using that SIM and see what happens.
I know there are delays after rebooting, I do a lot of magisk module work and every reboot try sending notifications using SMS or some other methods and I get around 3 mins no send or receive but not at the length you do.
Click to expand...
Click to collapse
I just had the issue again yesterday. Wife and I started texting eachother at about 8am, except, i didnt receive any of her messages until 5:30pm when she got home and told me she had been texting me. I rebooted 3 times, which once usually resolves the issue but not this time. I had to go into the settings and reset my WiFi/Mobile/Bluetooth settings, then it worked immediately.
Because of the solutions, i wouldnt think its a sim issue, but im going to test it anyway. I've factory reset a few times in the past and i still get the issue. I've had the issue while rooted and not rooted. Four of us have phones, 3 are Samsung and then there's mine, and mine's the only one with the issue.
PMad said:
I just had the issue again yesterday. Wife and I started texting eachother at about 8am, except, i didnt receive any of her messages until 5:30pm when she got home and told me she had been texting me. I rebooted 3 times, which once usually resolves the issue but not this time. I had to go into the settings and reset my WiFi/Mobile/Bluetooth settings, then it worked immediately.
Because of the solutions, i wouldnt think its a sim issue, but im going to test it anyway. I've factory reset a few times in the past and i still get the issue. I've had the issue while rooted and not rooted. Four of us have phones, 3 are Samsung and then there's mine, and mine's the only one with the issue.
Click to expand...
Click to collapse
What SMS app are you using? I wonder if you have enabled RCS messaging the new Google style messaging? Because maybe it uses WiFi to download some of the SMS, and if your carrier doesn't support it maybe you only receive it when you are on WiFi.
Try on WiFi then try just on mobile data and see if you notice.
I attached a photo check the top setting. Google might be persisting your setting (if you are using Google messages)
Also why don't you and your wife try a simnswap next time you happen and you are both at home, if your wife doesn't receive it then it's sim/network related.
LOGMD said:
What SMS app are you using? I wonder if you have enabled RCS messaging the new Google style messaging? Because maybe it uses WiFi to download some of the SMS, and if your carrier doesn't support it maybe you only receive it when you are on WiFi.
Try on WiFi then try just on mobile data and see if you notice.
I attached a photo check the top setting. Google might be persisting your setting (if you are using Google messages)
Also why don't you and your wife try a simnswap next time you happen and you are both at home, if your wife doesn't receive it then it's sim/network related.
Click to expand...
Click to collapse
I'm using Google Messages, and yes i do have RCS enabled. I dont believe thats the case though because the messages that are blocked are sometimes just an "ok" message. I'm almost always on WiFi though too.
The primary issue with sim swapping with my wife is that we would need to swap sims for up to 2 weeks since sometimes I have no issues for 2 weeks, then i get the issue once or twice a day for three days. The worst part (for me anyway) is that her screen is SHATTERED on her phone (she's using a Note10+) and its hard to see anything, so i've been trying to get her to get a new phone. I think we might be FINALLY upgrading her (after 5 months) to an S21 Ultra, so maybe we'll give that a shot there.
I'm actually wondering if it has something to do with messages for web. I've noticed that the issue only really happens after using that, but.. It doesnt always happen after using messages for web, so it might just be a coincidence.
I'm pretty sure its not Google Messages, or RCS, and fairly certain its not messages for web, because i used to use Signal only, and i still had the issue a few times.
PMad said:
I'm using Google Messages, and yes i do have RCS enabled. I dont believe thats the case though because the messages that are blocked are sometimes just an "ok" message. I'm almost always on WiFi though too.
The primary issue with sim swapping with my wife is that we would need to swap sims for up to 2 weeks since sometimes I have no issues for 2 weeks, then i get the issue once or twice a day for three days. The worst part (for me anyway) is that her screen is SHATTERED on her phone (she's using a Note10+) and its hard to see anything, so i've been trying to get her to get a new phone. I think we might be FINALLY upgrading her (after 5 months) to an S21 Ultra, so maybe we'll give that a shot there.
I'm actually wondering if it has something to do with messages for web. I've noticed that the issue only really happens after using that, but.. It doesnt always happen after using messages for web, so it might just be a coincidence.
I'm pretty sure its not Google Messages, or RCS, and fairly certain its not messages for web, because i used to use Signal only, and i still had the issue a few times.
Click to expand...
Click to collapse
When you say "ok" are you just sending short messages or the suggested replies by Google?
I had problems with auto reply in notifications for a while.
Tbh I just use telegram or signal becuase they don't require being connected to the device directly when using the web/desktop versions.
Yeah swapping for 2 weeks isn't great!
Interesting you had this issue with signal too, sounds like Google cloud messaging (needed for any app push notifications and messaging) is in a standby mode.
You got naptime or servicely installed? Shame no one else is seeing this issue might be easier to diagnose