mir_pixel_format_bgr_888 is selected by the nested server from the list of supported pixel formats, then the nested asks for a reconfigure to bgr_888, (which AndroidDisplay ignores).
a quick fix is to just remove mir_pixel_format_bgr_888 from the list of display-supported-pixel formats in mga::AndroidDisplayConfiguration. The proper fix is to get the display format from mga::Framebuffers to mga::AndroidDisplayConfiguration.
Android's displays aren't quite as configurable as the KMS ones. In FB/HWC1.0, we read a struct member to get the singular display format. In HWC 1.1/1.2 we scan over the EGL configs for a suitable config/format match. In HWComposer 1.3, the display format is actually opaque to us.
mir_pixel_ format_ bgr_888 is selected by the nested server from the list of supported pixel formats, then the nested asks for a reconfigure to bgr_888, (which AndroidDisplay ignores).
a quick fix is to just remove mir_pixel_ format_ bgr_888 from the list of display- supported- pixel formats in mga::AndroidDis playConfigurati on. The proper fix is to get the display format from mga::Framebuffers to mga::AndroidDis playConfigurati on.
Android's displays aren't quite as configurable as the KMS ones. In FB/HWC1.0, we read a struct member to get the singular display format. In HWC 1.1/1.2 we scan over the EGL configs for a suitable config/format match. In HWComposer 1.3, the display format is actually opaque to us.