just out of curiosity, are you on a Mac? I found the tools to be much less
stable on OSX than on Linux (don't know about Windows), although that has
gotten a little better (e.g. the adb server used to crash all the time on
OSX, and while the crashes are not entirely gone, it has gotten a lot bet
One more update - the avd based on SDK 2.3.3 was able to remain up and
running
for a while without crashing. I tried using the avd based on SDK 2.1,
it starts up
fine but when you try to press any buttons or open any apps it
crashes. This is
frustrating because I cannot run any of my projects on t
Much slower - I was finally able to get the 2.3.3 avd to run on the
tools rev 9 emulator
(kept crashing but the last time I run it it stayed up) and the whole
time that was up
it was running at 90%+ CPU ...
On Feb 10, 3:43 am, Matthias wrote:
> the rev9 emulator is also very unstable for me. Whe
the rev9 emulator is also very unstable for me. Whenever I send a geo fix
(from DDMS or telnet), the emulator crashes and reboots. It also randomly
reboots when using it sometimes. I wonder if that's related to the same
issue the Nexus S has. it's also slower than previous emulators.
--
You re
I had an incomplete sentence below - apologies. I meant to say
that once I click on anything in the emulator I get a windows crash
pop up window that says that the 'emulator.exe has encountered a
problem and needs to close ..." ... it includes technical data
and it is attaching a appcompat file wi
青铜 wrote:
> I also have this question.
> Every time I run HelloMapView (the example code in dev.android), I
> only can see the title of the app, and the content is just black.
Did you get your own Maps API key, as outlined in step #4?
--
Mark Murphy (a Commons Guy)
http://commonsware.com
_The B
I also have this question.
Every time I run HelloMapView (the example code in dev.android), I
only can see the title of the app, and the content is just black.
After I close the emulator, I can see these words:
DeviceMonitor]Error reading jdwp list: EOF
[2009-03-26 09:22:48 - DeviceMonitor]Connect
I'm running Windows Vista with Eclipse - and I'm getting the same
thing. Very annoying.
On Jan 5, 9:49 am, Sundog wrote:
> I am running it on Windows XP with Eclipse, and it does this every
> time I quit the Emulator while it's running my app. I don't know if
> it's always done it or not, I onl
I am running it on Windows XP with Eclipse, and it does this every
time I quit the Emulator while it's running my app. I don't know if
it's always done it or not, I only noticed it recently.
On Jan 5, 10:26 am, "David Turner" wrote:
> On Mon, Jan 5, 2009 at 6:23 PM, Sundog wrote:
>
> > I alwa
On Mon, Jan 5, 2009 at 6:23 PM, Sundog wrote:
>
> I always get this too. I don't think it interferes with normal
> operation.
>
thanks for pointing this out. Can you answer the same basic questions ?
>
> On Jan 4, 3:16 am, Vitaly wrote:
> > Hello,
> >
> > I'm just starting with Java, Eclipse
I always get this too. I don't think it interferes with normal
operation.
On Jan 4, 3:16 am, Vitaly wrote:
> Hello,
>
> I'm just starting with Java, Eclipse and Android, so maybe no wonder I
> ran into the following problem:
> when I run an application from Eclipse, emulator starts, my simple ap
this should not happen. you're probably encountering a weird emulator bug.
the Eclipse message is normal in case of an emulator crash.
what exact platform/OS do you have ? can you repeat this consistently, or
are the crashes random ?
thanks in advance
On Sun, Jan 4, 2009 at 11:16 AM, Vitaly wro
t; -Mike
>
> > > > - Original Message -
> > > > From: "Beginner" <[EMAIL PROTECTED]>
> > > > To: "Android Developers"
> > > > Sent: Friday, April 18, 2008 3:23:06 PM GMT -05:00 US/Canada Eastern
> > > > S
e mac.
>
> > > -Mike
>
> > > - Original Message -
> > > From: "Beginner" <[EMAIL PROTECTED]>
> > > To: "Android Developers"
> > > Sent: Friday, April 18, 2008 3:23:06 PM GMT -05:00 US/Canada Eastern
> > &g
>
> > If you have a mac, the emulator is certainly the best on the mac.
> >
> > -Mike
> >
> > - Original Message -
> > From: "Beginner" <[EMAIL PROTECTED]>
> > To: "Android Developers"
> > Sent: Friday, April 18, 20
ril 19, 2008 2:05:04 PM GMT -05:00 US/Canada Eastern
Subject: [android-developers] Re: Emulator crashing constantly on Windows Vista
- Installed SP1
- uninstalled both sdk and the plugin
No difference.
On Apr 18, 6:08 pm, "Michael R. Novak" <[EMAIL PROTECTED]>
wrote:
> I would
Linux.
>
> If you have a mac, the emulator is certainly the best on the mac.
>
> -Mike
>
> - Original Message -
> From: "Beginner" <[EMAIL PROTECTED]>
> To: "Android Developers"
> Sent: Friday, April 18, 2008 3:23:06 PM GMT -05:00 US/Cana
gt;
To: "Android Developers"
Sent: Friday, April 18, 2008 3:23:06 PM GMT -05:00 US/Canada Eastern
Subject: [android-developers] Re: Emulator crashing constantly on Windows Vista
I'm not sure if this is of any more help, but here we go
[Trace from console]
"failed to read packet from
I'm not sure if this is of any more help, but here we go
[Trace from console]
"failed to read packet from transport socket on fd 103
failed to read packet from transport socket on fd 108
This application has requested the Runtime to terminate it in an
unusual way.
Please contact the application
Just confirming that I am also seeing this.
On Apr 18, 9:42 am, Beginner <[EMAIL PROTECTED]> wrote:
> I'm seeing the same problem. The Windows message is:
>
> "adb.exe has stopped working
>
> A problem caused the program to stop working correctly.
> Windows will close the program and notify you i
Thank You so much!
I think the problem was with Windows. I upgraded to Windows Vista SP1, the
problem is solved.
Anyways, good piece of advise for the future.
Regards
Nitin Khanna
www.hsc.com
On Fri, Apr 18, 2008 at 10:02 AM, Digit <[EMAIL PROTECTED]> wrote:
> you should be able to get a bette
you should be able to get a better idea of the problem by doing the
following:
- close eclipse
- kill any adb.exe process that is running on your machine
- open a console, go to $SDK/tools
- type "set ADB_TRACE=all"
- type "adb nodaemon server"
this runs the ADB server in the foreground, dumping
I'm seeing the same problem. The Windows message is:
"adb.exe has stopped working
A problem caused the program to stop working correctly.
Windows will close the program and notify you if a solution is
available"
There is no "Details" button or anything of the sort. Only a "Close
Program" button
but there must be a button like "Details..." that should give you more
information about the crash. if you could paste this information here, that
would be useful to understand what's happening...
On Sun, Mar 30, 2008 at 10:00 AM, [EMAIL PROTECTED] <[EMAIL PROTECTED]>
wrote:
>
> The error message
The error message is that Emulator has stopped working.
nitin
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To uns
can you describe more precisely what you mean by "crash abruptly" ?
do you have some sort of error dialog from Windows which tells you the cause
of the crash, for example ?
what does the Applications event log records on your machine ?
On Sun, Mar 23, 2008 at 3:04 PM, [EMAIL PROTECTED] <[EMAIL PRO
Hi Derek!
Thanks for the reply. I have 4 gigs of RAM out of which more than 2
gigs is almost always free. So It seems not an issue related to
memory.
Regards
Nitin
On Mar 23, 4:30 pm, derekjay <[EMAIL PROTECTED]> wrote:
> Hi Nitin,
>
> How much free memory do you have on your machine? The emula
Hi Nitin,
How much free memory do you have on your machine? The emulator can use
upwards of 200Mb, so if your system memory is only 512Mb you may
struggle.
Regards,
Derek
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google
Gro
28 matches
Mail list logo
