Database Develop

Cannot open ddms.bat in order to take screenshots on Nexus One

I wanted to take screenshots of my Nexus One (2.2 FRF91/T-Mobile/Stock) but I'm just a newbie so I followed the guide on andriodcentral Anrdroid 101 tips. (Sorry I can't link to it since I'm a new user on these forums
That guide led me to another guide on how to install the sdk
When I tried to pull my 3rd party apps, cmd didnt do anything it simply said "0 pulled, 0 skipped", however I was able to pull my standard apps. I'm confident the sdk was installed correctly though.
I'm using a laptop with Windows 7 64bit and an AMD processor, I'm not sure if that information is helpful or not
I've already downloaded and installed the android 2.2 sdk, java runtime environment, java development kit. I've also properly installed the ADB drivers for the Nexus One. I also downloaded Eclispe but when I tried to run it, the application won't open. I have a feeling its because I didn't install it properly.
My problem now is that the ddms.bat (Dalvik Debug Monitor) won't open when I double click on it. I tried to right click and run as administrator but that didn't work either. In both cases when I try to open it, a cmd windows opens for a fraction of a second and then closes before I can read it. So I googled it and found a website that seemed to be able to solve the problem but its geared towards linux users.
I specifically followed these directions "To fix this a replace of the bundled swt is needed. The file is located under android-sdk-linux_x86-1.5_r3/tools/lib/. Rename swt.jar to swt_32b.jar. Next download swt for your platform. I have used swt-3.4.2-gtk-linux-x86_64.zip. Unpack the file swt.jar in the zipfile to android-sdk-linux_x86-1.5_r3/tools/lib/ and finally start ddms" but that didnt work either. So now my android-sdk-windows/tools/lib/x86_64 is full of other files rather than just having that swt.jar file.
Can anyone please help on getting ddms.bat to open or on how to get eclipse to open?, I'm so close to being able to take screenshots.
Some notes:
1.I'm not interested in rooting (too worried about bricking my phone), so please don't recommend that I root first.
2. USB debugging was ON when I tried it

TaeKwonDonkey said:
1.I'm not interested in rooting (too worried about bricking my phone), so please don't recommend that I root first.
Click to expand...
Click to collapse
Do you have the right drivers installed?
When your phone is on, plugged in, SD not mounted, and USB turned on, you should see "Android Phone" and "Android Composite ADB Interface" underneath that.
If you don't want to root (it's so easy and painless if you can follow instructions) then I don't know what to tell you other than:
1. Install "USB Deview" and remove all HTC/Google/Android related drivers.
2. Completely uninstall and wipe out the SDK stuff.
3. Rebooted, and reinstall Android SDK, and make sure that Windows7 installs the right drivers.
Installing the SDK is no more difficult than installing any other piece of software. If you've got Java installed, and you've plugged your phone in, and debugging is turned on, what *should* happen when you double-click ddms.bat is, the command prompt window opens, but then the Debug utility should open.
I had the screenshots stuff working before I ever rooted.
I followed the steps here: http://www.knowyourcell.com/google/...take_screenshots_on_the_google_nexus_one.html
Rooting is easy and painless. If you root, you don't have to flash a custom ROM or anything, but then you can install an app that you simply open, enable, then whenever you're doing something that you want to take a screenshot of, you shake the phone, and there it is.

How to install apk's?

Totally new to android, anyone mind explaining?

the command is "adb install <path/name of apk>".
do it from your computer in a shell/terminal.

Do I have to mess with the NDK at al? I thought I saw something on that...

Bump, more info please?

NDK? Did you mean SDK (android for windows developer kit), If so yes. Download and install. Follow the link below for drivers.
http://forum.xda-developers.com/showthread.php?t=882751
Once SDK and drivers are installed, connect the NC. open command prompt (start menu, run, CMD), type adb devices
You should get a return back of some numbers and DEVICE. This means SDK and drivers were installed correctly. Once ADB (SDK) is installed correctly follow this thread.
http://forum.xda-developers.com/showthread.php?t=857732
Post up if you need some more specifics.

fprice02 said:
NDK? Did you mean SDK (android for windows developer kit), If so yes. Download and install. Follow the link below for drivers.
http://forum.xda-developers.com/showthread.php?t=882751
Once SDK and drivers are installed, connect the NC. open command prompt (start menu, run, CMD), type adb devices
You should get a return back of some numbers and DEVICE. This means SDK and drivers were installed correctly. Once ADB (SDK) is installed correctly follow this thread.
http://forum.xda-developers.com/showthread.php?t=857732
Post up if you need some more specifics.
Click to expand...
Click to collapse
Thanks!
Even though I installed the JDK 6u23, the Android SDK installer won't let me install because it doesn't see the JDK installed...

