Fixed
Status Update
Comments
mh...@google.com <mh...@google.com> #2
Information redacted by Android Beta Feedback.
ra...@google.com <ra...@google.com> #3
Thank you for reporting this issue. We have shared this with our product and engineering team and will update this issue with more information as it becomes available.
cc...@google.com <cc...@google.com> #4
This issue is so annoying & makes battery draining too fast, especially when battery is 20% & the battery saver is enabled already.
ap...@google.com <ap...@google.com> #5
Confirm p8p beta 4.1. GPS 100%, google play services. Huge drain.
na...@google.com <na...@google.com> #6
Same issue. Pixel 7 Android 15 beta 4.1, 14+ hours of Google Play Services (basically entire time off charger). Tried clearing cache and dat from Google Play Services and Google Play Store. Multiple reboots and even leaving Google Play Services beta. No difference.
Description
Component used: not sure what this means but BaselineProfileRule from macrobenchmark library
Version used: latest nightly snapshot from androidx.dev (1.2.0-SNAPSHOT)
Devices/Android versions reproduced on: Android P on go/acid
The macrobenchmark library fails to get a profile when the apk under test is actually a bundle with multiple splits. We at chrome use bundles with multiple splits (actually most of our code lives in splits rather than in the base module). When I try to generate a profile I get this in the output of the instrumentation:
The cause of this is this line here expects only a single path to return but for bundles, you get multiple ones (one for each split). eg:
The rest of the code in BaselineProfiles.kt also expects only the one profile. But there are usually multiple (one for each split).
The documentation for baseline profiles mentions both APKs and Bundles so I assume bundles should be supported?