Android debug bridge

From Openmoko

Revision as of 10:51, 24 January 2009 by Jernst (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

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.

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.