Stop repeating request if any of its output stream is abandoned
and notify that repeating request has been stopped.
Update binder tests for binder interface changes.
Update CameraDeviceImpl to expect an exception when canceling
a repeating request that is already stopped.
Bug: 21270879
Change-Id: I9fa72ae7218948aac88cb1a8e57839bd022c4a5e
- Allow SearchView to expand to 48dp height if possible.
- Make the search clear button have 48dp height if possible.
- Expand the search TextView touch target height to 48dp is possible.
Framework version of patch ag/912646
Bug: 19479861
Change-Id: Ibaaef2afa20b8c05eaac8f028df4f616f2f96eb1
Fixes: 28074239
Need to convert from scaled window to screen before
updating position of the SurfaceView
Change-Id: I75dec23408c32ec01e88193ea38b1fb253b3fd6f
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
Framework edition
Previously we would throw away any stopped LoaderManagers when we went
to retain instances to pass along as nonConfigurationInstances during
config changes or similar activity restarts. This causes loaders to do
more work than they need to when a calling activity starts a new
activity on top, a config change happens (e.g. screen rotation) and
then the top activity is finished, restarting the caller in a new
configuration. The loaders would go through onReset unnecessarily,
potentially throwing away data to be reloaded again after the config
change completes.
Instead of throwing away stopped LoaderManagers in this case, restart
them and retain them across the config change so they can resume where
they left off.
Bug 27176186
Change-Id: Ia52c6448d2ad41dcb25d493770d9ffae20a19d2a
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
