On Fri, Apr 15, 2011 at 11:20 AM, Eric <[email protected]> wrote: > > On Apr 14, 11:22 pm, TreKing <[email protected]> wrote: > > I have a Nexus One with 2.3.3 installed as well and it runs just fine for > > me. > > A very real possibility is that the "complete crap environment" is your > own. > > It would be hard to tell, though, from the complete lack of information > in > > your post. "It's slow" doesn't tell us much. > > What else do you want to know??
Oh, sorry, I think you didn't get the previous email, where this was mentioned: * * *Including all the relevant variables (OS, Eclipse version, ADT version, any logs, etc, etc), with a polite request for help.* This should answer that question : ). When I run my app in the debugger, it > is unusably slow. When I run it outside the debugger, it performs > satisfactorily. The only changing variable is the debugger. I have a > lot of network communication going on in a background thread. When I > run the app in the debugger, the screens immediately become > unresponsive, whereas outside the debugger there is no noticeable > change in performance. > > Perhaps, I've had that happen once or twice, but typically my development environment runs pretty quick, even on emulator. I can notice some difference when using the debugger but not noticable enough to cause problems (how big is your app? Probably not very, so you shouldn't see problems either). > We can pretend the debugger is fast, like some of the follow up posts > have done, or we can discuss why Google can't provide developers with > a decent debugging environment (LET ALONE a simulator that is even > remotely usable). And right, some of the Google developers are on this list, and I'm sure they'd contend what you're saying. > - Eric Ultimately, I'm sure people would be glad to help you: typical use of the debugger is not noticeable enough to cause development issues, if you're having that much trouble something is probably wrong in your setup or app. But you'll first have to give a detailed description of what code causes problems, how you've diagnosed it (i.e., I started up emulator and broke at line 232 of this file, function presented here, and my build set is, etc...) However, insulting Google makes you look unintelligible (I'm guessing that calling it a "simulator" doesn't win many points either.) So if you'd like more assistance with the matter please try again with more detailed code and build environment description. Kris P.s., you should have expected bad responses if you go on a random user group and say (essentially) "this is bad, you suck." -- 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
