This reverts commit d1fc766d4d.
1.1 clearkey was kept in the old format, but because this manifest is
target-level 2, it should have been 1.0 default to be kept in the old
format.
Bug: b/73556059
Reason for revert: b/76227590
Test: boot
Test: vts_treble_vintf_test
Test: update from PPR1.180315.002 -> (ToT + this) succeeds
Change-Id: I6a437bd77c66a4be679da9cb9b44c5a80cb7a9b4
Qcom's driver can support a max of 512 scan results. Ensure that
wpa_supplicant is in sync with that number.
Bug: 74724482
Test: Device boots up and connects to wifi networks.
Change-Id: I62dbd2bd3789c454e9683320d3a58f67019ea7ee
debug.ramdump.* and persist.sys.crash_rcu should be renamed to
vendor.debug.ramdump.* and persist.vendor.sys.crash_rcu repectively
because they are vendor-specific properties.
Bug: 74266614
Test: succeeded building and tested with taimen
Change-Id: I4d277207b68000160e101456e110656aa483eb83
Removes wifi offload HAL service from Wahoo devices by removing related
entries from wahoo/device.mk and wahoo/manifest.xml
Bug: 74549432
Test: Check logs and verify offload HAL service is not running
Change-Id: I45799d07e49c03bac73037867fd0b1db95da495a
Unclear if advantages are worth cumulative power draw.
bug 73364974
Test: boot taimen, memlat is powersave
Change-Id: I7b5eb176d0f22281e687b9577f5eedf311fb4a11
Given default permission granting as TextClassifier service role, this
exception is not needed any more.
Test: Manually tested to confirm permissions were not granted by default
without TC service role.
Bug: 72222560
Change-Id: I99c8d929b247cda40f4418997be83830d512aea4
Generic System Image does not set any of:
- ro.bt.bdaddr_path
- persist.service.bdroid.bdaddr
- ro.boot.btmacaddr
Set ro.bt.bdaddr_path property on the vendor partition, so that it is
available when GSI image is installed and booted on the system side.
Bug: 71814221
Change-Id: Id9a84e9995f94cc02cb97fedbd4fe289348e73c6
We added four new thermal zones in wahoo. First 4 thermal_zone (0-3)
now are:
mnh_ipu1, mnh_ipu2, mnh_cpu, mnh_lpddr
so we need to shift all our thermal zone offsets by 4. This is also
causing an IO error whenever we call getTemperatures() since the battery
sensor tries to read mnh_ipu1:
taimen:/ # cat /sys/class/thermal/thermal_zone0/type
mnh_ipu1
taimen:/ # cat /sys/class/thermal/thermal_zone0/temp
cat: /sys/class/thermal/thermal_zone0/temp: I/O error
taimen:/ # cat /sys/class/thermal/thermal_zone4/type
battery
taimen:/ # cat /sys/class/thermal/thermal_zone4/temp
19800
Bug: 75842171
Test: VtsHalThermalV1_0TargetTest pass
Change-Id: Iaa54bd69caaa3b9a16324709d6b858a7dec6200e
1.1 clearkey is kept using the old format so that OTA
still works (otherwise, the old libvintf on the device
won't be able to see that 1.1 clearkey is on the device,
and will fail OTA.)
Use the latest <fqname> syntax.
Test: build device
Test: lshal
Test: play Google Play videos
Test: vts_treble_vintf_test DRM passes
Bug: 73556059
Change-Id: I7ef58838dbff0e28e55de2a9e9404571d2006af6
Expose USB-C to calls to getTemperatures() in ThermalHAL for wahoo.
Bug: 67749183
Test: VtsHalThermalV1_0TargetTest pass
Change-Id: Ic45dea1c990e0c71a6ac621145b93cb0f7aa9519
(cherry picked from commit 51872d4950)
If sensorservice goes down while folio_daemon is running, folio_daemon
will gracefully exit and restart. If sensorservice remains down while
folio_daemon is starting, it will eventually crash due to the way the
ASensorManager_getInstanceForPackage() API behaves (i.e., it will exit
with a SIGABRT after five minutes of waiting). We can reduce the
chance of this happening by ensuring folio_daemon is only started when
its dependent services are explicitly started as well.
Note that this cannot guarantee that folio_daemon will *never* crash due
to SIGABRT, since there is no variant of
ASensorManager_getInstanceForPackage() that allows for graceful handling
of the service timeout. Events that negatively affect the availability
of sensors are outside the control of folio_daemon.
Bug: 73555660
Test: loaded on walleye and tested with `stop` and `start` commands
Change-Id: I65e1b72745719f2540bff7cab8e556725486bcad
(cherry picked from commit 9ebb33ed13)
We disabled auto_hibern8 in kernel, so there's no sysfs entry for that.
Bug: 75004568
Bug: 66697973
Bug: 65535484
Change-Id: Iaa95c60435b74ffb97c103701515e9aa55946a91
Signed-off-by: Jaegeuk Kim <jaegeuk@google.com>
Currently, HIDL manifests files only support a single version of a HIDL
interface. Even though the Neural Networks API has defined and
implemented a 1.1 HAL, the only real driver (HVX service driver) is
currently only 1.0.
This problem is similar to that in b/73556059. Soon, HIDL will be able
to support multiple interface versions in the device manifest. Until
then, or until the HVX service driver is upgraded to 1.1, the manifest
will be changed to 1.0.
Bug: 74443090
Test: mma
Change-Id: I46811231dff92e136dfccb88e85b8ce70b89ac1d
* changes:
Remove regex and label the whole directory.
Remove unnecessary permissions.
Grant hal_bootctl permissions for new type.
Ensure taking a bugreport generates no denials.
libnfc-nci.conf shouldn't be a part of vendor image, since it is
accessed by libnfc-nci and Nfc application, both are part of system
image.
Test: Nfc enable/disable
Bug: 72080121
Change-Id: I686ba234c7d2aa923070c3fa980c56b73b18e574
(cherry picked from commit 3197b56882ed9997043d87e6582f6ebaa0fdbace)
The flag definition:
BOARD_USES_SDM845_BLUETOOTH_HAL := true
adds SDM845 Bluetooth components to the build:
vendor/qcom/sdm845/proprietary/bluetooth/hidl_transport/Android.mk
vendor/qcom/sdm845/proprietary/bt/hci_qcomm_init/Android.mk
and removes MSM8998 Bluetooth components from the build:
vendor/qcom/msm8998/prebuilts/grease/target/product/msm8998/Android.mk
vendor/qcom/msm8998/proprietary/proprietary/bt/hci_qcomm_init/Android.mk
Effectively, Walleye/Taimen switch to the same QCOM BT HAL as B1/C1.
Bug: 73968979
Test: Manual build and test with BT A2DP headphones
(cherry picked from commit 7c2dc1679d)
Change-Id: I4d6444932a807e573f6e8d88c6ad4ba4de8f277a
