halium-7.1: Disable cameraserver & mediaserver #9
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Halium-based ports either use droidmedia or camera_service in libhybris for camera needs.
Android's default cameraserver actively interferes with camera functionality provided by either of them,
while hosting an unnecessary Binder interface no one is using.
In addition to that it also takes over the socket for the camera trust agent which
we don't want.
Last but not least, since this racy behavior causes trouble, cameraserver's removal
also fixes the Xperia X's infamous "green half" screen in the viewfinder.
To round it up also disable mediaserver as it is an unnecessary Binder service for Halium.
Also, it might act as a fallback for providing camera functionality depending
on the device's hardening configuration, which would spawn yet another conflicting
cameraserver in disguise, replacing the trust agent socket underneath our feet.