| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
|
|
| |
These are essentially false positives that are just taking the flags in
as an argument and passing that over to PendingIntent methods. This
change should clear up the noise.
Bug: 160794467
Test: Errorprone builds should no longer show these as violations
Exempt-From-Owner-Approval: Trivial warning suppression
Change-Id: I8ae309fd53140718d41f4d3b94f92e111cdd8955
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The majority of Manager-style classes already use Context.getUserId()
when making calls into the OS, so clean up the remaining callers to
unify behind this strategy.
This gives @SystemApi developers a nice clean interface to interact
across user boundaries, instead of manually adding "AsUser" or
"ForUser" method variants, which would quickly become unsustainable.
Test: builds, boots
Bug: 72863821
Exempt-From-Owner-Approval: trivial changes
Change-Id: Ib772ec4438e57a2ad4950821b9432f9842998451
|
| |
|
|
|
|
|
|
|
|
|
| |
Previously, the panel would still collapse when launching
the notification settings. We're now looking at the
newly returned result of the activity launch instead to
determine if we should collapse.
Bug: 69168591
Test: launch settings activity from notification guts, observe no collapsing
Change-Id: I414e7f4a9fd22d4f0b46437bfdb94e5c0f6cce58
|
| |
|
|
| |
Change-Id: I40cea46efd80c448640ff69753698fe8404da40b
|
| |
|
|
|
|
|
|
|
|
|
| |
This changeset adds in typedef annotations (custom annotations
marked with @IntDef) for various int parameters and return values
in the API. It also adds nullness annotations for cases where the
documentation explicitly mentioned null policy, or where it was
blindingly obvious from the context. Also fixed some typos in the
documentation.
Change-Id: Ica27c01368895818e26237544edd8483007155bb
|
| |
|
|
|
|
| |
Bug 7001327
Change-Id: I5a79e6933cd33386cd0aa4df626f15902deedd67
|
| |\
| |
| |
| | |
Change-Id: Ifc2328e30a52c2baebc1322c9b161104dcf21618
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Required wiring up startActivitiesAsUser()
Bug: 7224950
Also fix a bug in navigateUp in secondary user
Change-Id: I114ae2de0457362d62e899fdb94b12239a3eb778
|
| |/
|
|
|
|
|
|
|
|
| |
When Activity#getParentActivityIntent() returns an Intent without an
explicit target, resolve it in order to determine a correct parent
stack.
Bug 7223318
Change-Id: I3e88129f1e538cc3d932d6b4f735a5bec54bb4ad
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Don't mutate original intents when adding default flags.
* Add the relevant flags to the array returned by getIntents() such
that it can be used directly in a call to startActivities or
similar.
* Deep copy the component intents when building an intent array for
getIntents()
* Clean up some internal code duplication
Change-Id: I71d3b7f30d4f7d8f1cce778d406ea0e513d382c5
|
| |
|
|
|
|
| |
Fix bug 7179104
Change-Id: Ia5d2d285cf22e97c452e0c385ef38c8bce330491
|
| |
|
|
|
|
|
|
|
|
| |
If a generated parent intent targets an Activity that itself has no
parent specified, generate the intent using Intent.makeMainActivity
to gather the correct flags for the root intent of a task.
Bug 6457058
Change-Id: I8d4a3823eda752306da18c2c38fa7e57f0a33bf3
|
| |
|
|
|
|
|
|
|
| |
Let callers try to get a parent stack for an activity class with no
parent declared.
Bug 6503702
Change-Id: Iec1bc7a8d9e5b65b756a8ebd0e53d63506796aa3
|
| |
|
|
|
|
|
|
| |
Don't assume the initial component has a valid parent specified.
Bug 6464209
Change-Id: I22aa4c0e667ea85dc46ad7320f4a9f52117af520
|
| |
|
|
| |
Change-Id: Ic9e11caa4541962d32b2c197f4f7b19ee67a0eda
|
| |
|
|
|
|
|
| |
Let TaskStackBuilder discover a parent activity stack by ComponentName
in addition to explicit Activity classes.
Change-Id: I18b8378548ed1d6ef033800e6a3e11ab965d07e5
|
| |
|
|
|
|
| |
not clear tasks properly.
Change-Id: I5a7918fa5e400c160409a45d3e00b32f6f4809aa
|
|
|
Promote navigation helpers from the support library to the core
platform.
The support library's meta-data element has been replaced with a
first-class parentActivityName attribute. This attribute is valid
on both activity and activity-alias elements. An activity-alias
will inherit the target activity's parentActivityName if one is
not explicitly specified.
Automatic Up navigation for Activities
Add the public method onNavigateUp() to Activity. The default
implementation will use the metadata supplied in the manifest about an
activity's hierarchical parent (parentActivityName) to do the right
thing.
If any activities in the parent chain require special Intent
arguments, the Activity subclass should override onNavigateUp() to
properly implement Up navigation for the app, supplying such arguments
as needed.
If automatic Up navigation within the same task can't find an activity
matching the supplied intent in the current task stack, it will act as
an in-app "home" and return to the root activity (presumably the app's
front page) in that task. (From this state, pressing "back" with
default behavior will return to the launcher.)
Change-Id: If163e27e59587f7af36975a09c986cb117ec3bc6
|