Custom ROMs aren't a special topic: they're relevant to Android, so a question on custom ROMs is allowable and encouraged, as long as it fits the other criteria. One of those is that it should be a specific question answerable with facts. Questions that solicit discussion or opinions are discouraged simply because they don't fit well with the question-and-...
There could be a couple of reasons for this. If you have a specific question in mind that you'd like an explanation for then feel free to point it out and I (or someone else) can take a look, but off the top of my head a few possibilities would be:
If the question's last activity is attributed to Community♦ and there are no edits/modifications, then it's ...
On SE sites, you don't mark the question as solved – but you mark the answer as solution, so it stands out and can easily be identified by other people with a similar problem. The exact details are described in our help center: What should I do when someone answers my question? with a link to accept the answer and How to accept an answer.
The reason I opted for a single expansive answer is because there are really only two core things involved (most of the time):
Get USB Debugging enabled.
Get the Factory Reset option enabled.
Likewise, these generally involve the similar sub-steps — trick a browser window into opening, trick Settings into opening, maybe create another user account, ...
As with the CyanogenMod nightlies, or any "pre-beta" ROM, they should be closed. The problem, whatever it happens to be, is probably not widely applicable, and is likely to be fixed in the short term. That makes the question virtually useless for future readers.
Just close them.
The question was automatically and randomly bumped by a Stack Exchange bot, the Community user.
Hi, I'm not really a person.
I'm a background process that helps keep this site clean!
I do things like
Randomly poke old unanswered questions* every hour so they get some attention
The criteria for the eligible questions are
Questions with at least 30 ...
These questions are not considered to be within our scope:
Please note the following topics are expressly off-topic here:
Questions asking the community to find or recommend something for you (a device, app, ROM, website, etc), including what to buy and where to buy it
They were determined to be too problematic because they generally ...
You could offer a bounty. Two of the possible canned reasons seem applicable, I would think:
Current answers are outdated
The current answer(s) are out-of-date and require revision given recent changes.
This question has not received enough attention.
Starting a bounty will put the question on the "featured" questions ...
I think you're right that these questions add no value to the site. They're almost never fixable by users, and we do seem to get a lot of them. I've tried to reduce their number in the past by adding to the cyanogenmod tag-wiki a note about nightlies and about how to get bugs fixed faster; also by adding a comment like "don't use nightlies" to such questions....
There are some questions which follow this template:
Can you tell me what is this icon in the following image that I received from my son/daughter/wife/friend.. ?
Followed by some low resolution image (which gives us virtually nothing relevant in Google reverse image search) and sometimes they don't even bother to upload one.
I think specially this ...
As you can see following your link, the answer is No:
"Questions asking us to find or recommend an app, device, ROM, accessory or off-site resource are off-topic for Android Enthusiasts as they tend to attract opinionated answers and spam and become obsolete quickly. Instead, describe your situation and the specific problem you're trying to solve.
Since this is 3.5 years old I don't remember exactly what happened, but this was part of an effort to consolidate duplicates into a single canonical question. The older question you point out specifically limits itself to Gingerbread and Ice Cream Sandwich, and we wanted something more general.
You can see from the other duplicates listed that there were ...
I agree that there is little value in questions that are specific to a nightly ROM builds. I think it would be a good idea to have a policy of closing such questions. We want questions (and answers) for the "long tail", not questions (and answers) which are only helpful to the Asker in the here-and-now.
To that end, a canonical question and answer here on ...
I would say not. Hardware modding doesn't really have anything to do with Android the platform, and would generally be generically about cell hardware than specifically Android hardware. It also doesn't match the expertise of most of our users.
From its topic description, the Electrical Engineering SE might be host to a subset of such questions.
Following approach may be considered:
Make a new question (henceforth as OQ). This question would serve as an index with entry for a device and that being hyperlinked to a relevant answer on the same page.
The question may or may not be made a community wiki. Decision of the community shall take priority.
Let users post device specific answers to OQ. If a ...
No. If we took that kind of question, we would end up having to create an index of every device and custom ROM there is. Not only that, we'd have to update it with new versions and to replace dead links. There's no way we can maintain that big a collection of links.
For this reason, such questions are always closed as a duplicate of Where can I find stock ...
It's not for us to judge people's relationships, so in cases like this, I'd prefer to "look through" to the Android question, and ignore the context completely.
The most frequent example of this kind of question is the "inaccurate location history" question, for which we have a canonical question. If the core of the question is about whether location ...
I'd treat it as any other "software recommendation" questions: always put the emphasize on the issue first, but allow optional requirements like (free) apps recommendation.
Sometimes the only solution to a problem is to use paid apps, and while they might not help the OP, they might help others instead.
The last and nuclear option is to ban any questions &...
I'd start with this:
... as the problem at hand has been fixed ...
Yes, if you solved a problem yourself, you're always encouraged to post a self-answer (and accept it if appropriate).
The goal of Stack Exchange is to build a library of knowledge to help not only the question asker, but more importantly, all future visitors to the sites. Therefore any ...
Unfortunately, for some phones, bloatware will inevitably be installed on the phone if third-party tools are used.
Usually, rooting would involve this:
Flash a custom recovery -> use said recovery to flash a zip -> profit
Of course, a custom recovery won't introduce bloatware in 99.999% of cases. The zip file, provided you use one that is from a ...
Only a minority of questions here get an answer. According to https://stackexchange.com/sites#percentanswered, 59% of the non-removed questions received an answer, and many questions are removed due to roomba:
As requested by OP:
Mentioning clearly in the question ( possibly prefacing so that knee jerk closure flags are not triggered) with a text on lines of
This question pertains to a problem that is a legacy issue carried over from stable versions and not a specific behaviour of nightly builds
This ought to prevent:
Flagging / closure of the question ...
In this case, 'prevention is better than cure'. On Stackoverflow, upon trying to submit a question, the editor is smart enough to realize there's more code snippets than text.
With that approach in mind, how about, upon asking the question, expressions like 'Unstable', 'Nightly', 'CyanogenMod' (or other custom ROMs with nightlies) in same sentence/paragraph ...
At the time this question was asked, well-defined requests for recommendations were acceptable here. That is no longer the case.
Sometimes the Asker will argue that they're not asking for a recommendation, but rather just if such an app exists. It amounts to the same thing. "Help me find an app that meets my specific requirements" is a ...
I don't think this is the same as rooting questions. Each permission gives access to (a) specific thing(s), there's not a potentially long and complicated answer for each one.
We could organize answers better, but I think splitting it up into different questions just makes it harder to find. I'd rather focus on formatting. For example, we could split ...
As we already do with rooting questions, we will permit "one question per permission", and link to it from What do android application permissions mean? This way we have a double profit:
our "permission index" stays compact
with the time, we might have closer and more detailed information on each permission, easy to find via the links
When we've consensus ...