This change adds support for the new MessagingStyle, which
supports a fully back-and-forth messaging/chat experience
within the notification display itself.
Bug:28043958
Change-Id: Ibb9c2a0784f028d8cf01bd3cee4fecc5f72d68cd
Settings screen should apply both primary and managed maximum
timeout policy, even separate profile challenge is enabled.
Bug: 27493348
Change-Id: Ia1ec1cafc7665c54816833af64e0f446a77a55b2
When the parent instance of DPM is used to call an API that is not
parent-aware, we should throw a security exception.
Bug: 27532279
Change-Id: I90abeb4c8522cb9af798301c1bb2048579596993
This adds a flag to WearableExtender (and Action.WearableExtender)
indicating that the attached ContentIntent will launch an activity
on Wear, which lets the platform know that it can (and should)
generate a sleek transition for the launching of said intent (as
opposed to the intent causing change in the background).
Bug:28019194
Change-Id: Id8b422ea52c5e941e38558aaf31ce2cf4bb7c6f3
In DPM it is possible to retrieve a parent instance to set policies
that are applied to the profile parent. Extend the javadoc to clarify
which APIs are actually callable on the parent instance.
Bug: 27532279
Change-Id: I7ed40f8c3c7c3089283489bff41a04c70239d5a4
1. Fix trust agent config does not persist across reboot
2. xxxTrustAgentConfiguration now supported in parent DPM instance
Bug: 27601827
Change-Id: I6ea4a089bf590d6c44be40318f3a69c35c54f796
Changing Instrumentation to modify the existing
UiAutomation when one with different flags is requested.
Also checking if UiAutomation is destroyed before disconnecting at the
end of a test.
Bug: 27365874
Bug: 27864279
Change-Id: Ia6efc4f89cc30dbe29286f30f8e9cb8f6fdb4712
When using applyOverrideConfiguration, subsequent callbacks to
onConfigurationChanged didn't take into account the locally overridden
configuration. This patches the incoming configuration to match
what is expected by the application.
Bug:27644297
Change-Id: I3a090e9862a56470d999aa0aa4d5bae29f533a11
Add shell commands to check on current FBE status and system ready
status. Mark variables without first-class locking as volatile.
Fix bug where UI automation would crash while device was locked by
marking it as forced direct-boot aware.
Bug: 26498834
Change-Id: Ib4dfb9350925e5413f93a09baacf84c62f2ba0ea
Framework edition
When setting a user visibility hint on a fragment it was possible to
have a FragmentManager already set due to a transaction being composed
but before the commit, so only checking that we have one isn't
sufficient for determining whether we should perform a pending
deferred start. This could happen easily with ViewPager adapters. Use
isAdded() instead.
Also fix a bug where we could set our internal tracking of fragments
that need a deferred start incorrectly.
Bug 27814550
Change-Id: I3be65728650c48d27a3a9dd4ca15f52006d14ab9
If AlarmManager.cancel is called before any component has had a chance
to register an alarm, sWrappers will not have been set, as it is only
initialized in setImpl.
When cancelling an alarm and sWrappers does not exist, log a warning and
return early.
BUG: 27972657
Change-Id: Ied10719ba1d154f97eecfc32f429fd9ce39bf747
Bug 27969302
mCalledExitCoordinator can be nulled before the onResume is called,
so it cannot be used to determine whether or not the Activity is
a caller or called.
Change-Id: Ie3696ed59b89cfc8c6145d22bc230111f0813701
Forgot to cache the creating of ResourcesImpl during an Activity
override config update.
Bug:27644297
Change-Id: I65d9086f6d32f5adc7231aa3a1797d4f00c4b9a9
If the profile owner wants to set a lock screen for a profile which they
created, we should let them. This will cancel any lock screen
unification that has been set up.
Attempting to clear the password will continue to throw
SecurityException if called from a managed profile.
Bug: 26682008
Change-Id: Ia09aef879a21c074ccb517905e43f62696837998
