+1 for that. I have all running on an S2 and it has been as smooth as. Beats my time on windows CE a few years back...
Rob. -----Original Message----- From: monodroid-boun...@lists.ximian.com [mailto:monodroid-boun...@lists.ximian.com] On Behalf Of Tomasz Cielecki Sent: Friday, 2 September 2011 20:17 To: st...@sharkcode.com; Discussions related to Mono for Android Subject: Re: [mono-android] Eval unusable, how about real devices? OK, I have just tried out the debugger on a real device (Samsung Galaxy SII) and it is by far faster. Stepping around when debugging happens within a second, so that is pretty good. The response time on a slower phone (HTC Desire) is a bit longer though about 2-3 seconds per step, but it is still a great improvement of the emulator. So I would go for it and buy a device to debug on if you don't like to wait. On Fri, Sep 2, 2011 at 10:10 AM, Tomasz Cielecki <tom...@ostebaronen.dk> wrote: > It is a fact that the Android emulator is very slow, some people talk > about using Android x86, which you can run in a Virtual Machine, but > how to use it along with MonoDroid I don't know. Has anyone tried > that? > > On Fri, Sep 2, 2011 at 7:03 AM, Steve Sharrock <st...@sharkcode.com> wrote: >> I use a DroidX for all testing -- much, much faster than the >> Emulator. I do Windows Mobile 5.0 development also and it's about the >> same performance when stepping thru debug code. >> >> >> Steve Sharrock >> Architecture/Design/Programming >> www.sharkcode.com >> >> -----Original Message----- >> From: monodroid-boun...@lists.ximian.com >> [mailto:monodroid-boun...@lists.ximian.com] On Behalf Of efontana >> Sent: Monday, August 29, 2011 9:34 AM >> To: monodroid@lists.ximian.com >> Subject: [mono-android] Eval unusable, how about real devices? >> >> I'm a registered MonoTouch owner, I want to port my app to Android, I >> tried the Eval for MonoDroid. >> >> It's totally unusable, even on my new i7 with 8 gigs of ram, the >> emulator is abysmal. >> >> So, my question is, if you use a *Real* device, what's the time like >> for a code change, deploy execute and hit a breakpoint? >> >> When trying this with the Eval, from the time I hit "Debug -> Start" >> till it hits the breakpoint, could be as long as 90 seconds, then >> single stepping goes off into the weeds. >> >> Does the debugger work on a real device? What's the typical turn >> around time? >> >> -- >> View this message in context: >> http://mono-for-android.1047100.n5.nabble.com/Eval-unusable-how-about >> -real-d >> evices-tp4746777p4746777.html >> Sent from the Mono for Android mailing list archive at Nabble.com. >> _______________________________________________ >> Monodroid mailing list >> Monodroid@lists.ximian.com >> >> UNSUBSCRIBE INFORMATION: >> http://lists.ximian.com/mailman/listinfo/monodroid >> >> >> _______________________________________________ >> Monodroid mailing list >> Monodroid@lists.ximian.com >> >> UNSUBSCRIBE INFORMATION: >> http://lists.ximian.com/mailman/listinfo/monodroid >> > > > > -- > Med Venlig Hilsen / With Best Regards > Tomasz Cielecki > http://ostebaronen.dk > -- Med Venlig Hilsen / With Best Regards Tomasz Cielecki http://ostebaronen.dk _______________________________________________ Monodroid mailing list Monodroid@lists.ximian.com UNSUBSCRIBE INFORMATION: http://lists.ximian.com/mailman/listinfo/monodroid _______________________________________________ Monodroid mailing list Monodroid@lists.ximian.com UNSUBSCRIBE INFORMATION: http://lists.ximian.com/mailman/listinfo/monodroid
