1 of 180

Break On Through To the Other Side

adb_

>

2 of 180

http://eyal.fr

Eyal Lezmy

3 of 180

Join us!

4 of 180

bit.ly/adb-chill

Slides

>

5 of 180

How adb works

Some adb commands

The internals

Dev on the adb project

The Android dev tools

>

6 of 180

alias adb=“Android Debug Bridge”

7 of 180

A command line tool

To communicate with Android devices

physical or emulators

8 of 180

Part of the SDK

on the platform-tools directory

2 versions distributed

Stable & Preview channel

9 of 180

How adb

works

10 of 180

adb

daemon

adb

client

adb

server

11 of 180

adb

client

12 of 180

adb

client

13 of 180

adb_

>

adb

client

14 of 180

adb

daemon

15 of 180

adb

daemon

16 of 180

Started at boot

As background process

Executes commands

on the device

adb

daemon

17 of 180

adb

server

18 of 180

adb

daemon

adb

client

adb

server

19 of 180

adb

daemon

adb

client

adb

server

20 of 180

A practical case

21 of 180

adb

client

22 of 180

adb

client

Is there an ADB Server?

23 of 180

adb

client

adb

server

Start adb server

24 of 180

adb

client

adb

server

Port 5037

25 of 180

adb

client

adb

server

Scan for Android devices and emulators

26 of 180

adb

client

adb

server

localhost

5555

5557

5681

27 of 180

adb

client

adb

server

localhost

5555

5557

5681

Is there a device bound here?

28 of 180

adb

client

adb

server

localhost

5555

5557

5681

Is there a device bound here?

29 of 180

adb

client

adb

server

localhost

5555

5557

5681

Is there a device bound here?

30 of 180

adb

client

adb

server

localhost

adb

daemon

5557

Android Studio

Emulator

31 of 180

adb

client

adb

server

localhost

adb

daemon

5557

Android Studio

Emulator

Open a connection to the device

32 of 180

adb

client

adb

server

USB Interface

33 of 180

adb

client

adb

server

USB Interface

/dev/…

adb

daemon

Nexus 6P (USB)

34 of 180

adb

client

adb

server

adb

daemon

Nexus 6P

adb

daemon

Network device

adb

daemon

AS Emulator

35 of 180

adb

client

adb

server

adb

daemon

Nexus 6P

adb

daemon

Network device

adb

daemon

AS Emulator

36 of 180

Some adb commands

adb tcpip

Commande pour choper les interactions utilisateurs. Grep sur les évents System (/etc/...)

Couvrir l'ensemble des commandes adb.

Send key event dig into the subject

How to grant permissions

Adb sqlite3 to open databases

Screenshot screenrecord

Port forwarding what you can do

Asis command to change the user. It is not working

"adb -s 098765432" peut s'ecrire "adb -s09876543" (sans espace)

"adb devices -l" donne beacoup plus d'info sur les devices, on peut connaitre le nom du device genymotion par exemple.

List of devices attached

192.168.56.101:5555 device product:vbox86p model:Google_Nexus_5___4_4_4___API_19___1080x1920 device:vbox86p

adb -p vbox86p pour filtrer uniquement sur les devices genymotion ou utiliser la variable d'environment ANDROID_PRODUCT_OUT (a tester)

** A PRIORI C'EST FAUX, j'ai pas reussi a trouver le bon nom a rentrer en parametre**

"adb -d" filtre uniquement les devices USB

"adb -e" filtre uniquement les emulateurs/network devices

adb -H <ip> -P <port> pour accéder a l'adb server d'un copain (utilisation pour un CI?)

adb shell == adb hell

pour adb hell, le shell est tout en rouge grace a un printf("\x1b[41;33m"); envoyé au debut

Supprimé depuis 1.0.36, voir le commit de suppression

adb logcat == adb logcat == adb longcat (give the detailed time/pid/tid/TAG/message)

Android studio uses adb longcat to get all the informations to display

adb sync

adb sideload

"adb bugreport" return all information from the device (Good for QA, intrumentation tests, etc.)

Check what is inside

adb install-multiple multi apk installation

adb install -g (grant all runtime permissions)

adb install-multiple [-lrtsdpg] <file...>

- push this package file to the device and install it

(-l: forward lock application)

(-r: replace existing application)

(-t: allow test packages)

(-s: install application on sdcard)

(-d: allow version code downgrade)

(-p: partial application install)

(-g: grant all runtime permissions)

Add more boot debug

adb root ; adb remount

and add a sys.init_loglevel = 7 to the build.prop file

37 of 180

adb tcpip 5555

>

Enable wireless debugging

adb connect <device-ip>

>

38 of 180

adb usb

>

Disable wireless debugging

39 of 180

adb tcpip 5555

>

40 of 180

adb tcpip 5555

>

ADB Server asks the Daemon to enable the network connection

“tcpip:5555”

41 of 180

adb tcpip 5555

>

ADB Server asks the Daemon to enable the network connection

The daemon sets a system property

setprop service.adb.tcp.port 5555

42 of 180

adb tcpip 5555

>

ADB Server asks the Daemon to enable the network connection

The daemon sets a system property

ADB Daemon closes itself

exit(1)

43 of 180

adb tcpip 5555

>

ADB Server asks the Daemon to enable the network connection

The daemon sets a system property

ADB Daemon closes itself

The system restarts automatically ADB Daemon

service adbd /sbin/adbd

44 of 180

adb tcpip 5555

>

ADB Server asks the Daemon to enable the network connection

The daemon sets a system property

ADB Daemon closes itself

The system restarts automatically ADB Daemon

The Daemon will read the property at start and will listen to this port

getprop service.adb.tcp.port

45 of 180

adb tcpip 5555

>

setprop service.adb.tcp.port 5555

#

stop adbd

#

start adbd

#

46 of 180

adb tcpip 5555

>

setprop persist.adb.tcp.port 5555

#

stop adbd

#

start adbd

#

Remains after reboot

47 of 180

adb devices -l

>

192.168.63.101:5555 device product:vbox86p model:myGenymotionNexus5 device:vbox86p

F5AZFG013292 device usb:336592896X product:WW_Z00A model:ASUS_Z00AD device:Z00A

HT4CNJT00728 device usb:336592896X product:volantis model:Nexus_9 device:flounder

Detailed device list

48 of 180

adb -e shell

>

Filter the type of device

Emulator or network device

adb -d shell

>

USB device

49 of 180

adb -H <ip> -P <port> devices

>

Access a remote ADB Server

50 of 180

adb -H 10.5.0.5 -P 5037 devices

>

51 of 180

adb

client

adb -H 10.5.0.5 -P 5037 devices

>

52 of 180

adb

client

adb

server

5037

adb -H 10.5.0.5 -P 5037 devices

>

Device farm server

10.5.0.5

53 of 180

adb

client

adb

server

Samsung S6

