Curso de Android
Guía Administración Android
Tutorial sobre conceptos básicos sobre el sistema operativo Android
Contenido
- 1 What is adb?
- 2 Popular adb commands
- 3 Downloading and installing adb
- 4 New behavior as of Android 4.2.2
- 5 Troubleshooting adb
- 6 Requisitos para usar adb
- 7 adb vía wifi
- 8 Comandos habituales de Linux en Android
What is adb?
ADB ("adb"), or the Android Debug Bridge, is a development tool included with the Android SDK (Software Developer Kit), which allows for communication from an Android device (such as a phone or tablet) to a personal computer, and vice-versa. This communication can be made over a wifi connection. However more commonly, it is made via a USB cable. adb can also be used by developers for communicating from a computer to a virtual android machine that is also running on the computer.
adb is the "Swiss-army knife" of Android development. It provides numerous functions that can be accessed in detail via the command: adb --help
Popular adb commands
Among the most popular among CyanogenMod include the following, which can be typed from a Terminal program on the attached computer:
-
adb shell-- this command establishes a shell interface for establishing a command-line session with the device. In practical purposes, this allows a person to type "into" their devices, much as one would use a terminal program a Linux or Mac OS X. Individual shell commands can be sent to the device by typingadb shell <command_to_be_executed_on_the_device>
-
adb push <local> <remote>-- this command pushes a local file on the computer to a remote file on the device. You can include the full path to either the local or remote file.
-
adb pull <remote> [<local>]-- this command will pull a remote file on the device (you can include the path) to either a specified location on the computer or, if no destination is specified, to the current directory where the command was issued.
-
adb logcat-- this command allows you to view the device log in real time. It is also very useful for discovering and reporting bugs.
-
adb install <file>-- this is used to "side-load" apps (in their .apk format) to the device.
There are many more useful commands. Check out the full instruction list here.
Downloading and installing adb
Although adb can be downloaded as a simple binary, perhaps the best way to get adb is to install the Android SDK directly from Google. That will ensure that, as adb is updated with the rest of the SDK, you can always have the latest version. adb will be located in the /platform-tools directory inside the SDK directory.
New behavior as of Android 4.2.2
In Android 4.2.2, Google implemented some new security features for using adb. This requires you accept the shell session prompt from within your ROM once past whatever unlock mechanism you use for the lock screen. In order to access your device via adb within a booted ROM, you MUST download the latest Android SDK and kill any existing adb daemon sessions to proceed. Once you receive the prompt on your device, you may check the 'trust this computer' box to not be prompted again when connecting your device to that specific PC.
Troubleshooting adb
"Device not found" errors
Sometimes adb can't find your device. One solution is to run adb kill-server and then adb start-server as root or Administrator to restart the adb daemon with elevated privileges.
Also, you should make sure that the USB debugging or Android Debug Bridge option (this will vary depending on the version of Android) is checked in the Settings under Developer Options.
Requisitos para usar adb
- Si lo utilizamos para debuggear una aplicación se debe indicar en el Android Manifest añadiendo android:debuggable="true" al elemento <application>. Eclipse lo hace solo.
Despliegue de aplicaciones a dispositivo físico
- A partir de la [1] documentación oficial de Android.
- Desplegar una aplicación a un dispositivo físico es un proceso con dos partes:
Configuración del dispositivo
- En Android 4 la habilitación del USB Debug está en Ajustes > Opciones de Desarrollo.
- Nota: A partir de Android 4.2, las opciones de desarrollo no están visibles por defecto: "To make it available, go to Settings > About phone and tap Build number seven times. Return to the previous screen to find Developer options."
Error en funcionamiento de dispositivos físicos y emuladores
- El error es el siguiente:
- [2013-02-22 13:55:20 - adb] Unexpected exception 'Cannot run program "/home/juanda/Android/sdk/platform-tools/adb": java.io.IOException: error=2, No existe el archivo o el directorio' while attempting to get adb version from '/home/juanda/Android/sdk/platform-tools/adb'
- Solución, instalar los siguientes paquetes:
sudo apt-get update sudo apt-get install ia32-libs
Problema con libncurses.so.5 64-bit
Under 64bits version of Linux Mint 14 and maybe other Debian/Ubuntu flavours adb shows the following error:
./adb: error while loading shared libraries: libncurses.so.5: cannot open shared object file: No such file or directory
You can solve it by installing libncurses5 i386's version. Just type apt-get install libncurses5:i386 as root.
adb vía wifi
To update ADB use SDK Manager.
For some reason the SDK Manager does not automatically show the new release versions of Android SDK Tools and Android Platform-Tools, so if the versions of your Android SDK Tools and/or Android Platform-Tools are respectively older than 21.1 and 16.0.1, you will need to first delete them then reload the SDK Manager to get their new release versions to be displayed and available for installation.
Also, it appears that Android Support Libraries (under Extra) is also required for ADB to work, so you should install it as well.
Also, to get ADB-over-WiFi to work, first use ADB-over-USB to the same given PC/Laptop and grant access with "always" box checked.
Comandos habituales de Linux en Android
- netcfg ->ifconfig
Actualización fichero /etc/hosts
- Obtenemos el fichero hosts del movil:
juanda@dpto-01:~/Android/sdk/tools$ adb pull /etc/hosts 0 KB/s (25 bytes in 0.038s) juanda@dpto-01:~/Android/sdk/tools$ cat hosts 127.0.0.1 localhost
Lo modificamos:
juanda@dpto-01:~/Android/sdk/tools$ vi hosts juanda@dpto-01:~/Android/sdk/tools$ cat hosts 127.0.0.1 localhost 192.168.1.1 incidencias.jd www.incidencias.jd 192.168.1.1 spp.jd www.spp.jd juanda@dpto-01:~/Android/sdk/tools$ adb push hosts /etc/hosts failed to copy 'hosts' to '/etc/hosts': Read-only file system juanda@dpto-01:~/Android/sdk/tools$
- En muchos dispositivos la partición /system se monta como solo lectura así que hay que montarla con permisos de escritura.
- A continuación todas las trazas al cambiarlo en mi sistema:
juanda@dpto-01:~/Android/sdk/tools$ adb shell shell@android:/ $ su - shell@android:/ # mount -o rw,remount /system shell@android:/ # exit shell@android:/ $ exit juanda@dpto-01:~/Android/sdk/tools$ adb push hosts /etc/hosts failed to copy 'hosts' to '/etc/hosts': Permission denied juanda@dpto-01:~/Android/sdk/tools$ adb shell shell@android:/ $ cd etc shell@android:/etc $ su - shell@android:/system/etc # chmod 777 hosts shell@android:/system/etc # exit shell@android:/etc $ exit juanda@dpto-01:~/Android/sdk/tools$ adb push hosts /etc/hosts 2 KB/s (103 bytes in 0.040s) juanda@dpto-01:~/Android/sdk/tools$ adb shell shell@android:/ $ su - shell@android:/ # cd etc shell@android:/etc # chmod 644 hosts shell@android:/etc # ls -l hosts -rw-r--r-- root root 103 2013-04-12 13:00 hosts shell@android:/etc # mount -o ro,remount /system shell@android:/etc # cat hosts 127.0.0.1 localhost 192.168.1.1 incidencias.jd www.incidencias.jd 192.168.1.1 spp.jd www.spp.jd shell@android:/etc #
