fail to lock the GPU clocks [213935715]

Fixed

Bug

Status Update

No update yet.

Description

ho...@gmail.com

created issue #1

Jan 11, 2022 09:26AM

The version used: https://developer.android.com/jetpack/androidx/releases/benchmark#1.1.0-alpha13

Devices/Android versions reproduced on: blueline based on Android 12

Running .\gradlew.bat lockClocks command couldn't lock the GPU frequency. The related log is shown as below: Unable to lock gpu clocks of AOSP on blueline (blueline).

Relevant code to trigger the issue. In the 384 rows in the lockClocks.sh script, after the change from -ne to != operators, the library work expectedly.

384 if [ "$DEVICE" -ne "wembley" ]; then
Please correct the "-ne" operators.

Comments

sj...@google.com <sj...@google.com> Jan 13, 2022 02:05PM

Assigned to du...@google.com.

cc...@google.com <cc...@google.com> Jan 13, 2022 05:08PM

Reassigned to cc...@google.com.

ap...@google.com <ap...@google.com> #2Apr 24, 2023 09:22PM

Marked as fixed.

Yigit, do you have time to fix it?

reemission of the same liveData is racy

na...@google.com <na...@google.com> #3May 3, 2023 06:24PM

yea i'll take it.

Issue 213935715

Description

Issue summary

Comments

sj...@google.com <sj...@google.com> Jan 13, 2022 02:05PM

cc...@google.com <cc...@google.com> Jan 13, 2022 05:08PM

ap...@google.com <ap...@google.com> #2Apr 24, 2023 09:22PM

na...@google.com <na...@google.com> #3May 3, 2023 06:24PM

Add comment

Issue metadata