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.
Related
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.
Really weird issue but when I try to click once it doesn't register on the emulator but then I click again and the click registers. This is using AVD. Every other click seems to trigger in the proper place. This has nothing to do with my app just base image.
Take a look at this:
https://www.youtube.com/watch?v=axvxtGj4HPo&feature=youtu.be
and notice the first click doesn't register.
I notice the age on this thread, so not sure if you have already figured this out. I ran into something similar like this today in which no clicks were being registered at all. This issue still persisted even after closing and reopening the simulator. One thing I did notice is that the power button still worked.
I ended up fixing this by:
Clicking and holding the Power Hard Key
Restarting the device OS by clicking the Restart
After the OS Reboots, everything seems to work again.
Note: the Hard Key for power is the power button next to the volume controls on the right.
In my case it usually happens when the size on disk is very high (see in AVD Manager) and the solution in my case is to make a Wipe Data
Update #1 (Because the solution from above not always works)
Another thing I found is that when you want to swipe up from the Google bar does not open the apps menu. Then I open first the Messages app or Chrome and close again. From there the Swipe up works again.
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.
Like the title says, whenever I make any changes in the code I don't see the changes in the AVD. Is there a way to do this without closing the AVD and starting it again?
I'm using Eclipse.
Thanks!
I have noticed this behavior at times as well. In the ADB log it will state something like the activity is already started and has been brought to the front even though it was already on the screen. Not sure what the cause of this behavior is and it seems to happen randomly. I have dealt with this in the past by force stopping the app in the AVD or just uninstalling it. Sometimes pressing the home button on the AVD and then running the APP from eclipse seems to fix this.
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.