Genymotion Kitkat

Pixel 2 XL

5037

adb -H 10.5.0.5 -P 5037 devices

>

Device farm server

10.5.0.5

54 of 180

adb reverse

>

55 of 180

adb reverse

>

Backend Server

Your app

localhost

2323

8181

56 of 180

adb reverse tcp:2323 tcp:8181

>

Backend Server

Your app

localhost

2323

8181

57 of 180

adb reverse tcp:2323 tcp:8181

>

Backend Server

Your app

localhost

2323

8181

58 of 180

adb reverse

>

SecuredBackend Server

Your app

VPN

59 of 180

adb reverse

>

SecuredBackend Server

Your app

VPN

Proxy

Setting

60 of 180

adb shell settings put global http_proxy localhost:3333

>

adb reverse tcp:3333 tcp:3128

>

docker run --name squid \

--publish 127.0.0.1:3128:3128 \

--volume $HOME/squid.conf:/etc/squid3/squid.conf \

--volume /tmp/squid/cache:/var/spool/squid3 \

--volume /tmp/squid/cache:/var/log/squid3 \

sameersbn/squid:3.3.8-12

>

61 of 180

adb

>

62 of 180

adb

>

...

-p <name or path> - simple product name like 'sooner', or a

relative/absolute path to a product out

directory like 'out/target/product/sooner'.

If -p is not specified, the

ANDROID_PRODUCT_OUT environment variable is

used, which must be an absolute path.

63 of 180

adb

>

...

-p <name or path> - simple product name like 'sooner', or a

relative/absolute path to a product out

directory like 'out/target/product/sooner'.

If -p is not specified, the

ANDROID_PRODUCT_OUT environment variable is

used, which must be an absolute path.

Sooner??

64 of 180

65 of 180

Andy Rubin

Holy crap, I guess we’re not going to ship that phone.

”

“

66 of 180

The adb internals

67 of 180

adb

daemon

adb

client

adb

server

68 of 180

adb

daemon

adb

client

adb

server

C-S

S-D

69 of 180

Client-Server

70 of 180

adb shell ls

>

71 of 180

adb shell ls

>

adb

client

adb

server

72 of 180

adb shell ls

>

adb

client

adb

server

What’s your protocol version?

73 of 180

adb

client

adb

server

adb shell ls

>

What’s your protocol version?

host:version

74 of 180

adb

client

adb

server

adb shell ls

>

It’s version 36

host:version

OKAY 36

75 of 180

adb

client

adb

server

adb shell ls

>

host:version

OKAY 36

76 of 180

adb

client

adb

server

adb shell ls

>

host:transport-any

I want to talk to any kind of device

77 of 180

adb

client

adb

server

adb shell ls

>

host:transport-any

OKAY

OKAY!

78 of 180

adb

client

adb

server

adb shell ls

>

shell:ls

Please execute the shell service with the parameter “ls”

79 of 180

adb

client

adb

server

adb shell ls

>

shell:ls

“ls output”

cache

charge

config

...

80 of 180

adb

client

adb

server

adb shell ls

>

host:version

OKAY 36

host:transport-any

OKAY

shell:ls

“ls output”

81 of 180

Service

execution

Startup

Device selection

82 of 180

adb devices

>

adb server version (32) doesn't match this client (36); killing…

adb devices

>

adb server is out of date. killing...

83 of 180

adb

>

At device selection

host:transport-any

84 of 180

adb

>

adb -s <serial>

>

At device selection

adb -d

>

adb -e

>

host:transport:<serial>

host:transport-any

host:transport-usb

host:transport-local

85 of 180

adb

client

Requests

a service execution

86 of 180

adb

client

adb

server

Requests

a service execution

Executes

host services

87 of 180

adb

daemon

adb

client

adb

server

Requests

a service execution

Executes

host services

Executes

local services

88 of 180

host:version Get the ADB Server version

host:kill Kill the ADB Server

host:devices List the connected devices

host:devices-l List the connected devices with details

host:track-devices Track the list of the connected devices

host:transport* Target a device to interact with

Some host services

Here are examples of services that can be invoked. I won’t go deeper on this topic, it’s more to let you come back on the slides later if you want.

This file tries to document all requests a client can make

to the ADB server of an adbd daemon. See the OVERVIEW.TXT document

to understand what's going on here.

HOST SERVICES:

host:version

Ask the ADB server for its internal version number.

As a special exception, the server will respond with a 4-byte

hex string corresponding to its internal version number, without

any OKAY or FAIL.

host:kill

Ask the ADB server to quit immediately. This is used when the

ADB client detects that an obsolete server is running after an

upgrade.

host:devices

host:devices-l

Ask to return the list of available Android devices and their

state. devices-l includes the device paths in the state.

After the OKAY, this is followed by a 4-byte hex len,

and a string that will be dumped as-is by the client, then

the connection is closed

host:track-devices

This is a variant of host:devices which doesn't close the

connection. Instead, a new device list description is sent

each time a device is added/removed or the state of a given

device changes (hex4 + content). This allows tools like DDMS

to track the state of connected devices in real-time without

polling the server repeatedly.

host:emulator:<port>

This is a special query that is sent to the ADB server when a

new emulator starts up. <port> is a decimal number corresponding

to the emulator's ADB control port, i.e. the TCP port that the

emulator will forward automatically to the adbd daemon running

in the emulator system.

This mechanism allows the ADB server to know when new emulator

instances start.

host:transport:<serial-number>

Ask to switch the connection to the device/emulator identified by

<serial-number>. After the OKAY response, every client request will

be sent directly to the adbd daemon running on the device.

(Used to implement the -s option)

host:transport-usb

Ask to switch the connection to one device connected through USB

to the host machine. This will fail if there are more than one such

devices. (Used to implement the -d convenience option)

host:transport-local

Ask to switch the connection to one emulator connected through TCP.

This will fail if there is more than one such emulator instance

running. (Used to implement the -e convenience option)

host:transport-any

Another host:transport variant. Ask to switch the connection to

either the device or emulator connect to/running on the host.

Will fail if there is more than one such device/emulator available.

(Used when neither -s, -d or -e are provided)

host-serial:<serial-number>:<request>

This is a special form of query, where the 'host-serial:<serial-number>:'

prefix can be used to indicate that the client is asking the ADB server

for information related to a specific device. <request> can be in one

of the format described below.

host-usb:<request>

A variant of host-serial used to target the single USB device connected

to the host. This will fail if there is none or more than one.

host-local:<request>

A variant of host-serial used to target the single emulator instance

running on the host. This will fail if there is none or more than one.

host:<request>

When asking for information related to a device, 'host:' can also be

interpreted as 'any single device or emulator connected to/running on

the host'.

<host-prefix>:get-product

XXX

<host-prefix>:get-serialno

Returns the serial number of the corresponding device/emulator.

