Android Virtual Device stalls on start up
I'm trying to run the standard 4" WVGA (Nexus S) AVD with API 24 on my Core 2 Quad (old) desktop with 6GB of RAM. Due to an incompatibility I had to downgrade to Intel HAXM 7.2.0.
The issue I'm having is that the startup stops at around the same time everytime (on the android logo screen). It seems to happen around the time logcat states "I/PackageManager: /system/app/YouTube changed; collecting certs" I've tried many different things to get this working:
1) Messing around with the memory allocations More/less RAM, heap and storage space.
2) Changing to a single emulated core and software graphics rendering.
3) Tried to use API 15 and got the same result.
4) Remove the space in my user name and directory just in case.
5) Tried the 2.7" standard AVD.
6) Trying to make the emulator run as administrator.
7) Creating a new virtual device with the same properties.
Nothing seems to make a difference. I had a bit of luck today when I left the standard pixel AVD again with API 24 running while I went out of the house. When I got back it had crashed but was showing the home screen with a black background. Logcat had the following messages:
"BroadcastQueue: Can't deliver broadcast to com.android.systemui (pid 1715). Crashing it.
JavaBinder: !!! FAILED BINDER TRANSACTION !!! (parcel size = 124)"
Re cold booting it actually worked and I was able to actually use the emulator. This would seem to throw out the theory that it is a limitation of my old hardware as the Pixel AVD would seem to be more demanding than the Nexus S.
I would still like to get the Nexus S running for better performance.
android qemu android-studio intel-haxm
asked Jan 30 at 13:52
Ben YazolliBen Yazolli
12
add a comment |
I'm trying to run the standard 4" WVGA (Nexus S) AVD with API 24 on my Core 2 Quad (old) desktop with 6GB of RAM. Due to an incompatibility I had to downgrade to Intel HAXM 7.2.0.
The issue I'm having is that the startup stops at around the same time everytime (on the android logo screen). It seems to happen around the time logcat states "I/PackageManager: /system/app/YouTube changed; collecting certs" I've tried many different things to get this working:
1) Messing around with the memory allocations More/less RAM, heap and storage space.
2) Changing to a single emulated core and software graphics rendering.
3) Tried to use API 15 and got the same result.
4) Remove the space in my user name and directory just in case.
5) Tried the 2.7" standard AVD.
6) Trying to make the emulator run as administrator.
7) Creating a new virtual device with the same properties.
Nothing seems to make a difference. I had a bit of luck today when I left the standard pixel AVD again with API 24 running while I went out of the house. When I got back it had crashed but was showing the home screen with a black background. Logcat had the following messages:
"BroadcastQueue: Can't deliver broadcast to com.android.systemui (pid 1715). Crashing it.
JavaBinder: !!! FAILED BINDER TRANSACTION !!! (parcel size = 124)"
Re cold booting it actually worked and I was able to actually use the emulator. This would seem to throw out the theory that it is a limitation of my old hardware as the Pixel AVD would seem to be more demanding than the Nexus S.
I would still like to get the Nexus S running for better performance.
android qemu android-studio intel-haxm
asked Jan 30 at 13:52
Ben YazolliBen Yazolli
12
add a comment |
I'm trying to run the standard 4" WVGA (Nexus S) AVD with API 24 on my Core 2 Quad (old) desktop with 6GB of RAM. Due to an incompatibility I had to downgrade to Intel HAXM 7.2.0.
The issue I'm having is that the startup stops at around the same time everytime (on the android logo screen). It seems to happen around the time logcat states "I/PackageManager: /system/app/YouTube changed; collecting certs" I've tried many different things to get this working:
1) Messing around with the memory allocations More/less RAM, heap and storage space.
2) Changing to a single emulated core and software graphics rendering.
3) Tried to use API 15 and got the same result.
4) Remove the space in my user name and directory just in case.
5) Tried the 2.7" standard AVD.
6) Trying to make the emulator run as administrator.
7) Creating a new virtual device with the same properties.
Nothing seems to make a difference. I had a bit of luck today when I left the standard pixel AVD again with API 24 running while I went out of the house. When I got back it had crashed but was showing the home screen with a black background. Logcat had the following messages:
"BroadcastQueue: Can't deliver broadcast to com.android.systemui (pid 1715). Crashing it.
JavaBinder: !!! FAILED BINDER TRANSACTION !!! (parcel size = 124)"
Re cold booting it actually worked and I was able to actually use the emulator. This would seem to throw out the theory that it is a limitation of my old hardware as the Pixel AVD would seem to be more demanding than the Nexus S.
I would still like to get the Nexus S running for better performance.
android qemu android-studio intel-haxm
asked Jan 30 at 13:52
Ben YazolliBen Yazolli
12
I'm trying to run the standard 4" WVGA (Nexus S) AVD with API 24 on my Core 2 Quad (old) desktop with 6GB of RAM. Due to an incompatibility I had to downgrade to Intel HAXM 7.2.0.
The issue I'm having is that the startup stops at around the same time everytime (on the android logo screen). It seems to happen around the time logcat states "I/PackageManager: /system/app/YouTube changed; collecting certs" I've tried many different things to get this working:
1) Messing around with the memory allocations More/less RAM, heap and storage space.
2) Changing to a single emulated core and software graphics rendering.
3) Tried to use API 15 and got the same result.
4) Remove the space in my user name and directory just in case.
5) Tried the 2.7" standard AVD.
6) Trying to make the emulator run as administrator.
7) Creating a new virtual device with the same properties.
Nothing seems to make a difference. I had a bit of luck today when I left the standard pixel AVD again with API 24 running while I went out of the house. When I got back it had crashed but was showing the home screen with a black background. Logcat had the following messages:
"BroadcastQueue: Can't deliver broadcast to com.android.systemui (pid 1715). Crashing it.
JavaBinder: !!! FAILED BINDER TRANSACTION !!! (parcel size = 124)"
Re cold booting it actually worked and I was able to actually use the emulator. This would seem to throw out the theory that it is a limitation of my old hardware as the Pixel AVD would seem to be more demanding than the Nexus S.
I would still like to get the Nexus S running for better performance.
android qemu android-studio intel-haxm
android qemu android-studio intel-haxm
asked Jan 30 at 13:52
Ben YazolliBen Yazolli
12
asked Jan 30 at 13:52
Ben YazolliBen Yazolli
12
asked Jan 30 at 13:52
Ben YazolliBen Yazolli
12
asked Jan 30 at 13:52
Ben YazolliBen Yazolli
12
asked Jan 30 at 13:52
Ben YazolliBen Yazolli
12
12
add a comment |
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1400089%2fandroid-virtual-device-stalls-on-start-up%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1400089%2fandroid-virtual-device-stalls-on-start-up%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
