For zumapro it shares the same libacryl_plugins in zuma but for
libexynosdisplay it still has different version between zuma and
zumapro. Add zumapro's own libexynosdisplay for zumapro.
Bug: 357500180
Test: lunch aosp_caiman-trunk_staging-userdebug; \
m libexynosdisplay
Flag: EXEMPT refactor
Change-Id: Iaf07baa8bb93ee6cd3da01e4b50231b7f5023fe9
This will only enable RE-Graphite for stages where the rollout aconfig
flag introduced in I30a59986d1da2dc8355c2b3cf2da436c6cc64120 is also
enabled (and if the force_compile_renderengine_graphite read-only flag
is also enabled.)
Rollout proposal discussed w/ Pixel Graphics leads out of band.
Bug: 380460068
Test: manual validation that RE-Graphite is only enabled w/ aconfig flag
Flag: com.android.graphics.surfaceflinger.flags.graphite_renderengine_preview_rollout
Change-Id: I29bade2e024771b2800ab23236ddab4b12d9425b
Since our feature is not ready, we utilize build flag we applied for this project to project this undone feature built accidentally on other targets.
Test: Run test `UpdatableCrashingBootTest` on caiman `trunk_staging`, `trunk_food` and `next` targets with go/forrest (https://android-build.corp.google.com/builds/abtd/run/L28000030007788752, https://android-build.corp.google.com/builds/abtd/run/L64100030007774323).
Test: Build and flash caiman with `trunk_staging` as target, GIA is up and running.
Flag: build.RELEASE_PIXEL_GIA_ENABLED
Bug: 378865024
Change-Id: Iffa7f11659ece8c0210023630568cdc45132840f
Signed-off-by: Kai Hsieh <kaihsieh@google.com>
Revert submission 30378113-revert-29512389-gia-PMLMEKURMT
Reason for revert: Revert to fix the issue that GIA cannot be started in caimen-next-userdbg
Reverted changes: /q/submissionid:30378113-revert-29512389-gia-PMLMEKURMT
Bug: 367881686
Change-Id: I74a61360d09f85a2404d884090fd2bedb1be4030
Revert submission 29512389-gia
Reason for revert: <Potential culprit for b/378865024 - verifying through ABTD before revert submission. This is part of the standard investigation process, and does not mean your CL will be reverted.>
Reverted changes: /q/submissionid:29512389-gia
Change-Id: Ic00760e1dfa0c23f76b1539b717aa2db2a552971
Root casue: there is no GTI built on ripcurrentpro devices. Solution: Add GTI for ripcurrentpro devices.
Test: go/forrest can successfully build for ripcurrentpro and on CM devices: https://android-build.corp.google.com/builds/abtd/run/L56200030007746343.
Bug: 378811601
Flag: build.RELEASE_PIXEL_GIA_ENABLED
Change-Id: If8a248b1f8f9a9cd82ea1a26aeb5244ec1de12bc
Signed-off-by: Kai Hsieh <kaihsieh@google.com>
The HAL service is needed for Updatable pVMs
Bug: 376015522
Test: get_build_var SECRETKEEPER_ENABLED
Test: VtsSecretkeeperTargetTest
Test: #UpgradedPackageIsAcceptedWithSecretkeeper
Change-Id: Ic1993de0f82feba0979e0403472ed4da79676137
Bug: 367881686
Test: Manually, build and flash the ROM and use `service list` to make sure the service is up.
Flag: build.RELEASE_PIXEL_GIA_ENABLED
Change-Id: Icfeb3d1707ead79f38e355d4502c24f1b5493a26
Signed-off-by: Kai Hsieh <kaihsieh@google.com>
VSS support removed from zumapro and made device specific
BUG: 369721391
Flag: EXEMPT refactor(SUPPORT_VENDOR_SATELLITE_SERVICE)
Test: Manual Test(Satellite Basic Test)
Change-Id: I52cb3e36dedecf7fb8dd14135dfe8da400210144
Makefile contain the following sysprops
bluetooth.profile.bap.unicast.server.enabled
bluetooth.profile.tbs.server.enabled
bluetooth.profile.vc.server.enabled
However, CS indicates the above sysprops aren't defined anywhere
nor read anywhere? Given how the following LE Audio sysprops are
missing from the makefile, and the similarities in naming, we
suspect there was a typo?
bluetooth.profile.bap.unicast.client.enabled
bluetooth.profile.ccp.server.enabled
bluetooth.profile.vcp.controller.enabled
Bug: 372711861
Test: builds
Flag: EXEMPT bugfix
Change-Id: I2e9812060733ba6d380a104d79e58867a3e01aa2
There are 4 partitions that are flashed at the factory and use F2FS fs with
4kb block size:
- /dev/block/by-name/efs
- /dev/block/by-name/efs_backup
- /dev/block/by-name/modem_userdata
- /dev/block/by-name/persist
These partitions can NOT be mounted by 16kb kernels because F2FS
expects BLOCK_SIZE == PAGE_SIZE.
In order to access the files in these partitions by 16kb kernels,
the dump.f2fs tool is used.
This change will perform these steps at boot time ONLY for 16kb mode. For
every partition (efs/efs_backup/modem_userdata/persist):
1. Use dump.f2fs to copy the content of the partition
to /data/vendor/copied/<partition name>.img.
2. If the copy was succesfull, rename /data/vendor/copied/<partition name>.img
to /data/vendor/copied/<partition name>
3. fsync the content of the directory /data/vendor/copied/<partition name>.
After the content of the partitions is in /data/vendor/copied,
bind-mount the partitions to the directory /mnt/vendor. See conf/fstab.efs.from_data.
Note: This change ONLY applies to 16kb kernels. This change does not modify
the original partitions.
Bug: 347015136
Bug: 362368691
Test: $ source build/envsetup.sh
$ lunch [zumapro]-trunk_staging-userdebug
$ m
$ ./vendor/google/tools/flashall -w
Flag: EXEMPT bugfix
Change-Id: Idf46a2a3a4f0b2e91ee4a0322a0c469e055684c8
The setup of the persist partition is moved to init.persist.rc.
This will make easier to configure 16kb targets in follow up
changes.
Bug: 347015136
Test: $ source build/envsetup.sh
$ lunch [zumapro]-trunk_staging-userdebug
$ m
$ ./vendor/google/tools/flashall -w
Flag: EXEMPT bugfix
Change-Id: Ifd17fc1f25ea8cf73470630e14a38116e0b7b96a
For PDK build, the "vendor/arm" path doesn't exist. The modules will be
built from vendor/google_devices/zumapro/prebuilts/gpu.
Flag: EXEMPT bugfix
Bug: 364491703
Test: 1. lunch comet-trunk_staging-eng
2. m libGLES_mali vulkan.mali libOpenCL libgpudataproducer
Change-Id: Ie58b2707fb9774f4a3552561b809c3c15d3803ef
The 16kb kernels need to select the fstab that has this configurations:
- data partition: fstab
- metadata partition: ext4
Bug: 350101696
Test: Built zumapro target and checked mounted partitions
Flag: EXEMPT bugfix
Change-Id: I2fc82946cdbadee7af0b3f6fc026b846fa79a146
For PDK build, the "vendor/unbundled_google" path doesn't exist.
"GoogleDialer" will be built from vendor/google_devices/zumapro/proprietary/GoogleDialer.
Flag: EXEMPT bugfix
Bug: 364510147
Test: export USES_GOOGLE_DIALER_CARRIER_SETTINGS=true; m GoogleDialer
Change-Id: I5c6796036627a5ae208dfda3ea19ead550a55c9a
- power measurement result is on b/262803152#comment5
Bug: 355912013
Test: spatial audio
Flag: EXEMPT bugfix
Change-Id: I1b0712254875bbecc89cd2355a3eac18d3789666
In case of always, we always enable hdcp regardless of drm status.
Bug: 359951297
Flag: EXEMPT bugfix
Change-Id: I477f5c0cfa1350c295c3722a35ab42fb7a9a73e6
Signed-off-by: Ji Soo Shin <jisshin@google.com>
