Join Date:Joined: Mar 2013
Donate to Me
Here we go. At this point, I am also waiting for a more stable version of CM 11 for Falcon. Yes, there are issues with it. Some are pretty notable, others are barely (or not at all) notable.
The thing here is that you are using open sourced software. There are some really, really experienced developers working on CM 11 to make it better for us, the end users. However, and I have seen this happen before, some lesser-experienced developers might forget about something every once in a while causing issues on the devices. This can happen. It happens to everyone, Motorola developers included (just look at the reports of battery drain issues across the Android versions).
CyanogenMod is a great team and are introducing features that improve Android in small, yet very useful ways. These features, in themselves, are working brilliantly. The only quirk with this is that CyanogenMod is trying to get each and every different phone to run Android in combination with those features. I might be wrong here, but that seems like that's causing a lot of trouble over some different devices, including the Moto G. If CyanogenMod adds a new feature to (for recent issues' sake) audio for devices CyanogenMod support (an update library for example), there's always a chance that gets pushed to the Moto G, and there's something with the Moto G that makes it not function properly. This is really notable in the Nightly releases. The most recent Nightly releases, 07-24 and 07-25 contain an issue that makes it so that audio isn't functioning properly. This is always a possibility. It's a Nightly, unstable, release. You cannot complain that it's not working on a version that's not intended to be stable.
This brings me to another point, the "Stable" release category. Moto G's most recent "Stable" release, M6, is really pretty stable. On everyday use, I could not see any one issue with it. The reason for there not being a M7 or M8 "Stable" release, is that there's issues with them, so CyanogenMod decided that it shouldn't be classed "Stable" for our device and therefor did not release them. I'm sure that, when there's a new safe-to-be-called-Stable release, CyanogenMod will push that to our device as well.
CyanogenMod is open source. There are bugs in it. You sign up for that in exchange for some new features and continued support from the developers. For the most part, the core software is stable. It's the "drivers" for the phone that are causing issues. Also, the new features have to be tested and the bugs that are in them should get reported to CyanogenMod so that the team can fix them. If you don't report the bugs, how would they get squashed? I have reported the audio issue on the most recent Nightly releases to CyanogenMod, which brings it to their attention and, while it is being fixed, the Nightly releases are temporarily postponed until the issue is fixed to prevent any further harm that this issue might cause. That is what CyanogenMod is about. They release something, obtain feedback, fix it, release that fix, obtain feedback, fix it and release that fix. That cycle keeps continuing. If they don't obtain feedback, they will just keep doing what they are doing -- add new features, which might cause the bugs you found to keep being there forever and ever.
And you may say that trying to report stuff in Nightly releases isn't 'allowed' on their feedback site, you're looking in the wrong place. You should look in the Nightly Regressions section of the CyanogenMod JIRA -- not the regular Issues section.
If you have any comment on what I just stated, please do reply to me. If there's anything that's wrong with what I just stated, please do correct me. If you dislike anything about what I just stated, please do not just post a hate comment on it -- actually explain what you don't like and why so I can, in turn, respond to that as well.
Thanks for reading.