Note that emulator serial numbers are of the form "emulator-5554"

<host-prefix>:get-devpath

Returns the device path of the corresponding device/emulator.

<host-prefix>:get-state

Returns the state of a given device as a string.

<host-prefix>:forward:<local>;<remote>

Asks the ADB server to forward local connections from <local>

to the <remote> address on a given device.

There, <host-prefix> can be one of the

host-serial/host-usb/host-local/host prefixes as described previously

and indicates which device/emulator to target.

the format of <local> is one of:

tcp:<port> -> TCP connection on localhost:<port>

local:<path> -> Unix local domain socket on <path>

the format of <remote> is one of:

tcp:<port> -> TCP localhost:<port> on device

local:<path> -> Unix local domain socket on device

jdwp:<pid> -> JDWP thread on VM process <pid>

or even any one of the local services described below.

<host-prefix>:forward:norebind:<local>;<remote>

Same as <host-prefix>:forward:<local>;<remote> except that it will

fail it there is already a forward connection from <local>.

Used to implement 'adb forward --no-rebind <local> <remote>'

<host-prefix>:killforward:<local>

Remove any existing forward local connection from <local>.

This is used to implement 'adb forward --remove <local>'

<host-prefix>:killforward-all

Remove all forward network connections.

This is used to implement 'adb forward --remove-all'.

<host-prefix>:list-forward

List all existing forward connections from this server.

This returns something that looks like the following:

<hex4>: The length of the payload, as 4 hexadecimal chars.

<payload>: A series of lines of the following format:

<serial> " " <local> " " <remote> "\n"

Where <serial> is a device serial number.

<local> is the host-specific endpoint (e.g. tcp:9000).

<remote> is the device-specific endpoint.

Used to implement 'adb forward --list'.

89 of 180

shell:<command> Run a shell command

shell: Open an interactive shell session

remount: Remount the filesystem in r-w mode

framebuffer: Get framebuffer snapshots

jdwp:<pid> Connects to the JDWP thread of a process

track-jdwp Track the list of all processes in debug

sync: Specific service used for push & pull

Some local services

Here are other examples. You see the framebuffer service used to get screenshots, jdwp is used by your IDE to connect the debugger to your application, sync is a dedicated service for push and pull commands, etc.

LOCAL SERVICES:

All the queries below assumed that you already switched the transport

to a real device, or that you have used a query prefix as described

above.

shell:command arg1 arg2 ...

Run 'command arg1 arg2 ...' in a shell on the device, and return

its output and error streams. Note that arguments must be separated

by spaces. If an argument contains a space, it must be quoted with

double-quotes. Arguments cannot contain double quotes or things

will go very wrong.

Note that this is the non-interactive version of "adb shell"

shell:

Start an interactive shell session on the device. Redirect

stdin/stdout/stderr as appropriate. Note that the ADB server uses

this to implement "adb shell", but will also cook the input before

sending it to the device (see interactive_shell() in commandline.c)

remount:

Ask adbd to remount the device's filesystem in read-write mode,

instead of read-only. This is usually necessary before performing

an "adb sync" or "adb push" request.

This request may not succeed on certain builds which do not allow

that.

dev:<path>

Opens a device file and connects the client directly to it for

read/write purposes. Useful for debugging, but may require special

privileges and thus may not run on all devices. <path> is a full

path from the root of the filesystem.

tcp:<port>

Tries to connect to tcp port <port> on localhost.

tcp:<port>:<server-name>

Tries to connect to tcp port <port> on machine <server-name> from

the device. This can be useful to debug some networking/proxy

issues that can only be revealed on the device itself.

local:<path>

Tries to connect to a Unix domain socket <path> on the device

localreserved:<path>

localabstract:<path>

localfilesystem:<path>

Variants of local:<path> that are used to access other Android

socket namespaces.

framebuffer:

This service is used to send snapshots of the framebuffer to a client.

It requires sufficient privileges but works as follow:

After the OKAY, the service sends 16-byte binary structure

containing the following fields (little-endian format):

depth: uint32_t: framebuffer depth

size: uint32_t: framebuffer size in bytes

width: uint32_t: framebuffer width in pixels

height: uint32_t: framebuffer height in pixels

With the current implementation, depth is always 16, and

size is always width*height*2

Then, each time the client wants a snapshot, it should send

one byte through the channel, which will trigger the service

to send it 'size' bytes of framebuffer data.

If the adbd daemon doesn't have sufficient privileges to open

the framebuffer device, the connection is simply closed immediately.

jdwp:<pid>

Connects to the JDWP thread running in the VM of process <pid>.

track-jdwp

This is used to send the list of JDWP pids periodically to the client.

The format of the returned data is the following:

<hex4>: the length of all content as a 4-char hexadecimal string

<content>: a series of ASCII lines of the following format:

<pid> "\n"

This service is used by DDMS to know which debuggable processes are running

on the device/emulator.

Note that there is no single-shot service to retrieve the list only once.

sync:

This starts the file synchronization service, used to implement "adb push"

and "adb pull". Since this service is pretty complex, it will be detailed

in a companion document named SYNC.TXT

reverse:<forward-command>

This implements the 'adb reverse' feature, i.e. the ability to reverse

socket connections from a device to the host. <forward-command> is one

of the forwarding commands that are described above, as in:

list-forward

forward:<local>;<remote>

forward:norebind:<local>;<remote>

killforward-all

killforward:<local>

Note that in this case, <local> corresponds to the socket on the device

and <remote> corresponds to the socket on the host.

The output of reverse:list-forward is the same as host:list-forward

except that <serial> will be just 'host'.

90 of 180

Server-Daemon

91 of 180

What the message looks like?

92 of 180

93 of 180

amessage

94 of 180

amessage

data

95 of 180

amessage

data

struct amessage {

unsigned command; /* command identifier constant */

unsigned arg0; /* first argument */

unsigned arg1; /* second argument */

unsigned data_length; /* length of payload (0 is allowed) */

unsigned data_crc32; /* crc32 of data payload */

unsigned magic; /* command ^ 0xffffffff */

};

96 of 180

amessage

data

struct amessage {

unsigned command; /* command identifier constant */

unsigned arg0; /* first argument */

unsigned arg1; /* second argument */

unsigned data_length; /* length of payload (0 is allowed) */

unsigned data_crc32; /* crc32 of data payload */

unsigned magic; /* command ^ 0xffffffff */

};

The verb of the action

97 of 180

amessage

data

struct amessage {

unsigned command; /* command identifier constant */

unsigned arg0; /* first argument */

unsigned arg1; /* second argument */

unsigned data_length; /* length of payload (0 is allowed) */

unsigned data_crc32; /* crc32 of data payload */

unsigned magic; /* command ^ 0xffffffff */

};

The arguments of the action

98 of 180

amessage

data

