Android debug bridge

From Openmoko

(Difference between revisions)
Jump to: navigation, search
(New page: {|align=right |__TOC__ |} Image:android.png To assist in debugging and to gain shell access to the phone with Android, you can use [http://people.openmoko.org/sean_mcneil/adb adb]...)
 
Line 18: Line 18:
  
 
Sometimes, adb gets stuck: if you cannot to the device run "adb kill-server" before trying other commands.
 
Sometimes, adb gets stuck: if you cannot to the device run "adb kill-server" before trying other commands.
 +
 +
 +
 +
Startup problems (Beta2): adb shell to the device and delete /data/data/com.android.providers.settings/databases/settings.db
 +
 +
Adb can not find any device:
 +
Make sure you can ping the device. Kill the background running adb-server by "adb kill-server" and start your first adb instance (which starts the background process) with "ADBHOST=192.168.0.202 adb devices". After that, you can run adb without ADBHOST-Variable.

Revision as of 00:41, 26 January 2009

Android.png

To assist in debugging and to gain shell access to the phone with Android, you can use 

  adb

You should be able to connect to the phone as long as you start it up with the USB connected to your host. I don't think it will work if you plug it in after starting. Of course, you need to setup USB_Networking (ifconfig usb0 ...) on your host before connecting.

Some helpful commands are: 

   ADBHOST=192.168.0.202 ./adb logcat           - like a tail -f of the android log
   ADBHOST=192.168.0.202 ./adb logcat -b radio  - same as above for the radio logs
   ADBHOST=192.168.0.202 ./adb shell            - bring up a command shell to the phone
   ADBHOST=192.168.0.202 ./adb kill-server      - kill the background server on the host

Sometimes, adb gets stuck: if you cannot to the device run "adb kill-server" before trying other commands.


Startup problems (Beta2): adb shell to the device and delete /data/data/com.android.providers.settings/databases/settings.db

Adb can not find any device: Make sure you can ping the device. Kill the background running adb-server by "adb kill-server" and start your first adb instance (which starts the background process) with "ADBHOST=192.168.0.202 adb devices". After that, you can run adb without ADBHOST-Variable.

Retrieved from "http://openmoko.org/index.php?title=Android_debug_bridge&oldid=64372"
Personal tools

Android.png

To assist in debugging and to gain shell access to the phone with Android, you can use 

  adb

You should be able to connect to the phone as long as you start it up with the USB connected to your host. I don't think it will work if you plug it in after starting. Of course, you need to setup USB_Networking (ifconfig usb0 ...) on your host before connecting.

Some helpful commands are: 

   ADBHOST=192.168.0.202 ./adb logcat           - like a tail -f of the android log
   ADBHOST=192.168.0.202 ./adb logcat -b radio  - same as above for the radio logs
   ADBHOST=192.168.0.202 ./adb shell            - bring up a command shell to the phone
   ADBHOST=192.168.0.202 ./adb kill-server      - kill the background server on the host

Sometimes, adb gets stuck: if you cannot to the device run "adb kill-server" before trying other commands.


Startup problems (Beta2): adb shell to the device and delete /data/data/com.android.providers.settings/databases/settings.db

Adb can not find any device: Make sure you can ping the device. Kill the background running adb-server by "adb kill-server" and start your first adb instance (which starts the background process) with "ADBHOST=192.168.0.202 adb devices". After that, you can run adb without ADBHOST-Variable.