adb wont see my device

by » Mon, 13 Apr 2009 12:13:37 GMT

Sponsored Links
 Hi guys

I am a newb, I just started to work the Android SDK, 1.1_r1 , I have
eclipse installed on a Windows Vista 64 box, every thing was going
well, My app was working fine in the Emulator , but things started to
go nuts when I tried to run it on the device (Retail T-Mobile G1 not
the Dev version) the Activity loads, when I click the only button on
there screen, I get a force close error. When I started to research
the problem , I think I may have messed something up because now my
device will not show up then device list in Eclipse and when I run
"adb devices" I get an empty list, also "adb get-state" returns

If any one can help please, I have pulled out what ever is left of my
hair trying to figure this out.


Other Threads

1. Web Runtime Curriculum Advanced v1.0 Beta

Hey Guys
Was going through this great Curriculum from Forum Nokia website,
thought to share it with you.
This set contains the following lectures: WRT widget structure, Ajax,
UI Development, Platform Services, Performance, and Homescreen
Topics covered are:
      Aptana Studio
      UI Design
      Web Technology
      Web Runtime (WRT)
      Widget for S60
Download it here


2. Android Emma Code Coverage

Hi All,

I was trying to generate the Emma code coverage report but it is
giving me 0% coverage every time I run it. In this group I have seen a
discussion regarding the same and the resolution given was as follows:
Finally, the emma code coverage measurement is working for me (for a
custom project). So here are the steps what you need to make it work
(I have tested it, with Java 1.5 on Ubuntu 8.04):

mkdir android-src
cd android-src
repo init -u git:// -b
repo sync

# Add emma.jar to the system/core/rootdir/init.rc
sed 's/\/system\/framework\/core.jar:\/system\/framework\/ext.jar:/\/
framework\/emma.jar:/' system/core/rootdir/init.rc > system/core/
mv system/core/rootdir/init.rc.tmp system/core/rootdir/init.rc

# Rebuild the boot image
make bootimage

# To build the full system image
make -j4

# Set the PATH:
export PATH=${PATH}:/<_path_>/android-src/out/host/linux-x86/bin/

# Build the emma jar itself
make emma

# Setting the environment and additional bash commands. (like
m,mm,mmm, choosecombo etc) Notice the space after the dot!
. build/


# Copy your project to development/samples/<_projectname_> or
# Based on the ApiDemo create an file for the project
directory and the project test directory
# The LOCAL_INSTRUMENTATION_FOR value in test dir has to be
equal with the LOCAL_PACKAGE_NAME defined in the in the
main project dir.
# Compile the Application would like to instrument
mmm development/samples/<_projectname_>

# Set the ANDROID_PRODUCT_OUT directory for the emulator to know the
image location
export ANDROID_PRODUCT_OUT=/<_path_>/android-src/out/target/product/

# Start an emulator with a simulated sdcard:
emulator -sdcard <path to sdcard>

# Remount the drive - it is needed to have a writable drive. without
that sync wont work
adb remount

# Synchronize the local content with the emulator
adb sync

adb shell
# create directory: mkdir /etc/coverageresult

# Executing tests
adb shell am instrument -w -e coverage true -e coverageFile /etc/
coverageresult/ hu.agsoftware.sample.tests/

# Dump a runtime coverage data file:
adb pull /etc/coverageresult/

# Generate a coverage report
java -cp external/emma/lib/emma.jar emma report -r html -in -sp development/samples/<_projectname_>/src -in out/

But I would like to know if there is any other way of generating the
report witout using the above steps. Because I don't have the linux
environment and I don't want to create another build.
Please help me in this regard


3. Are Android apps developed with the NDK slower than their counterparts on other OS's?

4. Samsung Galaxy S2 With HD Touchscreen--Too Good To Be True?

5. Display android screen on projector

6. Default Android Applications

7. XMPP Connection error