• 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!

I imagine we would have heard if someone had uncovered something. You aren't the only one who wants MMS.

Yeah... the other devs are working on it, I believe. Apparently there are smali changes needed, which is way above me. xD

Has anyone tried this?

Won't work. 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.

The fix for the issue that they were having with that ROM would be to push that MMS.apk and do the fix in the OP of this thread.
 
I appreciate the clarification between AOSP and Sense, I was just curious as to if the changes made to the MMS apk could be compared to the regular apk on that ROM, to see which fixes were applied - for any hints.
 
Just to clarify everything. It's going to take someone with a solid handle on mms in the aosp code to fix mms. No mod/hack/xml swap will fix mms. It will take code mods
 
I appreciate the clarification between AOSP and Sense, I was just curious as to if the changes made to the MMS apk could be compared to the regular apk on that ROM, to see which fixes were applied - for any hints.

That one looks like the Sense Mms.apk rather than the AOSP one. That would fix it

Just to clarify everything. It's going to take someone with a solid handle on mms in the aosp code to fix mms. No mod/hack/xml swap will fix mms. It will take code mods

Know anyone that does have a solid handle on MMS in AOSP code? xD
 
Just to clarify everything. It's going to take someone with a solid handle on mms in the aosp code to fix mms. No mod/hack/xml swap will fix mms. It will take code mods

Do you have any idea why it works for the One V but not for the Evo V?
 
I know there was a fix that got MMS working for an evo 4g ported to Virgin mobile running ICS. It is also a 4g wimax phone. I would assume there would be a lot of similarities between the two phones as they are both HTC wimax 4g phones.
 
I know there was a fix that got MMS working for an evo 4g ported to Virgin mobile running ICS. It is also a 4g wimax phone. I would assume there would be a lot of similarities between the two phones as they are both HTC wimax 4g phones.

This is probably true, but in order for them to use that phone on Virgin Mobile, they would have needed a donor phone (a VM's phone information). Since this is the first and only real 4G wimax phone on VM, we cannot compare to any other circumstances.
 
This is probably true, but in order for them to use that phone on Virgin Mobile, they would have needed a donor phone (a VM's phone information). Since this is the first and only real 4G wimax phone on VM, we cannot compare to any other circumstances.

Donor phone was for MEID and ESN, The APN settings and everything still needed to be changed to the correct values for Virgin mobile and the mms.apk needed to be changed in some way. The phone specific stuff that was needed from the donor phone doesn't really have anything to do with the MMS. I would be willing to bet that there is some useful information to be had there.
 
Donor phone was for MEID and ESN, The APN settings and everything still needed to be changed to the correct values for Virgin mobile and the mms.apk needed to be changed in some way. The phone specific stuff that was needed from the donor phone doesn't really have anything to do with the MMS. I would be willing to bet that there is some useful information to be had there.


But it was never setup as the evo v. I.e. sprint VM. And sprint 4g.
 
But it was never setup as the evo v. I.e. sprint VM. And sprint 4g.

True, I know the 4g never had to work along side the MMS, but it's got to be worth a look, all of the sprint 4g software was there, so maybe there is some clue or something useful in what was done to fix it for the evo.
 
Breakthrough Alert!!!
Users from my Paranoid Android post are saying that they are able to recieve mms messages perfectly... there are screenshots in the thread... im no dev but i think someone should dissect it... i have contacted lens_flare (the person who ported the rom to the evo 3d) for more info on how he got it to work.. when he respond.. i will update you guyz...
 
You can receive MMS, but not send MMS on the ParanoidAndroid ROM mentioned above with the Evo V on VM. Still a big breakthrough!
 
here is the only line of code with virgin mobile mentioned found in the apns-conf.xml used in the paranoid android rom... there are many other lines with sprint/boost/metro/cricket/mobipcs/etc... if needed, i can post the full file up...

<apn carrier="Virgin Mobile US" mcc="311" mnc="490" apn="0" mmsproxy="205.239.233.136" mmsport="81" mmsc="http://mmsc.vmobl.com:8088/mms?" port="" type="mms"/>
 
here is the only line of code with virgin mobile mentioned found in the apns-conf.xml used in the paranoid android rom... there are many other lines with sprint/boost/metro/cricket/mobipcs/etc... if needed, i can post the full file up...

<apn carrier="Virgin Mobile US" mcc="311" mnc="490" apn="0" mmsproxy="205.239.233.136" mmsport="81" mmsc="http://mmsc.vmobl.com:8088/mms?" port="" type="mms"/>

Can you upload the build.prop too?
 
Back
Top Bottom