The fix passes the calling userId instead of the current userId to
allow apps running as managed profiles to work.
Fixes bug 28666104
Change-Id: I9f8676ab11bd581d9e67b2b9f385036d4d3576ee
It's certainly not needed for two up, so remove the staging aspect.
Freeform resizing is currently broken because of another bug so this
can't be tested, but because we are not "shipping" it in any case
fixing the 2-up bug is more important, but it shouldn't break freeform
anyways.
Bug: 28618501
Change-Id: I6f285a714281fde50fd7328a3f8999cfa8dfb2c5
am: 0316ed0766
* commit '0316ed0766f6325fa9885488ae0ff0abe6a15a43':
Fix javadoc missing possible return value in AudioRecordingConfiguration
Change-Id: Ice00d789543bb7f9fb53c39052a3a9adfae1a4e0
Previously any apk bundled in priv-app could insert a backup transport.
Reduce risk surface by giving the OEM explicit control over who is
allowed to handle backup data.
Bug 28406080
Change-Id: I84ed954c31b41b671825122e537971b110e00a4d
am: 281d96e238
* commit '281d96e238ba53dba339df7ffde05cf1f46eb1b5':
TIF: Fix comments for program start/end times
Change-Id: Ied59868e8aaa3e35f27b0e4b42bc67eb3b50208a
This version of the APK Signature Scheme v2 documentation doesn't
mention the "apksigner" command-line tool, since this feature isn't
supported as of I/O 2016. However, it will still be possible to sign
an app using APK Signature Scheme v2---and disable v2 signing---using
Android Studio 2.2 and Gradle.
This document is gated on the release of Android Studio 2.2,
scheduled to release on the first day of I/O (May 18).
Bug: 28143514
Change-Id: I00164a740bcc19b5ba08b517023cca11f4373680
Original-Change-Id: Ied916823424d38731e03073b07166f54e8a86b66
Also, fix regression...don't show "internal storage" option in Downloads.
All other modes, fix inconsistencies in presentation of
internal-storage/new-windows commands by eliminating launch mode inference.
Update VolumeInfo and MTP provider to send correct launch mode extra.
Bug: 28691735,28695347
Change-Id: Ic480925f4c8f1beee4da104a2259c1ce5f28a6a1
am: fe03504cf1
* commit 'fe03504cf1904a955bd8bbcd26f9121d754f5fc0':
Fixed a bug where the content wasn't transforming in a group
Change-Id: I689fa839a7bd489b65cc160bda659a46411668a8
am: 549a822331
* commit '549a822331a522cabfb854b91b1cad5a0f7128ae':
Fixed a bug where the positioning on the lockscreen was wrong
Change-Id: Ia1a7619019069599fcde4f3002e44517bb7d4572
This fixes a bug where the cached copy of authenticatorId
was incorrect immediately after enrolling a new fingerprint.
During enroll, the authenticatorId is changed and needs to be updated.
The fix is to always get the new authenticatorId when we
call setActiveGroup(), which happens during every new
Fixes bug 28606914
Change-Id: I8b2d3afe67b3677b6e4516a550d874d9c2e426cd
Now that we live in an FBE world, we need the user to be involved
with every package move to ensure that CE storage is unlocked. This
means that a package upgrade session that would require moving an
app between storage devices cannot be satisfied.
Bug: 27147501
Change-Id: I274d85cbed727d9185178b77bfc6cef196df17f5
When installing an APK that supports multiple ABIs, the ABI installed
can be forced to the secondary ABI [i.e. On devices that support both
32 and 64 bit variants, the 32-bit version can be forced when it's
the secondary ABI.] In this case, instrumenting the class always tried
to use the primary ABI. Instead of blindly using the primary ABI and
dropping the secondary ABI, we propagate both ABIs and make a
decision on which one should be chosen.
Bug: 28406240
Change-Id: I7ebb2fd264d2281912afd30f6d73ccb460f9cf85
This change adds
- Open/close the disambig shade with a featured app
- Open/close the disambig shade with no featured app
- User selected "Always" for the featured app
- User selected "Just Once" for the featured app
- User chose a non-featured app
Bug: 26108706
Change-Id: I4d2c99cee1a784aa1cab156939c57c83d35a4aa5
am: a7ad6e912f
* commit 'a7ad6e912f82124b9a7e6f2d14a2ccbae79d16f2':
ExifInterface: Set mPosition in AssetStream with proper values
Change-Id: Ie35cbb23943aa087d261fd703204d2a4928cee06
- When we are setting the tasks during the initialization of the tasks,
only animate if we are not awaiting the first layout (since those
should override the existing layout).
Bug: 28701153
Change-Id: I4ccb38417df15f43408b2ae77708ba9de407e753
am: 56e2aeba8f
* commit '56e2aeba8fb40190dbe1303ae1d299e77e764b44':
Move Activity multi-window event logic out of the public methods
Change-Id: I7c774d19ff87c52594642f1e5f277f26a2a28b39
am: 9e935820b5
* commit '9e935820b5d0134d71fc5ae51001b276ab603c51':
Reducing the number of recent tasks we keep.
Change-Id: I8f1eab7444272080f151521d5ceab2c185fb828c
