Actually being able to configure a wallpaper relies on additional
work in the launcher and wallpapers that will be in another change.
Also note that this breaks all existing wallpapers, since they now
need to include a meta-data item about themselves. This also
will be fixed in another change.
Change-Id: I97d2c2bd07237abc32f92b9147c32530a2f73c71
Rewrote SurfaceFlinger's buffer management from the ground-up.
The design now support an arbitrary number of buffers per surface, however the current implementation is limited to four. Currently only 2 buffers are used in practice.
The main new feature is to be able to dequeue all buffers at once (very important when there are only two).
A client can dequeue all buffers until there are none available, it can lock all buffers except the last one that is used for composition. The client will block then, until a new buffer is enqueued.
The current implementation requires that buffers are locked in the same order they are dequeued and enqueued in the same order they are locked. Only one buffer can be locked at a time.
eg. Allowed sequence: DQ, DQ, LOCK, Q, LOCK, Q
eg. Forbidden sequence: DQ, DQ, LOCK, LOCK, Q, Q
- The logic for emitting "FN" is wrong.
- FileWriter's "double close" problem should occur in the current implementation.
- Let VCardParser_V31.java ignore AGENT field instead of throwing an unkind VCardNotSupportedException.
ViewRoot was using Surface.clear(), which has different behavior
in different processes -- in the system process it would kill the
surface, causing all windows in that process to immediately disappear
instead of animating away.
This change makes Surface.release() public and uses that instead. It
also renames Surface.clear() to Surface.destroy().
Also fixed some issues in the window manager that were causing the
wallpaper to not get immediately resized when the orientation changes
and its target window is removed and re-added.
Change-Id: I2a992e365cf5747511f0bf1193db32dc2525b218
The check for whether the release call is coming from another process was
very broken, and just happened to work by chance. It also never worked for
apps that had code running in two different processes, with one process
using a provider in another of its processes. Also a little cleanup and
debugging logs for provider management, and removal of that increasingly
annoying log about services being stopped.
Change-Id: Ibc298e674db7d35c4b6499fb32e30929a141b670
* changes:
Integrated the profiler into the framework. We run it all the time if the persist.sampling_profiler system property is set. Saves snapshots to the SD card.
Also, introducing a more advanced email filter, which will do a proper name
lookup using the normalized name and avoid returning duplicate results.
Also, upgrading the phone filter to do the same thing as the email filter
but with display names and phone numbers.
Merge commit 'a4eb91da03bd785bc91bed0d25a9efaa9baba1c1' into eclair-plus-aosp
* commit 'a4eb91da03bd785bc91bed0d25a9efaa9baba1c1':
dumpstate: Add the ctime (time the file was harvested out of /proc) to dump.
Merge commit 'ffae4fcc78d0f280da6052d102b11962fb8041b7' into eclair-plus-aosp
* commit 'ffae4fcc78d0f280da6052d102b11962fb8041b7':
attempt to fix [2099362] Possible SurfaceFlinger crash
Merge commit '9cc1817d46d8092865d8f1e7a6391dcae197a26a' into eclair-plus-aosp
* commit '9cc1817d46d8092865d8f1e7a6391dcae197a26a':
Fixing a concurrency problem by changing the contact aggregation exception API.
Merge commit 'ac67ebe667d30f3cd2e39fa57164d4f3ddaea677' into eclair-plus-aosp
* commit 'ac67ebe667d30f3cd2e39fa57164d4f3ddaea677':
Minor perf improvement to fall and expand use of struct.
Merge commit 'c2042f5e4910c4f7c5b812787ad2b025d93da497' into eclair-plus-aosp
* commit 'c2042f5e4910c4f7c5b812787ad2b025d93da497':
Fix mncLength in cases with a malformed AD_DONE msg from SIM
The current API requires a contact_id and a raw_contact_id
There are at least two issues with this approach I did not recognize initially:
1. Contact_id may be changed asynchronously by aggregation or some other process.
2. A raw contacts may need to be added to an aggregate before the actual aggregation pass
has gotten to it, so the client would need to wait for the aggregation to complete
before it can set an aggregation exception. That's backwards.
Merge commit '6e4b7d66998b9ec9255767f6070a2f94d83944a5' into eclair-plus-aosp
* commit '6e4b7d66998b9ec9255767f6070a2f94d83944a5':
Wallpapers: new transitions, hiding when not visible, other cleanup.
Merge commit 'da214787988ab6bf3c54d96072300723a72b9e3b' into eclair-plus-aosp
* commit 'da214787988ab6bf3c54d96072300723a72b9e3b':
Remove "predefined" elements from Java layer. Static elements continue to exist but are no longer treated as a special version of element.
