Use CAMERA_LAUNCH_EXTENDED to not limit max CPU frequency.
It improves launch time and buffer allocation latency especially for high memory pressure cases.
Bug: 208362912
Test: GCA
Change-Id: I85df14aaaad56232f6ffaef316adb0c6dde3e06f
init: change file owners of sysfs nodes min_vrefresh and
idle_delay_ms in order to grant permission for hwcomposer
Bug: 202567084
Test: use the following commands
adb shell "vndservice call Exynos.HWCService 1005 i32 0 i32 30"
adb shell "vndservice call Exynos.HWCService 1006 i32 0 i32 1000"
Change-Id: Ia072a9826402bdf23d2577b8dc7f82b5e4d903f6
Bug: 205240941
Test: regression test is passed. (b/207432169)
Signed-off-by: Carter Hsu <carterhsu@google.com>
Change-Id: Ieb6ff80aa61108e18fed65ad02f9754f59a2812c
Bug: 207587485
Test: ESW crash dump can be found under data/vendor/gps/logs after
running command :
echo Lhe:write=0xFFFFFFFF,4 > /data/vendor/gps/LheConsole.toAsic
Change-Id: Icf3505a8d29e867f81eb513d25bf790085a2819f
Add vid/pid 04e8/6862 for dm condition in NCM
Test: The usb gadget functions work normally
Bug: 206565428
Signed-off-by: Ricky Niu <rickyniu@google.com>
Change-Id: I04fba9fc137848d7f1c97a288bb12d76a613badc
This reverts commit e2da019e13.
Since the temperature getting struck at 10 degC b/192030129 has been fixed,
reenable dynamic Tj thresholds.
Bug: 202736847
Test: build and boot on device
Change-Id: I53c62595407ea156ee3aceef0d3723db46096b8f
To mitigate Synthetic load in brownout test, we need to increase
UVLO1 to 3.2V, UVLO2 to 3.0V, and SMPL_WARN to 3.1V.
Bug: 200943374
Test: Local Test
Signed-off-by: George Lee <geolee@google.com>
Change-Id: I182d55f3a898d6e9adc8d86747ae62541a1c8fab
Somehow FW will be unstable after dumping status.
Temporarily remove this to find out the root cause
with vendor.
Bug: 193467774
Test: lshal debug android.hardware.dumpstate@1.0::IDumpstateDevice/default pre-touch
Signed-off-by: Super Liu <supercjliu@google.com>
Change-Id: I670558f30f9d809a8f9df41e4844ee451c7f3f17
Bug: 193467774
Test: check bugreport for touch pre-logs.
Signed-off-by: Super Liu <supercjliu@google.com>
Change-Id: Iccf138fd891fd54bf22a56e8ed57643ef4d7d384
Bug: 193467774
Test: check bugreport for touch pre-logs.
Signed-off-by: Super Liu <supercjliu@google.com>
Change-Id: I5c854866302333df7eac803b0366d432bc8d2540
Copy default gps.xml to only specific projects under gs101 and maintain
new projects in their own folders.
Bug: 203745796
Test: Build test and check config
Change-Id: Ic0b6f8a6e41063f5c42573aea91650007963912b
This is not needed in device-specific init.rc file, because it's
is superseded by commit https://r.android.com/1866693.
Bug: 203720638
Test: presubmit
Change-Id: I9798f0fa868e453b62dcdd8d7b4ee7a94c7f148f
(cherry picked from commit e77021b4c4)
As dma devices are 36bit bounded, we don't need SWIOTLB
bounce buffers. Set swiotlb=noforce to disable this and
make the minimum amount of memory allocation.
Bug: 205246642
Test: check total memory and io_tlb_nslabs
Signed-off-by: Martin Liu <liumartin@google.com>
Change-Id: If9f68b269f326f0f4b8e165593ec5dd4787fbb52
Bug: 200221875
Test: build and check camera HAL APEX content for affected devices
Change-Id: Ic3b9c50fa63b656f7e5a42d2687f4e6775720e55
Merged-In: Ic3b9c50fa63b656f7e5a42d2687f4e6775720e55
This patch adds a dependency on the dwc3 device probing before setting
the sys.usb.controller property. Without this, we have a race between
fastbootd starting and the dwc3 device probing. If fastbootd starts
before the dwc3 device probes, then the recovery init.rc will fail to
setup the USB gadget resulting in "fastboot devices" failing to detect
the device.
Bug: 202338035
Test: verify device is detected in fastbootd
Change-Id: I146451eae03f23dde915c00af3028681be41a8c1
This is not needed in device-specific init.rc file, because it's
is superseded by commit I300265f4af9c2781d40537f391bda9eaf62c27ba.
Bug: 203720638
Test: presubmit
Change-Id: I9798f0fa868e453b62dcdd8d7b4ee7a94c7f148f
HDM debug information already expend to 64 bytes. Dump whole debug
information when bugreport is triggered.
Read HDM debug information twice to check if any status events keep
changing.
Bug: 174191180
Test: trigger bugreport and check the data.
Signed-off-by: davidycchen <davidycchen@google.com>
Change-Id: I9d2f9ed094f85dae303ba47e85a182adcd6954ac
Reflect the pKVM experiment status from the property into the misc
partition so the bootloader can apply it next boot. This is only done on
builds that don't have pKVM enabled by default by pkvm_enabler.
Bug: 192819132
Test: set property and observe change in pKVM state at reboot
Change-Id: Ief85fa196f630867d0a0ced7fa4744f0241d41ea
