Revert submission 27007604-pps_topic
Reason for revert: Droid-monitor created revert due to breakages in b/338407263. Will be verifying through ABTD before submission.
Reverted changes: /q/submissionid:27007604-pps_topic
Change-Id: Ice972552ad50f7af883dc0491426797da78f8918
Extend buffer size inside SIT API sitGpsSuplLppPrsInfoSet for larger messages
Provide the option of ignoring SUPL_INIT altogether for testing purposes
Bug: 321191652
Test: b/335776551
atest CtsLocationGnssTestCases
atest VtsHalGnssTargetTest
(cherry picked from https://googleplex-android-review.googlesource.com/q/commit:8bb99b0451d78f75f93f6c80aa4fdb22d12128b5)
Merged-In: Ifa5a6fe4393e7a3a4cb16aff2a09322903f9b78c
Change-Id: Ifa5a6fe4393e7a3a4cb16aff2a09322903f9b78c
p23_common includes 4 devices: `ripcurrent`, `shiba`, `husky`, and
`akita`.
Since `preloaded_nanoapps.json` has different configurations for
`factory` products and `non-factory` products, `soong_namespace {}`
needs to be added to the converted Android.bp file to avoid misuse.
Additionally, due to ag/27008138, ag/27046793, ag/27008143, and
ag/27056982, a common inheritance layer has been added to all
`non-factory` products. Therefore, setting different
`PRODUCT_SOONG_NAMESPACES` in the corresponding `<DEVICE>_generic.mk`
and `factory_<DEVICE>.mk` files will allow factory products and
non-factory products to use different preloaded_nanoapps.json.
Bug: 332219400
Test: 1. lunch <device_name>-trunk_staging-userdebug && \
m -j preloaded_nanoapps.json
2. Check ./out/target/product/<device_name>/.../preloaded_nanoapps.json
It should be the <device_name> version.
3. lunch factory_<device_name>-trunk_staging-userdebug && \
m -j preloaded_nanoapps.json
4. Check ./out/target/product/<device_name>/.../preloaded_nanoapps.json
It should be the factory version.
Change-Id: Ib33c71773617f7a20b3af982f6140f8f8da0ced4
Add an additional layer of inheritance for `aosp_akita`, and
`aosp_akita_fullmte`.
This change adds a common layer of inheritance (akita_generic.mk)
for non-factory products. This makes it easier to configure factory
and non-factory products differently.
Non-factory `akita` products now inherits from
`device/google/akita/akita_generic.mk` which inherit from
`device/google/akita/device-akita.mk`.
aconfig flags: Flag: EXEMPT mechanical refactoring
build flags: Flag: EXEMPT mechanical refactoring
Bug: 332219400
Bug: 335565718
Test: lunch aosp_akita-trunk_staging-userdebug && m
lunch aosp_akita_fullmte-trunk_staging-userdebug && m
Change-Id: Id98e494f8262e0dfe76349369d2e5c0c34eaaa2b
This reverts previous JankCheckTimeFactor from 1.43 to 1.2.
Since the current reported duration doesn't include the GPU
part, the JankCheckTimeFactor needs to be smaller for matching
jank frame detection.
Bug: 204204746
Test: adb shell dumpsys android.hardware.power.Ipower/default;
check adpf sessions' traces.
Change-Id: Ia90372cf08ddc31bfa527553b81e78084ac73f48
Extend buffer size inside SIT API sitGpsSuplLppPrsInfoSet for larger messages
Provide the option of ignoring SUPL_INIT altogether for testing purposes
Bug: 321191652
Test: b/335776551
atest CtsLocationGnssTestCases
atest VtsHalGnssTargetTest
Change-Id: Ifa5a6fe4393e7a3a4cb16aff2a09322903f9b78c
avc: denied { call } for scontext=u:r:hal_contexthub_default:s0 tcontext=u:r:hal_gnss_pixel:s0 tclass=binder permissive=0
Bug: 330120749
Test: Verify PixelGnss HAL can connect to Chre HAL.
Test: Function test verification b/330120749.
Test: b/330120749#comment24 health boot check.
Test: b/330120749#comment25 health boot check.
Change-Id: Ida89c542e8dc4ce29011357255385a0661962e16
Update it to align with the HWUI target duration scale factor,
so the adjusted jank check time duration is same as expected frame
timeline's duration.
HWUI target duration scale factor is 70%, and its inverse value is
approximately 1.43.
Bug: 204204746
Test: adb shell dumpsys android.hardware.power.IPower/default;
Check the device adpf sessions' traces.
Change-Id: Ia5b1090d54cd5b8c9490813a8ba74532a50f2b8a
