Freezing libraries which are being released in O-MR1.
Note the following remaining items:
- configstore@1.1 will be removed from O-MR1 (since it doesn't
add anything)
- neuralnetworks@1.0 will be frozen later (as it has some
remaining changes in progress)
Bug: 63603463
Test: -Lcheck
Change-Id: I888896a66e742613d0ce64c4ca6206972ac6aca8
They are injected via assemble_vintf by the build system
at build time. See build/make/target/board/Android.mk.
Test: m system_compatibility_matrix.xml, and manually
inspect $OUT/system/compatibility_matrix.xml; it contains
<kernel> versions.
Bug: 64124223
Change-Id: Ibf82efa0805233dedb6badce7e5a4ff62a9ff769
Merged-In: Ibf82efa0805233dedb6badce7e5a4ff62a9ff769
This doesn't actually matter in practice, but this
will help keep the file sane and make sure the wrong
hashes aren't modified in the future.
Test: pass
Bug: 63603463
Change-Id: I89e320d36c41b08ebbcee320ac37565bb1aa708c
Configstore was up-revisioned from 1.0 to 1.1. However no new
APIs were added to 1.1. Therefore configstore in mr1 will be down
revisioned to 1.0.
Bug: 64999074
Test: lshal | grep configsotre
Test: "cat proc/<configstore pid>/status | grep Seccomp " return:
Seccomp: 2
Change-Id: Ia2614439cd620fbe5fbd427571ab55a15089cc47
Do not crash in the vendor layer. The stack will crash
when it fails to initialize.
Bug: 64535243
Test: Bluetooth starts/stops
Change-Id: I69fdd2879c80fa2f006c50f0a42a85e9289b14fe
An invalid type byte can cause an access outside
the bounds of the array.
Bug: 64565737
Test: Bluetooth On/Off
Change-Id: Ie11dd62942f66b9fc60ebce2e4339c37d597fdf0
Full bias nanosecond flag is now set correctly for
legacy GpsData (vs. modern GnssData) implementations
of gps.h measurements, going through default GNSS
HAL implementation.
Change-Id: Iec8f03994b6d9e509221e1323b54dc997319fccc
Fixes: 64482271
Test: Before/after on device with GnssLogger
Vehicle HAL is property based and all properties are considered
optional. It is quite a bit of pain to create new versions of VHAL only
to extend properties.
Bug: 64303350
Test: build and flash, verefied system works stable.
Change-Id: I8adb858f53a5d9d31f7444bf97ae09baf2fffafa
Information such as tombstones and callstack are important when
debugging why a process crashed. configstore's seccomp filter
and selinux policy are currently overly strict and are blocking
the collection of crash data.
In order to keep configstore's sandbox as strict as possible, use
Crash_dump's fallback mechanism to collect crash data. This uses a
local socket to send crash data to tombstoned.
Bug: 64768925
Test: killall -ABRT android.hardware.configstore@1.1-service
Verify that configstore callstack gets dumped to logcat.
Verify that a crash tombstone gets recorded to /data/tombstones
Test: proto_fuzzer runs without crashing
Change-Id: I3c3e13d6aa1c1e2dda2a619dfa815375ee7ebff6
(cherry picked from commit 60ced29112)
This adds a single new member to the HalStream structure, used by
camera.device@3.2::ICameraDeviceSession.configureStreams, for
HALs to override the requested stream dataSpace.
This override may be used when the requested format is
IMPLEMENTATION_DEFINED.
Test: Builds
Bug: 62358514
Change-Id: Ie43e6cfd2ac52657c9366ff5297daa22c0bfa46c
audio_policy_configuration.xml can be loaded from the following places:
- /system/etc/
- /vendor/etc
- /odm/etc
Nevertheless the config validation test was expecting it to be in
/vendor/etc exclusively.
This patch changes the test logic to:
- look for the config files in all 3 folders
- make sure the config is unique
Test: run the following script to check for regressions and test that
invalid config make the test fail.
(
set -xe
runVTS() { vts-tradefed run commandAndExit vts \
--skip-all-system-status-check --primary-abi-only \
--skip-preconditions --module VtsHalAudioV2_0Target \
-t CheckConfig.audioPolicyConfigurationValidation; }
echo "# Test valid config"
runVTS
echo "# Test multiple invalid match"
adb shell touch /system/etc/audio_policy_configuration.xml
! runVTS
adb shell rm /system/etc/audio_policy_configuration.xml
echo "# Test multiple valid match"
adb shell cp /{vendor,system}/etc/audio_policy_configuration.xml
! runVTS
adb shell rm /system/etc/audio_policy_configuration.xml
echo "# Test invalid config"
adb shell sed -i /defaultOutputDevice/p /vendor/etc/audio_policy_configuration.xml
! runVTS
adb shell sed -i '"/defaultOutputDevice/{p;N;d}"' /vendor/etc/audio_policy_configuration.xml
echo "# Test that the test did not break the config"
runVTS
)
Bug: 64881365
Change-Id: I9db5e6f727d19fd654a3cc543a2aaab196682001
Signed-off-by: Kevin Rocard <krocard@google.com>
Update default implementation to use the new fields defined explicitly
for passing in target CHRE API version information, rather than adding
this data into the reserved area.
Bug: 64852297
Test: run CHQTS on Nanohub, rebuild test app targeting 1.2 and confirm
it's interpreted correctly
Change-Id: Id11f9b510a2d239d285436e119b7b8dbece4c5df
There exists the following race condition:
a). thread A receives setNotify and sets the callback to some object
b). thread B of the wrapped implementation calls
BiometricsFingerprint::notify which it was given a handle to. Thread B
executes past the nullptr check:
c). thread A receives setNotify and sets the callback to some other
object (or nullptr)
d). thread B resumes in notify with unknown state
Add mutex to protect access to mClientCallback.
Change-Id: I9163204ff5802e9246056caeb2a7857e6138531c
Fixes: 64802340
Test: VtsHalBiometricsFingerprintV2_1IfaceFuzzer
