When the maximum number of retries that has been exceeded is not for the primary profile of the user, wipe only the profile that set that policy (e.g. the managed profile) rather than the entire user. At the moment the whole device is wiped if the max number of incorrect passwords for a managed profile is reached, as the password is shared with the USER_OWNER.
Bug: 14453697
Change-Id: I5746de104133c0ea0a51d75b9c92e1516d365d8c
Use 400dp as the visual width of the shade across all devices
and orientations, except small device portrait.
Since the width is now dynamic across orientations, update the
necessary views in SystemUI on rotate.
Remove obsolete styles + resources.
Set max QS columns to 3 on all devices, due to the newer shade
width.
Bug:16825515
Change-Id: Iff171549a79bc318a4d585a2d9ea2af9bc686922
This change introduces a class that handles launching the secure camera even
when other apps may be using the camera hardware. It does this by sending out
a broadcast telling apps to stop using the camera as soon as the user begins to
swipe to use the secure camera. It then waits until either the camera is
available or a timeout period has expired before it fires off the intent to
start the secure camera.
Secure camera apps can indicate (via their meta-data) that they will instead
handle the responsibility of waiting for the camera to be available. In this
case, the new class still handles sending out the broadcast telling other apps
to close the camera, but it fires off the intent to start the secure camera
before the camera hardware is available. This is optimal because some of the
time spent closing the camera can happen in parallel with the time spent
starting the secure camera app. Since we can't depend on third-party apps to
wait for camera availability, the default is for us to wait for the camera to
be available before firing off the intent. However, our first party app is
able to take the optimized approach.
Change-Id: I1eaed94875e8f50018cffab25aa1e9b21d85f25b
Since all service-internal checks use stream alias, and the alias
for NOTIFICATION is RING, even on tablets.
This is a followup to ag/506532.
Ensure that #getMasterStreamType always follows the stream_system
alias, and update the system alias for tablets per the new policy.
Update the associate javadoc comment in AudioManager to make this
clear.
Note: there is now no difference in the alias maps between phones
and tablets.
Also fix a condition affected by this in VolumePanel.
Bug:16626879
Change-Id: I2700a48d2a3e7703607f771a1ab7f325596fd789
This reverts commit d9267cae958b572b715d22a4905b18749a369c9f.
Too much performance regression - need to figure out something else.
Change-Id: I2d399add74402e1c036235ec095a053a6d5b828e
Pull out 30-day feature timeout code into a separate helper, use
in both ColorInversionTile and HotspotTile.
Expose an intent to force a reset of the timeout.
Change-Id: Ic0b89913fd5cec4e1df3cb0d5a548f052a60550f
When notification alerts are disabled also turn off heads up. This
will fall back to the old behavior, which can allow the fullscreen
intent to be triggered instead.
Bug: 14157742
Change-Id: I4b6e3d9383894b1674d600c374ff8968ca53513e
