I am running a project in the debug configuration in VS2012 and the IDE intermittently beeps. I ran said project numerous times before and never experienced such a behavior. Is VS trying to draw my attention to something? How can I disable the beeps?
I had the same problem with beeping while debugging code in Visual Studio and it turned out that the root cause was a KVM switch, like this one: http://us.dlink.com/products/connect/4-port-usb-kvm-switch/ actually the source of beeping sound was the switch while pressing F10 or F11 buttons on keyboard connected to the switch. After plugging external devices like mouse and keyboard directly to the PC, the problem disappeared.
Related
I upgraded to Android Studio Bumblebee 2021.1.1 and realized that I cannot fully control the emulator with the touchscreen of my notebook anymore. Press events on the touchscreen (like mouse clicks) are still recognized correctly, but when I swipe nothing happens in the emulator.
Unfortunately, I did not note down the previous version of Android Studio that I had installed before, but with previous Android Studio versions I was always able to fully control the Android emulator via the touchscreen (as if I was actually testing my app on a real mobile phone).
My Google searches did not show any results related to this issue. Does anyone have an idea what the root cause could be and if it is possible to fix it?
Disabling launch in tool window in Settings::Tools::Emulator fixed it for me (requires emulator restart to take effect).
Credits to YuriBlaise on reddit
I am using Visual Studio 2017 on Windows 10 with a wireless keyboard, connected to my Notebook. My keyboard lost the connection to the notebook and I could not reconnect, until a restart.
After that, Visual Studio lost my individually created keyboard shortcuts. Even after a reset of the keyboard settings and re-assigning my shortcuts, it does not work. The keyboard combination is being recognized (shift+alt+o) and is being shown in the settings after closing the configuration window with OK. It appears that even the entry in the main menu is dead.
However, the original shortcut works. Scary, isn't it?
Does anyone have a solution which is not re-installing Visual Studio?
Discovery 1
Found a solution (admin rights required). See: https://developercommunity.visualstudio.com/content/problem/3278/go-to-symbolfiletype-shortcut-dont-work.html
Helps out, sometimes. Maybe some restarts of VS 2017 required.
However, still have problems with the window grid, like others are describing here as well. Visual Studio 2017 seems to be a complete mess.
Discovery 2
Consider this article, too: https://forums.asp.net/t/1103223.aspx?Find+also+find+and+replace+not+working+in+Visual+Studio
Discovery 3
Looks like that the problem had its origin really somewhere else. Someone plugged two cables from one monitor into my docking station. I use a notebook with docking station and two external monitors. One of the external monitors has been connected via DP and the other via DVI. This caused windows to think of one additional monitor in the setup (total count was 4), but with one deactivated.
As Windows 10 still cannot deal properly with multi monitor setups (think of DPI troubles on high res screens, especially when you mix a standard DPI monitor with a notebook that has a DPI screen), I currently have the suspicion, that Visual Studio opened the lost dialog windows on the non-existent screen.
Big oops. But maybe this article helps someone...
In Hololens Emulator with Windows 10 Pro, I can only use keyboard strokes and my mouse is not recognized. How can I turn on mouse input? I did nothing to connect my keyboard, so why is it with a mouse that I have to change something?
One problem that may solve it: make sure when using the emulator that in Package.appxmanifest in Visual Studio the MaxVersionTested line is the correct version. I was looking at an older version which everyone says to use: 10.0.10586.0 which was incorrect. When choosing the device for debugging, the version will be in the name. Currently, the most updated version (that I am using) is 10.0.14342.1018. After that, start debugging and run the emulator and you should have keyboard and mouse input!
I had the same problem, but I'm not sure how I solved it. Here is what I have done:
Installed Update 3 for VS 2015. Tried again without restarting the PC and got the same problem. On the next day I started the HoloLens Emulator directly via Hyper-V Manager. After that I started my project in Visual Studio. The Emulator loaded correctly and now the Human Input and Keyboard and Mouse Input buttons are enabled.
Update: That was definitely not the answer, but I found a working solution here:
http://forums.hololens.com/discussion/952/no-input-from-emulator
Just put off your proxy in IE and the icons will be enabled. I could turn my proxy on again and the controls remained active.
I must be missing something totally obvious, but I can't find a simple way to simply stop an app from running. I'm running it on my HTC One.
I first tried toggling the green run arrow. Didn't work.
I found a "Terminate Application" circle in the lower left of the window. That doesn't seem to do anything when you click it. It seems to be grayed out, non-functional. Screen shot here
http://www.screencast.com/t/VLTOzPQ7
So, I closed the entire project. That worked, but also the entire Android Studio closed instantly. Then reopening Android Studio failed (stack dump). Then reopening again worked, but it took 30 minutes to load my project.
To stop the next time, I turned my phone off, then closed the project. That seems to have worked better, since it took me to the Welcome to Android Studio screen and invited me to open or start a project.
Maybe there's an easier way to stop an app? I see the same question on this forum but no solutions.
The Android Studio controls you are trying to use only work if you are running your app in the emulator. There are a few ways to do this when you are using an actual device or VM (e.g., Genymotion):
Use the UI of the phone to Force Stop the application. This is done in the Settings->Apps menu.
Use Android Studio's terminal window or the host's shell and issue the command:
adb shell am force-stop <package-name>
Open Android Device Monitor (green "Droid" icon), select the process under the Devices tab and click the Stop Process button (stop sign icon). This is basically the GUI way of doing #2.
You need to select the process you want to terminate (ex. com.myname.myapp) then click terminate application.
Since the application is running on your phone, you need to end the application process on the phone. When you do that the application would be shown as terminated on Android Studio.
I updated to Android Studio 1.3 and to Windows 10 before that.
Now the issue I am facing is that my local embedded terminal in android studio has some how stopped responding to any kind of user input.
I have tried:
Restarting the android studio
Restarting the PC
Searching through Google for a solution
My Terminal settings
Has anyone ever faced a similar issue?
Is it a Android Studio problem or a Windows problem?
How to solve it?
You may suggest me to use the external terminal as that too will work fine. But that's not the answer I am looking for as it ruins the whole Android Studio experience.
This is an issue with IntelliJ and Windows 10 console.
Here is a workaround from "IntelliJ Idea Terminal broken with Windows 10" thread:
https://stackoverflow.com/a/31716623/703562
Works for Android Studio too.
The workaround:
Open a command-prompt window.
Right click on the title bar.
Select Properties, then check Set legacy mode box, and confirm the dialog.