I used the same 623 package, installed that, then reboot, then install the SDK. BTW what OS are you using?

fprice02 said:
I used the same 623 package, installed that, then reboot, then install the SDK. BTW what OS are you using?
Click to expand...
Click to collapse
Win x64... I installed the 32-bit version of the JDK and got it..

If you're totally new, I'd suggest heading over to http://nookdevs.com/NookColor and reading up there.

fprice02 said:
Once SDK and drivers are installed, connect the NC. open command prompt (start menu, run, CMD), type adb devices
You should get a return back of some numbers and DEVICE.
Click to expand...
Click to collapse
CMD is giving me 'adb is not recognized as a command'
The nook drivers are installed, along with the SDK

ironcrotch said:
If you're totally new, I'd suggest heading over to http://nookdevs.com/NookColor and reading up there.
Click to expand...
Click to collapse
This helped, thanks

fprice02 said:
Once ADB (SDK) is installed correctly follow this thread.
http://forum.xda-developers.com/showthread.php?t=857732
Post up if you need some more specifics.
Click to expand...
Click to collapse
My SDK install is in C:\Program Files (x86)\Android\android-sdk-windows
When I run in cmd:
cd\
cd Program Files (x86)\Android\android-sdk-windows\platform-tools
I can run adb commands. The thread wants me to run sqlite3 commands too, but they are in a different directory:
C:\Program Files (x86)\Android\android-sdk-windows\tools
I am pretty confused on what to do

Do you guys use search at all or check the development forum for this device i mean come on its all in black and white.

I don't know what I did exactly, but I managed to install apk's from the root of my SD card
sweet

Please someone help!
After following instructions of Easy USB ADB Installer for Windows, and running adb devices, my nook didn't show up as a device.
Also I tried installing a software and it said application not install.
Thanks in advance

Easier thing to do is go into Settings --> Application --> Unknown Sources then download an APK with your Browser and install it from the Downloads window. I suggest finding an APK for Astro File Manager and get Dropbox, that way you can install Apps straight from Cloud storage.
____________________________________________________
Sent from Nookie Froyo using Tapatalk

Try this Bro, it's the easiest way to get the USB Drivers onto your PC and then your NC recognized.
http://forum.xda-developers.com/showthread.php?t=910008

thereddog said:
Thanks!
Even though I installed the JDK 6u23, the Android SDK installer won't let me install because it doesn't see the JDK installed...
Click to expand...
Click to collapse
I have that same problem, have you found a fix for it yet?
I'm running Windows 7 x64
with an I-7 Processor

[TUT] ADB Guide

Hopefully this helps someone...
If something doesn't work here let me know and I'll add it and make corrections. I will gladly accept recommendations and input from anyone. Also Mac and Linux users please post your info and I'll gladly add your pieces to my guide as well.
Step 1:
Some files are needed such as the SDK and USB driver. Note: Some devices require Windows drivers provided by the manufacturer we will have to play around and see what works with Adam...
System Requirements
USB Drivers
Android SDK
- Download the zip file
Step 2:
Extract the zip and run the exe to install. It should check for JAVA dependencies and get you all setup.
Copy the SDK folder to the root of your C: drive or where ever you want. Plug in the device (Adam in this case), DO NOT MOUNT ANYTHING, and when prompted install the USB driver. NOTE: I'm not sure yet if the drivers in the link will work with Adam or not so play around and see what works. You can always go into Device Manager and remove the driver.
Step 3:
Create environment variables for ADB by right-clicking on "My Computer" and select Properties. Then go to Advanced tab (or Advanced Settings in Vista) and select Environment Variables. Add the following:
Variable name: adb
Variable value: C:\android-sdk-windows\tools
Note: that variable value may change if you do not run the sdk from the root of your C: drive and depending on the name of your SDK folder...
Step 4:
Code:
adb [COMMAND]
If you replace "[COMMAND]" with an adb command, the above should work for you. Go here for a listing of ADB commands...
A simple command to test with is:
Code:
adb shell
"adb shell" should return one of two values, "$" or "#". And this should be the shell prompt from the device, not your local terminal window.
If that code didn't work, put in your full SDK folder path and try again. If it works that way, look into the environment variable and make sure its the same as the path to your SDK folder.
References:
The first is the sweet guide from XDA member VanillaTbone and is widely used here at XDA.
The second is one I wrote over at NotionInkHacks. This one is only for Windows at the time being, but once people with other OSs leave feedback I will update to include those other OSs as well.

