Apparently, Google is using the Beta testers literally as guinea pigs (which is good):
“Several times in this interview we’re going to hear about Google’s experiments on the beta population, which is something I wasn’t aware of until now.Β The “infrastructure” Poiesz talks about is most likely theΒ A/BΒ testingavailableΒ throughΒ Google’s Firebase developer console. Though Firebase, app developers (in this case, Google) canΒ remotely swap bits of code in and out of an app for testing, all without having to update the app through the Play Store. For users this is invisible, and you’d never know a test was happening unless you noticed whatever was changed. I haven’t heard of A/B testing happening at an OS level in production, but apparently people on the beta builds get to be Google’s guineaΒ pigs. So a future note for people running beta versions of Android: don’t take battery life or performance issues too seriously, you might just be being experimented on.”
They can actually SWAP OUT CODE WITHOUT ROLLING AN UPDATE OUT to experiment with power efficiency! ππ
That explains why battery is very inconsistent throughout the beta tester community (including me).
I might actually right now having a battery test on my phone! That’s super fascinating π€―π₯°
https://arstechnica.com/gadgets/2018/08/p-is-for-power-how-google-tests-tracks-and-improves-android-battery-life///cdn.embedly.com/widgets/platform.js