| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
| |
Existing annotations in libcore/ and frameworks/ will deleted after the migration. This also means that any java library that compiles @UnsupportedAppUsage requires a direct dependency on "unsupportedappusage" java_library.
Bug: 145132366
Test: m && diff unsupportedappusage_index.csv
Change-Id: I5be7335b23a92b8ac80d2fd890198273b66ad644
|
| |
|
|
|
|
|
|
|
| |
Added ContextThemeWrapper#setTheme(Theme) method to programmatically
assign the theme without using a resource id
Change-Id: I043253e65a535abdf8d89d9421d2cff2b41bdb05
Fixes: 123768723
Test: Added CTS test to verify setTheme
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
For packages:
android.view.textservice
android.view.textclassifier.logging
android.view.textclassifier
android.view.inputmethod
android.view.autofill
android.view.accessibility
android.view
This is an automatically generated CL. See go/UnsupportedAppUsage
for more details.
Exempted-From-Owner-Approval: Mechanical changes to the codebase
which have been approved by Android API council and announced on
android-eng@
Bug: 110868826
Test: m
Change-Id: I4147b038ed7adf0311ee9918b44766f82a057eaf
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Rather than require an a-priori Notification be supplied in order to
start a service directly into the foreground state, we adopt a two-stage
compound operation for undertaking ongoing service work even from a
background execution state. Context#startForegroundService() is not
subject to background restrictions, with the requirement that the
service formally enter the foreground state via startForeground() within
5 seconds. If the service does not do so, it is stopped by the OS and
the app is blamed with a service ANR.
We also introduce a new flavor of PendingIntent that starts a service
into this two-stage "promises to call startForeground()" sequence, so
that deferred and second-party launches can take advantage of it.
Bug 36130212
Test: CTS
Change-Id: I96d6b23fcfc27d8fa606827b7d48a093611b2345
|
| |
|
|
|
|
|
|
|
|
| |
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
|
| |
|
|
|
|
|
|
|
| |
Refactors to getResourcesInternal() and calls that from both methods.
Adds documentation on Context.getResources() and getAssets() that the
instances returned should be consistent with each other.
Bug: 26228895
Change-Id: I41b09f1e9a3a0315bcdf1c08a7b431a9a697bb6f
|
| |
|
|
|
|
| |
Fix trailing white space, use of final, comments.
Change-Id: Iacc034acd46a651c35c32f2efbc0fe5fb58e1209
|
| |
|
|
|
| |
Bug: 23416037
Change-Id: Ia87bebbe6f23214c892bc2ca19d4112853023235
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Previously the theme could only be set if it had never been obtained,
which was inconsistent with the documentation for Context.setTheme()
and the behavior of ContextThemeWrapper.
Also prevents double-apply of themes in setTheme().
Bug: 20756250
Bug: 20230451
Change-Id: I2566b3e4546cd1c68db79f10f01a5a1256fd439c
|
| |
|
|
| |
Change-Id: I37c8afdaea455aa92bc8270bb2dfd60616c5f9bc
|
| |
|
|
|
|
|
|
| |
Also adds methods for setting the context used to inflate drop-down
views in several adapters.
Bug: 17625714
Change-Id: Id267afa4901c1d46ceb3bc3b10fc642cea1799fe
|
| |
|
|
|
|
| |
This reverts commit e4ab72d54cf41d16819b72e94d9b0d0d51289647.
Change-Id: Id17170312c75993fc1f7859d52c7e050b2aeaf80
|
| |
|
|
|
|
|
| |
Also adds a few missing styles and reorganizes some XML files. Makes
stackViewStyle public since it's defined in DeviceDefault.
Change-Id: I8f6a0f93410948b38619594474d60dc40ece5917
|
| |
|
|
|
|
|
| |
- remove reference to base Context as we can get it thru
getBaseContext() call
Change-Id: I2687c15db12624243fadba44d624e2e4bdae240d
|
| |
|
|
| |
Change-Id: Ia1f99bd2c1105b0b0f70aa614f1f4a67b2840906
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
This allows you to, say, make a Context whose configuration
is set to a different density than the actual density of the device.
The main API is Context.createConfigurationContext(). There is
also a new API on ContextThemeWrapper that allows you to apply
an override context before its resources are retrieved, which
addresses some feature requests from developers to be able to
customize the context their app is running in.
Change-Id: I88364986660088521e24b567e2fda22fb7042819
|
| |
|
|
|
|
| |
Also clean up theme selection code to get rid of duplication.
Change-Id: Idf7b21db70ee83fce24756ead877169bd08b77a9
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
...to throttle contentobserver-based requeries
Why yes, I guess it could.
This also reworks AsyncTaskLoader to not generate multiple
concurrent tasks if it is getting change notifications before
the last background task is complete.
And removes some of the old APIs that had been deprecated but
need to be gone for final release.
And fixes a few little problems with applying the wrong theme
in system code.
Change-Id: Ic7a665b666d0fb9d348e5f23595532191065884f
|
| |
|
|
| |
Change-Id: Ia2e8264147bb02e29599227d0588e40b1e626358
|
| | |
|
| | |
|
| |
|