I'm attempting to connect the Visual Studio Android Emulator v. 1.0.50813.2 through Fiddler as a proxy so I can monitor some network traffic for an application I'm writing.
I've followed the MS provided instructions to a T. (http://blogs.msdn.com/b/visualstudioalm/archive/2015/05/06/using-fiddler-to-monitor-network-traffic-from-the-vs-emulator-for-android.aspx) still I get a "net:ERR_TIMED_OUT" message when attempting to hit the Fiddler echo endpoint.
I've also tried following the instructions in How to connect Visual Studio 2015 Android Emulator to network? as I had the Xamarin Android Player installed at one point.
I'm trying to use the current VS Emulator 5.1-inch Lollipop (5.1.1) XXHDPI phone emulator environment, but I've also tried the VS Emulator 5-inch KitKat (4.4) XXHDPI phone environment as well. Both produce the same results.
The emulator will connect to the network just fine without the proxy being set up. I've completely disabled the Windows firewall so that shouldn't be an issue.
The Fiddler proxy echo service works just fine on the host operating system (Windows 8.1) and the Loopback extensions have been added to ensure that it isn't a problem with app container isolation.
Does anyone know how I can correct this and get the VS emulator to correctly interface with Fiddler? I'm OK switching to anything more recent than Android API Level 15.
I had the same error with Fiddler
its odd but I read some where to uninstall Fiddler and then reinstall it worked for me
give it a go and let me see how you go
just got mine working now
Related
I have installed Xamarin in Visual studio 2015 and I have android and ios application within same solution file. when I am trying run android project in my local machine, I got error 'click retry to run the emulator in elevated mode. you do not have permission to modify internal Hyper-V network adapter settings,which are required to run the emulator'. So I clicked on "Retry" - it said windows packages changed to machine and I click on 'Yes', after that my local machine internet connection was gone. with the help of network engineer,Internet connection came back, my question is how can I run android application to my local machine without Hyper-V error.
I am a .Net developer and learning Mobile Application development, please can you help me out and suggest me that what I need to do?.
Thanks.
You did the right thing by retrying emulator in elevator mode, That is supposed to create internal switches to run your emulator and set up internet connection for it. Shouldn't affect your internet connection.
I'll advice
1. Try running the emulator again and let it create the adapters as Visual studio android emulators run in Hyper V.
Test app with a physical device connected to your computer
I am very new to Android development. I am trying to create and run an app from tutorial - https://developer.android.com/training/basics/firstapp/creating-project.html
But while running app it is showing me "No USB devices or running emulator detected" in Select deployment target dialog.
Background and what I tried:
I am using Lenovo K4 note Vibe.
Android version 5.1
I have enabled USB Debugging from my phone also checked "Enable OEM unlock"
I have selected USB "MTP" as connection mode when I connected my phone to machine.
I am using windows 7 and Android studio version 2.3.2
My device appears in "Device Manager" of my system i.e. It is installed properly.
When I connect my phone to my system it shows AutoPlay dialog, asking to run "Run Lenovo_suite.exe", I tried to see if my deice appears in Studio when I allow to run that app, but still no luck
I also tried by checking and unchecking "Enable ADB Integration" from Android studio, still no luck
I have already installed Android SDK for verion 5.1
I have also tried installing "Google USB driver".
I also tried connecting my device to all of my machine port
I am tried using Emulator, but it is really very slow on my machine, it takes around 2-3 hours just to boot. So, I am using my phone.
Your assistance in this matter is greatly appreciated
this problem just happen when your USB connection mode is not work in debug mode, Like:
File Transfer Or MIDI device
The Charging Only is Work in android 5 and above
GoodLuck
a addition to above answer i think if you try to debug it , you will get better result since android if had problem throw a error that says restart adb.exe ,
another thing whats your hardware config ?
and have you tried genymotion , i prefer it over android virtual device , working with a real device is better , but i prefer when to concentrate on monitor have device on it ;)
As per My experience many device not connect
So you need to try this Windows Software to detected your android phone
Install it on your windows system PDANET+
Thanks for your support guys. After 2 hours of struggle I found below:
When I connect my device to the machine, it shows me a AutoRun dialog to Run Lenovo_suite.exe(Which I mentioned in my question), but instead of auto running, I explored that newly created lenovo drive, which had 2-3 setup exe's(usb drivers and magicPlus), I installed both and restarted my machine. When I run MagicPlus software, it helped me to Authorize USB debugging with some kind of fingerprints. And now my device appeared in studio.
Since I read the news about Xamarin now being "free", I immediately installed Visual Studio 2015 Update 2 and the Android tooling (NDKs, SDKs for 19-23, Visual Studio Emulator for Android dated January 2016) to start working on an Android application.
Excited I launched the emulator from Tools -> Visual Studio Emulator for Android and installed the profile that is the best match for my own phone. Since my phone is on Android 6, I decided to get a profile for API Level 23 / Android 6.
Since I had already enabled Hyper-V a few months ago, the installation for the profile only had to add me to the Administrators group and create 2 network adapters.
So far, so good.
Upon starting the emulator, it would stay at "OS is starting...". I figured I'd wait a while. I figured I'd wait a while longer too. After that, I gave up the possibility of it going to work and started investigating.
I also tried other profiles, a few others from API Level 23, one from 22 and one from 19. Only the ones from API Level 23 did not work.
The following steps are what I came up with so far by Googling etc. I tried them in all sorts of combinations:
Rebooting
Disabling / enabling Hyper-V
Removing vEthernet adapters (through the Hyper-V Manager).
Running XDECleanup
Allowing XDE through my Windows Firewall as application (incoming)
Restoring the emulator software in Programs and Features
Enabling / disabling "Processor Compatibility" in Hyper-V Manager.
This is the data I've gathered so far:
A screenshot of the error message that the emulator gives after waiting a long time (10 - 15 minutes, maybe a little longer)
A screenshot of the last part of the log when being connected to the Android 6 VM:
A screenshot of the last part of the log of a working VM (this one's from an Android 4.4 VM):
Responses I've got so far from Microsoft:
-Those errors are normal
-And the only step I've tryed which they told me to, and I don't see here, it's this one:
On Hyper-V Manager, check the option for compatibility under CPU section
Besides from this, just make sure that on Hyper-V you get only 2 switches, the one you use to connect to the internet and the one that the VS Emulator for Android creates, I haven't got any results, but if you try, maybe you will.
In my case, I was mucking around with the VS emulator's virtual switches and had the network adapters in the wrong order.
After I moved the Windows Phone Emulator Internal Switch (Created when first running the VS Emulator) to the first Network Adapter slot in my settings, the emulator started up just fine. Apparently, order matters.
Had the same problem but got mine to work after trying a lot of things from different threads.
In the end I think this did the trick for me:
I added "c:\Program Files (x86)\Microsoft XDE\10.0.10586.0\xde.exe" as an exception in the firewall.
(i also switched of the firewall, but was probably unnecessary)
Temporarly disabled the WiFi device
Uninstalled VirtualBox
Removed all Virtual Switches in Hyper-V
Executed XdeCleanup.exe
Started the emulator again and it started up successfully!
Swiched of the emulator and enabled Firewall, Wifi device.
The emulator still starts successfully every time!
Thanks to all for sharing!
If you're using Xamarin, it's recommended that you use Xamarin Player. It's not Xamarin exclusive, it's just a much faster Android emulator. I use Android Studio, and the Xamarin Player is still faster on boot and launch than the default. This is just my recommendation to you, I have no clue how to fix your Visual Studio emulator, sorry.
I've played a lot with this and realized that I have had manually configured paging file on Windows. After restoring it to default all worked perfectly without messing with the virtual switches or adapters.
Just make sure that you have all Windows memory etc. settings set to default.
Regards, Mladen
My problem was that the system image was missing for the emulator.
When I opened the android virtual device manager it had an exclamation mark next to actions(i had to download the system image via the download link).
I had the same error message. The solution for me was:
Uninstall all emulators in the Visual Studio Emulator for Android
Check in Hyper-V-Manager if there also no instances
Unistall Visual Studio Emulator for Android
Run xdecleanup.exe (C:\Program Files (x86)\Microsoft XDE)
Uninstall Hyper-V from Windows features
Removed virtual ethernet adapters through uninstalling in Device Manager
(be sure to display disabled devices too)
Install Hyper-V from Windows features
Install Visual Studo Emulator for Android again
Download and install your emulator/profile
Run the emulator and have fun :-)
It seems there was a problem with the virtual switches and Hyper-V. The correct settings for the adapter looks like these:
Hyper-V-Manager:
Device Manager:
Network adapter:
Ethernet:
vEthernet (Virtueller Switch: Intel(R) Ethernet Connection (2) I219-LM #2):
vEthernet (Internal Ethernet Port Windows Phone Emulator Internal Switch):
Emulator network settings:
I am attempting to connect to the localhost of the machine from which I am booting a VS Android Emulator. I am able to successfully connect to the IIS Server when the Android version is Kitkat. However, I fail to connect when the VS Android Version is Lollipop or Marshmallow. The way I am connecting to the localhost is typing http://169.254.80.80 in the browser of the Emulator. As per http://developer.android.com/tools/devices/emulator.html#networkaddresses I should be able to connect to localhost using the IP address 10.0.2.2. However, this IP address doesn't seem to work for me.
VS studio Emulator work very fine and fast
see the screen shot that how you can connect VS Emulator to localhoat
The network addresses specified on http://developer.android.com/tools/devices/emulator.html#networkaddresses will not work for the Visual Studio Emulator for Android (well, except the very last one, which is the standard localhost IP address).
The address 169.254.80.80 is expected to work as a loopback to the host. There seems to be a bug regarding connectivity back to the host using that address on images running Lollipop (21) and above. I have logged a bug internally for this.
The previous answer is perfect but Android studio 3+ emulator need to add IP and port on proxy under setting.
I cannot use the browser and internet connection in my android app with android simulator.
When I try to open a homepage using the native webbrowser in the emulator, but when I use the ip address, it opens just fine.
How can I fix DNS problems in the android Emulator.
I already turned off the Windows Firewall, but it didn't work.
Data: Windows 7 x64 / Eclipse Plugin for Android / Android version 2.1
Do you have multiple NICs on your machine? The emulator might be trying to use a DNS that it cannot access (i.e. going through the wired DNS server if wired is disconnected). You can check which DNS server is being used by starting the emulator with the -debug-slirp flag.
See here for more info.