Found the solution!
You have to edit menu.lst file. Here is how:
boot in debug mode (usually the second option in boot menu)
when booting stops (for me it just hangs there with flashing cursor and without any prompt) enter mount -o remount,rw /mnt
enter cd /mnt/grub
enter vi menu.lst
right under the first boot entry find the line starting ...
There are some hotkeys listed for ICS, which hopefully still work with Kitkat:
Rotating the screen: (to get that operate we must to have activated “Auto-rotate screen”)
Press F12 two times in less than 2 seconds = Rotate 90º to the LEFT.
Press F11 two times in less than 2 seconds = Rotate 90º to the RiGHT.
Press F10 two times in less than 2 ...
The solution is change Pointing Device type to PS/2 Mouse:
Make sure the VM is not running (powered off)
Click on the VM name in the list (e.g., Android X86)
Click on the System category
Make sure you’re on the Motherboard tab
Change Pointing Device to PS/2 Mouse
Detailed instructions are here: Android X86 – No Mouse Cursor in Oracle ...
I'd like to extend and improve @Jay Smith answer based on personal experience.
He is right in the core thing that the cause of the issue is VGA resolution used by Android, but he is wrong in his assumption it is disposable fix and should be typed at each boot.
It can be made persistent, and should be! And I show you how:)
First of all, install the Android ...
There is a cross-platform version of Odin called JOdin. It can run in a web browser, or locally after downloading the JAR file. Either one requires Oracle Java 8 to be installed first.
Web version: https://builds.casual-dev.com/jodin3/
Offline version: https://builds.casual-dev.com/index.php?dir=JOdin3%2F '
The offline version is started with $ java -jar /...
This solution worked for me.
Just enter the following command in a terminal (change PROXYIP:PROXYPORT )
iptables -t nat -A OUTPUT -o eth0 -p tcp --dport 80 -j DNAT --to PROXYIP:PROXYPORT
I had too tried all your commands without success. I was stuck behind a proxy trying to setup ...
I also had problems with Android x86 vitual box on a Windows 7 Pro x64 AMD machine. I suppose we are all going to have slightly different issues depending on our architecture/hardware but they all seem to be similiar root causes. I think more emphasis should be on the architecture/hardware then the host OS. Try 32bit without/with EFI set in System, leave ...
Some progress here, but not the real thing. The following allowed me to boot Android x86 6.0 under VirtualBox correctly - but only once:
1) When booting the installation image, the initial screen gives you four options. Move the cursor to the last one: Installation - Install Android-x86 to harddisk".
2) Press the [Tab] key for edit options.
3) Immediately ...
As it was mentioned in the comments above, there is reference for Android X86 – mouse support in Oracle VirtualBox linked in this answer. AFAIK I had not to install additional packages like vbox-guest-utillities. As you can see the following list is empty:
$ dpkg -l | grep virtualbox-guest
$ dpkg -l | grep vbox-guest
I only had to change the "Pointing ...
I was able to install Android on Virtualbox normally but never got Whatsapp working on it, always errors and complications (Tablets are not supported, etc...). Finally I found the only solution that worked for me on a spanish website. NO SIM-card needed! Also beginners will understand!
Here's the way I did it:
Download Virtualbox for your system, install ...
For your reboot problem, it sounds like your boot order is booting off the .iso, i.e., cdrom, before it looks for the disk partition where you installed Android. Shut everything down and disconnect the .iso. You can just delete the CD device under the controller within VirtualBox Settings->Storage. You probably shouldn't just change the boot order or you ...
Since your virtual machine doesn't have a battery, it uses a fake battery sensor to provide the required battery information to the OS. While it's possible to make it read any amount of charge, and to change over time, it's convenient to use a fixed amount somewhere in the middle of the range, since values close to 100% or 0% can cause the Android OS and ...
I encountered this problem when trying to run QQ on Android 4.4 running in VirtualBox. F9-F12 were ineffective as soon as QQ started. The app "Ultimate Rotation Control" does the trick but does not resize the QQ window. So part of it gets to lie out of the virtual screen. Finally, I ended up redefining the screen size of the virtual Android to 360x640 (...
ADB backs up Settings + Apps(System + User) + Apps Data + User Data. That's it. The backup made through it doesn't come close to be related to booting it into virtual machine or even a real device. Short story, you have a backup definitely but that's not a system image.
If you want to create a system image, you need to do it through a Nandroid backup or a ...
You can’t run two different emulation stacks on your processor at the same time. Sorry, it wouldn’t happen.
Update: Your processor can only run one emulation system at the time. Kernel modules will “reserve” the right to use the processor’s emulation capabilities at the exclusion of any other emulator that want to use it. So you can only use VMware, ...
WhatsApp requires a SIM-Card as stated in a comment already. I know from various xda-developers discussions, that it's easier to do a backup from whatsapp on your phone with titanium backup, and then restore it inside your VM. Beware: the message database is local and messages are not synced across identical accounts.
There is no direct way for installing WhatsApp for virtual device from Google Playstore.
Android x86 doesn't come with all features (core features e.g play services, services framework etc) and SIM functionality is also missing.
The virtual device being treated as as "tablet" is incompatible, as WhatsApp states:
Tablet devices are not supported
Uninstall Intel x86 Emulator Accelerator from windows control panel. Then install it again in android studio.
Tools => Android => SDK manager => SDK tools => Intel x86 Emulator Accelerator (HAXM installer).
Then make sure that you plug a microphone or a line - in cable to the input socket of your pc.
This is how I got my own issue disappeared.
You don't find an Android x86 9.0 image because now (2019-03-03) they are still working to get the Android 8.1 release finished.
As far as I know the Android x86 project does not provide the possibility to upgrade an existing installation. The recommended way to get a new version whilst keeping the existing app data is to use two partitions, one system ...
The table below lists some Linux vide mode numbers.
As stated here:
The mode you wish to use is derived from the
VESA mode number. Here are those VESA mode numbers:
| 640x480 800x600 1024x768 1280x1024
256 | 0x101 0x103 0x105 0x107
32k | 0x110 0x113 0x116 0x119
64k | 0x111 ...
I have the same issue from Android x86 6 upper version in VBox. It runs in a MacBook Pro Late 2013 with 16GB RAM. I tried to set different size of CPU/RAM/VideoRAM but no help.
When I installed it in VMWare, there is no such issue. So it looks related to VBox.
I see you made a mistake,you should do cd then the derectory of the extracted file then sh flash-script.sh such as su enter cd /sdcard/download/ file name /META-INF/com/google/android/ enter" sh flash-script.sh
You can get a little further by using Grubs 'edit, e' key and adding debug DEUBG=1
That will give you a linux shell, and kernel debug messages.
Also, you can force by choosing the resident option and replacing USB_PARTITION=1 with INSTALL=2
Select "Yes" when it asks "Do you want to install boot loader GRUB".
Now you can boot into Android. (Works even rebooted)
Yes, there is a way to run a VirtualBox Linux guest VM and the Android emulator at the same time.
I have a working setup doing exactly this now, and its reasonably simple. To solve the problem above, you can run Genymotion as your Android emulator, and Virtualbox for your Linux guest VM virtual machine.
This counteracts the problem described in the answers ...
After a lot of searching and contacting Viber, I found out that, such version of android does what is regarded as unusual activity by Viber. This results in blocking all phone numbers used in such version of Android.
To unlock my phone number, I insisted sending messages to Open a Ticket, explaining the situation. They sent an email and I had to explain ...