Pixel 5a (barbet) does not support Pixel dump, we need to exclude build
Pixel dump for Pixel 5a (barbet). The git_24Q2-beta-release TARGET_PRODUCT is barbet_beta, updated to barbet% for all barbet target products.
Bug: 330819191
Test: Local build and trigger a new build the result passed
(cherry picked from https://googleplex-android-review.googlesource.com/q/commit:d4de4ddf902f75ebcb6b0e1079e78b8a96410ed5)
Merged-In: I2c1785105bab74a483bc68893d96a8a88eabfd90
Change-Id: I2c1785105bab74a483bc68893d96a8a88eabfd90
TTS voice packs are better to be common for all devices
So the other device configs can have the common TTS voice packs
for the device build by "gs-common/device.mk"
And see doc, Preload Google Text-to-Speech (TTS) Voice Packs:
The voice packs are dowloanded follow the steps.
Bug: 333626474
Test: build passed and manual test
Change-Id: Idebba7ef2e69d0e9d2f30a94cbbcf70d2e3568d5
They include the domains:
1. dump_ramdump
2. ramdump
3. ramdump_app
4. sscoredump
5. ssr_detector_app
We copy policies of domains of ramdump and sscoredump from hardware/google/pixel-sepolicy to gs-common but don't remove them there to keep compatibility for other projects.
New SELinux policies:
1. Create a new file context of /data/vendor/ssrdump/logcat for SSRestartDetector to write device logs when it detects new coredumps.
2. RamdumpService will also access the path to compress device logs to zip files of coredumps.
Bug: 298102808
Design: go/sys-software-logging
Test: Manual
Change-Id: I02c2e1569a95ea90901d9476ef75bca74a4f43e1
Revert submission 26348985-bb-sepolicy-poc
Reason for revert: Droidfood blocking bug: b/327991669
Bug: 327991669
Reverted changes: /q/submissionid:26348985-bb-sepolicy-poc
(cherry picked from https://googleplex-android-review.googlesource.com/q/commit:aca06d61c64f947252808f73fbe01fdda5109c0e)
Merged-In: I0fe0bb22e293093d941b4d8ba826c8c8689a370d
Change-Id: I0fe0bb22e293093d941b4d8ba826c8c8689a370d
24D1-dev is based on 24Q2-release. Therefore, we merged this CL to 24D1-dev.
Since the gsc firmware doens't support mDL since MAIN-00009, we'll need
to remove HAL accordingly to avoid inteface confusion.
Bug: 330415816
Test: PTE release test
Change-Id: Ie91817c926d77209c8ac1119dc74053cb0f6215a
Revert submission 26593083-lassen_pps
Reason for revert: Culprit for test breakages in b/331680556. Will be verifying through ABTD for confirmation and before submitting the revert.
Bug: b/331680556
Reverted changes: /q/submissionid:26593083-lassen_pps
Change-Id: I97e29eaf09238d708fb9d941a5988ad42d583655
Write usage: setprop vendor.touch.gti0.ical VALUE
Any VALUE(e.g. 20X or 30X) set through this property will write
into gti interactive_calibrate sysfs except for the VALUE `read`.
Read usage: setprop vendor.touch.gti0.ical read
getprop vendor.touch.gti0.ical.result
setprop with VALUE `read` will read the gti
interactive_calibrate sysfs and save the result to
vendor.touch.gti0.ical.result.
Besides, please add your DOMAIN to access vendor_gti_prop.
set_prop(DOMAIN, vendor_gti_prop)
Bug: 331139251
Test: Manually verify the result.
Change-Id: I6296b9533dd0209e66832bfbbed6030a30077b96
Merged-In: I6296b9533dd0209e66832bfbbed6030a30077b96
Signed-off-by: Super Liu <supercjliu@google.com>
(cherry picked from commit 28754e355a)
Write usage: setprop vendor.touch.gti0.ical VALUE
Any VALUE(e.g. 20X or 30X) set through this property will write
into gti interactive_calibrate sysfs except for the VALUE `read`.
Read usage: setprop vendor.touch.gti0.ical read
getprop vendor.touch.gti0.ical.result
setprop with VALUE `read` will read the gti
interactive_calibrate sysfs and save the result to
vendor.touch.gti0.ical.result.
Besides, please add your DOMAIN to access vendor_gti_prop.
set_prop(DOMAIN, vendor_gti_prop)
Bug: 331139251
Test: Manually verify the result.
Change-Id: I6296b9533dd0209e66832bfbbed6030a30077b96
Signed-off-by: Super Liu <supercjliu@google.com>
Pixel 5a (barbet) does not support Pixel dump, we need to exclude build
Pixel dump for Pixel 5a (barbet). The git_24Q2-beta-release TARGET_PRODUCT is barbet_beta, updated to barbet% for all barbet target products.
Bug: 330819191
Test: Local build and trigger a new build the result passed
Change-Id: I2c1785105bab74a483bc68893d96a8a88eabfd90
This reverts commit 442f99acaf.
Re-enable MTE in this process now that the underlying issue has been
fixed.
Bug: 324412910
Test: Boot the device, observe no crashes.
Change-Id: I8b9e093f25b33b94e0c9635815d9b0a6e2f91b70
tmu intpend register dump sysfs is added so add the sysfs in thermal
dump script as well
Bug: 271619423
Test: adb bugreport
Change-Id: I9d5fe4302ce6101837a075ab46798e5f49a61d7d
Bug: 329367768
This is the basic SELinux setup for a HAL. Since this lives in
gs-common and not all pixel devices will have the corresponding vendor
manifest, this hal will have to be marked as optional.
Test: If this was configured incorrectly, then the build should fail
Doc: go/shared-modem-platform-cpp-backend
Change-Id: I6dd0ee3d68ff226e14e3bdffe2e828c1184c1a01
rpmb_dev is a mock implementation of rpmb for storageproxy.
It is used on emulation platforms where we don't have
real rpmb support in ufs.
Change-Id: I7a0d9e3ae2fef4c7652df9558c1d0aaaea328949
Test: storageproxyd
Bug: 328769740
Signed-off-by: Yurii Shutkin <shutkin@google.com>
Bug: 328704096
The soong config variable should be defined for all pixel products to
enforce backwards compatability (ensure that this is never built for non
enabled devices). In the case where `SHARED_MODEM_PLATFORM` is not
defined, then the soong config variable will choose the default
placeholder implmentation.
Doc: go/shared-modem-platform-cpp-backend
Test: Build for enabled and disabled targets and ensure that the
correct version of `shared_modem_platform` is being built.
Change-Id: I06ebdada2324fdd86cbb7718fd66602dd52070ea
