Define ConnectivityMonitor as _app & isPrivApp.
Give write permission in radio for
PowerAnomaly usecase.
Bug: 112197190
Test: manual - flashed build with changes in "connmon-privapp" topic,
ConnectivityMonitor works as intended
Change-Id: Iaf2ce49af29ed912024b30a07f80df4fe6220328
Bug: 78019660
- There are some wahoo devices occur unlabeled denials on persist_rfs_file
(/persist/rfs/msm/mpss/server_check.txt) with doing restorecon /persist.
- server_check.txt will be checked and re-generated whenever tftp_server is up.
Remove it and let tftp_server to re-generate it to workaround the denials on
these devices
avc: denied { getattr } for comm="tftp_server" path="/persist/rfs/msm/mpss/server_check.txt" dev="sdd3" ino=74 scontext=u:r:rfs_access:s0 tcontext=u:object_r:unlabeled:s0 tclass=file permissive=0
avc: denied { read } for comm="tftp_server" name="server_check.txt" dev="sdd3" ino=66 scontext=u:r:rfs_access:s0 tcontext=u:object_r:unlabeled:s0 tclass=file permissive=0
Change-Id: I105485111a2ca6072d596160fa7390e43e483b01
Signed-off-by: SalmaxChang <salmaxchang@google.com>
In current implementation, the icnss stats is not presented in
dumpstate_board.txt file because the file owner/group is set to
root/root.
This commit changes the owner of the file to system/system to enable
the bugreport to dump the info in dumpstate_board.txt. This setting is
consistent with other devices.
Bug: 111845187
Test: adb bugreport and check icnss stats in dumpstate_board.txt
Change-Id: Ieff0841b1aafc7428a9f88ffb7fb2c0ac9075f24
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
The Hearing Aid Profile was disable in an upstreamed branch and we need
to re-enable it here.
Test: Compile
Change-Id: I1fae1e66570d69e14d53c415838e882639761ec9
The code was only allowing the Learned Capacity to decrease while
QCOM FG learned capacity may actually go up for some reasons.
Ensure we use the FG learned capacity on update and always restore
the saved one on boot.
Bug: 109734601
Change-Id: I21b559c27a5298e8eea39ec502e4f1d6f7a4b053
Signed-off-by: Thierry Strudel <tstrudel@google.com>
These products have warnings about overriding build commands, which
means that there are multiple instructions on how to build a file, and
we've just picked one of them. Which one we pick is usually stable, but
it can change.
Bug: 77611511
Test: turn default to false, walleye still uses a warning
Change-Id: I11d194863b313f64b19291f65219682b169d9ced
This daemon doesn't exist on the device and causes init errors during
boot.
init: /vendor/etc/init/hw/init.walleye.rc: 745: Unable to decode GID
for 'qcom_diag': getpwnam failed: No such file or directory
init: Could not start service 'vendor.qmuxd' as part of class 'main':
Cannot find '/vendor/bin/qmuxd': No such file or directory
Test: tree-hugger passes
Merged-In: Ib2bc1739cac088af3e9ef2e0482f2536dad8fb8c
Change-Id: Ib2bc1739cac088af3e9ef2e0482f2536dad8fb8c
