Use ODPM data for power measurements on Android A new Power.ForegroundEnergyConsumedPerScenario.30Seconds metric is similar to Power.ForegroundBatteryDrainPerScenario.30Seconds, but it uses a different underlying API to get energy measurements from the device, more specifically https://developer.android.com/reference/android/os/health/SystemHealthManager#getPowerMonitorReadings(java.util.List%3Candroid.os.PowerMonitor%3E,%20java.util.concurrent.Executor,%20android.os.OutcomeReceiver%3Candroid.os.PowerMonitorReadings,java.lang.RuntimeException%3E) The advantage of the new metric is higher resolution - it should ~never (or at least very rarely) report misleading 0 deltas for a 30s interval. The disadvantage is that it's available on a more limited set of devices (Vanilla Ice Cream+, only some device models/OEMs). NO_IFTTT=the values moved in histograms.xml, but they didn't actually change Change-Id: Ie4f0912e3b598c43c61956573bbc55aa3507aa66 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6455067 Reviewed-by: Yaron Friedman <yfriedman@chromium.org> Reviewed-by: Francois Pierre Doray <fdoray@chromium.org> Commit-Queue: Igor Kraskevich <kraskevich@google.com> Cr-Commit-Position: refs/heads/main@{#1451902}
Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.
The project's web site is https://www.chromium.org.
To check out the source code locally, don't use git clone! Instead, follow the instructions on how to get the code.
Documentation in the source is rooted in docs/README.md.
Learn how to Get Around the Chromium Source Code Directory Structure.
For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.
If you found a bug, please file it at https://crbug.com/new.