tree: 90ddab82f28f81cb1b8baad851846f2366790b41 [path history] [tgz]
  1. Android.bp
  2. MODULE_LICENSE_APACHE2
  3. NOTICE
  4. OVERVIEW.TXT
  5. OWNERS
  6. README.md
  7. SERVICES.TXT
  8. SOCKET-ACTIVATION.txt
  9. SYNC.TXT
  10. adb.bash
  11. adb.cpp
  12. adb.h
  13. adb_auth.h
  14. adb_integration_test_adb.xml
  15. adb_integration_test_device.xml
  16. adb_io.cpp
  17. adb_io.h
  18. adb_io_test.cpp
  19. adb_listeners.cpp
  20. adb_listeners.h
  21. adb_listeners_test.cpp
  22. adb_mdns.h
  23. adb_test.xml
  24. adb_trace.cpp
  25. adb_trace.h
  26. adb_unique_fd.cpp
  27. adb_unique_fd.h
  28. adb_utils.cpp
  29. adb_utils.h
  30. adb_utils_test.cpp
  31. adb_wifi.h
  32. apex/
  33. benchmark_device.py
  34. bugreport_test.cpp
  35. client/
  36. compression_utils.h
  37. coverage/
  38. crypto/
  39. daemon/
  40. fastdeploy/
  41. fdevent/
  42. file_sync_protocol.h
  43. libs/
  44. mdns_test.cpp
  45. pairing_auth/
  46. pairing_connection/
  47. proto/
  48. protocol.txt
  49. security_log_tags.h
  50. services.cpp
  51. services.h
  52. shell_protocol.h
  53. shell_service_protocol.cpp
  54. shell_service_protocol_test.cpp
  55. socket.h
  56. socket_spec.cpp
  57. socket_spec.h
  58. socket_spec_test.cpp
  59. socket_test.cpp
  60. sockets.cpp
  61. sockets.dia
  62. sysdeps.h
  63. sysdeps/
  64. sysdeps_test.cpp
  65. sysdeps_unix.cpp
  66. sysdeps_win32.cpp
  67. sysdeps_win32_test.cpp
  68. test_adb.py
  69. test_device.py
  70. tls/
  71. tools/
  72. trace.sh
  73. transport.cpp
  74. transport.h
  75. transport_benchmark.cpp
  76. transport_fd.cpp
  77. transport_test.cpp
  78. types.cpp
  79. types.h
  80. types_test.cpp
README.md

ADB Internals

If you are new to adb source code, you should start by reading OVERVIEW.TXT which describes the three components of adb pipeline.

This document is here to boost what can be achieved within a “window of naive interest”. You will not find function or class documentation here but rather the “big picture” which should allow you to build a mental map to help navigate the code.

Three components of adb pipeline

As outlined in the overview, this codebase generates three components (Client, Server (a.k.a Host), and Daemon (a.k.a adbd)). The central part is the Server which runs on the Host computer. On one side the Server exposes a “Smart Socket” to Clients such as adb or DDMLIB. On the other side, the Server continuously monitors for connecting Daemons (as USB devices or TCP emulator). Communication with a device is done with a Transport.

+----------+              +------------------------+
|   ADB    +----------+   |      ADB SERVER        |                   +----------+
|  CLIENT  |          |   |                        |              (USB)|   ADBD   |
+----------+          |   |                     Transport+-------------+ (DEVICE) |
                      |   |                        |                   +----------+
+-----------          |   |                        |
|   ADB    |          v   +                        |                   +----------+
|  CLIENT  +--------->SmartSocket                  |              (USB)|   ADBD   |
+----------+          ^   | (TCP/IP)            Transport+-------------+ (DEVICE) |
                      |   |                        |                   +----------+
+----------+          |   |                        |
|  DDMLIB  |          |   |                     Transport+--+          +----------+
|  CLIENT  +----------+   |                        |        |  (TCP/IP)|   ADBD   |
+----------+              +------------------------+        +----------|(EMULATOR)|
                                                                       +----------+

