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
This HAL has been replaced with AIDL, so it does not exist anymore,
causing VtsHalBluetoothAudioV2_0TargetTest and VtsHalBluetoothAudioV2_1TargetTest
to fail.
Original Change: https://googleplex-android-review.git.corp.google.com/c/device/google/gs101/+/20061228
Bug: 231275829
Test: presubmit
Test: VtsHalBluetoothAudioV2_0TargetTest VtsHalBluetoothAudioV2_1TargetTest
Change-Id: Ie091dfce3c63be4fd6d0ed5b6600587aa56862cd
Ignore-AOSP-First: Dependent on internal change.
Bug: b/205760172
Test: Run confirmation UI test using CTS Verifier
Change-Id: Ifb3f692284eec45ca0c17838c1f39eaf2661650d
(cherry picked from commit 934b040eea)
Merged-In: Ifb3f692284eec45ca0c17838c1f39eaf2661650d
This variable is always false or empty now.
Remove it so we can mark it as deprecated later.
Bug: 241346584
Test: Presubmit
Change-Id: I57cbe875f556bb853d4ea9b1d458c9c554c6bfa5
Add NAVIC factory test to improve the time of L5 CW test
Fix millisecond error in receivedSvTimeNanos and the corresponding pseudoranges
Add protection code when gpsd call sensor API
Fix invalid sensor availability status report in the PGLOR msg
Bug: 235192024
Bug: 236572839
Bug: 240389454
Bug: 244118456
Verify test: 249174832
Test: atest VtsHalGnssTargetTest
atest CtsLocationGnssTestCases
atest PtsChreTestCases
Change-Id: I7085931ec83cc58515fefaf1be14e228cd64b5df
Ignore-AOSP-First: Dependent on internal change.
Bug: b/205760172
Test: Run confirmation UI test using CTS Verifier
Change-Id: Ifb3f692284eec45ca0c17838c1f39eaf2661650d
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
