Age | Commit message (Collapse) | Author |
|
Bug: 253366496
Test: wifi_diagnostic binary is available
Change-Id: I24c530df17def7dc4e6fa2922fa0e51d27436cde
|
|
This change landed in ag/16941691 but was rolled back due to
issues with stripping of CustomScrollView and PackageManager
shell command support. That issue has since been fixed.
Original change description:
Opt in to whole-program Java optimizations via R8 for Pixel devices.
This can be explicitly disabled during builds via
`SYSTEM_OPTIMIZE_JAVA=false m`.
Note that this change only enables code shrinking for system_server,
and should not impact stack traces. Additional R8 optimizations
will be enabled after broader improvements to retracing infrastructure.
See go/aperf-system-r8-faq for additional details and guidance. Also
note that R8 shrinking optimizations are implicitly disabled in ENG builds.
Enabling for non-Pixel devices will proceed in stages as we flesh
out infrastructure and validate with test populations.
Results: services.jar (20MB -> 17MB)
Bug: 210510433
Test: SYSTEM_OPTIMIZE_JAVA=true + atest
CtsInstalledLoadingProgressHostTests
CtsAutoFillServiceTestCases
CtsAppSecurityHostTestCases
CtsAppTestCases
Change-Id: I7f64819a8d23a39e7afbb1a210c229f223855243
|
|
Change-Id: I8ef86ddd144057ec4e20b40a24b38b47771738cb
DroidMonitor: Potential culprit for Bug X - verifying through ABTD before revert submission. This is part of the standard investigation process, and does not mean your CL will be reverted.
|
|
Opt in to whole-program Java optimizations via R8 for Pixel devices.
This can be explicitly disabled during builds via
`SYSTEM_OPTIMIZE_JAVA=false m`.
Note that this change only enables code shrinking for system_server,
and should not impact stack traces. Additional R8 optimizations
will be enabled after broader improvements to retracing infrastructure.
See go/aperf-system-r8-faq for additional details and guidance. Also
note that R8 shrinking optimizations are implicitly disabled in ENG builds.
Enabling for non-Pixel devices will proceed in stages as we flesh
out infrastructure and validate with test populations.
Results: services.jar (20MB -> 17MB)
Bug: 210510433
Test: m + atest FrameworksServicesTests + manual testing on Raven
Change-Id: I13c0674105aa2cab7722f52344486e86e3bde26b
|
|
This reverts commit 3582713a62a95f02b5c4d5ac32aeaf63ed28be20.
Reason for revert: R8 outlining fix landed in aosp/1958830,
related issues no longer observed.
Bug: 216055443, 203472868
Change-Id: I3fcd540be8a63f4898a607ec1474447f37a0da59
Test: atest SystemUITests + manual testing of various CUJs
|
|
|
|
This reverts commit 0e10670900215ab1e45621a4b15cafa4c59ff8c8.
Reason for revert: Droidfood blocking bug: 216055443
Change-Id: I24b5a042b3c4476cb0c6ab0039f34446e2b38f2b
|
|
ec5be98830 am: 2c680e838c am: cedd06f3f5
Original change: https://android-review.googlesource.com/c/platform/hardware/google/pixel/+/1954384
Change-Id: Id6495deae3f948210018bc24100e4d27b48015b6
|
|
Opt in to whole-program Java optimizations via R8 for Pixel devices.
This can be explicitly disabled during builds via
`SYSTEMUI_OPTIMIZE_JAVA=false m`.
Note that this change does introduce changes to stack traces that
may require retracing for fully accurate debugging and diagonstics.
See go/aperf-system-r8-faq for additional details and guidance. Also
note that optimizations are implicitly disabled in ENG builds.
Enabling for non-Pixel devices will proceed in stages as we flesh
out infrastructure and validate with test populations.
Results:
* SystemUIGoogle.apk (40MB -> 35MB)
* SystemUIGoogle.odex (32MB -> 25MB)
Test: m + atest SystemUITests + presubmit + manual testing on Raven
Bug: 203472868
Change-Id: I67ff2c06885b21164a3034e9922163337e8787f3
|
|
Bug: 210056469
Test: build on bramble
Change-Id: Ib4b6e70e5b4f2eb04f64c53c47a0e9c1c0c37aa0
|
|
Bug: 213117526
Test: wifi_perf_diag is workable
Change-Id: I051370e91ab9058b19e074a75f55b1776d5f2098
|
|
Revert submission 16091844-googlebattery-mk
Bug: 204278079
Reason for revert: b/204278079
Reverted Changes:
Idea994a54:move turbo settings from vendor to device folder
If55f161dd:move turbo settings from vendor to device folder
Ibc503993c:Avoid definition not found error in AOSP targets
I9eba9cdc5:Avoid definition not found error in AOSP targets
I1d22da983:move turbo settings from vendor to device folder
I789230c41:Avoid definition not found error in AOSP targets
Ie4ff6a302:move turbo settings from vendor to device folder
Change-Id: Ib693f725d506c7e3717f8b6234e4ff206d6d92c2
|
|
Bug: 201230944
Test: build pass
Change-Id: Ie4ff6a302d68c5220ec428dd77acc470f9034386
|
|
Bug: 196916111
Test: build ROM with wifi_sniffer started
Change-Id: I8d16b59c480b44a296bca3504fd7f15021d43f54
|
|
Bug: 191925901
Test: Build
Signed-off-by: Wei Wang <wvw@google.com>
Change-Id: I108f77de648c7c29ba6f2331592714b208853a2d
|
|
Today, the dark boot follows the Dark Theme mode in Settings. Now
the UI team decide to always use dark boot after the device is
provisioned. So users will see fewer disturbances when a scheduled
update is taken at night.
Light boot is still used on the first boot after a factory reset.
Bug: 181339788
Test: flash a Pixel -> boot -> dark theme is set;
boot again -> observe dark boot
Change-Id: I5c0e675fb31e844fe3830d78bb2378ebc17e49e4
|
|
Bug: 176859817
Signed-off-by: Minchan Kim <minchan@google.com>
Change-Id: Iab80d2f06ca093c32f24c1a4b5430d14835fff28
|
|
Original change: https://android-review.googlesource.com/c/platform/hardware/google/pixel/+/1511728
Change-Id: I2b52959420ed36ca7b21dcda21f9c7cfb66abb88
|
|
The property is set to inform kernel to do a warm_reset on the next
reboot. This is useful to persist the logs to debug device boot
failures. More details in http://go/rvc-ota-persist-logs.
The property is read by vendor_init. And according to its value,
vendor_init writes a particular sysfs file to schedule a warm reset
on the following reboot.
The vendor init also schedules the warm reset if the current slot
hasn't
been marked as successful during boottime, i.e.
ro.boot.slot_successful=no
Move definition of relevant rc scripts to pixel common script
Bug: 143489994
Bug: 173267277
Test: adb shell grep "ota.warm_reset" -r /vendor
Change-Id: I1f475403430149a0242e8ac098f1ce0155cad054
|
|
Revert^2 "Organize citadel's setting"
0ed91028402fc1e0bdc179cbd01f2745cc92fa7c
Change-Id: Ia034015051d7e998c0df6906d3c021b7f01f6e11
|
|
Revert "Organize citadel's setting"
Revert "Organize citadel's setting and fastboot lib"
Revert "Organize citadel's setting"
Revert "Organize citadel's setting"
Revert "Organize citadel's setting"
Revert "Organize citadel's setting and fastboot lib"
Revert "iOrganize citadel's setting"
Revert submission 12945656-ORGANIZE_CITADEL_LIB_AND_FASTBOOTD
Reason for revert: Device boot tests failing.
Reverted Changes:
Ieb1cf8cb6:Organize citadel's setting
I8c965ff88:Organize citadel's setting and fastboot lib
Ia472d7812:Organize citadel's setting
Id922447dd:iOrganize citadel's setting
I4e05236c0:Organize citadel's setting
I8fea8a68c:Organize citadel's setting and fastboot lib
I63c732ead:fastbootd: allow fastbootd to access citadel
I379e9a717:fastboot: Include fastbootd and lib in pixel-commo...
I46a30449a:fastboot: Use doOemSpecificErase() to erase Titan ...
I6cded2df5:Organize citadel's setting and fastboot lib
I388675440:Organize citadel's setting and fastboot lib
Iec10ebc27:Organize citadel's setting
I51d6db226:Organize citadel's setting
I44c4a232e:Organize citadel's setting
I8ef83954e:Organize citadel's setting
I72ae3f968:Organize citadel's setting
Ia3dbac300:Organize citadel's setting
I2c9ff026a:Organize citadel's setting
I50a6764e1:Organize citadel's setting
Bug: 172063886
Change-Id: I686a7165620deed08668e6e20fbbb74ec5f26f34
|
|
Bug: 169548154
Change-Id: I379e9a7179ccc0e417508fbf94c974cfeff9ce28
|
|
Bug: 157908868
Test: build and capture trace.
Change-Id: Ic387f2b0b492c47dd97a41d8a9be05c5e2a6938f
|
|
Its permission is related to the module it loads,
and they vary from device to device
Bug: 168440095
Test: boot with no SELinux error log
Change-Id: I0a9438ff776cec91aaf565e3c19d274520a13a51
|
|
Bug: 168440095
Test: boot to home with persist and firmware mounted on sunfish, coral
Change-Id: I6c58fd69bc9a09f365936fc8a5e242744e464620
|
|
Bug: 160434722
Change-Id: I770fe7feee467a9be843938ede2b6124b44a3ec1
|
|
If the module list is specified by a *, or empty, then use contents of
modules.load as argument to modprobe. Chose this route over enhancing
the modprobe tool to accept an argument of * natively. Specifically
also support the -b (blacklist) option to limit which modules to load.
Signed-off-by: Mark Salyzyn <salyzyn@google.com>
Bug: 151950334
Test: second stage modules load with * argument in config
Merged-In: Id3b5c43644e465f1327b1a56d11609bab6aad228
Change-Id: Id3b5c43644e465f1327b1a56d11609bab6aad228
|
|
If the module list is specified by a *, or empty, then use contents of
modules.load as argument to modprobe. Chose this route over enhancing
the modprobe tool to accept an argument of * natively. Specifically
also support the -b (blacklist) option to limit which modules to load.
Signed-off-by: Mark Salyzyn <salyzyn@google.com>
Bug: 151950334
Test: second stage modules load with * argument in config
Change-Id: Id3b5c43644e465f1327b1a56d11609bab6aad228
|
|
Test: Manual
Change-Id: If08e136ca0d1e4f2aca00f487eafce39ab86ffec
Signed-off-by: Harpreet \"Eli\" Sangha <eliptus@google.com>
(cherry picked from commit 85d9b8facd40b14810de67081a9ed0aa39462c44)
|
|
Bug: 150836896
Change-Id: I5366349dbf67394c7dea0caf5706359d97187dfd
|
|
Bug: 143338171
Test: boot to home with no avc error
Change-Id: I86b6137ceff94307facbe7f37ecce62dfc59eae6
|
|
Bug: 130377452
Test: boot to home with persist and firmware images mounted
Change-Id: I70869334b45d1271e4f2b1fc0fa59f69e87e4cb3
|