Rollouts this early feels more like a publicity stunt than anything else.
I do hope that faster rollouts or even Google Play rollouts become standard and wipes out differances regarding security and choosing of brand.
No more late rollouts and no more bi-monthly...

HoneycombJan 3, 2020

Rollouts this early feels more like a publicity stunt than anything else.
I do hope that faster rollouts or even Google Play rollouts become standard and wipes out differances regarding security and choosing of brand.
No more late rollouts and no more bi-monthly...

1. Have you recently updated the OS or factory reset? Some extra drain may be perfectly normal until the phone had time to optimize and learn usage pattern.
2. How is your charge pattern? Partial charging when needed is OK. But never letting it charge to 100% and "rest" on the charger is not good in the long run. You can miss out on the background optimizing work that is done then.
3. Look at running services and memory usage and app battery usage. Some apps can behave badly over time or after an app update. Wipe the problematic app cache or data depending on the app behavior problem. Usually full cache wipe in recovery is a waste of resources since it drains battery to rebuild the caches.
4. Signal quality, single or 2 simcards, wifi or mobile network usage, screen brightness, installed apps and app updates, Bluetooth, location and how often location updates is done (triggered by apps for example)... EVERYTHING including OS updates matters and can affect battery. It's easy to blame the OS update but check point 1, 2 and 3 first.
5. The phone should automatically learn how you use the phone and adjust accordingly but you can manually help it by defining the battery saving mode on the apps you rarely use. It's not nessesarilly a good idea to optimize battery on every single app and limit background activity in every way possible. That is why we have Intelligent control in 10. Permanently having to reload a app you use very often could lead to more drain!
6. Check if RAM boost OFF gives you better battery. The benefits of RAM boost may not be worth it for everyone.
7. More advanced battery monitoring can be done via BetterBatteryStats app. It's more than pure app drain that matters. How much your phone is allowed to deep sleep matters too.
8. There are apps that can help you. One of those is Naptime. May not fit everyone's need though.
9. More info here http://bit.ly/33bqDY2 (for example manual background optimizing command) and here http://bit.ly/2ZzdsP8 (my slightly outdated and in need of a rewrite battery guide with info about point 7 and 8 for example)

CupcakeJan 8, 2020

I've seen a few reporting this issue. I suggested to go into settings and change some stuff regarding networks.

View attachment 1211073
This one for example. Maybe it needs a few test and reboots and go back to standard setting or something. This is the only setting that should control if wifi only or mobile only rules and such would be applied as far as I know.
Some claimed this issue applied to all apps.

Maybe even try to reset app preferences.

No issues like that found on my phone yet.

Report this via the feedback tool too.

Click to expand...

I did play with that setting for a bit before posting this. However, I still have the issue. I've have reported it via feedback. Also, open beta 8 did not fix it either.

Ice Cream SandwichJan 11, 2020

CupcakeJan 21, 2020

On downloading the Open Beta 5 update package for OnePlus 7T from the link given above, I receive a file that has .jar extension at the end of the filename (which is not recognised for a local upgrade I suppose). I also tried renaming the file directly to .zip, but the updater still cannot find the update package. What next?
(PS: I did move the update package to the root)

KitKatJan 22, 2020

On downloading the Open Beta 5 update package for OnePlus 7T from the link given above, I receive a file that has .jar extension at the end of the filename (which is not recognised for a local upgrade I suppose). I also tried renaming the file directly to .zip, but the updater still cannot find the update package. What next?
(PS: I did move the update package to the root)