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

Root the AOKP 4.2.2 Magical Mystery MMS Thread

droiddekka

Well-Known Member
so this is what we know...or at least suspect:



1. dastin's 4.2.2 mms apk needs to be installed in place of mazda's 4.2.2 mms apk

2. build prop needs to have these two lines added to it


ro.cdma.home.operator.numeric=310120
ro.cdma.home.operator.alpha=Sprint


3. using the voice dialer to "open apns" and verify that your mmsc is showing http://mmsc.vmobl.com:8088/mms? along with the other info, which should be correct by default.





so what else is there?


i have done all this stuff and my mms force closes anytime i choose a pic to send. after opening mms back up the pic is there, but it never sends. txt msgs send and receive just fine.
 
Why don't you use the cm10.1 mms fix? No need to do all these changes to build prop.

http://androidforums.com/evo-v-4g-all-things-root/648971-zip-mms-fix-cm-aosp-aokp-thanks-wolfu.html

Tested it out this morning and it worked just fine on Dastins latest cm10.1



oh yeah, i did that too! (forgot)

its not working on aokp 4.2.2 tho...unless you're on 4.2.2? theres one other guy around here that has it working but i have no clue how. i'm gonna try it one more time before i crash out tonight.
 
What I did is pretty much what you did, flashed the CM10.1 MMS fix by krowley3, then added those lines to the build.prop. Make sure the lines are at the end of the build.prop and permissions are set correctly. That's all I can think of, works fine for me
 
oh yeah, i did that too! (forgot)

its not working on aokp 4.2.2 tho...unless you're on 4.2.2? theres one other guy around here that has it working but i have no clue how. i'm gonna try it one more time before i crash out tonight.

Yeah, I'm also on 4.2.2 and it sent a picture just fine to a friend.
 
i just copied my build.prop from aokp 4.1.2 and will drop it in next time i flash back over to 4.2.2. tonight and see what happens.

i found 3 redundant lines of code in there that look like they are the gsm counterparts to the ro.cdma.operator.etc.etc.etc lines

i deleted them. we'll see.
 
I loved the ROM it seemed smooth. the only reason I went back to my NAND is no MMS. I will try this fix. On another note my phone keeps randomly rebooting after I tried mazdas 4.2.2. formated all partiotions b4 i instal a new ROM it doesnt seem to matter. what ROM try either.... Im not sure if 4.2.2 had something to do with this or not.. I doubt it . still weird.so I ran the RUU. and Now I am sitting with a stock unrooted phone.... UGHHHHHH. But I will downgrade my HBOOT and try this ROM again
 
just did a fresh wipe, installed gapps, installed the cm10mms fix, edited the build.prop, verified the apn settings.


now when i send myself a picture it looks like its trying to send (no force closes this time...thats progress) but never shows "sent"


what's causing it to hang? why does aokp 4.1.2 work for me and 4.2.2 does not?


who else is having this problem?
 
I think you need the cm10.1 fix


What I did is pretty much what you did, flashed the CM10.1 MMS fix by krowley3, then added those lines to the build.prop. Make sure the lines are at the end of the build.prop and permissions are set correctly. That's all I can think of, works fine for me
 
just did a fresh wipe, installed gapps, installed the cm10mms fix, edited the build.prop, verified the apn settings.


now when i send myself a picture it looks like its trying to send (no force closes this time...thats progress) but never shows "sent"


what's causing it to hang? why does aokp 4.1.2 work for me and 4.2.2 does not?


who else is having this problem?
Wait, are you using the cm10 mms fix or the cm10.1 fix?
 
This is the file I've been flashing.

Where is the 10.1 fix ?
 

Attachments

  • uploadfromtaptalk1361585375983.jpg
    uploadfromtaptalk1361585375983.jpg
    40.9 KB · Views: 74
Back
Top Bottom