[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] theslam08:
"However as I originally said, I was merely saying if everyone else is also having issues to open another so the developers are aware it's not fully fixed. Is that not the correct process? The answer is yes it is..."

Yes you are correct, if many are having the same issue to open another report. But my point in this case was that it wasn't a fault of the ROM, so no point in having a "ROM" bug report open. These forums are best for help each other "diagnose" instead. Github is best if you have already diagnosed and have statistical information - like screenshots of battery use info like from AccuBattery. I see you posted the android battery screen there but unfortunately the android battery use screen is useless - I can't tell what is going on from it, it shows a major decline but can't tell how quickly because it shows from 3 days ago but nothing up until maybe 20 hours prior to the 2%? IDK. But this is irrelevant so...

"Maybe in the future the developers can add this as a suggestion in with any reports of battery issues? At least before completely closing it. If people are still complaining, basic logic says they might want some help identifying root cause and troubleshooting the issue, maybe throw a recommendation like this in to help troubleshoot the issues instead of assuming a "rouge app" with literally no evidence of that yet."

I gather probably 80% don't read the OP. The LOS 20 topic dev put a bug report "guide" or template for users to use while reporting bugs and no one uses it (maybe 10% do). Others just "it's broken, this don't work, etc.". If I were a ROM dev, I would personally still add the "template" and troubleshooting recommendations like the AccuBattery anyway because yes, it could help some. As my previous response to you, I gave the recommendation to use AccuBattery along with it's probably a rouge app. My reasoning to guess it's a rouge app is because I have no battery issues and my phone is as old as everyone else's. I did the base test above and got 1%/hr. So it IS possible to have like no battery draining at all. Which is why I'm guessing a rouge app. I didn't just pull that out of thin air.

"Let's be honest here; It's kind of dumb to expect everyone reporting bugs to be a genius at also troubleshooting them, a bug can be experienced without any coding or programing knowledge, so lets drop the expectation of only complete bug reports from someone who already troubleshooted the entire issue, which is unrealistic and stupid to be honest."

Fair enough but this isn't a car/mechanic shop where you just drop your car off and pay to have it diagnosed for you. Everyone using these ROMs have to have some understanding that simply saying "ya I have terrible battery drain too" helps no one - esp when there can be 100 factors involved in that. If you were able to flash the ROM, you're able to read. These forums have plenty of helpful tips to diagnose. People must use them (and many choose not to which is aggravating - they find it easier to just blame the ROM and expect the dev to just "magically" fix something that isn't broken to begin with). Which is why I posted to you to use AccuBattery - it's much more helpful in diagnosing the battery usage than the built-in android battery screen.

Anyway....as for your battery screenshot and the actual problem here...and you definitely have something weird going on.

See where it says "Screen off usage details" at the top? It describes what those two boxes mean. Awake means the screen was off but not in deep sleep (doze not in use). Deep sleep means phone is in low power mode while screen is off. Now your SS shows 0% used while in deep sleep for 7.5hrs. That is very odd - it should have used some at least. And awake for 14m (at 2.3%) - which is good out of 7.5hrs, that 14m was probably just at the beginning of the 7.5hrs.

The box above that (reference my battery test post screenshot) is more informative - it says the total, in deep sleep for, screen on and screen off - is missing from your ss and would help to see. But ultimately, the fact it says 0% used while in deep sleep for 7h is odd and isn't normal.

I request that you take a scrolling screenshot of that whole page (discharge) when you do the test again (and yes, charge to 100% from like 75% or lower). Take one scrolling screenshot with the "Forground app battery usage" section showing "Battery usage" and one with the "Discharge Speed" tab selected. More information will be gathered from that and might be able to poinpoint better what is going on (hopefully).

In the end though, I'm guesstimating from the ss you used like 400mAh, so like 10% in like 8hrs? If so, that isn't bad.