property
* Change to address failure with GSI on Camera Extensions due to the
extension not being available on GSI builds
Test: Passed CTS tests on GSI build
Bug: 293999720
Change-Id: Ia9fea23f174c8cafb3568151e131fbac1cd61624
Use the HAL code to control the MCPS and boost
the handset MCPS on SWB scenario
Bug: 292154162
Test: verified on test build
Change-Id: I6418e13a37d9b9d796f726218ce9b5de2534efa9
Signed-off-by: Carter Hsu <carterhsu@google.com>
Built and tested on Husky. Tested by setting a gray wallpaper and
getting the rounded corner rect to apply via begnning a gesture nav
event.
Test: manual
Bug: 284742800
Change-Id: I5b8121311bddbda10ff19df2bfc4e1f9cedd9d23
(cherry picked from commit 275d998342)
ag/24163297 defines a new power boost profile which gets applied during
camera transitioning its zoom ratio. This CL defines the parameters for
this boost profile to enhance the camera performance by relaxing the PMU
capping, which is achieved by setting the SPC thresholds to 100.
Bug: 291979193
Test: perfetto trace (https://ui.perfetto.dev/#!/?s=ee36305fa386b5e1825fe9982b984190b1c804cd3c2d0b0fe9c85b9df94659d7)
Change-Id: Id17721719151d216fa1bd3abd7bad613a0ee1c7b
it seems that there's conflict between samsung_iommu_v9 and trusty_log,
so load samsung_iommu_v9 in serial
Test: build pass and run 2000 times without error
Bug: 290561688
Change-Id: I6af250bbe3089f41229f6d674cc2e4a7eae3cbe1
Signed-off-by: Chungkai Mei <chungkai@google.com>
We found that CPU-MID loop will cause big bouncing (~2 degC) during
light loading test (burncycle with dutycycle), we can avoid such
bouncing by remove stop CPU-MID loop at 39.
Apply same change on CPU-HIGH to avoid similar issue.
Bug: 286773651
Test: run burn8 / burncycle_wih_dutycycle / gb5
Change-Id: I11cfbb940a556793ce1fe6d08ff06fc1df55d52a
Signed-off-by: Peter (YM) <peterym@google.com>
Compile ArmNN shim over the support library.
Remove SELinux permissions and settings for the old HIDL backend.
The AIDL settings will be in the gs-common folder.
Test: Local run of CtsNNAPITestCases
Test: Local run of VtsHalNeuralnetworksTargetTest
Test: Local run of MLTS Benchmark
Bug: 283724775
Change-Id: Ie9862ad196383126fa4f1a684bc2f5326d8fb15c
- SB3 HE
Turn on FENS on Condor V21 WB
Files from the latest attachment on b/291188480
Bug: 291188480
Test: verified by genewang@
Change-Id: Ib7b23277c04d736b9d9435a1831ab6f5a58b5513
- HK3 HE
Turn on FENS on Condor V21 WB
Files from the latest attachment on b/291188539
Bug: 291188539
Test: verified by genewang@
Change-Id: Ia714954f58d32e3d6a95c88c28ada4d1c081e911
By setting sae_pmkid_in_assoc in wpa_supplicant.conf file,
the PMKID generated in SAE authentication will be sent to
driver in External auth status(NL80211_CMD_EXTERNAL_AUTH) message
to driver. This will help driver/firmware to fill the PMKID
in association request frame.
Bug: 290562226
Test: Manual - Confirmed that sae_pmkid_in_assoc=1 is set in
wpa_supplicant.conf file.
Test: Connect/Disconnect with AP configured in WPA3 security
Change-Id: Ied6a1bea868c732e11a0a341e832701c05dd2478
