The common data providers will be moved to gs common directory. So
I removed them in this directory and used gs common library to get
the APIs.
Bug: 206576142
Test: dumpsys android.hardware.power.stats.IPowerStats/default
Change-Id: I81e7a957490fb563fdf25a6434aaf5e886456c5d
Signed-off-by: Darren Hsu <darrenhsu@google.com>
Add build target for libgpudataproducer for AGI support
Bug: 208165749
Test: libgpudataproducer can build for gs201 builds
Signed-off-by: Siddharth Kapoor <ksiddharth@google.com>
Change-Id: I4c16f28267e4a5733e84faf9ce3496dff244f25f
This property is found no used and causes a SELinux avc denial error,
so remove it accordingly.
auditd : type=1107 audit(0.0:4): uid=0 auid=4294967295 ses=4294967295
subj=u:r:init:s0 msg='avc: denied { set } for
property=dev.usbsetting.embedded pid=1 uid=0 gid=0
Bug: 184103246
Test: forrest test build
Signed-off-by: Albert Wang <albertccwang@google.com>
Change-Id: Ic077ae729cdf0a0f04aeec2e04aecdfe7011b52a
This reverts commit 11475b1588.
Reason for revert: b/208845456 disable modem logs until PCIe can sleep correctly
Change-Id: I86df81c96685c571a3deb478b3b24141f89e0e22
Add a file "fstab.gs201-fips" alongside the existing "fstab.gs201" in
order to specify different encryption settings in FIPS mode.
"androidboot.fstab_suffix=gs201-fips" on the kernel command line will be
used to select the FIPS fstab when needed.
As the two fstabs should be otherwise identical, generate them from a
template file so that they will stay in sync.
Note that generating the fstabs requires that they be installed as build
system modules rather than via PRODUCT_COPY_FILES, which results in the
vendor_ramdisk copy of the fstabs being installed to system/etc rather
than /. This shouldn't cause any problem, now that Android has been
updated to look for the fstab in this location too.
(cherry-pick from device/google/gs101)
Test: Boot to home screen with/without fips mode
Bug: 202417706
Signed-off-by: Konstantin Vyshetsky <vkon@google.com>
Change-Id: I8fdc1c9a91399816fa2d4c53f282d63e988ce7d5
In this commit, I remove WiFiOverlay and will add it into project
folder.
Bug: 204946036
Test: overlay configuration works as expected.
Change-Id: Iac69ff8749de7c2f43117f8e136bbfd0bd9a719d
- This fixes ravenclaw build by continuing to use slider as
target_device for camera tuning.
- Can be updated in the future by properly providing ravenclaw
target_device throughout 3A.
Bug: 204945921
Test: Compiles.
Change-Id: Icb010127eedde87e2c2e0f59d6061d52f53e3ec5
The current name is confusing, as "device" normally refers to the
product name, not the SOC name.
Bug: 203283069
Test: build and flash affected devices
Change-Id: I51014a3316dec4509e0113280b723efb95d26fad
Enable the realted property and the needed files
for MMAP use cases.
Bug: 202810406
Test: Oboetester
Change-Id: Ie851dc0152589f405558c744b0101115d9f1d9b0
Currently the persist partition is formatted as ext4. In order to
convert the partition to f2fs without losing data, add a script which
will copy the partition contents out, format the partition as f2fs and
then copy the contents back.
Bug: 202511062
Signed-off-by: Konstantin Vyshetsky <vkon@google.com>
Change-Id: I89502694d1e02261902525c11ac875dd7756721b
Enable building pvmfw.img through PRODUCT_BUILD_PVMFW_IMAGE for products
that currently enable pKVM. Note that the board-provided
BOARD_PREBUILT_PVMFWIMAGE may still overshadow that flag.
Bug: 199831815
Test: m ${ANDROID_PRODUCT_OUT}/pvmfw.img
Change-Id: Iefd5fcf1ce04b14b37ff9555db9acabffb010cff
