{"id":4042,"date":"2012-09-26T13:41:46","date_gmt":"2012-09-26T16:41:46","guid":{"rendered":"http:\/\/www.telecelula.com.br\/wordpress\/?p=4042"},"modified":"2016-11-18T06:55:55","modified_gmt":"2016-11-18T09:55:55","slug":"o-que-e-adb-e-como-instala-lo","status":"publish","type":"post","link":"https:\/\/www.telecelula.com.br\/wordpress\/?p=4042","title":{"rendered":"O que \u00e9 ADB e como instala-lo?"},"content":{"rendered":"

O que \u00e9 ABD ? <\/strong><\/p>\n

ADB significa Android Debug Bridge, ele vem de uma parte do Android SDK. B\u00e1sicamente ele d\u00e1 acesso a uma interface via terminal para integra\u00e7\u00e3o entre o usu\u00e1rio e o sistema de arquivo do telefone. Como o Android \u00e9 baseado em Linux as vezes \u00e9 necess\u00e1rio acessar o aparelho via linha de comando para executar certas opera\u00e7\u00f5es avan\u00e7adas em seu aparelho com root.
\n\u00c9 poss\u00edvel executar esses comandos via alguns aplicativos existentes no pr\u00f3prio Market mas \u00e9 bem complexo executar esses comandos em uma telinha pequena como a do celular. O ADB \u00e9 a interface entre seu computador e o seu celular.<\/p>\n

Como Instalar o ADB?<\/p>\n

Downloads necess\u00e1rios:<\/p>\n

SDK Android SDK Manager v20.0.3
\nhttp:\/\/www.telecelula.com.br\/new\/suporte_download_arquivo.asp?seguro=4EDA5332C26714999<\/p>\n

\u2022 Passo 1 <\/strong>Instalar o Android SDK<\/p>\n

Instalar o Android SDK verifique o link acima para baixar o arquivo em nossa \u00e1rea de download caso nao tenha acesso a nossa \u00e1rea de download acesse: https:\/\/www.telecelula.com.br\/new\/download_Assinar.asp .H\u00e1 vers\u00f5es para Windows, Linux e MacOS X. O arquivo disponibilizado acima \u00e9 do Windows<\/strong>. Ap\u00f3s o download do SDK, descompacte o arquivo baixado em seu computador, no nosso caso vamos descompactar na raiz do nosso C: e ele ficar\u00e1 em: C:\\android-sdk-windows.<\/p>\n

\u2022Passo 2 <\/strong>Baixando as SDK Platform Tools<\/p>\n

Antigamente o ADB j\u00e1 vinha com o SDK platform tools por padr\u00e3o em uma pasta chamada “tools” mas agora foi realocado para a subpasta “platform-tools” e precisa ser baixado como um pacote SDK<\/p>\n

V\u00e1 at\u00e9 a pasta do SDK (C:\\android-sdk-windows) e execute o arquivo SDK Manager (\u00e9 importante estar conectado a internet). Quando executar esse arquivo pela primeira vez, aparecer\u00e1 uma janela para escolher alguns pacotes para instala\u00e7\u00e3o. A primeira op\u00e7\u00e3o \u00e9 “Android SDK Platform-tools”, marque-a e DESmarque todos os outros pacotes abaixo. Para marcar\/desmarcar um pacote basta clicar sobre ele e depois clicar na op\u00e7\u00e3o Accept para instalar ou Reject para n\u00e3o instalar.<\/p>\n

Depois de selecionar o “Android SDK Platform-tools” clique em install e o pacote ser\u00e1 instalado. Assim que o processo terminar voc\u00ea ter\u00e1 a pasta “platform-tools”dentro da pasta do SDK (C:\\android-sdk-windows). Essa pasta tem o ADB e suas dependencias.
\n
\nPasso 3<\/strong> Adicionando o local do ADB como vari\u00e1vel<\/p>\n

Agora que o ADB foi instalado \u00e9 necess\u00e1rio configurar o local onde ele est\u00e1 como uma variavel de ambiente pois assim voc\u00ea n\u00e3o precisa entrar na pasta C:\\android-sdk-windows\\platform-tools\\adb toda vez que for usar o ADB. Vou descrever apenas o m\u00e9todo para o windows pois presumo que seja o sistema que a maioria use no f\u00f3rum.<\/p>\n

No Windows 7 clique no “Windows ORB” ou no s\u00edmbolo do windows do lado inferior esquerdo da tela, depois clique com o bot\u00e3o direito sobre o \u00edcone “Computador” e depois clique em “Propriedades”. Nas op\u00e7\u00f5es do lado esquerdo clique em “Configura\u00e7\u00e3o avan\u00e7ada de Sistemas”, no windows XP \u00e9 s\u00f3 clicar com o bot\u00e3o direito sobre o “Meu Computador” e depois em propriedades.<\/p>\n

Na janela que se abrir h\u00e1 uma aba chamada avan\u00e7ada, clique nela e depois h\u00e1 um bot\u00e3o no canto inferior direito da janela chamado “Vari\u00e1veis de ambiente…” clique sobre ele.<\/p>\n

Uma nova janela abrir\u00e1, na parte de baixo, em Vari\u00e1veis de Sistema, procure pela vari\u00e1vel Path e de um duplo clique nela.<\/p>\n

Uma nova janela abrir\u00e1, N\u00c3O DELETE nada que est\u00e1 l\u00e1, isso pode trazer MUITOS problemas para seu windows.<\/p>\n

V\u00e1 at\u00e9 o final do campo “Valor da Vari\u00e1vel” e ADICIONE a seguinte linha:
\n
\n;c:\\android-sdk-windows\\tools;c:\\android-sdk-windows\\platform-tools
\n<\/strong>
\n\u2022Passo 4<\/strong> – Instalando os drivers USB<\/p>\n

Primeiro temos que baixar os drives USB, para isso \u00e9 necess\u00e1rio abrir novamente o SDK Manager que est\u00e1 na pasta SDK e em seguida clicar em “Available Packages” no lado esquerdo da janela<\/p>\n

Expanda a op\u00e7\u00e3o “Third party Add-ons” e depois a op\u00e7\u00e3o “Google Inc. add-ons” e marque a op\u00e7\u00e3o “Google Usb Driver package, revision” Onde\u00e9 a revis\u00e3o pertinente a aplica\u00e7\u00e3o SDK, a atual \u00e9 4.<\/p>\n

Clique em “Install Selected” e uma nova janela aparecer\u00e1, clique em “Accept all” e depois no bot\u00e3o “install”. Aguarde enquanto os drivers s\u00e3o baixados e instalados.<\/p>\n

Os drives USB estar\u00e3o na pasta “c:\\android-sdk-windows\\extras\\google\\usb_driver\\<\/strong>“.<\/p>\n

Os drivers foram baixados e est\u00e3o prontos para serem instalados. Voc\u00ea pode instala-los em sua m\u00e1quina da seguinte forma:<\/p>\n

\u2022 No aparelho, na tela inicial, aperte menu, selecione aplica\u00e7\u00f5es e depois Desenvolvimento, habilite a op\u00e7\u00e3o Depura\u00e7\u00e3o USB<\/p>\n

\u2022 Conecte seu aparelho no PC via USB e o windows iniciar\u00e1 uma instala\u00e7\u00e3o de um novo hardware. Caso ele n\u00e3o encontre autom\u00e1ticamente os drivers, fa\u00e7a-o procurar os drivers na pasta onde foram baixados (c:\\android-sdk-windows\\usb_driver) e aguarde a instala\u00e7\u00e3o<\/p>\n

\u2022 Assim que os drivers forem instalados voc\u00ea ter\u00e1 uma interface ADB instalada no seu gerenciador de dispositivos Como utilizar o ADB<\/p>\n

Como utilizar o ADB <\/strong><\/p>\n

Se voc\u00ea seguiu tudo conforme descrito acima e n\u00e3o teve nenhum erro est\u00e1 tudo pronto para a utiliza\u00e7\u00e3o do ADB para manipular seu telefone. A melhor forma de mexer com o ADB \u00e9 pela linha de comando, para certificar-se de que o ADB est\u00e1 instalado corretamente entre no prompt de comando com o seu telefone plugado no computador, digite “adb devices” e pressione enter aparecer\u00e1 abaixo o serial number do aparelho.<\/p>\n

TABELA DE COMANDOS<\/p>\n

\n

Table 1.<\/strong> Available adb commands<\/p>\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
Category<\/th>\nCommand<\/th>\nDescription<\/th>\nComments<\/th>\n<\/tr>\n
Target Device<\/td>\n-d<\/code><\/td>\nDirect an adb command to the only attached USB device.<\/td>\nReturns an error if more than one USB device is attached.<\/td>\n<\/tr>\n
-e<\/code><\/td>\nDirect an adb command to the only running emulator instance.<\/td>\nReturns an error if more than one emulator instance is running.<\/td>\n<\/tr>\n
-s\u00a0serial_number<\/var><\/code><\/td>\nDirect an adb command a specific emulator\/device instance, referred to by its adb-assigned serial number (such as “emulator-5556”).<\/td>\nSee Directing Commands to a Specific Emulator\/Device Instance<\/a>.<\/td>\n<\/tr>\n
General<\/td>\ndevices<\/code><\/td>\nPrints a list of all attached emulator\/device instances.<\/td>\nSee Querying for Emulator\/Device Instances<\/a> for more information.<\/td>\n<\/tr>\n
help<\/code><\/td>\nPrints a list of supported adb commands.<\/td>\n<\/td>\n<\/tr>\n
version<\/code><\/td>\nPrints the adb version number.<\/td>\n<\/td>\n<\/tr>\n
Debug<\/td>\nlogcat\u00a0[option] [filter-specs]<\/code><\/td>\nPrints log data to the screen.<\/td>\n<\/td>\n<\/tr>\n
bugreport<\/code><\/td>\nPrints dumpsys<\/code>, dumpstate<\/code>, and logcat<\/code> data to the screen, for the purposes of bug reporting.<\/td>\n<\/td>\n<\/tr>\n
jdwp<\/code><\/td>\nPrints a list of available JDWP processes on a given device.<\/td>\nYou can use the forward jdwp:pid<\/var><\/code> port-forwarding specification to connect to a specific JDWP process. For example:
\nadb forward tcp:8000 jdwp:472<\/code>
\njdb -attach localhost:8000<\/code><\/td>\n<\/tr>\n
Data<\/td>\ninstall\u00a0path_to_apk<\/var><\/code><\/td>\nPushes an Android application (specified as a full path to an APK file) to an emulator\/device.<\/td>\n<\/td>\n<\/tr>\n
pull\u00a0remote<\/var>\u00a0local<\/var><\/code><\/td>\nCopies a specified file from an emulator\/device instance to your development computer.<\/td>\n<\/td>\n<\/tr>\n
push\u00a0local<\/var>\u00a0remote<\/var><\/code><\/td>\nCopies a specified file from your development computer to an emulator\/device instance.<\/td>\n<\/td>\n<\/tr>\n
Ports and Networking<\/td>\nforward\u00a0local<\/var>\u00a0remote<\/var><\/code><\/td>\nForwards socket connections from a specified local port to a specified remote port on the emulator\/device instance.<\/td>\nPort specifications can use these schemes:<\/p>\n
    \n
  • tcp:port_number<\/var><\/code><\/li>\n
  • local:unix_domain_socket_name<\/var><\/code><\/li>\n
  • dev:character_device_name<\/var><\/code><\/li>\n
  • jdwp:pid<\/var><\/code><\/li>\n<\/ul>\n<\/td>\n<\/tr>\n
ppp\u00a0tty<\/var>\u00a0[parm]...<\/code><\/td>\nRun PPP over USB.<\/p>\n
    \n
  • tty<\/var><\/code> \u2014 the tty for PPP stream. For example dev:\/dev\/omap_csmi_ttyl<\/code>.<\/li>\n
  • [parm]... <\/code>\u2014 zero or more PPP\/PPPD options, such as defaultroute<\/code>, local<\/code>, notty<\/code>, etc.<\/li>\n<\/ul>\n

    Note that you should not automatically start a PPP connection.<\/td>\n

<\/td>\n<\/tr>\n
Scripting<\/td>\nget-serialno<\/code><\/td>\nPrints the adb instance serial number string.<\/td>\nSee Querying for Emulator\/Device Instances<\/a> for more information.<\/td>\n<\/tr>\n
get-state<\/code><\/td>\nPrints the adb state of an emulator\/device instance.<\/td>\n<\/tr>\n
wait-for-device<\/code><\/td>\nBlocks execution until the device is online \u2014 that is, until the instance state is device<\/code>.<\/td>\nYou can prepend this command to other adb commands, in which case adb will wait until the emulator\/device instance is connected before issuing the other commands. Here’s an example:<\/p>\n
adb wait-for-device shell getprop<\/pre>\n
Note that this command does not<\/em> cause adb to wait until the entire system is fully booted. For that reason, you should not prepend it to other commands that require a fully booted system. As an example, the install<\/code> requires the Android package manager, which is available only after the system is fully booted. A command such as<\/p>\n
adb wait-for-device install app.apk<\/pre>\n
would issue the install<\/code> command as soon as the emulator or device instance connected to the adb server, but before the Android system was fully booted, so it would result in an error.<\/td>\n<\/tr>\n
Server<\/td>\nstart-server<\/code><\/td>\nChecks whether the adb server process is running and starts it, if not.<\/td>\n<\/td>\n<\/tr>\n
kill-server<\/code><\/td>\nTerminates the adb server process.<\/td>\n<\/td>\n<\/tr>\n
Shell<\/td>\nshell<\/code><\/td>\nStarts a remote shell in the target emulator\/device instance.<\/td>\nSee Issue shell commands<\/a> for more information.<\/td>\n<\/tr>\n
shell\u00a0shell_command<\/var><\/code><\/td>\nIssues a shell command in the target emulator\/device instance and then exits the remote shell.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

Issue shell commands<\/h2>\n
\n

You can use the shell<\/code> command to issue device commands through adb, with or without entering the adb remote shell on the emulator\/device. To issue a single command without entering a remote shell, use the shell<\/code> command like this:<\/p>\n

adb [-d|-e|-s serial_number<\/var>] shell shell_command<\/var><\/pre>\n
Or enter a remote shell on an emulator\/device like this:<\/p>\n
adb [-d|-e|-s serial_number<\/var>] shell<\/pre>\n
When you are ready to exit the remote shell, press Control + D or type exit<\/code>.<\/p>\n
The shell command binaries are stored in the file system of the emulator or device, at \/system\/bin\/<\/code>.<\/p>\n
Call activity manager (am<\/code>)<\/h3>\n
Within an adb shell, you can issue commands with the activity manager (am<\/code>) tool to perform various system actions, such as start an activity, force-stop a process, broadcast an intent, modify the device screen properties, and more. While in a shell, the syntax is:<\/p>\n
am command<\/var>\r\n<\/pre>\n
You can also issue an activity manager command directly from adb without entering a remote shell. For example:<\/p>\n
adb shell am start -a android.intent.action.VIEW\r\n<\/pre>\n
Table 2.<\/strong> Available activity manager commands<\/p>\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
Command<\/th>\nDescription<\/th>\n<\/tr>\n
start [options<\/var>] intent<\/var><\/code><\/td>\nStart an Activity<\/a><\/code> specified by intent<\/var><\/code>.See the Specification for intent arguments<\/a>.<\/p>\n
Options are:<\/p>\n
    \n
  • -D<\/code>: Enable debugging.<\/li>\n
  • -W<\/code>: Wait for launch to complete.<\/li>\n
  • --start-profiler file<\/var><\/code>: Start profiler and send results to file<\/var><\/code>.<\/li>\n
  • -P file<\/var><\/code>: Like --start-profiler<\/code>, but profiling stops when the app goes idle.<\/li>\n
  • -R count<\/var><\/code>: Repeat the activity launch count<\/var><\/code> times. Prior to each repeat, the top activity will be finished.<\/li>\n
  • -S<\/code>: Force stop the target app before starting the activity.<\/li>\n
  • --opengl-trace<\/code>: Enable tracing of OpenGL functions.<\/li>\n
  • --user user_id<\/var> | current<\/code>: Specify which user to run as; if not specified, then run as the current user.<\/li>\n<\/ul>\n<\/td>\n<\/tr>\n
startservice [options<\/var>] intent<\/var><\/code><\/td>\nStart the Service<\/a><\/code> specified by intent<\/var><\/code>.See the Specification for intent arguments<\/a>.<\/p>\n
Options are:<\/p>\n
    \n
  • --user user_id<\/var> | current<\/code>: Specify which user to run as; if not specified, then run as the current user.<\/li>\n<\/ul>\n<\/td>\n<\/tr>\n
force-stop package<\/var><\/code><\/td>\nForce stop everything associated with package<\/var><\/code> (the app’s package name).<\/td>\n<\/tr>\n
kill [options<\/var>] package<\/var><\/code><\/td>\nKill all processes associated with package<\/var><\/code> (the app’s package name). This command kills only processes that are safe to kill and that will not impact the user experience.Options are:<\/p>\n
    \n
  • --user user_id<\/var> | all | current<\/code>: Specify user whose processes to kill; all users if not specified.<\/li>\n<\/ul>\n<\/td>\n<\/tr>\n
kill-all<\/code><\/td>\nKill all background processes.<\/td>\n<\/tr>\n
broadcast [options<\/var>] intent<\/var><\/code><\/td>\nIssue a broadcast intent.See the Specification for intent arguments<\/a>.<\/p>\n
Options are:<\/p>\n
    \n
  • [--user user_id<\/var> | all | current]<\/code>: Specify which user to send to; if not specified then send to all users.<\/li>\n<\/ul>\n<\/td>\n<\/tr>\n
instrument [options<\/var>] component<\/var><\/code><\/td>\nStart monitoring with an Instrumentation<\/a><\/code> instance. Typically the target component<\/var><\/code> is the form test_package<\/var>\/runner_class<\/var><\/code>.Options are:<\/p>\n
    \n
  • -r<\/code>: Print raw results (otherwise decode report_key_streamresult<\/var><\/code>). Use with [-e perf true]<\/code> to generate raw output for performance measurements.<\/li>\n
  • -e name<\/var> value<\/var><\/code>: Set argument name<\/var><\/code> to value<\/var><\/code>. For test runners a common form is -e testrunner_flag<\/var>value<\/var>[,value<\/var>...]<\/code>.<\/li>\n
  • -p file<\/var><\/code>: Write profiling data to file<\/var><\/code>.<\/li>\n
  • -w<\/code>: Wait for instrumentation to finish before returning. Required for test runners.<\/li>\n
  • --no-window-animation<\/code>: Turn off window animations while running.<\/li>\n
  • --user user_id<\/var> | current<\/code>: Specify which user instrumentation runs in; current user if not specified.<\/li>\n<\/ul>\n<\/td>\n<\/tr>\n
profile start process<\/var> file<\/var><\/code><\/td>\nStart profiler on process<\/var><\/code>, write results to file<\/var><\/code>.<\/td>\n<\/tr>\n
profile stop process<\/var><\/code><\/td>\nStop profiler on process<\/var><\/code>.<\/td>\n<\/tr>\n
dumpheap [options<\/var>] process<\/var> file<\/var><\/code><\/td>\nDump the heap of process<\/var><\/code>, write to file<\/var><\/code>.Options are:<\/p>\n
    \n
  • --user [user_id<\/var>|current]<\/code>: When supplying a process name, specify user of process to dump; uses current user if not specified.<\/li>\n
  • -n<\/code>: Dump native heap instead of managed heap.<\/li>\n<\/ul>\n<\/td>\n<\/tr>\n
set-debug-app [options<\/var>] package<\/var><\/code><\/td>\nSet application package<\/var><\/code> to debug.Options are:<\/p>\n
    \n
  • -w<\/code>: Wait for debugger when application starts.<\/li>\n
  • --persistent<\/code>: Retain this value.<\/li>\n<\/ul>\n<\/td>\n<\/tr>\n
clear-debug-app<\/code><\/td>\nClear the package previous set for debugging with set-debug-app<\/code>.<\/td>\n<\/tr>\n
monitor [options<\/var>]<\/code><\/td>\nStart monitoring for crashes or ANRs.Options are:<\/p>\n
    \n
  • --gdb<\/code>: Start gdbserv on the given port at crash\/ANR.<\/li>\n<\/ul>\n<\/td>\n<\/tr>\n
screen-compat {on|off} package<\/var><\/code><\/td>\nControl screen compatibility<\/a> mode of package<\/var><\/code>.<\/td>\n<\/tr>\n
display-size [reset|width<\/var>xheight<\/var>]<\/code><\/td>\nOverride emulator\/device display size. This command is helpful for testing your app across different screen sizes by mimicking a small screen resolution using a device with a large screen, and vice versa.Example:
\nam display-size 1280x800<\/code><\/td>\n<\/tr>\n
display-density dpi<\/var><\/code><\/td>\nOverride emulator\/device display density. This command is helpful for testing your app across different screen densities on high-density screen environment using a low density screen, and vice versa.Example:
\nam display-density 480<\/code><\/td>\n<\/tr>\n
to-uri intent<\/var><\/code><\/td>\nPrint the given intent specification as a URI.See the Specification for intent arguments<\/a>.<\/td>\n<\/tr>\n
to-intent-uri intent<\/var><\/code><\/td>\nPrint the given intent specification as an intent:<\/code> URI.See the Specification for intent arguments<\/a>.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
Specification for intent arguments<\/a><\/h4>\n
Call package manager (pm<\/code>)<\/h3>\n
Within an adb shell, you can issue commands with the package manager (pm<\/code>) tool to perform actions and queries on application packages installed on the device. While in a shell, the syntax is:<\/p>\n
pm command<\/var>\r\n<\/pre>\n
You can also issue a package manager command directly from adb without entering a remote shell. For example:<\/p>\n
adb shell pm uninstall com.example.MyApp\r\n<\/pre>\n
Table 3.<\/strong> Available package manager commands.<\/p>\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
Command<\/th>\nDescription<\/th>\n<\/tr>\n
list packages [options<\/var>] filter<\/var><\/code><\/td>\nPrints all packages, optionally only those whose package name contains the text in filter<\/var><\/code>.Options:<\/p>\n
    \n
  • -f<\/code>: See their associated file.<\/li>\n
  • -d<\/code>: Filter to only show disabled packages.<\/li>\n
  • -e<\/code>: Filter to only show enabled packages.<\/li>\n
  • -s<\/code>: Filter to only show system packages.<\/li>\n
  • -3<\/code>: Filter to only show third party packages.<\/li>\n
  • -i<\/code>: See the installer for the packages.<\/li>\n
  • -u<\/code>: Also include uninstalled packages.<\/li>\n
  • --user user_id<\/var><\/code>: The user space to query.<\/li>\n<\/ul>\n<\/td>\n<\/tr>\n
list permission-groups<\/code><\/td>\nPrints all known permission groups.<\/td>\n<\/tr>\n
list permissions [options<\/var>] group<\/var><\/code><\/td>\nPrints all known permissions, optionally only those in group<\/var><\/code>.Options:<\/p>\n
    \n
  • -g<\/code>: Organize by group.<\/li>\n
  • -f<\/code>: Print all information.<\/li>\n
  • -s<\/code>: Short summary.<\/li>\n
  • -d<\/code>: Only list dangerous permissions.<\/li>\n
  • -u<\/code>: List only the permissions users will see.<\/li>\n<\/ul>\n<\/td>\n<\/tr>\n
list instrumentation [options<\/var>]<\/code><\/td>\nList all test packages.Options:<\/p>\n
    \n
  • -f<\/code>: List the APK file for the test package.<\/li>\n
  • target_package<\/var><\/code>: List test packages for only this app.<\/li>\n<\/ul>\n<\/td>\n<\/tr>\n
list features<\/code><\/td>\nPrints all features of the system.<\/td>\n<\/tr>\n
list libraries<\/code><\/td>\nPrints all the libraries supported by the current device.<\/td>\n<\/tr>\n
list users<\/code><\/td>\nPrints all users on the system.<\/td>\n<\/tr>\n
path package<\/var><\/code><\/td>\nPrint the path to the APK of the given package<\/var><\/code>.<\/td>\n<\/tr>\n
install [options<\/var>] path<\/var><\/code><\/td>\nInstalls a package (specified by path<\/var><\/code>) to the system.Options:<\/p>\n
    \n
  • -l<\/code>: Install the package with forward lock.<\/li>\n
  • -r<\/code>: Reinstall an existing app, keeping its data.<\/li>\n
  • -t<\/code>: Allow test APKs to be installed.<\/li>\n
  • -i installer_package_name<\/var><\/code>: Specify the installer package name.<\/li>\n
  • -s<\/code>: Install package on the shared mass storage (such as sdcard).<\/li>\n
  • -f<\/code>: Install package on the internal system memory.<\/li>\n
  • -d<\/code>: Allow version code downgrade.<\/li>\n
  • -g<\/code>: Grant all permissions listed in the app manifest.<\/li>\n<\/ul>\n<\/td>\n<\/tr>\n
uninstall [options<\/var>] package<\/var><\/code><\/td>\nRemoves a package from the system.Options:<\/p>\n
    \n
  • -k<\/code>: Keep the data and cache directories around after package removal.<\/li>\n<\/ul>\n<\/td>\n<\/tr>\n
clear package<\/var><\/code><\/td>\nDeletes all data associated with a package.<\/td>\n<\/tr>\n
enable package_or_component<\/var><\/code><\/td>\nEnable the given package or component (written as “package\/class”).<\/td>\n<\/tr>\n
disable package_or_component<\/var><\/code><\/td>\nDisable the given package or component (written as “package\/class”).<\/td>\n<\/tr>\n
disable-user [options<\/var>] package_or_component<\/var><\/code><\/td>\nOptions:<\/p>\n
    \n
  • --user user_id<\/var><\/code>: The user to disable.<\/li>\n<\/ul>\n<\/td>\n<\/tr>\n
grant package_name<\/var> permission<\/var><\/code><\/td>\nGrant a permission to an app. On devices running Android 6.0 (API level 23) and higher, may be any permission declared in the app manifest. On devices running Android 5.1 (API level 22) and lower, must be an optional permission defined by the app.<\/td>\n<\/tr>\n
revoke package_name<\/var> permission<\/var><\/code><\/td>\nRevoke a permission from an app. On devices running Android 6.0 (API level 23) and higher, may be any permission declared in the app manifest. On devices running Android 5.1 (API level 22) and lower, must be an optional permission defined by the app.<\/td>\n<\/tr>\n
set-install-location location<\/var><\/code><\/td>\nChanges the default install location. Location values:<\/p>\n
    \n
  • 0<\/code>: Auto\u2014Let system decide the best location.<\/li>\n
  • 1<\/code>: Internal\u2014install on internal device storage.<\/li>\n
  • 2<\/code>: External\u2014install on external media.<\/li>\n<\/ul>\n
    Note:<\/strong> This is only intended for debugging; using this can cause applications to break and other undesireable behavior.<\/p>\n<\/td>\n<\/tr>\n
get-install-location<\/code><\/td>\nReturns the current install location. Return values:<\/p>\n
    \n
  • 0 [auto]<\/code>: Lets system decide the best location<\/li>\n
  • 1 [internal]<\/code>: Installs on internal device storage<\/li>\n
  • 2 [external]<\/code>: Installs on external media<\/li>\n<\/ul>\n<\/td>\n<\/tr>\n
set-permission-enforced permission<\/var>[true|false]<\/code><\/td>\nSpecifies whether the given permission should be enforced.<\/td>\n<\/tr>\n
trim-caches desired_free_space<\/var><\/code><\/td>\nTrim cache files to reach the given free space.<\/td>\n<\/tr>\n
create-user user_name<\/var><\/code><\/td>\nCreate a new user with the given user_name<\/var><\/code>, printing the new user identifier of the user.<\/td>\n<\/tr>\n
remove-user user_id<\/var><\/code><\/td>\nRemove the user with the given user_id<\/var><\/code>, deleting all data associated with that user<\/td>\n<\/tr>\n
get-max-users<\/code><\/td>\nPrints the maximum number of users supported by the device.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
Take a screenshot<\/h3>\n
The screencap<\/code> command is a shell utility for taking a screenshot of a device display. While in a shell, the syntax is:<\/p>\n
screencap filename<\/var>\r\n<\/pre>\n
To use the screencap<\/code> from the command line, type the following:<\/p>\n
$ adb shell screencap <\/span>\/<\/span>sdcard<\/span>\/<\/span>screen<\/span>.<\/span>png<\/span><\/pre>\n
Here’s an example screenshot session, using the adb shell to capture the screenshot and the pull<\/code> command to download the file from the device:<\/p>\n
$ adb shell\r\nshell@ $ screencap <\/span>\/<\/span>sdcard<\/span>\/<\/span>screen<\/span>.<\/span>png\r\nshell@ $ <\/span>exit<\/span>\r\n$ adb pull <\/span>\/<\/span>sdcard<\/span>\/<\/span>screen<\/span>.<\/span>png<\/span><\/pre>\n
Record a video<\/h3>\n
The screenrecord<\/code> command is a shell utility for recording the display of devices running Android 4.4 (API level 19) and higher. The utility records screen activity to an MPEG-4 file.<\/p>\n
Note:<\/strong> Audio is not recorded with the video file.<\/p>\n
A developer can use this file to create promotional or training videos. While in a shell, the syntax is:<\/p>\n
screenrecord [options<\/var>] filename<\/var>\r\n<\/pre>\n
To use screenrecord<\/code> from the command line, type the following:<\/p>\n
$ adb shell screenrecord <\/span>\/<\/span>sdcard<\/span>\/<\/span>demo<\/span>.<\/span>mp4<\/span><\/pre>\n
Stop the screen recording by pressing Control + C, otherwise the recording stops automatically at three minutes or the time limit set by --time-limit<\/code>.<\/p>\n
To begin recording your device screen, run the screenrecord<\/code> command to record the video. Then, run the pull<\/code> command to download the video from the device to the host computer. Here’s an example recording session:<\/p>\n
$ adb shell\r\nshell@ $ screenrecord <\/span>--<\/span>verbose <\/span>\/<\/span>sdcard<\/span>\/<\/span>demo<\/span>.<\/span>mp4\r\n<\/span>(<\/span>press <\/span>Control<\/span> +<\/span> C to stop<\/span>)<\/span>\r\nshell@ $ <\/span>exit<\/span>\r\n$ adb pull <\/span>\/<\/span>sdcard<\/span>\/<\/span>demo<\/span>.<\/span>mp4<\/span><\/pre>\n
The screenrecord<\/code> utility can record at any supported resolution and bit rate you request, while retaining the aspect ratio of the device display. The utility records at the native display resolution and orientation by default, with a maximum length of three minutes.<\/p>\n
There are some known limitations of the screenrecord<\/code> utility that you should be aware of when using it:<\/p>\n
    \n
  • Some devices may not be able to record at their native display resolution. If you encounter problems with screen recording, try using a lower screen resolution.<\/li>\n
  • Rotation of the screen during recording is not supported. If the screen does rotate during recording, some of the screen is cut off in the recording.<\/li>\n<\/ul>\n
    Table 4.<\/strong> screenrecord<\/code> options<\/p>\n\n\n\n\n\n\n\n\n\n
    Options<\/th>\nDescription<\/th>\n<\/tr>\n
    --help<\/code><\/td>\nDisplays command syntax and options<\/td>\n<\/tr>\n
    --size width<\/var>xheight<\/var><\/code><\/td>\nSets the video size: 1280x720<\/code>. The default value is the device’s native display resolution (if supported), 1280×720 if not. For best results, use a size supported by your device’s Advanced Video Coding (AVC) encoder.<\/td>\n<\/tr>\n
    --bit-rate rate<\/var><\/code><\/td>\nSets the video bit rate for the video, in megabits per second. The default value is 4Mbps. You can increase the bit rate to improve video quality, but doing so results in larger movie files. The following example sets the recording bit rate to 6Mbps:<\/p>\n
    screenrecord <\/span>--<\/span>bit<\/span>-<\/span>rate <\/span>6000000<\/span> \/<\/span>sdcard<\/span>\/<\/span>demo<\/span>.<\/span>mp4<\/span><\/pre>\n<\/td>\n<\/tr>\n
    --time-limit time<\/var><\/code><\/td>\nSets the maximum recording time, in seconds. The default and maximum value is 180 (3 minutes).<\/td>\n<\/tr>\n
    --rotate<\/code><\/td>\nRotates the output 90 degrees. This feature is experimental.<\/td>\n<\/tr>\n
    --verbose<\/code><\/td>\nDisplays log information on the command-line screen. If you do not set this option, the utility does not display any information while running.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
    Read ART profiles for apps<\/h3>\n
    Starting in Android 7.0 (API level 24) the Android Runtime (ART) collects execution profiles for installed apps, which are used to optimize app performance. You might want to examine the collected profiles to understand which methods are determined to be frequently executed and which classes are used during app startup.<\/p>\n
    To produce a text form of the profile information, use the command:<\/p>\n
    $ adb shell cmd package dump-profiles package<\/var>\r\n<\/pre>\n
    To retrieve the file produced, use:<\/p>\n
    $ adb pull \/data\/misc\/profman\/package<\/var>.txt\r\n<\/pre>\n
    Other shell commands<\/h3>\n
    For a list of all the available shell programs, use the following command:<\/p>\n
    adb shell ls \/system\/bin<\/pre>\n
    Help is available for most of the commands.<\/p>\n
    Table 5 lists some of the more common adb shell commands.<\/p>\n
    Table 5.<\/strong> Some other adb shell commands<\/p>\n\n\n\n\n\n\n\n\n\n
    Shell Command<\/th>\nDescription<\/th>\nComments<\/th>\n<\/tr>\n
    dumpsys<\/code><\/td>\nDumps system data to the screen.<\/td>\nThe Dalvik Debug Monitor Server<\/a> (DDMS) tool offers an integrated debug environment that you may find easier to use.<\/td>\n<\/tr>\n
    dumpstate<\/code><\/td>\nDumps state to a file.<\/td>\n<\/tr>\n
    logcat\u00a0[option]...\u00a0[filter-spec]...<\/code><\/td>\nEnables system and app logging and prints output to the screen.<\/td>\n<\/tr>\n
    dmesg<\/code><\/td>\nPrints kernel debugging messages to the screen.<\/td>\n<\/tr>\n
    start<\/code><\/td>\nStarts (restarts) an emulator\/device instance.<\/td>\n<\/td>\n<\/tr>\n
    stop<\/code><\/td>\nStops execution of an emulator\/device instance.<\/td>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n
    <\/div>\n
     <\/p>\n","protected":false},"excerpt":{"rendered":"
    O que \u00e9 ABD ? ADB significa Android Debug Bridge, ele vem de uma parte do Android SDK. B\u00e1sicamente ele d\u00e1 acesso a uma interface via terminal para integra\u00e7\u00e3o entre o usu\u00e1rio e o sistema de arquivo do telefone. Como o Android \u00e9 baseado em Linux as vezes \u00e9 necess\u00e1rio acessar o aparelho via linha […]<\/p>\n","protected":false},"author":17,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[121,47,288],"tags":[],"class_list":{"0":"post-4042","1":"post","2":"type-post","3":"status-publish","4":"format-standard","6":"category-android-manutencao-em-celulares","7":"category-samsung","8":"category-smartphones","9":"czr-hentry"},"_links":{"self":[{"href":"https:\/\/www.telecelula.com.br\/wordpress\/index.php?rest_route=\/wp\/v2\/posts\/4042","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.telecelula.com.br\/wordpress\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.telecelula.com.br\/wordpress\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.telecelula.com.br\/wordpress\/index.php?rest_route=\/wp\/v2\/users\/17"}],"replies":[{"embeddable":true,"href":"https:\/\/www.telecelula.com.br\/wordpress\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=4042"}],"version-history":[{"count":5,"href":"https:\/\/www.telecelula.com.br\/wordpress\/index.php?rest_route=\/wp\/v2\/posts\/4042\/revisions"}],"predecessor-version":[{"id":7048,"href":"https:\/\/www.telecelula.com.br\/wordpress\/index.php?rest_route=\/wp\/v2\/posts\/4042\/revisions\/7048"}],"wp:attachment":[{"href":"https:\/\/www.telecelula.com.br\/wordpress\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=4042"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.telecelula.com.br\/wordpress\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=4042"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.telecelula.com.br\/wordpress\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=4042"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}