As many of you who try to flash AOSP/AOKP/CM/MIUI builds know, MMS doesn't like to work on these builds. What the goal of this thread is to finally get it working on our Evo V's. Post any info/findings you've made here!
(SKCM is short for AOSP/AOKP/CM/MIUI in this post)
Things I've found out:
MMS works fine on the Evo 3D counterparts for most SKCM ROMs. For other VM phones with Sprint counterparts (the LG Optimus V for example), the fix is a simple apn-conf.xml change. CM even comes with this change baked into the ROM, and offers support for BOTH Sprint/VM. This fix doesn't work for our phones for some reason though.
Oddly enough, the Sense 3.6/4 ROMs use a different simple fix that actually works on our Evo V- replacing the apns.xml in /res/xml of framework-res.apk does the trick with the one from the stock VM image does the trick. If you try this on SKCM ROM, it doesn't work, and wipes all APN settings for some reason. This also brings me to another point- there is less info in the Sense config. If you go to Messaging>Settings>MMS settings>Connection Settings in any Sense 3.6/4 based ROM, you'll see there are only three pieces of information: Name (SPG), MMSC (http://mmsc.vmobl.com:8088/mms?) and the MMS protocol which is WAP 2.0. The proxy and port are left unspecified.
This is the interesting part- in the CM apns-conf.xml file, there is a lot more information defined- MMS proxy, port, MNC, and MCC. Yet this works for other VM phones, just not ours. There must be some difference between the MMS settings on our phones and other VM phones. Only question is: what is it? And where is it defined in Sense ROMs? Another odd thing: there is no apns-conf.xml in Sense 3.6, nor 4.
If you open up APNs from the Voice Dialer (just say 'APN' into the Voice Dialer), it shows up blank on Sense ROMs. This makes sense, since I believe that menu reads off the apns-conf.xml.
Senseless builds vs AOSP
To clarify- Senseless =/= AOSP. AOSP is from the Android Open Source Project, which is basically stock Android straight from Google. Stuff the Nexus devices run. Also what CyanogenMod and AOKP are based off of.
Senseless is based off of Sense builds (such as the stock Virgin Mobile ROM) from HTC, but with MOST of the Sense elements removed (you'll still notice a few Sense bits, like the Camera app, 3D functionality, etc). Also the reason why Senseless ROMs work perfectly for our phone.
However, it's impossible to truly de-sense a ROM unless you manage to decompile ALL of the code/get source for the Virgin Mobile ROM. Sense is a very large addition to Android, and is pretty much baked in everywhere.
Kind of like a chocolate cookie (the kind that are brown over) compared with something like a chocolate chip cookie- it's impossible to get the chocolate out of the chocolate cookie.
Also the reason why AOSP ROMs are much smaller than the Senseless counterparts- 100MB vs (on average) 450MB.
New information!
-The MMS.apk from ParanoidAndroid 2.5.0 receives MMS now! No sending, but it's a giant step forward!
(SKCM is short for AOSP/AOKP/CM/MIUI in this post)
Things I've found out:
MMS works fine on the Evo 3D counterparts for most SKCM ROMs. For other VM phones with Sprint counterparts (the LG Optimus V for example), the fix is a simple apn-conf.xml change. CM even comes with this change baked into the ROM, and offers support for BOTH Sprint/VM. This fix doesn't work for our phones for some reason though.
Oddly enough, the Sense 3.6/4 ROMs use a different simple fix that actually works on our Evo V- replacing the apns.xml in /res/xml of framework-res.apk does the trick with the one from the stock VM image does the trick. If you try this on SKCM ROM, it doesn't work, and wipes all APN settings for some reason. This also brings me to another point- there is less info in the Sense config. If you go to Messaging>Settings>MMS settings>Connection Settings in any Sense 3.6/4 based ROM, you'll see there are only three pieces of information: Name (SPG), MMSC (http://mmsc.vmobl.com:8088/mms?) and the MMS protocol which is WAP 2.0. The proxy and port are left unspecified.
This is the interesting part- in the CM apns-conf.xml file, there is a lot more information defined- MMS proxy, port, MNC, and MCC. Yet this works for other VM phones, just not ours. There must be some difference between the MMS settings on our phones and other VM phones. Only question is: what is it? And where is it defined in Sense ROMs? Another odd thing: there is no apns-conf.xml in Sense 3.6, nor 4.
If you open up APNs from the Voice Dialer (just say 'APN' into the Voice Dialer), it shows up blank on Sense ROMs. This makes sense, since I believe that menu reads off the apns-conf.xml.
Senseless builds vs AOSP
To clarify- Senseless =/= AOSP. AOSP is from the Android Open Source Project, which is basically stock Android straight from Google. Stuff the Nexus devices run. Also what CyanogenMod and AOKP are based off of.
Senseless is based off of Sense builds (such as the stock Virgin Mobile ROM) from HTC, but with MOST of the Sense elements removed (you'll still notice a few Sense bits, like the Camera app, 3D functionality, etc). Also the reason why Senseless ROMs work perfectly for our phone.
However, it's impossible to truly de-sense a ROM unless you manage to decompile ALL of the code/get source for the Virgin Mobile ROM. Sense is a very large addition to Android, and is pretty much baked in everywhere.
Kind of like a chocolate cookie (the kind that are brown over) compared with something like a chocolate chip cookie- it's impossible to get the chocolate out of the chocolate cookie.
Also the reason why AOSP ROMs are much smaller than the Senseless counterparts- 100MB vs (on average) 450MB.
New information!
-The MMS.apk from ParanoidAndroid 2.5.0 receives MMS now! No sending, but it's a giant step forward!