I've been developing on the simulator, but now I have a real device.
adb can see the device (from adb devices), and I've installed Eclipse/ ADB.
I can't work out how to get debug to use the device instead of the simulator though.
View 2 Replies
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 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?
View 3 Replies View RelatedI 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.
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...
View 2 Replies View RelatedI created one android application it is using one native method. I created shared library using ndk tools.My jni function is having some problems i want to debug it. How to debug it in eclipse tool
View 2 Replies View RelatedI 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.
View 2 Replies View RelatedThis is the error that eclipse gives with the latest Android SDK code...
Linux myubuntu 2.6.28-16-generic #55-Ubuntu SMP Tue Oct 20 19:48:24 UTC 2009 i686 GNU/Linux
java version "1.6.0_13" Java(TM) SE Runtime Environment (build 1.6.0_13-b03) Java HotSpot(TM) Server VM (build 11.3-b02, mixed mode)
Any clues on how to solve this error?
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'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.
View 1 Replies View RelatedI need to debug android's java framewoek layer like telephony so how to debug that.
View 3 Replies View RelatedDoes anyone know how to DEBUG build an APK and launch it directly with Eclipse?
in my case, no matter whether i use Run> or Debug> menu command in Eclipse, my apk always logs Config.DEBUG as "false", although obviously the apk is signed with the key in factory debug.store.
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 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.
View 3 Replies View RelatedI am running Eclipse on Win32 and my Android emulator on Linux.
Is there a way to use Win32 eclipse to debug code on the emulator that runs on Linux?
Why should the debugger don't make breakpoints stop when running an android app on Eclipse ?
View 4 Replies View Relatedi install new version of eclipse and Android sdk , but when i run an android project i get this error
Code:
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:
Code:
-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!
OS : debian6 x64bit
IDE : eclipse juno
I'm new to Android development, and am attempting to run a test application on my actual device. I followed the instructions at http://developer.android.com/guide/developing/device.html (and related links), but the Android Debug Bridge (adb) doesn't recognize my connected device.
Some quick background info, I'm running WinXP, developing with Eclipse, with a Motorola Droid running Android 2.1 as my physical device.
An overview of the steps I've taken: Installed the Android SDK, downloading all necessary packages. Enabled USB Debugging on my device. Connected Device via USB, installing the driver from the SDK folder.
I'll stop here (though I continued to setup my application to be debug-able in Eclipse), because I at this point I noticed a problem.
Running "sdkoolsadb devices" at this point (at least, by my understanding), should list my device as connected. However, running this yields only: List of devices attached
My device recognizes that it's connected to a computer in debug mode, and my computer recognizes the device. However, I can't seem to get the sdk to recognize it. I'll leave out the steps I used to setup Eclipse for debugging on a device, as it doesn't seem relevant to the problem. I'll include them if requested.
I have a HTC Desire which i would like to debug and run my Android application on. But when i in Eclipse gets the Window where i can choose between devices my HTC Desire is listed with only questionmarks (???).
I have tried this:
Enabled USB Debugging on my device and enabled debugging in my application Manifest.xml file.
In Terminal i have do this:
1. Log in as root and create this file: /etc/udev/rules.d/51-android.rules.
2. SUBSYSTEM=="usb", SYSFS{idVendor}=="0bb4", MODE="0666"
3. sudo service udev restart
I developer a android app. Today I get the HTC hero for testing. I installed the driver and can start the app on the device. The problem is that I need a network connection. I am connect via usb to my desktop computer. Can the device that is on usb connect use my i-net connection to send a request?
View 2 Replies View RelatedI'm trying to develop an android application that uses network connection. The server is up and running, but when i am trying to access it from the device that runs the android app (in debug mode-using eclipse) it outputs a message that 'cannot find the server' after a UnknownHostException occurs! I have tested the server with a java application and it works fine! What is the problem then with the device?
View 1 Replies View RelatedWhen I'm using the device and click on my debug the application is lunched in my device but I cant see the break points .
In the debug window the application whom run is shown for a second and then disappear and I cant debug my application on the device .
Did I miss something ? can someone please explain me what I did wrong and correct me
I need test my Android app on a Motorola Cliq but don't have one. Is there a testing service that will let me make a debug connection to that device so I can run some tests and find out where the code is failing. Video connections won't tell me that.
View 2 Replies View RelatedWhat kind of permission/Flag do I have to add to the manifest to debug my application on an actual Android device?
View 1 Replies View RelatedIs there a way to debug Android source code with eclipse?
View 4 Replies View RelatedI have a completely broken screen/lcd/digitizer on my Samsung Galaxy S3, debug mode was not on. The phone works as it will still vibrate when turned on and the LED / Menu / Back buttons light up during a boot. USB connector works as well. The phone was not previously rooted.
I had most important data on the sd card and I've already wrote off any other data on the phone as I've since moved on to a GN2. I would like to make use of the S3 (not necessarily as a phone but a server, security camera, etc.). I've read several posts here about my options and looked at numerous google articles, all seem to require debug mode being on or assume/require the data/OS must remain as this is what the user is trying to recover. I do not care if all data is lost on the phone, I just want to make the device useful again.
Am I out of luck if debug mode was not enabled or can I flash through adb via some obscure mechanism? Also note that fastboot is not an option here as the S3 (samsung) does not have it enabled. I am unable to get into "Download Mode" as I cannot see info on the screen.
I have tried with zero success to get a USB debug connection from a WinXP dev box to a brand X Android 1.6 tablet. I believe I had everything configured correctly on the Android and installed correctly on the dev box, but when the two are connected with a USB cable NOTHING HAPPENS; i.e. Windows finds no new hardware much less a new USB device; therefore, I cannot then install the Android SDK USB drivers on Windows and do the debug thing with Eclipse.
Either the mfg of the Android tablet device has disabled USB debugging and just didn't remove the UI that appears to enable it -- or I've left out some crucial step(s). (The device manual is 100% Chinese and I'm 0% Chinese, so it's no help. The tablet is very nearly, but not, the model A84 7" touch screen 'laptop' at 'www.lezestar.com' in case this helps.)
On the tablet:
- 'Settings/Application/Development/USB Debugging' is enabled.
- Tried 'Settings/Application/Development/Allow mock locations' enabled and not.
- Has 500MB internal flash 'hard disk'
- Has installed 2G SD card
- Firmware: 1.6
- Kernel: 2.6.29-002360g4f8dbbb-dirty
- Build No: 1.7.3
On Dev box:
- Windows XP SP3
- Device Manager finds no 'new hardware' when XP<-->Android USB cable is connected.
- Neither USBDeview.exe (Nirsoft) nor USBView.exe (Microsoft) find any evidence of connection with the Android
- Eclipse Galileo (3.5.2) with Android SDK (for 1.6) and ADV Manager.
- USB Driver package, rev 3. downloaded using ADV Manager.
Other:
- USB ports on both Tablet and dev box successfully connect a USB mouse.
- Tablet and Windows XP have been rebooted often.
Is permanently disabling debugging something that Android manufacturors are allowed to do and therefore I'm trying something that can't be done?
If the mfg has 'disabled' debugging, is there a way to work around this; e.g. download a tool that can change Android OS configuration to reenable it?
I have a brand new Nexus One. I'm trying to follow the directions for installing the USB driver. When I plug in the device, it doesn't start the New Hardware Wizard, as the documentation suggests. I can run hdwwiz.exe to launch it and manually install the driver, but when I do, Device Manager says: "This device cannot start. (Code 10)"
View 4 Replies View RelatedFor others who might choose to do debugging on CLI , here's how.
View 2 Replies View Related