Its nice to see that you are back to working on Celadon. I would
strongly recommend that you move to Android P, unless you have a
constraint, as it is currently better tested than OMR1
If you still want to use OMR1, please find my comments inline.
Michael Goffioul <michael.goffioul(a)gmail.com> writes:
2) The animations work fine in the launcher app, but whenever I
another app, e.g. Settings, the display freezes halfway through animation,
and I can see these messages in the logs (repeated a bunch of times):
09-26 20:15:33.587 1667 2075 E iahwcomposer: CommitFrame: Failed to
commit pset ret=Unknown error -22
09-26 20:15:33.587 1667 2075 E iahwcomposer: Commit: Failed to Commit
09-26 20:15:33.587 1667 2075 E iahwcomposer: Failed to set layers in the
09-26 20:15:33.587 1677 1677 E HWComposer: presentAndGetReleaseFences:
failed for display 0: BadLayer (3)
The device is not completely frozen. It's just the display that is stuck on
a given frame in the animation. Although the display is not updated
anymore, the UI is still functional.
In previous instances of Android-IA, I used to set
"board.disable.explicit.sync=1" for that device, to avoid display problem.
But if I do it on celadon, the whole graphic stack doesn't start, the
screen stays on the prompt 'celadon$'.
Once quick hack would be to try building IAHWC with this  set to
true. If that doesn't work then try setting this  to true also.