1. If the device is powered off by users, boot to charger mode
after plugging in the charger. Otherwise, boot to OS.
2. Disable this feature by default
3. Enable this feature by persist.sys.boot.charger_mode.enable=1
Bug: 251680171
Test: can enter charger mode from power off
Signed-off-by: Jack Wu <wjack@google.com>
Change-Id: Ibd1f88c961d884d8e6f9d0019cf550fd0de1192d
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)
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: I2e9f3cbce55f3f894ca346bafa5ded280086a3ca
Move charger pixel-thermal-symlink from common to project folder
to prevent the GKI version dependencies from blocking init.
Bug: 240897207
Test: thermal_symlinks worked properly in charging mode
Change-Id: I0d3b03c9add57b14f255eb66a1a7a46fa6c4b257
The correct path should be under /data,
or it is not writable.
wpa_supplicant now support p2p overlay configuration, a unified
wpa_supplicant init entry can be used.
Bug: 238601241
Test: create a group and check this group is persisted
after reboot
Merged-In: I3c5523626de22c26cb562c03e9fbd7aabf6d98e7
Change-Id: I3c5523626de22c26cb562c03e9fbd7aabf6d98e7
Test: Tested with tablet with dock. Userspace is able to read
and clear sysfs node successfully
Bug: 218802317
Signed-off-by: Prasanna Prapancham <prapancham@google.com>
Change-Id: I1e97920ff0e810ce2888102f3971b21aabc55909
The correct path should be under /data,
or it is not writable.
wpa_supplicant now support p2p overlay configuration, a unified
wpa_supplicant init entry can be used.
Bug: 238601241
Test: create a group and check this group is persisted
after reboot
Change-Id: I3c5523626de22c26cb562c03e9fbd7aabf6d98e7
User will enable/disable this feature from UI setting
Bug: 239889098
Test: dock-defend is disabled by default
Signed-off-by: Jack Wu <wjack@google.com>
Change-Id: I25376ce6174e4e09ed4a7ce8f1258dc099da4cd8
1) for projects with device specific modules, this property should only
be set while device modules been loaded.
2) also remove "wait_for_prop vendor.device.modules.ready 1" to prevent
infinite wait
3) migrate vendor.all.modules.ready/vendor.all.devices.ready to
init.insmod.<DEVICE>.cfg and set these proprieties while .cfg not
exist
Bug: 238853979
Signed-off-by: Robin Peng <robinpeng@google.com>
Change-Id: I17aa42ef0a459c33871891e5036edf7eea57e39a
SOFT_OCP_TPU/GPU/CPU are no longer used. Clock divider ratio should
also be set accordingly.
Bug: 234275748
Test: Boot and verify
Signed-off-by: George Lee <geolee@google.com>
Change-Id: Icb45b4f30605efaae72bef3ccd1c3d82df8b71a7
To aligned with P22 to move charger thermalHAL setup into common code
Bug: 200615564
Test: build pass and boot to home
Change-Id: Idfe47fe64e4c158f27cd587ca8d768e13292c361
Need to meet energy certification test requirement which needs to
be able to charge FULL.
Bug: 235437635
Test: can charge to full on dock in charger mode
Signed-off-by: Jack Wu <wjack@google.com>
Change-Id: I9f92cffdefbeef8e3671812dbc2891d4fef71230
This reverts commit 980650080a.
Reason for revert: Since the vendor.thermal.symlinks is init early than google-module init
such as gpu cooling, the gpu cooling is not ready while creating thermal.symlinks.
Thermal-hal GPU thermal throttling will fail because there is no thermal-gpufreq-0 in thermal.symlinks.
Bug: 200615564
Test: thermal symlinks can be created in dev folder
Change-Id: Ia3b0999c7a8038f7be5e2390926ff74473c0c339
This reverts commit 58893b442f.
Reason for revert: OTA failues observed during S -> T
Bug: 228927535
Test: Full and Incremental OTA's.
Change-Id: Iec9e15d60dab92213494c9e679de6702f8d56e37
Let vendor_init adjusted the cpusets by device config from the
server. Allow us to study the performance and power impacts
by various experiment settings.
Bug: 223685902
Test: adb remount ; adb push init.gs101.rc /vendor/etc/hw/ ; adb reboot
Test: change persist.device_config.vendor_system_native.<group>_cpuset and check /dev/cpuset/<group>/cpus is also modified
Change-Id: I73369f2cef7b999cb380278503a4dbfcc4cff3cd