struct amessage {

unsigned command; /* command identifier constant */

unsigned arg0; /* first argument */

unsigned arg1; /* second argument */

unsigned data_length; /* length of payload (0 is allowed) */

unsigned data_crc32; /* crc32 of data payload */

unsigned magic; /* command ^ 0xffffffff */

};

The size of the data

99 of 180

adb connect <ip:port>

>

100 of 180

adb

daemon

adb

server

adb connect <ip:port>

>

101 of 180

adb

daemon

adb

server

adb connect <ip:port>

>

CNXN, 0x01000000, 256K

102 of 180

adb

daemon

adb

server

adb connect <ip:port>

>

CNXN, 0x01000000, 256K

Command

Arg 1

Arg 2

103 of 180

adb

daemon

adb

server

adb connect <ip:port>

>

CNXN, 0x01000000, 256K

CONNECT command

104 of 180

adb

daemon

adb

server

adb connect <ip:port>

>

CNXN, 0x01000000, 256K

Protocol version

105 of 180

adb

daemon

adb

server

adb connect <ip:port>

>

CNXN, 0x01000000, 256K

Max payload size

106 of 180

adb

daemon

adb

server

adb connect <ip:port>

>

CNXN, 0x01000000, 256K

device::ro.product...

107 of 180

adb

daemon

adb

server

adb connect <ip:port>

>

CNXN, 0x01000000, 256K

device::ro.product...

Command

Arg 1

Arg 2

108 of 180

adb

daemon

adb

server

adb connect <ip:port>

>

CNXN, 0x01000000, 256K

device::ro.product...

Data

109 of 180

adb

daemon

adb

server

adb connect <ip:port>

>

CNXN, 0x01000000, 256K

device::ro.product...

Device identity string

110 of 180

adb shell ls

>

111 of 180

adb

daemon

adb

server

adb shell ls

>

112 of 180

adb

daemon

adb

server

adb shell ls

>

OPEN, server-id, 0, shell:ls

113 of 180

adb

daemon

adb

server

adb shell ls

>

OPEN, server-id, 0, shell:ls

Command

Arg1

Arg2

Data

114 of 180

adb

daemon

adb

server

adb shell ls

>

OPEN, server-id, 0, shell:ls

The ADB service to execute

115 of 180

adb

daemon

adb

server

adb shell ls

>

OPEN, server-id, 0, shell:ls

OKAY, daemon-id, server-id

116 of 180

adb

daemon

adb

server

adb shell ls

>

OPEN, server-id, 0, shell:ls

OKAY, daemon-id, server-id

WRITE, daemon-id, server-id

“DATA”

117 of 180

adb

daemon

adb

server

adb shell ls

>

OPEN, server-id, 0, shell:ls

OKAY, daemon-id, server-id

WRITE, daemon-id, server-id

“DATA”

OKAY, server-id, daemon-id

118 of 180

adb

daemon

adb

server

adb shell ls

>

OPEN, server-id, 0, shell:ls

OKAY, daemon-id, server-id

WRITE, daemon-id, server-id

“DATA”

OKAY, server-id, daemon-id

WRITE, daemon-id, server-id

“DATA”

CLOSE, daemon-id, server-id

119 of 180

adb

daemon

adb

server

adb shell ls

>

OPEN, server-id, 0, shell:ls

OKAY, daemon-id, server-id

WRITE, daemon-id, server-id

“DATA”

OKAY, server-id, daemon-id

WRITE, daemon-id, server-id

“DATA”

OKAY, server-id, daemon-id

CLOSE, server-id, daemon-id

CLOSE, daemon-id, server-id

120 of 180

Why ADB is

now faster?

121 of 180

122 of 180

123 of 180

124 of 180

data (256KB)

amessage

Now

125 of 180

data (256KB)

amessage

data (4KB)

Now

Before

126 of 180

adb

daemon

adb

server

WRITE, “256KB DATA”

OKAY

WRITE, “256KB DATA”

127 of 180

adb

daemon

adb

server

WRITE, “256KB DATA”

OKAY

WRITE, “256KB DATA”

OKAY

WRITE, “256KB DATA”

OKAY

WRITE, “256KB DATA”

OKAY

WRITE, “256KB DATA”

OKAY

WRITE, “256KB DATA”

OKAY

WRITE, “256KB DATA”

OKAY

WRITE, “256KB DATA”

OKAY

WRITE, “256KB DATA”

OKAY

WRITE, “256KB DATA”

OKAY

WRITE, “256KB DATA”

OKAY

WRITE, “256KB DATA”

OKAY

WRITE, “256KB DATA”

OKAY

WRITE, “256KB DATA”

OKAY

WRITE, “256KB DATA”

OKAY

WRITE, “256KB DATA”

OKAY

WRITE, “256KB DATA”

OKAY

WRITE, “256KB DATA”

OKAY

WRITE, “256KB DATA”

OKAY

WRITE, “256KB DATA”

OKAY

WRITE, “256KB DATA”

OKAY

WRITE, “256KB DATA”

OKAY

WRITE, “256KB DATA”

OKAY

WRITE, “256KB DATA”

OKAY

WRITE, “256KB DATA”

OKAY

WRITE, “256KB DATA”

OKAY

WRITE, “256KB DATA”

OKAY

WRITE, “256KB DATA”

OKAY

WRITE, “256KB DATA”

OKAY

WRITE, “256KB DATA”

OKAY

WRITE, “256KB DATA”

OKAY

WRITE, “256KB DATA”

OKAY

WRITE, “256KB DATA”

OKAY

WRITE, “256KB DATA”

OKAY

WRITE, “256KB DATA”

OKAY

WRITE, “256KB DATA”

OKAY

WRITE, “256KB DATA”

OKAY

WRITE, “256KB DATA”

OKAY

WRITE, “256KB DATA”

OKAY

WRITE, “256KB DATA”

OKAY

WRITE, “256KB DATA”

OKAY

WRITE, “256KB DATA”

OKAY

WRITE, “256KB DATA”

OKAY

WRITE, “256KB DATA”

OKAY

WRITE, “256KB DATA”

OKAY

WRITE, “256KB DATA”

OKAY

WRITE, “256KB DATA”

OKAY

WRITE, “256KB DATA”

OKAY

WRITE, “256KB DATA”

OKAY

WRITE, “256KB DATA”

OKAY

WRITE, “256KB DATA”

OKAY

WRITE, “256KB DATA”

OKAY

WRITE, “256KB DATA”

OKAY

WRITE, “256KB DATA”

OKAY

WRITE, “256KB DATA”

OKAY

WRITE, “256KB DATA”

OKAY

WRITE, “256KB DATA”

OKAY

WRITE, “256KB DATA”

OKAY

WRITE, “256KB DATA”

OKAY

WRITE, “256KB DATA”

OKAY

WRITE, “256KB DATA”

OKAY

WRITE, “256KB DATA”

OKAY

WRITE, “256KB DATA”

