Thread: Setting up SDK in Linux
- 02-10-2010, 09:24 PM #1
So I Hear You Can Mod
- Join Date
- Feb 2010
- Posts
- 282
- Thanks
- 1
- Thanked 7 Times in 7 Posts
- Downloads
- 0
- Uploads
- 0
Setting up SDK in Linux
So, Ubuntu has decided to be mean to me.
I can't get my SDK path to stick, and when I cd to sdk tools it tells me the device doesn't have the right permissions.
Help with setting up SDK?
- 02-11-2010, 03:46 AM #2
Banned
- Join Date
- Jan 2010
- Location
- Winter Haven, Florida, USA
- Posts
- 24
- Thanks
- 0
- Thanked 4 Times in 3 Posts
- Downloads
- 8
- Uploads
- 0
With Linux, you don't really have to set up the SDK at all if you just want to use ADB (assumption is that you just want to use ADB). The only real setup happens when you want to actually develop using the SDK, when you need to make sure you have the proper dependencies (like Eclipse, etc.)
Once you get the SDK, find the ADB binary file and copy it (as root) to /usr/local/bin. It will be in your path and you can most likely get rid of the rest of the SDK. That way, when you type "adb" in a terminal shell, it will always be there. It also helps to keep a copy of ADB backed up somewhere in case you reinstall Ubuntu later on, since it's not in the repositories.
Something like "sudo cp /home/me/android-sdk-linux_86/tools/adb /usr/local/bin" should do the trick.
- 02-11-2010, 08:03 AM #3
Itty Bitty Modder
- Join Date
- Dec 2009
- Posts
- 6
- Thanks
- 2
- Thanked 3 Times in 1 Post
- Downloads
- 9
- Uploads
- 0
Did you add android rules to the rules.d folder?
i had to add the vendor id to the android rules to get mine to work though im using ubuntu 8.10 >.>
make a file in your etc/udev/rules.d called 51-android.rules and add
SUBSYSTEM=="usb", SYSFS{idVendor**=="22b8", MODE="0666"
its how i got mine to work
hope it helps ^^
- 02-11-2010, 08:57 AM #4
or you could do what i do
open terminal in the tools directory
and run ./adb as root
(after installing eclipse)Code:sudo ./adb devices
- 02-11-2010, 10:46 AM #5
So I Hear You Can Mod
- Join Date
- Feb 2010
- Posts
- 282
- Thanks
- 1
- Thanked 7 Times in 7 Posts
- Downloads
- 0
- Uploads
- 0
Alrighty, got it set in paths, now just need to figure out why it says "no permissions" when I do "adb devices"
- 02-11-2010, 12:49 PM #6Nexus S: CM7.1 Kang w/Voodoo
Backflip: CM7.1
Cliq: CM7.1
Follow me on Twitter
If you like something I have done & want to buy me a RedBull click HERE
- 02-11-2010, 09:47 PM #7
So I Hear You Can Mod
- Join Date
- Jan 2010
- Posts
- 102
- Thanks
- 6
- Thanked 6 Times in 5 Posts
- Downloads
- 7
- Uploads
- 0
i had this exact problem myself.
when you type
echo $PATH
what do you get?
if your sdk isnt in there you need to add the directory to your path. what commands are you typing?
- 02-11-2010, 10:51 PM #8
So I Hear You Can Mod
- Join Date
- Feb 2010
- Posts
- 282
- Thanks
- 1
- Thanked 7 Times in 7 Posts
- Downloads
- 0
- Uploads
- 0
I put the ADB file in Usr/local/bin like beartard suggested, the ADB command works, just isn't showing my device
- 02-12-2010, 11:48 AM #9
So I Hear You Can Mod
- Join Date
- Jan 2010
- Posts
- 102
- Thanks
- 6
- Thanked 6 Times in 5 Posts
- Downloads
- 7
- Uploads
- 0
what do you mean? like you can adb shell and adb push but when you type adb devices it doesnt show?
and it doesnt need to be there btw. mine is in /home/art/sdk/tools and it works just fine
- 02-12-2010, 02:26 PM #10
Banned
- Join Date
- Jan 2010
- Location
- Winter Haven, Florida, USA
- Posts
- 24
- Thanks
- 0
- Thanked 4 Times in 3 Posts
- Downloads
- 8
- Uploads
- 0
No, it doesn't *need* to be there, but I find that putting all my self-installed (ie, not in the ubuntu repositories) programs in /usr/local/bin helps me out when I want to make a backup before re-installing, upgrading, or trying out another distro. I don't use the SDK for development and ADB is the only tool I need. I put it in /usr/local/bin, forget about it, and delete the SDK. Also, with it in /usr/local/bin, there's no need to cd to the directory or use dot-slash in front of the command.
Last edited by beartard; 02-13-2010 at 08:42 AM.
- 02-12-2010, 08:04 PM #11
So I Hear You Can Mod
- Join Date
- Feb 2010
- Posts
- 282
- Thanks
- 1
- Thanked 7 Times in 7 Posts
- Downloads
- 0
- Uploads
- 0
That's what I get when doing various adb commandssteven@steven-laptop:~$ adb shell
error: insufficient permissions for device
steven@steven-laptop:~$ adb devices
List of devices attached
???????????? no permissions
- 02-12-2010, 08:45 PM #12
So I Hear You Can Mod
- Join Date
- Jan 2010
- Posts
- 102
- Thanks
- 6
- Thanked 6 Times in 5 Posts
- Downloads
- 7
- Uploads
- 0
so you cd to the directory, and for all intensive purposes ill use mine for this:
$ cd /home/art/sdk/tools
/sdk/tools$ ./adb devices
* daemon not running. starting it now *
* daemon started successfully *
List of devices attatched
well right now its not giving ne thing but usually i believe says mb200 then the serial.
from the looks of it your not putting in the ./ in front of your adb commands, try that and see if it helps out, also are you running as su?
- 02-13-2010, 04:53 AM #13
like i said earlier just run:
sudo ./adb devices
and see if that works for you - if it says its already running then:
./adb kill-server
Followed by
sudo ./adb devices
Make sure you run these from within the TOOLS directory in terminal!
- 02-13-2010, 10:18 AM #14
So I Hear You Can Mod
- Join Date
- Feb 2010
- Posts
- 282
- Thanks
- 1
- Thanked 7 Times in 7 Posts
- Downloads
- 0
- Uploads
- 0
I hate this:
Just tried it. It works. I did nothing to fix it. I hate computers!
- 10-13-2010, 07:34 PM #15
Hi,
I'm n00b here , just want to share mine.I'm using ubuntu 10.4 , just now finished download android sdk for linux.I'm extracting to my home dir and name the directory to android and here're the output
Seem it work out of the boxCode:cd android pwd /home/whoiskliwon/android/ cd tools sudo ./adb devices * daemon not running. starting it now on port 5037 * * daemon started successfully * List of devices attached TA1XX0160X device


LinkBack URL
About LinkBacks
Reply With Quote

