Related
I found out I was in a VoLTE market a couple of months ago when I was using the MLG 4.4 link and AT&T's "nxtgenphone" APN worked. Official 4.4 used the phone APN and I left it alone. About a week ago S Voice stopped working when I was using AT&T data but continued working fine over Wi-Fi. I pulled my hair out resetting S Voice and trying different versions; even the one from the SGS5. It still wouldn't work. I manually input the nxtgenphone APN and it started working again. So if you're having trouble with S Voice and are in a VoLTE market you might want to change/update your APN.
BarryH_GEG said:
I found out I was in a VoLTE market a couple of months ago when I was using the MLG 4.4 link and AT&T's "nxtgenphone" APN worked. Official 4.4 used the phone APN and I left it alone. About a week ago S Voice stopped working when I was using AT&T data but continued working fine over Wi-Fi. I pulled my hair out resetting S Voice and trying different versions; even the one from the SGS5. It still wouldn't work. I manually input the nxtgenphone APN and it started working again. So if you're having trouble with S Voice and are in a VoLTE market you might want to change/update your APN.
Click to expand...
Click to collapse
im betting that is what my issue is, can you give me the settings so I can make this apn?
BarryH_GEG said:
I found out I was in a VoLTE market a couple of months ago when I was using the MLG 4.4 leak and AT&T's "nxtgenphone" APN worked. Official 4.4 used the phone APN and I left it alone. About a week ago S Voice stopped working when I was using AT&T data but continued working fine over Wi-Fi. I pulled my hair out resetting S Voice and trying different versions; even the one from the SGS5. It still wouldn't work. I manually input the nxtgenphone APN and it started working again. So if you're having trouble with S Voice and are in a VoLTE market you might want to change/update your APN.
Click to expand...
Click to collapse
EDIT
Here's the Nxtgenphone APN...
I was just out of town in a non-VoLTE market and had to go back to the phone APN. When I got home, I changed to the nextgenphone APN but S Voice wouldn't work again. I have a Gear and I had to completely reset it along with removing Gear Manager in order to get S Voice working again. So whatever's trashing S Voice may have something to do with the Gear, VoLTE, or both. Not having S Voice on your phone over AT&T's data lines (vs. WiFi) pretty much renders the Gear useless. Do any of you having issues also have a Gear running off your phone?
BarryH_GEG said:
EDIT
Here's the Nxtgenphone APN...
I was just out of town in a non-VoLTE market and had to go back to the phone APN. When I got home, I changed to the nextgenphone APN but S Voice wouldn't work again. I have a Gear and I had to completely reset it along with removing Gear Manager in order to get S Voice working again. So whatever's trashing S Voice may have something to do with the Gear, VoLTE, or both. Not having S Voice on your phone over AT&T's data lines (vs. WiFi) pretty much renders the Gear useless. Do any of you having issues also have a Gear running off your phone?
Click to expand...
Click to collapse
Yes. This is what started me on his quest lol. My s voice has been working and then quit which rendered the watch pointless. So I have been trying to fix it for a few days now
I did download the update from here for Svoice,
http://www.sammobile.com/2014/03/24/download-samsungs-s-voice-app-from-the-galaxy-s5/
That seemed to help a bunch with the Svoice issues. But my phone still gets kicked off LTE and stuck at 4g where others that use ATT still show LTE. I can restart my phone and I will then have LTE service.
raiu said:
I did download the update from here for Svoice,
http://www.sammobile.com/2014/03/24/download-samsungs-s-voice-app-from-the-galaxy-s5/
That seemed to help a bunch with the Svoice issues. But my phone still gets kicked off LTE and stuck at 4g where others that use ATT still show LTE. I can restart my phone and I will then have LTE service.
Click to expand...
Click to collapse
It's an odd problem and not easy to isolate. When S Voice first died I thought it was related to the S Voice app itself. I tried the SGS5 update in your link right before the problem started and thought that was it. So I cleared data in the app via Settings and went back to the factory version and the N3-specific S Voice update that came out a few months ago. Didn't solve the problem - S Voice was fine over Wi-Fi but borked on AT&T data.
I remembered I was in a VoLTE market and tried the nxtgenphone APN and that solved the problem. All three versions of S Voice worked; original, N3 update, and SGS5 update. Everything was fine until I had to use the "phone" APN in a non-VoLTE market. S Voice worked fine until I got home to my VoLTE market and it stopped working again. This time, the nxtgenphone APN didn't help. I cleared data on S Voice again and tried all three versions and S Voice still wouldn't work.
Thinking it might be Gear related I deleted the Gear from BT settings, uninstalled Gear Manager from my phone, hard reset my Gear by long pressing the power button and using recovery, and rebuilding it via reset rather than using "restore" to reinstall my previous apps/settings. For some reason, the original and N3 update of S Voice wouldn't work. The SGS5 version did. At some point in the second "S Voice is broken" repair S Voice started to work on my phone but not the Gear.
So some combination of playing with the APN's, installing different versions of S Voice, and resetting the Gear, S Voice is working reliably again. What a pain in the ass. I'm guessing it's AT&T network related because its the only common denominator in both times S Voice started to fail and using the nxtgenphone APN fixed it the first time.
Same issue here (Samsung Note 3), ATT & Samsung are clueless
There is a significant amount of discussion of this issue in the att forums (I can't post links, but it's at https : // forums.att.com/t5/Android/S-Voice-now-Voice-talk-and-non-Wi-Fi-connection/m-p/4053580#M53935). I've been experiencing this for about four days now. S-Voice suddenly stopped working and returned "I can't find a network connection. Please connect to network and try again." This only happens on the AT&T data network; wi-fi works fine. When I called AT&T tech support last night, they actually knew about this issue but had nothing to offer me beyond the fact that it was a "known issue" and that "Samsung is working on a solution." They gave me the number for Samsung tech support, but those folks were less than helpful. At first, they pretended it was an issue with my phone and said I should send it in for repair. He said that there were no other reports of this issue from other users.
Then, when I mentioned that this issue is all over the Internet, the guy said "Well, we have had a 'significant' number of complaints about this, but not a high number." Every time I asked a question ("Do you have an SLA for a resolution?"), he put me on hold for five minutes and came back and asked irrelevant questions. ("So, you say this happened because of a software update?" "No, YOU said that.")
Finally, he said it was an Android issue and that Google is working on a fix.
I have downloaded the S5 version of S-Voice: apart from the ugly colors, it behaves exactly the same as the Note 3 version (i.e, works on wifi and does not work on the mobile network). I also tried changing the APN per the screenshot in this thread, but that did not change the situation.
As a workaround, I'm currently using "S for Switch Voice" (a buggy little app that switches to Google Search every time S-Voice is opened), but I'm really hoping this is fixed soon. Right now, all I'm seeing is finger pointing.
Avi-J said:
There is a significant amount of discussion of this issue in the att forums (I can't post links, but it's at https : // forums.att.com/t5/Android/S-Voice-now-Voice-talk-and-non-Wi-Fi-connection/m-p/4053580#M53935). I've been experiencing this for about four days now. S-Voice suddenly stopped working and returned "I can't find a network connection. Please connect to network and try again." This only happens on the AT&T data network; wi-fi works fine. When I called AT&T tech support last night, they actually knew about this issue but had nothing to offer me beyond the fact that it was a "known issue" and that "Samsung is working on a solution." They gave me the number for Samsung tech support, but those folks were less than helpful. At first, they pretended it was an issue with my phone and said I should send it in for repair. He said that there were no other reports of this issue from other users.
Then, when I mentioned that this issue is all over the Internet, the guy said "Well, we have had a 'significant' number of complaints about this, but not a high number." Every time I asked a question ("Do you have an SLA for a resolution?"), he put me on hold for five minutes and came back and asked irrelevant questions. ("So, you say this happened because of a software update?" "No, YOU said that.")
Finally, he said it was an Android issue and that Google is working on a fix.
I have downloaded the S5 version of S-Voice: apart from the ugly colors, it behaves exactly the same as the Note 3 version (i.e, works on wifi and does not work on the mobile network). I also tried changing the APN per the screenshot in this thread, but that did not change the situation.
As a workaround, I'm currently using "S for Switch Voice" (a buggy little app that switches to Google Search every time S-Voice is opened), but I'm really hoping this is fixed soon. Right now, all I'm seeing is finger pointing.
Click to expand...
Click to collapse
Unfortunately that doesn't work for us with the galaxy gear or gear 2. What ever happened has disabled the ability to use s voice on the gear and the ability to start calls using your voice.
raiu said:
Unfortunately that doesn't work for us with the galaxy gear or gear 2. What ever happened has disabled the ability to use s voice on the gear and the ability to start calls using your voice.
Click to expand...
Click to collapse
Have you completely removed the Gear from your phone and reset it using recovery? That's what fixed it for me the second time I had the issue. It only works with the SGS5 version of S Voice though.
BarryH_GEG said:
Have you completely removed the Gear from your phone and reset it using recovery? That's what fixed it for me the second time I had the issue. It only works with the SGS5 version of S Voice though.
Click to expand...
Click to collapse
mine works with the s5 svoice app update
raiu said:
mine works with the s5 svoice app update
Click to expand...
Click to collapse
I hate the SGS5 version of S Voice; especially in driving mode which I use a lot. It disables saying "Hi Galaxy" when the device is off which I also used heavily. I tried to downgrade again but you're right, the SGS5 version of S Voice is the only one that works. Hopefully a bunch of AT&T employees with N3's complain internally and AT&T's dev group gets off their asses and works with Samsung's dev group on a real solution.
BarryH_GEG said:
I hate the SGS5 version of S Voice; especially in driving mode which I use a lot. It disables saying "Hi Galaxy" when the device is off which I also used heavily. I tried to downgrade again but you're right, the SGS5 version of S Voice is the only one that works. Hopefully a bunch of AT&T employees with N3's complain internally and AT&T's dev group gets off their asses and works with Samsung's dev group on a real solution.
Click to expand...
Click to collapse
check the galaxy app store there a SE update and an Svoice update and it now works on ATT data
raiu said:
check the galaxy app store there a SE update and an Svoice update and it now works on ATT data
Click to expand...
Click to collapse
Thanks for that. I saw the security update yesterday but didn't think it would solve the problem so didn't play with S Voice after I installed it. AT&T must have done something security permissions wise on their network otherwise all carriers would have had S Voice issues which we know isn't the case. The S Voice app in Galaxy Apps is the one and only update the N3 received in January so that's not what fixed the problem.
Hi All.
Have my MXP on Verizon. Love it. However, I'm currently having some issues - I can't get MMS when I'm on wifi - I get notifications for the messages, and then get "failed to retrieve message" and then it just never shows up.
I'm using the stock messenger app.
I know textra has an option to "fix" T-Mobile (where this happens apparently), but I don't really want to use that because it uses a different text message database than the standard one, so I can't launch tasker events based on SMS/MMS when I use it.
I have unlocked the "secret" menu and enabled HD calling, and I switched my "preferred network type" to LTE/CDMA (since I'm on Verizon) in an effort to allow voice and data concurrently. It seems to be working. Not sure if this causes an error when I'm on wifi.
I also have Adblock Plus. Per this thread I just changed my APN to set MMS port to 8080; I'll see if that affects anything when I get home.
However, as I have not tested this, I am wondering if anyone else has this problem? As I type this, I'm now thinking that I may only see this when sending messages to/from iPhones ... I'll do more testing tonight and update, but I'm hoping someone sees this and is like, "Oh, I know exactly what it is ...."
EDIT:
So this didn't fix anything. I have to turn wifi off to get mms. REALLY ANNOYING. Anyone at all see this and have any solutions? Anything?
Thanks.
never had problems since day 1 if I was on wifi or not to send MMS. Maybe try factory reset.
To my knowledge, you can't get regular MMS over WiFi. You have to have your phone data on too. I have found no solution to automatically turn phone data on when a text comes in. Every solution I found doesn't work for Lollipop.
i just got the same thing but after i updated to 6.0 so figured it was because of the update
So I have cellular data on and wifi on. I don't know if there's a setting I'm missing that turns data off automatically when connect to wifi ... anyone know anything about this?
Either way, if I'm on wifi, I get no MMS whether using default messaging app or hangouts.
There is a know issue with any app that accesses the MMS database on 6.0 ....ie Pushbullet.
Let me see if I can find a link
Found it...
http://www.androidpolice.com/2015/12/09/android-6-0-1-fixes-the-annoying-failed-mms-bug-in-marshmallow/
So I recently upgraded from my Nexus 6 to the 6P. Fantastic upgrade, except that there seems to be the issue I mentioned in this thread title.
Whenever I'm on LTE my MMS messages / group messages come in just fine. But whenever I'm connected to WiFi -- either at home or at work -- I'll get the blinking LED notification that I've received an MMS message and sometimes see the "Message is Downloading" placeholder, only it won't ever download. I physically have to disconnect from Wifi, and then the message will roll in a few moments later.
A few specs to hopefully help out: - T-Mobile user, phone is stock but unlocked/rooted. I've flashed a different kernel (Franco) but that's it. I live in Los Angeles, and this wasn't an issue with the old N6, but first made it's ugly appearance on the 6P. Wi-Fi calling is always on and preferred. I can literally pop my SIM out and into the old phone, and the MMS will send/receive just fine. It appears to be a 6P problem. I've tried disabling WiFi Calling but it doesn't resolve the issue.
ADDED NOTE: I primarily use Messenger, but I switched to Hangouts to see if it rectified the problem. Same problem persisted. Same with Textra.
I've had experience with flashing other ROMS/radios on the old N6. I'm hesitant to change to a different ROM because I'm pretty happy with how the phone is working with stock, and everything I change can basically be done with Nova Launcher.
I've downloaded the older radio files, and was ready to attempt flashing one of those, but it's very different with this new TWRP 3.00+ and different partitions. My confidence with that has vanished with the new 6.01 partition stuff. If this is a potential fix, any help in that area would be appreciated.
I've also changed and fiddled with the APN settings, hoping the change might improve the MMS issue. It hasn't. I'm using the suggested T-Mobile APN settings that pop up when searching for this issue.
I've been debating switching to Project Fi, but with the absolute reliance on WiFi this hiccup has given me a bit of pause regarding that switch. Specifically because it happens on my home Wifi in Culver City, then the business Wifi in Downtown Los Angeles, across both 2.4ghz and 5ghz wifi bands.
Just looking for any help or suggestions. Thanks!
DigitalRPM said:
So I recently upgraded from my Nexus 6 to the 6P. Fantastic upgrade, except that there seems to be the issue I mentioned in this thread title.
Whenever I'm on LTE my MMS messages / group messages come in just fine. But whenever I'm connected to WiFi -- either at home or at work -- I'll get the blinking LED notification that I've received an MMS message and sometimes see the "Message is Downloading" placeholder, only it won't ever download. I physically have to disconnect from Wifi, and then the message will roll in a few moments later.
A few specs to hopefully help out: - T-Mobile user, phone is stock but unlocked/rooted. I've flashed a different kernel (Franco) but that's it. I live in Los Angeles, and this wasn't an issue with the old N6, but first made it's ugly appearance on the 6P. Wi-Fi calling is always on and preferred. I can literally pop my SIM out and into the old phone, and the MMS will send/receive just fine. It appears to be a 6P problem. I've tried disabling WiFi Calling but it doesn't resolve the issue.
ADDED NOTE: I primarily use Messenger, but I switched to Hangouts to see if it rectified the problem. Same problem persisted. Same with Textra.
I've had experience with flashing other ROMS/radios on the old N6. I'm hesitant to change to a different ROM because I'm pretty happy with how the phone is working with stock, and everything I change can basically be done with Nova Launcher.
I've downloaded the older radio files, and was ready to attempt flashing one of those, but it's very different with this new TWRP 3.00+ and different partitions. My confidence with that has vanished with the new 6.01 partition stuff. If this is a potential fix, any help in that area would be appreciated.
I've also changed and fiddled with the APN settings, hoping the change might improve the MMS issue. It hasn't. I'm using the suggested T-Mobile APN settings that pop up when searching for this issue.
I've been debating switching to Project Fi, but with the absolute reliance on WiFi this hiccup has given me a bit of pause regarding that switch. Specifically because it happens on my home Wifi in Culver City, then the business Wifi in Downtown Los Angeles, across both 2.4ghz and 5ghz wifi bands.
Just looking for any help or suggestions. Thanks!
Click to expand...
Click to collapse
This is not a solution just wanted to confirm the issue on dirty unicorn and with qksms app.
Sent from my Nexus 6P using Tapatalk
wis3m0nkey said:
This is not a solution just wanted to confirm the issue on dirty unicorn and with qksms app.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
It's been this way for me for as long as I've owned an Android device. MMS has never worked over wifi for me....I've owned a Nexus 5 and Nexus 6 as well as some HTC and Samsung devices (quite a few). The only device I've ever owned that it worked on is my Mi Note Pro. Even then, it seems to toggle on mobile data and give it priority over wifi until the message is downloaded. I know this isn't a solution, but just letting you know that this is pretty common.
I've used sprint in the past but am now on T-Mobile
Sent from my Nexus 6P using Tapatalk
skw5115 said:
It's been this way for me for as long as I've owned an Android device. MMS has never worked over wifi for me....I've owned a Nexus 5 and Nexus 6 as well as some HTC and Samsung devices (quite a few). The only device I've ever owned that it worked on is my Mi Note Pro. Even then, it seems to toggle on mobile data and give it priority over wifi until the message is downloaded. I know this isn't a solution, but just letting you know that this is pretty common.
I've used sprint in the past but am now on T-Mobile
Click to expand...
Click to collapse
Yes MMS inherently built to use only mobile data.
However SMS applications have setting along the line: enable data when dealing with MMS.
For e.g.
That's what I mean by not being able to send/receive MMS on WiFi.
What messaging app is that?
Sent from my Nexus 6P using XDA-Developers mobile app
I think that's a T-mobile issue. I used to get it all the time.
I have an Amazon Prime XT1625 on H20 wireless (via AT&T networks) and cannot get the MMS to work. Interestingly, it DID work for a day with the phone in the beginning then stopped working.
Originally purchased back in october. Trying to wipe the AMZN bloat and root the phone I soft bricked it. I followed this thread and unbricked it (http://forum.xda-developers.com/moto-g4/help/soft-bricked-prime-exclusive-xt1625-t3470693/ ). Currently loaded with XT1625-XT1644_ATHENE_RETUS_MPJ24.139 firmware.
The MMS did work the first day and that was it. For the last 3 months no MMS. I have copied both H20 wireless' official recommended APN settings again and again and also tried using the same APN settings from my previous phone (same sim & service), but none are working to either send or receive. H20 wireless customer service eventually gave up and blamed it on the phone saying because it is not an official AT&T phone it works on different MHz - LOL!
Dialed *#*#4636#*#* and messed around with switching "SET PREFERRED NETWORK TYPE" dropdown, cycling through the LTE options (did not perform reboot between each though). Also tried "turning on sms over IMS", but nothing worked.
What's odd is at one point it did work at one point. I do not know if something happened during loading the firmware after the softbrick or something else.
Does anyone have any suggestions on where to start? Of course, I'm hoping it's a hidden switch or menu, but I'm open to reloading new firmware as well. In fact, I was looking to upgrade to Nougat but I see that there are only soaps available and no official release yet, so I wanted to post this first.
Thanks!
Have you tried a factory reset? Sounds like after the soft brick you messed up the MMS service.
GWCAMO said:
I have an Amazon Prime XT1625 on H20 wireless (via AT&T networks) and cannot get the MMS to work. Interestingly, it DID work for a day with the phone in the beginning then stopped working.
Originally purchased back in october. Trying to wipe the AMZN bloat and root the phone I soft bricked it. I followed this thread and unbricked it (http://forum.xda-developers.com/moto-g4/help/soft-bricked-prime-exclusive-xt1625-t3470693/ ). Currently loaded with XT1625-XT1644_ATHENE_RETUS_MPJ24.139 firmware.
The MMS did work the first day and that was it. For the last 3 months no MMS. I have copied both H20 wireless' official recommended APN settings again and again and also tried using the same APN settings from my previous phone (same sim & service), but none are working to either send or receive. H20 wireless customer service eventually gave up and blamed it on the phone saying because it is not an official AT&T phone it works on different MHz - LOL!
Dialed *#*#4636#*#* and messed around with switching "SET PREFERRED NETWORK TYPE" dropdown, cycling through the LTE options (did not perform reboot between each though). Also tried "turning on sms over IMS", but nothing worked.
What's odd is at one point it did work at one point. I do not know if something happened during loading the firmware after the softbrick or something else.
Does anyone have any suggestions on where to start? Of course, I'm hoping it's a hidden switch or menu, but I'm open to reloading new firmware as well. In fact, I was looking to upgrade to Nougat but I see that there are only soaps available and no official release yet, so I wanted to post this first.
Thanks!
Click to expand...
Click to collapse
Had this issue on both my XT1625 (non Amazon) and my wife's Moto G3. turned out the APN settings were not setup correctly so it was accessing the wrong MMS proxy. AT&T is also who our provider (Consumer Cellular) uses. Check with H2O wireless and find out what your APN settings should be and set them up accordingly.
Make the APN settings match the settings on this page.
https://www.h2owirelessnow.com/mainControl.php?page=dataManualConfig
You also know that MMS probably won't go if you have wifi enabled while sending. Many apps have a T-Mobile setting that disables wifi while sending MMS. For grins, disable wifi then try sending the MMS with just data enabled.
Sent from my SM-T530NU using Tapatalk
Tel864 said:
Make the APN settings match the settings on this page.
You also know that MMS probably won't go if you have wifi enabled while sending. Many apps have a T-Mobile setting that disables wifi while sending MMS. For grins, disable wifi then try sending the MMS with just data enabled.
Click to expand...
Click to collapse
This worked: disabling wifi allowed the MMS to send.
Is this a moto g4-carrier specific problem, or universal problem? Is there a work-around to enable both MMS and wifi simultaneously?
GWCAMO said:
This worked: disabling wifi allowed the MMS to send.
Is this a moto g4-carrier specific problem, or universal problem? Is there a work-around to enable both MMS and wifi simultaneously?
Click to expand...
Click to collapse
It's not a G4 problem, it's more the app and I use Textra SMS for that reason but there are several that you can use. You can try that or Chomp which is by the same developer and I believe both are free to try. I actually purchased Textra because I just like the features more. In the MMS settings for both there is a setting called T-Mobile Fix. What it does is when an MMS is coming in or when you're sending one, it will turn off the wifi, send or receive the MMS and then turn wifi back on. I've seen that setting on other SMS apps also.
Tel864 said:
It's not a G4 problem, it's more the app and I use Textra SMS for that reason but there are several that you can use. You can try that or Chomp which is by the same developer and I believe both are free to try. I actually purchased Textra because I just like the features more. In the MMS settings for both there is a setting called T-Mobile Fix. What it does is when an MMS is coming in or when you're sending one, it will turn off the wifi, send or receive the MMS and then turn wifi back on. I've seen that setting on other SMS apps also.
Click to expand...
Click to collapse
Interesting. I haven't seen any issues with WIFI being enabled blocking MMS messages from being sent. I just use the built in Messaging app that coms with opengapps. My wife had an issue on her G3 that prevented her from sending MMS to a group but worked fine for single recipients. It turned out to be APN settings.
But this is good to know should I see any issues in the future.
OK, have had quite the adventure getting this to work.
I did install Textra and selected the "T-Mobile workaround" setting within the app and MMS worked wonderfully. For about one week.
The all of a sudden it stopped working. Phone crashed and upon reboot MMS ceased to work in its entirety.
This got me thinking there must be a conflict somewhere. So I uninstalled Lucky Patcher and HEBF, and lo and behold MMS would send and RECEIVE only upon reboot. Not once the OS was completely booted, but in that sweet spot of 30 seconds after the main screen popped up and the rest of the OS booted. So I'm thinking there is a conflict somewhere. The only other apps I have that require root is Titanium Backup and SuperSU - I don't think these would cause conflict but I suppose I could uninstall and see.
Short of doing a full factory reset, is there some sort of conflict debugging software that I can use to trace the conflict?
GWCAMO said:
OK, have had quite the adventure getting this to work.
I did install Textra and selected the "T-Mobile workaround" setting within the app and MMS worked wonderfully. For about one week.
The all of a sudden it stopped working. Phone crashed and upon reboot MMS ceased to work in its entirety.
This got me thinking there must be a conflict somewhere. So I uninstalled Lucky Patcher and HEBF, and lo and behold MMS would send and RECEIVE only upon reboot. Not once the OS was completely booted, but in that sweet spot of 30 seconds after the main screen popped up and the rest of the OS booted. So I'm thinking there is a conflict somewhere. The only other apps I have that require root is Titanium Backup and SuperSU - I don't think these would cause conflict but I suppose I could uninstall and see.
Short of doing a full factory reset, is there some sort of conflict debugging software that I can use to trace the conflict?
Click to expand...
Click to collapse
I have TB installed and had SuperSU as well when I was on stock. Didn't see any issues with MMS once I got APN setup correctly. Short of doing a factory reset or disabling individual apps you probably don't have any options to find the conflict, if that is the issue.
I ordered my OP8P directly from OnePlus, but my MMS doesn't seem to be working. Anyone else had the issue?
I actually got a message that the settings were not correct, and that the correct ones were being sent to my phone (had never seen that before). I looked at the APN info, and it seems to be correct... based on memory.
I'm on T-MOBILE also and received the same message. The phone had an update so I installed and rebooted the phone. All call,text, MMS, data worked like it's supposed to. Try rebooting?
I have issues when connected to WiFi, message comes in but doesn't download
hschreibz7 said:
I'm on T-MOBILE also and received the same message. The phone had an update so I installed and rebooted the phone. All call,text, MMS, data worked like it's supposed to. Try rebooting?
Click to expand...
Click to collapse
I've tried rebooting. Things are a lot better, but I still have some issues with calling out (can't remember the message... will try and get a screenshot next time). If I immediately try again, the call will go out.
I'm also not seeing any wifi calling. The feature is enabled, but it doesn't seem to be working... even on the "wifi calling preferred" setting.
Just wanted to post an update.... still having issues. MMS pretty much never works with wifi on. For this reason, my wifi is off pretty much all day. It never fails that as soon as I turn it on, a picture or group message comes in.
Also, this does not affect SMS or RCS messages, which appear to come in over data somehow.... just MMS.
Need a fix bad.
I'm having the same issues with T-Mobile. I'm leaving wifi off in the meantime. Hope there is a fix soon.
That was supposedly fixed with the last update. What software version are you on?
Sent from my IN2025 using Tapatalk
Hi, not sure if it would make a difference but I'm using Google messages with the chat features enabled. I never noticed anything unusual though but I live in Louisiana. Sorry to hear that. I know there is an option for mobile and wifi (dual-channel network optimization) that I haven't been using. Anyway I hope this clears up for y'all.
I'm on 10.5.6. I just went to t mobile and got a new sim card.. It didn't resolve the issue.
Use Textra app, go into settings for Textra and it has option for TMobile WiFi, works great
Samuel Holland said:
Hi, not sure if it would make a difference but I'm using Google messages with the chat features enabled. I never noticed anything unusual though but I live in Louisiana. Sorry to hear that. I know there is an option for mobile and wifi (dual-channel network optimization) that I haven't been using. Anyway I hope this clears up for y'all.
Click to expand...
Click to collapse
You really, REALLY had my hopes up. It actually makes sense, but it doesn't work. I tried with both on and off... no luck. MMS messages (both inbound and outbound) are stuck until I turn off wifi.
cwalker0906 said:
Use Textra app, go into settings for Textra and it has option for TMobile WiFi, works great
Click to expand...
Click to collapse
I used to use the Textra app, but really prefer Google Messages for it's web app. I am on the PC all day, so it's aggravating to have to pick up the phone all the time. I've tried MS Your Phone, but it's not as easy to use, or as reliable.
I created a thread with a similar (but opposite) issue to what you're experiencing. A friend of mine with an international 8 Pro on TMO is having the exact issue you are.
https://forum.xda-developers.com/oneplus-8-pro/help/receive-mms-wifi-calling-tmobile-t4088673
Didn't get any help from that but you can try the APN trick for a temporary fix until it's patched for real. I also created a thread on Reddit for this and I think I found the solution. I use Textra, but that alone didn't help. Someone on Reddit told me to disable the stock messaging app, as well as revoke it's permissions to everything. Since doing that I'm no longer having issues. It's only been about a day so we'll see how it goes from here.
Hope I could help!
CosMiiK said:
I created a thread with a similar (but opposite) issue to what you're experiencing. A friend of mine with an international 8 Pro on TMO is having the exact issue you are.
https://forum.xda-developers.com/oneplus-8-pro/help/receive-mms-wifi-calling-tmobile-t4088673
Didn't get any help from that but you can try the APN trick for a temporary fix until it's patched for real. I also created a thread on Reddit for this and I think I found the solution. I use Textra, but that alone didn't help. Someone on Reddit told me to disable the stock messaging app, as well as revoke it's permissions to everything. Since doing that I'm no longer having issues. It's only been about a day so we'll see how it goes from here.
Hope I could help!
Click to expand...
Click to collapse
Duplicating the APN worked (of course, I did the whole thing then swiped back, thinking it would save, grr). I'm guessing it won't last long. It's just as easy to disable wifi for it to send... so weird that you're having the opposite problem.
**EDIT**
Nevermind... it didn't work. I was able to send out with wifi on (which I couldn't do before), but my wife's test message wouldn't download until I disabled wifi.
I had frozen the stock messaging app on day one, with tibu. I thawed it, revoked the permissions, and disabled it via settings this time. No luck "Not sent. Tap to try again".
Anyone find a fix for it yet? I thought 10.5.8 would help but I still can't receive or send MMS on WiFi.
mmad81 said:
Anyone find a fix for it yet? I thought 10.5.8 would help but I still can't receive or send MMS on WiFi.
Click to expand...
Click to collapse
Granted, I haven't done any extended testing yet, but I can send/receive MMS now with wifi connected. I upgraded about 4 hours ago, and this is probably the longest I've ever had wifi on.
Now that you've posted this, I'm skeptical it will last, though.
**EDIT**
Yep. MMS is still broken when on wifi. Geez....
mmad81 said:
Anyone find a fix for it yet? I thought 10.5.8 would help but I still can't receive or send MMS on WiFi.
Click to expand...
Click to collapse
The latest update seems to have fixed it for me. I was also having issues receiving calls. Callers would get a busy signal. The update fixed that as well. Maybe try taking your SIM out, reboot, then put it back in and reboot.
That didn't work. I'm finally getting notifications from my sports app after the 10.5.8 update. Just have to fix the wifi now.
Wifi still dies on me, but not with the ! on the icon. Just no traffic. I had to toggle it. But nowhere near as much as it used to. The MMS issue is the only reason I don't leave wifi on. I was really hoping it was fixed.
Same issue here even with most recent updates. MMS will work 1/10 times over wifi (sending & receiving) but not the other 9 times.
Since the update I've also noticed wifi issues - they may have been there before but didn't notice. Wifi seems to hang, I sometimes see a "!" next to the wifi symbol. In many cases I turn WiFi off and the connectivity issue in whichever app is resolved.
So at this point on TMobile there is no reason to keep wifi on, which is unfortunate because with their "5G" I actually get half the speeds of LTE. ?
BoxyBox said:
Same issue here even with most recent updates. MMS will work 1/10 times over wifi (sending & receiving) but not the other 9 times.
Since the update I've also noticed wifi issues - they may have been there before but didn't notice. Wifi seems to hang, I sometimes see a "!" next to the wifi symbol. In many cases I turn WiFi off and the connectivity issue in whichever app is resolved.
So at this point on TMobile there is no reason to keep wifi on, which is unfortunate because with their "5G" I actually get half the speeds of LTE. ?
Click to expand...
Click to collapse
Pretty much everything you said. I'm really upset and disappointed. I'm actually considering returning the phone and going back to the OP7P. Not even sure what the return policy with them is...