am: 9e06acf
* commit '9e06acf392e82cb539b9e40ec9909a9c8dbc221b':
Add a callback for when a gl functor is released
Change-Id: I4f3d272a598f45a6124a6fc64f9178f1c4d659a0
am: 85cfc8c
* commit '85cfc8c368523359be8c12b8551e122b94972ab7':
Add a callback for when a gl functor is released
Change-Id: Ie9f602710d46faf045d04ff425bee8428d6fe9c7
When having an app docked and then going home, and then launching
the app from the homescreen, we had a wrong transition because
getTopMost task was already set to the launched app, because
getRunningTasks doesn't exclude the docked stack. Instead of adding
flags for getRunningTasks, which sounds risky, we just pass a "force"
value when we launch recents in this state.
Bug: 27154882
Change-Id: Iee4512fed13115dbbe8b74413ff1fa9b87afa0ef
am: 229e517
* commit '229e5179ba1915b5beb86b0d7989fb356bef9966':
Make ConnectivityMetricsLogger and related classes @SystemApi
Change-Id: Ia33ecf02187f0c945c0e70d6d939c310cca3c6e1
am: 74870c4
* commit '74870c441fde0aa141edca84f066d1ace4cf5db5':
Make ConnectivityMetricsLogger and related classes @SystemApi
Change-Id: Id302c045286578163c40eb02108d675c6031afc5
Per feature council decision, the multi-endpoint APIs will be @hide for
the N release.
Bug: 28196918
Change-Id: Ia80b089bc754ce87ca208382eb79442b5265844d
Setting PARSE_IS_SYSTEM to the parse flags happens long after the
APK is actually parsed. So, we fail to pick up the boot aware and
protected storage attributes. Instead, always pull them from the
manifest, but, remove the flags if the package is not actually a
system package.
Also, we were incorrectly skipping certificate verification if
the flag PARSE_IS_SYSTEM was set. However, this flag is used for
_any_ system package -- whether it's physically on /system or if
it's an unbundled update. Instead, we should only skip this step
if the flag PARSE_IS_SYSTEM_DIR. We can implicitly trust any
APK actually stored in /system.
On a different note ... At some point, we will break apart the
parse flags into actual parse flags [i.e. those that change
physically parsing an APK] and policy flags [i.e. those that
change the interpretation of the APK contents].
Bug: 28116074
Bug: 28088617
Change-Id: I85246b0cb18fb5647df3618107910e288137fbc7
am: f1320d1
* commit 'f1320d1d7fb91b66e82533ea6b93ffd6903d834e':
Maybe decrypt user when quiet mode is disabled
Change-Id: I5f021888ad89e554f8b47e9ff8283f2b12bdabee
am: 2f4c229
* commit '2f4c2299c7ef4b9d604b9833c790a7afd2ed75af':
Maybe decrypt user when quiet mode is disabled
Change-Id: I0d84934a978205c283b846b7412446a064aac01c
When quiet mode is disabled for a user and that user is not currently
decrypted, we show a confirm credentials screen to trigger decryption
of that user. Only if that was successful, do we actually disable quiet
mode.
Bug: 27764124
Change-Id: Ib1f649194d89e225dad62c14f3ddba1fa3d79da2
The JavaDoc for many of the requestNetwork and
[un]registerNetworkCallback APIs incorrectly mentions the
PendingIntent version of the APIs instead of the NetworkCallback
version.
Also fix a minor issue in the registerDefaultNetworkCallback
JavaDoc: the default network request is an implementation detail,
so don't mention it. Instead, talk about the "system default
network".
Change-Id: Id94d98261daa2bd768c10e033cb8092729b21c91
am: 021af18
* commit '021af1800c352933d25f927dc357534c62a9e39c':
Remember task which is being locked
Change-Id: I06c64b220fe20775510b938c5235acf026c83c7d
am: 5981b8c
* commit '5981b8c2e8f6363d1f3bf09e7f1b3b5fb9a3846a':
Remember task which is being locked
Change-Id: Id672304edaa6a02777e79fe6b4fcdd64e3c5f7e8
am: 77efec3
* commit '77efec3b61e8083468594f288e27811281e8d515':
Disable resize when IME is adjusted
Change-Id: I04013df69b368c8aecb53790a7985e38be4641ce
am: 698e763
* commit '698e7634aa2ced554f564f588c2e878fb35757a3':
Disable resize when IME is adjusted
Change-Id: I27772f9325668c48d878533074d72b07ad78f909
We need to remember task which requested to be locked
because we can accidentally lock another task after
user interacts with pinning request dialog.
Bug: 27876860
Change-Id: Ie8e607df4380dd33ea9b3474afc247b02e31de07
am: 29900ea
* commit '29900ea7512676a658c5f0232598ca567a32021d':
Fix bug where fingerprint events can be delivered to the wrong client
Change-Id: I49d7088704373a1c2a6b77c6b3dbe0123ccca058
am: 9520505
* commit '952050539c991fcf58cd1f336193aa04890ad0a3':
Fix bug where fingerprint events can be delivered to the wrong client
Change-Id: Ie924a9b1f05ed7988a5b897ef3c3f35b088080ff
- Make FingerprintService more closely track the expected state of fingerprintd.
- Don't switch to a new operation until fingerprintd completes previous operation.
- Refactor clients into separate classes and add tracking logic.
- Add missing enumerate()/cancelEnumeration() methods to IFingerprintDaemon
- Make late-binding decision of "foregroundness" of activity so that it's
decided in the order the events are actually handled.
- Add more logging so we can determine FingerprintService state when errors occur.
- Cache a copy of authenticator_id from the last time it was set so we don't
interrupt the driver during actual authentication.
- Don't allow clients to access authenticator_id unless they're current.
Fixes: 27902478, 26273819
Change-Id: Ic1f9e30bd89bcdbb8fe7f69e0545e68339317721
