[G2 Original Android Development] dr4stic:
So there are a few issues with this that people should understand... First, bug reports happen as usual through CM's jira system. That's always been the case and it's listed in the wiki on the CM website.

I'm in contact with "the devs" as much as I can be and tend to act as a liaison as best as I can. They don't monitor these forums generally, and XDA isn't considered an official venue for CM support . They prefer their own forum system, though I don't think that'd help much in our case for a reason I'll explain later. I asked to be the one to set up the G2 MM thread so that I could at least monitor it and update the OP with pertinent information, unlike what happened on the CM-12.1 release and the thread that Shelnutt set up.

In this capacity I have to do a bunch of things when it comes to the bugs I see. Basically I have to be a big filter. I have to distinguish what's a CM bug and what's a G2 CM bug. Our devs only care about the latter. Furthermore there are some bugs that would require WAY too much work to fix, at least for the current devs. The RIL related issues are an example of that. And so I have to judge reports based on how they related to the things I know pretty much won't be fixed. (And trust me, I have discussions with them to make sure I understand the why's, the who's, and all the relations before I accept that something is really really difficult to do).

There are any number of bugs that are related to corrupted settings and caches from the countless nightly updates that people apply, just hoping for relief from whatever they think is a bug. Not every update is managed cleanly in the code and it's amazing how much simply resetting your phone can help, especially if you've been doing the update process for a while. And btw, I reset my phone quite a bit just to test out the things you people here complain about, as well as to test patches for you guys with my own custom builds.

So, with all that said above we come down to the second major problem: interest. Open source works because of interest, and a project like CM is based on the open source concept. You have two different types of interest: user interest and developer interest. For users, the interest is obvious... they typically want the latest features their hardware can support as cleanly as it can support them.

For developers the interest usually comes from having a shiny new toy to play with. The latest tech, etc. This should put into perspective why cheaper phones tend to lose support more quickly than more expensive "premium" models. And by the way, no one buys them hardware, they usually get it on their own. Even when manufacturers play ball and donate a device or two, it's not representative of the whole line (eg there are a TON of different models of the G2 alone, with at least 4 unique hardware combinations globally). I ported CM to a device once and heard all sorts of offers of doner hardware and donations... I think I collected a grand total of $28. And while I wasn't doing it for the money, it certainly wasn't representative of the months of work I put into it.

Once the device is old (like the g2) and past it's prime (like the g2) it becomes a maintenance case. And developers of shiny new things hate feeling like they're just in a maintenance role and they understandably lose interest. Angry users that don't know how to properly report or filter bugs certainly don't help.

I do my best to bring up the issues with the devs. I talk to Rashed regularly and badger him on any number of things. I make mention of bugs to him at least once, and then I hound him on things I think I can actually get him to do. And occasionally, when I get frustrated enough, I'll try and get them done myself (as with the GPS random crash bug in 12.1, or the HDR now that I'm gonna mess with). I try to befriend the newer devs to get a sense of what's going on and maybe guide some of the frustrations (hello [MENTION=4647521]PsychoGame[/MENTION]!).

The music one is a weird one, and I've been chalking it up to a weird CM thing, and since I never seek I've basically ignored it. But I'll take some time this week to bring up some of my other devices to CM-13 and see if they exibit the same behavior. I know I've had issue with the bluetooth and audio routing that seems to have cleared up a little recently, but I've still been *****ing at Rashed about it. If I see the bug I'll put it on the list in the OP and see if I can at least figure out where it's coming from. I usually get better traction on a bug when I can provide the actual error and the place it's coming from.

I hope that answers your question :)