Status Update
No update yet.
Comments
jv...@google.com
1. Emulator version
2. Run the emulator from command line with “$ANDROID_SDK_ROOT/emulator/emulator -avd <NameOfAVD> -verbose -show-kernel” and send the resulting logs
3. Any relevant Logcat logs
4. The results of running “adb shell top” in the command line.
For more information on what’s needed and how to obtain this information please read the guide at
st...@gmail.com
Am Fr., 7. März 2025 um 16:08 Uhr schrieb <buganizer-system@google.com>:
rk...@google.com
Hi Stean, the file you attached shows
INFO | Boot completed in 62411 ms
Did the Emulator work for you when you started from the command line? Could you also attach idea.log (in Android Studio, Help > Show Log) please.
st...@gmail.com
Yes, a device popped up and for a time it seems to work, but then it shut
down.
Am Fr., 7. März 2025 um 18:57 Uhr schrieb <buganizer-system@google.com>:
rk...@google.com
Thank you for the update.
but then it shut down.
This could be a graphics related crash. Does it crash on its own or when you start an app, e.g. Chrome. Try switching to software graphics (it will be slow) or create an AVD with an lower API level (try API33). You can also add -wipe-data -feature -Vulkan to the command line.
The problem you see in idea.log is 0xC0000135 which means "missing DLLs". For some reasons when the Emulator is started from the Android Studio we can't find our own DLLs. Did you add any Emulator specific environment variable yourself before? You can check all your environment variables by running SET in the command line.
If you can share the output of SET with us that could help figuring out why you cannot start the Emulator from the Android Studio.
st...@gmail.com
Now i desinstalled the API 35 and tried to install the API 33 but suddenly
an error occurred - that never happened before.
Am Fr., 7. März 2025 um 19:35 Uhr schrieb <buganizer-system@google.com>:
rk...@google.com
an error occurred - that never happened before.
Connection reset.
I don't know, maybe retry?
rk...@google.com
AndroidStudioSet.txt
I don't see any variables which could confuse the Emulator.
st...@gmail.com
I will deinstall everything and try it again.
Am Fr., 7. März 2025 um 20:43 Uhr schrieb <buganizer-system@google.com>:
st...@gmail.com
Am Fr., 7. März 2025 um 20:45 Uhr schrieb Stefan <stean.hubner@gmail.com>:
st...@gmail.com
Am Fr., 7. März 2025 um 22:02 Uhr schrieb Stefan <stean.hubner@gmail.com>:
rk...@google.com
I tried again with the latest version and still got the same error
We have two issues here:
- the Emulator crashes with
0xC0000135when you start it from the Android Studio. We received several reports like this. We don't know why this happens. And we cannot reproduce this on our end. - the Emulator boots when it is started from the command line but then crashes randomly. I think this is a graphics related issue and it is probably caused by interaction between our code and your GPU drivers while both of them are not perfect :) To workaround this please try creating an older API level AVD and run without Vulkan (add
-feature -Vulkanto the command line).
st...@gmail.com
device - there always came an error.
Am Fr., 7. März 2025 um 22:12 Uhr schrieb <buganizer-system@google.com>:
st...@gmail.com
But is there a way that i can use it without the cmd?
Thanks for your help
Am Sa., 8. März 2025 um 09:49 Uhr schrieb Stefan <stean.hubner@gmail.com>:
Description
I tried to create a new device, but it allows shows the error in the title.
I tried nearly everything, installed, deinstalled, closed the android studio, restart the computer, but the error still keeps popin up...
Thanks for your help.
Best regards, Stefan