John,
I am developing on a Moto Milestone, which is essentially same phone.
Pull down the status area.
Select the item with the USB icon ("USB connection management, or
something like that), not the triangular one.
Choose "Portal & Tools" from the list that pops up.
This will make the phone visible to adb and Eclipse - assuming the
drivers really did install correctly.
You might be prompted to install additional drivers at this point
(actual adb driver).
-- Kostya
12.08.2010 3:25, john brown пишет:
Hello,
I am trying to connect a Verizon Motorola Droid (Android 2.1) to my
computer and Run my application on the device. I have followed the
instructions on developer.android.com about how to "install the USB
driver" and "set up the device for development".
Specifically, I installed the Usb driver from whithin Eclipse
(galileo) using the Adnroid SDK and AVD Manager. (I checked adb at
this time and no recognition.) Then I installed the driver in windows
(XP) via Start> Control Panel> Add Hardware. The windows
installation seemed to work because during or after the installation
of the C:\android-sdk-windows\usb_driver some window came up and
announced that the "adb bla.. bla." was installed successfully.
On the device I have enabled debugging via Settings> Applications>
Development> USB debugging is checked. I also bring down the tri fork
thing and "mount" the sdcard. I can successfully copy files to and
from the device sdcard.
My application successfully runs on the ADV and I can access the ADV
sdcard using "adb push" and "adb shell".
With the moto droid connected, mounted, etc, if I run the command
prompt adb command "adb devices" the resulting list is empty. No
devices recognized.
With the ADV running and the moto droid connected, mounted, etc, if I
run the command prompt adb command "adb devices" the resulting list
shows only the "emulator-5554 device". (this is the same thing it
shows if the moto droid is not connected and only the ADV is running).
If I "Run" from Ecipse with the device connected, debugging, and
mounted, an instance of the ADV is launched and the program runs on
the ADV, not the device.
I cannot get anything to recognize that the device is connected.
My conclusion is that the android debug bridge, adb, is not
recognizing the device.
I would appreciate any suggestions on how to get adb to recognize and
work with my device.
Thanks to all persons for previous favors and advice. John Brown
P.S.
Verizion website has a "fix for device not recognized" that is called
"DriverBoost" and will update all your USB driver to the "official"
version. I did not like the sound of Verizon "fixing all my drivers"
when I am only having trouble with Verizon's Moto droid but I
downloaded it anyway. this is the actual quote:
"DriverBoost scans your PC and uniquely identifies each and every
device driver. Then using a sophisticated matching algorithm every
device driver on your PC is matched with the latest version of that
driver on our proprietary database. New drivers are then quickly
downloaded onto your computer."
I went to install DriverBoost and it quickly informs me that the first
thing it will do is install the latest version of Microsoft.net. I
DROPPED IT LIKE A HOT POTATO.
--
Kostya Vasilev -- WiFi Manager + pretty widget -- http://kmansoft.wordpress.com
--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
