History log of /external/qemu/android/sensors-port.h
Revision Date Author Comments (<<< Hide modified files) (Show modified files >>>)
7136b053b7fc7840ec64e01d1d19ab822e1f949a 10-Apr-2012 Vladimir Chtchetkine <vchtchetkine@google.com> Use new SdkController communication protocol for emulation ports

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
/external/qemu/android/sensors-port.h
db611d57e0da9acd7ecf2a4a9b2a63e7620fe54d 02-Nov-2011 Vladimir Chtchetkine <vchtchetkine@google.com> Implements sensors emulation using a connected Android device

There are three major things in this CL:
1. Abstract a connection with an Android device that is connected to the host via
USB, and there is a TCP port forwarding to this device via 'adb forward' command.
This abstraction is implemented in android/android-device.*
2. A client for android device API that talks to an app on the connected device that
provides values for sensors available on the device. This is implemented in
android/sensors-port.*
3. Changes to the sensor emulation code in android/hw-sensors.c to use sensors port
(when available) for sensors emulation.

Change-Id: I12901e8db6b6a6262fc1703ed96a9f714335d666
/external/qemu/android/sensors-port.h