Yeah - it's crazy slow. I think it took more like 20+ minutes on first run
with a freshly created emulator.
On Tue, Dec 20, 2011 at 5:20 PM, Jonathan Pobst wrote:
> The shared runtime has slowly gotten bigger as we added v7a and x86
> support. In the future, we may have to look at shipping 3 s
I'm currently using an EVO 4g running ICS for development. It's pretty
handy as I can perform a NAND backup and bounce between 4.0.3 and 2.3.7 in
a matter of minutes ..
On Mon, Dec 19, 2011 at 1:01 PM, John Morris wrote:
> I'm not sure one is out yet. The Galaxy Nexus phone might be the first
>
Have any performance improvements been made?
On Tue, Aug 9, 2011 at 11:22 AM, Jonathan Pobst wrote:
> Hey Everyone!
>
> We are proud to announce the first Xamarin release of Mono for Android! It
> took us a while to relearn our release infrastructure, but now we are ready
> to resume frequent
Just use the standard Android SDK for now. You need to understand it quite
well to take advantage of M4A anyhow.
On Tue, Jul 12, 2011 at 11:49 AM, Wally McClure <
theevilprogram...@hotmail.com> wrote:
> While I admittedly have a bias, I'd still go grab an eval copy and play
> with it. There ar
I have been performing tests with porting code between native Java apps w/
Eclipse + ADT to VS2010 + Monodroid.
My initial findings are as follows:
Even for a simple/contrived application with a minimal UI/logic, start-up
times for a Mono app are in the 5-10 second range. This improves on
subseq
