Age | Commit message (Collapse) | Author |
|
The stats are calculated using quota APIs for all the apps.
This is going wrong for the app owning external storage, as it includes
the external storage files also. The reason for that is the uid for the
external storage files and the app owning the external storage is the
same. Calculating the size manually avoids the problem.
Bug: 195804288
Test: atest StorageHostTest
Test: atest installd_service_test.cpp
Change-Id: I183c6997375b94dc02562bede03e3a15036efb6e
Ignore-AOSP-First: already submitted in AOSP
Merged-In: I183c6997375b94dc02562bede03e3a15036efb6e
|
|
Increase core count in atrace.rc to support future devices with
more cores
Bug: b/203651019
Test: Build
Change-Id: I4c7b0ba6a4883cc21f45428368b60759c54ef985
Merged-In: I4c7b0ba6a4883cc21f45428368b60759c54ef985
(cherry picked from commit 2895eeb632400c708ae0a01596ff2eda9c3f6de2)
|
|
am: 7089fbbfe5
Original change: https://googleplex-android-review.googlesource.com/c/platform/frameworks/native/+/15404710
Change-Id: I5d3b808662dfb487389c70de0efd1125814ced67
|
|
Original change: https://googleplex-android-review.googlesource.com/c/platform/frameworks/native/+/15345066
Change-Id: I26aebce0f7d2d1ffd4295cdf3540fe473e927560
|
|
sc-dev am: 5eaa7c3136
Original change: https://googleplex-android-review.googlesource.com/c/platform/frameworks/native/+/15150900
Change-Id: I8578a717172c8245da2c8352cbec14f4b9729628
|
|
Only create mm_event tracing instance if
persist.mm_events.enabled=true. This saves ~5.5MB on low
memory devices that don't enable mm_events. The memory saved is
slab memory that would be allocated for the ftrace instance's
inode/dentry objects.
Set the per-CPU trace buffer sizes to 1KB by default to minimize
trace buffer memory usage if perfetto isn't started.
Also disable tracing by default, traced_probes will enable
as needed.
Bug: 194156702
Test: boot; ls /sys/kernel/tracing/instances -> No mm_events
Test: setprop persist.mm_events.enabled true; boot;
ls /sys/kernel/tracing/instances -> mm_events
Change-Id: I89d7e5e1cd0d32b5612bc419b1a1c4b8c3c8ade6
|
|
|
|
Revert "Adding system property tracing"
Revert submission 1403568-sysprop_trace
Reason for revert: makes property get/set non-reentrant
Reverted Changes:
I6f85f3f52:Add systrace tag for system property
Id2b93acb2:Adding system property tracing
Id78992d23:Add systrace tag for system property
I1ba9fc7bd:Add systrace tag for system property
Bug: 193050299
Change-Id: I4d8c9e191e28cc99abc4f80600405bfc1b7e48b6
Merged-In: I4d8c9e191e28cc99abc4f80600405bfc1b7e48b6
Test: build and boot a device
(cherry picked from commit dc5577c75e0c68de6069e3f14c887edea051ba97)
|
|
- Add a layer state to indicate that this layer and its children
in the hierarchy are trusted. This can only be set by callers
holding ACCESS_SURFACE_FLINGER, and will be used for the PIP
task layer to indicate that activities in PIP are trusted (as
they are controlled only by the user and SystemUI)
Bug: 191529039
Test: TBD
Change-Id: Id92ccb087bd0d8dbaeeef3ba50b67fe015e53db8
|
|
Original change: https://googleplex-android-review.googlesource.com/c/platform/frameworks/native/+/15259876
Change-Id: I98458b5d241dfd1bb07c739c159cebfae121816b
|
|
|
|
To prevent deadlocks.
Bug: 188393100
Test: N/A
Change-Id: Icf7a04c8f9d244b7bdd94b2111f41ce489d39302
Merged-In: Icf7a04c8f9d244b7bdd94b2111f41ce489d39302
|
|
into sc-dev am: b0eecadde9
Original change: https://googleplex-android-review.googlesource.com/c/platform/frameworks/native/+/15226977
Change-Id: Id84d3cce68819a03120f161a0683f36076b70faf
|
|
into sc-dev
|
|
Original change: https://googleplex-android-review.googlesource.com/c/platform/frameworks/native/+/15243093
Change-Id: I195194ef9734a6e5ad3ab4be555e5254887e7cf4
|
|
|
|
Since installation time is also critical and sometime we want a finer
control on its behavior for vendor. Instead of setting dex2oat to
background group, add a new task profile (by default same as background
group).
Test: Boot
Bug: 188947181
Signed-off-by: Wei Wang <wvw@google.com>
Change-Id: I37a36050a338f9eba8d605a00a32b99a4a590bac
|
|
Increases the meminfo dumpsys timeout from 30s to 60s, since
30s is sometimes not enough.
Test: Check that longer timeout is used in writeDump call
Bug: 191615258
Change-Id: Ic270a81f3dde1329881023d533ffbff43a82127c
Merged-In: Ic270a81f3dde1329881023d533ffbff43a82127c
(cherry picked from commit fac7e2b57ba6b9d461ed779a7fe6a620335d16c8)
|
|
Original change: https://googleplex-android-review.googlesource.com/c/platform/frameworks/native/+/15215411
Change-Id: I24d86fad37d63f51ea1175998a50e6806221122f
|
|
(cherry picked from commit c47757ca9c91266e7ec0c23207379ef2fff8716c)
Bug: 192871419
Test: atest installd_dexopt_test
Ignore-AOSP-First: cherry pick of https://r.android.com/1757092
Merged-In: I7aeef7465f3617393ede43b24b142d7149942b3d
Change-Id: I3f93f2c1079fe6a44326f60b29a088e4eb6bac97
|
|
sc-dev am: 9345fd4c67
Original change: https://googleplex-android-review.googlesource.com/c/platform/frameworks/native/+/15175854
Change-Id: If8a94428e1997d3f24cf6fce847358bc40aea5aa
|
|
(cherry picked from commit 2b12e7c84a89f71e3869d8f0186d1946b8703081)
Bug: 192049377
Test: manual
Ignore-AOSP-First: cherry pick of https://r.android.com/1753962
Merged-In: I10094499b6141e134cb873d6c6590a1731e5910b
Change-Id: I4ea0b562cdd90b454dc352cc36b648ae5ef1d9fe
|
|
Original change: https://googleplex-android-review.googlesource.com/c/platform/frameworks/native/+/15163080
Change-Id: Idf821b73b15cc8f376ea3bc5976a38f57d0019f3
|
|
Bug: 192493418
Bug: 192512069
Test: adb bugreport
Change-Id: Ia95d8b14062e65248a0f4d97fe70b5d1010a9299
|
|
Original change: https://googleplex-android-review.googlesource.com/c/platform/frameworks/native/+/15110199
Change-Id: I597656bafd7e76bf62b86d09c779a6d0ed30eb39
|
|
This reverts commit 9c4f39e9f3d591c302b059a275f16284770e07a7.
Fixes: 190711180
Test: build and boot
Change-Id: I779b1500f7d53bd02e3c7d8adbc0f6364270c9be
|
|
sc-dev am: dd3a5b7e55
Original change: https://googleplex-android-review.googlesource.com/c/platform/frameworks/native/+/15025721
Change-Id: Iba59fe7ad1b94aa01ccab4744d1f28e835636dc8
|
|
Original change: https://googleplex-android-review.googlesource.com/c/platform/frameworks/native/+/14982071
Change-Id: I8ff34ae7659e4aef80ec4f8828c4a5b28f7ac7c3
|
|
Original change: https://googleplex-android-review.googlesource.com/c/platform/frameworks/native/+/14982070
Change-Id: I4abe79cc5121a8edcd72d541139f30ef852d6eca
|
|
It takes longer but reduces the memory footprint.
Test: adb install
Bug: 190277710
Merged-In: I42d24cfb2e965e440d7595da4c2e4ef7e97c0f23
Change-Id: I42d24cfb2e965e440d7595da4c2e4ef7e97c0f23
(cherry picked from commit 380fff71fd7c8a433a6ce74e35c9bc1bc2ade1d0)
|
|
This will help quantify the number of bytes we free for
telemetry purposes.
Test: installd_tests
Bug: 187458876
Change-Id: I29f7974977a58decf784bda443715f8b11fdf7c1
(cherry picked from commit 0f3bebad25baf74fec2348b270514f7bf63b78b7)
|
|
This allows us to fine tune the optimization strategy when
profiles are empty.
Test: atest installd_dexopt_test
Bug: 188655918
Change-Id: Iaf782eedd92dfddd522feaecb446c85f3ae1c51e
(cherry picked from commit e90de86f92669fc5557891fdfd1d6e6c2ef240fc)
|
|
sc-dev am: db5dc52be5
Original change: https://googleplex-android-review.googlesource.com/c/platform/frameworks/native/+/14907970
Change-Id: I64079570ba9cc2a51797663958a7280ffe8e0305
|
|
|
|
Original change: https://googleplex-android-review.googlesource.com/c/platform/frameworks/native/+/14910832
Change-Id: Iba8f0c85578f05802b3898e04d60e93a1296f905
|
|
This is a temporary fix while we determine a better long term fix.
This will recursively fix up the selinux context of
/data/user/0/com.google.android.gsf.
Bug: 188141923
Bug: 190567190
Test: 1. adb root
2. adb shell cp /system/build.prop /user/data/0/com.google.android.gsf
3. adb reboot
4. adb root; adb shell ls -laZ /user/data/0/com.google.android.gsf
5. verify that installd has fixed up incorrect labels.
Change-Id: Ieadd64b61162f2fa802add2a8e54d2072ad2fd48
|
|
The reference profile is now used to determined whether or not
ART should trigger a profile save earlier.
Test: manual
adb shell stop;
adb shell setprop dalvik.vm.ps-min-first-save-ms 300;
adb shell setprop dalvik.vm.extra-opts -verbose:profiler;
adb shell start;
Bug: 185979271
Merged-In: I49002965e27e41b2beb753335962edbd93c54146
Change-Id: I49002965e27e41b2beb753335962edbd93c54146
(cherry picked from commit 31c68e7966b5fc725b0829bddf665fba650688dc)
|
|
Right now, multiple display devices can share a layerstack.
This means that when constructing InputWindowInfo, its
impossible to know which display transform matches the
display viewport that inputflinger dispatches against. To
remedy this, have displaymanager inform surfaceflinger
which displays "receiveInput" using the same logic that
controls which display viewport it sends to inputflinger.
Bug: 179274888
Test: atest SetDisplayStateLockedTest
Change-Id: If0ffb1b5405f7e7dcdf8ea2f12c109d661a540fe
|
|
The dumpsys design in connectivity was updated due to mainline
modularization work. Module can only register with default
priority which is NORMAL. RunDumpSysHigh will not be able to
dump the priority high information in ConnectivityService.
Thus, dump HIGH connectivity specifically to align with legacy
behavior.
Bug: 188387185
Test: adb bugreport
Change-Id: I0b712143527b866d2d749e37aa3d7f0f85317b17
Merged-In: I0b712143527b866d2d749e37aa3d7f0f85317b17
|
|
Original change: https://android-review.googlesource.com/c/platform/frameworks/native/+/1707026
Change-Id: I453da617406dc74068f7cba91b6b3d6df1416c25
|
|
|
|
Original change: https://android-review.googlesource.com/c/platform/frameworks/native/+/1706700
Change-Id: I07ffadfe3e519c2e1663f1719c21e03d8287bab0
|
|
Test: Builds
Bug: 188024968
Change-Id: I0709a20f4a8363ec918d6aebc37e86c359fa5023
|
|
Bug: 186864416
Test: Builds
Change-Id: I104daa7cb8d655f53a0ae5c4d311a00376ac7207
|
|
am: 2f18fdbdf5 am: af2b7f3856
Original change: https://android-review.googlesource.com/c/platform/frameworks/native/+/1704014
Change-Id: Idbae3e433c1b86cc81cec9bca4f2b0f76621413b
|
|
unavailable" into sc-dev
|
|
VCN is a new networking feature for carriers in Android S, so we need to
include this info in the BRs that carriers can collect.
vcn_management is already dumped in full BRs when all running services
are dumped.
Bug: 187870480
Test: adb shell am bug-report --telephony (inspect content)
Change-Id: I817b75b4be9b398ca605e033e129acef1c1420ea
|
|
BUG: 185825114
Test: Confirm that the bugreport is .zip when the user consent is unavailable
Change-Id: I6fc28aa3e040152ed16a2807afcef3516ebbc210
|
|
ecc7eb519f
Original change: https://android-review.googlesource.com/c/platform/frameworks/native/+/1697247
Change-Id: I4efb85f13e6c16501d2394f089f8e8a4d7ab6a6c
|
|
Print .modinfo of each kernel module in section "MODULES INFO". Size of
modinfo for a module is usually 200 ~ 500 bytes. The number of kernel
modules of product with GKI enabled can be 200+, so this could add
extra 100 KB to bugreport in such case.
Bug: 186171455
Test: Take bugreport and check outputs
Change-Id: Ie3d21bc27f9310b741c955f95243936d52d95f1c
|