I have installed Android 7.1 on VirtualBox 5.2 on Lubuntu 18.04 on Thinkpad T400 following this tutorial. Here is the configuration

VirtualBox dialog

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.

booting Android - GRUB menu

Android seems to be booting

black screen


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?

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.

  • 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 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 at 11:43
  • 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 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 at 16:22

Your Answer

 

By clicking "Post Your Answer", you acknowledge that you have read our updated terms of service, privacy policy and cookie policy, and that your continued use of the website is subject to these policies.

Not the answer you're looking for? Browse other questions tagged or ask your own question.