I just figured out that undervolting even just a little bit is not a good idea when you are trying to use hulu plus or Netflix. Phone froze up and I had to pull battery 3 times. Reset the default voltages and everything is good now. Settings freelunch/zen
http://androidforums.com/virgin-mob...te-mms-fix-wip-cm-aosp-tw-update-10-14-a.html Flashing the first one (mod #1) worked for me. Using Go SMS Pro, send/receive on wifi/3g working perfectly. Have not tested on LTE.
Honestly to the best of my ability to determine it was LTE, it's still working, has been all day. The screen shot was taken with WiFi off on both phones (i was at home at the time) sent to and received from an AT&T LTE phone. I used the build from the other post and fix number 2. Shrug maybe I've gotten lucky I'm not a heavy MMS user.
Are you positive your phone didn't revert to 3g at any point? Do you happen to know what modem you're using? Mind taking a screenshot of your APN page? I'm running the 12/17 nightly with the 2nd fix from moped ryder and am only able to send mms right now. Been fiddling with APN settings for a while but nothing seems to be working yet.
I just wanted to update that it appears I've gotten MMS send/receive to work over 4g after flashing the MG2 modem and the 2nd fix by mopedryder. I'm not sure if it's of any consequence but I'm using hangouts for sms. This was not working for me previously on the MK5 modem.
I don't believe that it shifted to 3g, I'm still quite new to this. I know that 'this' is a biggie I'll do what I can to help and provide information so others more skilled and experienced can proof this . It still appears to be working both send and receive this morning
Yeah, this is pretty much the Holy Grail for users who want to use custom AOSP ROM's. MopedRyder worked his tail off to get those fixes for 4.3.x, and as you can see, at that point there was always a tradeoff. The sticking point was that the phone couldn't shift between LTE and 3G in order to send and receive MMS, it had to be done manually. So, if you have LTE running and aren't doing anything else, as in manually changing back to 3G, then this should be legit, something about the combo of 4.4.x/modem/APN fix is working! Not having LTE myself, I didn't have an issue, as long as I could use MMS. This is truly an awesome find if it is possible to have the whole package on 4.4.x, keep posting those results!
I can confirm that on the mk5 modem using riders 2nd fix, I have successfully sent an MMS using 4g. I am on the dec15 from the op
Go to the thread by iMaYG titled "Radios" I have posted all the links for the VM/Boost modems as well as the Sprint modems in that thread. Give my man JD (jdsingle76) thanks while you're at it, he is the one responsible for creating flashable zip files of all three VM/Boost modems. Edit: that thread is now on page 2, here's the link: http://androidforums.com/virgin-mobile-galaxy-s3-all-things-root/799809-radios.html
I got mk5,did fresh install for cm 11 on the 15 the nightly release, and did MopedRyders 2nd fix. No luck for me. I can send, not receive.
Try the first fix. I'm not sure if it works on LTE but I had the same issue with the 2nd fix. I didn't flash mk5 yet but I suspect it doesn't matter in this case.
I know the first fix works on 3g. I've been using it this whole time, just thought I'd give the 2nd fix a shot.
I was able to send but not receive mms over lte with the mk5 modem. Have you tested receiving? To you guys trying to get the second fix to work over LTE, I would suggest trying what I finally got to work. MG2 modem with second fix allowed me to send and receive, would like to hear feedback and see if it works for others as well. It's the only thing that made sense to me is if some users were on other modems and flashing the second fix just worked out of the box for them, I believe if we looked into it we'd find they were all on MG2.
Did you also reflash the mms fix after reverting to MG2? I would try that for good measure. It's possible MG2 isn't for everyone unfortunately.
Dang, I was really hoping we had lucked into a workaround. Unfortunately this is beyond the scope of my skillset to do much more digging. I'd be more than willing to offer up my time to someone more knowledgeable to get details of why it's working for me and see if it can be applied elsewhere. I feel like this problem would be easily fixed if someone that knew their way around MMS transmission on the backend just took a look at it.
