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

Root [ZIP] MMS FIX FOR CM/AOSP/AOKP (THANKS wolfu)

I got a problem here, I'm using gangnamstyle ROM (sprint version) I did the MMS fix I can receive and send MMS to other people but for some reason I cannot download or see this particular person's media messages is weird..is any one else having this problem..by the way he has sprint network idk if that could be the problem?? Just saying... this a screenshot of how his media messages show up on my phone.

Screenshot_2013-01-07-22-03-32-1.png


If you use a different SMS app such as Chomp SMS, they'll display in that app fine. That's what I ended up doing since I can't see MMS messages from my friend with an iPhone 4S on AT&T, if it's a group message.

EDIT: Clicked quote on wrong post; fixed. Edited again to add details of what images don't show for me.
 
Upvote 0
op has been updated
- Now has a 'rom specific zip' section for rom specific files...
for now it has miui and slim bean.. if i have missed any, just reply with or pm me the link

- For those that care, I have been working on bringing back the themes and making a new one but time and life have not been my friends

- Also added the wierd sprint picture thing to the bugs list

this is also a good time to point out that i prob had the least to do with the development of these fixes.
At this point im just keeping the op updated...
If any1 who was involved in this fix feels that the need to start their own thread, they have my full 'go ahead'..
 
  • Like
Reactions: dstrcto
Upvote 0
I would have answered sooner...but work is a cruel mistress. Confirmed as working. I can't believe I didn't look in the build.prop...I over analyzed it as always. Thank you krowley!
Someone should let mazda know that change fixed MMS on SlimBean. I'm sure he would appreciate it and the build.prop changes with each release so it would be a hassle to maintain that fix.

ramjet73
 
Upvote 0
Someone should let mazda know that change fixed MMS on SlimBean. I'm sure he would appreciate it and the build.prop changes with each release so it would be a hassle to maintain that fix.

ramjet73

The build.prop was the only change that I made from the other CM10/AOKP MMS flashable zip. I thought I put that in the post on XDA, but I will double check it. I will not have any time for the next few days, some hopefully, we are now rolling ok on every AOSP rom. At least we have a flashable fix for each of them at this point.

Slimbean
CM10/AOKP/PACMAN
Evervolv 4.2
 
Upvote 0
The build.prop was the only change that I made from the other CM10/AOKP MMS flashable zip.
Yes, I understood that, but what I meant is that the build.prop file changes with each release for at least the version and build date and possibly other values if mazda fixes something. Since you are replacing rather than editing the build.prop file in the fix zip for SlimBean it can only be used for one version, and someone would have to update the zip file with the new build.prop every time a new build is released.

Hopefully mazda will incorporate the build.prop changes into the next version so the fix won't be necessary for Sprint users and the build.prop file can be removed from the VM version. Otherwise, the changes could be done as an edit in a script rather than a total replacement of that file.

Edit: There's a post in the SlimBean thread on XDA where neogenx says flashing the MMS fix zip reverted his dpi density back to the default. That makes sense because it and other system parameters are stored there, which is why concatenating new parameters via an edit script is recommended over completely replacing build.prop.

ramjet73
 
Upvote 0
Yes, I understood that, but what I meant is that the build.prop file changes with each release for at least the version and build date and possibly other values if mazda fixes something. Since you are replacing rather than editing the build.prop file in the fix zip for SlimBean it can only be used for one version, and someone would have to update the zip file with the new build.prop every time a new build is released.

Hopefully mazda will incorporate the build.prop changes into the next version so the fix won't be necessary for Sprint users and the build.prop file can be removed from the VM version. Otherwise, the changes could be done as an edit in a script rather than a total replacement of that file.

Edit: There's a post in the SlimBean thread on XDA where neogenx says flashing the MMS fix zip reverted his dpi density back to the default. That makes sense because it and other system parameters are stored there, which is why concatenating new parameters via an edit script is recommended over completely replacing build.prop.

ramjet73

You make some very valid points that I did not think of. That is why I put the only thing I changed in the post. I have no idea about how to make a script to do that, that is way out of my league. Hopefully he will incorporate the fix so we can just use the same flash for all AOSP roms except Evervolv 4.2.
 
Upvote 0
You make some very valid points that I did not think of. That is why I put the only thing I changed in the post. I have no idea about how to make a script to do that, that is way out of my league. Hopefully he will incorporate the fix so we can just use the same flash for all AOSP roms except Evervolv 4.2.
I have a script that edits the build.prop file in the updater-script that can be modified for those parameters if needed, but hopefully mazda will incorporate them in the next release so that's not necessary.

ramjet73
 
  • Like
Reactions: krowley3
Upvote 0
I've tried it. I had flashed it and downloaded go SMS pro and didn't set custom settings. Didn't work for me. Can you explain a little more?

I flashed the zip. Checked APNs to make sure it was correct. In Go SMS under MMS settings make sure everything is unchecked. Hit make MMS auto-retrieve. I raised the minimum size to 1MB.

My mom sent me a picture. Went into it and hit download and it came through. I also had a friend send a picture and it came through without me hitting download. Either way, seems to be working for me.

Edit: Also wifi was on and connected while doing this.
 
Upvote 0
Having an issue with receiving on 3.5.2 AOKP. I have a message thread going, and when they send an MMS it shows up as a new message thread that appears to be a forwarded message from my own number. I've read through the thread and couldn't figure out if anybody else had this issue.

I'm using the latest Stock MMS zip from the OP (CM10 +cache). Tried just about every install method, and just looking for some advice before I do a complete reinstall of aokp to start from scratch.

I am actually receiving the picture, but just in a strange way. Have a screencap link below.

Screenshot of what I'm seeing
 
Upvote 0
Having an issue with receiving on 3.5.2 AOKP. I have a message thread going, and when they send an MMS it shows up as a new message thread that appears to be a forwarded message from my own number. I've read through the thread and couldn't figure out if anybody else had this issue.

I'm using the latest Stock MMS zip from the OP (CM10 +cache). Tried just about every install method, and just looking for some advice before I do a complete reinstall of aokp to start from scratch.

I am actually receiving the picture, but just in a strange way. Have a screencap link below.

Screenshot of what I'm seeing

I'm having the same problem on the same ROM

it'a a known issue, I think. Hopefully it will be ironed out in the future.
 
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