HI Ulff,
thank you for the patience
Now are several days I am busy with debugging with Android. Two points to develop.
Unfortunately despite my huge progress I discovered I cannot see the flux if an interface is called, because the "breakpoints" cannot be applied to interfaces, and Api classes es if I want to see a shared preference method I am calling importing the libraries, I cannot do it.
1)First of all I use the debugger to step through the flux of programs I do not know. Please... what is the order the breakpoints appear?
I do not understand if I have to select a couple of them, of all the methods, in fact if I select all the method it looks like the program starts not from OnCreate, but for the last break point i selected! this makes impossible to see the flux of code like with the great Log.d that is time consuming if I need to examine all the code, in fact I am still wondering why there is not a tool that add log.d numerated and with the print of the line they refer, so that one can see from the Log DDMS the exact sequence the code is running
( i would do but reflection is too advanced for me at the moment). I finstead I select only a couple of break points I can see better the flux, but I miss the big picture. any tip to see the flux in an easy way, or if the automatic Log.d project has been already implemented by someone? thanks and sorry maybe I am OT for Android, as could be a more an Eclipse
IDE issue.
2) Second I would like to change the post to "Debugging in Android with Eclipse: if Debugger does not work" to give benefit to future searches by users with similar issues, because I went through a lot of setting problems, the more important solutions are the following:
a) changing the ADB connection timeout. Ifrom 5000ms to 10000ms to get rid of the problem app and debugger do not start.
Window -> Preferences --> DDMS under Android set 10000
b)Change the manifest, debug could be set as false. Instead to change it to true, to avoid the so called "hardcoding" just erase the line in the manifest and it will be recognized automatically as degug is true
c) Use step filters. otherwise you will receive a lot of source not found errors, because Eclipse Debugger is mainly set to catch
Java code, activate step filters and add to all the libraries, also other two adding: android.* and com.android.*