vintf: Disable kernel compat check at boot time.
Before this change, if the kernel has a set of CONFIGs
that is not compatible with the system image, a dialog
is displayed for user / userdebug builds at boot time.
This check has been doing more harm than good because:
- This check is already enforced at build time and during
VTS tests (See vts_treble_vintf_framework_test).
- The dialog blocks UI automation for tests. For these UI
automation tests, they need to respond to the dialog.
- GKI has been enforced ecosystem-wide except for a few
low-end devices of other verticals. For these non-GKI
devices, the check enforced by VTS should guard this.
Hence, the check does not give us any signal.
- During development, a kernel that corresponds to the latest
release (android15 as of now) might not have valid kernel
config requirements in userspace. Kernel development schedule
is usually ahead of the userspace development schedule.
It does not always carry the string "-mainline-", because
it is not a mainline kernel. To unblock test automation on
these latest, bleeding-edge kernels, this kernel check should
go away.
- This is a small steps towards dropping the dependency on libvintf
on libandroid_runtime. libvintf links to libselinux, which is
huge. libandroid_runtime loads this, and the memory stays there
forever. Ideally, we should disable the whole VINTF check at
boot time, but let's do this one step at a time.
Bug: 272479887
Bug: 270169217
Test: TH
Change-Id: If24cdca9fb535b8f443c0d21f9a46c7ea25c1f9f
3 files changed