Camera hints was canceled at activityStop and applied the rule for
a while after LAUNCH hint, exten the LAUNCH HINT to fix it.
Bug: 255927500
Test: build and launch/exit camera
Change-Id: I95031b5aa1d19f618bc3321679015c9be76fdbea
Remove spatial audio configuration in speaker path
to match the rule.
Bug: 247415765
Test: spatial audio playback
Change-Id: Ib6de42e0cf9b97fb47781eb4fee9541c841b89c3
BUG: 237621645
Test: Check the vibrator work normally when using biometric unlock
Change-Id: Ib64abdff6a6e3eec2ead03849cf37b8fdcf0750e
Merged-In: Ib64abdff6a6e3eec2ead03849cf37b8fdcf0750e
(cherry picked from commit 41969d9eab)
Add new system proprty persist.bluetooth.opus.enabled to
indicate devices enable OPUS codec.
Bug: 254609888
Test: atest net_test_stack:A2dpCodecConfigTest#init
Change-Id: I3741ea42b5513ae1dd0cb7609301953a13861293
When exiting camera app, camera daemon is still busy in background,
which may affect the launch animation of launcher. So, limit the cpuset
of camera daemon to little cores for 1 second when there is app launch
hint to improve it. This only happens when camera is running. Also bypass
this behavior when video recording is active.
Bug: 240889279
Test: camera daemon cpuset changed as expected
Change-Id: Idc01944eda94240d14b69f64da1e7620195912a0
Update wifi overaly to enable WPA2 to WPA3 auto-upgrade offload
to capable Driver/Firmware.
With this feature enabled, Pixel can support cross akm roaming.
Bug: 236096597
Bug: 236098039
Test: AU drop test
Test: Roaming and connection test (go/cross-akm-roaming)
Change-Id: Ie6dd4180e2a68a39cc20bd7c4dd8fec13eb05a2b
Since there is no different setting for sub project under same prohject,
we will change the setting file from `bluetooth/project/` to
`bluetooth/` to simplify the file structure.
Bug: 238983662
Test: make sure file added in config folder can be copied into devices
Change-Id: I1b0d6a2107f5d69fd7bf650bad314e920810c156
Merged-In: I1b0d6a2107f5d69fd7bf650bad314e920810c156
(cherry picked from commit 6f30806b78)
A recent change (ag/20028064) has caused regression in HDRnet latency
due to activation of PMU feature and EM profile in 30fps. To mitigate this regression, this CL disables EM Profile and PMU features during the capture time (also increasing the boost profile duration from 1000ms to 2500ms).
Bug: 249665681
Test: HDRnet latency from perfetto trace
Change-Id: I892c9ea2e9b004cb4e47d10f61bc8fbf756682a7
A recent change (ag/20028064) has caused regression in GCA launch
time due to activation of PMU at the camera launch time, and capping the
CPU frequency. This CL prevents PMU activation for as long as we are in
powerhints or power-boosts related to camera launch (LAUNCH, CAMERA_LAUNCH,
CAMERA_LAUNCH_EXTENDED).
Bug: 248718485
Test: Perfetto trace
Change-Id: I6d88e4ccaf6790578223202ee69c105360cfc559
When exiting camera app, camera daemon is still busy in background,
which may affect the launch animation of launcher. So, limit the cpuset of camera daemon to little cores for 1 second when there is app launch hint to improve it, but cancel it right away when there is camera launch hint. Also bypass this behavior when video recording is active.
Bug: 240889279
Test: camera daemon cpuset changed as expected
Change-Id: Ieeafb0d96fbce1b7a97df0e554bd2223529bf1ed
Using PMU feature together with Energy Metric (EM) profile is shown to
have benefits in terms of power, without increasing the framedrop rate.
This CL addes necessary changes to the powerhint files to activate both
features for P10 and C10 device for 30FPS use cases.
Bug: 235147585
Test: ODPM and framedrop tests
Change-Id: I5eb4a6c658a4afdfca6405c106cc2c2542d2c316
This CL updates the paths for the corners as
well as small adjustments to the front-facing holepunch camera.
Test: adb shell setprop debug.screenshot_rounded_corners 1 // then restart sysui
Bug: 238416581
Change-Id: Idfe83b9732b30a8fff92ed1eb5bc8959ab1526eb
