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
AU031 graphics drivers introduce SELinux denials for
"vendor_default_prop".
Pending a proper fix, tracking this bug so the new graphics driver
can be merged.
Test: Check that presubmit succeeds.
Bug: 79426077
Change-Id: I775de870c6fae32f35acaa7017192ef12254dd7f
Wahoo devices don't have keymaster4 hardware, just a software
implementation that was used for testing.
Bug: 77307896
Test: Check that the KM4 binary and RC are no longer on the device
Change-Id: I607937921c09bf24bb971bb7ef089aab2346debd
This should help fix presubmit tests.
Bug: 79541095
Test: Built policy.
Change-Id: Ide4401527cce5473288092a6c44fc446e9c1fc27
(cherry picked from commit 703a55c3a9)
Test:
- delete file /persist/battery/qcom_charge_full
- adb logcat to check code flow related health@2.0
- adb bugreport
- no "avc: denied" on health vendor service
- check learned capacity in both
/sys/class/power_supply/bms/charge_full
/persist/battery/qcom_charge_full
-- decrease /sys/class/power_supply/bms/charge_full
to check backup to /persist/battery/qcom_charge_full
-- increase /sys/class/power_supply/bms/charge_full
to check restore from /persist/battery/qcom_charge_full
(simluate the reset condition)
Bug: 78883741
Change-Id: Ib17bc0938d3a4b78376140a8a1008b4fc82220af
Signed-off-by: Jack Wu <wjack@google.com>
b/71936484 has audio accessories failing to connect
when there's a transition to suspend when they're attempting
to enumerate.
Avoid this problem by increasing autosuspend delay
from the default 2s to 7s.
The longest I've seen a device take to enumerate after
vbus is ~3 seconds, this gives a 2x margin.
Test: booted on Walleye, saw no more messages:
[ 472.412555] c0 5675 msm-dwc3 a800000.ssusb: DWC3 in low power mode
between device connection and enumeration.
Bug: 71936484
Change-Id: Ic655f2ce6dec429510cc7c00452da4d49f2392b0
After disabling vendor driver override, supplicant needs to specify
the max channel width and pass it to driver.
Bug: 79236591
Test: manually check channel width is HT80 when operating as GO on walleye
add p2p_go_vht=1, ch_width should be 80MHz
Note: need HIDL wpas_p2p_connect argument fix
Change-Id: I14d04556470c5efa66287f2327d7c6324885e822
We saw a similar denial on Marlin where thermal_engine was trying to
access /dev/diag. This ports that fix to Wahoo to try to fix its
denial.
Bug: 78019417
Test: Build policy.
Change-Id: I3702e705ea4f99a58f4b96008d236d33ecd8045c
(cherry picked from commit 200ded4ed8)
audio.usb.enable.debug is used to dump information of the
audio usb device connected in the vendor implementation.
Bug: 77926553
Test: atest VtsHalAudioV4_0TargetTest
without sepolicy errors
Signed-off-by: Kevin Rocard <krocard@google.com>
Change-Id: Ia36823fab7087c3dd77eade28fe14dc6805a1551
This allows android auto and accessory hid
to both work, and matches functionality
on other device in O.
Bug: 74172000
Test: auto starts
Change-Id: I786cd66bed015c5ad2a4ca668f0d0fbc9c8af507
These denials seem to be caused by a race with the process that labels
the files.
Bug: 77635294
Test: Build policy.
Change-Id: Ieed9c2be18a092e92ec90fc8a07fa17c8ec19308
This reverts commit 6c41af4807.
This is a partial revert; CleanSpec.mk is not reverted.
Reason for revert: prevents boot with O-MR1 vendor + P system
Test: boots
Change-Id: Ib573f525da836f12201fd0f9793441a9fed31969
Fixes: 78550051
Enable the Hearing Aid Profile for Taimen and Wally.
Bug: 78142728
Test: Manual Pairing on various Pixel phones
Change-Id: I1323387592bbedf69b4fc9185b121d616c96fd9e
We've seen these processes trying to access this file, so allow it.
Note that this is likely why they needed the sysfs_diag permission we
granted earlier.
Bug: 77908806
Test: Build
Change-Id: I60a2dae5a0635156070397242f13695678f1d00e
(cherry picked from commit 2e41f0e3f0)
This allows the behavior on userdebug and eng builds and hides it on
user builds.
Bug: 77908806
Test: Build policy.
Change-Id: I0d858a94bb1bab6069107209494536a62019788f
(cherry picked from commit e7e22f5e82)
While snapshot Easel power data is captured in bugreports via dumpstate,
Easel does not provide low power stats on a recurring basis via
PowerHAL, which is the type of data need to detect the presence and
scope of power drain issues in the field. As a temporary workaround,
this set of changes keeps cumulative counts of the number of times
PowerHAL saw Easel's state (an existing sysfs node) as "on" (state 1)
or "not on" (state 0 or 2), and logs the "on" count as cumulative count
and the "not on" count as cumulative duration.
This does not sufficiently address the long term need for cumulative
stats, since this will just be comprised of essentially random snapshots
of Easel's current state. However, for the known issue already being
investigated, this should be enough to gauge the scope of the issue.
sepolicy updates allow hal_power to search/read the directory/file
containing Easel's current state: /sys/devices/virtual/misc/mnh_sm/state
Bug: 77208137
Bug: 36576572
Test: Installed on taimen, used camera for various functions, used
easel debug commands and properties to force it into different states,
captured a bugreport and verified the content against observed "current
state" values from monitoring the state file while performing similar
camera functions.
Change-Id: Ib1ee92db477d2a6c9d6f293fb4fcc2f753b8335a
