[solved/info] - adb with ubuntu

---

I am running ubuntu 9.04. I have eclipse and the Android s.d.k. set up and running perfectly. But I cannot figure out how to setup a.d.b.


I apologize for the new post, but I promise I have searched for hours on this forum and Google. All I found was info on installing on Windows, and fixing a.d.b that used to work but won't work now after updating to 9.04. Anybody have a tutorial or a fix that I might have missed? Thanks in advance.

there is nothing to set up just make shure it has execute permissions, thats what had me stumped LOL
#chmod +x adb

then just plug in the g1 (no drivers required) and
#adb whatever you want

but i was using arch :eek:

to make it easier copy the adb executable to /usr/bin and you can execute from any directory withoud using cd /directory

sudo cp /androidsdk/tools/adb /usr/bin
sudo chmod +x /usr/bin/adb

that's how i use mine on my 8.10 and 9.04

Thanks guys, pretty sure it's working, just need to figure out how to connect to device. I will try your suggestions.

Done. Then I tried
#adb logcat
and i get
- waiting for device -
should I
#cd /bin
#adb logcat
?

I am following tutorials for windows, so it is kind of confusing. I don't think I can connect. I get

chris@chris-laptop:~$ adb start-server
chris@chris-laptop:~$ adb devices
List of devices attached 

chris@chris-laptop:~$

Here is me trying all kinds of stuff

chris@chris-laptop:~$ adb start-server
chris@chris-laptop:~$ adb devices
List of devices attached 

chris@chris-laptop:~$ adb kill-server
chris@chris-laptop:~$ adb
Android Debug Bridge version 1.0.20

 -d                            - directs command to the only connected USB device
                                 returns an error if more than one USB device is present.
 -e                            - directs command to the only running emulator.
                                 returns an error if more than one emulator is running.
 -s <serial number>            - directs command to the USB device or emulator with
                                 the given serial number
 -p <product 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.
 devices                       - list all connected devices

device commands:
  adb push <local> <remote>    - copy file/dir to device
  adb pull <remote> <local>    - copy file/dir from device
  adb sync [ <directory> ]     - copy host->device only if changed
                                 (see 'adb help all')
  adb shell                    - run remote shell interactively
  adb shell <command>          - run remote shell command
  adb emu <command>            - run emulator console command
  adb logcat [ <filter-spec> ] - View device log
  adb forward <local> <remote> - forward socket connections
                                 forward specs are one of: 
                                   tcp:<port>
                                   localabstract:<unix domain socket name>
                                   localreserved:<unix domain socket name>
                                   localfilesystem:<unix domain socket name>
                                   dev:<character device name>
                                   jdwp:<process pid> (remote only)
  adb jdwp                     - list PIDs of processes hosting a JDWP transport
  adb install [-l] [-r] <file> - push this package file to the device and install it
                                 ('-l' means forward-lock the app)
                                 ('-r' means reinstall the app, keeping its data)
  adb uninstall [-k] <package> - remove this app package from the device
                                 ('-k' means keep the data and cache directories)
  adb bugreport                - return all information from the device
                                 that should be included in a bug report.

  adb help                     - show this help message
  adb version                  - show version num

DATAOPTS:
 (no option)                   - don't touch the data partition
  -w                           - wipe the data partition
  -d                           - flash the data partition

scripting:
  adb wait-for-device          - block until device is online
  adb start-server             - ensure that there is a server running
  adb kill-server              - kill the server if it is running
  adb get-state                - prints: offline | bootloader | device
  adb get-serialno             - prints: <serial-number>
  adb status-window            - continuously print device status for a specified device
  adb remount                  - remounts the /system partition on the device read-write
  adb root                     - restarts adb with root permissions

networking:
  adb ppp <tty> [parameters]   - Run PPP over USB.
 Note: you should not automatically start a PDP connection.
 <tty> refers to the tty for PPP stream. Eg. dev:/dev/omap_csmi_tty1
 [parameters] - Eg. defaultroute debug dump local notty usepeerdns

adb sync notes: adb sync [ <directory> ]
  <localdir> can be interpreted in several ways:

  - If <directory> is not specified, both /system and /data partitions will be updated.

  - If it is "system" or "data", only the corresponding partition
    is updated.
chris@chris-laptop:~$ adb get-state
* daemon not running. starting it now *
* daemon started successfully *
unknown
chris@chris-laptop:~$ devices
bash: devices: command not found
chris@chris-laptop:~$ adb devices
List of devices attached 

chris@chris-laptop:~$ adb remount
error: device not found
chris@chris-laptop:~$ adb start-server
chris@chris-laptop:~$ adb remount
error: device not found
chris@chris-laptop:~$ adb get-serialno
unknown
chris@chris-laptop:~$

tried another usb cable, different usb port. Same stuff

chris@chris-laptop:~$ adb shell
error: device not found
chris@chris-laptop:~$ adb start-server
chris@chris-laptop:~$ adb shell
error: device not found
chris@chris-laptop:~$ ls
adb                           examples.desktop       Templates
android-sdk-linux_x86-1.5_r2  Firefox_wallpaper.png  Videos
Desktop                       Music                  workspace
Documents                     Pictures               World of Warcraft Trial
eclipse                       Public
chris@chris-laptop:~$ cd /
chris@chris-laptop:/$ ls
bin    dev   initrd.img  media  proc  selinux  tmp  vmlinuz
boot   etc   lib         mnt    root  srv      usr
cdrom  home  lost+found  opt    sbin  sys      var
chris@chris-laptop:/$ adb shell
error: device not found
chris@chris-laptop:/$ adb start-server
chris@chris-laptop:/$ adb shell
error: device not found
chris@chris-laptop:/$ ls
bin    dev   initrd.img  media  proc  selinux  tmp  vmlinuz
boot   etc   lib         mnt    root  srv      usr
cdrom  home  lost+found  opt    sbin  sys      var
chris@chris-laptop:/$ adb start-server
chris@chris-laptop:/$ adb shell
error: device not found
chris@chris-laptop:/$ adb kill-server
chris@chris-laptop:/$ adb devices
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached 

chris@chris-laptop:/$ adb shell
error: device not found
chris@chris-laptop:/$

Any ideas?

I am using the Rogers v3 Rom with jf1.42 bootloader and the 2005 s.p.l

Would any of that matter.

Originally Posted by CBowley

I am using the Rogers v3 Rom with jf1.42 bootloader and the 2005 s.p.l

Would any of that matter.

Doubtful. I too am looking to get ADB running on my Ubuntu laptop, as it would save a bunch of time for me being able to use it instead of my slow windows computer (ADB is corrupted driver-wise on my main rig).

Anyone have any reasonable tutorials for lower-level linux users on Ubuntu 9.04 32-bit?