Related
For T-Mobile users, anyhow.... Found this link elsewhere on XDA, and figured it was worth a repost.... Would put it in the thread, but that 10-post rule keeps me from doing so....
Turns out it is an APN issue preventing the use of MMS reliably.
To start, I couldn't MMS over either data OR wifi, when running Speed Rom 6.5 or 6.0.
Other folks in the Speed ROM DEV thread have the same problem, and there has been much change-ing of MMS apps and so on to try and fix it.
Well... I tried all that, and it didn't work... But this does.
It's based on this article from TMO, but updated for our phones...
1) Delete all APNs other than T-Mobile Data
2) Use the following settings for T-Mobile Data (Case Sensitive)
Name: T-Mobile Data (or T-Mobile US)
APN: epc.tmobile.com
Proxy: <Not set>
Port: <Not set>
Username: None
Password: <Not set>
Server: <Not set>
MMSC: http://mms.msg.eng.t-mobile.com/mms/wapenc
MMS proxy: <Not set>
MMS port: <Not set>
MCC: 310
MNC: 260
Authentication type: <Not set>
APN type: default,supl,admin,dun,mms,hipri
Click to expand...
Click to collapse
Note: For the Username, enter "None" with the keypad. Do not leave it not set.
If your phone or ROM has a field not in the above list, leave it at the default setting.
CM10 Note: Astrisks (eg, *) are not the same as 'Not Set'. The phone will say 'Not Set' if you have it right.
3) Save the APN
Following these instructions WORKS to allow me to MMS *OVER WIFI CALLING AND DATA* for roms that have WFC, when all of the other fixes involving different MMS apps FAILED. Even works on STOCK.
If you want MMS over WiFi Calling you MUST use a SENSE rom with the SENSE WiFi calling App.
The AOSP-wifi-calling-on-CM10 'nut' has not been cracked yet, and CM9 has not been updated with the fixes from CM10.
dcacklam said:
For T-Mobile users, anyhow.... Found this link elsewhere on XDA, and figured it was worth a repost.... Would put it in the thread, but that 10-post rule keeps me from doing so....
Turns out it is an APN issue preventing the use of MMS reliably.
To start, I couldn't MMS over either data OR wifi, when running Speed Rom 6.5 or 6.0.
Other folks in the DEV thread have the same problem, and there has been much change-ing of MMS apps and so on to try and fix it.
Well... I tried all that, and it didn't work... But this does.
Essentially, you have to merge the APNs, following the steps below, and your MMS will work as it should. It's an issue that impacts the stock Sense ROM as well - which is why phones that shipped configured for a separate MMS APN (as mine did) may have issues with MMS-over-wifi on stock firmware too...
Found this link elsewhere.
Following these instructions WORKS to allow me to MMS *OVER WIFI CALLING AND DATA*, when all of the other fixes involving different MMS apps FAILED.
http://support.t-mobile.com/docs/DOC-1976?noredirect=true
There is one thing I did differently - instead of re-writing the 'APN type' line to exactly quote the line in the TMO article, I simply added the comma-delimited items that were not there, while leaving the ones that are on my Amaze but not shown in place...
Eg, I added:
,mms,dun
to the end of the list, rather than removing anything from the list that wasn't in TMO's article... And it works...
Click to expand...
Click to collapse
Very interesting, I'm working right now or else I'd test and confirm it myself. I've always been under the assumption that mms over WiFi was not possible on our Amaze.
Can anyone else confirm this to work? I'm in a WiFi available environment all day so this would be pretty convenient for me.
Also op... Has this fix caused any other issues? Lol seems like with HTC, when you fix one thing - it breaks something else
- HTC Amaze 4G using XDA Venom Premium
TMAC 13 said:
Very interesting, I'm working right now or else I'd test and confirm it myself. I've always been under the assumption that mms over WiFi was not possible on our Amaze.
Can anyone else confirm this to work? I'm in a WiFi available environment all day so this would be pretty convenient for me.
Also op... Has this fix caused any other issues? Lol seems like with HTC, when you fix one thing - it breaks something else
- HTC Amaze 4G using XDA Venom Premium
Click to expand...
Click to collapse
No other issues.
I am able to use both the Sense MMS app recommended in the Dev thread for Speed Rom as a 'fix' (which did NOT work for me), and the ICS/AOSP one.
ETA: Testing further... Having some issues with AOSP MMS app when the Sense one has been deleted...
It just plain works.
I live in a completely DEAD zone for ALL carriers, so WiFi calling is a must-have.
By using these instructions (only one APN for all services, configured as per that article with the change I noted) I went from being UNABLE to MMS *AT ALL* (either sending OR recieving, on WiFi, HSPA(+), *or* 2G/EDGE), to having full MMS capability on any app, regardless of what network tech I was using.
It works both out on the data network AND at my house where WiFi calling is the only way to get service.
HTC Amaze, Speed Rom 6.5, T-Mobile USA
Wow... That sounds pretty awesome and important to MOST of us amazers.
I will get to try this after work and update later tonight.
Thanks in advance man!!
- HTC Amaze 4G using XDA Venom Premium
Further testing...
Last night, after getting this working, I was kind of excited to have it & thought the stock app should have full capabilities alone...
So I deleted the IcedBullet Mms.apk (3.xMB Sense version) and put the ICS one on alone...
This killed my MMS-over-WiFi and the ICS app (from a Nexus system dump) couldn't send MMS but could recieve them...
So I'm going back through and identifying WHAT EXACTLY is required for MMS over WiFi, and in more detail what works...
It seems that Mms.apk has TWO pieces of software inside it - the MMS 'service' that allows 3rd-party MMS clients to send/recieve MMS... And the MMS 'client' (Sense or AOSP)....
With the IcedBullet Mms.apk AND the TMO-recommended APN changes, MMS works over wifi calling and data, with any client app (eg, you can run the AOSP app alongside the Sense one and it will work, Handicent will work, etc...)
Without the IcedBullet (Sense) Mms.apk (e.g. with Mms.apk from the Nexus installed as the primary MMS app), MMS only works over data, and very slowly/poorly...
SO: To make this work, you need:
1) Sense MMS.apk, installed as 'Mms.apk' in your /system/app folder. I am using the 'IcedBullet' version recommended in the Speed Rom DEV thread.
2) You need your APN settings configured as described at the top of this thread, including deleting ALL other APNs other than T Mobile Data
3) Modifications to the above pairing result in partial or complete loss of MMS.
4) The WiFi calling MMS issue on 'stock sense' (and thus all Sense ROMs) is due to phones being shipped with the wrong APN configuration - specifically 2 or 3 APNs rather than one single one.
5) Presumably, the AOSP Mms.apk service process does not support WiFi calling because they are not designed for phones shipped with it. Remember: the Galaxy Nexus did not have WFC in 'stock' - even though IIRC CM9 has 'created' it for this phone. Thus running Mms.apk from an AOSP or Nexus phone produces the Only-Over-Data issue...
I tried this fix and it didn't work for me, but mms is working fine for me on fourth bar even with the tmobile mms APN still in place.
Sent from the morgue.
UPDATE
misfit61871 said:
I tried this fix and it didn't work for me, but mms is working fine for me on fourth bar even with the tmobile mms APN still in place.
Sent from the morgue.
Click to expand...
Click to collapse
For whatever reason, 3rd-party MMS apps are only working for me in data-mode now. Perhaps I made a mistake in my original testing, and thought I had confirmed them on WiFi but they were really going over cell.
The 'sense' app I got from the SpeedRom 6.5 thread, however still does work for me in both Wifi and Data - this is the one I tested and confirmed at my house (which has no cell service at all) when I originally posted this.
I'm attaching the APK that DOES work in both modes...
This has only been tested on SpeedRom 6.5. My phone was previously on stock-HTC ICS. I have not tried to use GO SMS, or any of the clients besides the Stock ICS one, the Sense one attached here, and Handicent.
In my installation, Mms_Sense.apk is renamed Mms.apk and put in /system/app - NOT installed as an app.
The Mms_1_.apk that comes with SpeedRom is removed (note: For other roms, if you're trying to get this working, you probably want to remove the ROM's MMS apk - whatever it is - from /system/app).
And the APN settings are done as per the article.
I can MMS myself, MMS others, and recieve MMS over wifi and data.
I can confirm I am able to receive and send mms over wifi calling after adding the lines into the apn menu. I am only able to do this with the mms.apk from sense as handsent doesn't work. 2 thumbs up on this.
Sent from my HTC_Amaze_4G using xda premium
Oh I'm also on NRG 8/1 stock rom.
Sent from my HTC_Amaze_4G using xda premium
Weather apk
Is there a way to get the weather app working on v7?
Or is there another app I could use for clock/weather app?
Some app I found on the market, only works for one location.
I'm running into another issue, but with sending MMS messages that are empty.
It happened to me on the Version 7.5 and also on the CapcomCE ROM I'm using at the moment.
I can receive MMS messages. But when I send MMS, they send empty messages.
Turns out that I have to use ROOT EXPLORER from the Appstore for the messages to work. The MMS.apk I'm using is the AOSP one that came with the CapcomCE ROM. I opted for this instead of the Sense-MMS when I first installed CapcopCE (it has Aroma option to keep/remove sense and install AOSP version of apps).
Its annoying and frankly it used to work. Was able to send MMS from Sense Gallery App. Now I have to navigate with Root Explorer.
Anyone ever tested this?
ST4321 said:
Is there a way to get the weather app working on v7?
Or is there another app I could use for clock/weather app?
Some app I found on the market, only works for one location.
Click to expand...
Click to collapse
Google Now! does weather by default - not the HTC 'weather clock', but it's 1 tap away...
I use the ICS-stock clock widget (under widgets, does the dots-in-a-circle analog clock)
vmartinez39 said:
I'm running into another issue, but with sending MMS messages that are empty.
It happened to me on the Version 7.5 and also on the CapcomCE ROM I'm using at the moment.
I can receive MMS messages. But when I send MMS, they send empty messages.
Turns out that I have to use ROOT EXPLORER from the Appstore for the messages to work. The MMS.apk I'm using is the AOSP one that came with the CapcomCE ROM. I opted for this instead of the Sense-MMS when I first installed CapcopCE (it has Aroma option to keep/remove sense and install AOSP version of apps).
Its annoying and frankly it used to work. Was able to send MMS from Sense Gallery App. Now I have to navigate with Root Explorer.
Anyone ever tested this?
Click to expand...
Click to collapse
Due to the fact that I'm WiFi-dependent most of the time, and the wifi-calling functionality for MMS is apparently hardcoded into the sense app, I'm kind of stuck on it...
I can confirm that 3rd-party apps still work (including AOSP-style ones from the Market) alongside it - but if you want to MMS while on Wifi you need to use the Sense app.
I have no experience with other roms besides CM9 and Eclipze's SpeedRom
UPDATE: Speed ROM 7.6
NO Messaging works over WiFi under SR7.6 with the AOSP apks in place...
If you want MMS over WiFi on the latest version, you have to REPLACE with the versions from SR7:
Phone.apk
Phonesky.apk
DELETE
Mms_1_.apk
ADD SENSE VERSION OF
Mms.apk
I also replaced Settings and SettingsProvider APKs so I could control WiFi calling...
dcacklam said:
UPDATE: Speed ROM 7.6
NO Messaging works over WiFi under SR7.6 with the AOSP apks in place...
If you want MMS over WiFi on the latest version, you have to REPLACE with the versions from SR7:
Phone.apk
Phonesky.apk
DELETE
Mms_1_.apk
ADD SENSE VERSION OF
Mms.apk
I also replaced Settings and SettingsProvider APKs so I could control WiFi calling...
Click to expand...
Click to collapse
Is SR7 available for download on xda? If not can you show me where to find it so I may extract these files and replace the ones on 7.5 with SR7 files...thank you
HTC Amaze 4G
Unlocked Bootloader
Unlocked CDMA/GSM
SpeedRom 7.5 (Stable)
Faux 4Ext S-On
lsmrfydgaf said:
Is SR7 available for download on xda? If not can you show me where to find it so I may extract these files and replace the ones on 7.5 with SR7 files...thank you
HTC Amaze 4G
Unlocked Bootloader
Unlocked CDMA/GSM
SpeedRom 7.5 (Stable)
Faux 4Ext S-On
Click to expand...
Click to collapse
I have no experience with 7.5 - I went 7.0 to 7.6, but might be stepping back to 7.5 due to some issues...
I'll post a zip later on....
Here are the files from SpeedRom 7, to allow MMS over WiFi on SpeedRom 7.6 (and prob 7.5)....
So far they also seem to be averting the Phone.apk force-close I've experienced on 7.6.
I am still testing APNs and such to get a reliable MMS-over-WiFi solution for these versions, but I did have it working as of the last time I tried it...
File downloads from here: https://docs.google.com/open?id=0B-RdpTUm3qYZNHFxUXE5NWFyZEE
Damn.. not the news I wanna hear.. trying to convert over from sensation 4g.. more more hard for me to move.. Really like the amaze. i'm really reliant on wifi calling and wifi texting.. since signal sucks at my work area.. but got TONS of wifi signal to use.. would be cool if sense mms could send mms chat then i'd be ok with it. Not pretty but at least it works.. I'll try to play with APN setting as well.. so that 3rd party apps can work along side it. At least texting works..
[Cruzer] said:
Damn.. not the news I wanna hear.. trying to convert over from sensation 4g.. more more hard for me to move.. Really like the amaze. i'm really reliant on wifi calling and wifi texting.. since signal sucks at my work area.. but got TONS of wifi signal to use.. would be cool if sense mms could send mms chat then i'd be ok with it. Not pretty but at least it works.. I'll try to play with APN setting as well.. so that 3rd party apps can work along side it. At least texting works..
Click to expand...
Click to collapse
The problem is with AOSP mms not sense mms
The amaze is better that's all you need to know
Sent from my HTC Ruby using Tapatalk 2
I discovered today I only encounter sending mms errors when I've hit my 4G cap with tmobile. Just a thought. Maybe it's trying to send via the wrong bands
Sent from my HTC Ruby using xda app-developers app
I have a rooted, stock rom hox+. Everything great aside from an issue sending/receiving mms. It will be working fine for a little while after boot, then randomly stop working. Rebooting fixes issue. When the issue is occurring, there is nothing to let me know until I find out I never got a mms someone sent, or someone never got mine. Texting app (tried several, they all do it, currently go sms as main) says it sent just fine. When someone sends me a mms, I get the 'download' button, but it tries for a second then does nothing. The problem didn't start occurring until after I deleted the stock sms app. This makes me think deleting it caused the issue.
Unless someone thinks it is something else, I want to restore the default sms app to see if that fixes it. I was stupid and didn't back it up when I deleted it. Is there an easy way to restore the stock sms app? I'd rather not do a factory reset if I can avoid it.
Thanks =D
Can you specified which ROM you are using? Also can verify if your APN's are correctly installed?
If you follow this path : Settings -> click on Mobile Data left part -> Access point names -> APN's
Do you have a black screen with only APN'S & Menu on top? If yes, then you need to create an APN to regain your DATA access.
Who's your service provider?
I am using the stock rom, up to date (4.1.1). APN's are installed and look correct. I'm with AT&T.
Thanks for the help
Lucky Thirteen said:
Can you specified which ROM you are using? Also can verify if your APN's are correctly installed?
If you follow this path : Settings -> click on Mobile Data left part -> Access point names -> APN's
Do you have a black screen with only APN'S & Menu on top? If yes, then you need to create an APN to regain your DATA access.
Who's your service provider?
Click to expand...
Click to collapse
Are you using adblock plus by any chance? I had it enabled and it was blocking all mms messages.
jtrue said:
Are you using adblock plus by any chance? I had it enabled and it was blocking all mms messages.
Click to expand...
Click to collapse
Yes I am, I will look into this and update. Thanks for the suggestion. =D
I seem to be having the same problem, hoping someone can help me out.
I'm running Elegancia 5.2 on AT&T, the APN settings I put in are AT&T HSPA+ (name) and "Phone" (APN). I cannot send SMS messages, not sure about receiving. Thanks in advance.
---------- Post added at 02:42 PM ---------- Previous post was at 02:13 PM ----------
Found a solution here, though I'm not sure if it's optimal for where I live in NYC.
Name: ATT PHONE
APN: phone
Proxy: -
Port: -
Username: -
Password: -
Server: -
MMSC: -
MMS Proxy: -
MMS Port: -
MCC: 310
MNC: 410
Authentication Type: -
APN Type: default,internet
APN Protocol: ipv4
Finally updating about jtrue's suggestion. Tested to see if any adblock apps were causing the issue. Turns out that isn't it.
If anyone has other suggestions please let me know, this is beginning to get very annoying.
To reiterate: mms will randomly not send/receive. I've done everything I know to troubleshoot it, at this point I'm hoping for helpful suggestions in that direction, or a pointer on how to restore the stock sms app (hoping that will fix it).
Thanks in advance for any help.
I have a att compatible SIM in my DNA with working data and calls but no mms, I can recieve but not download the pic and can't send.....please help must be wrong Apn somewhere
I have the same problem and couldn't fix it. I read all over the web and the only solution I could come up with was to get a new Sim. Apparently this worked for some. I use GoSMS now and MMS works. It has lots of themes so I just replaced the stock text messaging app with it.
I keep seeing AT&T is extremely difficult to get MMS working properly on, even T-Mobile can suck getting it working, on anything but AOSP ROMs I had to use GoSMS also.
Sent from my maguro using Tapatalk 2
pio_masaki said:
I keep seeing AT&T is extremely difficult to get MMS working properly on, even T-Mobile can suck getting it working, on anything but AOSP ROMs I had to use GoSMS also.
Sent from my maguro using Tapatalk 2
Click to expand...
Click to collapse
Well guys I found the issue and I'm fixed mms and web work great now. The trick is to call 18553332355 and tell the mms was working and now its not. They will go over the Apn settings and then you have to keep them on the phone, after 30 min they HAVE to get a manager who will then use their "tool" and have you turn your device off for 1 min then everything works great. I had to do this 4 times with 4 devices. Trust me this works . I know its 30 min but if you want a 100% working service this is a must
Name net10
Apn tfdata
Mmsc http://mms-tf.net
Mms proxy mms3.tracfone.net
Mms port 80
All else leave blank
canemaxx said:
Well guys I found the issue and I'm fixed mms and web work great now. The trick is to call 18553332355 and tell the mms was working and now its not. They will go over the Apn settings and then you have to keep them on the phone, after 30 min they HAVE to get a manager who will then use their "tool" and have you turn your device off for 1 min then everything works great. I had to do this 4 times with 4 devices. Trust me this works . I know its 30 min but if you want a 100% working service this is a must
Name net10
Apn tfdata
Mmsc http://mms-tf.net
Mms proxy mms3.tracfone.net
Mms port 80
All else leave blank
Click to expand...
Click to collapse
wonder what the correct apn settings are for att then. i have a chance to get a dna at a good price but have to have mms.
I tried with the default T-mobile AP, which is the old one, and I tried the new one. When neither of those worked, I called T-MO and got their help. They created a new AP using the new settings (fast.t-mobile.com). It also didn't work. Anyone get MMS to work on T-MO?
adding mms to APN type worked for me.
APN Type:
default, supl, mms
Thanks for helping. Didn't work but I appreciate trying.
Here's what I had to do to get it working:
First, reset the APN settings to default.
Then, add mms to APN type.
Next, clear the setting for server.
Then add the mmsc.
Then it worked.
chasmanian said:
Here's what I had to do to get it working:
First, reset the APN settings to default.
Then, add mms to APN type.
Next, clear the setting for server.
Then add the mmsc.
Then it worked.
Click to expand...
Click to collapse
Weird that you had to do anything at all. I got the phone, inserted my SIM, rebooted, went through the setup wizard and was good to go.
Finally!
chasmanian said:
Here's what I had to do to get it working:
First, reset the APN settings to default.
Then, add mms to APN type.
Next, clear the setting for server.
Then add the mmsc.
Then it worked.
Click to expand...
Click to collapse
Worked for me. You rock!
This happened to me when I first used the phone with AT&T as my carrier. AT&T couldn't determine the issue and are still investigating it. I ended up doing a factory reset and it fixed it.
Im having some issues on the subject, that i cannot really figure out..
I have a Asus Padfone X Mini (T00S) and i cannot send MMS texts on the epc.tmobile.com APN,
i have tried messing around adding this and that, but all my attempts to send a MMS have failed
supl,mmsc and everything i have tried failed.
I would appreciate it if you would please send me a screen shot from you apn settings and also explain what is happening
Im fairly new to the APN system
My phone is the Boost Mobile XT1526. Running Cyanogenmod 13 by squid2. The latest build.
I've been using the Boost APN found here, and even though it works, its not ideal. I'd rather use the APN that's built into the ROM or the APN I pulled from the stock ROM.
My problem is that, for the life of me, I absolutely cannot get the APNs to stick. The APN that's built into CM13, doesn't stick. It disappears. And if I manually add the APN I pulled from the stock ROM, that disappears as soon as I hit save. I have no clue why. The only APN I can use is the one I linked to above. But that one isn't ideal. But I'll use it if I have to.
Can anyone help me with this that knows more about this then I do? I'd really love to use either the built-in APN or the APN I pulled from the stock ROM, if its even possible.
I have data so that's not my problem. I just can't send or receive MMS messages using the SMS app in Cyanogenmod.
Thanks!
If anything isn't clear then please tell me and I'll try to explain better. I suck at explaining.
Trying to get it to work too!
I'm having the exact same problems. I think it might be an issue with cellular network settings in CM13/MM roms (you'll notice clicking "Carrier Settings" in any of them causes com.android.phone to stop).
I've been playing around with various things, and I've found so far that using the Cypher rom (which doesn't have any Boost stuff baked in) I can put in the APN settings you linked to and send and receive MMS but LTE doesn't work. I then went back to Squid's CM13 rom (which is amazing, btw!) and LTE appears from install but changing any APN setting makes it fall over. Then I tried editing the Boost APN in deega/Buzbee2's flashable zip from "n.boost.ispsn" to "Boost_Mobile". I could flash that, and that does make it "stick" in the APN settings but, again, LTE disappears when I do this. Entries under the "Access Point Names" tab do seem to appear and disappear somewhat randomly whatever I do!
I've tried various other fixes suggested online, from root-deleting the telephony database to trying some SMS programs that let you put in the APN settings manually, but still nothing. I feel I'm close...but not that close I'll keep fiddling and see what happens but I'm not entirely sure whether this is a settings issue or a CM13 issue.
Thanks for replying. I'm gonna do some testing too. I had the same exact issue on CM12.1 so I don't think its a CM13 issue.
I wonder if there's a way to use adb or fastboot to force the APNs to stick?
I tried using the Boost APN I pulled from the stock ROM that Motorola or Boost put there and you'd think it'll work but no. It disappears as soon as I hit save.
I know CM13 has to be using some kind of APN because I have data, but I don't know what that APN is nor why I can't get the SMS app to use it so I can send MMS messages.
I'm confused but I'll figure it out. Maybe. :/
EDIT: I notice too that whenever I tried to get into Network Operators that com.android.phone would FC. I was able to get in there by putting my phone in airplane mode and rebooting. I can take the phone out of airplane mode while I'm in it without it force closing. But I'm not able to do anything. Kept saying "error while searching for networks" or something along those lines. So I just gave up for right now.
EDIT2: I noticed that in the file /data/data/com.android.settings/shared_prefs/com.android.settings_preferences.xml that it had APN settings in there that were blank for the most part. I tried editing that file to add my APN settings but it didn't help.
I've been testing things during the day and my hunch is there's a deeper problem with the LTE implementation in the 6.x roms (and earlier, perhaps, if you had issues with CM12 as well). It's difficult to know if this is Boost/Sprint related only - Buzbee2's flashable fix seems to be working for people on Freedompop and Virgin. I had a few issues today where my phone would be telling me I had LTE connectivity but web pages would give timing-out errors. I switched to Cypher which was solid on 3G where LTE had basically crashed. I sent MMS with manually inputted settings on Cypher again.
So I was left feeling that at the moment it's a choice between fast (patchy?) LTE speeds without MMS or solid (slow!) 3G with MMS. Hmm. It may be that current roms have a issue switching down and up between LTE and 3G...?
Looking at deega/Buzbee2's flashable zip it doesn't seem like it changes much, so it should be a settings issue, just as long as those settings can stick! Trouble is there might be multiple points of failure at present.
I dug up an interesting thread on the Moto G forum where a user who struggled with this on their phone found that Boost requires authentication for MMS over LTE but not on 3G:
Getting MMS to work on LTE made me pull my hair out. Virgin mobile(Boost) working on Sprint networks when it comes to MMS messages is an over complicated issue caused by the providers. When attempting to receive MMS on LTE networks with stock MMS or some 3rd party MMS apps it returns with a "HTTP error: Authorization Required". When trying it on 3G its no problem. Seems they required "Authorization" for MMS on LTE but not 3G - go figure. Hangouts basically works for all because the app itself doesn't use the phones APN settings. It tries (and does) to attain what carrier you are on and use its settings. In our case it will identify you are on the Sprint network and use those APN settings. Why don't we set our phones to the Sprint settings?...no LTE then.
Click to expand...
Click to collapse
Sounds eerily similar, but his fix file has disappeared into the mists of time and seems to have only worked on certain roms. Anyway, I'll keep digging and hope others might chip in.
I found a file called preferred-apn.xml in the data/data/com.android.providers.telephony/shared_prefs directory where you can set a preferred APN. Least I'm assuming that's what its for. But I need the APN id and I can't find the id for the built-in Boost APN.
I'll keep looking and testing stuff. Hopefully we can get this figured out.
I'm stuck with using 3G where I live. Boost/Sprint doesn't have LTE where I live. So LTE isn't a issue for me.
That's a good find. I think the APN ID refers to the line where you can find the details for the APN in the telephony database. There's some stuff on the Moto G forum about it here.
I'm guessing that the APN settings tab is pulling stuff from the telephony db and that your XML file is telling the phone which is the default. If so, maybe writing to the telephony.db (in the databases folder just along from shared_prefs) might make changes "stick", although if you delete that db it's recreated at reboot so it's not the originator of the data. My feeling is that there's a screwy connection between telephony.db and various other bits of CM13 right now...
Maybe taking telephony.db from a stock Boost rom and copying that in will do something.
I still have a backup of the stock ROM on my laptop. Tomorrow I'll pull the telephony.db and copy it onto my phone replacing the original one and see what happens.
Update:
I pulled the telephony.db from the stock ROM and copied it to my phone, replacing the original and I set the APNs in apns.xml to what I thought the APN should be. I wouldn't recommend it.
As soon as I rebooted CM13 stopped recognizing my sim card and the com.android.phone error popped up and wouldn't disappear. I couldn't do anything. Had no choice but to reboot into twrp and use its file manager to delete the db file. So that's a no go I guess.
I found a program for Linux (also available for Windows) called SQLiteBrowser which let's me open the telephony.db files and look through them. All of the APN IDs are stored in that db file. I'm going to use it to look through the telephony.db file for CM13 and get the APN IDs that I need. Then try to edit the preferred_apns.xml file to set it and see what happens.
EDIT: I'm looking through the telephony.db file from CM13 but there are no APNs in it for some odd reason. Wonder if we can manually add them if need be?
Finally working for me
Buzbee2 made some suggestions on his support thread so I tried them and - to my amazement - everything worked. Not immediately, I had to wait a few hours (for the APNs to be picked up from Boost?) but it did work.
So what I did was first go into airplane mode and entered the Boost_Mobile APN details that you can find everywhere online (and on Buzbee's support thread). When I switched off airplane mode those settings disappeared and those baked into Squid's CM13 (or flashed via Buzbee's zip) came back. Switched on airplane mode again, those disappeared and the Boost_Mobile one I entered and saved is there. I can't believe that's meant to happen, but there it is.
I then downloaded Google Hangouts. I'd heard it sorts out its own APN settings if you set it to be your default SMS program. I could send SMS through Hangouts but still no MMS. I gave up at this point as I had to go out.
Checked my phone a couple of hours later and my MMS sent via Hangouts had arrived. I tried a few more and they all worked. Then I tried the stock messaging app and that could send MMS too! I couldn't believe it. I uninstalled Hangouts (much prefer the simpler app) and went to bed. In the morning, no MMS. Reinstalled Hangouts, still no good. Left it a few hours and - yep! - MMS was back for all my MMS apps. I tested with and without wi-fi, knowing that Hangouts likes shortcuts , and it was all good.
So the moral of the story is...I have no idea. But either Hangouts sets the APNs for the whole rom, or some combination of the Boost_Mobile APN (even though it doesn't "stick") and Hangouts gets it going. Maybe set that up, leave it overnight, and see. It doesn't explain some of the weirdness in the carrier settings, but at least it might work.
I'll try that. ☺
Any luck, Debdude? My phone has not been perfect, with it refusing to switch down to 3G when out of LTE coverage, and MMS mostly sending but sometimes not, but acceptable for something running a cutting-edge rom. It'll hopefully improve as things mature.
davidxd said:
Any luck, Debdude? My phone has not been perfect, with it refusing to switch down to 3G when out of LTE coverage, and MMS mostly sending but sometimes not, but acceptable for something running a cutting-edge rom. It'll hopefully improve as things mature.
Click to expand...
Click to collapse
Damn. I forgot. My bad. I got busy with my new laptop and my ps2 I just completely forgot about this.
I'll mess around with it in a bit. And try the suggestions you mentioned a couple posts back.