[Samsung Galaxy Nexus] MWisBest:
I have some good(?) news... the issue with the SMS/MMS stuff was introduced by some changes CM made, it appears they fixed it not too long ago. I'll be putting out a new build with this fix included ASAP.

This was part of why I liked having an AOSP base earlier with my 4.4 ROMs, not having to deal with outside forces.

Any time I merge in changes CM has made to any of the git repos I've forked, I always take a look at it to make sure something like this wouldn't happen. Unfortunately, I can't simply fork all 400-some repos that get synced. I'm just one person. Most of my current forks are of a more "core" nature in that they are some of the bigger and more important sections to Android's code, which is why not a lot of big things like this get by me. I've seen a change of just 6 or so lines in a makefile (a makefile is sort of like an instruction manual for the computer as to what to do with some code) end up causing any attempt to build a ROM fail within 30 seconds, thankfully it was in something I had already forked so I was able to fix it quickly and easily while CM sat around and didn't even realize it happened until an hour or more later (the reason I didn't submit a fix myself is that they would nitpick however I did it for a few hours in the review process (see below paragraph about review process) and by that time somebody else with more "power" (again, see below about that) will have fixed it exactly like I did in the first place, and they refuse any bug report for a nightly or nightly-type build so it's not like I can report it to anybody, so why bother). I have honest to god never seen anything that ludicrous happen with development, how people can make changes at not at least make sure it builds, let alone works on a device or emulator itself is beyond me.

CM has a review process for code (review.cyanogenmod.org), which is supposed to prevent these kinds of things from happening, but there are some people on there that will put up some code and pass it through right away by themselves without any sort of input etc. Usually people with that kind of power are responsible, smart, and will at least do a quick test on whatever they've changed, but that responsibility has been forgotten more and more as CM goes on. My biggest pet peeve with computer programming is people that don't test their code. It's like, a plumber fixing a leak, but they didn't actually test it to make sure it's fixed, and instead the home owner uses it and finds out it still leaks or even leaks in new places too. That kind of thing just doesn't happen.

For those of you who may have been using FML for quite a while and keeping up with the thread, you'll probably have noticed I'm usually more level-headed than other ROM makers can be. I don't ignore you if you don't provide a logcat if you report a bug or ridicule you, I'll just ask if you can provide one in case I can't reproduce the issue you have (if I can reproduce it, I should be able to get the logcat myself, after all, I'm the developer, I'm the person who needs it!). I don't get angry with people. I don't let the fact that I got featured on the XDA portal and XDA TV for having the first KitKat ROM for the VZW Galaxy Nexus inflate my ego or make me think I'm better than somebody else at something. I don't go around boasting that one of my more recent builds got 1,200+ downloads or care for that kind of *****-measuring contest at all. Heck, I don't even throw a hissy-fit if somebody says they're using/like another ROM better than mine, I just feel glad they found something they like. The other day I even recommended trying out some other ROMs if you were impatient with how long the new build had been taking me. With all the time I've been using ROMs, I never saw a developer behave in such a polite and humble (if I do say so myself) way.

If I do get upset like I did with this, fixed some bad code from CM-changes, etc., I've always kept it to myself as I don't think that's something I need to be sharing. Unfortunately, I've now reached a breaking point with the issues I've talked about in this post, and I felt it was time I share my thoughts on these problems. Maybe if it gets read by the right person, some changes can be made to address this stuff. If not, CM can continue on this path until it gets to the point that they're forced to recognize that changes need to be made on their own.

I mean no disrespect to CyanogenMod or any of its contributors. They've done great things for Android and its community. This post is more out of concern, even if I come across as just "trolling" or "raging." That's not a manner in which I like to act, which I hope is evident by my consistent, respectful, polite way of behavior.

If you did read this post, I thank you for taking the time to do so. I might have "tl;dr" it myself. On a semi-related note, does anybody know if there's a way to highlight text? I'd like to be able to do that as it'd allow me to just emphasize the more important information to condense this a bit.

EDIT: I ended up discovering something that might be contributing to this a little bit... frankly, CM just supports too many devices. A lot of things might be done that fix something for one device, but then breaks 20 others because it wasn't tested on those devices before being pushed out to everything. For starters, I'd suggest that they make sure anything related to the cell radio/RIL/whatever you want to call it is tested on different carriers and with different hardware... one thing I discovered was that they made a change that breaks 3G data after using WiFi on VZW devices unless you reboot. Had they tested a single Verizon/CDMA device, that could've been avoided, and there's still some arguing going back and forth about that change. The argument to leave the change that breaks Verizon devices is that it is needed for other devices, but to me common sense says fix that change other devices need so that it doesn't break other devices. What a mess, which could have been avoided if they waited just a little bit for the change to be tested more first.