The Help Center page What topics can I as about here? has the following sections:
Recommendations, like "Which phone is better?" or "Can you suggest an app that does X?"
Shopping advice and suggestions, including what device to buy or where to buy it
This is because shopping questions have no one definite answer, and as such are a bad fit for a ...
As mentioned on the Help Center page titled "What topics can I ask about here?":
Please note the following topics are expressly off-topic here:
Developing/programming for Android (please ask these questions on
Marketing your Android app or doing market research
Issues with the Google Play Store (or any other app marketplace) ...
Afraid this would be considered off-topic by most users, as you already guessed. I'd suggest checking with our charging tag-wiki first (especially the "Chargers/Cables" section), and cross-check with questions using that tag.
If you weren't able to solve your issue that way, an acceptable approach would be asking for criteria (not chargers directly) – along ...
I don't think it's necessarily off-topic, but you're less likely to get a good answer here than there IMO. It really should be a bug report. The portion asking whether anyone else has the issue would be off-topic (polling), but presumably you care about the solution more than the prevalence. Asking where to find it would also be off-topic.
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 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 ...
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 ...