The last time we talked about CyanogenMod was in June when CyanogenMod 11 M7 launched. This week the latest version of CyanogenMod has launched bringing the software to version M10. The developers behind the software say that this new version was a bit late to market thanks to the holiday at the beginning of the month.
Amongst the changes made to this latest version of the software is a new tool added called the CM Bug Tracker application. When a crash happens with a device running CyanogenMod 11 users will now get the option to upload a snippet of the log to developers. The tool will also upload the stack trace that goes along with the log.
A new field was also added to the take a bug report option in Developer settings. A scrubbed copy of that bug report can be sent via the send action users are shown. Data uploaded to the developers when a crash or bug is reported includes what device users are on, build, kernel, and Android runtime the user was running when the submission was made.
Other changes with the latest version of the software includes the addition of the Galaxy S5 for Sprint. The Galaxy Note 3 was also split out into GSM (hlte), Sprint (hltespr), and Verizon (hltevzw). ANT+ support for various hardware was added along with a number of other software updates and fixes.
SOURCE: CyanogenMod.org
Dear morons,
I submit a bug just about every twelve seconds for Google play services stopping (unfortunately). If I submit this bug hundreds of times a day for months on end, when will the bug be fixed? Is it never? Is never the answer? Is it less of a bug than it is a feature? If that is the case, I’d think that is a pretty shitty feature, but, then again, I’m not retarded.
I did turn off all location services because that seemed to create the most havoc with Google play services crashing, and that helped for a month or so. It at least made the instances where it crashed much more infrequent. I used to be hard pressed to hit submit on the bug report window, then hit the app switcher to kill the app, before it crashed again and prompted me to report it. It would just say it had already been reported, otherwise.
Long story short, who is looking at that long string of text that I submit every few seconds? And why isn’t anyone fixing the problem that I assume is being explained in that long string of characters every few seconds?