So where do we actually report issues...and how would the Devs even know what is working and what isn't if we don't report it somewhere? I thought that was the purpose of this thread...not to only say 'Thanks' a million times...I might be wrong but i'm sure many of us want to know what is working and what isn't on the new releases even if the Devs mentioned it in the changelog...I read it everyday but there r new features and bugs that come out regularly. I'm sure they read these posts to figure out what has been resolved or broken...if they don't hear from the community than there would be no use for us testing it or even having a thread.
I think the cleanup should be focused mainly on repeated questions...which have answers...or people asking '.... is this fixed yet?'
Testing of new nightlies and its results...new features/bugs/resolutions should be allowed to be posted here in my opinion.
I hope I don't get a treat lol...
you have a point, but when people are just saying, "bluetooth not working," "is audio fixed in the newest nightly?" "mute doesn't work" and then you get 10 "i can confirm" posts, that does nothing for the devs but point out a problem. The purpose of this kind of a development thread is to post logs of specific issues so the devs can pour over them to find out that "lib x isn't reading this way and needs to tweaked to read this way to fix it" or something along those lines.
These development threads get clogged with "help x is broken, could someone fix it for me?" or "x is broken so I'm switching to z ROM until it gets fixed." both of those do absolutely nothing but clutter the thread. If people aren't willing to search for a solution for a problem they are having and just posting blindly, that takes away from the development. If people aren't willing to try and fix the problem themselves, that takes away from development. I'm not saying people shouldn't ask questions, thats what these forums are for, but people asking the same questions over and over, that have been answered/solved, obviously not searching before posting, is frustrating to those who a) answered it b) are watching for real problems to help fix them and c) those of us who are trying to learn by following along with the development.
Back on point, yes this thread is for reporting bugs, issues, problems, etc but people should take the extra step and provide a log of the issue to help the developers fix it not just post and say "x is broken." If people don't know how to create a log, there are tools in the market, threads that teach you, and tons of other things to help you, but search for it first. I'm with bigjoe on this, things are getting out of control, instead of having him take his time to clean the thread, we should
search first, then ask questions and if you have an issue to report post a log with it to help fix it and be
APART of the development.
---------- Post added at 08:52 AM ---------- Previous post was at 08:43 AM ----------
I don't want to flame and please don't take it that way, but this kind of question should be asked in the Q&A thread, not here. If you don't understand what the code says/means don't post random links to git. The changelog (found
HERE) has brief explanations of what was fixed. It may not be a complete fix but a step in the right direction. An issue like audio isn't going to get fixed overnight, its going to take time. Through trial and error. Samsung uses a lot (understatement) of proprietary things and then provides zero documents on them. CM uses open source things and is very open about their documents. But when you are trying to make the open source work and don't have a road map to help with the directions, you're driving blind. Please ask questions like yours in the Q&A thread not here.