Hello friend,
I am having amd system with just 256 mb memory. It takes about 20 minutes
(the emulator , i mean) to get started but after starting, it works very
fast.
see http://geeth.ganesan.googlepages.com/android-tutorial
She has clearly mentioned this.
Best Regards.
RSR
======================================
On 5/16/08, prodvit <[EMAIL PROTECTED]> wrote:
>
>
> Thanks for your reply Digit. I didn't know that you are a Google
> employee!
> I understand that for you and your team it's very difficult to test
> Android on many different configuration.
> But I tried it on two very different configuration and the results are
> the following:
>
> 1) Desktop Pc
> AMD Athlon 1GHz
> 512 MB
> Windows XP Home Edition SP2
>
> time to load the emulator: about 20 minutes
>
> My opinion is that I have to few RAM because the emulator is also too
> slow when I click on menu, launch an application...so this is a
> problem of my pc.
>
> 2) Asus Laptop
> Intel Centrino 1,75 GHz
> 2 GB
> Ubuntu 8.10
>
> time to load the emulator: about 5-6 minutes (more reasonable time)
>
> The most amazing thing is that in both configurations the log trace is
> very similar: in particular I can see many ClassNotFoundExceptions.
> For example
>
> DEBUG/dalvikvm(496): NOTE: loadClass 'android.app.Activity
> $LocalWindowManager' 0x40018950 threw an exception
> DEBUG/dalvikvm(496): Exception Ljava/lang/ClassNotFoundException; from
> PathClassLoader.java:205 not caught locally
>
> In the android's jar (the m5_r15) the class Activity
> $LocalWindowManager', in the package android.app, doesn't exist!
> Instead I found it in the old jar (m3)...
>
> What I mean is:
> Is it a my configuration problem or a bug (of eclipse plugin or the
> android's jar)?
>
> In your precedent post you talk about crash: do you refer about this?
>
>
> On 16 Mag, 14:24, Digit <[EMAIL PROTECTED]> wrote:
> > sorry if this is not clear. I'm a Google employee, part of the Android
> > development team.
> >
> > what I mean is that it's very difficult for us to spend any more time
> trying
> > to debug something that isn't really easily reproducible on our machines,
> > moreover the up-to-date sources are internally very different from the M5
> > one.
> >
> > and in case you'd want to ask, I don't know when there will be a new SDK
> > release.
> >
> > On Fri, May 16, 2008 at 12:30 PM, prodvit <[EMAIL PROTECTED]> wrote:
> >
> > > What you means with
> > > " the M5 codebase is so dated compared
> > > to our current sources that we won't be able to spend a lot of
> > > resources on
> > > this anymore (and believe me, I tried a lot)."?
> >
> > > Have you modified the source code?
> >
> > > The M5_r15 is the last available release...if it's a known bug like
> > > you said, I am amazed that anyone has fixed!
> >
> > > I also tried to search on google but seems that anyone has the same
> > > problem...
> >
>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google
Groups "Android Beginners" group.
To post to this group, send email to android-beginners@googlegroups.com
To unsubscribe from this group, send email to
[EMAIL PROTECTED]
Announcing the new M5 SDK!
http://android-developers.blogspot.com/2008/02/android-sdk-m5-rc14-now-available.html
For more options, visit this group at
http://groups.google.com/group/android-beginners?hl=en
-~----------~----~----~----~------~----~------~--~---
