The license declaration can't be handled in Android.bp currently.
So keep them in Android.bp.
Bug: 310058310
Test: NA
Change-Id: I3e25fa07f6b3e1bffaf585d69e342c651b50f6ef
Report COMPLIANCE_WARNING_INPUT_POWER_LIMITED instead of
COMPLIANCE_WARNING_OTHER to flag incompatible chargers. The underlying
logic that generates the warning remains the same, what's changed is
the enum that's being used.
The purpose of the change is to have a warning type that better
represents what actually happens and free up COMPLIANCE_WARNING_OTHER
that was intended to act as a fallback reason code.
The flag enable_input_power_limited_warning controls whether to switch
to the new enum, while the flag enable_usb_data_compliance_warning
controls the new enums that are added as FlaggedApi in the framework.
Both flags need to be on to enable the change.
Bug: 308700954
Test: manual tests with local flag override
Change-Id: I6595706d1b83d533fc2d3e29086773270e045ede
am skip reason: Merged-In Iee542cf5ab4973ee9cb2c1fe66d00b642fdf525b with SHA-1 662e1bc915 is already in history
Original change: https://android-review.googlesource.com/c/device/google/gs101/+/2819677
Change-Id: I1f546f53b63b7db94cd7443650688027c61e185b
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
am skip reason: Merged-In Iee542cf5ab4973ee9cb2c1fe66d00b642fdf525b with SHA-1 662e1bc915 is already in history
Original change: https://android-review.googlesource.com/c/device/google/gs101/+/2819677
Change-Id: I254534a8ec4b951fdc7a5aa8d731f84dda03e900
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
am skip reason: Merged-In Iee542cf5ab4973ee9cb2c1fe66d00b642fdf525b with SHA-1 662e1bc915 is already in history
Original change: https://android-review.googlesource.com/c/device/google/gs101/+/2819677
Change-Id: Ia2839d3e016de4ee45b4323a790ad42abb48c0d6
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
am skip reason: Merged-In Iee542cf5ab4973ee9cb2c1fe66d00b642fdf525b with SHA-1 662e1bc915 is already in history
Original change: https://android-review.googlesource.com/c/device/google/gs101/+/2819677
Change-Id: I5bbe3a94b51939ec0d8050ef32292ec1fb8020ab
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
am skip reason: Merged-In Iee542cf5ab4973ee9cb2c1fe66d00b642fdf525b with SHA-1 662e1bc915 is already in history
Original change: https://android-review.googlesource.com/c/device/google/gs101/+/2819677
Change-Id: Ibae31049dc107670bbc5d13bfac967ebf19c8e55
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
Set `avb_keys=no_such_key` for the vendor_dlkm dynamic kernel partition
to allow booting unlocked devices with a custom kernel. This allows a
few things:
1) Dogfooders can flash a custom kernel without wiping their device.
This can help developers track down hard-to-reproduce bugs without
rolling out a patch to the whole dogfooder population.
2) Developers can uprev their device's kernel without wiping their
device or packaging the kernel with an Android platform build.
Note: we are using "no_such_key" to ensure an AVB keys file doesn't
accidentally get created.
Test: Flash CI build. Then flash custom kernel on top.
Bug: 274825778
Change-Id: Iee542cf5ab4973ee9cb2c1fe66d00b642fdf525b
Merged-In: Iee542cf5ab4973ee9cb2c1fe66d00b642fdf525b
Set `avb_keys=no_such_key` for the vendor_dlkm dynamic kernel partition
to allow booting unlocked devices with a custom kernel. This allows a
few things:
1) Dogfooders can flash a custom kernel without wiping their device.
This can help developers track down hard-to-reproduce bugs without
rolling out a patch to the whole dogfooder population.
2) Developers can uprev their device's kernel without wiping their
device or packaging the kernel with an Android platform build.
Note: we are using "no_such_key" to ensure an AVB keys file doesn't
accidentally get created.
Test: Flash CI build. Then flash custom kernel on top.
Bug: 274825778
Change-Id: Iee542cf5ab4973ee9cb2c1fe66d00b642fdf525b
Checks syntax and simple brace balances for all JSON files.
Test: Edit any json file and try upload
Bug: 127794899
Change-Id: I70ad38f73a4fea908442b4411e3aa7ffbaeb7d88
Trigger fsck on mount of /data if the value of ro.preventative_fsck is
not equal to the contents of /metadata/vold/preventative_fsck, then set
the file to the property to prevent future runs
See b/305658663 for context
Bug: 305658663
Test: Make sure fsck run after first boot and not after second
(cherry picked from https://googleplex-android-review.googlesource.com/q/commit:1bc693d338e8d26307d51bb6731d8e94f1df33f9)
Merged-In: I1263d2d55fe22d994ae8c8654b1e75ad9e4ddafe
Change-Id: I1263d2d55fe22d994ae8c8654b1e75ad9e4ddafe
Trigger fsck on mount of /data if the value of ro.preventative_fsck is
not equal to the contents of /metadata/vold/preventative_fsck, then set
the file to the property to prevent future runs
See b/305658663 for context
Bug: 305658663
Test: Make sure fsck run after first boot and not after second
Change-Id: I1263d2d55fe22d994ae8c8654b1e75ad9e4ddafe
Vendor sched procfs path hierarchy gets updated in kernel.
Update the paths in init rc file and task profiles to match the change.
Bug: 289151587
Test: UIbench ab test
Change-Id: I6f8aa26587578860483d6ededf88e9c04a926644
Since LMKD introduced aggressive kill for cached apps, we can change the
swap_free_low_percentage back to 10.
Bug: 300660611
Change-Id: Ib570d579e0d3addee242b226aed72a3a138a0f78
Signed-off-by: Minchan Kim <minchan@google.com>
am skip reason: Merged-In Ib4ec351fd5f2d59d161578440e8c0d36f8b68a6f with SHA-1 c6b5b5990a is already in history
Original change: https://android-review.googlesource.com/c/device/google/gs101/+/2774918
Change-Id: I6fbdc86dd4d90a5c09760cecd45473caa8ee3359
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
am skip reason: Merged-In Ib4ec351fd5f2d59d161578440e8c0d36f8b68a6f with SHA-1 c6b5b5990a is already in history
Original change: https://android-review.googlesource.com/c/device/google/gs101/+/2774918
Change-Id: Id486c53997b232c2b02d18d1c7a6d773f1319110
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
am skip reason: Merged-In Ib4ec351fd5f2d59d161578440e8c0d36f8b68a6f with SHA-1 c6b5b5990a is already in history
Original change: https://android-review.googlesource.com/c/device/google/gs101/+/2774918
Change-Id: I8f0576cf46996c9ff8d02cf69b0c05345e26de64
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
am skip reason: Merged-In Ib4ec351fd5f2d59d161578440e8c0d36f8b68a6f with SHA-1 c6b5b5990a is already in history
Original change: https://android-review.googlesource.com/c/device/google/gs101/+/2774918
Change-Id: I1b75b5a02f0f999fd15d601fa4932b0c9f50ca8f
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
am skip reason: Merged-In Ib4ec351fd5f2d59d161578440e8c0d36f8b68a6f with SHA-1 c6b5b5990a is already in history
Original change: https://android-review.googlesource.com/c/device/google/gs101/+/2774918
Change-Id: I51a81140c8882e60540742f189eb9edabd51cc62
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
Upload metrics for the last data session that just ends upon
data role changes. The change is purely metric collection and
does not change any business logic.
This is a direct CP from ag/24816727
Bug: 297224564
Test: Trigger metric upload for both host and device mode and
verify it by statsd_testdrive
Change-Id: I823ae8712b7914cfc7f6c6379acb3749d13c0974
(cherry picked from commit ccb35c81ff0bbfb013136bae7a572280b196bd1a)