Thanks for the links!
They were helpful to me and I am sure they will be to others.

Thank you, stickied! This is useful to people unfamiliar with ADB.

Updated the OP so this is now a full guide. I also updated the title to reflect tutorial.

webs05 said:
Updated the OP so this is now a full guide. I also updated the title to reflect tutorial.
Click to expand...
Click to collapse
Excellent work. This will help all the first time Androiders here!

How to get your Adam detected in Windows
After following this.. you can follow this next to now make sure windows detects your Adam.
http://forum.xda-developers.com/showthread.php?p=12022670#post12022670

it would be more uniform if people installed the .exe and have 2 paths for step 3 depending on 64 bit or 32 bit
for 64 bit when installing the exe the path is
C:\Program Files (x86)\Android\android-sdk-windows\platform-tools
and for 32 bit I believe its (not sure on this one because I have 64 bit)
C:\Program Files\Android\android-sdk-windows\platform-tools
Also might be wise to mention that if you do not define a push or pull path way when you start up the command prompt it will look in C:\users\"UserName"

edit: fixed: http://developer.nvidia.com/tegra/forum/after-installing-froyo-adb-cant-see-device
thanks for your help
howdy,
I have previously installed the adb driver for my sgs and sgs2. When I plug in my adam, the mass storage components come up, but nothing shows up with regards to android devices which will allow me to update the driver for.
Debugging is enabled on my adam (it is a PixelQi/Wifi version running beast+clemsync v3) and shows up in the notifications. USB Mass storage works fine.
ADB also works fine for my SGS2 when I plug it in and run adb shell/devices. When I plug my adam in, adb does not see anything related to it.
Where should I go from here to get windows to like this thing?
edit:
When I plug it in I can see these things:
If the nvidia harmony device shows up in the device manager I don't know where
Click to expand...
Click to collapse

[TUT] Getting Windows to detect your Adam via ADB

How to get ADB to work with Adam by detecting in Windows properly.
Hello I wanted to document a way to get this going so hopefully this helps anyone interested in using ADB with their Adams since the original tutorial seems to lack some important "how-to" parts.
Another thing.. I am only trying to help and add to the adam experience.. I am not a teacher or anything so if you are unsure about a step STOP and go do some research.. this is for someone who already has a general knowledge and to assist those to are trying to learn this.. its not a substitute for learning it yourself.
----------
Here are the steps that you need to follow in order to enable these drivers:
You must have Android SDK installed before you can proceed!!
If you don’t have it already, proceed to download here and you can see a ADB guide found here.
Make sure you download the Google USB Driver Package as well.
Open the google-usb_driver folder that you will find inside your Android SDK folder.
Open the android_winusb.inf file in notepad or any text editor to edit it.
Add these lines under [Google.NTx86] or [Google.NTamd64] depending on whether you are using 32 bit or 64 bit Windows. If unsure, it is safe to add these under both these sections.
Code:
;NVIDIA Tegra
%SingleAdbInterface% = USB_Install, USB\VID_0955&PID_7000
%CompositeAdbInterface% = USB_Install, USB\VID_0955&PID_7100&MI_01
Don’t edit or replace any other text that is already there; just add these new lines and save the file. You can add them right before the
Code:
; HTC Dream
To be able to use ADB and other SDK tools with your device, you can proceed as follows:
On your tablet, go to Menu > Settings > Applications > Development and enable ‘USB Debugging’.
Connect your tablet to your PC via USB. You will get a notification that some drivers were not installed, which is OK for now.
Go to device manager and Identify your device from the list, right-click it and click ‘Update Driver Software..’.
Choose to browse your computer for driver software and then select to pick from a list device drivers on your computer.
Choose to view all devices and click ‘Have Disk…’.
Browse to the google-usb_driver folder inside your Android SDK folder and select the android_winusb.inf file.
If you get any warnings prompts telling you that the driver might not be compatible, just choose to continue installing.
Once the drivers have been installed, you should be able to use ADB with your device.
You will want to connect your device via usb and make sure usb debugging is on. (Settings, applications, development, usb debugging CHECKED!!)
To confirm that your device is recognized, launch a Command Prompt window and enter these commands:
Code:
adb kill-server
adb start-server
adb devices
If you see your device name or a few numbers as the output under the list of devices, your device is now recognized by ADB.
Happy Developing!
--------------------------------------
My Notion Ink Adam Videos

