Fixed
Status Update
No update yet.
Comments
am...@google.com
pe...@google.com
ro...@google.com
ro...@google.com
an...@google.com
I am not sure I understand the use case. how can the benchmark be code to real world scenario when it's not possible to do right now ? which scenario is it ?
In any case, since this would be for benchmarking, this would clearly not be available through the public DSL. We should find a semi-private way of doing this (maybe the private variant API object could offer that functionality for instance or a property).
Description
AI-213.7172.25.2113.9123335, JRE 11.0.13+0-b1751.21-8125866x64 JetBrains s.r.o., OS Mac OS X(x86_64) v13.0.1, screens 1920.0x1200.0, 1920.0x1200.0
AS: Dolphin | 2021.3.1 Patch 1
Kotlin plugin: 213-1.7.20-release-for-android-studio-AS6777.52
Android Gradle Plugin: 7.2.2
Gradle: 7.4.2
Gradle JDK: Oracle OpenJDK version 12.0.2
NDK: from local.properties: (not specified), latest from SDK: (not found)
CMake: from local.properties: (not specified), latest from SDK: 3.22.1-g37088a8, from PATH: (unable to invoke cmake)
The emulator AVD editor always reverts the "Device Type" in the hardware configuration profile back to phone/tablet which is a real pain when you are constantly editing an Automotive device profile.
Steps (assuming you already have an Automotive AVD device)
1. Select edit from Device Manager of Automotive AVD
2. Press "change" button to modify hardware profile
3. Press "edit device"
4. Hardware profile editor appears and has revert the "Device Type" back to Phone/Tablet
See attached image.