Emulator fails at boot up

Common bugs/problems with the Android SDK the Emulator and the ADT-Plugin.

Emulator fails at boot up

Postby help_me » Thu Mar 19, 2009 3:24 pm

Hello everyone. I am using android on windows.

I am using android-sdk-windows-1.1_r1. when i start the emulator the first screen appears and then it freezes. I dont get the home screen even if i wait for 10 min.

In ddms log cat i get these messages
03-19 09:08:18.291: INFO/DEBUG(20): debuggerd: Feb 5 2009 15:37:59
03-19 09:08:21.432: ERROR/mountd(19): could not read initial mass storage state
03-19 09:08:22.370: ERROR/flash_image(27): can't find recovery partition
03-19 09:08:23.525: DEBUG/RILD(21): overriding with -s /dev/socket/ qemud_gsm
03-19 09:08:39.041: DEBUG/AndroidRuntime(22): >>>>>>>>>>>>>>AndroidRuntime START<<<<<<<<<<<<<
03-19 09:08:39.051: DEBUG/AndroidRuntime(22): CheckJNI is ON
03-19 09:08:40.362: ERROR/dalvikvm(22): Can't open dex cache '/data/
dalvik-cache/system@framework@core.jar@classes.dex': No such file or
directory
03-19 09:08:40.362: INFO/dalvikvm(22): Unable to open or create cache
for /system/framework/core.jar
03-19 09:08:40.362: DEBUG/dalvikvm(22): Failed on '/system/framework/
core.jar' (boot=1)
03-19 09:08:40.374: DEBUG/dalvikvm(22): VM cleaning up
03-19 09:08:40.381: DEBUG/dalvikvm(22): LinearAlloc 0x0 used 4100 of
4194304 (0%)
03-19 09:08:40.431: WARN/dalvikvm(22): JNI_CreateJavaVM failed
03-19 09:08:40.431: ERROR/AndroidRuntime(22): JNI_CreateJavaVM failed
03-19 09:08:45.991: INFO/(23): ServiceManager: 0xaab8
03-19 09:08:46.508: INFO/AudioFlinger(23): AudioFlinger's main thread
ready to run.
03-19 09:08:46.921: INFO/CameraService(23): CameraService started:
pid=23
03-19 09:08:47.681: DEBUG/AndroidRuntime(47): >>>>>>>>>>>>>>
AndroidRuntime START <<<<<<<<<<<<<<
03-19 09:08:53.177: DEBUG/dalvikvm(51): Failed on '/system/framework/
core.jar' (boot=1)

Pls tell me the reason for errors and how to fix it, thank you in advance
help_me
Freshman
Freshman
 
Posts: 2
Joined: Thu Mar 19, 2009 3:19 pm

Top

Solution!?

Postby AudioDroid » Fri Mar 20, 2009 6:37 pm

Hey there,

I think I just had the same problem, because I was working on my laptop until the very(!) last moment. Therefore I had an a mediated shut down, like a system crash. But I found the solution:

http://code.google.com/p/android/issues/detail?id=887

Just type
C:\myAndroidFolder\tools\emulator -wipe-data

in the windows command windows.

That made my day. :-)
Hope it helps you as-well.

Your AudioDroid
AudioDroid
Freshman
Freshman
 
Posts: 2
Joined: Fri Mar 20, 2009 6:28 pm

Postby help_me » Fri Mar 20, 2009 6:51 pm

Thank u for the solution. I ll try this out. But can u mention the reason for this. I had the same problem earlier when i reinstalled both eclipse and emulator, it worked well. And again got the same problem.
help_me
Freshman
Freshman
 
Posts: 2
Joined: Thu Mar 19, 2009 3:19 pm

emulator system

Postby AudioDroid » Sat Mar 21, 2009 4:04 pm

The emulator is a so called virtual machine and as such retains its last state. So if it crashed and you don't call "-wipe-data" it will stay in it's crashed state. I am not sure about this, but that is my explanation to it.
I also tried to reinstall everything with no success. There must be a hidden "status-file" that somehow doesn't get deleted on a reinstall.

AudioDroid
AudioDroid
Freshman
Freshman
 
Posts: 2
Joined: Fri Mar 20, 2009 6:28 pm

Postby ashish » Thu Mar 26, 2009 1:05 pm

when u call emulator -wipedata everything install previously will be washed away....and thus any blocking application will be removed...


read documentation...
http://developer.android.com/sdk/1.1_r1/upgrading.html
ashish
Experienced Developer
Experienced Developer
 
Posts: 62
Joined: Fri Feb 20, 2009 8:09 am

Top

Return to SDK/ADT/Emulator Problems

Who is online

Users browsing this forum: No registered users and 7 guests