With b/144533348, there will be symlinks from libs in APEXes to the libs
in the system partition. This is to reduce the size of APEXes when the
APEX is bundled with the platform.
Adding the /system/lib to the permitted paths so that the realpaths of
the symlinks are allowed for the namespaces.
Note that this however does not open all libs in the system partition to
the APEX namespaces, because searching of the libs are NOT done in
/system/lib, but in /apex/<module>/lib directory.
Bug: 144533348
Test: m
Change-Id: I959d4312a7bc5427c4d84885fbac4bc235cffa86
Media swcodec apex module breaks when ag/9857054 is applied.
Apex can't auto generate namespace.*.link.platform. This patch
adds libbinder_ndk.so so ag/9857054 can be merged.
Bug: 146070048
Test: Compiles and boots with ag/9857054
Change-Id: I26645a46019904884657011bf385821837c06c44
Till now, file_contexts has been treated differently that other input
src files. Now it is tagged as `android:"path"` because it is.
Bug: 144732805
Test: m
Change-Id: I9d842958da500900e83a95b7d194c9d8a46feee0
media/swcodec apexes should support Android 10.
With this flag, apex packages will include older APEX manifest format
(JSON) as well as new format (Protobuf) so that they will work with
Android 10.
Bug: 143951586
Test: m com.android.media com.android.media.swcodec
and install these to Android Q device
Change-Id: I927a464a8c7b88060126db398f568720396847f0
With VNDK APEX, the path for VNDK libs has been changed
from /system/lib/vndk-VER to /apex/com.android.vndk.vVER/lib
But we need to keep older location since it should run on
older version of system due to APEX requirements.
When VNDK APEX is used, older location is just a symlink to a new
location. So we have to add a new location as permitted path. Otherwise,
linker would fail because it checks accessibility using realpath().
Test: add a vendor binary to /apex/com.android.media.swcodec/bin
which opens /system/lib/vndk-sp{VNDK_VER}/hw/android.hidl.memory@1.0-impl.so
via android_load_sphal_library()
Bug: 142912195
Change-Id: I13779679af5cf7f687a726afe0b6118e15cf1869
With VNDK APEX, the path to VNDK libs is changed from
/system/lib/vndk-VER to /apex/com.android.vndk.vVER/lib.
Bug: 141451661
Test: m && boot (tested with cuttlefish)
Change-Id: Id3a335ad1dfea71fb53ce80b96d550af8ac61760
Searching /apex/com.android.runtime/${LIB} in the platform namespace makes
its libraries visible in the wrong namespace - they should be in a separate
"runtime" namespace to keep separation. Furthermore, in R the directory
only contains Bionic internal dependencies that no external package should
depend upon.
However the directory cannot be removed from the search paths because this
linker config is in an APEX that needs to work on Q too, where it is used to
find libclang_rt.hwasan*.so. (The issue with the libraries being visible in
the wrong namespace applies to Q too, but it doesn't have any known
observable effects.)
Hence only add a comment to highlight that it should be cleaned up when the
code has branched and Q compatibility can be dropped.
Test: Build & boot
Bug: 140790209
Bug: 139408016
Change-Id: I2a5e6418977200c56d01f52c0d78dd820cc643a2
For devices disabling treble, some VNDK-SP libraries needs to be loaded
as LLNDK. The CL modifies ld.config.txt to allow to load them from sphal.
Bug: 140781725
Test: Boot and check logcat. No native crash from mediaswcodec
Change-Id: Iec24405ec78359d78f4e7f43d9d046f3c70ff129
BUG: 140996463
Test: Local, TH and Forrest
Exempt-From-Owner-Approval: Need this change in before next cut.
Change-Id: I651a4fac7871c46415667fac33fa725c25dd8fc2
The canonical location of the HWASAN runtime, an LL-NDK library, is being moved
to the runtime APEX. It is apparently the first LL-NDK library in the runtime
APEX that does not require a legacy symlink in /system/${LIB}. Therefore we
need to add the runtime APEX's ${LIB} directory to the various search paths
used by the linker so that the library can be loaded from the default and
sphal namespaces.
Bug: http://b/134459232
Test: Builds
Change-Id: I1f63e1a2a61e1717d00736ef431f3ec2a9334193
Merged-In: I1f63e1a2a61e1717d00736ef431f3ec2a9334193
(cherry picked from commit 61f5fdf5c9)
On devices where VNDK is not enforced, libz.so is llndk.
Test: stagefright -s -S /sdcard/crowd_350x350p50f32_200kbps_meta.webm
Bug: 133351160
Change-Id: I8a563f86fe820e49ed6bae4e7e0f4a64bf1bddfa
Min sdk version has been force set to 28 (P) to support beta devices.
Since we now don't need to support them, we delete it. It is set to 29
by the build system.
Target and max sdk versions are bumped to 29.
Bug: 131128233
Test: m and check the sdk version numbers
Change-Id: I9ecf2b7542bde239955daf91c88b8e612d7d7069
* changes:
codec2: use media_codecs from apex and support variants/domains
media: add media_codecs.xml to apex module
media: expand media_codecs.xml to support variants and domains
media/omx: Make OMX software plugin an actual plugin
omx: only list existing OMX codecs in OmxStore
This reverts commit 784bfac0b0.
Reason for revert: decided to use device which matches to the test suite.
Bug: 131869673, Bug: 125914810
Change-Id: I5738a5303f3368f63fcd51074ee9b2db7344d518
The Beta 3 builds (which are in dogfood and public beta) will receive modules via the Play Store with version numbers 210000000. Hence, we must bump the version in qt-dev and hence beta 4.
BUG: 131240537
Change-Id: Ia568319821f3bc8765ff3c2096e963a32ffb15d6
The test APEX is built with aosp_x86_64 where first ABI is 64-bit.
But the test APEX can be installed to 32-bit target like cf_x86_phone.
The lack of 32-bit extractor libraries in the 32-bit target can cause
problem. So, install both ABIs of the extractor libraries to the test
APEX.
Bug: 125914810
Test: choosecombo to aosp_x86_64 and build test_com.android.media
Check that the test APEX has both lib and lib64 directories.
Change-Id: Ib073f61838fea0b823c870c8c71b49a7ecc9346e
When running with asan, the platform namespace didn't have /system/lib,
but /data/asan/system/lib in its search paths. As a result, clang
runtime libraries like libclang-rt.asan-i686-android.so which are still
in /system/lib cound not be found.
Fixing the problem by adding /system/lib to the search paths after the
asan path.
Bug: 131170196
Test: check if mediaswcodec process is running in aosp_cf_x86_pasan
Change-Id: Iffe5d25613999a00ead5eb03c0efca1d6c9ce012
The default namespace need access to libdl_android.so from platform
namespace for libgraphicsenv.so
Bug: http://b/130373059
Test: boot a sailfish with the change wait until it gets to setup wizard
Change-Id: I55faa4b42f863dfbcc3b959d113cf481c7e2e337
This is a workaround for b/130058564.
Test: adb shell stagefright -i | grep "c2.android"
Bug: 130254909
Change-Id: I8e8f7bbd9c1f777285cdcc58ea6610639122c928
This makes the entry for media.c2 in the framework manifest
device-independent.
Test: adb shell stagefright -i | grep -E "c2.*android"
Bug: 129999541
Change-Id: Idba276c512f495937aec32c4217dfd447e562139
To make sure we catch certain breakages related to the media codec
(test) APEX at presubmit.
Bug: 129996486
Test: run atest in frameworks/av/apex
Change-Id: Icf5933aee02ebad80c709ec3de340bbc733a14bd
The system version recently bumped to 200000000, which caused failures
in tests, because we aren't allowing downgrades. Bump to 300000000 to
make sure the tests pass again.
Bug: 129093117
Test: atest media_swcodec_e2e_tests
Change-Id: Icc84f4a0f749916aded6746923f0d82b2b9dc473
Automerger Merge Worker
Jiyong Park
Treehugger Robot
Marissa Wall
Jooyung Han
Martin Stjernholm
Daichi Hirono
Baligh Uddin
Akshay Thakker
Peter Collingbourne
Dongwon Kang
Lajos Molnar
Marco Nelissen
dimitry
Pawin Vongmasa
Martijn Coenen