add persist battery folder for BatteryDefender
Bug: 258535661
Test: confirm the BatteryDefenter feature works fine
Change-Id: I5e2925d4fe188e0a104f2b20e7b230d60d7f8039
Signed-off-by: Wasb Liu <wasbliu@google.com>
Since retry times of kernel driver are 24 during USB enumeration,
the total time of bad USB enumeration will waste 48 seconds.
This patch will reduce the timeout from 2 seconds to 500ms, so the
total time is changed to 12 seconds.
(cherry-pick from commit dd9bb5578cd197b44f32c0c19aca79610b5bdd54)
Bug: 256100001
Test: the timeout value is 500
Change-Id: I6c30e3c9168242f5c22443cbd5622892617e0520
Signed-off-by: Puma Hsu <pumahsu@google.com>
Add pixel temperature residency metrics paths in sysfs paths list for gs201
Bug: 246799997
Test: Verified the existence of atom and correctness of atom stats
Signed-off-by: Ziyi Cui <ziyic@google.com>
Change-Id: Ib0788756eb77490e257145bd90c9b8041149ede0
Bug: 241739027
Test: trigger bugreport with `adb bugreport` and inspect the
logs to to make sure it is copying over LoggingMaskHistory and
including it in the tar file at the end.
Change-Id: I93ad2655193c57a0782c1535dc1cde3d0db1aeec
To support input device lights manager feature in frameworks, provide
sysfs node access to system server process.
DD: go/pk_backlight_control (For keyboard backlight control for external
keyboards)
Similar CL: ag/20102346
Kernel provides a standardized LED interface to expose LED controls
over sysfs: https://docs.kernel.org/leds/leds-class.html
The feature will be provided for devices with kernel sysfs class led
support and vendor kernel driver for input controllers that do have
lights. The kernel sysfs class led support is a kernel config option
(LEDS_CLASS), and an input device driver will create the sysfs class
node interface.
By giving system_server the access to these sysfs nodes, the feature
will work on devices with the kernel option and kernel input/hid driver
support. We do use CTS tests to enforce the kernel options and the
input device drivers.
What's already supported:
- We already expose paths for UHID based LED nodes which covers all
bluetooth based peripherals that have custom vendor drivers to expose
LED sysfs nodes. (see CL aosp/1546377)
What's included in this CL:
- Exposing paths for sysfs nodes for external USB based devices that
expose LED nodes using vendor specific drivers using standard LED
interface provided by Kernel
- We are using specific paths for USB devices instead of
/sys/class/leds to avoid giving access to system LED nodes that would
also appear under /sys/class/leds (see discussion in aosp/1546377)
NOTE: Light HAL should never touch the HID device sysfs light, as the
light HAL only defines a number of lights supported
(https://android.googlesource.com/platform/hardware/interfaces/+/master/light/2.0/types.hal)
but not include input device lights, so we shouldn't have conflict
for managing these lights.
NOTE: External keyboard backlight is different for HAL light type
KEYBOARD which is for devices with attached keyboards.
Test: manual
Bug: 245506418
Change-Id: I17031179b7c1e56b0e841d4047859006d005fd21
This reverts commit f7f4d8e84f.
Reason for revert: The issue b/255244818 caused by cl/476717338 is fixed in cl/477452462 on QPR2.
Bug: 257660234
Test: CTS
Test: Check DSP-TPU landmark is enabled.
Change-Id: I122b3d786cf670515fc471baa043fdd4ccdf0d72
This app files bugreport for user-debug build with reboot reason = ocp
or uvlo. Removed the dependency on BetterBug.
Bug: 237287659
Test: Ensure bugreport is generated under user-debug build with reboot
reason = ocp or uvlo.
Signed-off-by: George Lee <geolee@google.com>
Change-Id: I267f077e9c6c856b038b008397c0b465d209d9c3
(cherry picked from commit d0d71a7ce8)
Merged-In: I267f077e9c6c856b038b008397c0b465d209d9c3
This app files bugreport for user-debug build with reboot reason = ocp
or uvlo. Removed the dependency on BetterBug.
Bug: 237287659
Test: Ensure bugreport is generated under user-debug build with reboot
reason = ocp or uvlo.
Signed-off-by: George Lee <geolee@google.com>
Change-Id: I267f077e9c6c856b038b008397c0b465d209d9c3
In aosp, the name of the variable changed from
FORCE_MULTILIB_FIRST_ON_DEVICE to IGNORE_PREFER32_ON_DEVICE.
So actually modify this so the new devices don't have 32 bit
servers.
Test: Verified that drmserver/mediaserver are 64 bit processes.
Change-Id: I282f5129bcc91d99e924f514b01fc4e7e37e9ea9
