Owners source of truth is now in AOSP but has merge conflicts with
internal so submitting a separate CL here (AOSP change at
aosp/813915).
Test: N/A
Change-Id: I0e96914bb339874a30c80776596f2d84e508df85
Fix translateable -> translatable in .xml files. The attribute
must be correctly named to influence behavior.
Bug: 119884572
Bug: 119941330
Test: build only
Change-Id: I59b17e914f90cab495c1e7be3c14b0423da73b43
zygote is excluded from NativeProcessMemoryState to investigate whether
the unexpected values reported in the atom are due to its forking.
Test: atest UidAtomTests#testNativeProcessMemoryState
Change-Id: I9e29955d9931ac19c49d0ee18a5245a40034486f
Change 1/2. Change 2/2 will setup the class loader namespace for
shared libraries.
This change sets up shared libraries class loaders for applications
and for dexopt.
bug: 111174995
Test: DexoptUtilsTest, device boots
Change-Id: Ie9a2b4eaa85cda59951703433f7a2d03bc12095d
Let each display have one status bar and one navigation bar. This is
so on each display, status bar and navigation bar can be laid out with
apps and produce proper insets.
Bug: 117474929
Test: atest com.android.server.wm
Test: Watch YouTube video in fullscreen mode, and see if status bar
and navigation will be hidden as expected. Swipe on the edge
of screen and see if status bar and navigation bar are both
shown as expected.
Change-Id: I1550659b7cd1dd1676bf04483c5b68376ef42905
Some time zone related libcore classes are moving from
libcore.util to libcore.timezone.
Bug: 119026403
Test: build only
Exempt-From-Owner-Approval: Trivial import change
Change-Id: Ie90c219799cbf9601a22a2d972c09e3d94fc0c43
add carrierId and preciseCarrierId in CarrierIdentifier
which will be passed to carrier service to decide which carrier
info to look up
Bug: 110559381
Change-Id: I1b4a44dd32148ebdf5aa437c5938cb89656c27c2
Merged-in: I1b4a44dd32148ebdf5aa437c5938cb89656c27c2
This is needed so the PermissionController can differentiate between
multiple versions of the same app.
Bug: 119811056
Test: Call API.
Change-Id: I19150e1c8e5f204a846500cfe0021da742235213
The size in /proc/vmallocinfo actually represents the size of
the virtual region and not the size of memory allocated for the same.
So, we have been over counting vmalloc memory usage in most cases
leading into negative "Lost RAM".
Moreover, as of kernel 4.14, binder allocations that were ignored before
are now counted as vmalloc allocations since binder started using the
'vmalloc' flag instead of 'ioremap' flag for its vm area allocations.
See: 86eda3864a
.. This makes the problem even worse for devices that are running
kernel 4.14 and beyond.
Fix that by looking specifically for "pages=" in each line of
/proc/vmallocinfo to get the number of physical pages associated with
the particular allocation.
Bug: 119639955
Test: 'dumpsys meminfo' before and after on cuttlefish running 4.14 kernel.
Result:
Lost RAM (before) : -151,462K
Lost RAM (after) : -5,312K
Change-Id: I3d677572613392383ee8ea0968bde0e0913c42cf
Signed-off-by: Sandeep Patil <sspatil@google.com>
