[Epic 4G Android Development] Sesquipedalian:
GoSMS allows you to manually configure your APN as well, however for me it works fine without manually entering those settings. I may try ChompSMS and see if setting it there allows the default Messaging to properly send and receive MMS.

If you open the APNs Activity (either by a program that opens Activities or using the voice dialer and saying "open APNs"), and then tap "APN2 EHRPD internet", the settings you just posted are correctly configured. To the best of my knowledge, that's where the Messaging app should be checking for it's APN settings.

UPdownLoAD pointed out that checking the Data Programming screen (access on CM via dialer app: *#*#3282#*#*), under Others > MMSC URL, the URL listed it http://mms.mobipcs.com. I don't know enough about the system to explain the difference between that setting and the APN setting. UPdownLoAD also pointed out that those settings cannot be edited in CM, which is something of a known issue.

My first thought was to multiboot to FC09, however for the life of me I couldn't get it to load. I suspect there may be something going on with the JB_BigMem patch that's fouling up multiboot. (Also, the BigMem revert zip did NOT work.) Anyway, I'm not sure if the Data Programming is stored somehow in the radio or if it would simply fix the setting in the multiboot FC09 installation (and be useless when booting back to CM).

My second thought was to fix the setting manually with QPST, however I cannot get the phone into Modem mode. Apparently whatever fix bbelos put in to allow *#*#8778#*#* to work is somehow also not working. I spent about 30 minutes trying to find another way to get the phone into modem mode without using multiboot, and came up empty-handed.

I'm not even sure if the MMSC URL in data programming even matters. Apparently it's possible to send and receive MMS under certain conditions (3rd party software, editing APNs) with the mobipcs URL in data programming. So I don't know. I am beginning to suspect there is something awry in Mms.apk, but I have no idea how to confirm that. I may try some of the alternative Mms.apk's floating around, or an earlier version, or maybe even some that have been modified to support alternate carriers.

So far I'm pretty stumped by this. I don't mind using a 3rd party messaging app, but I would like to know what's going on, especially considering some of the failures have been practically silent. I wouldn't have known I missed some of those MMS messages if I hadn't seen them in the mmssms.db tables.

There have been a few MMS messages that I've simply lost. I've even gone so far as to try to manually retrieve them from the MMSC, but haven't had any luck. I get what appears to be a properly encoded MMS back, and managed to get this PHP application running locally, and modified it to read from the file rather than HTTP POST, but it presented some error trying to parse it. I don't understand the MMS binary format enough to know interpret it. I suspect that the data I got from the MMSC is encoded in some fashion similar to an MMS, but it refers to a file "receive.txt", which perhaps contains data to access the actual MMS and MIME-encoded parts. I've even looked at the Android source for telephony, but there's just a lot there to try and understand. I'm in over my head.

The drawing board now is to look more closely at mmssms.db. There are a number of triggers in there, and according to this XDA post, some of them have bugs. I'm a little skeptical about that, but I should be able to figure that out. I do understand SQL rather well. Unfortunately some of the last posts in that thread indicate problems applying the fix in CM 10.1.

Obviously something is wrong with either mmssms.db, Mms.apk, or some of the telephony source.