I have a need to install an Android emulator to support things via a VPN halfway across the country. But none that I have found work. And I've spent many days trying various settings and releases. So far, the best is Android x86 for kernel 4.9. But it ONLY works Sometimes, when I use the menu to select android without Acceleration.
All the install instructions I've found on the net leave major things out. The last is that, if you install on ubunto, it configures grub, but doesn't configure it to pop up the boot menu. I got around that, but still no joy.
FYI I do NOT want to run android within Windows or OSx for security reasons AND because the wireless network it needs to connect to should have NO production computing equipment on it. it is an IoT network only. Major reason for needing emulator is to configure and manage a pill dispenser, But also because I need to help someone with AV and other controls that she is having trouble managing herself (due to age).
I'm not entirety clear as to some of your requirements or terminology, for instance when you say emulator, do you mean running within an existing Ubuntu operating system VM, or as a standalone Android VM ? If I understand the requirements:
I've used Android-x86 within a standalone VM without any issues. As an aside, as Android is a mobile operating system based on a modified version of the Linux kernel, is there something specific that is required to remotely manage remote devices ?
From there I can set it up, but at a point things hung and messed up the VM so that whenever I tried to boot back in I got an error saying that the vmware guest disabled the CPU. All I could do was create a new VM from scratch.
Also, If I let the android go to sleep, it goes to a black screen and NOTHING can revive it, short of powering off the VM and restarting. Unfortunately, Android does not let me configure it to NEVER sleep.
Also, I installed ubunto 22.04 lts in a vm because that loads open vmtools. Then installed android x86. But it hangs when booting to Android (sits at the console / # with a black screen. never gets to the android splash screen.
I knew someone was going to tell me Android isn't supported by vmware. But that is like telling me vmware doesn't support LibraOffice. It Does, because they both run on Linux, which it does support. If some form of the vmtools (open or vmware) can be loaded on the base linux, it would surely assist the operation of android or anything else that runs on top of it.
Not saying it can't run - as the Android-x86 port will run in a virtual machine. But the VMware Tools for Linux OS's certainly aren't supported and likely won't install. Perhaps you could modify the install/config scripts and get them working - and if so, please share back here with the community.
Just because VMware does not officially support an OS/Appliance doesn't mean they won't run, in realty there are many in this camp, as testimony shows. After all, is this not the technical challenge that is presented, and VMware provides the tool to support this.
This is -android-x86-in-vmware-fusion/ guide is near perfect, but read/write should be ON not OFF, because most Android apps don't work on VM because Android is natively an ARM system, not x86. Most apps will have a libmain.so error appear when the app is attempted to be loaded, but there is a hack hat works but it involves putting a file (houdini.sys) in system/etc and running an executable file (native bridge). This can only be done if the system is read/write mode (read only configuration won't work and you can't change to read/write after you've installed your system).
The quick answer is yes. You can run an x86 port of Android in a VMware virtual machine. There are several pages on the net that tell you what you have to do in order to get it to work. You'll have to configure things like IDE disks and such in the virtual machine to be sure that your virtual hardware is recognized by Android.
UPDATE: A quick google search for android workstation turned up what looks to be a pretty good guide. According to the guide, the virtual network adapter needs to be manually (i.e edit the vmx file) set to vlance (a pcnet32 driver is apparently in Android while an e1000 driver is not), and change the sound card should be changed to "SB X-Fi Audio"
KitKat is the latest Android release from Google with a lot of attractive changes both inside and outside. Before it hits every Android phone out there, you certainly have a new way to experience it with a very simple set up in VMware Workstation 10.
Last week, our team was very excited to see that the latest Android x86 release (a.k.a. 4.4 RC1) supports VMware virtual machines. Details are available in the release note at -x86.org/releases/releasenote-4-4-rc1.
I downloaded the ISO file and successfully set it up to run within Workstation 10 but you need to be aware of a couple tips and tricks. The part that you need to notice during installation is that once the Android ISO file is selected, it will be detected as FreeBSD and 256 MB of memory is assigned by default which was not enough to power on the VM without errors. After a few trials of modifying the memory settings of the VM, I found out that 4 GB of virtual memory could sufficiently make it run in a very smooth style.
Upon successful VM power up you will need to walk through a manual installation of Linux which is not covered in this article. However if during the installation you run into any problem when creating and formatting the disk, here is a brief reference you can use as a guide, -android-running-on-your-workstation.html. One thing to note is VMware Tools are not supported for Android.
Once the Android VM was setup and I powered on the VM, KitKat worked very well as you can see from the screenshot below. You can surf the web and use most of the Android application, mouse curser/clicks mimic the touch screen input, and I also tried to run it on Microsoft Surface tablet, where you can really leverage the touch screen to operate the Android VM. While most of applications I tried worked well, Google Maps App could not be rendered properly at the moment.
Other problems:
FDroid apk signing key still uses SHA1 despite a SHATTERED 2 attack published recently. Someone needs to let them know. They already had a forum topic about it two years ago but it never went anywhere.
Android emulator applications allows us to run our favorite Android apps or games directly from Linux system. There are many android emulators are available for Linux and we had covered few applications in the past. You can review those by navigating...
Other problems:
FDroid apk signing key still uses SHA1 despite a SHATTERED 2 attack published recently. Someone needs to let them know. They already had a forum topic about it two years ago but it never went anywhere.
The FDroid apk signing key still uses SHA1 despite its vulnerability to the SHAttered attack and others like it. While this subject was touched upon in a previous thread it it might be prudent to start looking for a way to move to a more secure...
I think if you start anbox in a certain way or a certain component of it directly from the command line, it should be more verbose and tell you what exactly makes it crash or return something that will lead you to a fix after searching for the reported error.
I estimated the RAM usage of a minimalist graphical base Linux OS to maybe be around 200-300 MB, the Whonix-Gateway could be run with 256 MB in CLI mode and the Whonix-Workstation itself with a minimum of 768 MB in graphical mode.
A good source for this is the apkmirror site whose ploads are vetted. It depends if closed source companies provide x86 versions off their apps. How likely it is to work without the Google framework stuff depends. YMMV.
Waydroid uses a container-based approach to boot a full Android system on a regular GNU/Linux system like Ubuntu. - GitHub - waydroid/waydroid: Waydroid uses a container-based approach to boot a fu...
Hi, I installed it, everything seems to have been done according to the manual, but anbox does not start.
Another question is how to disable/enable the firewall? what command is used to check whether the firewall is enabled/disabled?Do I need to disable firewalls in workstation or getway?
13. Then you'll see a screen which shows you if you to run Android or reboot. You can go either way, but don't forget to disconnect the ISO file before the next reboot otherwise you'll start over and you'll be presented with the LiveCD option again!
Ok, now you should see the VM booting into a configuration of Android, where you can personalize the system. As being said at the beginning, there is no necessary to tweak any other options, nor the VMX file for network access. The network works out of the box (I kept NAT as an option).
This website is maintained by Vladan SEGET. Vladan is as an Independent consultant, professional blogger, vExpert x16, Veeam Vanguard x9, VCAP-DCA/DCD, ESX Virtualization site has started as a simple bookmarking site, but quickly found a large following of readers and subscribers.
Thank you very much, I followed your instructions and now it works perfectly.
but I just want to ask if you would guide us through vmware tools installation for android (if there are vmware tools for android).
And thank you very much ?
Playstore and Sound
HELLO I INSTALLED ANDROID KITKAT in VM but the sound inside the android is not working also the microphone and cant download from googleplarstore
if you have any solution please reply
It installed ok in vmware workstation 11, as described.
As soon as I opened a game, the display went turtle (on the side) and the touchpad became unmanageable.
Pressing F11 and F10 (the only F keys responsive) flipped the display 180 degrees, so still on one side. Had a hell of trouble to escape from there.
Any 1 a suggestion?
Thank you,
P.
Some games detect which device you are using to serve you advertisements tailored to your device/OS, and other might just not be able to read the hardware that you have on your VM. I currently have android 6.0.1 on VMware Workstation 12 Player, it has 8 GBs of ram, 120 GB hard drive, and 6 processors, and i still get the hardware error.
b1e95dc632