ADB / QtADB
Then there's the easy way .... http://forum.xda-developers.com/showthread.php?t=1009982

stewarta said:
Then there's the easy way .... http://forum.xda-developers.com/showthread.php?t=1009982
Click to expand...
Click to collapse
Well I took a look at your "easier way" and its exactly what I explain to do in my tutorial but maybe others will enjoy your wording better, thank you for your input and for sharing.

[Q] Tons of Trouble with ADB and Fastboot

I'm having a crapload of trouble with adb and fastboot. I've been searching for the last few hours but to no avail. I've downloaded multiple drivers and tried to do everything i can to setup the adb and fastboot. I managed to get the bootloader unlocked and its rooted and usb debugging is enabled. Every time i type "adb devices" into a command prompt it says that adb is not a valid command etc. What the heck am i doing wrong and why is this supposedly simple process so difficult here?? Please help...

Did you use the "cd" command to change the directory to where the platform-tools folder is?
That's assuming you have the Android SDK and Java Dev Kit (JDK) installed already..
Sent from my Atrix HD via XDA-Developers application

pianoman102 said:
I'm having a crapload of trouble with adb and fastboot. I've been searching for the last few hours but to no avail. I've downloaded multiple drivers and tried to do everything i can to setup the adb and fastboot. I managed to get the bootloader unlocked and its rooted and usb debugging is enabled. Every time i type "adb devices" into a command prompt it says that adb is not a valid command etc. What the heck am i doing wrong and why is this supposedly simple process so difficult here?? Please help...
Click to expand...
Click to collapse
Here is installer. Run it under administration mode on windows.
No needs to install the whole android SDK anymore. Enjoy!!
http://d-h.st/FFo
P/s: U still need JDK as Byakko Custom said.

devilsking said:
Here is installer. Run it under administration mode on windows.
No needs to install the whole android SDK anymore. Enjoy!!
http://d-h.st/FFo
P/s: U still need JDK as Byakko Custom said.
Click to expand...
Click to collapse
Ah, thanks so much! That finally got it working after i installed jdk and ran the program. Awesome! time to start flashing!

pianoman102 said:
Ah, thanks so much! That finally got it working after i installed jdk and ran the program. Awesome! time to start flashing!
Click to expand...
Click to collapse
U're welcome

devilsking said:
Here is installer. Run it under administration mode on windows.
No needs to install the whole android SDK anymore. Enjoy!!
http://d-h.st/FFo
P/s: U still need JDK as Byakko Custom said.
Click to expand...
Click to collapse
2 Questions
Does that install the tools in the Windows equivalent of "$PATH" so users don't have to cd to the tools' location.
And do you mind if I link to this in my how-to guide? Credit will be given to you and your team of course.

skeevydude said:
2 Questions
Does that install the tools in the Windows equivalent of "$PATH" so users don't have to cd to the tools' location.
And do you mind if I link to this in my how-to guide? Credit will be given to you and your team of course.
Click to expand...
Click to collapse
Yep. U can do it I'm happy to share this tools with other users :good:
About the location, I set the installation path to C:\Windows so it means that it can be used as an windows services whenever u call it on cmd. No needs to set the location.
For example: If users use command "adb devices", it will work immediately and show the result. However when they want to decompile an apk and put file in a folder named "X", it's needed to use cd command to set the location in cmd to "X" then use adb/apktool/fastboot as normal without having adb/apktool/fastboot files in "X" folder. It helps to define the location of apk file, not the apktool/adb/fastboot.
Hope u can understand my idea =.= Sometimes, my explanation is really not good becoz English is not my mother language

devilsking said:
Yep. U can do it I'm happy to share this tools with other users :good:
About the location, I set the installation path to C:\Windows so it means that it can be used as an windows services whenever u call it on cmd. No needs to set the location.
For example: If users use command "adb devices", it will work immediately and show the result. However when they want to decompile an apk and put file in a folder named "X", it's needed to use cd command to set the location in cmd to "X" then use adb/apktool/fastboot as normal without having adb/apktool/fastboot files in "X" folder. It helps to define the location of apk file, not the apktool/adb/fastboot.
Hope u can understand my idea =.= Sometimes, my explanation is really not good becoz English is not my mother language
Click to expand...
Click to collapse
Thanks.
That's what I thought it did. I was going to do something similar, but I couldn't remember if the correct folder was and I was just too lazy to do the research and find out. I was thinking System32, but its been so long that I couldn't remember.