Get the canonical identity and metadata about the package from the
Package Manager at time of usage rather than rely on the caller to
have gotten things right, even when the caller has the system uid.
Bug 28795098
Change-Id: I215786bc894dedf7ca28e9c80cefabd0e40ca877
Get the canonical identity and metadata about the package from the
Package Manager at time of usage rather than rely on the caller to
have gotten things right, even when the caller has the system uid.
Bug 28795098
Change-Id: I62710b15bb601fdfedd68e32349168c10725eb45
This reverts commit 21893824c1.
Original commit revealed issue b/29342752 when launch logic was applied
to incorrect stack while moving to PiP mode.
Bug: 29342752
Bug: 29237751
Change-Id: I88d75399eb4b9daf4de87a9a560eb0df0b515173
Because it's not guaranteed to use any builder at all,
there is another case where the SmallIcon could remain null.
We are now checking this lazily instead of ahead of time.
Change-Id: I7a0feff6911b2bce6707427259d3423131a26e32
Fixes: 29255365
* define a update hash such that com.android.cts.priv.ctsshim can't
be updated
* create a new APK to verify that <restrict-update> works as expected
Bug: 29311441
Change-Id: I61f3ae3dbd9c79b2dcdfbc30757af0f9a669fce6
This method is called by AM with the lock held, so can't take the
DPMS lock.
It still takes a different lock, but we don't call into the external
world while holding this lock, so this is fine.
Bug 29242568
Change-Id: Idbecdd7d97385ca66c693903443471fdbae833e6
Adding details on which notification message to listen for
when developing apps that need to interact with direct boot mode.
Note: This is a doc fix for the N direct boot feature docs, but
not specific to any preview release.
Bug: 28729775
Change-Id: If6b239e7aa92bced735cfa1e72d8891d193a420c
Use JobScheduler's minimum period in SyncManager.
Syncs will respect JobScheduler's min period anyway,
this change ensures that dumpsys of both services
show the same period.
Bug: 29253834
Change-Id: I0cd7f85da56af967963573a048c3a71436ed9c5b
It's with the rest of the logic now and allows checking whether the
lockdown state matches, too, which led to a lot of misunderstandings.
Fix: 29199431
Change-Id: I94a2c38c4837f9c33b5b9c2becb52eeb7e2a2534
Improves the transition of the action bar between
the collapsed and expanded states.
Bug: 28935363
Change-Id: I89efe95aa045d04bab4208a001f82cb69b38fce5
For the setClipToScreen case we need constraint to
the available display area, but not to the parent window.
If we don't pass FLAG_LAYOUT_NO_LIMITS, we will be constrained
to the parent window. However when we do pass it, we will
not be constrained to the system insets. So, we can pass
FLAG_LAYOUT_NO_LIMITS and constrain ourselves to the insets
via getWindowVisibleDisplayFrame. We also need to avoid
calling setWidth/Height with these resolved values
so we can preserve the indeterminate values in case
layout changes (e.g. rotation).
Bug: 29166136
Change-Id: I4c7c6204e6bc1cdcf4ad86f7e99e3511d4312ae4
In the Keyboard Shortcuts Helper section, changed the command to read 'Meta + /' and added information related to Meta key.
Bug: 28240770
Change-Id: Id7317999ea9acb4aa904d440af63b7d02c39184f
Verified the checksums against the image files before uploading
them to cloud share. For OTA versions, only the SHA256 checksums were
provided; I verified those checksums against the original image files,
then generated the MD5 and SHA1 checksums myself.
Once all files were staged to cloudshare, I re-downloaded them and
verified them against the checksums I'd added to the preview HTML
page; everything checks out.
See first comment for doc stage location.
bug: 28981896
Change-Id: I10165d402c4f7f07cad267f460b289a7bbf6b858
