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
Notes:
- Update the HAL version in VINTF manifest from
AIDL 1.0 to AIDL 2.0
Bug: 245126454
Test: E2E auth enroll, atests
Change-Id: I75bde5164ecb9b7a51088ba5ea4dd6ebbfce9566
(cherry picked from commit 7a25196bf5)
These HALs are already included in VINTF fragments, so
there's no need to be specified here.
Test: TH
Bug: 148808037
Change-Id: Iaa719867c7318a5a1bb180430346ffb50852e556
Merged-In: Iaa719867c7318a5a1bb180430346ffb50852e556
We are too late to upgrade the latest version of libyuv in Android T
to fix color conversion (BT.709 YUV to RGB) accuracy issue in HeifWriterTest when we exposed CQ mode for H/W hevc encoder. Move CQ mode support in Android U.
Note: remove CQ mode support, HeifWriterTest will use software hevc encoder to run the test. Since software encoder only support 512x512 resolution the default color primary is using BT.601 which will not
meet color accuracy issue.
Bug: 242466144
Test: atest android.media.misc.cts.HeifWriterTest
Change-Id: I4e0cf6995980603c9473086a385617e47a16b4b9
These HALs are already included in VINTF fragments, so
there's no need to be specified here.
Test: TH
Bug: 148808037
Change-Id: Iaa719867c7318a5a1bb180430346ffb50852e556
Merged-In: Iaa719867c7318a5a1bb180430346ffb50852e556
Notes:
- Update the HAL version in VINTF manifest from
AIDL 1.0 to AIDL 2.0
Bug: 245126454
Test: E2E auth enroll, atests
Change-Id: I75bde5164ecb9b7a51088ba5ea4dd6ebbfce9566
These HALs are already included in VINTF fragments, so
there's no need to be specified here.
Test: TH
Bug: 148808037
Change-Id: Ie7bd72e3e38a7aa0d25645f47011c8121f643676
Merged-In: Ie7bd72e3e38a7aa0d25645f47011c8121f643676
These HALs are already included in VINTF fragments, so
there's no need to be specified here.
Test: TH
Bug: 148808037
Change-Id: Ie7bd72e3e38a7aa0d25645f47011c8121f643676
am skip reason: Merged-In I95218c593ee614234d60f1d411332a398416923a with SHA-1 52bda3cb87 is already in history
Original change: https://android-review.googlesource.com/c/device/google/gs101/+/2203462
Change-Id: I9a38b7aca42f2e5529fcb2a7618800d89f619d7b
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
