8 replies to this topic

[PsychoI3oy]

I've seen a handful of bugs reported on CM6.0.0-n1-a1 and while the team is glad for the reports, there's another half to testing.

I have yet to see one report on a previously posted bug for 5.0.8 from a 6.0.0-a1 user. I'm hoping more than a few of them are fixed by the move to froyo, but I'd like to know which bugs still persist as well.


So, please do me a favor and look at the existing bugs in the tracker (particularly those marked 'new', which most of the N1 bugs are) and see if you can duplicate them on this build. Moreso if you've had the bug before on previous builds (and please say so) because that gives a more consistent report.


Thanks,
Psycho the BugMonkey.

ETA: The issue tracker is not for posting bugs about nightlies, stuff you've compiled yourself, or anything not posted on n0rp.chemlab.org by cyanogen.

[PsychoI3oy]

I still haven't seen a single report of anything in 5.x fixed in cm6-n1-a1. I am disappoint.

I will make one exception to the above rule about nightlies: if an existing (a1 or 5x) bug is fixed in the nightlies you can report on the existing bug to that effect and we can tag it ShouldBeFixed. Reporting new bugs on the nightlies is still verbotten.

[PsychoI3oy]

Thanks, elegos

FYI you can click the headers above the columns and go to show only-> 5.0.8 etc. Also, bugs without a model set have appeared on more than one device.

So, if one was particularly clever, they could 'show only' all the devices other than nexus and put a - in front of them and come up with http://code.google.c...A%20type=Defect

[SeidoJohn]

Just to be clear, and not make more work for you, Psycho13oy, you do want us to say if one of the bugs from 5.08 is fixed on one of the nightly builds (making sure to note which build)? Or was that only for the a1 testers?

Clearly, I wouldn't even think about posting new bugs from the nightlies. ;-)

Thanks!
SeidoJohn (AKA Johntastic)

[PsychoI3oy]

Yes, I'm being selfish/silly but:

new bugs found on nightlies: do not report
old bugs fixed on nightlies: report

While the same logic dictates that bugs fixed in nightlies may not be in any final release, I am curious to see what might be cleared out of the issue tracker soonish.

[PsychoI3oy]

RC1 is an official release, so bug reports on it are accepted. Be aware that the various gapps floating around may be causing issues, use the ones linked in cyanogen's post.

And please report on existing bugs, fixed or otherwise, so everyone knows that they're doing a good job making things better.

[SeidoJohn]

Thanks for the clarification. I just updated two bugs on the tracker (1806 & 1804) as a test to make sure that's what you're looking for. I didn't want to inundate the tracker (or your inbox/RSS) with bogus updates. If what I added is either unhelpful or not detailed enough, let me know, and I'll step my game up.

[whoisthedrizzle]

The problems with SU are still very much present in RC2 even though it is marked as Fixed on the tracker and in fact I think they're worse

Still getting identical behavior from all apps that need root - SU hangs granting permissions, then spams the notification at least 5x before actually holding. SetCPU is now autodetecting all kernels (including the stock toxygene) at 883Mhz/Userspace and this is even after a fresh install with nothing but SetCPU added at that point. Apps granted root will often not detect root after opening again a bit later, and SU is bugging granting permissions just trying to open apps (meaning before I even selecting an action to execute within an app). Watching the device log in the debug monitor I just see a wall of orange and then red text any time an app wants root or SU is called...

Should I post a specific log/filter or a portion of one?


All the CM customization is coming along very nicely Getting more and more excited for a stable build keep up the great work!