I am following the instructions given HERE
I can install it to the vmware hard disk fine and get it running, but then it says to open a terminal and execute su
The terminal says that it cannot make me a root and nothing else
I am not able to go any further after this and so the internet isn't working in the virtual machine
Moreover, the internet works if I was just using the live CD version, without me having to do anything else
How do I get root permissions in android x86 on VMware?
--- EDIT---
After playing around some more with this I have noticed another problem: when I try to start the virtual machine, most of the times it reaches the Chrome coloured android startup logo, the logo animates continuously but the screen is sort of stuck at that phase. And if I loose focus to the vmware window and come back, I see that the window is blank and I am not sure if the virtual machine is even further loading or not. How do I properly get Android x86 to work on vmware (with full install on it's virtual hard disk and not just the live CD version? Should I try other virtual machines? I have not been able to get others such as qemu and bochs to work in the past and see that vmware is the easiest and most stable option, so I would like to run this in vmware if possible.
check here www.bitdirect.nl/?p=128
I followed this with a few little tweaks here and there and it worked perfectly.
only downside is transferring data outside of the android os is a pain.
I bought a new Nexus 7, and Eclipse cannot see it. It is appearing in Device Manager as Android Device ---> Android Composite ADB Interface. There is no other devices category, and I have updated the list.
My SDK Manager has everything except for the obsolete installed and updated. I have also tried reinstalling Eclipse all together.
I have updated the driver via \adt-bundle-windows-x86_64-20130514\sdk\extras\google\usb_driver and it says the best one is already installed. USB-debugging is enabled on the Nexus 7. I am all out of ideas. Please help!
Uninstall and Reinstall Nexus 7
Update:
Plan B:
OK you say it didnt work.... this is kind of a long shot but saved my bacon a lot when I was working as a technician in my past life and had to find unknown device drivers.
Right click your Nexus in device manager , select properties and go to this page
The example shows my radeon card but if you google this hardware ID( the top one in your pc), and check a couple of random sites , you are likely to find it. This method is used for finding unknown drivers, and you may as well give it a shot as you have exhausted most options.
Plan C:
Trying the same nexus on a different windows7 computer to see if it installs . If it does, then you can try to extract it from that computer ( e.g. using driverguide software) and force windows on your main pc to use that.
Plan D:
run sysprep.exe on your PC by typing it in RUN and double clicking the file and clicking Generealize.This prepares your pc for imaging and removes all drivers. Note that you'll have to activate windows again after this.
Plan E:
And lastly, the call center answer , use system restore, although the damned thing fails 90% of the time and install again after a reboot. or a whole scary reinstall of windows :(
//Ignore below now as it didn't work for you
Download this driver http://www.samsung.com/us/support/owners/product/SCH-I515MSAVZW
You can also check this question for a solution for Nexus and an alternative driver. I had the same problem , although not with a Nexus, but a sony Xperia, and I had to download a generic driver to get it going. The above samsung site has the driver, but the model is called SCH-I515. You should be able to fix it without the generic driver
ADB dosn't recognize my Galaxy Nexus - Win7
Whenever I have Virtualbox running, I cannot start an Android emulator image (and vice versa). The error message in the AVD manager is
ioctl(KVM_CREATE_VM) failed: Device or resource busy
ko:failed to initialize KVM
How can I make both run at the same time?
That is a Ubuntu 64 bit, all involved software is of the latest released version.
Removing the kvm kernel modules (using 'sudo rmmod kvm_intel kvm') makes it possible to run the Virtualbox and the Android emulator at the same time but the performance of the Android emulator in such a setup is extremely bad. If possible it is better to shutdown the Virtualbox emulator and unload its driver (vboxdrv) by running 'sudo /etc/init.d/vboxdrv stop'. Google suggests this "solution" on its Android Emulator page in the section about Linux.
I got the same VirtualBox conflict.
Solved it by using ABI different from "x86" (armeabi-v7a in my case)
I stopped the virtual machines I had running with VirtualBox. This made the error disappear.
I had the same problem on Ubuntu 13.10.
Try to remove kvm and kvm_intel kernel modules.
To do this:
Stop all emulators.
Run command: 'sudo rmmod kvm_intel kvm'
Without these kernel modules Virtualbox and Android emulators can work at the same time.
BTW, I do not know why the modules are loaded.
There is finally a fix for this.
Follow these steps for macOS:
In Android Studio Go to Tools -> Android -> SDK Manager
Confirm you have the latest version of Intel Emulator Accelerator HAXM installed (v6.1.1) .
Go to the extras directory of the Android SDK location displayed in the preferences. On MacOS you can do this:
open ~/Library/Android/sdk/extras
Install the HAXM packing by opening IntelHAXM_6.1.1.dmg, then opening IntelHAXM_6.1.1.mpkg in the mounted folder, and following the installer instructions.
Follow these steps for Windows:
In Android Studio Go to Tools -> Android -> SDK Manager
Confirm you have the latest version of Intel Emulator Accelerator HAXM installed (v6.1.1) .
Go to the extras directory of the Android SDK location displayed in the preferences. Something like:
C:\Users\<username>\AppData\Local\Android\sdk\extras
In that directory is some kind of file like intelhaxm-android.exe. Run it.
You also can change CPT/ABI setting from x86 to arm in emulator settings.
I finally made this problem obsolete by using Genymotion instead of the standard Android emulator. Besides not having this conflict, it is several times faster than the normal emulator.
Another solution is to use libvirt backed vagrant using vagrant-libvirt plugin.
For those who are developing on Linux and are stuck with a host of back-end systems running inside virtualbox, a simple solution is simply to create a virtualbox X86 Android VM and expose the 5555 port on the NAT interface tunnelled from localhost through PAT.
No need for slow arm AVD, no need for libvirt/vagrant let alone killing kvm!
Then let adb know about it
$ adb tcpip 5555
restarting in TCP mode port: 5555
$ adb connect 127.0.0.1
connected to 127.0.0.1:5555
$ adb devices
List of devices attached adb server
* daemon started successfully
emulator-5554 device
Then, pressing run or debug, in Android Studio will deploy and execute on that VM.
You have complete control under Android Studio debugger.
Though it's a workaround either, but definitely better than disabling KVM as everyone suggesting.
Just run the virtualbox guest in KVM instead. For example (kvm here is just a script running a qemu-system-x86_64 -enable-kvm):
kvm Win7.vdi -boot c -m 2G -vga qxl
In some cases, we need to keep virtualbox machines up and running therefore let all the virtualbox machines keep running, switch to physical mobile device to test your application instead of emulator.
you can use expo if you are doing with react-native or your real android/ios device.
I resolved it by installing HAXM 6.1.2.
Please refer to the following link for details :- https://forums.docker.com/t/cant-using-docker-for-mac-with-android-emulator-haxm/8939/11
This might be out of topic, due to the fact that OP requested VirtualBox + KVM in the same time, but still, it might be the workaround:
I was looking for a way to launch Windows 7 and AVD on Ubuntu 18.10 x64. Turning off KVM is not an option due to the fact that performance of AVD is critical to me. I have installed Windows 7 via Virtual Machine Manager (virt-manager package) and now both the AVD and Windows 7 are hardware accelerated.
Here is how solved this issue, using vagrant and it's two plugins 'libvirt' and 'mutate':
Open terminal and set environment variables:
export VAGRANT_DEFAULT_PROVIDER=libvirt
export VAGRANT_HOME=/home/directoryToStoreVagrant/
VBoxManage list vms
Now copy the a the code obtained from last command like
"c1530713-aec2-4415-a6b5-b057928c7e5f" and use in the following:
vagrant package --base c1530713-aec2-4415-a6b5-b057928c7e5f
--output window7.box
vagrant init window7
vagrant up window7 --provider=libvirt
vagrant box list
You need to install some vagrant plugins like libvirt and
mutate. Mutate will convert .box to libvirt VM:
vagrant plugin install vagrant-libvirt
vagrant plugin install vagrant-mutate
Converting vagrant box to libvirt:
vagrant mutate window7_.box libvirt
Now you can initialise the vagrant VM. If any error persist move to
edit your Vagrant file. Like for me I uncomment the line starts with
config.vm.network and then run command below:
vagrant up --provider=libvirt
This is how I was able get rid of this error completely
How can I connect my Android emulator to the internet, e.g. to use the browser? I've found lots of advice on what do to when your connected through a proxy, but that's not the case here, my machine (Windows 7) is directly connected to the router.
I think some of the answers may have addressed this, however obliquely, but here's what worked for me.
Assuming your problem is occurring when you're on a wireless network and you have a LAN card installed, the issue is that the emulator tries to obtain its DNS settings from that LAN card. Not a problem when you're connected via that LAN, but utterly useless if you're on a wireless connection. I noticed this when I was on my laptop.
So, how to fix? Simple: Disable your LAN card. Really. Just go to your Network connections, find your LAN card, right click it and choose disable. Now try your emulator. If you're like me, it suddenly ... works!
If you are on Mac - try this -
GoTo Apple Icon -> System Preferences -> Network
Click on the gear icon on the and select 'Set Service Order'
Bring the active interface before other interface.
Restart the Android Emulator.
[EDIT]
For more recent version of Android Studio, the emulator you need to use is no longer in the ~/Library/Android/sdk/tools folder but in ~/LibraryAndroid/sdk/emulator.
If while trying the below solution you get the following message "PANIC: Missing emulator engine program for 'x86' CPU.”, then please refer to https://stackoverflow.com/a/49511666 to update your bash environment.
Operating System : Mac OS X El Capitan
IDE : Android Studio 2.2
For some reasons, I wasn't able to access internet through my AVD at work (probably proxy or network configuration issues).
What did the trick for me was to launch in command line my AVD and giving manually the Google public DNS 8.8.8.8.
In your Terminal go to the folder tools of your Android sdk to find the 'emulator' program:
cd ~/Library/Android/sdk/tools
Then retrieve the name of your AVDs :
emulator -list-avds
It will return you something like this:
Android_Wear_Round_API_23
Nexus_10_API_22
Nexus_5X_API_22
Nexus_5X_API_24
Nexus_9_API_24
Then launch the AVD you would like with the following instructions:
emulator -avd NameOfYourDevice -dns-server 8.8.8.8
Your AVD is launched and you should be able to use internet.
My platform: Mac OS 10.6.4
Eclipse: 3.6
I had a similar problem where my map app background was grey (no tiles) and the browser was unable to connect to the internet.
Within Eclipse I went to Run Configurations -> Target and added "-dns-server X.X.X.X" and everything worked fine afterwards. (obviously X.X.X.X was the IP address for my DNS server).
In order to use internet via proxy on emulator try these steps it Worked for me:
Go to settings->Wireless & networks->mobile networks->Access Point Names.
Press menu button. an option menu will appear.
from the option menu select New APN.
Click on Name. provide name to apn say My APN.
Click on APN. Enter www.
Click on Proxy. enter your proxy server IP. you can get it from internet explorers internet options menu.
click on Port. enter port number in my case it was 8080. you can get it from internet explorers internet options menu.
Click on User-name. provide user-name in format domain\user-name. generally it is your systems login.
Click on password. provide your systems password.
press menu button again. an option menu will appear.
press save this and try to open your browser. I think it has helped u?
righ click on the Project in Eclipse
select Run As -> Run Configurations ...
select Android Application and then select "target" tab
Looking for "Additional Emulator Command Line Options" and put this command line to text box
-http-proxy http://< username >:< password >#< hostname >:< port >
There are different solutions to this problem . One of these , i will show you on my experiment and outcomes seen on results using a recent android studio and AVD images downloaded 2017.
First thing you have to do is launch your AVD from android studio.(in my case i choose NEXUSAPI25 android 7.1 image)
Goto Settings->Wirless and Networking - > Cellular Network - > Access Points -> (+) press add - > enter the following if you dont have NTLM proxy or proxy at all (that means you are directly connected)
a. add apn name as myAPN
b. add apn server => www
c. save and try browsing the internet.
if this doesn work add 'ANDROID_SDK_ROOT' in you environment variable
Then , launch AVD using emulator command as follow
emulator -avd Nexus25 -dns-server 8.8.8.8
For those who use NTLM proxies , i will show you how it work for me next.
add your Android_sdk_root path into your environment variable. THis make command line code read succesfully like using AVD names and so on.
Launch your emaulator using the following command
>emulator -avd Nexus_5X_API_25 -http-proxy http://username:password#ipaddress:port
ENTER
Have you tried starting the emulator with administrative privileges? It worked for me, I'm running Windows 7 64bit)
In my case I just had to launch the Android virtual device (AVD) from the "Android SDK and AVD Manager", and it was working
If you are behind a proxy in the SDK Manager, under Tools -> Options, do NOT configure the proxy settings.
When you run from the command line add -http-proxy:
emulator.exe -avd YOUR_AVD_NAME_HERE -http-proxy PROXY:PORT
Worked for me.
I also experienced the same problem.
The simplest solution I found out is:
Go to your Android\Sdk\emulator folder and open command prompt.
Type emulator -list-avds to see available emulator names.
Type emulator -avd name-of-your-device -netdelay none -netspeed full
-dns-server 8.8.8.8 command and press enter.
I encounter this issue when I first run the simulator, I solved it by setting the dns server with
Library/Android/sdk/platform-tools/adb shell getprop net.dns1
get the current dns server of simulator 10.0.2.3
Then set it to my lan dns server
Library/Android/sdk/platform-tools/adb shell setprop net.dns1 192.168.1.1
I had similar problem. I have installed an application that required INTERNET permission (and used it), and all of sudden, worked.
Guys, check also whether if you are not connected through a VPN somewhere, because it also can disturb the Internet connection.
blacharnia
In eclipse go to DDMS
under DDMS select Emulator Control ,which contains Telephony Status
in telephony status contain data -->select Home , this will enable your internet connection ,if you want disable internet connection for Emulator then --->select None
(Note: This will enable internet connections only if you PC/laptop on which you are running your eclipse have active internet connections.)
After reading this I decided to look at my "NICs". I put this in quotes because like many I am running virtual nics for devices like Hamachi and Virtual Box. After I disabled Hamachi I am able to use the internet. My guess is that the emulator picks the first available nic regardless of whether it is virtual. Now to find out if I can rearrange my nic order without tearing my box down.
Windows 7 32bit
My Service Order preferences were correct (Wi-Fi was first) but still could not connect.
Answer was to turn off the Thunderbolt Bridge:
System Preferences > Network > Thunderbolt Bridge
Then set Configure IPv4 to off and Apply your changes.
No need to screw around with Access Points in the emulator.
I solved it my disabling all network connections except the wifi connection I was using, then setting the properties on that one remaining enabled connection to have statically assigned DNS addresses. (no DHCP) This was on Win7 64bit
Thanks for the pointers. They really helped. The "Firewall" word clicked an idea in my mind.
I have a Windows XP machine with WIFI connection and no proxy. I have Norton Internet Security running on my machine which has a Smart Firewall. This Smart Firewall manages programs' access to network, including emulator.exe. I went into Settings -> Program Control and then granted full access to emulator.exe. After this I started Android Emulator and bang... I could connect to internet.
Hope this helps new folks.
~Saggy
Within the Android emulator, turning Airplane Mode on, then off again worked for me.
If you're on MacOS with 2.2 and you keep seeing an error about data connectivity, try the above, it works.
I removed all the network interfaces via Sys Prefs except LAN
Even thought my DNS is provided by DHCP, I retyped DNS with just one server
I used -http-proxy on the command line to specify one
It starts working at the office. Phew.
I think sometimes it's just enogh to simply restart the virtual device. :-)
I had the same problem on my virtual windows 7.
Go to Network Connections
Alt > Advanced > Advanced Settings...
In the second tab bring the internet networks interface on the top
hope it's helpful
thanks to
I had this issue due to a network change after I opened the emulator. If you change your WiFi after you start the emulator, you only need to restart the emulator to get internet access
yes--in win 7 start the emulator with administrator privs and all will be well--or at least you'll get the wireless going in android.
I had a similar problem on Win7 64 bit. Tried disabling my hamachi and virtualbox adapters and didn't work. Tried starting avd as admin and didn't work. In the end I disabled the teredo tunneling adapter using the info on this site and it worked:
http://www.mydigitallife.info/2007/09/09/how-to-disable-tcpipv6-teredo-tunneling-in-vista/
I found that starting the emulator with 'wipe user data' checked cleared this problem up for me after I rebuilt my dev machine from Vista x64 to Win7 x64.
it appears there might be a few reasons why there might be no internet connection for an emulator, in my case i was working from home where i have a wireless connection then came into the office and plugged in direct, however although my wireless connection was disconnected it was not disabled resulting in no emulator connection. my understanding is that when it starts up it looks for a network adapter and if there is any conflict here it might result in no internet connection. to resolve go to Start > Settings > Network Connections right click on Wireless Network Connection (if you are not using wireless) and select disable
I am not using a proxy...however I am using a script...Is there anyway around this. I am behind a company firewall
I'm not sure if this is your issue, but here's how I fixed mine.
I always had this "No DNS servers found" error when starting the emulator and did a lot of research on google to no avail. Anyway, I found a post somewhere (can't find it anymore) that was saying that the number of NICs, number of DNS entries could affect the emulator. Also, knowing that the emulator uses a Windows API function (GetNetworkParams()) to resolve DNS entries, I couldn't rely on the %WINDOWS%\System32\Hosts file.
However, I did went in the NICs properties (on Windows 7) to find that I was specifying a static IP, but no DNS entries. So, I got the DNS entries from my router and plugged them in the NICs property. I restarted the emulator and it is now using the correct DNS entries!
I can use my internet connection with the emulator now, and it works wonders!
Hope it helps!
I thought I experienced issues with connecting my emulator to the internet but it turned out to be problems with the code I was using. I know its obvious but in the first instance try the browser on the emulator to confirm you have no internet access. I would have saved an hour if I had done that first.