Also tweak the cursor loader samples to filter out query
callbacks that don't change the filter, to avoid restarting the
loader on a configuration change.
Change-Id: Iac9293fed45e127698be59262d68b0b59a8ec9ce
This doesn't contain API 16 just yet. This is just a new version
based on reading all the android.jar instead of the text-based
files.
This new mechanism filters out all methods coming from super
classes as well as interfaces in an effort to make the file
smaller.
Change-Id: Ieefa7d01c29944b2b77b22e8cb81ee2e67afd555
As the delay is added as WaitEvent, throttle time is applied after
the WaitEvent. This cause problem for Tap and Drag. The thorrle time
is then inserted between ACTION_DOWN and ACTION_UP, or ACTION_DOWN
and ACTION_MOVE. This broke the two actions.
Change-Id: I5a122d6cb3d99e38d9442c3de50e0360652c4baf
I've marked this do-not-merge because Email/Exchange are different
in master and this will probably break 'em.
Change-Id: I9f10bd41e143d7b9b6c784d503e79ec28e9f56c3
- Content browser now lets you long press to go into selection mode.
- Overscan demo has more options for controlling more window state.
Change-Id: I04cfb58f515882cc6dccd65cb68bc073e53dcad5
Last attempt to fix ACTION_MOVE ended up breaking stuff
elsewhere.
For a touch based gesture, it usually have a group of motion
events, and typically they have the same down time and individual
event times. Example: a tap should have ACTION_DOWN with same
down time and event time, and subsequent ACTION_UP should have
the same down time as previous one, but a fresh event time.
Similar situation applies to ACTION_DOWN, ACTION_MOVEs,
ACTION_UP sequence of a drag/scroll/fling gesture
In addition, a 5ms delay is added for a tap between DOWN and
UP. And a 5ms delay is added for each injected event in a drag
gesture
Change-Id: I8e65e578152b1c1ff1fa4c0f476ef45806826479
- removed UnifiedEmail, not used in JB
- updated references to media/mca packages, which moved
- libcore junit stuff is now accessed via a library, built from external
Bug: 5584451
Change-Id: Ia5358c66ba191a3a08fea731ad5d8ba3e93c1f89
Currently for motion events, monkey forces current system uptime
onto both down time and event time. This breaks ACTION_MOVE
events because the down time of it is supposed to be the time
when finger is down.
the new logic is:
* check down time, if it's invalid (<0), fill in uptime
* always update event time with a fresh uptime
Bug: 6424997
Change-Id: I0b445815a5015d48c08bebc921c572164874449d
Currently for motion events, monkey forces current system uptime
onto both down time and event time. This breaks ACTION_MOVE
events because the down time of it is supposed to be the time
when finger is down.
the new logic is:
* check down time, if it's invalid (<0), fill in uptime
* always update event time with a fresh uptime
Bug: 6424997
Change-Id: I0b445815a5015d48c08bebc921c572164874449d
Not completely right - seems gubuntu/ubuntu both get unhappy after running
with the 'bridge' option and the PC's routes get hosed (right after the
script is run all is fine, but some agent then removes the routes on the
bridged iface and sets up routes on the native iface (eth0) and things on
the PC lose net access. Note that you can manually reset the routes and make
it happy again).
The fix I applied to the script was related to turning on rndis on the device
and setting device side dns servers correctly so my 'fix' is not responsible
for the eventual unhappniess on the PC. Also, the rev-tether continues
to work fine even when the PC is unhappy, so this may be useful.
Perhaps somebody can figure out who is changing the pc routes and why.
bug:4208971
Change-Id: I6ef6a88c71779b2083dad26a4be35ff74c26aae4
