Preinstalled overlays needn't be signed with the same cert
as the package it overlays, simply being preinstalled is
enough. Sign with the default cert instead for now, which
provides fewer special privileges.
Bug: 162195999
Test: verify values still overlaid correctly
Change-Id: I017491fd383551c5aadf8648edb900e0c12a27b8
[ArianK16a]: Adapt to previous configuration
Bug: 148617260
Test: Device boots up and connects to wifi networks.
Change-Id: Iec27a6d947a232a42451ef095dc73d1a52327db5
These are replaced by formal mainline module overlays.
Bug: 143464763
Test: Send for Wifi regression tests
Change-Id: I45881ed210132252b9c5c7d6be03ed845e33f971
The framework was changed in Android R to require explicit authenticator registration.
This change allows apps to continue to use the fingerprint sensor.
Bug: 147445115
Test: Builds
Change-Id: Id3385edc784b2053c8b54ec3153728f4e6e22a45
In Android R, the SurfaceFlinger calculate phase offsets
based on duration. Adopt the new way of specifying
phase offsets to SurfaceFlinger.
Bug: 158464992
Test: scrolling, app launching/closing, playing video
Change-Id: Ia717f5c0075b6adaedaf20dd6be689737edc1415
This CL removes the definition for the hostapd hidl interface from
manifest.xml and rely on vint-fragements entry.
This is to avoid the need to modify the revision in future
Bug: 145780363
Test: builds and wifi softap works
Change-Id: I2a9cb25209efc94f6306f38d89cb5e1ff6f72bed
This CL removes the definition for the IWifi hidl interface from
manifest.xml and rely on vint-fragements entry.
This is to avoid the need to modify the revision in future
Bug: 138243400
Test: builds and wifi works
Change-Id: Icaff93193e10d4953d9947d2739b05959ece79f1
Since these were combined into libhidlbase.
Bug: 135686713
Test: build only (libhwbinder/libhidltransport are empty)
Change-Id: I640a3f0e0839214523627bf0b59fd5ae9dd2c61c
Remove various variables related to where kernel and ramdisk are loaded
by the bootloader. There are two reasons for this:
1. The B1C1 bootloader ignores all the offset values for kernel, ramdisk
and tags. The default B1C1 memory layout has been designed to accomodate
a larger KASAN kernel.
2. The variables BOARD_KERNEL_TAGS_OFFSET and BOARD_RAMDISK_OFFSET are
ignored by the Android build system (unless they are copied into the
BOARD_MKBOOTIMG_ARGS variable). This is in contrast to the variables
BOARD_KERNEL_BASE, BOARD_KERNEL_PAGESIZE and BOARD_MKBOOTIMG_ARGS which
are referenced by build/make/core/Makefile
Bug: 117832711
Change-Id: I3404a4e084ed063d51077a3a80229854362c768b
* Enabling the services allows them to start at their proper stage (class main)
* Enable them on boot to ensure they are enabled before class main starts
Change-Id: I71c3fcb72b38d247d304fda2fa6b2cc76baa0db2
* These modules are disabled by default and started by
init.class_main.sh which we do not ship. Start them from init.qcom.rc
on post-fs-data instead, just like qcrild.
Change-Id: Ifa907b5e33d8d3d08e64baaabfb8e3e450925e96
* We are using the left led as notification LED and hence it
could be breathing or shining while we open or close the
camera. So we don't just set it's brightness to 0 but read
and store the state of the LED before enabling it and
restoring that afterwards.
* To ensure that the left LED is shining while the camera
opens or closes we set it's breathing effect to 0 before
enabling the LEDs.
Change-Id: Ibdfbff3072398bc77ec3257b60622cfc50e8d857
* Give the motor enough time to close in case it was
still opened on boot without showing the error dialog.
Change-Id: Ibc00a999858f5067bbcf07bfecc779f1d0bf3664
* using updateMotor does not make sense here because it
would only close it when the state is MOTOR_STATUS_POPUP,
but we explicitly also want to try to take it back when
it's jammed.
Change-Id: I7594fe01266a514a9fd780d17a91b0c7f957a1e1