OKAY

WRITE, “256KB DATA”

OKAY

WRITE, “256KB DATA”

OKAY

WRITE, “256KB DATA”

OKAY

WRITE, “256KB DATA”

OKAY

WRITE, “256KB DATA”

OKAY

WRITE, “256KB DATA”

OKAY

WRITE, “256KB DATA”

OKAY

WRITE, “256KB DATA”

OKAY

WRITE, “256KB DATA”

OKAY

WRITE, “256KB DATA”

128 of 180

Develop on the ADB project

129 of 180

Configure your environment

Fetch the source code

Make it!

Build your own ADB

130 of 180

repo init \

-u https://android.googlesource.com/platform/manifest \

-b master

repo sync -c --force-sync

source build/envsetup.sh

lunch

make -j24 adb

>

131 of 180

adbd

adb

libadb

132 of 180

The client host binary

Bundle in the Android SDK

The one you use everyday

Output path

./out/host/<your-platform>/bin/adb

adb

133 of 180

The device’s daemon binary

Bundle in the Android OS

The one you use everyday

Maybe without noticing

adbd

134 of 180

Adb static library

Contains the common files

libadb

135 of 180

Originally written in

C

136 of 180

Aimed to be written in

C++

137 of 180

Actually written in

C+

138 of 180

Actually written in

C~++

139 of 180

Actually written in

C++--

140 of 180

ADB sources are ubiquitous

141 of 180

ADB sources are ubiquitous

142 of 180

ADB sources are ubiquitous

adb

daemon

adb

client

adb

server

143 of 180

ADB sources are ubiquitous

adb

daemon

adb

client

adb

server

144 of 180

adb

client

adb

server

adb

daemon

Nexus 6P

adb

daemon

Network device

adb

daemon

AS Emulator

adb

client

adb

client

145 of 180

#if ADB_HOST

...

#else // !ADB_HOST

...

#endif // ADB_HOST

146 of 180

#if ADB_HOST

...

#else // !ADB_HOST

...

#endif // ADB_HOST

62 times

147 of 180

#if defined(_WIN32)

...

#endif

148 of 180

#if defined(_WIN32)

...

#endif

51 times

149 of 180

adb kill-server

>

export ADB_TRACE=adb

>

Debug ADB

adb start-server

>

150 of 180

adb devices

>

...

adb I 39295 1708488 adb_client.cpp:135] _adb_connect:host:devices

adb I 39295 1708488 adb_io.cpp:99] writex: fd=3 len=16 30303063686f73743a64657669636573 000chost:devices

...

ADB Client logs

tail -f /tmp/adb.log Linux

tail -f $TMPDIR/adb.*.log Mac

ADB Server logs

>

151 of 180

ADB &

The Android Dev Tools

Android Studio

The UI

adb longcat

adb devices -l

Instant Run

How Instant run uses adb?

https://medium.com/google-developers/instant-run-how-does-it-work-294a1633367f#.6x2u16qxm

https://speakerdeck.com/atsushieno/how-instant-run-works-at-droidkaigi2016

The debugger

How debugger uses adb?

ddmlib

A java ADB client library.

Starts the adb server like the client adb -P 5035 start-server on a dedicated process

Then it connects to the server started, it forges the adb client request the same way adb does it and send these commands to the server.

Interesting point: ADB binary will only be compatible with the last version of the adb server while this library is maintained by google and supports all adb versions since 1.0.20

https://android.googlesource.com/platform/tools/base/+/studio-master-dev/ddmlib/src/main/java/com/android/ddmlib/AndroidDebugBridge.java#586

Instruction to get the code here: http://tools.android.com/build

Publicly maintained by Google.

Available here: https://bintray.com/android/android-tools/com.android.tools.ddms.ddmlib

Example using the lib: https://github.com/Ladicek/ddmlib-demo

ddmlib install

// Installing multiple APK's is perfomed as follows:

// # First we create a install session passing in the total size of all APKs

// $ pm install-create -S <total_size>

// Success: [integer-session-id] # error if session-id < 0

// # Then for each APK, we perform the following. A unique id per APK is generated

// # as <index>_<name>, the - at the end means that the APK is streamed via stdin

// $ pm install-write -S <session-id> <per_apk_unique_id> -

// # Finally, we close the session

// $ pm install-commit <session-id> (or)

// $ pm install-abandon <session-id>

adb install will not use “pm” anymore from Nougat. It uses “cmd package” instead. What are the differences? Apparently it is faster.

But it is not used by ddmlib for now: https://code.google.com/p/android/issues/detail?id=217002&q=component%3DTools%20-has%3Amilestone%20-has%3Afixit%20label%3ASubcomponent-Tools-deployment&colspec=ID%20Status%20Priority%20Owner%20Summary%20Stars%20Reporter%20Opened

When you are on instant run you switch to android monitor sometimes you have tio kill adb server

Cheeva answer: Android Studio and eclipse are using libddms (or libddm) and this lib opens sockets to the native and java debugger servers. When you open Android Monitor the processes are supposed to close connections and sometimes race condition happen and it is not possible to reconnect. Adb kill-server will do the job.

Debug ports are open only on debug process

Future is that they open connection only to needed process

Gradle

Connected Tests : How the tests are launched, how the result are gathered ?

Compile 2 APKs (one to-be-tested and one to instrument the tested apk) > Install the both APKs using ddmlib > run adb shell command “am instrument -w -r -e argKey argValue ...” (coverage true, coverageFile /data/data/<pkg>/coverage.ec, ...) > Parse the result from ADB > generate result tree > generate the HTML report

Gradle plugin uses ddmlib to communicate with adb too.

You want to see the adb commands lunched by your build system? Add these line to your build.gradle:

import com.android.ddmlib.DdmPreferences

DdmPreferences.setLogLevel("verbose")

Chris Warrington cmw@google.com

De la part de Jedo, poser les questions sur le plugin gradle et la création des résultats de test run a partir des outputs.

adbOptions {� timeOutInMs 5000 // 5 seconds in ms.

installOptions “-g”, “-r”�}�

Genymotion

AdbTunnel?

Structure of the project (local computer/remote device/adb)
multi user connection -> multiplexing
explain the id swapping process
potential improvements

Adb auto connection

Our player controls the ADB connection of the Android OS
It connects the device when we get it’s ip address
then it opens a shell prompt
when the shell prompt exists we know the adb connection is lost

Vysor

Contains an adb server

Can communicate with an already running adb server, including usb access

opens connection on both side:

tcp4 0 0 localhost.5037 localhost.55092 ESTABLISHED

tcp4 0 0 localhost.55092 localhost.5037 ESTABLISHED

tcp4 0 0 localhost.5037 localhost.55085 ESTABLISHED

tcp4 0 0 localhost.55085 localhost.5037 ESTABLISHED

Inject

JRebel Android

Port forwarding

Class injection

