| 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: I534e3fd1305e2f4af076986770033478448a665c
|
| |
|
|
|
| |
Change-Id: Ie142c281c48bda35f5c8fb01ec8a001e0229fd2e
BUG=144042891
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
For packages:
android.os
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
Merged-In: I4ece0a3f37f88fc2508cb965092aed7cabc61819
Change-Id: I0d942254f06c1a355fb906640e223ad34cced6ab
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Remove the queue, reduce core pool size but no longer let it time out.
Reduce the timeout for additional threads.
If necessary, use a special executor, with an unbounded queue, to run
overflow tasks.
Bug: 123762797
Test: AOSP boots, also with MAXIMUM_POOL_SIZE = 1.
Change-Id: I4bc9593a044d1773ff1878684e2397a7c2a9a87a
|
| |
|
|
|
|
| |
Bug: 34278255
Test: TreeHugger
Change-Id: I0347072112254f98d257a72ef1fc7c21b086df39
|
| |
|
|
|
|
|
|
|
| |
Use the looper from the TextView's thread for the helper
Bug 62043115
Test: Manual, type on edit field and select text
Change-Id: I501430a500016a81963a9f9fa636474b708b9b36
|
| |
|
|
|
|
|
| |
Test: cts/tests/tests/os/src/android/os/cts/AsyncTaskTest.java
b/30304893
Change-Id: Icb50cda8026ddd70d457b5e62eb29c81313ee47d
|
| |\
| |
| |
| |
| |
| | |
am: bae52ec98c
Change-Id: Idb695142488874d52dd406bede0fb4848f7663a9
|
| | |
| |
| |
| |
| | |
Bug: 29323321
Change-Id: Ie3a62480bfee881083b5d266cbc1481fb148d237
|
| |/
|
|
|
|
|
|
|
|
| |
When cancelling, the exception will be eaten by FutureTask, but
onCancelled would end up never being called due to the exception
causing the code to skip calling postResult.
b/30304893
Change-Id: I47d859d9ef77245889816b2b6e10bb380bc4979b
|
| |
|
|
|
|
| |
Bug: 24821101
Bug: 23722178
Change-Id: I73741eb4f812e754d5823b27efec98fca9938329
|
| |
|
|
|
|
|
|
| |
...of address space causing package manager to fail
Make sure to flush binder commands when done with an async task.
Change-Id: I9f171add7051587ab854226b97a12c7e1844ad5d
|
| |
|
|
| |
Change-Id: I24bda29261cdecbe78b2529866624b9313ca5c03
|
| |
|
|
| |
Change-Id: If59381862e3332675fd7b929bcee2928ecd0da21
|
| |
|
|
|
|
|
|
|
|
| |
It seems we were sort of trying to do this by forcing the AsyncTask
static initializer to run at certain times but it was not sufficiently
reliable. In particular, this resulted in occasional system
server crashes.
Bug: 18192406
Change-Id: Ief73210c60e7680fbed6df74e3e58809b7ec7e4d
|
| |
|
|
| |
Change-Id: Ida827957623cf49981e5a0c2c9193ef4efe8d1ce
|
| |
|
|
| |
Change-Id: I418d855b5d08a1a20eaca3d8e4d2e5d0fca23dd5
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Bug #10228005
From the ThreadPoolExecutor documentation:
- If fewer than corePoolSize threads are running, the Executor
always prefers adding a new thread rather than queuing.
- If corePoolSize or more threads are running, the Executor
always prefers queuing a request rather than adding a new thread.
- If a request cannot be queued, a new thread is created unless
this would exceed maximumPoolSize, in which case, the task will
be rejected.
Before this change AsyncTask could create up to 128 threads because
of the limited queue of 10 items (the capacity of a blocking queue
is fixed.)
This change increases the size of the queue to 128 items and reduces
the maximum number of threads to the number of CPU cores * 2 + 1.
Apps can still submit the same number of tasks.
Change-Id: I015d77b53b6a9fda39c618830b34d45a10de5571
|
| |
|
|
| |
Change-Id: Ie98dd00f41add876f3740f5d37781a10c6bd41fe
|
| |
|
|
| |
Change-Id: I678506309f027bb12d0c3f42436a60611aca5d8c
|
| |
|
|
|
|
|
| |
Throwable includes classes of Error that really should be fatal.
Bug: 5945222
Change-Id: I602f958396048451f404dd2306cdf5e57172acf0
|
| |
|
|
| |
Change-Id: I039e5d6cb7157a0c8873e0d29161daf1cbda5577
|
| |
|
|
|
|
|
|
| |
Bug #5651553
As dfined by the documentation.
Change-Id: I627a49ee000d6990b61fd64dde9b06f72cd5cbae
|
| |
|
|
| |
This reverts commit 7498ccb6b9a1e61281d998fc81adc9a4a5e87e56.
|
| |
|
|
| |
This reverts commit 4db2504adab21e4439c123d2675db555e0143afa.
|
| |
|
|
| |
Change-Id: I3071feab62abee7393557ceb920786b476fb0b02
|
| |
|
|
| |
Change-Id: I181b253c50a6579f35e61cd4b0c500379462e035
|
| |
|
|
| |
Change-Id: I5df1c4e13af67ff4c4a5b22f3cb1247bf0103b09
|
| |
|
|
|
| |
This reverts commit 6dafefb0f44c4e57384e2ec3e08fefac5cc7e071
This change is breaking the system on startup with an NPE. Need to fix that first then resubmit.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Bug #5333924
This might break applications trying to use AsyncTask on a looper
that is not the main thread, but such apps would already have
issues (AsyncTask has a single static handler and attempting to
use AsyncTask outside of the main thread would likely result
in weird threading issues in other parts of the app.)
Change-Id: Ibbf480627fc7b91326a27d4f5e5af49e8c5b5115
|
| |
|
|
|
|
| |
serialized one after that.
Change-Id: I47d135ace5f8e78e4fa44ac9d1bf7abeeb9d3ba0
|
| |
|
|
|
|
| |
...for now.
Change-Id: I1fe64f3e3a575f85add11dfe4d405f0c3a4a49de
|
| |
|
|
| |
Change-Id: I4b543f306d58ec95693c8e3515dffcb7dd55dc29
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The default is now to serialize everything onto the thread pool. If you would
like to have finer grained control over how AsyncTasks are executed, you can
call the new executeOnExecutor method, which takes a custom Executor. The
pool used by the default is handily now accessible as THREAD_POOL_EXECUTOR.
This change is because it is too tempting to convert single threaded Janky™
code to use AsyncTask in a way that is unsafe and ends up calling the
AsyncTasks in parallel.
Also, this adds a static execute(Runnable) method to AsyncTask that posts
onto the serialized queue, so that if you don't have any parameters or
return values, you can just use Runnable instead of AsyncTask.
Change-Id: I91bdfb00193542bfc2e101bcad56e3430421884a
|
| |
|
|
|
|
|
| |
In some situations, when cancel() was called before the task had a
chance to start its execution, onCancelled() would not be invoked.
Change-Id: I6c1f4cd28a209fb8cc779bb212f500565dfceaae
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Bug #3109366
Bug #3109382
The new behavior of AsyncTask is the following:
- Unchanged if you don't call cancel()
- If you call cancel():
- Either onCancelled() *OR* onPostExecute() is invoked
- onCancelled() is invoked only after doInBackground() finishes
Change-Id: If53faec5890d2fa7098aea76973186a0b1026b39
|
| |
|
|
|
|
|
|
| |
- Remove old method names.
- Introduce onXxx() hooks to Loader.
- Improve debugging.
Change-Id: I3fba072a05c7023aa7d2c3eb4e126feb514ab6d8
|
| |\
| |
| |
| |
| |
| |
| |
| |
| | |
threads." into gingerbread
Merge commit '282315e154b63a2eec84609600c81ad9e1c72994'
* commit '282315e154b63a2eec84609600c81ad9e1c72994':
Change the keep alive time for excess idle threads.
|
| | |
| |
| |
| | |
Change-Id: Ie076544df5ee8df185f0824333fdc62203a565c2
|
| | |
| |
| |
| | |
Change-Id: I4fba91922f033af408903cc4b455daa291e3f6ac
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This introduces basic infrastructure that should allow content
providers holding complex data to perform on-demand conversion
of their data to streams of various types. It is achieved through
two new content provider APIs, one to interrogate the possible
stream MIME types the provider can return, and the other to
request a stream of data in a particular MIME type.
Because implementations of this will often need to do on-demand
data conversion, there is also a utility intoduced in ContentProvider
for subclasses to easily run a function to write data into a
pipe that is read by the client.
This feature is mostly intended for cut and paste and drag and
drop, as the complex data interchange allowing the source and
destination to negotiate data types and copy (possible large)
data between them. However because it is fundamental facility
of ContentProvider, it can be used in other places, such as for
more advanced GET_CONTENT data exchanges.
An example implementation of this would be in ContactsProvider,
which can now provider a data stream when a client opens certain
pieces of it data, to return data as flat text, a vcard, or other
format.
Change-Id: I58627ea4ed359aa7cf2c66274adb18306c209cb2
|
| | |
| |
| |
| |
| |
| | |
Re-ran runtest cts-os
Change-Id: I518a2a4f842b01d082078e16643aa377a4575237
|
| | |
| |
| |
| |
| |
| | |
Bug #2734382
Change-Id: I8d507ae72af2f6dfe66598fb9090872520111a6b
|
| |/
|
|
| |
Change-Id: I0541709a719e35575bb2c42e6f2ea457d21c545b
|
| |
|
|
| |
Change-Id: Idbe649678a7321a6bd9511218788bc4dfb3cbdb4
|
| |
|
|
|
|
|
| |
This is in accordance to the documentation. This bug was approved by hackbod.
The change is safe and is a single line of code.
Change-Id: I9b771df3ae2aa4f496d15e6c43b677f3245539ac
|
| |
|
|
|
|
|
| |
This change allows up to 5 AsyncTasks to run concurrently. Before, only 1 task
could run at a time, which was too limited. This change also bumps up the maximum
number of tasks that can be created; this large number is not an issue because
tasks are queued up and run only 5 at a time.
|
| | |
|
| | |
|
| | |
|