[Epic 4G Android Development] labumm:
MMS issues and the "fix"

My MMS probelms resurfaced. Basically images get stuck "sending"--sometimes. Once they are stuck "sending" the only solution was to delete all the stick MMS and resend. This seemed to happen when I was on a weak network connection and was possibly related to switching between wifi and data. But that is just a wild guess.

Anyway I am on CM10-20121228-Nightly. I have been looking at fixes involving various changes to the APNs.

Fix 1 : "open APNs" with voice dialer. Then set up MMS (see post for details)

http://xdaforums.com/showthread.php?t=1756464

Fix 2: Another fix involves applying MMSfix, which just replaces the file: system/etc/apns-conf.xml

http://xdaforums.com/showthread.php?t=1622055

I did not apply fix 2 because that was older and the CM10 apns-conf.xml had a lot more sprint related data. However when I proceeded to fix 1, I opened the APNs and did not see "Sprint". Four entries were there:

APN0 EHRPD ota

APN0 LTE ota

APN2 EHRPD internet

APN2 LTE internet

I don't think any of these are applicable because we are not LTE.

Not seeing and entry called "Sprint", I created a new APN named "Sprint" then followed Fix 1, setting the proxy and MMS proxy the same. And MMS now seems to work.

So what gives with the apns-conf.xml file?

I took a closer look--the entry apn carrier="Sprint" is <!--commented out.--> See below.

<!--<apn carrier="Sprint" mcc="310" mnc="120" apn="Sprint" user="Sprint" server="*" password="*" mmsc="http://mms.sprintpcs.com" authtype="3"/>-->

This line is NOT commented out in the version in MMSfix, so may explain why it works for some.

Is a real fix as simple as changing the settings in this line? (and un-commenting) And do we need two lines: "Sprint ota" and "Sprint internet"?

Sure I could just experiment, but I am hoping that others here will know what parameters are required and valid.

--UPDATE--

FWIW, I edited and un-commented the line above to:

<apn carrier="Sprint" mcc="310" mnc="120" apn="Sprint" user="Sprint" server="*" password="*" mmsc="http://mms.sprintpcs.com" mmsproxy="68.28.31.7" mmsport="80" authtype="3"/>

Consistent with the parameters in the apns-conf.xml from Clean GB in Jan 2012. After I made the change to the file and then "open APNs" and reset to defaults, these values were applied and, well, it works. Note that "Sprint" is now a member of the APNs list and with in that, "proxy" and "port" are both "not set", but "MMS proxy" and "MMS port" have the values assigned in the statement above. I'm not sure if this really solves all the problems some are experiencing with MMS, however it does set up the APNs as in Fix 1. At least it is another data point.

--UPDATE 2--

I was poking around trying to make a flashable zip of the changed file without sucess. Instead I posted a zip of the "trivially" modified anps-conf.xml file. If you replace the original file with this one, them "open APNs" and "reset to defaults", the deed will be done. Alternatively replace the file, then in "/data/data/com.android.providers.telephony/databases/" delete telephony.db and telephony.db-journal, then reboot (from updater-script in Fix 2 flashable zip). I also set the permissions to rw-r--r-- and ownership/group to root to match those of the original file.

here is the md5 hash: C4326A482B9F4A32BE577A9A18947FB2