Supports to enable/disable USB data signaling
Bug: 161414036
Test: Pass USB V1.3 HIDL tests
Signed-off-by: Albert Wang <albertccwang@google.com>
Change-Id: Iffe00f8753206fb66cd3ab96cae5aa5ad9c410cd
The pinner now asks the runtime for these files.
Test: adb shell dumpsys pinner
Bug: 144773394
Change-Id: I8de2a2935901cbd3eaa50ce2d8aa09f61080ba02
Merged-In: Ie633ea788dab3389a3407ec9a461b5837befca46
This change replaces the '/system/lib64/libsurfaceflinger.so' pin, as
the file was removed in ag/12524602. The updated pin relies on
go/aog/1552085, as system_service needs read access to SurfaceFlinger.
Bug: 176197656
Test: adb shell dumpsys pinner (coral)
- shows that /system/bin/surfaceflinger is successfully pinned
adb logcat | grep PinnerService (coral)
- no longer shows a file-not-found error in PinnerService
Change-Id: Iae2a96c5fe4b1f5698d21de9970140321d11c460
Populates a new feature flag to record the level of OpenGL ES dEQP
test support. Updates the analogous Vulkan dEQP feature flag to the
value for the next dessert release.
Bug: 159841535
Bug: 175706433
Merged-In: Ib0fb8f83732d0b3f56bb11a97c84fdc7727c1026
Change-Id: Ic97a65fba95a67e3e16cedd0eb4f3f209f645421
We are going to enforce that each property has an explicit owner, such
as system, vendor, or product. This attaches vendor_property_type to
properties defined under vendor sepolicy directories.
Bug: 159097992
Test: m selinux_policy && boot device
Change-Id: Ibed833cd9e5d786e82985ded6bc62abdf8cd9ded
Fixes:
warning: BOARD_PLAT_PRIVATE_SEPOLICY_DIR has been deprecated.
Use SYSTEM_EXT_PRIVATE_SEPOLICY_DIRS instead.
warning: BOARD_PLAT_PUBLIC_SEPOLICY_DIR has been deprecated.
Use SYSTEM_EXT_PUBLIC_SEPOLICY_DIRS instead.
Change-Id: I752602079de8ff4c5370fe3ec861b8746838d878
* ELF prebuilts were banned in PRODUCT_COPY_FILES starting
May 11th. See b/156534160 for long-term fix which should
override this change.
Change-Id: Icd25b40ca4e4285319775046a1b70de30572be07
High power consumption issues were reported for some HS/CK/Speaker
in close range(1 meter) on hastings platform as they may not have
perfect RSSI golden range logic for power control and always request
SOC to increase TX power to max power level. Newer hastings SOC support
LPA power control to avoid unnecessary higher power consumption.
The change enable this soc feature according to value of property.
And disable it for special remote devices which have been added in BL
when new ACL link is created.
If feature is enabled, controllable power level for remote is L0-L9,
BT controller increase it to L10 or L11 according to RSSI and NAK rate.
Otherwise controllable power level for remote is from 0 to max power
level signified in NVM, most likely L11 for hastings.
CRs-Fixed: 2597191
Change-Id: I354bb34a84aa7a55537e3a595daac54c46d90603
Signed-off-by: Omkar Chandorkar <gotenksIN@aosip.dev>
Signed-off-by: Adithya R <gh0strider.2k18.reborn@gmail.com>
For earpiece to be properly enumerated as a output device,
set valid and supported out_ channel mask.
Change-Id: Ic83b009956ff43567b3acbb186d0069b16e91e83
Adding stereo config channel support to usb surround sound proflle
to address CTS-V failure issue seen due to mismatch in channel mask
support for record usecase
Change-Id: Ib50511d2fa6df24b3aa4764553cd48726129b2c2
Bring raw mixport back and drop "USB Device In" and "USB Headset In" from
"primary input" again.
This partially reverts commit 0b7df4e151.
Change-Id: I547518fbd6318dcb5fcb7c4ab85e8ad9da3d48ad
A compiled build has no chance of booting without the prebuilt
binaries, so fail the build if those are not present.
Change-Id: Iadd43e887d426732e549969ab8deb14194ca818d
* It's largely for testing purposes and it consumes
a large amount of memory. If your hardware doesn't
have graphics then it can be useful, which isn't the
case for shipped devices.
Change-Id: I2348718ad3afba846498572161fa7e83dd8b7ce9
* Drop foreground and top-app cpus
* Set 0-3 as background cpus
* Drop xiaomi iolimit and custom types for shima
Change-Id: I3733e196a8ed090c15d6867b0722425435f31474
If we set 2048KB ra value in the beginning of the
boot process, services initialized at this time would
keep 2048KB ra value even though we adjust the ra value
to 128KB after boot completion.
This may cause memory pressure.
Bug: 174700194
Signed-off-by: Randall Huang <huangrandall@google.com>
Change-Id: I97ee0ee9511eaada011f2634afd68d68cdca4570
