Status Update
Comments
sp...@google.com <sp...@google.com>
ju...@google.com <ju...@google.com>
wa...@google.com <wa...@google.com> #2
Pump to P1 as it blocks OEM to use new emulator density.
ro...@google.com <ro...@google.com> #3
When and where does this error appear in Studio? I tried changing hw.lcd.density
to 200 in config.ini
on an emulator and it seemed to start up ok.
sp...@google.com <sp...@google.com> #4
Please attach idea.log. Thank you.
wa...@google.com <wa...@google.com> #5
The comments from reporter:
The issue is not when reading the config.ini. That is indeed the current workaround: create the AVD, then edit the config.ini to fix the density to 200.
The problem is when you use a hardware configuration (devices.xml) where the device specifies 200 for the display density Android Studio refuses to create the AVD with that density. The config.ini ends up with a different value written for the display density than what was in devices.xml.
The other missing densities (140 and 180) have the same problem.
sp...@google.com <sp...@google.com>
ro...@google.com <ro...@google.com> #6
It looks like the path to this error is: Device Manager -> Virtual -> Create Device -> Import Hardware Profiles -> (provide a device.xml file as described above).
Given that the emulator has been updated to support these values, it makes sense that we should allow them as well.
ro...@google.com <ro...@google.com> #7
(Also the error handling is pretty abysmal here... there's no feedback to the user when the file fails validation, just the SAXParseExecption goes to the IDE error log.)
ro...@google.com <ro...@google.com> #8
This should be fixed at tip-of-tree.
re...@google.com <re...@google.com> #9
I just tested this (with an unsupported dpi) on the latest emulator and the error message of supported dpis does not reflect this change:
INFO | Android emulator version 31.3.5.0 (build_id 8311694) (CL:N/A)
emulator: INFO: Found systemPath /usr/local/google/home/rengels/Android/Sdk/system-images/android-31/google_apis/x86_64/
INFO | Duplicate loglines will be removed, if you wish to see each indiviudal line launch with the -log-nofilter flag.
WARNING | unexpected system image feature string, emulator might not function correctly, please try updating the emulator.
WARNING | cannot add library /usr/local/google/home/rengels/android/prebuilts/android-emulator/linux-x86_64/qemu/linux-x86_64/lib64/vulkan/libvulkan.so: failed
INFO | added library /usr/local/google/home/rengels/android/prebuilts/android-emulator/linux-x86_64/lib64/vulkan/libvulkan.so
INFO | configAndStartRenderer: setting vsync to 60 hz
INFO | Sending adb public key [QAAAAMEuKpu/nqwJy5uKHCOrpzvzcyu4lxdmH6uGrQ/LAa3M606YSWwFi/0u01WflKg90dE1hbyr7449fZzD2BgeRGD145Firstch/g8oWCRDTOM/LYNUWmUdlJ2VqPIT14KckXFUgf+RXq29XWgxYDIdXngADnFIcLdQma2jvEXDE5cQExG94DGPtrUnK0DTrlU1gAtQ74QfKsveKIuJkhu4sghOcPEp2QLe9ulzA/DY9i3S6/OMUIJyq5ipe4F4UFdL/hiS0fuLvGRG+1QbRrkEPxfzH0jLs2mAoduLBo0Ee0aR3Oapt2+rECZVEJ8H9xAVsphI33Z+FiRJr/+EsVFrFJa5daqLeNxJTBO7zcDv/QTLwWXMtc4WPEG7AR1n1+OmH00oTf+E36HagZRHRx/InnpeafE/pGwT7sYWFc0HVbp8bYTAKHObyU0q9jfUfDAeWoSD2dkLtv9gF86Trmyq3bIuFbZi4TrOjXoDWKNE7xeJQOhXF6ELFAUkPwEtIbWCBw1K3TZ+C00YRzzArhDBgzq86ncP5EeUSIWE7yPoxADiH0/DhtCJrYA8r7kXMfeuxjVLozRT++g/SWQZdzTodMEbZnesvLsg7tArNKzksP0FzL5LOdI9C18fq541IVGztFbwAX7sStxB2Q/4MkXCx6IinRr7P2nIUCp4q8ZdlP1UTJmegEAAQA= rengels@unknown]
qemu: Bad LCD density: 288. Available densities are: 120, 140, 160, 180, 213, 240, 280, 320, 340, 360, 400, 420, 440, 480, 560, 640.
The version of 31.3.4
shows as the latest. Do we know when this will be released?
re...@google.com <re...@google.com> #10
To clarify, the reported valid densities above do not match the schema:
<xsd:restriction base="xsd:token">
<xsd:enumeration value="ldpi" />
<xsd:enumeration value="mdpi" />
<xsd:enumeration value="tvdpi" />
<xsd:enumeration value="hdpi" />
<xsd:enumeration value="140dpi" />
<xsd:enumeration value="180dpi" />
<xsd:enumeration value="200dpi" />
<xsd:enumeration value="260dpi" />
<xsd:enumeration value="280dpi" />
<xsd:enumeration value="300dpi" />
<xsd:enumeration value="xhdpi" />
<xsd:enumeration value="340dpi" />
<xsd:enumeration value="360dpi" />
<xsd:enumeration value="400dpi" />
<xsd:enumeration value="420dpi" />
<xsd:enumeration value="440dpi" />
<xsd:enumeration value="xxhdpi" />
<xsd:enumeration value="560dpi" />
<xsd:enumeration value="xxxhdpi" />
</xsd:restriction>
re...@google.com <re...@google.com> #11
re...@google.com <re...@google.com> #12
ro...@google.com <ro...@google.com> #13
The Studio part of the fix should be available in the Dolphin canary, which is publicly available. I think it's too late to patch it into Chipmunk.
The message you're seeing in the emulator in #9 is surprising based on
re...@google.com <re...@google.com> #14
@ro...@google.com As an FYI, the client tested in Dolphin Canary and it is still broken.
I will follow up with the emulator team.
hl...@ford.corp-partner.google.com <hl...@ford.corp-partner.google.com> #15
re...@google.com <re...@google.com> #16
I tested using Dolphin RC1 and this is working. The following pixel-density
values are valid:
ldpi, mdpi, tvdpi, hdpi, 140dpi, 180dpi, 200dpi, 260dpi, 280dpi, 300dpi, xhdpi, 340dpi, 360dpi, 400dpi, 420dpi, 440dpi, xxhdpi, 560dpi, xxxhdpi
Android Studio created the proper config.ini in the AVD.
Description
DESCRIBE THE ISSUE IN DETAIL:
The issue copied from b/192478074 . Few new densities been added to Android emulator, include 140,180 and 200. refer to b/171223840 . But Android studio doesn't support them. The bug is to support these densities in Android studio when creating a new AVD.
Here's the error message. Refer to b/192478074 for details.
200dpi has been released, but studio doesn't pass the validation becausehttps://cs.android.com/android-studio/platform/tools/base/+/mirror-goog-studio-main:device_validator/dvlib/src/main/resources/com/android/dvlib/devices-5.xsd;l=519 hasn't been updated. Studio fails with error: