Anyone using Adblock Plus on this phone? I installed that as a replacement for AdAway and now can't receive or send mms. There are numerous posts stating this ad a problem. The solution is apparently to change the Apn mms port from 80 to 8080. However on the D850 the default ATT Apn is not editable. Tried creating a duplicate except for setting the Mms port to 8080 and still can't send or receive mms. Has anyone solved this problem? Adaway messes up too many legitimate referrers with Webkit browsers that can't be fixed by whitelisting them, so I am looking for alternatives
I ended up switching to adaway and haven't had any issues with referrers at all.
You could get your own list from somewhere and manually edit the hosts file.
Related
I have found several posted that refer to Adblock Plus breaking MMS.
I've also read that changing the MMS port from 80 to 8080 may fix the problem.
On a rooted AT&T G3, I cannot change the setting.
I've tried created a nearly identical second APN setting. However, it either doesn't work, or I cannot select it as default.
All I can tell you is that this didn't fix the problem.
Anyone have this combination working? I don't want to give up Adblock, or MMS.
Thank you for any help in advance.
XC
Use AdAway instead
I'm using AdAway. No mms issues here as well. But is anybody else having issues with chrome constantly having to reload with AdAway?
Not that I've noticed.
Hmmm. I'm sure I'll figure out the deal. All I know as of now is it only happens when AdAway is installed. Still better than mms issue though. Lol [emoji13]
Hi guys - It seems my XT1045 just does not want to MMS, either send or receive. I have the AT&T Go Phone Service. I took my SIM out and put it in my iPhone 3gs and MMS works just fine. So it is not the service, but I am sure it is the phone.
I couldn't access the APN settings on the iPhone so I am not too sure of what is being used. I had UnLockIt.co.nz do the APN settings a few years ago. But now I cannot access that site anymore. So like I said, I do not know what the APN settings are.
I have tried different apps like the default app, an app called Messengers, and Handcent SMS, the results are all the same. I have also tried the various APNs for AT&T still with no luck. And I do have Data on, WiFi off.
So I raise the question, does anyone here have the XT1045, AT&T GoPhone Service, and capable of sending and receiving MMS?
Everything else works fine. voice, data, standard SMS, but no MMS.
Thanks,
Brian D
[Solved] Issues with Moto XT1045 and AT&T MMS
After much more research, I find that AdBlock Plus (ABP) may be the reason my MMS is not working. Has something to do with affecting Port 80 which is used by MMS to send and receive picture messages. I disabled ABP and it worked but not all the time. More research was needed.
Found that instead of using Port 80, I needed to change to Port 8080. This also worked. Started ABP and tested one more time. This time it worked. Not sure of the relationship of MMS Port 80 and ABP using/blocking Port 80.
The solution to this issue was to change my APN which is the default created either by the XT1045 based off of the network being used, or AT&T generated the APN. Either way, MMS Port should be 8080.
As the title states I can no longer send or receive mms on att. The only thing I've done is root the phone. I installed Greenify but have since disabled it to make sure that's not the issue. Also I debloated some stuff but did that way before I rooted and way before the mms issue started. I checked my apn settings and nothing seems out of place. I created a new apn and changed the apn protocol from ipv4/ipv6 to just ipv4 per an older thread I found.
When I reboot the phone, all all of the mms will come through and I'm able to send them as well for just a few minutes and then the problem shows again. It doesn't matter which texting app I use either. Tried stock, Textra and handcent. All unique error messages of course but same issue.
Anyone else? Can't find anything similar.
jiggyb21 said:
As the title states I can no longer send or receive mms on att. The only thing I've done is root the phone. I installed Greenify but have since disabled it to make sure that's not the issue. Also I debloated some stuff but did that way before I rooted and way before the mms issue started. I checked my apn settings and nothing seems out of place. I created a new apn and changed the apn protocol from ipv4/ipv6 to just ipv4 per an older thread I found.
When I reboot the phone, all all of the mms will come through and I'm able to send them as well for just a few minutes and then the problem shows again. It doesn't matter which texting app I use either. Tried stock, Textra and handcent. All unique error messages of course but same issue.
Anyone else? Can't find anything similar.
Click to expand...
Click to collapse
Did you turn on your data?
Yes, data works fine.
Sent from my LG-H810 using Tapatalk
Are you running AdBlock? If so, it's blocking ads and your MMS pictures on port 80. Switch your APN settings to MMS port 8080, and your MMS should work again. Had the same issue and took me a few hours to figure it out.
I searched and searched for a while but mostly found complaints but no solid solutions to the issue with MMS failures on Verizon using 3rd party texting apps with the HTC U11. Excuse me for starting a new thread regarding this issue if it's redundant or if it's actually been answered. I just wanted to share what worked for me - and I am also very curious if anyone else actually tried exactly what I did here, just to find that MMS failed later on.
So I use AT&T and just finally switched to my U12+, and my wife is now officially the proud user of my U11 (previous phone was a VZW HTC 10). But she uses Verizon. Phone, data, LTE, VoLTE, SMS (regular text) all seem to work great so far. But then I remembered reading about Verizon ppl having issues with MMS with this phone.
So I basically noticed the APN settings are greyed out and I can't edit or create new ones since they're pulled from the carrier, that is, Verizon. Within the default APN, the MMSC settings are blank. Furthermore, the APN type doesn't even include "mms". C'mon Verizon... (see attached screenshots).
But Textra has advanced options to manually enter the MMSC settings. See other attached screenshot for the settings used. Now her phone is able to both send and receive MMS (pics).
- In case you don't want to view the screenshot - Textra - Settings - MMS:
- MMSC: http://mms.vtext.com/servlets/mms
- MMS Proxy: (leave blank)
- MMS Proxy Port: 80
So my ultimate question is, have any other users who have experienced this problem used this solution, only to find that it failed for no reason later on? Or hopefully, this may help other users; either way, sorry I'm so late to the U11/Verizon party. =D
Thanks.
PS: Also, if it makes a difference, everything is currently working even while heavily modified. Before setting up today, I RUU'ed back to stock with newest as of today firmware (2.42.617.7), flashed latest TWRP, installed Viper 2.2.0, Magisk 17.1, Cleanslate 3.7.17, a few Magisk modules (Enable GMS Doze, Google Framework, YouTube Vanced), AdAway is run and active, and more. I read some people who suspected Magisk or other mods were causing the issues, but it doesn't seem that way to me. Of course, it's reaaaally early to tell!
edit, 5 minutes after posting: also, I'm aware Verizon has also made a lot of progress in the last 12+ months in phasing out CDMA for LTE, so maybe this post is indeed outdated. We also live in NJ, close to Philadelphia, and most of the Tri-State area here is usually really good with most cell providers, so maybe that could be partially why we're having good luck with the U11 on vzw? I dunno, just a thought...
This is one for the search engines since I couldn't find an answer for this out there for this so hopefully this helps someone else.
My MMS messages were suddenly failing to send. I took a look at my logcat and saw that for some reason even though the MMS service was pulling the correct MMSC from the profile, the OkHTTP API was failing to connect to localhost. My only guess is that apparently the MMSC http URL was sending an HTTP redirect to something that my device was resolving to localhost since I could connect to the MMSC with my web browser and ping it successfully by name with a terminal client without it resolving to 127.0.0.1 (localhost). I tried disabling my ad blocker since that's the only thing I could think of that could be causing a DNS resolve to 127.0.0.1, but that wasn't it.
I also knew that my MVNO had updated their MMSC and so I tried adding in a new APN with those settings, with the new MMSC entered both by name and by IP address (note: with OnePlus you always need to specify an MVNO type, in my case GID, for a custom APN to save). From the logcat, I saw that the MMS service was unbelievably still using the grayed out APN profile with the old MMSC, even after a reboot. I verified that my custom APN was in fact selected. I tried deleting the storage from several different phone services, as well as locating and deleting the custom APN file, to no avail.
Finally, I figure out what was going on. OnePlus has an evil APN locking file at:
/system/etc/apns-conf.xml
If an APN name on your SIM matches with an APN name in this file, then you are locked to that APN even if you have defined and selected a custom APN!
So, I made a backup copy of this file first, then I located the grayed out APN profile in this file (search by APN name), deleted it, and rebooted. Looking at the logcat though, I still saw that the phone was not using my custom APN profile!! It turned out that there was a second match for the APN name in this file. I deleted that as well, rebooted, and voila - no more grayed out APN in my APN settings that I'm locked to and can't edit. I verified in logcat that my phone was now using my custom APN profile and now my MMS are working again!
Hope this helps someone else!
Notes:
I'm using the last Oreo/ OxygenOS 5.1.11 for best xPosed support, but I did see on the OP forums that other people were having issues with their MMS and APN grayed out even with Pie on several different OP phones.
Yes, I have an older SIM from my MVNO, but not that old