Boot process of Android installed in VirtualBox seems to get stuck
I have installed Android 7.1 on VirtualBox 5.2 on Lubuntu 18.04 on Thinkpad T400 following this tutorial. Here is the configuration
In particular, I have assigned 1GB RAM to Android. On Lubuntu currently free shows this:
$ free -h
total used free shared buff/cache available
Mem: 7.7G 5.4G 492M 608M 1.8G 1.4G
Swap: 14G 850M 14G
When I boot up the Android VM, the screen shows some information about booting Android, but eventually is stuck with a blank screen with a cursor on the top left corner, and at the same time Lubuntu has slightly changed free RAM as below
$ free -h
total used free shared buff/cache available
Mem: 7.7G 5.8G 242M 628M 1.6G 992M
Swap: 14G 863M 14G
I guess Android getting stuck is not because of a shortage of RAM. I was wondering what the reason is and what I can do to solve the problem? Thanks.
Update
I've tried changing the assigned memory size in the settings of the virtual machine to 2GB and then to 4GB, but starting Android still gets stuck at the same place in both cases. I suspect that it is not the memory size but something else.
Related Why is starting Android from a vdi file in VirtualBox stuck?
boot virtualbox lubuntu android
asked Oct 29 '18 at 10:46
TimTim
8,12142104177
add a comment |
I have installed Android 7.1 on VirtualBox 5.2 on Lubuntu 18.04 on Thinkpad T400 following this tutorial. Here is the configuration
In particular, I have assigned 1GB RAM to Android. On Lubuntu currently free shows this:
$ free -h
total used free shared buff/cache available
Mem: 7.7G 5.4G 492M 608M 1.8G 1.4G
Swap: 14G 850M 14G
When I boot up the Android VM, the screen shows some information about booting Android, but eventually is stuck with a blank screen with a cursor on the top left corner, and at the same time Lubuntu has slightly changed free RAM as below
$ free -h
total used free shared buff/cache available
Mem: 7.7G 5.8G 242M 628M 1.6G 992M
Swap: 14G 863M 14G
I guess Android getting stuck is not because of a shortage of RAM. I was wondering what the reason is and what I can do to solve the problem? Thanks.
Update
I've tried changing the assigned memory size in the settings of the virtual machine to 2GB and then to 4GB, but starting Android still gets stuck at the same place in both cases. I suspect that it is not the memory size but something else.
Related Why is starting Android from a vdi file in VirtualBox stuck?
boot virtualbox lubuntu android
asked Oct 29 '18 at 10:46
TimTim
8,12142104177
add a comment |
I have installed Android 7.1 on VirtualBox 5.2 on Lubuntu 18.04 on Thinkpad T400 following this tutorial. Here is the configuration
In particular, I have assigned 1GB RAM to Android. On Lubuntu currently free shows this:
$ free -h
total used free shared buff/cache available
Mem: 7.7G 5.4G 492M 608M 1.8G 1.4G
Swap: 14G 850M 14G
When I boot up the Android VM, the screen shows some information about booting Android, but eventually is stuck with a blank screen with a cursor on the top left corner, and at the same time Lubuntu has slightly changed free RAM as below
$ free -h
total used free shared buff/cache available
Mem: 7.7G 5.8G 242M 628M 1.6G 992M
Swap: 14G 863M 14G
I guess Android getting stuck is not because of a shortage of RAM. I was wondering what the reason is and what I can do to solve the problem? Thanks.
Update
I've tried changing the assigned memory size in the settings of the virtual machine to 2GB and then to 4GB, but starting Android still gets stuck at the same place in both cases. I suspect that it is not the memory size but something else.
Related Why is starting Android from a vdi file in VirtualBox stuck?
boot virtualbox lubuntu android
asked Oct 29 '18 at 10:46
TimTim
8,12142104177
I have installed Android 7.1 on VirtualBox 5.2 on Lubuntu 18.04 on Thinkpad T400 following this tutorial. Here is the configuration
In particular, I have assigned 1GB RAM to Android. On Lubuntu currently free shows this:
$ free -h
total used free shared buff/cache available
Mem: 7.7G 5.4G 492M 608M 1.8G 1.4G
Swap: 14G 850M 14G
When I boot up the Android VM, the screen shows some information about booting Android, but eventually is stuck with a blank screen with a cursor on the top left corner, and at the same time Lubuntu has slightly changed free RAM as below
$ free -h
total used free shared buff/cache available
Mem: 7.7G 5.8G 242M 628M 1.6G 992M
Swap: 14G 863M 14G
I guess Android getting stuck is not because of a shortage of RAM. I was wondering what the reason is and what I can do to solve the problem? Thanks.
Update
I've tried changing the assigned memory size in the settings of the virtual machine to 2GB and then to 4GB, but starting Android still gets stuck at the same place in both cases. I suspect that it is not the memory size but something else.
Related Why is starting Android from a vdi file in VirtualBox stuck?
boot virtualbox lubuntu android
boot virtualbox lubuntu android
asked Oct 29 '18 at 10:46
TimTim
8,12142104177
asked Oct 29 '18 at 10:46
TimTim
8,12142104177
edited Oct 29 '18 at 16:43
Tim
asked Oct 29 '18 at 10:46
TimTim
8,12142104177
asked Oct 29 '18 at 10:46
TimTim
8,12142104177
asked Oct 29 '18 at 10:46
TimTim
8,12142104177
8,12142104177
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
Your Lenovo ThinkPad T400 has an Intel Core 2 Duo processor and 8GB DDR3 RAM. You allocated only 1GB Base Memory to the Android guest OS, but Android-x86 VirtualBox How To recommends that you allocate at least 2GB of RAM to the Android guest OS. For optimal performance, make sure you have enabled either VT-x or AMD-V in your host operating system's BIOS. The recommended starting size of 8GB is enough for creating a new VM. Click through the rest of the options for creating your hard disk. By default, your installation of Android-x86 will be able to automatically connect to the internet.
The alternative to installing Android in VirtualBox is the anbox snap package. Anbox has >=4GB RAM recommended hardware requirements. I was able to install Anbox successfully and run apps in it.
answered Oct 29 '18 at 11:11
karelkarel
59.4k13129151
Thanks. My T400 has 8GB RAM for Lubuntu. (1) Windows 8.1 having 2GB RAM on virtualbox works fine, while Android on virtualbox requires more RAM than Windows 8.1? (2) wine on my Lubuntu works fine, and does Anbox require more RAM than wine, and why does Anbox requiring 4GB RAM not work on Lubuntu?
– Tim
Oct 29 '18 at 11:26
If I assign 4GB to the virtual machine for Android, will running the Android immediately reserve 4GB physical memory? My 8GB physical RAM is often used 80%, when not running virtualbox, and I worry running Android will immediately cause heavy thrashing.
– Tim
Oct 29 '18 at 11:43
unix.stackexchange.com/questions/478420/…
– Tim
Oct 29 '18 at 11:55
Thanks. I change the assigned memory size in the settings of the virtual machine to 2GB and then to 4GB, but starting Android still get stuck at the same place in both cases. I suspect that it is not the memory size but something else.
– Tim
Oct 29 '18 at 13:59
You and I had a similar problem with Android-x86 in VirtualBox, so I'm starting to have my doubts about Android-x86, even though two instances is not a large enough sample size to properly judge the Android-x86 project.
– karel
Oct 29 '18 at 16:22
|
show 1 more comment
A YouTube user by the name foodisgood1989 has posted the following solution which has fixed this error for me:
In the system tab under settings for the android machine uncheck "Hardware clock in utc time" in the display tab set graphics controller to "VBoxVGA" and enable 3d hardware acceleration.
Thanks. Link please?
– Tim
Jan 24 at 20:44
It's one of the comments under this (youtube.com/watch?v=u4Bw2jeYwZg) video.
– jahu
Jan 24 at 20:49
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
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%2faskubuntu.com%2fquestions%2f1088222%2fboot-process-of-android-installed-in-virtualbox-seems-to-get-stuck%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
Your Lenovo ThinkPad T400 has an Intel Core 2 Duo processor and 8GB DDR3 RAM. You allocated only 1GB Base Memory to the Android guest OS, but Android-x86 VirtualBox How To recommends that you allocate at least 2GB of RAM to the Android guest OS. For optimal performance, make sure you have enabled either VT-x or AMD-V in your host operating system's BIOS. The recommended starting size of 8GB is enough for creating a new VM. Click through the rest of the options for creating your hard disk. By default, your installation of Android-x86 will be able to automatically connect to the internet.
The alternative to installing Android in VirtualBox is the anbox snap package. Anbox has >=4GB RAM recommended hardware requirements. I was able to install Anbox successfully and run apps in it.
answered Oct 29 '18 at 11:11
karelkarel
59.4k13129151
Thanks. My T400 has 8GB RAM for Lubuntu. (1) Windows 8.1 having 2GB RAM on virtualbox works fine, while Android on virtualbox requires more RAM than Windows 8.1? (2) wine on my Lubuntu works fine, and does Anbox require more RAM than wine, and why does Anbox requiring 4GB RAM not work on Lubuntu?
– Tim
Oct 29 '18 at 11:26
If I assign 4GB to the virtual machine for Android, will running the Android immediately reserve 4GB physical memory? My 8GB physical RAM is often used 80%, when not running virtualbox, and I worry running Android will immediately cause heavy thrashing.
– Tim
Oct 29 '18 at 11:43
unix.stackexchange.com/questions/478420/…
– Tim
Oct 29 '18 at 11:55
Thanks. I change the assigned memory size in the settings of the virtual machine to 2GB and then to 4GB, but starting Android still get stuck at the same place in both cases. I suspect that it is not the memory size but something else.
– Tim
Oct 29 '18 at 13:59
You and I had a similar problem with Android-x86 in VirtualBox, so I'm starting to have my doubts about Android-x86, even though two instances is not a large enough sample size to properly judge the Android-x86 project.
– karel
Oct 29 '18 at 16:22
|
show 1 more comment
Your Lenovo ThinkPad T400 has an Intel Core 2 Duo processor and 8GB DDR3 RAM. You allocated only 1GB Base Memory to the Android guest OS, but Android-x86 VirtualBox How To recommends that you allocate at least 2GB of RAM to the Android guest OS. For optimal performance, make sure you have enabled either VT-x or AMD-V in your host operating system's BIOS. The recommended starting size of 8GB is enough for creating a new VM. Click through the rest of the options for creating your hard disk. By default, your installation of Android-x86 will be able to automatically connect to the internet.
The alternative to installing Android in VirtualBox is the anbox snap package. Anbox has >=4GB RAM recommended hardware requirements. I was able to install Anbox successfully and run apps in it.
answered Oct 29 '18 at 11:11
karelkarel
59.4k13129151
Thanks. My T400 has 8GB RAM for Lubuntu. (1) Windows 8.1 having 2GB RAM on virtualbox works fine, while Android on virtualbox requires more RAM than Windows 8.1? (2) wine on my Lubuntu works fine, and does Anbox require more RAM than wine, and why does Anbox requiring 4GB RAM not work on Lubuntu?
– Tim
Oct 29 '18 at 11:26
If I assign 4GB to the virtual machine for Android, will running the Android immediately reserve 4GB physical memory? My 8GB physical RAM is often used 80%, when not running virtualbox, and I worry running Android will immediately cause heavy thrashing.
– Tim
Oct 29 '18 at 11:43
unix.stackexchange.com/questions/478420/…
– Tim
Oct 29 '18 at 11:55
Thanks. I change the assigned memory size in the settings of the virtual machine to 2GB and then to 4GB, but starting Android still get stuck at the same place in both cases. I suspect that it is not the memory size but something else.
– Tim
Oct 29 '18 at 13:59
You and I had a similar problem with Android-x86 in VirtualBox, so I'm starting to have my doubts about Android-x86, even though two instances is not a large enough sample size to properly judge the Android-x86 project.
– karel
Oct 29 '18 at 16:22
|
show 1 more comment
Your Lenovo ThinkPad T400 has an Intel Core 2 Duo processor and 8GB DDR3 RAM. You allocated only 1GB Base Memory to the Android guest OS, but Android-x86 VirtualBox How To recommends that you allocate at least 2GB of RAM to the Android guest OS. For optimal performance, make sure you have enabled either VT-x or AMD-V in your host operating system's BIOS. The recommended starting size of 8GB is enough for creating a new VM. Click through the rest of the options for creating your hard disk. By default, your installation of Android-x86 will be able to automatically connect to the internet.
The alternative to installing Android in VirtualBox is the anbox snap package. Anbox has >=4GB RAM recommended hardware requirements. I was able to install Anbox successfully and run apps in it.
answered Oct 29 '18 at 11:11
karelkarel
59.4k13129151
Your Lenovo ThinkPad T400 has an Intel Core 2 Duo processor and 8GB DDR3 RAM. You allocated only 1GB Base Memory to the Android guest OS, but Android-x86 VirtualBox How To recommends that you allocate at least 2GB of RAM to the Android guest OS. For optimal performance, make sure you have enabled either VT-x or AMD-V in your host operating system's BIOS. The recommended starting size of 8GB is enough for creating a new VM. Click through the rest of the options for creating your hard disk. By default, your installation of Android-x86 will be able to automatically connect to the internet.
The alternative to installing Android in VirtualBox is the anbox snap package. Anbox has >=4GB RAM recommended hardware requirements. I was able to install Anbox successfully and run apps in it.
answered Oct 29 '18 at 11:11
karelkarel
59.4k13129151
edited Oct 29 '18 at 13:21
answered Oct 29 '18 at 11:11
karelkarel
59.4k13129151
answered Oct 29 '18 at 11:11
karelkarel
59.4k13129151
answered Oct 29 '18 at 11:11
karelkarel
59.4k13129151
59.4k13129151
Thanks. My T400 has 8GB RAM for Lubuntu. (1) Windows 8.1 having 2GB RAM on virtualbox works fine, while Android on virtualbox requires more RAM than Windows 8.1? (2) wine on my Lubuntu works fine, and does Anbox require more RAM than wine, and why does Anbox requiring 4GB RAM not work on Lubuntu?
– Tim
Oct 29 '18 at 11:26
If I assign 4GB to the virtual machine for Android, will running the Android immediately reserve 4GB physical memory? My 8GB physical RAM is often used 80%, when not running virtualbox, and I worry running Android will immediately cause heavy thrashing.
– Tim
Oct 29 '18 at 11:43
unix.stackexchange.com/questions/478420/…
– Tim
Oct 29 '18 at 11:55
Thanks. I change the assigned memory size in the settings of the virtual machine to 2GB and then to 4GB, but starting Android still get stuck at the same place in both cases. I suspect that it is not the memory size but something else.
– Tim
Oct 29 '18 at 13:59
You and I had a similar problem with Android-x86 in VirtualBox, so I'm starting to have my doubts about Android-x86, even though two instances is not a large enough sample size to properly judge the Android-x86 project.
– karel
Oct 29 '18 at 16:22
|
show 1 more comment
Thanks. My T400 has 8GB RAM for Lubuntu. (1) Windows 8.1 having 2GB RAM on virtualbox works fine, while Android on virtualbox requires more RAM than Windows 8.1? (2) wine on my Lubuntu works fine, and does Anbox require more RAM than wine, and why does Anbox requiring 4GB RAM not work on Lubuntu?
– Tim
Oct 29 '18 at 11:26
If I assign 4GB to the virtual machine for Android, will running the Android immediately reserve 4GB physical memory? My 8GB physical RAM is often used 80%, when not running virtualbox, and I worry running Android will immediately cause heavy thrashing.
– Tim
Oct 29 '18 at 11:43
unix.stackexchange.com/questions/478420/…
– Tim
Oct 29 '18 at 11:55
Thanks. I change the assigned memory size in the settings of the virtual machine to 2GB and then to 4GB, but starting Android still get stuck at the same place in both cases. I suspect that it is not the memory size but something else.
– Tim
Oct 29 '18 at 13:59
You and I had a similar problem with Android-x86 in VirtualBox, so I'm starting to have my doubts about Android-x86, even though two instances is not a large enough sample size to properly judge the Android-x86 project.
– karel
Oct 29 '18 at 16:22
Thanks. My T400 has 8GB RAM for Lubuntu. (1) Windows 8.1 having 2GB RAM on virtualbox works fine, while Android on virtualbox requires more RAM than Windows 8.1? (2) wine on my Lubuntu works fine, and does Anbox require more RAM than wine, and why does Anbox requiring 4GB RAM not work on Lubuntu?
– Tim
Oct 29 '18 at 11:26
Thanks. My T400 has 8GB RAM for Lubuntu. (1) Windows 8.1 having 2GB RAM on virtualbox works fine, while Android on virtualbox requires more RAM than Windows 8.1? (2) wine on my Lubuntu works fine, and does Anbox require more RAM than wine, and why does Anbox requiring 4GB RAM not work on Lubuntu?
– Tim
Oct 29 '18 at 11:26
If I assign 4GB to the virtual machine for Android, will running the Android immediately reserve 4GB physical memory? My 8GB physical RAM is often used 80%, when not running virtualbox, and I worry running Android will immediately cause heavy thrashing.
– Tim
Oct 29 '18 at 11:43
If I assign 4GB to the virtual machine for Android, will running the Android immediately reserve 4GB physical memory? My 8GB physical RAM is often used 80%, when not running virtualbox, and I worry running Android will immediately cause heavy thrashing.
– Tim
Oct 29 '18 at 11:43
unix.stackexchange.com/questions/478420/…
– Tim
Oct 29 '18 at 11:55
unix.stackexchange.com/questions/478420/…
– Tim
Oct 29 '18 at 11:55
Thanks. I change the assigned memory size in the settings of the virtual machine to 2GB and then to 4GB, but starting Android still get stuck at the same place in both cases. I suspect that it is not the memory size but something else.
– Tim
Oct 29 '18 at 13:59
Thanks. I change the assigned memory size in the settings of the virtual machine to 2GB and then to 4GB, but starting Android still get stuck at the same place in both cases. I suspect that it is not the memory size but something else.
– Tim
Oct 29 '18 at 13:59
You and I had a similar problem with Android-x86 in VirtualBox, so I'm starting to have my doubts about Android-x86, even though two instances is not a large enough sample size to properly judge the Android-x86 project.
– karel
Oct 29 '18 at 16:22
You and I had a similar problem with Android-x86 in VirtualBox, so I'm starting to have my doubts about Android-x86, even though two instances is not a large enough sample size to properly judge the Android-x86 project.
– karel
Oct 29 '18 at 16:22
|
show 1 more comment
A YouTube user by the name foodisgood1989 has posted the following solution which has fixed this error for me:
In the system tab under settings for the android machine uncheck "Hardware clock in utc time" in the display tab set graphics controller to "VBoxVGA" and enable 3d hardware acceleration.
Thanks. Link please?
– Tim
Jan 24 at 20:44
It's one of the comments under this (youtube.com/watch?v=u4Bw2jeYwZg) video.
– jahu
Jan 24 at 20:49
add a comment |
A YouTube user by the name foodisgood1989 has posted the following solution which has fixed this error for me:
In the system tab under settings for the android machine uncheck "Hardware clock in utc time" in the display tab set graphics controller to "VBoxVGA" and enable 3d hardware acceleration.
Thanks. Link please?
– Tim
Jan 24 at 20:44
It's one of the comments under this (youtube.com/watch?v=u4Bw2jeYwZg) video.
– jahu
Jan 24 at 20:49
add a comment |
A YouTube user by the name foodisgood1989 has posted the following solution which has fixed this error for me:
In the system tab under settings for the android machine uncheck "Hardware clock in utc time" in the display tab set graphics controller to "VBoxVGA" and enable 3d hardware acceleration.
A YouTube user by the name foodisgood1989 has posted the following solution which has fixed this error for me:
In the system tab under settings for the android machine uncheck "Hardware clock in utc time" in the display tab set graphics controller to "VBoxVGA" and enable 3d hardware acceleration.
answered Jan 24 at 20:42
community wiki
jahu
Thanks. Link please?
– Tim
Jan 24 at 20:44
It's one of the comments under this (youtube.com/watch?v=u4Bw2jeYwZg) video.
– jahu
Jan 24 at 20:49
add a comment |
Thanks. Link please?
– Tim
Jan 24 at 20:44
It's one of the comments under this (youtube.com/watch?v=u4Bw2jeYwZg) video.
– jahu
Jan 24 at 20:49
Thanks. Link please?
– Tim
Jan 24 at 20:44
Thanks. Link please?
– Tim
Jan 24 at 20:44
It's one of the comments under this (youtube.com/watch?v=u4Bw2jeYwZg) video.
– jahu
Jan 24 at 20:49
It's one of the comments under this (youtube.com/watch?v=u4Bw2jeYwZg) video.
– jahu
Jan 24 at 20:49
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- 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%2faskubuntu.com%2fquestions%2f1088222%2fboot-process-of-android-installed-in-virtualbox-seems-to-get-stuck%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