Hierarchy Viewer

Port forwarding?

CTS

Comment les outils de test notamment utilisent adb. Ouverture d'un tty ? Voir avec Sam.

-t -T to enable tty or not. More close to ssh way of using

Vi should be working better with N because of this improvements

We should update our cts before running with Master branch of adb as they should basically been updated according to these modifications

152 of 180

Android Studio

Get the source code

ddmlib

A java ADB client library.

Starts the adb server like the client adb -P 5035 start-server on a dedicated process

Then it connects to the server started, it forges the adb client request the same way adb does it and send these commands to the server.

Interesting point: ADB binary will only be compatible with the last version of the adb server while this library is maintained by google and supports all adb versions since 1.0.20

https://android.googlesource.com/platform/tools/base/+/studio-master-dev/ddmlib/src/main/java/com/android/ddmlib/AndroidDebugBridge.java#586

Instruction to get the code here: http://tools.android.com/build

Publicly maintained by Google.

Available here: https://bintray.com/android/android-tools/com.android.tools.ddms.ddmlib

Example using the lib: https://github.com/Ladicek/ddmlib-demo

ddmlib install

// Installing multiple APK's is perfomed as follows:

// # First we create a install session passing in the total size of all APKs

// $ pm install-create -S <total_size>

// Success: [integer-session-id] # error if session-id < 0

// # Then for each APK, we perform the following. A unique id per APK is generated

// # as <index>_<name>, the - at the end means that the APK is streamed via stdin

// $ pm install-write -S <session-id> <per_apk_unique_id> -

// # Finally, we close the session

// $ pm install-commit <session-id> (or)

// $ pm install-abandon <session-id>

adb install will not use “pm” anymore from Nougat. It uses “cmd package” instead. What are the differences? Apparently it is faster.

But it is not used by ddmlib for now: https://code.google.com/p/android/issues/detail?id=217002&q=component%3DTools%20-has%3Amilestone%20-has%3Afixit%20label%3ASubcomponent-Tools-deployment&colspec=ID%20Status%20Priority%20Owner%20Summary%20Stars%20Reporter%20Opened

When you are on instant run you switch to android monitor sometimes you have tio kill adb server

Cheeva answer: Android Studio and eclipse are using libddms (or libddm) and this lib opens sockets to the native and java debugger servers. When you open Android Monitor the processes are supposed to close connections and sometimes race condition happen and it is not possible to reconnect. Adb kill-server will do the job.

Debug ports are open only on debug process

Future is that they open connection only to needed process

The UI

adb longcat

logcat -v long

adb devices -l

Instant Run

How Instant run uses adb?

https://medium.com/google-developers/instant-run-how-does-it-work-294a1633367f#.6x2u16qxm

https://speakerdeck.com/atsushieno/how-instant-run-works-at-droidkaigi2016

The debugger

How debugger uses adb?

Hierarchy Viewer

Port forwarding?

153 of 180

repo init \

-u https://android.googlesource.com/platform/manifest \

-b studio-master-dev

repo sync -c --force-sync

cd ./tools/idea

>

Get the source code

154 of 180

Android Studio

does not use

adb

155 of 180

Android Studio

does not use

adb

…almost

156 of 180

Android Studio

uses

ddmlib

157 of 180

A Java library

Behaves as an ADB Client

Part of the AOSP

tools/base/ddmlib

ddmlib

158 of 180

ddmlib

does not use

adb

159 of 180

ddmlib

does not use

adb

…almost

160 of 180

ddmlib

adb

server

adb

daemon

Nexus 6P

adb

daemon

Network device

adb

daemon

AS Emulator

5037

161 of 180

What’s the difference between ddmlib and adb binary?

162 of 180

What’s the difference between ddmlib and adb binary?

one of

s

163 of 180

What’s the difference between ddmlib and adb binary?

one of

s

The backward compatibility

164 of 180

adb binary

ddmlib

Latest version only

From ADB 1.0.20

165 of 180

adb binary

ddmlib

Latest version only

From ADB 1.0.20

(October 2008)

166 of 180

Maintained by Google

Open source

Many thousands of daily users

Still need the adb binary

ddmlib as library

167 of 180

Maintained by Google

Open source

Many thousands of daily users

Still need the adb binary

Possibly a good tool for your project

ddmlib as library

168 of 180

repositories {

google()

}

dependencies {

implementation 'com.android.tools.ddms:ddmlib:26.1.0'

}

169 of 180

The Android Gradle Plugin

Gradle

when adb is it used?

When interacting with Android devices -> Installation, instrumented tests, get the ABIs of the connected devices (to install the good version)

It uses the ConnectedDeviceProvider class to wrap the AndroidDebugBridge from ddmlib

Connected Tests : How the tests are launched, how the result are gathered ?

Compile 2 APKs (one to-be-tested and one to instrument the tested apk) > Install the both APKs using ddmlib > run adb shell command “am instrument -w -r -e argKey argValue ...” (coverage true, coverageFile /data/data/<pkg>/coverage.ec, ...) > Parse the result from ADB > generate result tree > generate the HTML report

Gradle plugin uses ddmlib to communicate with adb too.

You want to see the adb commands lunched by your build system? Add these line to your build.gradle:

import com.android.ddmlib.DdmPreferences

DdmPreferences.setLogLevel("verbose")

Chris Warrington cmw@google.com

De la part de Jedo, poser les questions sur le plugin gradle et la création des résultats de test run a partir des outputs.

adbOptions {� timeOutInMs 5000 // 5 seconds in ms.

installOptions “-g”, “-r”�}

170 of 180

repo init \

-u https://android.googlesource.com/platform/manifest \

-b gradle_3.0.0

repo sync -c --force-sync

cd ./tools/base/build-system/

>

Get the source code

171 of 180

The Android Gradle Plugin

uses

ddmlib

172 of 180

The Android Gradle Plugin

uses

ddmlib

Like Android Studio

173 of 180

The Android Gradle Plugin

uses

ddmlib

How does

?

174 of 180

When there is an interaction with a device

Install an APK

Launch instrumented tests

Get devices information

175 of 180

Manages the list of connected devices

Interacts with the device through ddmlib

DeviceProvider

ConnectedDevice

176 of 180

gradlew <yourTask> --debug

>

Make ddmlib verbose from the build.gradle

import com.android.ddmlib.DdmPreferences

DdmPreferences.setLogLevel("verbose")

You want to see the adb commands launched by your build system? Add these line to your build.gradle:
import com.android.ddmlib.DdmPreferences
DdmPreferences.setLogLevel("verbose")

V/ddms: execute: running am instrument -w -r com.genymotion.binocle.test/android.test.InstrumentationTestRunner

V/InstrumentationResultParser: INSTRUMENTATION_STATUS: numtests=5

V/InstrumentationResultParser: INSTRUMENTATION_STATUS: stream=

