On Apr 15, 12:47 pm, Streets Of Boston <[email protected]> wrote: > At what point does your app start running slowly: > - Initially, don't start DDMS or Jetbrain or Eclipse. > - Run the app on your phone which is unconnected. Does it run OK or slow? > - Then connect your phone to your Mac through USB: Does the app still run > OK? > - Then start DDMS (not Jetbrain or Eclipse). Check if DDMS 'sees' your > connected phone. Does the app still run OK? > - In DDMS, get some heap info or examine threads running in your app? Does > the app still run OK? > - Close DDMS and start Jetbrain. Does the app still run OK? > - In Jetbrain, in the DDMS view, connect to your device. Does your app start > running slowly?
Thank you for your suggestions. Closing IDEA and running DDMS still results in a slow running app on the phone device. In any event, since absolutely nobody else seems to experience a debugging situation that is painfully slow, I will have to unfortunately assume that some aspect of my application (i.e. high level of network traffic, and high level of UI updates popped off the background thread), is somehow causing the ADB interface to get fried. I have no problems with this functionality without the debugger (IDEA, DDMS, whatever you want to attach), but they pop up with the debugging session attached. The other disadvantage that I have is that we have a very nice simulation environment available to us on iOS, and the lack of which on Android, coupled with these debugging problems, is making it difficult for me to justify shipping my app on Android too. Thank you, Eric -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