The Client and the Server are contained in the same executable and both run on the Host machine. Code sections specific to the Host is enclosed within ADB_HOST guard. adbd runs on the Android Device. Daemon specific code is enclosed in !ADB_HOST but also sometimes with-in __ANDROID__ guard.

“SMART SOCKET” and TRANSPORT

A smart socket is a simple TCP socket with a smart protocol built on top of it. This is what Clients connect onto from the Host side. The Client must always initiate communication via a human readable request but the response format varies. The smart protocol is documented in SERVICES.TXT.

On the other side, the Server communicate with a device via a Transport. adb initially targeted devices connecting over USB, which is restricted to a fixed number of data streams. Therefore, adb multiplexes multiple byte streams over a single pipe via Transport. When devices connecting over other mechanisms (e.g. emulators over TCP) were introduced, the existing transport protocol was maintained.

THREADING MODEL and FDEVENT system

At the heart of both the Server and Daemon is a main thread running an fdevent loop, which is an platform-independent abstraction over poll/epoll/WSAPoll monitoring file descriptors events. Requests and services are usually server from the main thread but some service requests result in new threads being spawned.

To allow for operations to run on the Main thread, fdevent features a RunQueue combined with an interrupt fd to force polling to return.

+------------+    +-------------------------^
|  RUNQUEUE  |    |                         |
+------------+    |  POLLING (Main thread)  |
| Function<> |    |                         |
+------------+    |                         |
| Function<> |    ^-^-------^-------^------^^
+------------+      |       |       |       |
|    ...     |      |       |       |       |
+------------+      |       |       |       |
|            |      |       |       |       |
|============|      |       |       |       |
|Interrupt fd+------+  +----+  +----+  +----+
+------------+         fd      Socket  Pipe

ASOCKET, APACKET, and AMESSAGE

The asocket, apacket, and amessage constructs exist only to wrap data while it transits on a Transport. An asocket handles a stream of apackets. An apacket consists in a amessage header featuring a command (A_SYNC, A_OPEN, A_CLSE, A_WRTE, A_OKAY, ...) followed by a payload (find more documentation in protocol.txt. There is no A_READ command because an asocket is unidirectional. To model a bi-directional stream, asocket have a peer which go in the opposite direction.

An asocket features a buffer where the elemental unit is an apacket. Is traffic is inbound, the buffer stores apacket until they are consumed. If the traffic is oubound, the buffer store apackets until they are sent down the wire (with A_WRTE commands).

+---------------------ASocket------------------------+
 |                                                   |
 | +----------------APacket Queue------------------+ |
 | |                                               | |
 | |            APacket     APacket     APacket    | |
 | |          +--------+  +--------+  +--------+   | |
 | |          |AMessage|  |AMessage|  |AMessage|   | |
 | |          +--------+  +--------+  +--------+   | |
 | |          |        |  |        |  |        |   | |
 | |  .....   |        |  |        |  |        |   | |
 | |          |  Data  |  |  Data  |  |  Data  |   | |
 | |          |        |  |        |  |        |   | |
 | |          |        |  |        |  |        |   | |
 | |          +--------+  +--------+  +--------+   | |
 | |                                               | |
 | +-----------------------------------------------+ |
 +---------------------------------------------------+

This system allows to multiplex data streams on an unique byte stream. Without entering too much into details, the amessage fields arg1 and arg2 are used alike in the TCP protocol where local and remote ports identify an unique stream. Note that unlike TCP which feature an “unacknowledged-send window”, an apacket is sent only after the previous one has been confirmed to be received.

The two types of asocket (Remote and Local) differentiate between outbound and inbound traffic.

adbd <-> APPPLICATION communication

This pipeline is detailed in services.cpp. The JDWP extension implemented by Dalvik/ART are documented in:

  • platform/dalvik/+/master/docs/debugmon.html
  • platform/dalvik/+/master/docs/debugger.html