Some help with Eclipse and ADB in Linux

[JoshHart]

Hey, did a search but couldnt find a solution. I'm having problems getting my device to pull up in adb remount on Ubuntu. When I try remount it says no command 'adb' found sometimes or permission denied when it does work, I have root and USB debugging enabled on the devices (a Nexus One and G1). When I try adb devices I just get ?????????????? unknown.

Also, and I don't know if it's related, but in Eclipse, I can't get the SDK location loaded, I have the directory right, but when I hit Apply or OK nothing happens, it just doesnt load. So if I try to start a project I have no Build Targets to select from.

Any help would be appreciated. I have everything running fine in Windows but I'm fairly new to Linux I haven't used it in years. I'm running Ubuntu distro if that matters. Thanks.

 

[timothydonohue]

i'm with you. i picked up the android sdk tarball, and am a little lost too . i tried getting adb to work in windows 7, but i can't get that going either. dangit. if someone could put up some good reference material, it'd be appreciated

 

[Richard_Xeli]

Hello,

The problem with linux having trouble with adb probably lies with a permission issue try adb kill-server && sudo start-server.

The other issue is most likely because you did not download any targets yet. goto windows in eclipse and select android sdk and adv, then at available packages or something like that download your target

 

[timothydonohue]

i can't even get that far. i switch to my androidSDK/tools and then "adb devices" all i get is 'no command adb found'

 

[JoshHart]

I did the first couple times too, then I went to command and did:
su
<enter password>
cd
export PATH=${PATH}:<your_sdk_dir>/tools

then when I adb remount or adb devices it gives me the unknown device thing

but I think the next secret is here
http://forum.xda-developers.com/showthread.php?t=613217
in like the 3rd post. However I think the export PATH is a temp fix because the ~/.bashrc needs to be modified with the path settings and I have no idea how to do that. I just get lots of permission errors or file not found for everything I try, even with root. I'm just using Eclipse in Windows for now, and hopefully someone can help us out cause I'd like to work on roms but I guess I need to brush my Linux up first.

 

[timothydonohue]

http://forum.xda-developers.com/showthread.php?p=5377103

i found some help elsewhere on the net, and posted it up at the end of this thread. they were having similar issues with the dream, apparently.

i also found this

that link there will probably get you hooked up

 

[timothydonohue]

adb devices now has a readout!


and, you're right about adding the export PATH=${PATH}:<your_sdk_dir>/tools to
~/.bashrc

i think this command will do it. run in terminal
gksudo gedit ~/.bashrc

i just made a comment line that says
# android sdk export path

and another line underneath it that says
export PATH=${PATH}:/home/timmyd/androidSDK/tools

because that's where i have the extracted sdk

all good, i think. now, let's see what's going on ...


oh yeah, don't forget to enable usb debugging on the device itself.
settings>applications>development
allow usb debugging

 

[timothydonohue]

screeny works at least

 

[JoshHart]

Cool, I'll try that out tomorrow.

 

[jenocrates]

i'm with you. i picked up the android sdk tarball, and am a little lost too . i tried getting adb to work in windows 7, but i can't get that going either. dangit. if someone could put up some good reference material, it'd be appreciated

Hi all!!!!

I have a problem with my HTC Tattoo, can't connect the tatto with adb in ubuntu and eclipse Helios.

/android-sdk-linux_86/platform-tools$ ./adb devices
List of devices attached
???????????? no permissions

Thank you very much.

 

[javment]

Hi, I have tha same problem with ????? and can't connect to eclipse my galaxy, so the solution is just use the instructions from the h**p://developer.android.com/guide/developing/device.html

I solve this problem with

1. Log in as root and create this file: /etc/udev/rules.d/51-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+r /etc/udev/rules.d/51-android.rules

The USB Vendor IDs foreach manufacturer

Manufacturer USB Vendor ID
Acer 0502
Dell 413c
Foxconn 0489
Garmin-Asus 091E
HTC 0bb4
Huawei 12d1
Kyocera 0482
LG 1004
Motorola 22b8
Nvidia 0955
Pantech 10A9
Samsung 04e8
Sharp 04dd
Sony Ericsson 0fce
ZTE 19D2

Hope to help you!