If the app requests its activity to be finished allow it to be finished
immediately if the activity is already paused.
Also, don't schedule stop for an activity that was already finished in
ActivityStack.stopActivityLocked().
Bug: 22170595
Bug: 22397812
Change-Id: If349f7d3070a1fd2c0688fda7381b42f625ed9e4
Raised the protection level of WRITE_SETTINGS permission to appop and also
allowed backwards compatibility with pre23 flag. Also made sure that this
permission is not added as RuntimePermission in DefaultPermissionGrantPolicy as
that breaks a lot of gmscore stuff.
Introduced new action to manage write system settings as a new API and
renamed the string that describes the managing of overlay permission.
Change-Id: Ifd25a6ddc06de68ee37015cb9fb23452e4ef10f4
This is to fix the case where the caller has GRANT_REVOKE_PERMISSIONS
but does not have MANAGE_USERS permission.
Related to a recent fix for
Bug: 22356546
Change-Id: Id51157abad14a0bdba3a16d7cd168f61ba25e890
This allows fingerprint enrollment to be done from
system-installed apps, such as Setup Wizard.
Fixes bug 21695577
Change-Id: I990912dcf229aa03f6350f96a09ff4588b20ca48
The existing documentation is very terse and users were getting
confused whether the method escapes HTML metacharacters or not. Expand
the description a bit and explicitly state that metacharacters are
escaped.
Bug: 17456925
Change-Id: Icaae7fe1344629de5c0860674f3913781de18013
Also removed READ_PHONE_STATE from SystemUI since it has
READ_PRIVILEGED_PHONE_STATE.
Bug: 22376654
Change-Id: I437f9bf324950cb70bae5be76699824da5897a6f
Previously touch slop for line movement was based on the line position
of the HandleView, not the previous line touched.
Thai and CJK languages don't have a space at the end of a line so
the handle jumps to the beginning of the next line. This meant that
when calculating the touch slop it'd be from the incorrect line.
This CL tracks the previous line touched and uses that instead to
calculate touch slop and applies it to the selection and insertion
handles.
Note this is *not* added to the drag accelerator because
it does not have the problem of the handle jumping to the next line
since it has no handles.
Bug: 21925162
Change-Id: If4b231725c06489ec780a5b5a308ceffee804c20
Fixes a bug where during the animation of
the backdrop uninitialized memory was showing
because the backdrop's alpha was zero, so RenderNode
didn't issue any drawing commands.
Bug: 21472158
Change-Id: I7ad6bb64e739059febffca10463c8097693a9563
This reverts commit bef8a3e39372ca85104b894f7359deddc97a8fec.
Changed caused some existing apps to crash. Reverting to unblock the
build while I investigate.
Bug: 22170595
Bug: 22397812
Legacy VPN does nothing if the device has no underlying network
connection, so showing this warning in that case is confusing.
Conversely third-party VPN can still be dangerous since a malicious
app will store sensitive information and upload it later.
Bug: 21499103
Change-Id: I25a0d4e1e5b10198cb067f06645f0e5ecf81bf56
When a Keyguard exit animation was played while the screen was
turning off, the window animation was cancelled. However, since
we didn't reset mPostKeyguardExitAnimation, we thought we need to
apply it again, with a start time of Long.MIN_VALUE. For some reason,
this animation never ended, and it was stuck at the beginning. Thus,
the alpha was 0 and the user just saw a blank wallpaper.
In addition, we also forbid starting the Keyguard exit animation when
the screen is about to turn off.
Bug: 21124013
Change-Id: Ief022c5bd758a9fedcaab3fe9fc385fa4234b37f
Fixes broken anchors in yellow banner on English version. Adds the banner
to non-English version pages. Adjusted wording for a Known Issue on the
"Support and Release Notes" page.
Change-Id: Ia1db8db34cec854bcc4ad7daa1ad44fa23fc878e
