[NiteLordz]

Great news… i got it working with trial and error… so the process i have to run thru to be able to debug is as follows

in simulator
-Build normally
-Debug Android App
-wait
-when the message comes up APP_CMD_INPUT_CHANGED, place a breakpoint inside the app
-commence debugging

On device
same as above, only Debug App Startup ( this gives the debugger time to connect since hte device is so much faster

Issues still have
-Breakpoints do not persist (once you debug and stop, you have to repeat the process, the breakpoints dont stick thru additional runs)

Thanks much for your time, and now that i ahve it working, i believe i will purchase it, if i can get the breakpoints to persist

[NiteLordz]

i have got it working ( not using any of those solutions ) but it is not reliable… what is interesting is that it seems to work one out of 3 times or so. From logcat, what seems to be happening is that the application/debugger is still running even after i stop the application and uninstall it. I then start to Debug Android App again, and it seems to pick up where it was.

what setting do i need to set for a “complete refresh” everytime

thanks much for your help, and i will try your solutions now, and let you know.

[NiteLordz]

So i found out that if i my files are in the JNI directory, then the application will be debuggable, but if my files live outside of the JNI folder, then they are not debugged… how can this be corrected?

thanks much

[NiteLordz]

more details,

I am debuggin with a Droid X2 device

and i also just seen this message in Log Cat

debugger has settled
Debugger has detached; object registry had 55 entries ( this was in blue )

[Author]

Posts