| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
| |
As it turned out, emulator has been sending Fb updates faster than MT handler on the
device could process them. This lead to significant screen lag between the emulator
and the device. With this CL emulator will not send FB updates to the device until
the device has fully proccesed the previous FB update.
Change-Id: I9a39e9f358f87d5bd6baaa2617a79e7de59ae99e
|
| |
|
|
|
|
|
|
|
| |
When MT handler gets deactivated, and then activated again, it shows a stale emulator
display, since it didn't have a chance to catch up with emulator display updates. This
CL ensures that entire emulator display is pushed to the device when MT handler gets
activated.
Change-Id: I58c1680f50e2af3e6afa0518f6bcaa3ed087638d
|
| |
|
|
|
|
|
|
|
| |
It turned out, that OpenGLES framebuffer update callback is expensive, and since it's
used rather rarely (since multi-touch emulation is usually off), it's a waste to have
that callback always active. So OpenGLES has now an ability to enable / disable framebuffer
update callback, and emulator needs to catch up with that change.
Change-Id: Iee028ed79f1d9472c3f31bbfbcb5676c4716c34c
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
android/sdk-control-socket.* has replaced android/android-device.* as the back-bone
of communicating with SDK controller on the device. The major differences are:
- New communication protocol uses just one (async) socket connection to communicate
with the device (the old one used two sockets: one sync, and another - async).
- New communication protocol connects to one TCP port (1970 in this CL) for all emulation
ports. Channel multiplexing is done by using port names, and assigning a separate socket
for communication inside each separate port. The old protocol had separate TCP ports for
each emulation ports (1968 for sensors, and 1969 for multi-touch)
Change-Id: I779fcbdfba2f9b4c433a9d76a567975708b00469
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This CL implements a callback that gets invoked by OpenGLES emulator on it framebuffer
updates. This allows transferring framebuffer changes to the supporting device.
Proper implementation of this new callback also required changes to JPEG compression,
addressing:
1. OpenGLES framebuffer format is RGBA8889, which required implementing line conversion
for this format.
2. OpenGLES framebuffer is (or at least could be) bottom-up arranged. This requires changes
to the compressor, so it compresses the FB starting from the bottom, so the resulting
image is up-bottom.
Change-Id: Icd4efbe4a251c838adfa3518decbfc43a7ef06c8
|
|
|
Change-Id: I311dc55fe10f41637775baa330a7c732ff317f51
|
