For ppl still having MMS issues and the earlier telephony.db trick didn't work, try Verizon Messages app from Play Store... I was successfully using it for MMS for about two weeks with no issues. Supports group MMS as well.
Sent from my XT894 using Tapatalk 2
Anyway. After digging around on Google, I've managed to find a fix for MMS messages, outside of deleting/modifying telephony.db. I kinda felt that modifying system files was a bad idea, and no one seemed to know why deleting or renaming telephony.db worked, or even what the file was for, so I took it into my own hands to find an alternative method of getting MMS to work.
Go to Settings, Wireless & Networks, More..., Mobile Networks, Access Point Names. Scroll down until you find whichever APN that your phone is using - in my case, my phone uses "LTE - Verizon Internet". Tap on the selection - NOT the blue bubble on the right - and scroll down until you find "MMSC". Tap on that, and in the box that comes up, type "http://mms.vtext.com/servlets/mms", without the quotes. Submit, press the Menu key, tap "save", back out to the Home screen, and reset. Hopefully, this should fix things.
Hm... that's odd. I've noticed that, with CyanogenMod, sending an MMS is either a hit or a miss. Every once in a while, it'll send, but otherwise? Nope. Truth be told, I don't know if my recent MMS messages have been sent, either... since I never get a reply.
Anyway, yeah. I don't really feel comfortable with deleting a system file like telephony.db. I'd rather know exactly what the file does before I delete it; it's normally inaccessible for a reason, y'know?
Anyway, as for my previous post... look. I'm thankful for the work that the developer has put into this ROM. Really, I am - in fact, I use it as my daily driver. However, I feel like it wasn't quite ready to be pushed into "Stable" status; I get random freezes, sound cuts out every once in a while, the lockscreen freezes/crashes (thus needing a simulated battery pull), MMS messages don't send, the works. Basically, everything works fine until, well... it doesn't. And when it doesn't, all hell breaks loose. The ROM feels more like a beta build than anything. Anyway, is there any way that I could directly communicate with the developer of this ROM and offer my input? It seems like he's not too active on either this forum or the XDA Forums, and, since I'm basically sticking with CyanogenMod on the Droid 4, I'd like to help with bug reports and other issues. It's a brilliant ROM, and a brilliant port, but it still needs quite a bit of polish.
EDIT: One theory that I have in regards to fixing MMS is to boot up the stock ROM, look at your Mobile Network/APN settings, and copy any and all settings over to CyanogenMod. A lot of the APN settings in CM are not set, and I'm wondering if that may be causing the MMS send failure - if you copy the settings (port numbers, MMSM, all of those things), it may work as intended. However, I'm also wondering if, by copying the settings over from the stock ROM to CM, you'll lose access to wireless tethering.
Last edited by Jishkah; 07-09-2013 at 12:45 PM.
Anybody having issues with GPS? Mine won't lock on at all. This results in Google Navigation not working, which results in me being lost. All the ****ing time. I've tried a couple of different builds now. It was working fine, and then one day it stopped and hasn't locked on since.
My workouts are all guess work now, I can't map any thing out, and driving is now a dangerous combo of trying to figure out my stupid phones little picture of the map and watching for all the collective asses on the road.
I hoped the stable build would fix this issue for me, but so far no dice. Any help would be greatly appreciated. Thanks for the time, and for reading my minirant.
Motorola Droid 4 on 4.0.4
Motorola Droid on 4.1.1