Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.Sign up
libhybris: 2018-06-18 -> 2019-12-02 #65
Two big things
The main issue with adbd (better described in commit messages and the patch) is that new versions of libhybris highly assume that you will be using libhybris with vendor libraries available.
This is not true here, and especially not with adbd in stage-1.
The adb daemon was running quite fine with the few bits of libhybris it was using, before they changed the behaviour. The added patch reverts the new behaviour to the older behaviour, which makes libhybris not load any libraries for adbd.
In the future, it might be ideal to extract the minimum libhybris required to run adbd, and rely on that instead.
This does mean that #30 will conflict, I'll rebase it on top of this PR.
This is used to get a slimmer libhybris for adbd for stage-1. The previous behaviour (before 35976c201741cfc21c114615b8524db5367e034a) was to rely on a "homegrown" system to get properties. Starting with that new properties system, it will rely on the vendor libraries, thus requiring all of them, plus the linker, to get properties. Turns out, adbd doesn't actively need anything from the vendor libraries or from the actual propeties system. So, it's fine to revert the change to get a working libhybris for stage-1. Though, what would be even better is to strip out only the minimum requirements for adbd, and make a "mini hybris" that we can rely on for adbd.