i have downloaded the android sdk for the saphire and am having trouble in the command prompt with the given command. the wiki says to put adb and it should run smoothly but this is not working for me.
I saved the .zip file in a new folder at C:\androidSDK and it is still not working.
Can anyone help me PLZ!?!
Two quick questions; any help is much appreciated. As a newbie I am unable to get adb to detect my device; running 'adb devices' always yields an empty list under Windows 7. Searching different threads lead me to the recommendation to uninstall the mass storage device driver with USBdeview and then reinstall with the android usb driver (which is said to be under tools in the SDK); however, I can't find the driver file anywhere., nor is there an USB available package in the SDK. If someone could point me in the correct direction regarding how to run adb I'd be much appreciative; I have the SDK installed and the adb daemon appears to be running.
A quick second question is if I can get the device to be detected under adb, can mass storage driver and the android driver run simultaneously? Thanks again.
Duffyxy said:
Two quick questions; any help is much appreciated. As a newbie I am unable to get adb to detect my device; running 'adb devices' always yields an empty list under Windows 7. Searching different threads lead me to the recommendation to uninstall the mass storage device driver with USBdeview and then reinstall with the android usb driver (which is said to be under tools in the SDK); however, I can't find the driver file anywhere., nor is there an USB available package in the SDK. If someone could point me in the correct direction regarding how to run adb I'd be much appreciative; I have the SDK installed and the adb daemon appears to be running.
A quick second question is if I can get the device to be detected under adb, can mass storage driver and the android driver run simultaneously? Thanks again.
Click to expand...
Click to collapse
Look about 1/2 way down in the first post here:
http://forum.xda-developers.com/showthread.php?t=827209
Two quick questions; any help is much appreciated. As a newbie I am unable to get adb to detect my device; running 'adb devices' always yields an empty list under Windows 7. Searching different threads lead me to the recommendation to uninstall the mass storage device driver with USBdeview and then reinstall with the android usb driver (which is said to be under tools in the SDK); however, I can't find the driver file anywhere., nor is there an USB available package in the SDK. If someone could point me in the correct direction regarding how to run adb I'd be much appreciative; I have the SDK installed and the adb daemon appears to be running.
A quick second question is if I can get the device to be detected under adb, can mass storage driver and the android driver run simultaneously? Thanks again.
Click to expand...
Click to collapse
i downloaded "pda net " to my windows 7 64 bit pc when i was having the same usb issue, it then recognized my adb device(of course you have to uninstall the drivers that windows assigned to it first)... question 2 is yes!
Sent from my VEGAn-TAB-v1.0.0b2 using Tapatalk
You can always try Wireless ADB:
http://www.appbrain.com/app/adb-over-wifi-widget/bohlool.net.wifiadb
Wiki entry on setting up adb here: http://wiki.tegratab.com/index.php/Setting_up_ADB
aver2one said:
i downloaded "pda net " to my windows 7 64 bit pc when i was having the same usb issue, it then recognized my adb device(of course you have to uninstall the drivers that windows assigned to it first)... question 2 is yes!
Sent from my VEGAn-TAB-v1.0.0b2 using Tapatalk
Click to expand...
Click to collapse
You mentioned that you had to first uninstall the drivers that Windows assigned to it first.
Would you please share how you went about doing that? I've been stuck on this part (adb not recognizing my device) for quite a while now and can't seem to get past it.
Any help would be greatly appreciated.
Thanks much for the replies.....
Thanks. I tried each one but only the pad net worked. Regarding the second reply, there was no usb_driver folder in my Android SDK folder. I downloaded the inf file anyway but when I pointed to it during installation it gave me a 'file not found' error although it recognized the driver. PDA net worked fine. The adb wireless widget connected to my PC but the list of devices remained blank.
Thanks again for l the suggestions; perhaps as I become more knowledgeable I'll appreciate why the first and third suggestions didn't work, but I really appreciate your willingness to help.
Duffyxy said:
Thanks. I tried each one but only the pad net worked. Regarding the second reply, there was no usb_driver folder in my Android SDK folder. I downloaded the inf file anyway but when I pointed to it during installation it gave me a 'file not found' error although it recognized the driver. PDA net worked fine. The adb wireless widget connected to my PC but the list of devices remained blank.
Thanks again for l the suggestions; perhaps as I become more knowledgeable I'll appreciate why the first and third suggestions didn't work, but I really appreciate your willingness to help.
Click to expand...
Click to collapse
The reason you had no usb driver folder is because the android sdk was not fully setup. You need to run the sdk setup file in the android sdk folder first and download the rest of it. There are a bunch of different packages available. Follow the prompts.
To connect by wifi you need to use one of the adb wifi widgets on your tablet. When it is ready it should give you an address to connect to.
Then on your pc from a command line change the directory to your tools folder in the android sdk. Then type adb connect "address from adb wifi widget" and hit enter. Should then connect.
Sprdtyf350 said:
The reason you had no usb driver folder is because the android sdk was not fully setup. You need to run the sdk setup file in the android sdk folder first and download the rest of it. There are a bunch of different packages available. Follow the prompts.
To connect by wifi you need to use one of the adb wifi widgets on your tablet. When it is ready it should give you an address to connect to.
Then on your pc from a command line change the directory to your tools folder in the android sdk. Then type adb connect "address from adb wifi widget" and hit enter. Should then connect.
Click to expand...
Click to collapse
Thanks again! The wireless adb directions worked, although I should note that adb.exe is in the "platform-tools" folder and most references suggest it should be in the "tools" folder.
I thought I had installed the SDK correctly using the .exe file but, after downloading a number of packages, no USB package was available. After seeing your post I uninstalled, downloaded the zip version, ran android.bat update SDK and it again installed available packages but no USB; these included Android SDK tools, rev 8, SDK Platform tools, rev 1, documentation for SDK API 9, SDK Platform for vers 1.5 - 2.3, and several sample packages. Under 'Available packages' no USB package is listed, and there no .inf file in any of the installed directories.
Any thoughts? Could the inf file be located somewhere else?
Duffyxy said:
Thanks again! The wireless adb directions worked, although I should note that adb.exe is in the "platform-tools" folder and most references suggest it should be in the "tools" folder.
I thought I had installed the SDK correctly using the .exe file but, after downloading a number of packages, no USB package was available. After seeing your post I uninstalled, downloaded the zip version, ran android.bat update SDK and it again installed available packages but no USB; these included Android SDK tools, rev 8, SDK Platform tools, rev 1, documentation for SDK API 9, SDK Platform for vers 1.5 - 2.3, and several sample packages. Under 'Available packages' no USB package is listed, and there no .inf file in any of the installed directories.
Any thoughts? Could the inf file be located somewhere else?
Click to expand...
Click to collapse
I have seen the same thing with the locations. I just copied the files in the platform-tools folder to the tools folder. Send me a pm with your email and i will send my USB folder if you want.
Hi. I 'figured' it out (if it could be called that). rather than click on 'update all' in SDK manager, I selected Android SDK tools, then clicked 'update all' which gave me a series of archives options, one of which included the USB package. This was very non-intuitive but worked.
Thanks!
Cool.. Don't forget to use the modded info file.
Sent from my VEGAn-TAB-v1.0.0b3 using Tapatalk
Last night I was doing a fresh install of Sabayon and one of the first things I setup was eclipse and the Android SDK. I thought I should let everyone know that the new SDK moves ADB from the 'tools' folder to a new folder called 'platform-tools'.
So you may need to change your environmental variables (in windows) or .bashrc file (in linux) to reflect this change. Otherwise ADB won't work. Most developers will already know this but new people and non devs will find the instructions for setting up ADB wrong as far as the path is concerned.
Ex:
c:\android_sdk\platform-tools
or
/home/[user_name]/android_sdk/platform-tools
Thanks, though this changed from v8 (2.3) of the SDK, when adb was also moved out of the SDK starter package and into an add-on.
Oh, so it was changed already in a previous update?
I'm more of a terminal guy myself (and use .sh scripts in recovery) and it shows now
So I'm trying to root my G2 on my mac. I've installed the sdk but when I go to run the android tool I get an error message in my command line. Is anyone else experiencing this?
I rooted using my mac, use the Android SDK often and may be able to help here.
What guide are you using, and what android tool are you referring to?
when I open terminal and run the "android" file from the sdk and instead of launching the sdk manager I get an error in terminal saying "cannot find sdkmanager.jar"
Hello everyone
Have you ever been bored in a borrowed pc and wanting to try out a new library/idea on your android but dont have admin privileges to install all the needed android tools? I was in this exact same situation, so i decided to engineer a solution (After all, i AM an engineering student ) to this boring problem. This solution works almost entirely like a standard Android SDK install (Only downside: Eclipse won't run your application) and has only been tested on Ubuntu Linux so you are on your own on other platforms, but the principle is the same, it might work after all.
Whenever prompted for a platform choose x86 , x64 needs ia32-libs which you cant install due to not having admin privileges
1. Create a directory for all the files and folders (I'll name mine "Development")
2. Download the JDK tar.bz file from http://www.oracle.com/technetwork/java/javase/downloads/jdk7-downloads-1637583.html (You'd better search for an updated link when you read this tho) and extract it into Development
3. Download eclipse from http://eclipse.org/downloads/ (I used the Eclipse IDE for Java Developers) and extract it into the Development folder
4. Download the Android SDK from http://developer.android.com/sdk/index.html (If you are on windows, choose the zip!. Again, i've only tested on Linux so you are on your own) and extract it into the Development folder
5. Open the tools/android (It's a shell script) file with gedit/any other editor and edit the line containing java_cmd=".." to read java_cmd="/home/xxx/Development/jdk1.7.0_06/bin/java" (This is my case, make sure this line actually points to the place where you extracted the jdk zip, else this will fail)
6. Open a terminal, cd to the location where you extracted the android sdk, then type "./tools/android" and press enter (Without the quotation marks) to start the sdk manager, install the platform-tools package, the Jellybean (4.1) SDK, and any other SDK you may want, then close the SDK manager.
7. cd to the Development folder and run this "./eclipse/eclipse -vm jdk1.7.0_06/bin" (Assuming you kept the stock folder names from the zips) to run eclipse, then install the ADT as described here http://developer.android.com/sdk/installing/installing-adt.html.
8. When eclipse restarts, it will ask you for the android sdk, just point it to the location where you extracted it.
That's it, your eclipse installation is ready for you to write code.
Now, to debug you'll need to do so manually as eclipse won't somehow recognize this workaround to the usb priviliges (Linux won't allow adb to communicate with the phone unless it's ran as root [Which you can't, that's why you are here] or a configuration file [Again, written as root] is present) system so you need to do this to make adb work:
1. Disconnect your phone from 3G (Optional)
2. Connect your phone to your pc via usb
3. Enable usb tethering on your phone
4. Enable ADB over Network on Application settings
5. On the terminal emulator, run "ip addr show" and look for the usb section
6. On your computer, open a terminal and cd to the tools directory fo the android sdk, then type "./adb connect xxx.xxx.xxx.xxx" (Replace the x's with the IP of your phone, as it appears on the output of the previous command. Remember to use the one on the USB section)
7. Verify adb picked up your device by runing "./adb devices", if it lists an IP as a device, you are ready
Each time you want to test your app, export a signed apk from your project (I may write a small guide for that later, google will help you if you dont know how to do it) and run "./adb install xxx.apk" (Obviously, replace xxx with the path to your exported apk). The icon(s) for your main activity(ies) will promptly appear on your launcher. Again, Eclipse won't run nor debug your app using this method. (Maybe it's an SDK bug?)
I know it's not exactly streamlined but it's something for when you are on the go.
Hope you find this guide useful someday. Until next time.