Database Users

[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 :O

to make it easier copy the adb executable to /usr/bin and you can execute from any directory withoud using cd /directory
Code:
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
Code:
[email protected]:~$ adb start-server
[email protected]:~$ adb devices
List of devices attached
[email protected]:~$

Here is me trying all kinds of stuff
Code:
[email protected]:~$ adb start-server
[email protected]:~$ adb devices
List of devices attached
[email protected]:~$ adb kill-server
[email protected]:~$ 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.
[email protected]:~$ adb get-state
* daemon not running. starting it now *
* daemon started successfully *
unknown
[email protected]:~$ devices
bash: devices: command not found
[email protected]:~$ adb devices
List of devices attached
[email protected]:~$ adb remount
error: device not found
[email protected]:~$ adb start-server
[email protected]:~$ adb remount
error: device not found
[email protected]:~$ adb get-serialno
unknown
[email protected]:~$

tried another usb cable, different usb port. Same stuff
Code:
[email protected]:~$ adb shell
error: device not found
[email protected]:~$ adb start-server
[email protected]:~$ adb shell
error: device not found
[email protected]:~$ 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
[email protected]:~$ cd /
[email protected]:/$ 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
[email protected]:/$ adb shell
error: device not found
[email protected]:/$ adb start-server
[email protected]:/$ adb shell
error: device not found
[email protected]:/$ 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
[email protected]:/$ adb start-server
[email protected]:/$ adb shell
error: device not found
[email protected]:/$ adb kill-server
[email protected]:/$ adb devices
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
[email protected]:/$ adb shell
error: device not found
[email protected]:/$
Any ideas?

I am using the Rogers v3 Rom with jf1.42 bootloader and the 2005 s.p.l
Would any of that matter.

CBowley said:
I am using the Rogers v3 Rom with jf1.42 bootloader and the 2005 s.p.l
Would any of that matter.
Click to expand...
Click to collapse
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?

I have Ubuntu + SDK and I don't have any issue.
Are you sure you installed your SDk the correct way == you followed exaclty the android.com howto ?

it should work with ubuntu 9.04. Just follow this instructions to setup connection to your phone. mainly create rule for you device in udev.
http://developer.android.com/guide/developing/device.html
If you're developing on Ubuntu Linux, you need to add a rules file:
1. Login as root and create this file: /etc/udev/rules.d/50-android.rules.
For Gusty/Hardy, edit the file to read:
SUBSYSTEM=="usb", SYSFS{idVendor}=="0bb4", MODE="0666"
For Dapper, edit the file to read:
SUBSYSTEM=="usb_device", SYSFS{idVendor}=="0bb4", MODE="0666"
2. Now execute:
chmod a+rx /etc/udev/rules.d/50-android.rules
reboot, then if you are still having problem after this, one more thing to try to start server swith sudo.
adb kill-server
sudo adb start-server

knaries2000 said:
it should work with ubuntu 9.04. Just follow this instructions to setup connection to your phone. mainly create rule for you device in udev.
http://developer.android.com/guide/developing/device.html
If you're developing on Ubuntu Linux, you need to add a rules file:
1. Login as root and create this file: /etc/udev/rules.d/50-android.rules.
For Gusty/Hardy, edit the file to read:
SUBSYSTEM=="usb", SYSFS{idVendor}=="0bb4", MODE="0666"
For Dapper, edit the file to read:
SUBSYSTEM=="usb_device", SYSFS{idVendor}=="0bb4", MODE="0666"
2. Now execute:
chmod a+rx /etc/udev/rules.d/50-android.rules
reboot, then if you are still having problem after this, one more thing to try to start server swith sudo.
adb kill-server
sudo adb start-server
Click to expand...
Click to collapse
I think I did this part, I will double check. I did try sudo adb start-server, that didn't work. I will double check the rest. Thank you.

Oh that's why I never did it, I cannot find a rule for jaunty, only hardy, dapper, and gutsy.. I'll do more searching. Thanks for the idea.

Okay it works now. This is what I get
Code:
[email protected]:~$ adb start-server
* daemon not running. starting it now *
* daemon started successfully *
[email protected]:~$ adb devices
List of devices attached
HT845GZ28769 device
[email protected]:~$ adb shell
# ls
cache init.goldfish.rc sbin
data init.rc sdcard
default.prop init.trout.rc sqlite_stmt_journals
dev proc sys
etc root system
init runme.sh
#
THIS IS WHAT I DID:
created 2 files on my desktop named:
50-android.rules
51-android.rules
Then I edited both files to read:
SUBSYSTEM=="usb", SYSFS{idVendor}=="0bb4", MODE="0666"
Then I opened terminal and did this
Code:
[email protected]:~$sudo mv /home/chris/desktop/50-android.rules /etc/udev/rules.d
[email protected]:~$sudo mv /home/chris/desktop/51-android.rules /etc/udev/rules.d
Then I rebooted and It all worked. I am runnung ubuntu 9.04 jaunty jakelope(sp?)
Thanks for everyones help. Hope this helps someone else.

CBowley said:
Okay it works now. This is what I get-------
Thanks for everyones help. Hope this helps someone else.
Click to expand...
Click to collapse
Thank you so much, this works perfectly. Bump for someone else finding this who needs it.

Yes it has to be rule 51, not 50 with Jaunty. Google doc is not up to date yet.
see this thread :
http://groups.google.com/group/andr...read/thread/ab6e89c4b51cd905/a05c2a749cd55b88
> this was in /etc/udev/rules.d/50-android.rules
> But it seems to also work like this : (method for Ubuntu 9.04 :
> http://www.frandroid.com/2371/ubuntu-904-et-android/ )
> -> in /etc/udev/rules.d/51-android.rules :
> SUBSYSTEM==”usb”, SYSFS{idVendor}==”0bb4", MODE=”0666"
Ubuntu 9.04 already has a rules/50-something file so you need to make
sure that the android rule is > 50. Otherwise whatever you define gets
reset. We should update the doc to just state rule/51-android.rules
which will work right now till the base configuration changes once
again
> Also take care if you copy/paste this rule : looks like double quotes
> (") may be wrongly copied from html page, and then it did not work for
> me before I retyped them.
Hmm thanks for the info. That's a new one.

Edit
Ok sorry a little OT, but I responded to this because I did not see an answer posted. I Seem to be having problems with posts showing up when I am logged in... but not when I am logged out... really weird. After I logged out at least another dozen posts showed up in this thread.

you need to change the rule from 50 to 51 on ubuntu 9.4
didnt realise the answer was posted sorry. but its def the right answer

CBowley said:
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.
Click to expand...
Click to collapse
sudo bash -c "echo SUBSYSTEM==\"usb\", SYSFS{idVendor}==\"0bb4\", MODE=\"0666\" > /etc/udev/rules.d/51-android.rules"
sudo /etc/init.d/udev restart
killall adb
adb shell

[Q] Simple development on 10.1 retail via Linux?

Greetings,
I'd have posted this on '10.1 development', but I'm not allowed to yet.
I just received the new G.T. 10.1 to use for development. I'm trying to push my first Android app to it, but am having no luck. I'm running the latest Ubuntu. I've followed the instructions here:
Code:
http : // developer.android.com/guide/developing/device.html
Here's my rules file:
Code:
$ ls -l /etc/udev/rules.d/51-android.rules
-rw-r--r-- 1 root root 55 2011-06-18 08:42 /etc/udev/rules.d/51-android.rules
$ cat /etc/udev/rules.d/51-android.rules
SUBSYSTEM=="usb", SYSFS{idVendor}="04e8", MODE="0666"
but I get this from adb:
Code:
$ adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
???????????? no permissions
My device is seen by Ubuntu:
Code:
$ lsusb
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 002: ID 04e8:685e Samsung Electronics Co., Ltd
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Here's my system id:
Code:
$ uname -a
Linux ubuntu 2.6.32-30-generic #59-Ubuntu SMP Tue Mar 1 21:30:21 UTC 2011 i686 GNU/Linux
Can anyone tell me what I'm missing? Has anyone connected to the new US consumer 10.1? Any help in getting me over this hump would be greatly appreciated.
Blat

USB debugging enabled?
What if you run adb as root?

try the commands bellow:
Code:
su
adb kill-server
adb start-server

[Q] Linux (Ubuntu) & Honeycomb 3.2 usb

Lots of instructions both here and on the Ubuntu forums.
Nothing seems to work for me. I want to connect my Acer A500 to
a pc running linux. Things work fine on Windows XP with the Acer Driver.
added mtp support to ubuntu and a host gmtp I haven't tried usb rule setup
Should the Tablet be in USB debug mode or not?
Any help appreciated. Things seem to have change since May when most of the posts appeared.
Bob

I tested this way with 3.2 a couple of hours ago. Works fine.
1. Install mtpfs
Code:
sudo apt-get install mtpfs
2. In the tablet, go to Settings->Applications->Development and turn USB Debugging on (check the box).
3. Plug your USB cable into the tablet and your Ubuntu machine.
4. Press Ctrl+Alt+t to open console
5. execute lsusb
Code:
lsusb
6. In the result find the line
Code:
Bus 001 Device 005: ID 0502:3325 Acer, Inc.
It tells you that your vendor id is 0502
7. Disconnect the USB cable
8. Edit the file /etc/udev/rules.d/51-android.rules
Code:
sudo nano /etc/udev/rules.d/51-android.rules
you need to add this line (Note, the vendor id is one that has been got on step 6):
SUBSYSTEM=="usb", ATTR{idVendor}=="0502", MODE="0666"
Click to expand...
Click to collapse
9. Create a mount point as root and set your user as its owner
Code:
sudo mkdir /media/a500
sudo chown [B]username:groupname[/B] /media/a500
username:groupname is your username and his primary group name
for me it was deo:users
10. Change your fstab:
Code:
sudo nano /etc/fstab
to the very end add
# mount point for Acer A500
mtpfs /media/a500 fuse user,noauto,allow_other 0 0
Click to expand...
Click to collapse
11. change fuse.conf:
Code:
sudo nano /etc/fuse.conf
here you need to uncomment the line
#user_allow_other
Click to expand...
Click to collapse
should become
user_allow_other
Click to expand...
Click to collapse
12. Add yourself to the fuse group
Code:
sudo usermod -a -G fuse [B]username[/B]
username is your username
13. Reboot.
Mountpoint appears in Nautilus (and on Desktop as well)
don't forget to unmount the device before unplugging the cable

adb connection to kindle with linux problems

I'm on unbuntu 11.10, my kindle has CM7 on it, when it's plugged in and I run ./adb devices it shows up as a bunch of question marks and says no permissions. My phone connects fine in adb, so its not a problem with adb. The kindle also connects fine for USB storage and stuff.

i used to have the problem when I was running ubuntu, but even since I started running arch I haven't had that problem. It has something to do with user privelidges and the way I fixed it was by running
Code:
sudo ./adb kill-server
sudo ./adb start-server
./adb devices
stating the adb server using root fixed the problem for me.
btw this isn't the right forum for questions.

Theres no questions forum for the kindle yet. I tried killing and re-starting adb with the sudo command, and it still shows question marks and no permissions

when in run lsusb i get 4 linux foundation root hubs for device1 and for device2 i get
ID 1949:0006 Lab126

Try sudo su or sudo ./adb devices
Sent from my Incredible 2 using XDA App

tried sudo ./adb devices and still question marks and no permissions.

Here's what I know, which isn't much. Maybe some of it will help?
Set up your /etc/udev/rules.d/51-android.rules file like this:
SUBSYSTEM=="usb", ATTR{idVendor}=="1949", ATTR{idProduct}=="0006", MODE="0600", OWNER="<username>"
SUBSYSTEM=="usb", ATTR{idVendor}=="1949", ATTR{idProduct}=="0005", MODE="0600", OWNER="<username>"
Replace <username> with your user name.
The kindle reports idProduct 0005 when in recovery (at least mine did).
It's worth a shot.

teookie said:
Here's what I know, which isn't much. Maybe some of it will help?
Set up your /etc/udev/rules.d/51-android.rules file like this:
SUBSYSTEM=="usb", ATTR{idVendor}=="1949", ATTR{idProduct}=="0006", MODE="0600", OWNER="<username>"
SUBSYSTEM=="usb", ATTR{idVendor}=="1949", ATTR{idProduct}=="0005", MODE="0600", OWNER="<username>"
Replace <username> with your user name.
The kindle reports idProduct 0005 when in recovery (at least mine did).
It's worth a shot.
Click to expand...
Click to collapse
Yea, this should fix your problem.
Open terminal and do this...
Code:
gksudo gedit /etc/udev/rules.d/51-android.rules
which will open up 51-android.rules in gedit so that you can add this rule...
Code:
SUBSYSTEM=="usb", SYSFS{idVendor}=="1949", MODE="0666"
Save the document and then close and reopen terminal.
Type...
Code:
adb devices
If you do not see your device try rebooting your computer
I do not have the rule set up the way it is quoted from the above post but you can add that in addition to the rule that I posted here.
This is the way my rules look for all of my devices. Notice that for some devices I have "subsystem" and subsystems" rules set up but there does not seem to be a difference in gaining access for ADB. I think I set up "subsystems" on a few devices a while ago for porting clockwork to a few devices or some other random thing. Either way you should just need the "subsystem" rule that I posted in the code box above.
SUBSYSTEM=="usb", SYSFS{idVendor}=="0bb4", MODE="0666"
SUBSYSTEM=="usb", SYSFS{idVendor}=="12d1", MODE="0666"
SUBSYSTEM=="usb", SYSFS{idVendor}=="18d1", MODE="0666"
SUBSYSTEM=="usb", SYSFS{idVendor}=="0955", MODE="0666"
SUBSYSTEM=="usb", SYSFS{idVendor}=="1949", MODE="0666"
SUBSYSTEMS=="usb", ATTRS{idVendor}=="12d1", ATTRS{idProduct}=="3610", MODE="0666", OWNER="brian"
SUBSYSTEMS=="usb", ATTRS{idVendor}=="18d1", ATTRS{idProduct}=="d00d", MODE="0666", OWNER="brian"
SUBSYSTEMS=="usb", ATTRS{idVendor}=="0955", ATTRS{idProduct}=="7820", MODE="0666", OWNER="brian"
Click to expand...
Click to collapse
Good luck!!
(This thread should be moved to General. Mods?)

I was having this issue yesterday as well... Fixed be making sure I edited usb.ini in ./android folder with 0x1949 and 0x0006 then i restarted computer.{ just to feel good about myself} rebooted. typed sudo su put my password in typed ./adb kill-server typed ./adb start-server typed ./adb devices and POW im running just fine. Ubuntu 11.10 here

my linux can't list the deivce
my dmesg is:
[ 1283.317124] usb 2-2: new high speed USB device using ehci_hcd and address 13
[ 1283.434819] usb 2-2: New USB device found, idVendor=1949, idProduct=0006
[ 1283.434828] usb 2-2: New USB device strings: Mfr=5, Product=1, SerialNumber=2
[ 1283.434835] usb 2-2: Product: kindle
[ 1283.434840] usb 2-2: Manufacturer: Amazon
[ 1283.434846] usb 2-2: SerialNumber: 0123456789ABCDEF
----
when I use adb-linux devices, it said nothing. : (includibg run with sudo)
>./adb-linux devices
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
how can I checked and connect it. my kindle can't boot up, it's always in opening-screen "Kindle fire".

ixc said:
my linux can't list the deivce
my dmesg is:
[ 1283.317124] usb 2-2: new high speed USB device using ehci_hcd and address 13
[ 1283.434819] usb 2-2: New USB device found, idVendor=1949, idProduct=0006
[ 1283.434828] usb 2-2: New USB device strings: Mfr=5, Product=1, SerialNumber=2
[ 1283.434835] usb 2-2: Product: kindle
[ 1283.434840] usb 2-2: Manufacturer: Amazon
[ 1283.434846] usb 2-2: SerialNumber: 0123456789ABCDEF
----
when I use adb-linux devices, it said nothing. : (includibg run with sudo)
>./adb-linux devices
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
how can I checked and connect it. my kindle can't boot up, it's always in opening-screen "Kindle fire".
Click to expand...
Click to collapse
Did you do what post #9 said?
printf "0x1949\n0x0006\n" >>~/.android/adb_usb.ini
adb kill-server
adb devices

I'm on Ubuntu 11.10. I spent a few hours trying different things, but adding SikYou's rule to 51-android.rules:
SUBSYSTEM=="usb", SYSFS{idVendor}=="1949", MODE="0666"
Click to expand...
Click to collapse
...finally solved the issue for me. "adb devices" now shows my Kindle Fire.

Cannot access device with adb

Hello all,
I want to reflash my Nexus 6P with a custom version of the AOSP. I can't access the device using "adb devices".
Code:
adb devices
List of devices attached
???????????? no permissions
I guess I need to add an entry for Nexus 6P (and also for 5X) to the /etc/udev/rules.d/51-android.rules file. For this, I need the idProduct code for these two phones.
Code:
# adb protocol on hammerhead (Nexus 5)
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", [B]ATTR{idProduct}=="4ee1"[/B], MODE="0600", OWNER="paul"
Where can I find this code?
Many thanks,
Paul

I see 'no permissions'.
Maybe you should try clearing the permissions cache in the developer options, and then request adb again, so you'll see a popup on your phone for permission?

Sorry for bothering the group, I found it, use
Code:
lsusb
Bus 001 Device 070: ID 18d1:4ee7 Google Inc.
Set idProduct 4ee7 as follows:
Code:
# adb protocol on angler (Nexus 6P)
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4ee7", MODE="0600", OWNER="paul"