We confirmed CIV_01.21.03.39_A11.xml has such kind of problem, which is caused by
SurfaceFlinger only supported two physical display with hard coded IDs 0 and 1 by default.
To support 3rd display, need call HWC API to obtain display id.
Such implementation is already done in latest HWC code.
The stable manifest.xml is a little old and not updated frequently. You just need pull
latest CiV code and try.
We have confirmed on our side, the log is like:
caas:/ # dumpsys SurfaceFlinger --display-id
Display 1241614750824224 (HWC display 0): port=32 pnpId=ACI displayName="ASUS
Display 25441752664638509 (HWC display 1): port=45 pnpId=VSC displayName="TD2230
Display 1881593711195957 (HWC display 2): port=53 pnpId=AUO displayName="RTK UHD
From: Marijn Simons <marijn.simons(a)tomtom.com>
Sent: Thursday, November 18, 2021 3:41 PM
Celadon] Re: Celadon multi-display support (3 displays)
Thanks for your answer. I tried the latest CIV_01.21.03.39_A11.xml. It does show on 3
displays with mirrored view. However, When I try to run different activities on different
displays, I can only detect 2 displays.
Running `adb shell dumpsys SurfaceFlinger --display-id` also gives me only 2 displays. So
for some reason it does not get detected as 3 separate displays in Android.
Do you have any more suggestions to have Android detect them as 3 separate displays?
Celadon mailing list -- celadon(a)lists.01.org To unsubscribe send an email to