Using physical streams reduces power since camera consumes
a bulk of the power.
Bug: 242346116
Test: Manual webcam use; See power reduction
Change-Id: Ibfc0698f410c90049f77f0a071b8b4999fb1cfdd
Signed-off-by: Jayant Chowdhary <jchowdhary@google.com>
Updated overlay file to configure and enable the UWB filter engine on
Raven.
Bug: b/237098661
Test: make, flash, manual test
Change-Id: I421b1b7335d9a403d0cfed5486457c2dfb5fa051
Use runtime resource overlay instead of build time
config overlay so that P21 and later devices are covered
automatically
Bug: 274172776
Test: Manual testing with Messenger app video call
Change-Id: I56f1ab98c09120460af68a5c44c6a243d8d70690
Test: Manually, on a raven or oriole, inspect the output of
`dumpsys batterystats --wakeups`
Bug: 267717665
Change-Id: I92fce56d81a5915184b2c83d3b9c93af54d10af4
Turn off the large JPEG stream on camera1 apps
that experience high power consumption during
video call
Bug: 254350466
Test: Manual testing with Messenger app video call
Change-Id: Ic695299a03fe442e36a35b0770b855ac989c0923
enable load kernel modules in parallel but load some
specific modules in sequential
Test: reboot more than 5000 times without failure
Bug: 229794277
Signed-off-by: chungkai <chungkai@google.com>
Change-Id: Ic4961389d58b5195d252dff15cbb92bb391caacc
This mapping is used by the framework for attributing wakeups. Each
hardware device that can cause wakeups can be mapped to a list of
subsystems that rely on that device for functioning properly.
Adding the mapping of rtc clock in these devices to the "Alarm"
subsystem, which is the only subsystem currently defined by the
framework for wakeup attribution. More mappings can be added as more
subsystems are defined.
Test: Manually: Build and flash a raven/oriole target and run:
adb shell dumpsys batterystats --wakeups
The map output should match the xml file.
Bug: 249370357
Bug: 195684213
Change-Id: I11b8297ac07dee2bba3715e6047271026093c5c8
New structure will make sure all future changes to BoardConfig
will be applicable to AAOS on phone builds.
bug: 227488008
Test: Local build and wifi works on raven and oriole car builds
Change-Id: I928a2fb5cfc876427c382d06d798e684e0691ce9
As HW doesn't have 32 bit address limitation, we can disable
zone dma32 to simplify memory management and improve performance.
Bug: 236225957
Test: boot
Signed-off-by: Martin Liu <liumartin@google.com>
Change-Id: I3297a9a7440e0baf80666152ae9f54e93491f362
Revert "DO NOT MERGE Remove unintended face config am: 875235afbf"
Revert submission 18799414-am-e98f52416a40436ba0044e72d6feed21
Reason for revert: The merge path was only meant for tm-dev.
Reverted Changes:
I6ace51cab:DO NOT MERGE Remove faceauth from raven am: 783e56...
I049a9c205:DO NOT MERGE Remove unintended face config am: 875...
I50ae185c6:DO NOT MERGE Remove unintended faceauth configs am...
Change-Id: I26f6409b50769dac5509313a32517cb270edc779
[O6/R4]
Phasing out config_roundedCornerMultipleRadius config from device
overlay package.
Bug: 224688507
Test: Build ROM and pass presubmit tes
Change-Id: Ie0b0c7b9e3591f11e4a481440943cf0a8b328340
only enable for launched project.
Test: boot to home screen without error and avc denials on R4/O6
Bug: 180676019
Signed-off-by: chungkai <chungkai@google.com>
Change-Id: I374a25b3c7debcf8a268e62f939a7909b31fe1e8
Bring back old usage of status_bar_height, status_bar_height_portrait,
and status_bar_height_landscape by set the size containing cutout size.
Bug: 216782082
Test: make
Change-Id: I05142c120f05bdb5fa0543e61a6f50f46f6b0d82
This reverts commit 25c80c8cca.
Reason for revert: This frequency range is still unstable, needs to be validated before it can be used.
Bug: 223739586
Change-Id: Id3853b1041d441f80b19965f5875040f2aabb8ab
Make pattern vibrate on a higher frequency range to increase the overall
vibration intensity and make the notification vibration more noisy when
the phone is on a solid surface, to address user feedback.
Bug: 210535717
Test: manual
Change-Id: Ic7d97d35e271b23e34dde8afb92dfcee29e7563a
This CL updates resource overlay of
rounded_corner_content_padding
for raven/oriole so that the same device-specific value can be seen
from both the Framework code and the SysUI.
With my previous CL [1], the SysUI continues to see the same value
even after this migration.
[1]: I0c3717c0bdfc928167c6eba06247b37caabf33b9
24d6b891f572f7be419d3acc9793ca68d062cf35
Bug: 215554582
Test: presubmit
Change-Id: Id95b8c063ece7eb43d91f96afe21b4fb01e8b489