Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Commit d1ea38b8 authored by Steven Moreland's avatar Steven Moreland
Browse files

updatable-via-apex on c2 manifest 

In case we need to update the version, go ahead and start setting this on devices. Also add notes on the history here why this is such a different setup than other APEXes.

Change-Id: I47fe4c39ebe1e3c1191eb34d2a031962a180ef64
Test: N/A
Bug: 385355208
parent bb24e525

media/mediaserver/manifest_media_c2_software.xml

+14 −1
Original line number Diff line number Diff line
@@ -8,7 +8,20 @@ 
            <instance>software</instance>

        </interface>

    </hal>

    <hal format="aidl">



    <!--

        This (and above) are actually served as part of the swcodec APEX.

        However, this was one of the first APEXEes, so they were created

        before APEX supported VINTF manifest. So, devices have old manifest

        entries, and the manifest is not in the APEX. The manifest also

        does not contain updatable-via-apex until Android 16 (B). Because of

        this, if the version is updated, vts_treble_vintf_vendor_test may

        fail on old devices which have the updated mainline module. If the

        manifest entry is conditionally added to the APEX, so that it is only

        read on new devices, we could move this entry from the platform into

        the APEX.

    -->

    <hal format="aidl" updatable-via-apex="true">

        <name>android.hardware.media.c2</name>

        <version>1</version>

        <fqname>IComponentStore/software</fqname>