V/InstrumentationResultParser: com.genymotion.binocle.test.TestBattery:

V/InstrumentationResultParser: INSTRUMENTATION_STATUS: id=InstrumentationTestRunner

V/InstrumentationResultParser: INSTRUMENTATION_STATUS: test=testBatteryWarning

V/InstrumentationResultParser: INSTRUMENTATION_STATUS: class=com.genymotion.binocle.test.TestBattery

V/InstrumentationResultParser: INSTRUMENTATION_STATUS: current=1

Starting 5 tests on nexus5 - 5.1

V/InstrumentationResultParser: INSTRUMENTATION_STATUS_CODE: 1

V/InstrumentationResultParser: INSTRUMENTATION_STATUS: numtests=5

V/InstrumentationResultParser: INSTRUMENTATION_STATUS: stream=.

V/InstrumentationResultParser: INSTRUMENTATION_STATUS: id=InstrumentationTestRunner

V/InstrumentationResultParser: INSTRUMENTATION_STATUS: test=testBatteryWarning

V/InstrumentationResultParser: INSTRUMENTATION_STATUS: class=com.genymotion.binocle.test.TestBattery

V/InstrumentationResultParser: INSTRUMENTATION_STATUS: current=1

com.genymotion.binocle.test.TestBattery > testBatteryWarning[nexus5 - 5.1] [32mSUCCESS [0m

177 of 180

Make ddmlib verbose from the build.gradle

V/ddms: execute: running pm install-create -r -S 945819

V/ddms: execute: running pm install-write -S 945819 26732 0_binocle-flavor1-debug -

V/ddms: execute: running pm install-commit 1802739235

…

V/ddms: execute: running am instrument -w -r com.genymotion.binocle.test/android.test.InstrumentationTestRunner

V/InstrumentationResultParser: INSTRUMENTATION_STATUS: numtests=5

V/InstrumentationResultParser: INSTRUMENTATION_STATUS: stream=

V/InstrumentationResultParser: com.genymotion.binocle.test.TestBattery:

V/InstrumentationResultParser: INSTRUMENTATION_STATUS: id=InstrumentationTestRunner

V/InstrumentationResultParser: INSTRUMENTATION_STATUS: test=testBatteryWarning

…

You want to see the adb commands launched by your build system? Add these line to your build.gradle:
import com.android.ddmlib.DdmPreferences
DdmPreferences.setLogLevel("verbose")

01:31:15.988 [QUIET] [system.out] 01:31:15 D/ddms: Checking '/Users/eyal/Library/Android/sdk/platform-tools/adb version'

01:31:16.001 [QUIET] [system.out] 01:31:16 D/adb: Android Debug Bridge version 1.0.36

01:31:16.002 [QUIET] [system.out] 01:31:16 D/adb: Revision e02fe72a18c3-android

01:31:16.003 [QUIET] [system.out] 01:31:16 D/ddms: Launching '/Users/eyal/Library/Android/sdk/platform-tools/adb,start-server' to ensure ADB is running.

01:31:16.022 [QUIET] [system.out] 01:31:16 D/ddms: '/Users/eyal/Library/Android/sdk/platform-tools/adb,start-server' succeeded

01:31:16.034 [QUIET] [system.out] 01:31:16 D/DeviceMonitor: Opening adb connection

01:31:16.035 [QUIET] [system.out] 01:31:16 D/DeviceMonitor: Connecting to adb for Device List Monitoring...

01:31:16.047 [QUIET] [system.out] 01:31:16 D/DeviceMonitor: Connected to adb for device monitoring

01:31:16.106 [QUIET] [system.out] 01:31:16 V/ddms: execute: running getprop

01:31:16.153 [QUIET] [system.out] 01:31:16 V/ddms: execute 'getprop' on '192.168.63.101:5555' : EOF hit. Read: -1

01:31:16.157 [QUIET] [system.out] 01:31:16 V/ddms: execute: returning

01:31:16.163 [QUIET] [system.out] 01:31:16 V/ddms: execute: running echo $EXTERNAL_STORAGE

01:31:16.168 [QUIET] [system.out] 01:31:16 V/ddms: execute 'echo $EXTERNAL_STORAGE' on '192.168.63.101:5555' : EOF hit. Read: -1

01:31:16.169 [QUIET] [system.out] 01:31:16 V/ddms: execute: returning

01:31:16.170 [QUIET] [system.out] 01:31:16 V/ddms: execute: running echo $ANDROID_DATA

01:31:16.176 [QUIET] [system.out] 01:31:16 V/ddms: execute 'echo $ANDROID_DATA' on '192.168.63.101:5555' : EOF hit. Read: -1

01:31:16.177 [QUIET] [system.out] 01:31:16 V/ddms: execute: returning

01:31:16.182 [QUIET] [system.out] 01:31:16 V/ddms: execute: running echo $ANDROID_ROOT

01:31:16.211 [QUIET] [system.out] 01:31:16 V/ddms: execute 'echo $ANDROID_ROOT' on '192.168.63.101:5555' : EOF hit. Read: -1

01:31:16.212 [QUIET] [system.out] 01:31:16 V/ddms: execute: returning

01:31:17.074 [DEBUG] [org.gradle.api.Project] DeviceConnector 'nexus5 - 5.1': installing /Users/eyal/genymotion/gradle-plugin/genymotion-gradle-plugin/samples/genymotion-binocle/binocle/build/outputs/apk/binocle-flavor1-debug.apk

01:31:17.078 [QUIET] [system.out] 01:31:17 D//Users/eyal/genymotion/gradle-plugin/genymotion-gradle-plugin/samples/genymotion-binocle/binocle/build/outputs/apk/binocle-flavor1-debug.apk: Uploading main /Users/eyal/genymotion/gradle-plugin/genymotion-gradle-plugin/samples/genymotion-binocle/binocle/build/outputs/apk/binocle-flavor1-debug.apk and /Users/eyal/genymotion/gradle-plugin/genymotion-gradle-plugin/samples/genymotion-binocle/binocle/build/outputs/apk/binocle-flavor1-debug.apk split APKs onto device '192.168.63.101:5555'

01:31:17.079 [QUIET] [system.out] 01:31:17 V/ddms: execute: running pm install-create -r -S 945819

01:31:17.202 [QUIET] [system.out] 01:31:17 V/ddms: execute 'pm install-create -r -S 945819' on '192.168.63.101:5555' : EOF hit. Read: -1

01:31:17.203 [QUIET] [system.out] 01:31:17 V/ddms: execute: returning

01:31:17.204 [QUIET] [system.out] 01:31:17 D//Users/eyal/genymotion/gradle-plugin/genymotion-gradle-plugin/samples/genymotion-binocle/binocle/build/outputs/apk/binocle-flavor1-debug.apk: Established session id=1802739235

01:31:17.204 [QUIET] [system.out] 01:31:17 D/1802739235: Uploading APK /Users/eyal/genymotion/gradle-plugin/genymotion-gradle-plugin/samples/genymotion-binocle/binocle/build/outputs/apk/binocle-flavor1-debug.apk

01:31:17.205 [QUIET] [system.out] 01:31:17 D/1802739235: Executing : pm install-write -S 945819 1802739235 0_binocle-flavor1-debug -

01:31:17.207 [QUIET] [system.out] 01:31:17 V/ddms: execute: running pm install-write -S 945819 1802739235 0_binocle-flavor1-debug -

01:31:17.453 [QUIET] [system.out] 01:31:17 V/ddms: execute 'pm install-write -S 945819 1802739235 0_binocle-flavor1-debug -' on '192.168.63.101:5555' : EOF hit. Read: -1

01:31:17.453 [QUIET] [system.out] 01:31:17 V/ddms: execute: returning

01:31:17.453 [QUIET] [system.out] 01:31:17 D/1802739235: Successfully uploaded binocle-flavor1-debug.apk

01:31:17.454 [QUIET] [system.out] 01:31:17 V/ddms: execute: running pm install-commit 1802739235

01:31:18.462 [QUIET] [system.out] 01:31:18 V/ddms: execute 'pm install-commit 1802739235' on '192.168.63.101:5555' : EOF hit. Read: -1

01:31:18.463 [QUIET] [system.out] 01:31:18 V/ddms: execute: returning

01:31:18.463 [DEBUG] [org.gradle.api.Project] DeviceConnector 'nexus5 - 5.1': installing /Users/eyal/genymotion/gradle-plugin/genymotion-gradle-plugin/samples/genymotion-binocle/binocle/build/outputs/apk/binocle-flavor1-debug-test-unaligned.apk

01:31:18.464 [QUIET] [system.out] 01:31:18 D/binocle-flavor1-debug-test-unaligned.apk: Uploading binocle-flavor1-debug-test-unaligned.apk onto device '192.168.63.101:5555'

01:31:18.479 [QUIET] [system.out] 01:31:18 D/Device: Uploading file onto device '192.168.63.101:5555'

01:31:18.488 [QUIET] [system.out] 01:31:18 V/ddms: execute: running pm install -r "/data/local/tmp/binocle-flavor1-debug-test-unaligned.apk"

01:31:18.829 [QUIET] [system.out] 01:31:18 V/ddms: execute 'pm install -r "/data/local/tmp/binocle-flavor1-debug-test-unaligned.apk"' on '192.168.63.101:5555' : EOF hit. Read: -1

01:31:18.830 [QUIET] [system.out] 01:31:18 V/ddms: execute: returning

01:31:18.831 [QUIET] [system.out] 01:31:18 V/ddms: execute: running rm "/data/local/tmp/binocle-flavor1-debug-test-unaligned.apk"

01:31:18.873 [QUIET] [system.out] 01:31:18 V/ddms: execute 'rm "/data/local/tmp/binocle-flavor1-debug-test-unaligned.apk"' on '192.168.63.101:5555' : EOF hit. Read: -1

01:31:18.873 [QUIET] [system.out] 01:31:18 V/ddms: execute: returning

01:31:18.876 [QUIET] [system.out] 01:31:18 I/RemoteAndroidTest: Running am instrument -w -r com.genymotion.binocle.test/android.test.InstrumentationTestRunner on nexus5 - 5.1

01:31:18.877 [QUIET] [system.out] 01:31:18 V/ddms: execute: running am instrument -w -r com.genymotion.binocle.test/android.test.InstrumentationTestRunner

178 of 180

Inject ADB options from the build.gradle

for all the tasks

android.adbOptions {

timeOutInMs 5000 // 5 seconds

installOptions “-g”

}

adbOptions {� timeOutInMs 5000 // 5 seconds in ms.

installOptions “-g”, “-r”�}�

android.testVariants.all { variant ->

String flavorName = variant.productFlavors[0]?.name

if (flavorName?.startsWith(DEVICES_BATCH_PREFIX)) {

tasks.instrumentationTest.dependsOn variant.connectedInstrumentTest

/**

* If the previous test run raised an error, we want to force the next run to be executed

* despite everything. So each time, the tests are executed on all devices

**/

variant.connectedInstrumentTest.ignoreFailures = true

}

/**

* We add the "-g" option to the APKs installation command to grant all the permissions to our

* app and avoid interrupting the UI workflow with permissions popups.

* This flavor must run only on Android 6.0 and above devices because the -g option is

* not supported below

**/

if (flavorName?.startsWith(DEVICES_BATCH_WITH_GRANT_PREFIX)) {

variant.connectedInstrumentTest.installOptions = ["-g"]

}

179 of 180

Inject ADB options from the build.gradle

for a single task

android.testVariants.all { variant ->

variant.connectedInstrumentTest.installOptions = ["-g"]

}

adbOptions {� timeOutInMs 5000 // 5 seconds in ms.

installOptions “-g”, “-r”�}�

android.testVariants.all { variant ->

String flavorName = variant.productFlavors[0]?.name

if (flavorName?.startsWith(DEVICES_BATCH_PREFIX)) {

tasks.instrumentationTest.dependsOn variant.connectedInstrumentTest

/**

* If the previous test run raised an error, we want to force the next run to be executed

* despite everything. So each time, the tests are executed on all devices

**/

variant.connectedInstrumentTest.ignoreFailures = true

}

/**

* We add the "-g" option to the APKs installation command to grant all the permissions to our

* app and avoid interrupting the UI workflow with permissions popups.

* This flavor must run only on Android 6.0 and above devices because the -g option is

* not supported below

**/

if (flavorName?.startsWith(DEVICES_BATCH_WITH_GRANT_PREFIX)) {

variant.connectedInstrumentTest.installOptions = ["-g"]

}

180 of 180

http://eyal.fr

bit.ly/adb-chill

Thank you!

Slides

>

adbOptions {� timeOutInMs 5000 // 5 seconds in ms.

installOptions “-g”, “-r”�}�

android.testVariants.all { variant ->

String flavorName = variant.productFlavors[0]?.name

if (flavorName?.startsWith(DEVICES_BATCH_PREFIX)) {

tasks.instrumentationTest.dependsOn variant.connectedInstrumentTest

/**

* If the previous test run raised an error, we want to force the next run to be executed

* despite everything. So each time, the tests are executed on all devices

**/

variant.connectedInstrumentTest.ignoreFailures = true

}

/**

* We add the "-g" option to the APKs installation command to grant all the permissions to our

* app and avoid interrupting the UI workflow with permissions popups.

* This flavor must run only on Android 6.0 and above devices because the -g option is

* not supported below

**/

if (flavorName?.startsWith(DEVICES_BATCH_WITH_GRANT_PREFIX)) {

variant.connectedInstrumentTest.installOptions = ["-g"]

}