No suggestions at all?
There must be a way to do this. My hunch is that debugging slowdown is
related to the amount of user code that is being invoked. So the more
custom code you execute the more you'll see the slowdown. The android
frameworks themselves don't seem to be influenced by this;
In my project I've implemented a custom view that does a substantial
amount of processing when rendering itself. When I attach the debugger
to my application I'm experiencing so much slowdown that the application
is essentially not useable anymore. Due to the increased time taken by
certain
2 matches
Mail list logo