I've been doing development with Flutter. I was using a real hardware but wanted to use an emulator. I set it up but there's this issue.
I usually put my apps in virtual desktops and I switch between them with Ctrl+Meta+[arrow keys]. Each of them have a special purpose, usually desktop 1 is for browsing, desktop 2 is for development and desktop 4 is extra (for testing UI apps and emulator in this case).
However, after I launch Android emulator and switch to a different desktop, it results in the issue seen below:
The red area you see stays unresponsive for other apps such as browser, VSCode etc. (i.e. does not respond to clicks). That area is where the emulator is on Desktop 4. And it also keeps showing multitouch tool.
It's a bit annoying so I wanted to ask if anyone got this issue and if they have any solutions.
Thanks in advance.
Environment
Kubuntu 20.04
AMD Radeon R7 240/340
Solution 1
I have, somehow in a weird way, found a workaround for this issue.
After having this issue, go to the emulator window and press the magnifying glass with a plus button icon twice.
After that, it will drop that weird multitouch state and it won't bother you even as you switch desktop.
Rebooting computer will result in the same bug, however, you have to do it again.
Solution 2
Another method that works is to simply resize the window. If you have a device frame on your emulator, you can simply hold down the Meta key and hold right click and resize your window.
Solution 3
You can also maximize the window. If you have device frame around emulator window, you can press ALT+F3, which opens up window options menu, then click "Maximize". This will get rid of it.
Related
I'm trying to run a sample Xamarin app and I think my Android emulator is acting up. I've tried enabling Hyper-V, increasing the RAM, telling it to use the host GPU, launching the virtual device from the command line instead of the GUI, and double checking that I have the correct version of the build tools for the version of Android I'm attempting to run.
As a test I've just run the emulator by itself without an app and have discovered that it still shows a white screen even when it is apparently running, somehow. The first image is what I get when I press the Screenshot button. The second image is what I actually see on my desktop. It's been like this for over 10 minutes.
Any advice? I've been Googling like crazy and can't seem to work this out.
Have you tried simply changing the renderer?
Go on the sidebar menu, click the 3 dots>Settings>Advanced and try changing the OpenGL ES Renderer
After installing androidx86 on VirtualBox at boot android boot in CLI and after a couple of seconds I got a black screen, with a blinking underscore at the top-left of the screen, its keep blinking without any change, it wont boot the gui.
I have tried different installations following various guides on internet, but I got ever the same problem, I have also tried with Alt+f7 key combo and putting nomodoeset in boot option in grub, but nothing.
In all tutorial I have found online they always start the gui without any problem. But I got always the black screen after 2 seconds of cli.
Found a fix posted by Val at superuser.com:
I managed to solved my problem :
I just changed the display option Graphics Controller to VBoxVGA and enabled 3D animation.
Right click on the virtual machine you are looking to modify, and hit Settings
Navigate to Display, then make sure you are on the Screen tab
Set Monitor Count to 2 or more
Set the Graphics Controller to VBoxVGA
Increase the Video Memory to 128MB (choose the maximum amount available to you)
I encounter really strange behavior with android emulator. First of all, I am using extended monitor for development. So i code on my laptop and check the app on emulator on second screen. For some reason, I can't see emulator again after disconnect vga cable but I can see emulator is running on taskbar. Somehow, I can't bring emulator out on desktop screen or move to another screen, it just hidden and I don't know how to bring it out. It already happens to me two or three times. Can somebody help me out? What can I do to solve it?
Below is screenshots of my desktop with emulator running.
alt+tab
avd manager
It happens again when I change to another monitor for extended screen. I try what #Zoe suggested press ALT+SPACE to move but it doesn't work because move is grey out.
So my solution, I created two emulators, for two different monitors.
I am not sure why I got downvoted though.
http://tinypic.com/view.php?pic=25h1i7q&s=8#.VcISK26qpBd
Apparently since I don't have enough rep points, I cannot upload an image, so you can find the image in the link above.
Whenever I try running the virtual emulator, the emulator will start and work properly, but there is no cross/minimize button available, which not only makes it hard to quit the application, but also makes it impossible to move the window around.
I have tried disabling host GPU but that hasn't helped either.
Any ideas on how to get this working would be greatly appreciated.
Proabably its hidden up there by your titlebar of the curruntly active window ,
One thing you can try is make it smaller by adjusting the avd size from avd manager in android studio. This happens normally to me in ubuntu
I am trying to write an application with Mono for Android. In an attempt to do this, I'm using the default template in monodevelop. I can successfully compile and run the application. When I run the application, it looks similar to the one shown here: http://docs.xamarin.com/android/getting_started/hello_world
There are two oddities in my version though:
The button is red
I can't seem to actually click the button. When I use my computers mouse, it acts like it won't click the button. This is not limited to the application either. If I try to click the home or search button in the emulator itself, I noticed that nothing happens either. Its like the emulator is not responding to my mouse.
As someone new to working with Android, can someone please tell me what I'm doing wrong? I'm using MAC OS X with Lion installed. I'm assuming that I have the SDK and Java SDK installed properly considering the app compiles and when I press "play" I can load the app in the emulator. I just can't figure out why I can't actually click the button. So bizarre.
Any ideas?
The title of this question is pretty misleading, since you're saying that the emulator is not very responsive even outside the Mono for Android application. The problem here is with the emulator itself. The one thing I would recommend trying with respect to Mono for Android is to try starting the application without debugging, as debugging will add extra overhead to running the app.
The Android emulator is notoriously slow, since it is fully emulating the ARM instruction set in software. That said, there are certain things you can do in order to squeeze some more speed out of it. One thing that I've seen make a big difference is to decrease the screen size of the emulator image. Setting this to a small screen size (such as QVGA) can make a big difference. You can manage these settings through Android's AVD Manager.