The problem I am having is that when I run a FWVGA or WVGA sized emulator it sometimes runs at a MDPI size instead of HDPI. Here is an example with pictures. I create the AVD with the proper hw.lcd.density setting and screen size and it randomly does this. There doesn't seem to be a pattern. I used to be able to just delete the AVD and create it over again and it would fix itself for a while but now it's getting worse.
I'm trying to debug my native JNI code located on a shared library. I have been trying to debug using gdb/gdbserver.
Here is how I go about, trying to debug:
How to debug JNI native code on the Android emulator I'm using gdb/gdbserver I do this at the emulator terminal gdbserver localhost:
when I step on the Android Java code so the function Java_testJNI_printHello is called, I get this error on the server side gdb: Unable to get location for thread creation breakpoint: requested event is not supported
When I am developing for Android and repeatedly running and/or debugging an Android app in the emulator then about every two hours or so I get an Out-of-memory exception, occasionally also an out-of - resources- or out-of-GWT-handles exception. At that point one can only stop and restart eclipse. Apparently the ADK must be doing something wrong, because I have been developing with Eclipse now for 5+ years and I normally never see this. ADT is a really the exception here. Is there any setting or patch that helps top avoid this? I have already given it more heap space (750M) to stretch the time between these hickups a bit, but that approach isn't really sustainable.
This is using Eclipse 3.5 (Galileo) and the Android SDK r06 running a FroYo AVD.
After deleting a phone device from the emulator, I can no longer hit the green triangle button in eclipse and have it launch my application in the emulator. I had been developing for 2.0.1, but then decided to try my app out in 2.1. I created a phone device for 2.1 and tried running it. I encountered some problems. Eclipse pops up a dialog box: Problem Occurred, Launching "my app" had encountered a problem. An internal error occurred during: 'Launching my app". When I look at details, it says: An internal error occurred during: "Launching Pingo". java.lang.NullPointerException.
I have an app that has a few checkboxes in the settings and then compiles a remote sql based on the checkboxes selected. i ran it in the emulator and it's fine. but then i exported it and published it as an app, and the same checked boxes aren't being passed correctly. i wonder if it's a caching issue or something. tried deleting the apks a few times and republish but to no avail. i "fake-edited" the source java and then export again, still no difference.
I'm kind of new to eclipse but is there a force build option? i only see build-automatically option under project but not sure how i can make sure that the apk exported is the same as run in the emulator
edit the emulator is version 1.5, and my phone is nexus one running 2.1- not sure if that makes a difference
I have written a simple Authenticator service to work with the new AccountManager API introduced in 2.0. When I launch a test app that uses the authenticator the authenticator service is launched (as expected) and it's onBind method is called. However, if I run my test application a second time in the same emulator (without restarting the emulator) my service is not launched and onBind is not called.
So far the only way I have found to get my service to launch and onBind to call again is to restart the emulator, which is a very time consuming process. I have looked at the Devices view in Eclipse and ensured that all of my processes have been killed, just in case one of them was just being rebound to or something.
Yesterday, my app worked fine on the emulator, but today after the app launches, I can't click on anything when the app runs. The code hasn't changed, my OnClickable event is wired up correctly and there are no errors in the compiler. I can't hit a breakpoint in the debugger. All the output in the console looks normal.
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.
I have an app the runs fine on my emulator and my incredible with android 2.2. Users say my app won't run on the galaxy s. What options exist to troubleshooting this? Is there a special agreement for galaxy?
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 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 recently downloaded the latest NetBeans IDE (for MACOSX) and imported/migrated a project over from the ECLIPSE environment.Everything looks, and works well... except that EMULATOR gets stuck "waiting for the debugger to attach." I tried "Attaching Debugger." and set the PORT value to every case I've ever read about (8200, 8700, 5555, etc.) but the connection is refused.I am of the opinion that this is not the preferred way to start a debugging session in NetBeans for Android.
I've got some trouble with the media backend (mostly Stagefrightplayer) in Android, and I'd like to understand why it throws the errors it does. The errors are usually device spesific, so debugging on an emulator wouldn't be sufficient.
I've also gotten the player to bork completely and spit out a traces.txt.
Is there a way to debug what's happening, just like I debug Java code?
I am programming Android applications, and the best way here may or may not be the same as Java in general.I simply want to be able to set a debug flag that will only execute certain portions of code when it's set to true equiv to C++ setting a preprocessor #define DEBUG and using #ifdef DEBUG.Is there an accepted or best way to accomplish this in Java?
Right now I'm just going to set a variable in my Application object, but I don't imagine this is the best way.