[android-developers] Re: Emulator crashing with System Tools rev 9
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 better with the last few SDK releases) -- 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 unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
[android-developers] Re: Emulator crashing with System Tools rev 9
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 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 unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
[android-developers] Re: Emulator crashing with System Tools rev 9
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 m.kaepp...@googlemail.com wrote: 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 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 unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
[android-developers] Re: Emulator crashing with System Tools rev 9
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 these emulators at this point. Any suggestions as to how to solve this? On Feb 10, 1:13 pm, kypriakos demet...@ece.neu.edu wrote: 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 m.kaepp...@googlemail.com wrote: 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 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 unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
[android-developers] Re: Emulator crashing with System Tools rev 9
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 with the error message. Any ideas would be greatly appreciated? Thanks On Feb 10, 2:49 am, kypriakos demet...@ece.neu.edu wrote: After I upgraded the following: Eclipse plugin to ADT 9 SDK tools from rev 6 to 9 Added SDK 2.3.1 and 2.3.3 I already had SDK 1.6, 2.1, 2.2. Now trying to run again the emulators on any of the AVDs I had or I generate it crashes. It opens the emulator and once I click on anything I get the I also noticed that while the emulator starts it does not go through the sequence of displaying ANDROID and then the flashing Android logo. It skips that one ... Any ideas would be greatly appreciated. I was under the impression that the tools can be easily upgraded without any issues but this is putting a stop on the show. Thanks very much in advance ( I am running all this one Win XP SP3 - things have been working great for a couple of years now so I know that the latest update is the cause). -- 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 unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
[android-developers] Re: Emulator crashing
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]Connection Failure when starting to monitor device 'emulator-5554' : device (emulator-5554) request rejected: device not found --~--~-~--~~~---~--~~ 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 unsubscribe from this group, send email to android-developers-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~--~~~~--~~--~--~---
[android-developers] Re: Emulator crashing
青铜 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 Busy Coder's Guide to Android Development_ Version 2.0 Available! --~--~-~--~~~---~--~~ 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 unsubscribe from this group, send email to android-developers-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~--~~~~--~~--~--~---
[android-developers] Re: Emulator crashing
I'm running Windows Vista with Eclipse - and I'm getting the same thing. Very annoying. On Jan 5, 9:49 am, Sundog michael_...@tmail.com 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 only noticed it recently. On Jan 5, 10:26 am, David Turner di...@android.com wrote: On Mon, Jan 5, 2009 at 6:23 PM, Sundog michael_...@tmail.com 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 vita...@gmail.com 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 app shows up, etc. But when I close the emulator, I get a Windows' standard error message Emulator.exehasstoppedworkingand will be closed and another error message in the Eclipse's console window: [2009-01-04 12:23:06 - DeviceMonitor]Error reading jdwp list: EOF [2009-01-04 12:23:06 - DeviceMonitor]Connection Failure when starting to monitor device 'emulator-5554' : device (emulator-5554) request rejected: device not found I'd appreciate if someone could tell me what I'm doing wrong and how can I terminate the emulator correctly. Thanks, Vitaly- Hide quoted text - - Show quoted text - --~--~-~--~~~---~--~~ 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 unsubscribe from this group, send email to android-developers-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~--~~~~--~~--~--~---
[android-developers] Re: Emulator crashing
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 vita...@gmail.com 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 app shows up, etc. But when I close the emulator, I get a Windows' standard error message Emulator.exe has stopped working and will be closed and another error message in the Eclipse's console window: [2009-01-04 12:23:06 - DeviceMonitor]Error reading jdwp list: EOF [2009-01-04 12:23:06 - DeviceMonitor]Connection Failure when starting to monitor device 'emulator-5554' : device (emulator-5554) request rejected: device not found I'd appreciate if someone could tell me what I'm doing wrong and how can I terminate the emulator correctly. Thanks, Vitaly --~--~-~--~~~---~--~~ 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 unsubscribe from this group, send email to android-developers-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~--~~~~--~~--~--~---
[android-developers] Re: Emulator crashing
I always get this too. I don't think it interferes with normal operation. On Jan 4, 3:16 am, Vitaly vita...@gmail.com 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 app shows up, etc. But when I close the emulator, I get a Windows' standard error message Emulator.exe has stopped working and will be closed and another error message in the Eclipse's console window: [2009-01-04 12:23:06 - DeviceMonitor]Error reading jdwp list: EOF [2009-01-04 12:23:06 - DeviceMonitor]Connection Failure when starting to monitor device 'emulator-5554' : device (emulator-5554) request rejected: device not found I'd appreciate if someone could tell me what I'm doing wrong and how can I terminate the emulator correctly. Thanks, Vitaly --~--~-~--~~~---~--~~ 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 unsubscribe from this group, send email to android-developers-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~--~~~~--~~--~--~---
[android-developers] Re: Emulator crashing
On Mon, Jan 5, 2009 at 6:23 PM, Sundog michael_...@tmail.com 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 vita...@gmail.com 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 app shows up, etc. But when I close the emulator, I get a Windows' standard error message Emulator.exe has stopped working and will be closed and another error message in the Eclipse's console window: [2009-01-04 12:23:06 - DeviceMonitor]Error reading jdwp list: EOF [2009-01-04 12:23:06 - DeviceMonitor]Connection Failure when starting to monitor device 'emulator-5554' : device (emulator-5554) request rejected: device not found I'd appreciate if someone could tell me what I'm doing wrong and how can I terminate the emulator correctly. Thanks, Vitaly --~--~-~--~~~---~--~~ 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 unsubscribe from this group, send email to android-developers-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~--~~~~--~~--~--~---
[android-developers] Re: Emulator crashing
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 di...@android.com wrote: On Mon, Jan 5, 2009 at 6:23 PM, Sundog michael_...@tmail.com 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 vita...@gmail.com 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 app shows up, etc. But when I close the emulator, I get a Windows' standard error message Emulator.exe has stopped working and will be closed and another error message in the Eclipse's console window: [2009-01-04 12:23:06 - DeviceMonitor]Error reading jdwp list: EOF [2009-01-04 12:23:06 - DeviceMonitor]Connection Failure when starting to monitor device 'emulator-5554' : device (emulator-5554) request rejected: device not found I'd appreciate if someone could tell me what I'm doing wrong and how can I terminate the emulator correctly. Thanks, Vitaly- Hide quoted text - - Show quoted text - --~--~-~--~~~---~--~~ 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 unsubscribe from this group, send email to android-developers-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~--~~~~--~~--~--~---
[android-developers] Re: Emulator crashing constantly on Windows Vista
In my email above, I posted the server trace collected though the procedure you described: [This is the entire trace from the 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's support team for more information. On Apr 20, 1:21 am, Digit [EMAIL PROTECTED] wrote: please provide us with ADB server traces (collected through the procedure I described a few posts ago in this thread). without this, there is little we can do On Sat, Apr 19, 2008 at 8:05 PM, Beginner [EMAIL PROTECTED] wrote: - Installed SP1 - uninstalled both sdk and the plugin No difference. On Apr 18, 6:08 pm, Michael R. Novak [EMAIL PROTECTED] wrote: I would try reinstalling the sdk and if needed the eclipse plugin. I have noticed issues with the emulator on both Windows and 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 android-developers@googlegroups.com 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 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's support team for more information. The failed to read packet lines appear when I close the emulator [What I did] Here are the steps I took to get the problem... I'm not sure if they tell you anything or if they're useless. But I will include them just in case. - Delete old userdata img file - Run (not debug) emulator from eclipse - ./adb shell - cd data/misc/location - mkdir MY_MOCK_PROVIDER - exit - From eclipse File Explorer view - push properties file to MY_MOCK_PROVIDER - push kml file to MY_MOCK_PROVIDER - close emulator - start emulator again - run for 5 minutes (everything works fine) - close emulator - wait a few minutes - see error I hope this helps, but I'm sure the above gives you no useful info. So if you want me to try something specific, let me know. On Apr 18, 2:23 pm, burevestnikov [EMAIL PROTECTED] wrote: 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 if a solution is available There is no Details button or anything of the sort. Only a Close Program button. Eclipse has the following message in the Console: [2008-04-18 04:41:28 - adb] This application has requested the Runtime to terminate it in an unusual way. [2008-04-18 04:41:28 - adb] Please contact the application's support team for more information. [2008-04-18 12:17:04 - DeviceMonitor] Adb connection Error:An existing connection was forcibly closed by the remote host Any ideas what could be causing this? On Mar 30, 12:28 pm, Digit [EMAIL PROTECTED] wrote: 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 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 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-developers?hl=en -~--~~~~--~~--~--~---
[android-developers] Re: Emulator crashing constantly on Windows Vista
Okay, so it looks like the crashes stop once I turn off User Account Control. On Apr 20, 1:36 pm, Beginner [EMAIL PROTECTED] wrote: In my email above, I posted the server trace collected though the procedure you described: [This is the entire trace from the 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's support team for more information. On Apr 20, 1:21 am, Digit [EMAIL PROTECTED] wrote: please provide us with ADB server traces (collected through the procedure I described a few posts ago in this thread). without this, there is little we can do On Sat, Apr 19, 2008 at 8:05 PM, Beginner [EMAIL PROTECTED] wrote: - Installed SP1 - uninstalled both sdk and the plugin No difference. On Apr 18, 6:08 pm, Michael R. Novak [EMAIL PROTECTED] wrote: I would try reinstalling the sdk and if needed the eclipse plugin. I have noticed issues with the emulator on both Windows and 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 android-developers@googlegroups.com 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 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's support team for more information. The failed to read packet lines appear when I close the emulator [What I did] Here are the steps I took to get the problem... I'm not sure if they tell you anything or if they're useless. But I will include them just in case. - Delete old userdata img file - Run (not debug) emulator from eclipse - ./adb shell - cd data/misc/location - mkdir MY_MOCK_PROVIDER - exit - From eclipse File Explorer view - push properties file to MY_MOCK_PROVIDER - push kml file to MY_MOCK_PROVIDER - close emulator - start emulator again - run for 5 minutes (everything works fine) - close emulator - wait a few minutes - see error I hope this helps, but I'm sure the above gives you no useful info. So if you want me to try something specific, let me know. On Apr 18, 2:23 pm, burevestnikov [EMAIL PROTECTED] wrote: 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 if a solution is available There is no Details button or anything of the sort. Only a Close Program button. Eclipse has the following message in the Console: [2008-04-18 04:41:28 - adb] This application has requested the Runtime to terminate it in an unusual way. [2008-04-18 04:41:28 - adb] Please contact the application's support team for more information. [2008-04-18 12:17:04 - DeviceMonitor] Adb connection Error:An existing connection was forcibly closed by the remote host Any ideas what could be causing this? On Mar 30, 12:28 pm, Digit [EMAIL PROTECTED] wrote: 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 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 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-developers?hl=en -~--~~~~--~~--~--~---
[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 try reinstalling the sdk and if needed the eclipse plugin. I have noticed issues with the emulator on both Windows and 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 android-developers@googlegroups.com 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 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's support team for more information. The failed to read packet lines appear when I close the emulator [What I did] Here are the steps I took to get the problem... I'm not sure if they tell you anything or if they're useless. But I will include them just in case. - Delete old userdata img file - Run (not debug) emulator from eclipse - ./adb shell - cd data/misc/location - mkdir MY_MOCK_PROVIDER - exit - From eclipse File Explorer view - push properties file to MY_MOCK_PROVIDER - push kml file to MY_MOCK_PROVIDER - close emulator - start emulator again - run for 5 minutes (everything works fine) - close emulator - wait a few minutes - see error I hope this helps, but I'm sure the above gives you no useful info. So if you want me to try something specific, let me know. On Apr 18, 2:23 pm, burevestnikov [EMAIL PROTECTED] wrote: 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 if a solution is available There is no Details button or anything of the sort. Only a Close Program button. Eclipse has the following message in the Console: [2008-04-18 04:41:28 - adb] This application has requested the Runtime to terminate it in an unusual way. [2008-04-18 04:41:28 - adb] Please contact the application's support team for more information. [2008-04-18 12:17:04 - DeviceMonitor] Adb connection Error:An existing connection was forcibly closed by the remote host Any ideas what could be causing this? On Mar 30, 12:28 pm, Digit [EMAIL PROTECTED] wrote: 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 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 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-developers?hl=en -~--~~~~--~~--~--~---
[android-developers] Re: Emulator crashing constantly on Windows Vista
try installing the Java EE version of eclipse, that is what i switched to on windows. It doesn't make it perfect but it certainly makes it easier. mike - Original Message - From: Beginner [EMAIL PROTECTED] To: Android Developers android-developers@googlegroups.com Sent: Saturday, April 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 try reinstalling the sdk and if needed the eclipse plugin. I have noticed issues with the emulator on both Windows and 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 android-developers@googlegroups.com 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 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's support team for more information. The failed to read packet lines appear when I close the emulator [What I did] Here are the steps I took to get the problem... I'm not sure if they tell you anything or if they're useless. But I will include them just in case. - Delete old userdata img file - Run (not debug) emulator from eclipse - ./adb shell - cd data/misc/location - mkdir MY_MOCK_PROVIDER - exit - From eclipse File Explorer view - push properties file to MY_MOCK_PROVIDER - push kml file to MY_MOCK_PROVIDER - close emulator - start emulator again - run for 5 minutes (everything works fine) - close emulator - wait a few minutes - see error I hope this helps, but I'm sure the above gives you no useful info. So if you want me to try something specific, let me know. On Apr 18, 2:23 pm, burevestnikov [EMAIL PROTECTED] wrote: 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 if a solution is available There is no Details button or anything of the sort. Only a Close Program button. Eclipse has the following message in the Console: [2008-04-18 04:41:28 - adb] This application has requested the Runtime to terminate it in an unusual way. [2008-04-18 04:41:28 - adb] Please contact the application's support team for more information. [2008-04-18 12:17:04 - DeviceMonitor] Adb connection Error:An existing connection was forcibly closed by the remote host Any ideas what could be causing this? On Mar 30, 12:28 pm, Digit [EMAIL PROTECTED] wrote: 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 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 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-developers?hl=en -~--~~~~--~~--~--~---
[android-developers] Re: Emulator crashing constantly on Windows Vista
please provide us with ADB server traces (collected through the procedure I described a few posts ago in this thread). without this, there is little we can do On Sat, Apr 19, 2008 at 8:05 PM, Beginner [EMAIL PROTECTED] wrote: - Installed SP1 - uninstalled both sdk and the plugin No difference. On Apr 18, 6:08 pm, Michael R. Novak [EMAIL PROTECTED] wrote: I would try reinstalling the sdk and if needed the eclipse plugin. I have noticed issues with the emulator on both Windows and 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 android-developers@googlegroups.com 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 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's support team for more information. The failed to read packet lines appear when I close the emulator [What I did] Here are the steps I took to get the problem... I'm not sure if they tell you anything or if they're useless. But I will include them just in case. - Delete old userdata img file - Run (not debug) emulator from eclipse - ./adb shell - cd data/misc/location - mkdir MY_MOCK_PROVIDER - exit - From eclipse File Explorer view - push properties file to MY_MOCK_PROVIDER - push kml file to MY_MOCK_PROVIDER - close emulator - start emulator again - run for 5 minutes (everything works fine) - close emulator - wait a few minutes - see error I hope this helps, but I'm sure the above gives you no useful info. So if you want me to try something specific, let me know. On Apr 18, 2:23 pm, burevestnikov [EMAIL PROTECTED] wrote: 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 if a solution is available There is no Details button or anything of the sort. Only a Close Program button. Eclipse has the following message in the Console: [2008-04-18 04:41:28 - adb] This application has requested the Runtime to terminate it in an unusual way. [2008-04-18 04:41:28 - adb] Please contact the application's support team for more information. [2008-04-18 12:17:04 - DeviceMonitor] Adb connection Error:An existing connection was forcibly closed by the remote host Any ideas what could be causing this? On Mar 30, 12:28 pm, Digit [EMAIL PROTECTED] wrote: 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 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 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-developers?hl=en -~--~~~~--~~--~--~---
[android-developers] Re: Emulator crashing constantly on Windows Vista
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. Eclipse has the following message in the Console: [2008-04-18 04:41:28 - adb] This application has requested the Runtime to terminate it in an unusual way. [2008-04-18 04:41:28 - adb] Please contact the application's support team for more information. [2008-04-18 12:17:04 - DeviceMonitor] Adb connection Error:An existing connection was forcibly closed by the remote host Any ideas what could be causing this? On Mar 30, 12:28 pm, Digit [EMAIL PROTECTED] wrote: 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 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 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-developers?hl=en -~--~~~~--~~--~--~---
[android-developers] Re: Emulator crashing constantly on Windows Vista
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 all traces to the console now start Eclipse and try to use it as normal; when the ADB server crashes, send me the traces you collected until then thanks in advance On Fri, Apr 18, 2008 at 6:42 PM, 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 if a solution is available There is no Details button or anything of the sort. Only a Close Program button. Eclipse has the following message in the Console: [2008-04-18 04:41:28 - adb] This application has requested the Runtime to terminate it in an unusual way. [2008-04-18 04:41:28 - adb] Please contact the application's support team for more information. [2008-04-18 12:17:04 - DeviceMonitor] Adb connection Error:An existing connection was forcibly closed by the remote host Any ideas what could be causing this? On Mar 30, 12:28 pm, Digit [EMAIL PROTECTED] wrote: 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 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 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-developers?hl=en -~--~~~~--~~--~--~---
[android-developers] Re: Emulator crashing constantly on Windows Vista
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 PROTECTED] wrote: Hi! I updated to the latest release of the Android SDK, and since the emulator and adb.exe crashes, every now and then abruptly. Any inputs. Regards 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 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-developers?hl=en -~--~~~~--~~--~--~---
