Fixed
Status Update
Comments
jp...@google.com <jp...@google.com>
ya...@google.com <ya...@google.com> #2
Alok, any idea on how we should lay this out?
ya...@google.com <ya...@google.com>
ko...@google.com <ko...@google.com>
ko...@google.com <ko...@google.com> #3
Split screen has 3 "stops" - 1/3, 1/2, and 2/3.
This looks like the icon is either getting cropped OR it is getting scrolled (same as other items such as Display > Lock screen display > Lock screen pop has a scrollable content inside). Do you know what is the case here?
In terms of solutions, assuming we need to keep all the elements, we can:
1. shrink the icon
2. let is scroll, and leave it WAI
This looks like the icon is either getting cropped OR it is getting scrolled (same as other items such as Display > Lock screen display > Lock screen pop has a scrollable content inside). Do you know what is the case here?
In terms of solutions, assuming we need to keep all the elements, we can:
1. shrink the icon
2. let is scroll, and leave it WAI
Description
The following Vulkan related problems were found on emulator 35.1.18 and emu-master-dev.
While running android emulators with big parallelism (10+ instances in parallel) i've noticed that occasionally there are errors like:
which do seem to affect the succeeding sessions. Most likely it could be a problem in the gpu vulkan library or smth else, but the issue is that I'm running the emulators withhttps://android.googlesource.com/platform/external/qemu/+/refs/heads/emu-master-dev/android/android-ui/modules/aemu-gl-init/src/android/opengl/emugl_config.cpp#246 )
-feature -Vulkan
to turn of Vulkan in order to be able to use snapshots, but nevertheless some Vulkan APIs are called (as seen from the error) which seems to cause issues at my scale. The problematic place seems to beemuglConfig_get_vulkan_hardware_gpu
inexternal/qemu/android/android-ui/modules/aemu-gl-init/src/android/opengl/emugl_config.cpp
(stack:
For now I've been able to get around this by renaming the
vulkan
folder underlib64
so that no Vulkan API calls are ever made (the flow just stops since it cannot load the library), but could it be possible to adjust this so that-feature -Vulkan
really disabled Vulkan.Another much smaller related issues is that even with
-feature -Vulkan
, the following lines are logged:This seems to come fromhttps://android.googlesource.com/platform/external/qemu/+/refs/heads/emu-master-dev/android/android-ui/modules/aemu-ui-window/src/android/main-common-ui.c#315 ) which does not seem to honour the feature flag (eventually Vulkan is not used since lower in the logic it does check the override state, but that could have been done at the very start to avoid the confusing log messages).
main-common-ui.c
(