Home/ Questions/Q 8090307
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-05T19:40:29+00:00

I know there are many discussions about the emulator which is so slow that

  • 0

I know there are many discussions about the emulator which is so slow that is essentially unusable for routine debugging tasks. I am talking about debugging with physical devices. My app runs about an order of magnitude slower in debug mode than in non-debug mode. I mean “an order of magnitude” literally. I can think of three possible candidates for the bottleneck:

  1. Computer.
  2. Android device.
  3. Eclipse.

Checking my computer during debugging shows its quad-core CPU and 8 GB memory on Windows 7 Ultimate 64-bit has plenty of room left. The devices I use are Samsung Admire running Gingerbread, Airpad X running ICS (a generic tablet). My Eclipse is Indigo Service Release 2 Build id: 20120216-1857.
Could any experts, especially those who have successfully boosted Android app debugging performance offer some tips

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    not a solution , but a few tips that might make the problem a little less , well, problematic :

    1. try to reduce the number of logs written at runtime.

    2. you can run the app normally , and then debug it at runtime . simply choose the process via eclipse , and choose the bug-icon in the ddms view (not the one next to the launch-icon) .

    3. same as #2 , but inside the code : use “waitForDebugger” when you see fit.

    4. try to reduce the number of expressions that need to be evaluated in the debug mode.

    • 0