Reply to thread

Message: <blockquote data-quote="SlayerOfDValley" data-source="post: 14704767" data-attributes="member: 386204">ADBAll Thanks goes to Android developers (hi1jason, bshuy2003, thanhhoa, chuyennho184, trakiho, ndvudung, Lamhoang, gatre1, hoangnova and many mem contribute to topic...) Android Debug BridgeAndroid Debug Bridge (adb) is a versatile command line tool that lets  you communicate with an emulator instance or connected Android-powered  device. It is a client-server program that includes three components: <ul> <li data-xf-list-type="ul">A client, which runs on your development machine. You can invoke  a client from a shell by issuing an adb command. Other Android tools  such as the ADT plugin and DDMS also create adb clients.</li> <li data-xf-list-type="ul">A server, which runs as a background process on your development  machine. The server manages communication between the client and the adb  daemon running on an emulator or device.</li> <li data-xf-list-type="ul">A daemon, which runs as a background process on each emulator or device instance.</li> </ul>You can find the adb tool in <sdk>/platform-tools/.When you start an adb client, the client first checks whether there is an adb server process already running. If there isn't, it starts the server process. When the server starts, it binds to local TCP port 5037 and listens for commands sent from adb clients—all adb clients use port 5037 to communicate with the adb server. The server then sets up connections to all running emulator/device instances. It locates emulator/device instances by scanning odd-numbered ports in the range 5555 to 5585, the range used by emulators/devices. Where the server finds an adb daemon, it sets up a connection to that port. Note that each emulator/device  instance acquires a pair of sequential ports — an even-numbered port for  console connections and an odd-numbered port for adb connections. For example: Emulator 1, console: 5554Emulator 1, adb: 5555Emulator 2, console: 5556Emulator 2, adb: 5557and so on... As shown, the emulator instance connected to adb on port 5555 is the same as the instance whose console listens on port 5554. Once the server has set up connections to all emulator instances, you can use adb commands to access those instances. Because the server manages connections to emulator/device instances and handles commands from multiple adb clients, you can control any emulator/device instance from any client (or from a script).Note: When you connect a device running Android 4.2.2 or higher to your computer, the system shows a dialog asking whether to accept an RSA key that allows debugging through this computer. This security mechanism protects user devices because it ensures that USB debugging and other adb commands cannot be executed unless you're able to unlock the device and acknowledge the dialog. This requires that you have adb version 1.0.31 (available with SDK Platform-tools r16.0.1 and higher) in order to debug on a device running Android 4.2.2 or higher.</blockquote>

Verification: Haya warak paha keeyada? (haya wadi kireema paha)

Top Bottom