Status Update
Comments
vi...@google.com <vi...@google.com>
di...@google.com <di...@google.com>
ch...@google.com <ch...@google.com> #2
Pump to P1 as it blocks OEM to use new emulator density.
ch...@google.com <ch...@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.
jl...@google.com <jl...@google.com>
jl...@google.com <jl...@google.com> #4
Please attach idea.log. Thank you.
jg...@google.com <jg...@google.com>
jg...@google.com <jg...@google.com>
an...@google.com <an...@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.
an...@google.com <an...@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.
Description
Android Studio 4.1.1
Build #AI-201.8743.12.41.6953283, built on November 5, 2020
Runtime version: 1.8.0_242-release-1644-b3-6222593 amd64
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
Linux 4.15.0-124-generic
Current Desktop: X-Cinnamon
Some vector drawables show fine in Design window, but are cropped/displaced very much in Resource Manager panel.
Two specific cases I've discovered:
See the left side on screenshots. Sample project attached.
Same happens in Android Studio 4.2 Canary 16. Not affected by enabling/disabling new Layout Rendering Engine. So it's not yet another duplicate of that issue . ;)