We could communicate both queue length and swapinterval to the server, if we don't want to re-do the client side buffer swapping (which we probably don't).
If the ANativeWindow gets attention in the future, we'd probably want to make a android-specific queue that honors more of the requests the driver can make through the ANativeWindow interface (and then lp: #1369763 could be solved properly).
"As discussed a while back [1], living with LP: #1369763 is probably
the lesser evil. But we should still strive to fix all the bugs."
True, it is probably better to have overlays back.
We could communicate both queue length and swapinterval to the server, if we don't want to re-do the client side buffer swapping (which we probably don't).
If the ANativeWindow gets attention in the future, we'd probably want to make a android-specific queue that honors more of the requests the driver can make through the ANativeWindow interface (and then lp: #1369763 could be solved properly).
"As discussed a while back [1], living with LP: #1369763 is probably
the lesser evil. But we should still strive to fix all the bugs."
True, it is probably better to have overlays back.