[Android For Virtualbox Mac Os
Tilo Chopin
I am running a VirtualBox with android-x86 (as a replacement for the ultra-slow AVD emulator).Its a Linux VirtualBox running android 4.0, on a Windows 7 Host.The machine boots up and everything works fine, but if i leave the machine idle for less than 5 min, i can't perform any action - all the menus,buttons,etc are unresponsive although the android clock is changing, and i can go to command (alt + F1) and back to gui (alt + F7).Has anyone came across this phenomenon or has an idea what goes wrong here?
I am running android 3.2 RC2 eeepc on Virtual Box.The OS assumes it a tablet and sets the orientation to landscape by delfault.How can I manually change the orientation between landscape and portrait?
I use the VM to run an app that I am currently building.My app has many views and most are set to work in both portrait and landscape.One view is strictly set to portrait. When I launch this, the entire OS turns to portrait.How to revert to landscape mode?
Sadly, VBox is really bad at handling screen orientation. There is no shortcut to change screen orientation on the go I'm afraid. However, there are ways to force the screen into one orientation always. This is however probably not what you were looking for.
You could however try going with BuilDroid - which is a type of addon for VBox to try and support Android as best as possible. It makes sure that screens are "managed". I have no experience with BuilDroid myself, but it could have what you're looking for.
EDIT: The problem seems to have been solved by apps such as the one user2835272 referred to. I have not tried the app personally, but trying "Set Orientation" might be a proper solution for the problem now. Even better, if F9 - F12 works now, that is the functionality that should be used. Again, I haven't played around with VM Android for a while, so I cannot confirm this.
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 (portrait) as described here. It seems that QQ detects which side of the screen is longer and rotates according to this. So if you start with a portrait aspect ratio it will not rotate sideways. I do not about other apps, but guess they operate the same way.
To run VB on the full-screen mode on a vertical screen, select different sizes and scales from view>>virtual screen x>>resize to ../scale to xx%. After trying different combinations you will find the right settings for you.
(2) I use other OS like windows XP with NAT connection settings to: AMD PCNet FAST III (Am79C973) setting that work nice like internet and everything. so plz give me a other option for android-x86-4.2-20121225 to connect internet ??
In the virtual Android it will not show up but you will be able to browse and access the app store.You will need to change the settings inside of the Android OS to allow big files to be downloaded regardless of the network it want you to use by default, otherwise, for example, large games will not install.
The following are instructions on how to run Android-x86 inside VirtualBox.
Note: For optimal performance, make sure you have enabled either VT-x or AMD-V in your host operating system's BIOS.
Android-x86 versions tested against Virtualbox versions. Date Tested Virtualbox Host OS Android-x86 Result ??2.2.4Windows XP??Good ??3.0.2Fedora 11??Good Nov. 2 20175.2.0Windows 106.0-r3 32/64 bitGood
Download an ISO of Android-x86 from here. Caution If you are using Android-x86 for debugging purposes, some binaries (gdb for example) are built for 32-bit architectures and will not support debugging 64-bit binaries such as the Android app host. Download a 32-bit distribution instead.
If you have not already created a VirtualBox virtual machine for Android-x86 yet, do so as follows:
- Click the "New" button, and name your new virtual machine however you like. Set Type to Linux, and Version to Linux 2.6 / 3.x / 4.x. Note that you should choose the appropriate bit type for the version of Android-x86 that you downloaded.
- Specify how much RAM will be allocated to your virtual machine when you run it. Android doesn't specify a bare-minimum requirement for memory, just keep in mind what apps you plan on running. 2GB (2048MB) is a good place to start, and you can change this later if you need to.
- Create a new Hard disk image which will act as your machine's storage. The recommended starting size of 8GB is enough. Click through the rest of the options for creating your Hard disk.
Tested on VirtualBox 64-bit for Windows, version 5.2.0. Android-x86 version 6.0-r3, both 32-bit and 64-bit.
Select your machine, then click the Settings button and refer to the below recommended configuration to make sure your settings match.
- [System] Recommended: Processor(s) should be set above 1 if you have more than one virtual processor in your host system. Failure to do so means every single app (like Google Chrome) might crush if you try to use it.
- [Display]:
- Optional: Video Memory may be increased beyond the minimum selected automatically. The affects of this are unknown.
- Mandatory: Unless guest additions are installed[1], change the default VMSVGA to VBoxVGA.
- Optional: Enable 3D Acceleration may be checked. The Linux Guest Additions must (VirtualBox v6.1+) / may (VirtualBox v6.0 and below) need to be installed[2][1] to get any benefit from this. Failure to do so means you won't even be able to launch Android-X86 in the first place.[3]
- [Storage] Find the first "Empty" item (this should have an icon of a CD). In the Attributes, click on the CD icon with a small down arrow, and pick "Choose Optical Virtual Disk File...". Specify the Android-x86 ISO that you downloaded.
- [Audio] Intel HD Audio seems to be natively supported in Android-x86.
- [Network] By default, your installation of Android-x86 will be able to automatically connect to the internet. If not, you can try to enable WiFi in Settings/Network & Internet, and connect to showing VirtWifi. If you do not want to connect to the internet in VirtualBox, uncheck Enable Network Adapter under the Adapter 1 tab.
When you are prompted to Choose a partition:
- If you upgrade Android-x86 from a previous version, just select the existing partition. Agree to overwrite it when prompted.
- If this is a new VM, choose to Create/Modify partitions. Use Bootable but not GPT! This will cause the GRUB installation to fail later.
Continue through the installation. You should install GRUB when it prompts you to. You may also leave /system as read and write when prompted.
Once the installation is complete, force close/shut down the virtual machine and remove the ISO from the virtual CD drive.
Finaly, start Android-x86. If it's a new machine, once loaded you can perform the Android setup to begin using your machine.
This section describes two ways to upload music files into Android running on a vbox so you can play them by the Music app. Of course, you can save the files to the virtual disk mounted at /sdcard, as described above.
Adb is Android Debug Bridge, a tool to debug Android system. If you compile from source, it is located in out/host/linux-x86/bin/adb. Otherwise you can get it from Android SDK. Suppose the network of your vbox is OK, you can upload a file from your host by ADBHOST= out/host/linux-x86/bin/adb push /sdcard You need to know the ip of your vbox. You can get it by Alt-F1 and netcfg. You may also need to reboot Android to see the uploaded files. Of course in this way you have to mount /sdcard to a virtual disk partion.
For complex network settings of the VirtualBox VM, you should refer to Debug How To on how to connect adb to the VM.
If we want to debug with adb via network, we should ensure the ip of vbox can be accessed by host machine. So we should change the Network Adapter type of vbox to Bridged Adapter. After starting the android-x86, we should follow the above Settings/[Network] section to ensure the network of android-x86 is enabled, and enable USB debugging in Settings/System/Developer Options. Then we can get the device ip from Settings/System/About tablet/IP address. For example, if we see the ip address is 192.168.0.116, then we can use following command to connect android-x86 in vbox from host machine. adb connect 192.168.0.116 Then you can use adb command to debug android-x86 such as get log, and dump system information.
Did someone managed to connect android phone? I want to connect to tor network
with android phone, over wifi or usb cable. I tried to install hostapd but it was
not installed sucessfuly in virtual machine.
-wireless-access-point-hostapd
but no luck. I used this guide in my linux pc and it is ok, but in whonix-virtualbox is not working.
So, I am looking for some solution to connect android either via wifi or usb.
One of the reasons for using Whonix-Workstation in a VM and not on bare-metal is to provide an abstraction layer between your apps and your hardware. Compare that to routing your (compromised) phone through a VM (not to mention IMEI + who knows what unique identifiers).
I will not use all apps on android, only some apps for messaging, and I need them behind tor.
I think that web apps on android cant see IMEI, I will have to check that. Phone app can, but that is not internet and I will not use phone app while connected to tor, only internet.