I have installed Xamarin under Visual Studio 2015 Community Edition, including the intel HAXM hardware acceleration, but I have a problem with the emulator:
None of the default Xamarin avd's seem to have been installed
When I create one myself and run it, it doesn't look right.
The attached image should make it clear. As you can see the top bar takes up about 1/5th of the screen height, and the bottom bar about 1/4.
Does anyone know what is wrong?
I'm also confused by the buttons on the right hand side. Are they supposed to be there?
VS can use AVDs but it's better to use emulators for Android for VS. It is using Hyper-V virtual PCs.You need to download and run Visual Studio Emulator for Android, then download VMs
Because the screen display size is too small. You should use an AVD Device Template to get a normal size:
When you launch it, make sure that the display doesn't get scaled. You can scale this, but you might accidentally make it too small
The buttons on the right are due to the Skin you have selected.
Based on your screenshot, it looks like you potentially are using the old version of emulators. Make sure to update your Android SDK tools and then re-create an emulator to benefit from the 2.0 emulators:
https://developer.android.com/studio/run/emulator.html#dependencies
After a reboot things seem to be working which weren't before, so I guess something hadn't finished installing. I still find that when I use a skin I don't see any message about hardware acceleration HAXM working, but I think it probably is. With regards to speed, it improved dramatically when I selected the option to 'Use host GPU'.
The HVGA skin still looks wrong, but I downloaded some ones for the Samsung Galaxy which work well.
Related
I'm experiencing a really weird and frustrating issue with the Android Emulator on macOS Monterey.
I have "tap to click" enabled on my Macbook Pro (Mid 2015 15"), and it works fine in all other apps. But somehow, when the emulator window is active it seems to miss almost every other tap. If I click hard instead of tapping, it catches every click. The tap sensitivity in the Trackpad settings is set to "light".
So, it seems that the emulator window is somehow less sensitive to tapping than all other apps. I don't even know how this is possible, is there even such a thing as app-specific tap-sensitivity??
What's more, it's not only the emulator window itself that has this issue, but the emulator settings window as well. If I tap the "Enable clipboard sharing" toggle, it misses about 50% of the taps. If I click hard, it catches them 100%. If I try the same in some other app (tested with the "System Preferences" window), it catches 100% of the taps.
I have tested and tested this again to make sure I'm not biasing the results, but there really is a difference, and it's driving me nuts. I think it appeared after updating to Monterey, but not 100% sure of the exact timing correlation.
Any ideas??
My problem was really similar, I am using MAC with apple mouse, so I could fix it by disabling the mouse wheel on Android Emulator Extended Controls.
Hope that help
I've noticed the same issue some time ago. Unfortunately, I didn't find any solutions.
However, there are a couple of good enough workarounds:
Launch the emulator in a tool window. Anyway, this is a default approach for modern versions of Android Studio. To enable/disable it check Preferences -> Tools -> Emulator -> Launch in a tool window.
Use alt emulators. For instance, Genymotion doesn't have such an issue.
I ran into a simmiliar issue for me and the solution that i found was enabling "tap on click" to in the "system preferences" -> "trackpad".
I am new to the Android Emulator, but am experiencing the same issue in Ubuntu, even though I have tap-to-click disabled in the OS. I hate tap-to-click, so having an ultra-sensitive-to-touch Android screen emulated on my laptop is beyond frustrating.
Looking at the documentation, I came across the SOURCE_CLASS_POINTER method, which states:
The input source is a pointing device associated with a display. Examples: SOURCE_TOUCHSCREEN, SOURCE_MOUSE. A MotionEvent should be interpreted as absolute coordinates in display units according to the View hierarchy. Pointer down/up indicated when the finger touches the display or when the selection button is pressed/released. Use getMotionRange(int) to query the range of the pointing device. Some devices permit touches outside the display area so the effective range may be somewhat smaller or larger than the actual display size.
In reading that, I've come to believe this may actually be the default behavior due to touchpad events being interpreted through the SOURCE_TOUCHSCREEN method, rather than SOURCE_TOUCHPAD or SOURCE_MOUSE.
Unfortunately, I don't have a solution as much as a workaround:
I plugged in a mouse and tested the pointer up/down movements over the screen, which this part of the document suggests should register as a press. However, with the mouse it only responds to clicks. So it suggests to me that it is indeed properly interpreted as a SOURCE_MOUSE controlled pointer and not a SOURCE_TOUCHSCREEN controlled pointer.
So unless we can find out how to make the AVD properly interpret a touchpad as a touchpad, and not a touchscreen, using a mouse seems like the best solution.
For reference, I'm including this link to the AVD manual: https://developer.android.com/studio/run/emulator
UPDATE: Somehow over the period of about 18 hours and several restarts, my AVD no longer does tap-to-click on its virtual screen. It would be very hard to pinpoint exactly what changed because I've been updating packages frequently since I'm running a pre-alpha release of Ubuntu, but I think it's from using X11 instead of Wayland.
Which got me thinking, you could try changing your display server from Cocoa to X11. Thankfully, MacPorts, the MacOS version of the FreeBSD Ports Tree, makes it fairly easy to cross-compile software. It contains build recipes for multi-platform unix-like software, much like HomeBrew but often allowing for more customization.
That tap issue was annoying enough it's probably worth giving a shot.
(from macports website) The X11 windowing environment, for ports that depend on the functionality it provides to run. You have multiple choices for an X11 server: https://www.macports.org/install.php
I would build them in this order:
MacPorts: X11 - If you build it, you'll have a bunch of libraries already
MacPorts: QEMU - use make configure menu to select GTK3+, if there's no option for X11, try this build flag with make after you install X11 (pointing it at your X11's lib dir):
make -L/opt/X11/lib -lX11
Lastly, MacPorts: Android Platform tools
Related StackOverflow Q/As:
Compiling a C program that uses OpenGl in Mac OS X
Running x11 on Mac OS
Getting an error message, 'System UI isn't responding.' and it gives me the options 'Close app' or 'Wait' when debugging Xamarin.Forms. This is on the emulator that launches. I have set the memory at 512 and the resolution at 800x600 as some have suggested in other threads. I also did a 'factory reset.' Nothing has helped so far.
Are there any other options that may get me past this? I just purchased a Xamarin class from Udemy and can't even get past the first few videos.
I should mention that I do not think I am short on resources. I have two 500 GB SSD drives and the following memory and processor specs.
First of all, please make sure your have enabled the Hardware acceleration for emulator, https://learn.microsoft.com/en-us/xamarin/android/get-started/installation/android-emulator/hardware-acceleration?pivots=windows
If you enabled it, please delete this emulator, create a emulator like this screenshot.
https://imgur.com/a/ZyBakKc
I resolved this issue by going to Tools in Visual Studio. Tools > Android > Android Device Manager > select and edit property (hw.gpu.mode) of emulator to mesa
I have a Windows 10 64-bit PC (fresh install, not an upgrade).
When I run the setup file (web or offline alike) in order to install Visual Studio (2013 or 2015, Community edition), all I get is a small black rectangle on the screen (which I later found out that this is actually the title of the setup popup window), without the actual window of the installation.
I have tried it also after a reboot, and with various "versions" of the installation files (web, iso, standalone), but it's always the same situation.
What can I do about it? VS is my main development tool and I really need it on this computer as soon as possible.
Similar problem here. Program install ok but display blank screen after launched.
Problem solved when I changed my Nvidia graphics's global 3D setting to integrated graphics.
Right click desktop
Select Nvidia Control Panel
Select Manage 3D Settings
Under preferred graphics processor, select integrated graphics.
Apply.
If you are using a laptop with an external monitor, try unplugging it and using your primary monitor to launch. This worked for me. Laptops often have dual graphics cards and I believe we're hitting some issue with the way the Installer for VS was written (likely WPF)
Once I launced it and started the installation, I could safely plug my monitor in and it kept working properly.
I'm using an AMD GPU, It was a blank white screen but when I hover the mouse over it, I can see the text events
By the way
I went to my AMD Radeon Settings and saw that vs_installershell.exe and vs_setup_bootstrapper.exe were added automatically to the Switchable Graphics list
they were with Not Assigned Option which usually is like High Performace Option
means It would run it with my ATI GPU.
So I clicked on them
Selected Power Saving Option (to work with my Intel GPU)
Which worked and I can see the window of visual studio installer back
after restarting visual studio installer for sure.
whether is your graphics card, just turn on power saving for it.
Had the same issue. Since this topic is not accept any answare, there is one from https://developercommunity.visualstudio.com/content/problem/150888/visual-studio-installer-shows-blank-screen.html
Try to open installer as Admin.
You will probably have blank screen. Do not close it!
Open installer once more.
Hope it help other people with same issue.
the same thing happened to me, i didn't do anything i just waited for it and it started showing it's status, i suggest you close other running programs to avoid conflicts and performance hindering, and try it again.
This seems like a very shoddy issue. I've run into this problem too, and I tested all solutions that I came across online. These all work:
Running the installer as administrator, which is a blank screen. Leave it open and run a second instance of the installer, which will not be blank (doesn't need to be run as administrator the second time.
Changing screen settings so that the laptop screen is not being used.
Downloading the AMD Settings application, and setting vs_installershell.exe to run on powersaving mode. Restart the installer after saving the settings.
Use a default graphics driver instead of the AMD one.
I had the the same problem in my laptop. The temporary solution is: start the installer only without the battery, if installer starts you can connect the cable, it works fine.
I had to run integrated graphics rather than my Nvdia. That solved it for me.
Remember to change it back when programming in OpenGL and DirectX otherwise you may get a list of messages staying that nothing works.
I had the the same problem in my laptop. The work around is, in device management, remove the amd graphics or start the installer only with battery.
I have a strange issue whit my emulate touch functionality on Google Chrome version 49.0.2623.110 m.
I'm using laptop + monitor (both Dell) and running Windows 8.
The issue is that while Chrome is on my secondary monitor and touch screen emulation is enabled I cannot see a touch screen pointer (black circle) nor any kind of pointer, but when I move my Chrome to my main laptop display it would show. I tried disabling laptop display while using external monitor and it is the same, I cannot see the pointer. This was not a problem with previous Chrome version.
Did anyone had similar issues with this version?
Thank you
EDIT:
I've change the laptop, updated to win10 and updated Chrome to 50.0.2661.87 m version and I still have the same issue (colleague of mine has the same problem as well).
A colleague of mine "solved" the problem by enabling Windows' Mouse pointer trails at minimum length. I find it too annoying to work with the setting enable, but it does work if you really need it.
Mouse settings
They did some changes in recent version of Dev Tools and some options are now gone. Ensure you have "Mobile" or "Desktop with touch" selected, as you can see on the screenshot.
This issue is driving me crazy. I'm on a corporately controlled network but have local administrator rights. This issue is happening with all versions of Visual Studio installer where you initiate the install, then you see the initial splash screen and then that vanishes and it looks like nothing is there. But if you click and drag that area you can see the window borders during the drag. Some portions of the invisible window even respond to mouse clicks. There's even a task bar indication that is blank when you hover over it. I can't even update the current 2013 installation to SP5 because even that window behaves the same way.
However, it just totally hangs the install and since I can't see the install options I don't know if there's a failure or it's just waiting on me to do something.
I've seen several posts about this outside of here but all of them lead to a dead-end.
I have installed Studio on this machine before - actually all versions since 2005 and never have seen this issue until it started about 2 months ago. I did updates galore and all that. Updated my video drivers, blah, blah, blah. I've even tried remoting into this this box and seeing if that would alter the display enough to see what is going on...all to no avail.
The box is beefy (i5, 16GB, 500GB SSD...triple display, etc...) so it more than meets the requirements.
When I try to install any version of Visual Studio, the install window briefly appears and then disappears. However, it is still there, just 100% transparent. Has anyone else seen this before?
I was able to finally find an answer to the invisible install dialog question, it is however not an adequate solution, but an answer. I have to run only one monitor then the install dialog is visible and things proceed normally.
My solution was to disable the graphics card I have on my computer and run on onboard graphics card. It seems that the issue is with the graphics, so forcing the system to use the "regular" graphics card did the trick.
I have to use /Full /Passive from the command line to install on a build server. I would prefer less flashy installer for a more robust one. I am sure its a combination of the graphics card etc. But other installers work.