* These are mostly useful for debugging purposes so I've added them
in the project's utilities wiki page.
* alsa-utils have been renamed to use their original names if there's no
conflict with other packages in AOSP.
* HIDL services are not included on API level 35. Add the services since
we're still using few HIDL HALs.
4ce8327a8f
* FCM level can't be bumped to 202404 until all HALs have been updated to
AIDL i.e. at least following HALs reported by 'make check-vintf-all'.
All HALs in device manifest are declared in FCM <= level 202404
ERROR: files are incompatible:
...
android.hardware.camera.provider@2.5::ICameraProvider/legacy/0 is deprecated in compatibility matrix at FCM Version 202404; it should not be served.
because it matches android.hardware.camera.provider@2.4::ICameraProvider/[^/]+/[0-9]+ from /system/etc/vintf/compatibility_matrix.7.xml
android.hardware.audio@7.1::IDevicesFactory/default is deprecated in compatibility matrix at FCM Version 202404; it should not be served.
because it matches android.hardware.audio@7.0::IDevicesFactory/default from /system/etc/vintf/compatibility_matrix.8.xml
android.hardware.audio.effect@7.0::IEffectsFactory/default is deprecated in compatibility matrix at FCM Version 202404; it should not be served.
because it matches android.hardware.audio.effect@7.0::IEffectsFactory/default from /system/etc/vintf/compatibility_matrix.8.xml: Success
INCOMPATIBLE
* Needed for AIDL HDMI-CEC HAL to work. Some functions that were in the
HIDL HDMI-CEC HAL have been moved to separate HDMI connection HAL in the
AIDL versions. Only returns connection status of HDMI ports on Pi.
onHotplugEvent is not implemented.
* Use hardware/interfaces/tv/hdmi/connection/aidl/ as reference.
* Start the service later at 'class hal' to avoid making this into bootstrap
APEX. 'class early_hal' is started on trigger 'on late-fs' which is too
early for vendor APEX.
* Use device as an identifier in package names so APEXs on rpi4/rpi5 trees
can co-exist. Somehow apex definitions escape the soong namespace. It
doesn't complain about duplicate package names but dependecies later in
the build after analyzing Android.bp files and generating ninja file.
FAILED: ninja: ... multiple rules generate com.android.hardware.bluetooth.rpi-deps-info [-w dupbuild=err]
https://android.googlesource.com/platform/build/soong/+/refs/heads/main/README.md#namespaces
* Not sure if this is an AOSP bug or intended behaviour for apex targets.
Don't like using the rpi4/rpi5 tags but couldn't come up with better
solution to limit the visibility that worked.
* General cleanups. As APEX package contains all dependencies that are
needed for the service, remove unused shared libraries.
Run 'bpfmt -s -w Android.bp'.
* This gets built as a dependency to minigbm gbm_mesa_driver's
libgbm_mesa_wrapper but add it here for completeness.
* Move Mesa gbm libraries under separate section.
