Preinstalled overlays needn't be signed with the same cert
as the package it overlays, simply being preinstalled is
enough. Sign with the default cert instead for now, which
provides fewer special privileges.
Bug: 162195999
Test: verify values still overlaid correctly
Change-Id: I017491fd383551c5aadf8648edb900e0c12a27b8
* 'Display white balance' only works when color_mode is
set to something other than the default value
DISPLAY_COLOR_UNMANAGED (1).
Change-Id: Idaf30a2f2924c461fc0f034f099afaecb5bbf79b
add support for callscreening support in audio_policy_configuration
- add mixer paths related to proxy ports needed in call_screening
Change-Id: Ib0c220fa44c23454e71e772bfa406bd82c06b90d
Generic recording and SVA LAB capture usecase can select
"fast input" or "quad mic" as a compatible profile, due
to the max active count is 1, audio recording and SVA
LAB capture concurrency can be failed.
Move the two profiles to the bottom for exact match
purpose.
Change-Id: Idaa615e653f0cf49e465809ab0034c0e56470a6e
Use usb_surround_sound input profile for usb capture to avoid
opening a new input for the second usb capture.
Change-Id: Id17a5daf9aefb390f374754c340a69b2113fe987
Usecase audio-record and audio-record-compress2 can both be
mapped to record_24 profile, if both the usecases are active,
when BT SCO mic is connected, due to no more available usecases
in audio hal, check inputs for device can fail for other input
profiles which support BT SCO mic.
This makes BT SCO mic connection to be rejected and phone call
can't route to BT.
Add the support for record_24 profile, so existing input handle
can be returned when checking inputs for BT SCO mic.
Change-Id: I63046ec87e35774474e08762fb6aa6275318b2c8
Remove surround sound recording support from audio policy config xml
as its resulting in CTS failure due to mismatch in channel index support
for record usecase.
Change-Id: Idf50b3f2e71c4209720e79c0248ce74bc1a0edf2
Fixes:
E AndroidRuntime: FATAL EXCEPTION: main
E AndroidRuntime: Process: com.android.hotwordenrollment.xgoogle, PID: 4331
E AndroidRuntime: java.lang.NoClassDefFoundError: Failed resolution of: Lcom/android/hotwordenrollment/common/EnrollmentUtil;
E AndroidRuntime: at com.android.hotwordenrollment.common.EnrollmentService.onCreate(EnrollmentService.java:59)
E AndroidRuntime: at android.app.ActivityThread.handleCreateService(ActivityThread.java:4186)
E AndroidRuntime: at android.app.ActivityThread.access$1500(ActivityThread.java:237)
E AndroidRuntime: at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1932)
E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:106)
E AndroidRuntime: at android.os.Looper.loop(Looper.java:223)
E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:7660)
E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
E AndroidRuntime: at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:592)
E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:947)
E AndroidRuntime: Caused by: java.lang.ClassNotFoundException: com.android.hotwordenrollment.common.EnrollmentUtil
E AndroidRuntime: ... 10 more
Change-Id: I5e9605a3ecb9ec080aed554c1541ded9f25c188b
* This was in stock /system/build.prop but since it's
labeled as u:object_r:exported3_default_prop:s0 it
may as well be put in /vendor/build.prop instead.
Change-Id: I5c03cedec64e7364c0733cd2ea416ca6a7b09089
* This was in stock /system/build.prop but since it's
labeled as u:object_r:exported3_default_prop:s0 it
may as well be put in /vendor/build.prop instead.
Change-Id: I462c575da006f096185f515ffb1b050d7bd4ae3c
* For some users L1 isn't disabled on BL unlock.
While this occurence is a true mystery that
I wasn't able to reproduce on my hardware,
it's totally fine to include these blobs in
the vendor image so that these users can enjoy L1.
Change-Id: Ib5fdb7a41fec84a9df03296ad48473e70ce8f208
* Somehow this lib is being loaded by `media.codec` process
and thus along with stagefright vendor plugin fixes video
recording start timestamp (?)
Change-Id: Ib39fb9385b13947b5e1ec6f0bf7e62a22d7ab0c3
Runtime Resource Overlays (RROs) can no longer change the value of
resources in manifest when read during PackagerParser.
This change uses component-override to enable the service by default.
Remove usages of profile_supported_* from overlays as they no
longer configure the enable state of Bluetooth components.
Bug: 135048762
Test: adb shell pm query-services \
com.android.bluetooth/.avrcpcontroller.AvrcpControllerService
adb shell pm query-services \
com.android.bluetooth/.hid.HidDeviceService
adb shell pm query-services \
com.android.bluetooth/.sap.SapService
Change-Id: I284d254a921b14d1533745611a083f4b5a27d9dc
* Build whatever we can from source
* Import vintf compatibility_matrix and manifest
* Import stock vendor props
Change-Id: I905b2b6c388f6b76844e7cea2def70d10e164dab
* Drop all old rules, but keep tri-state-key.
* Also introduce dashd/wlchgd domain as they are needed for seclabels.
Change-Id: I0a7121f51d106d927866aead746a49b3dea6a149
