[Verizon Samsung Galaxy S III] Chris Hansen:
Sorry, was out walking my dog while writing the response, that post wasn't there when I started writing it. :eek:

I'm going to disagree with this completely. Number one, this is for all unofficial builds, not just Mastas. The very first sentences of the OP are (from mastamoon):

Not only that, but isn't the point of a ROM thread to figure out what works and what doesn't? What's the difference between "I installed a kernel, and it doesn't work" or "Instagram doesn't work"? The end user is the one who installed either of these, but because one is an app, that's okay? Should people start complaining on the Play Store that Instagram doesn't work on a specific build?

If people are listing what their configuration is (we're not all going to be running the exact same setup, after all, that's the beauty of Android, is it not?), then I don't see the problem. We can pinpoint where errors are originating from, and if it's from an external source, then we can go to that source and notify them. And to top it off, wouldn't you only be cluttering the kernel thread at this point, since there are dozens of ROMs out there? I've seen many kernel devs respond with 'flash it and see', because there's just too many ROMs out there for them to test on each one.

It also helps users (that actually take the time to read and/or search the thread) to find out if something will work for them, or why they were having a problem, instead of searching out a number of threads to find if another program or configuration may have caused their issue. We're all here to help each other out. I do agree that the "me too" posts are a bit excessive, but then again, you have to remember the user base. This thread has almost 100k views, there's bound to be a handful of people that things just don't work for. There's a reason why some kernels work for some people while others get constant reboots using the exact same settings. I would say 5-6 people confirming an issue is probably plenty, but then again, they could also just be your statistical outlier if some 10k (arbitrary number) people installed this ROM.

And if you read the first page of responses, there's nothing helpful there, aside from your response and aerovan's. And I'm sure there's others riddled throughout the thread as well. Many people were also posting about using either TWRP or CWM to flash... yet those aren't ROM-related. At least when it comes to flashing an alternate kernel, it is somewhat related to the ROM due to the fact that they aren't jiving properly. Especially when you consider that the same kernel worked on previous builds... that means something changed on the new ROM release, as the other variables remained the same.

Here's an example of how posting about different configurations can help others (not necessarily the developers, but you never know);

Now anyone wondering if another kernel will work would know that BMS would have issues using the torch. This could help someone who is deciding whether or not to flash the BMS kernel and if it works, or it may help someone who has already flashed it find out if that is what caused their issue. It's not to put the burden on the developer, but just as an informative statement. But, then again, there have been times where developers have also offered a simple fix that solves the problem.

I have personally never delved deep into Linux, so I'd like to help others in any way I can - be it testing, troubleshooting, or confirming an issue.

/rant

All that said, I am greatly appreciative of those that are taking the time to test, compile, and provide this ROM (or any Android item, ROM/kernel/theme/app/etc). Keep doing what you're doing! :good: