[Samsung Galaxy Nexus] MWisBest:
Oh, awesome! While I was so busy working on FML just doing my own thing, I didn't keep up with some news.

http://androidfannetwork.com/2013/09/21/the-dark-side-of-cyanogenmod-aka-cyanogen-inc/

NOTE: If an external link such as this isn't allowed here, I have no objections to voluntarily removing it, I'm not entirely sure of XDA's rule or common-practice on this.

This explains a lot of what I had talked about in that long post a few pages back, and reiterates on quite a bit of it. I was completely blind-sided by this information.

How does this effect FML? Well, believe it or not, I'm somewhat happy by knowing this information. I was starting to see this already, e.x. that long post I had a few pages back. So seeing that information now rather than when it first started developing, is actually good for me because I know I'm not reading some drama or biased crap and that it's true. And of course I'm not thrilled with knowing this, but for now it's good-to-know (or to CM, need-to-know?).

It can certainly explain a lot of things too. When CM says they're going through all their features to see which are still "viable," that's code for "we're removing everything that doesn't pass the CTS and doesn't let us use it in a commercial manner." When commits are pushed through with small, shady commit messages, or saying "it doesn't work," it's code for "we don't need people looking at this and/or doesn't pass CTS." It explains a bunch of stuff I've seen that is of little-to-no-use for open development but is extremely useful or even crucial for a vendor like Oppo or something like that.

This will change how I do some things with FML, but in a good way. One, I'm not going to sit on my ass and wait for CM to re-implement features. I now know that it isn't going to happen. Two, I'm going to be screening more changes before I sync in their code. I'll be looking at their GitHub and go over every last bit of history since the last time I synced up. I've looked into the feasibility of this, and I can manage it fine. If I just at the very least screen commit messages if a lot has changed since my last sync it won't take me long and it'll be definitely worth it. If I sync and all of a sudden a bunch of commits are discarded (like what happened the other night, totally screwing up my and plenty of other people's builds since CM just deleted 300+ total commits related to Bluetooth stuff) I'll fork whatever they messed with and grab it from a backup I have run automatically before I sync on any key repos which I don't already have a fork or full-control over. Three, I had been thinking of submitting some of my things I work on upstream to CM itself so others could enjoy using it, I figured there's some things that I'd be able to push through their hostile gerrit review, but now that isn't going to be happening. I won't be agreeing to the possibility of my code being used in a commercial manner like CM is doing. Four... four I can't say unless I construct a bomb shelter and communicate via a headset inside of it that's wired to a loudspeaker on the roof of it. :eek: Good thing though, improves one of my main motives for doing FML already.

EDIT: BTW, [MENTION=3527370]taz1458[/MENTION], I'm wondering if this is indeed something with Handcent and not with FML. If it still doesn't work in the next FML build coming out in the next couple of days or so, then I can only chalk it up to a Handcent issue and not an FML issue, unless you're certain it's working fine on other 4.4 ROMs...