-> Making sure to update visuals every time adapter count changes
-> Fixing a clipping issue seen on some devices
Change-Id: I489395b5caaa06eb7187b2dac679b793bf54d7e1
We preload classes for two reasons. Classes that are popular can be
shared and can increase the number of apps that can be run concurrently.
Classes that initialize slowly can be initialized at system boot time
by the zygote, decreasing the time to launch a specific app.
To select which classes to preload, I exercised Android's built-in apps
as well as these apps from Market: ESPN score center, Amazon, Flixster,
Twitter, Adobe Reader, Ebay Mobile, Facebook, Solitare (Ken Magic),
Barcode Reader, Google Earth and Square.
A cycle of launching ~460 (non unique) activities in sequence took 9m35s
with the previous preloaded-classes list. The update improves the launch
time of the same sequence to 9m27s: the marginal improvement over the
previous set of preloaded classes is negligible.
http://b/3004763
Change-Id: Ida511ae31eeff6d95d9cb6aacae68b9bb9dd2ebe
Once WebKit claimed it doesn't want to consume the multi-touch events,
we remember that and handle the events in WebView directly.
Change-Id: Idfc99c16b3f4d7f4719791c64fb2355ff66aba5e
dithered at full size
Fix bug 3357191 - Need holo star assets
Fix bug 3357255 - Need expandable list item arrow assets
Fix bug 3373538 - Holo button padding settings difficult to work with
- remove hard padding from holo button styles. This also adds explicit
'small button' holo assets.
Fix bug 3362311 - PopupMenu with just one item has broken borders -
fix 9-patches.
Fix bug 3357195 - Need holo toggle button assets
Change-Id: I9aad9487960dc9f7e7671431ff753a6dde10908a
http://b/issue?id=3378224
This is a simple unhide.
Allow the use of WebView pinch-to-zoom gestures
without the on screen zoom controls.
Currently, enabling pinch to zoom with the public API also shows the
on screen zoom buttons.
If the zoom buttons are not wanted, a custom implementation of pinch to
zoom is required, which can't be done correctly at this point.
Change-Id: I3f94080471c3a4b498b11c91603fff9994dc3c2c
This is a band-aid over the existing kludgy stopping mechanism
where the semantics of stop are different in the activity manager
than in the clients.
This change is intended to be as unobtrusive as possible, only
impacting the sleep case. I have a different change that
completely reworks how we stop activities to simply this all
a lot by unifying the semantics between the server and client.
However, it is too late in HC for such an extensive change. Later
I'll revert this one and put in the better solution.
Change-Id: Id77f2db1ec83469cdd888acb8fbc4679daa7766e
Bug 3374062
When the tap in slightly off the EditText, it receives focus from its parent layout
which dispatches the event. However, the touch event is (correctly) not propagated
in that case.
onFocusChanged should hence do actions similar to what is done on touch up events.
Change-Id: Ia5c04546674fc6239aa4d0b8d051f4951ca91352
