• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [PROJECT] Get MMS working on AOSP/AOKP/CM/MIUI builds!

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!
 
  • Like
Reactions: Kahroo and G19
We should have a thread for 3D support as well :p

3D is much harder to get working, simply because that's a driver issue and a lot more in depth haha. :p

If anyone has managed to get it to work on the Boost Ego Design 4G which also has WiMaxx radios then we might just be in business.

Within about 20 seconds of searching, I found this! Apparently they have MMS working! I'm downloading it now to see what kind of changes they made... I'm also going to download a stock image of the Boost Evo Design 4G and see what they did there.

I think it'd also help to see what the devs over on the One V (the closest cousin the Evo V has on Virgin Mobile) have done to get it working.
 
  • Like
Reactions: Dilwann
Upvote 0
1. I didn't see anywhere in that thread they had it working for Boost Mobile. It is setup for USCC.

2. Someone is going to have to get in the code and fix MMS. Moving stuff and changing stuff isn't going to fix it.

3. I AM the dev that got MMS working on the One V. Both CM9/10. It was straight forward and no diff than anything else.

4. I believe the issue to be because of Wimax and that is why MMS won't work using every known method. (Despite belief, I have lost hours/days caught up on MMS)
 
Upvote 0
I'm not sure if this would help but they got a Epic 4G to flash to VM. And that's a Wimax device so maybe doing what they did will get MMS working.

Epic 4G to Virgin Mobile(SMS/MMS/VOICE/3G)*WORKING!* UPDATED:4-23-2012 - xda-developers

Also this found this from here(http://www.groovypost.com/howto/epic-4g-on-virgin-mobile/):
(Optional) Before we get started, if you want MMS (Multimedia Messaging Services) for picture messaging to work you’ll need to flash your Epic 4G to CyanogenMod 7 Nightly 45 Rebuild w/ Fix [Download Link]. Or if you are running CyanogenMod 9 you can just apply this fix.
So maybe that CM9 Fix might help.
 
Upvote 0
Looked into the zip, it basically edits the apn-config.xml file mentioned in OP. and that would be the normal fix. I've trying different methods of applying them to some of JMZ's builds before I flash but no go on MMS still.
Besides different methods being overlooked I'm starting to think JMZ is right and its likely WiMax conflicting in some way when connecting to the virgin mms service.
 
Upvote 0
1. I didn't see anywhere in that thread they had it working for Boost Mobile. It is setup for USCC.

I didn't see any Boost users having issues with MMS on that build. I think the default apns-conf.xml for CyanogenMod worked for the Design 4G

2. Someone is going to have to get in the code and fix MMS. Moving stuff and changing stuff isn't going to fix it.

I was looking through you old CM9 build thread, what exactly did you find that was broken? Something about it looking for a Sprint APN?

3. I AM the dev that got MMS working on the One V. Both CM9/10. It was straight forward and no diff than anything else.

Oh... then it's an Evo V specific issue then...

4. I believe the issue to be because of Wimax and that is why MMS won't work using every known method. (Despite belief, I have lost hours/days caught up on MMS)

Thank you so much for your hard work! And if it's because of Wimax, then wouldn't the same issue happen on the Evo 3D? Do you happen to know how the devs on the Evo 3D did it?

.
 
Upvote 0
Sprint handles MMS diff. That's why its working there and not working for us

Do you happen to know what the difference is? I know that it's pretty much sent through Sprint, since VM is a Sprint subsidiary, but other than that... also, I get an odd message on logcat- something about the preferred APN being -1 or something like that. Also, type=null messages too. Has anyone tested it via GoSMS?
 
  • Like
Reactions: kagevazquez
Upvote 0
Do you happen to know what the difference is? I know that it's pretty much sent through Sprint, since VM is a Sprint subsidiary, but other than that... also, I get an odd message on logcat- something about the preferred APN being -1 or something like that. Also, type=null messages too. Has anyone tested it via GoSMS?

Sprint doesn't use a proxy.

The issue is and I have said it multiple times. (Not a shot at you, just mentioning it)

When a MMS is sent on a properly working ROM it authenticates to the MMS proxy and sends. If you type in the IP address plus port into a properly working ROMs browser you will get a page to come up.

On all aosp ROMs it times out to the proxy server. You also cannot pull up the page like on a sense ROM.

How it authenticates I have no idea.
 
  • Like
Reactions: heythereitsv
Upvote 0
Sprint doesn't use a proxy.

The issue is and I have said it multiple times. (Not a shot at you, just mentioning it)

When a MMS is sent on a properly working ROM it authenticates to the MMS proxy and sends. If you type in the IP address plus port into a properly working ROMs browser you will get a page to come up.

On all aosp ROMs it times out to the proxy server. You also cannot pull up the page like on a sense ROM.

How it authenticates I have no idea.

By proxy, do you mean the MMS Proxy? Because Sprint uses one I believe.

Sorry if I'm being slow, this bit is new to me. If I understand what you're saying correctly, that the AOSP ROMs fail to authenticate, and the Sense ROMs somehow authenticates via an unknown method.
 
Upvote 0
If anyone has managed to get it to work on the Boost Evo Design 4G which also has WiMAX radios then we might just be in business.

The problem there is that both as a Sprint and a Boost branded phone there is very little dev support. I think it's much more likely from our end then theirs. And as everyone one knows even without Wimax thrown into the picture, Virgin's handling of mms has caused us headaches porting roms all the way back to the Intercept days.
 
Upvote 0
Would this help ?
 

Attachments

  • uploadfromtaptalk1348620539170.jpg
    uploadfromtaptalk1348620539170.jpg
    75 KB · Views: 229
Upvote 0
The problem there is that both as a Sprint and a Boost branded phone there is very little dev support. I think it's much more likely from our end then theirs. And as everyone one knows even without Wimax thrown into the picture, Virgin's handling of mms has caused us headaches porting roms all the way back to the Intercept days.

The thing is they've already got MMS working on some of their ROMs and/or the fix posted above.
 
Upvote 0
The problem there is that both as a Sprint and a Boost branded phone there is very little dev support. I think it's much more likely from our end then theirs. And as everyone one knows even without Wimax thrown into the picture, Virgin's handling of mms has caused us headaches porting roms all the way back to the Intercept days.

^This.

Would this help ?

Sadly, no. The 4G somehow screws everything up... we've already tried versions of that fix (for VirginMobile of course)

The thing is they've already got MMS working on some of their ROMs and/or the fix posted above.

What about the ones specifically for the Evo Design 4G?

It reboots by itself when it's not
xiaowang0.jpg

xiaowang1.jpg

xiaowang2.jpg

xiaowang3.jpg

test3.jpg

Might I ask what those are? Images are broken
 
  • Like
Reactions: nsciucco
Upvote 0
And I will throw the bullshit flag. He hasnt provided anything

On Sense 4? Actually, I've gotten it working lol. Same fix as the Sense 3.6 ROMs, swap out /system/framework/framework-res.apk/res/xml/apns.xml with the one from the stock VM image

*EDIT*

I also had it in the OP "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."
 
Upvote 0
That still leaves us at a blank for AOSP Roms though.
Gosms isn't much for an mms work around as it basically uploads and holds a picture for a bit. and if the recipient doesn't have the app, all they get is a link. I haven't really tried the other types of mms through the app though.

Still we want a solid fix.

Back to the topic, anyone else found anything that might work?
 
Upvote 0

BEST TECH IN 2023

We've been tracking upcoming products and ranking the best tech since 2007. Thanks for trusting our opinion: we get rewarded through affiliate links that earn us a commission and we invite you to learn more about us.

Smartphones