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.
Related
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.
My Android emulator crashes whenever I press keys on the pc keyboard or hit the emulator side buttons. the only part that works is the emulator mobile screen. This doesn't happen to just one device but to all emulators I use. This is really annoying cause whenever I press any key on the keyboard while the emulator screen is active it will instantly crash. But keystrokes won't crush it when text input is active on the emulator screen. The operating system I use is ubuntu but Windows fix is also useful.
I need help from someone who has managed to solve this problem before.
I'm pretty sure I got this error before too. Whenever I pressed a button, the emulator would just say "Saving State..." and just closes. The only solution I found to fix this was to delete the emulator and create a new one. It's not the most effective solution, but I couldn't find any other solutions.
I created a brand new emulator today but it is behaving weird today. Here is my setting:
When i start it up, it loads fine. Until it gets to the lock screen. I keep on dragging/swiping from bottom to top to unlock, but it wont! This is the first time I encountered such behaviour. I tried with target Android 6.0 - API Level 23 but was able to unlock. I want to test my app on Google API 23. Please help to figure out the proper setting values.
Happened to me as well.
Another solution in addition to what #TTRansmit suggested is as below:
Close emulator.
Go to AVD manager screen, edit your Emulator and go to Advanced Settings.
Select Cold boot as Boot option located in Emulated Performance section. This way you will be able to restart your emulator and get it unlocked without loosing data.
Power off (via holding power) on the device buttons and wipe data (from Android Virtual Device Manager) worked for me. It was turning off the Device Frame from the edit/Virtual Device Configuration screen of AVD that seemed to cause the problem.
I still did not solve this problem, somewhat. To get thru, what I did was I activated the Camera emulation then relaunched the emulator. On the lock screen, I dragged the Camera icon. The camera would crash and emulator would notify you about it thru a pop up dialog. Once you exit the dialog, it will go back to your homepage UNLOCKED! I know, it was weird but it worked.
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 having a problem in hadling the galaxy tablet emulator whenever I'll run my application and the tablet launcnh then it will not shown any option to open my appliction or goto the menu! It will shows the normal home not having any menu kind of option. I am sending you the screen shot of emulator.Plz help I try a lot to handle this but no clue how to use.....
Android Galaxy Tab Emulator
edit after looking at picture: Wait--first of all. You know you have to drag that slider thing across the screen to get started, right? After that--
I'm not sure about that specific one, but I did notice some general weirdness with the Android emulators. I found a pattern that makes them work--be patient and deliberate.
First restart all your stuff--heck restart your computer to be safe.
Launch eclipse. Start a debug session with the emulator. wait. WAIT... wait... Might be 30 seconds, might be 3 minutes, who knows.
Eventually the emulator should come up and, behold, maybe it works!
If so--here's the trick--never ever shut it down. Leave it up the whole time you are debugging. It will load your app in seconds and run it like a champ. Shut it down and you will have to restart eclipse to get it to work correctly again.
Between the long wait time and that bug I've seen people extremely frustrated (including myself).
If this isn't your problem--sorry, worth a shot.