Increase disconnect timeout from 10ms to 100ms for the host ports which
dont strictly adhere to the spec to sense disconnect.
This is a work around given that some of the root ports dont detect
it. From the USB 2.0 spec guidelines, the disconnect should be
detected in 2.5us.
From the USB 2.0 spec (pg 186)
Time to detect a disconnect event
at a hub’s downstream facing port
TDDIS Section 7.1.7.3 2 2.5 µs
Bug: 110412433
Test: Walleye entering accessory mode in USB 3.0 with IOGear cable
and USB 3.0 host.
Change-Id: I8d8f62dc1a7bcbc9c7727c51cad7f3cb07ba6b50
(cherry picked from commit 28ad0a90cf)
Some Pixel devices had a wrong brand value provisioned into keymaster.
Due to this misprovisioning those devices fail device ID attestation because it includes a check for the correct brand value.
This is now solved by re-trying Device ID attestation if we are running on a potentially misprovisioned device, allowing for the known incorrect brand value.
Bug: 69471841
Test: atest com.android.cts.devicepolicy.MixedDeviceOwnerTest#testKeyManagement
Change-Id: I41b51a355e1b582fd7c7f12f8b7e0992294b16e3
Merged-In: I73dd4501416bcc2587d137d8b1e27127e3bfc0c0
(cherry picked from commit 0e5b3f1396)
Test labs use start and stop charge levels to control the battery levels
of DUTs. This is not currently possible since retaildemo mode is set to
0 on every boot. After this behavior is removed, it will still be
possible to reset the charging behavior via a factory reset.
Bug: 112763954
Change-Id: I73992bb44d32357f0ed41b55fc551db79c486338
Signed-off-by: Maggie White <maggiewhite@google.com>
Add property to disable usb overheat mitigation that prevent device
offline during thermal testing in chamber.
Bug: 111762741
Test: Run thermal test in chamber
Change-Id: I23a760c8e31979b38ae89cd6750ae107605d5c3b
ro.vendor.graphics.memory and vendor.debug.rs.* are used by Render
script (one of same-process HALs).
So they should be public-readable because Render script can be loaded
from almost everywhere.
Bug: 109653662
Test: succeeded building and tested with taimen
Change-Id: I5c6d6dd2f2406feaec60c965a763215c4a064f52
vendor.debug.egl.changepixelformat and vendor.debug.prerotation.disable
are used by libEGL (one of same-process HALs).
So they should be public-readable because libEGL can be loaded from
almost everywhere.
Bug: 80135368
Test: succeeded building and tested with taimen
Change-Id: I2e9c0809a4868329ab76a94800a144283f523579
Merged-In: I2e9c0809a4868329ab76a94800a144283f523579
(cherry picked from commit 52ca941f7a)
Since NFC has a common vendor library, adding dontaudit rules
for properties which are not used by this product.
type=1400 audit(0.0:35): avc: denied { read } for comm="nfc@1.1-service"
name="u:object_r:default_prop:s0" dev="tmpfs" ino=17612 scontext=u:r:hal_nfc_default:s0
tcontext=u:object_r:default_prop:s0 tclass=file permissive=0
Test: check logcat
Bug: 79417308
Change-Id: If2d0a1d3403851d819305f18c96c18eca35db7a8
system properties must not be used as a communication channel in between
system and vendor processes. However, there has been no enforcement on
this: system process could write system properties that are owned and
read by vendor processes and vice versa. Such communication should be
done over hwbinder and should be formally specified in HIDL.
Until we finish migrating the existing use cases of sysprops to HIDL,
whitelisting them in system_writes_vendor_properties_violators so that
the violators are clearly tracked.
These violators are allowed only for P, but not for Q.
Bug: 78598545
Test: m -j selinux_policy
Change-Id: I60b12f1232c77ad997c8c87e6d91baa14c626e94
Setting PRODUCT_COMPATIBLE_PROPERTY_OVERRIDE to true blocks
System-only-OTA from OMR1 devices because it does not allow some
propertis set by the OMR1 vendor partition.
Only if we include the VNDK snapshot v27 to wahoo devices, remove
PRODUCT_COMPATIBLE_PROPERTY_OVERRIDE from wahoo as well as ag/3694012
for rild.
Bug: 74505580
Test: Check if Bluetooth could be turned on in P-OMR1 walleye device.
Change-Id: I5113988b10f0cdde394ed2fc31ebc9d1ea811e1c
