On my very fast machine, the emulator is at least an order of
magnitude slower if the app is being debugged than if it isn't. So
your result is not too surprising to me not knowing what in the
debugger causing the slowdown.
On Nov 4, 5:59 am, John Gaby wrote:
> I have noticed that as well. I ha
I have noticed that as well. I have some list views which are very
sluggish when I fling through the list while debugging, but are
perfectly fast when not debugging. I have never seen this big of a
difference, however (23 seconds when debugging to < 2 seconds
without).
John
On Nov 3, 2:07 pm, K
Debugging seems to slow *everything* down a lot.
Sometimes even simple UI updates become a slide show. Once you run
without debugging, it's back to normal.
This is weird, since I'm seeing this on 2.1, so it's not caused by JIT
being disabled (since there is no JIT on 2.1), but it's definitely
As an update to others who run into this problem, oddly enough, the
long delay seems to only happen when I debug the app. If I run it
without debugging, the whole license check (including creating the
AESObfuscator object) take only a couple of seconds.
On Oct 28, 12:12 pm, John Gaby wrote:
> On
On a real device (Motorola Droid) it is faster but it still takes
about 8-10 seconds which is way to long to have to wait every time the
program starts. I have gotten around the problem by putting the
license check (including the call to AESObfuscator) in a separate
thread (note that the network c
Android emulator is superrr slow. After a while and some complaining,
you will get used to the slowness.
There are quite a few discussions on this group as to why it is slow
compared to iphone/other emulators.
I bet on a real device it would be at least 10x faster. Still, you
should do license ch
6 matches
Mail list logo