Android : Cannot Run / Debug With Eclipse 3.5.1 On Windows
Nov 10, 2009
I installed and eclipse, android sdk and tried the first "hello, android" tutorial but nothing happened on the AVD There are no compilation error, I tried to set break points in the but it does not seem like the application started running at all...
I am using Windows 7 64bit and I am trying to get my computer to detect my HTC Desire, but it's not picking it up. I have everything available installed through the Android Updater and I have got my phone running through Ubuntu, so it is definitely a problem with Windows.
I am using Windows 7 64 bit. I have a HTC Desire running Stock 2.2 (Froyo) that works with USB Debugging on my Ubuntu machine. Windows does detect that my phone is plugged in. It shows as a mass storage device. I have all the available things installed via the Android Updater.
I want to debug on my device and I am using a Windows 7, 64 bit, but I can't find correct drivers to do so. The perspective in Eclipse is whether changing nor halts the IDE at any breakpoint.Can you send me any suggestions how to use debugging?
I have mostly been avoiding debugging when I can because of these two problems, so hopefully someone here has suggestions to avoid them:
1. It seems that I have to build the SDK (`make sdk`) and copy it off to a directory for Eclipse to use almost every time I want to debug. I haven't followed through the "sdk" directive, so I'm not clear on why this is necessary instead of just having Eclipse read from the source in my directory. Isn't there some way for it to do this? FYI: I have a (modified) full checkout of Donut, not just the SDK.
2. How can I debug without using Eclipse? I would really like to be able to use something like gdb/jdb.
In Ubuntu, I have double checked the udev rules. They all look perfect. (I cross checked using another phone too). The USB debug mode doesn't show up no matter what. And I have the adb_usb.ini in the right place. I have tried running all possible combinations of running adb, adb start-server as root. But
adb devices shows no devices at all.
However, with the USB debugging option enabled on phone, it worked on Win7 after windows installed a Common handset driver.
If I go back to Ubuntu without disconnecting the cable and do
Code: $ adb devices * daemon not running. starting it now on port 5037 * * daemon started successfully * List of devices attached 1234567890ABCDEFdevice
The product id is 1234567890ABCDEF and I am able to see it and everthing works fine!!But the moment I disconnect the USB cable, its gone.
So I guess it's not the development machine that is at fault. The device seems to be setting a property while in Windows which stays latched till the usb connection goes off.
Btw the Code:
/data/property/persist.service.adb.enable is 1 too.
I can no longer run/debug my application in eclipse, when I attempt to I get the following error in the console:Installation error: INSTALL_PARSE_FAILED_NO_CERTIFICATES.E/PackageParser( 65): Package com.example.foo no certificates at entry assets/community_error.html; ignoring.I have not touched my android config or project configuration, and it was working fine yesterday, i'm running ubuntu/jaunty, i did a kind of security update this morning and i think it might have broken zlib or something.
I am trying to following this documentation 'http://source.android.com/using-eclipse' to debug android Launcher Activity in eclipse.
It said' You may need to open the Debug perspective (next to the "Java" perspective icon in the upper-right, click the small "Open Perspective" icon and select "Debug"). Once you do, you should see a list of threads; if you select one and break it (by clicking the "pause" icon), it should show the stack trace, source file, and line where execution is at. Breakpoints and whatnot should all work.
My question is which threads I need to select in order to debug Launcher Activity? I don't see a thread name Launcher.
I have set up a "Debug Configuration" to debug my Android project. However to get it to debug on a device (HTC Desire) I have to set the Configuration's "Target" to "Manual", there seems to be no way to set in the Debug Configuration that it should go to a selected Device.
It does work, but each debug session I have to "Manually" choose the HTC device from the dialog. Can I set it to always to go the Device?
I'm using Eclipse and have an emulator running Android 2.1 and my IntentService. I'd like to step through my onHandleIntent() overridden function. I've put in a breakpoint on the first statement of the function, which is Context context = getBaseContext();. When the intent is called the program just fails and does not go to debug view in Eclipse.
I am using eclipse android plugins to build a project, But i am getting this error in the console window: [2010-02-03 10:31:14 - androidVNC]Error generating final archive: Debug certificate expired on 1/30/10 2:35 PM!
I uploaded my application to Market and then downloaded it to my phone. Now I'm unable to use debug keystore which is used by default by Eclipse ADT Plugin (Re-installation failed due to different application signatures) and when I'm trying to setup own keystore in Eclipse->Windows->Android->Build->CustomDebugKeystore, I'm unable to enter password or accept keystore and type password later. Is there anything I can do or only way do debug app on device is to uninstall market version and deal with default debug keystore?
I have an application I am writing for Android that basically does a screen scrape of a large table on the web and presents it in a nicer way on the handset. Its 500k of html and takes about 20 seconds or so normally.
When I have my phone hooked up to the computer, I used to be able to just click on "Run" and my code would execute similiarly speedy, as opposed to Debug where it would take 10 minutes to complete.
Now, however, clicking "run" behaves just like debug mode.... I don't want this overhead, how do I get eclipse to stop sending my app to the debugger already? I have searched online and found a couple people with the same issue, but simply rebooting my phone doesn't fix it, and there have been no other solutions posted that I have found.
This is more of an Eclipse error than an Android or Ant error. My Eclipse project won't build because when it sees the build.xml created from the Android command, it starts looking for the debug and release commands. Well, since they are dynamically generated from the <setup> task, they don't exist. So now Eclipse (Build id: 20100218-1602) locking the project from build/run based on these errors. kay.. so here is the weird part: It worked this morning. In fact it has been working for weeks with the build.xml file sitting there. All I did was edit the build.xml file in Eclipse (changed some constants). Ant thinks everything is peachy.
i install new version of eclipse and Android sdk , but when i run an android project i get this error
Could not open Selected VM debug port (8700). Make sure you do not have another instance of DDMS or of the eclipse plugin running. If it's being used by something else, choose a new port number in the preferences. ADB server didn't ACK * failed to start daemon * i try to solve the problem by following this , but i still get the same problem:
-Window -> Preferences -> Android -> DDMS -Set Base local debugger port to "8601" - Check the box that says "Use ADBHOST" and the value should be "127.0.0.1"
i am also tryng to reinstall android pluing for ecipse and even the android sdk , but i still get the same problem!
I've tried to search for similar problems, but can't seem to find it.
Windows 7 Java SE Developement Kit x64 Eclipse Helios (downloaded here from Eclipses homepage --> Downloads --> Eclipse IDE for Java EE Developers --> 64 Bit) "Android SDK Windows"
I've been following the guide from the Android Developers homepage.
I can launch Eclipse just fine. Under Help --> Install New Software ... Here, I give it a name myself (Android Plugin Test), and under location, I've typed "http://dl-ssl.google.com/android/eclipse", as said in the link. Then it find Developement Kit, and I install it and all that & restart Eclipse.
The following are now installed: - Android DDMS - Android Development Tools - Eclipse IDE for Java EE Developers
So everything seems fine. BUT .. When I go to Window --> Preferences, "Android" is missing. I have no problems seeing General, Ant, Data Management etc.
So my question is, what's the problem ?
As said, I downloaded Android SDK, but when I try to run the setup, I get this error, about missing Java:
And that's where I'm lost. Because, under installed programs, it says: - Java(TM) SE Developement Kit 6 Update 21 (64-bit)
And yes, I have restarted after installing Java.
For some odd reason, it's not possible for to run the SDK setup with any compatibility. It's greyed out (Yes, I'm admin, and I don't have any problems on other programs)
I checked the Requirements for Android SDK, and it says Windows XP & Vista, but not 7 .. But as far as I know, other people got it to work.
I am having a lot of problem getting Eclipse with Android plug-in to work on Windows 7 64K. I am getting eclipse not responding a lot. It seem to happen pretty randomly. I know that Windows 7 is currently not support for Android SDK.
However has anyone got this to work ?
I am using the following: - Windows 7 64K - eclipse galileo (3.5.2) - JDK 1.6.0_21 64k
On my brand new Windows 7 machine, I downloaded Eclipse (Galileo) and several Eclipse plugins (Android's ADT plugin, Subclipse, etc.) After rebooting, neither of these plugins are showing up in the IDE (nothing in the preferences, menus, etc.) but if I click "Installation Details" in the 'About Eclipse' popup, I see all of the plugins listed as Installed Software. (ex. Android DDMS 0.9.5, Subclipse 1.6.5, etc.) How do I get my plugins to work?