Basically push them through downloads.ui TrampolineActivity
to get origin url and referer and other security bits
added before handing off to package manager.
Bug: 24676446
Change-Id: Id40787ada6ace424c4e5e4bfeedc0a8005b7a734
This reverts commit 24e46045956da911b385be33cff473bdacebf780.
Un-hiding this for continued development in nyc-dev.
Based on conversations between those at higher paygrades, we'll either leave this visible or re-hide prior to next dev release.
Change-Id: I235eb0f593daa7b34ea10ed4c9df4eaa6c68078c
Propagate setVisible calls to current drawable. Take window visibility
into account when determining drawable visibility.
Bug 27461595
Change-Id: Ia1de1d1686f26c2cf27630c5bde70f23c2c332bd
Do not merge because the resource implementation has changed in N and
the change is no longer valid there.
This is a very hacky fix to make layoutlib work with the latest support
lib. Inject a couple of fields in android.content.res.Resources to
allow using most of the earlier code as is.
Bug: 27403642
Bug: http://b.android.com/201934
Change-Id: I186cad32b1b4de64164fbad937d989e0110c6976
Also includes a regenerated test-current.txt.
bug: 27426688
(cherry picked from commit 7d18ce744fff219ab60470ec095d585b854b91e1)
Change-Id: I754803d51d365ac1fe26c638b12efb88d23b35c6
Includes generated changes for test-current.txt.
bug: 27426688
(cherry picked from commit de33c660df4a6ff8a138e3033c9e1d446bd6b570)
Change-Id: Idd323fe7458a2b124aae0009b4de83039e2ade21
The main purpose is to fix the security flaw that
user can force isDeviceOwnerProvisioningAllowed to return true
by setting the device_provisioned without factory reset
Check UserSetupComplete instead, as it's cached by DPMS if it's ever set to true
Refactor common code of isDeviceOwnerProvisioningAllowed and enforceCanSetDeviceOwnerLocked
The functionality of enforceCanSetDeviceOwnerLocked should be exactly the same.
DPM Unit Test all pass
Bug:27403225
Change-Id: I32dae8e222e01e08664abb313ead3a92d4186658
It is possible for an activity to be in the stopped state without
setting it's visiblility to false in window manager.
For example, the home acitivty behind the lock screen. Since the
lock screen isn't an activity it doesn't affect the visiblity set
of the home activity, so AM doesn't tell WM to hide the app token.
However, AM uses another channel to detect that the device is locked
and moves the activity into stopped state. WM on the other hand also
detects that the device is locked and hides the window surfaces of
all windows behind the lock screen. So, at this point AM has also
told WM that the activity is stopped. Once you unlock the screen
AM resumes the activity but doesn't report any visiblility changes to WM
since it's internal state didn't change. So, if you go from the home
activity to another app the home activity window will be destroyed
before the activity is stopped because mAppStopped is set to true.
We now set mAppStopped to false when the activity is resumed.
Bug: 27286867
Change-Id: Ic75456d30abd582fa44f932f5aeeb449950157ee
Disable multi tasking support by default for all operators.
Enable based on MCC/MNC for required oeprators.
Bug: 27484483
Change-Id: Ib321747885435c110360370eb243eee35762dfe3
Initial implementation of getRestrictBackgroundStatus() was just
handling the whitelist status of apps when data saver is turned on, but
when an app is blacklisted, it should return
RESTRICT_BACKGROUND_STATUS_ENABLED regardless of the data saver status.
BUG: 27432317
Change-Id: I5a027d8b7d17a13075510ff8f29d41eaa5a6beb8
