When I start a Virtual device older than 4.2.2 version ... the display it is something like the picture....
What I'm doing wrong?
Try rotating with the Keyboard Commands for the emulator:
http://developer.android.com/tools/help/emulator.html#KeyMapping
Or
Check How do I rotate the Android emulator display?
UPDATE:
I've investigated a bit. It's probably a ROM / system library bug, not an emulator bug, since it happens on real phones too.
UPDATE2:
Why don't you post it as an Android issue in their site https://code.google.com/p/android/issues/list?
Related
I am trying to start a emulator to develop a mobile app, due to the huge size of the emulator the icons do not response on clicks.
Attached is the emulator started from AVD. I have tried to edit the device settings, disable the frame around the screen. Nothing seems to work.
Emulator Specs: Pixel 3a API 30, Resolution-1080x2220
I have faced the same issue, in my case restarting the emulator did work.
Or create your own custom emulator
Go to AVD Manager and try Cold boot Now and if that doesn't work then try Wipe Data.
Also, Let us know how the issue got fixed.
Cold boot your emulator in order to refresh.
I have a problem with my android emulator. It only shows a fraction of the screen.
Screenshot:
I have Android Studio version 3.0.
I tried a lot of things. I could fix the error when I use the emulator with Software emulated graphics but it is really slow.
know someone the solution?
thank you.
Make sure you have configured hardware acceleration correctly.
Disable the Device Frame by edit action.
Start the emulator and Go to Extended Control
Go to Settings and change OpenGLES render to Desktop native OpenGL
Restart Emulator and Resize the Emulator Window.
I just installed Android Studio and was trying to get a preview of my application but whenever i start the AVD Emulator on whatever devices or API it crashes, but it only do crash when I swipe the window of the AVD to my second monitor.
my computer configuration : i7-6700k, 16Gb RAM and a GTX 1060
the AVD configuration :
Anyone had the same problem in the past or have a solution ? feel free to ask me for more info in case I didn't explained enough
I had the same problem, and I found a solution that you can have the hardware acceleration still activated and move the AVD between monitors.
Here's how I did it:
Start the AVD.
Go to Extended Controls (the last button on the control strip, with the 3 dots) > Settings > Advanced
Change the "OpenGL ES renderer" to "ANGLE (D3D11)"
Restart the AVD.
And there you go.
I had this same problem and solved it by setting the AVD Graphics performance from 'automatic' or 'hardware' to 'software' graphics acceleration. You can see the setting here: Android AVD graphics acceleration setting picture
You can read more about that setting here: Configure Hardware Acceleration for the Android Emulator
I believe this has something to do with Nvidia drivers and the android emulator, as I only got the problem on the display using a Nvidia GPU and not the display using the Intel integrated one... which is disappointing not to be able to take advantage of the better GPU for graphics acceleration.
Thanks to the hint provided by Serjux's answer, I resolved my similar problem - Android emulators freeze immediately when moved from one monitor to another. They worked fine without this problem until I upgraded my PC from Intel i5-3570K to AMD Ryzen 7 2700 while the video card GeForce GTX 1050 remained. I use Hyper-V versions of Android emulators. For hw.gpu.mode, I have tried auto, host, angle, mesa, and found only mesa works fine:
In my case moving the AVD window very slowly, does the trick.
Serjux's answer works but apparently at the cost of performance. I should mention that moving it to my primary monitor at speed doesn't cause a crash, but moving it quickly to the second one does.
For me what worked was changing the
gpu.mode from config.ini located in users/youruser/.android/avd/emulator-name/config.ini to gpu.mode=host
The problem appears also with a i7-6700k, GTX 1080 and miscellaneous AVDs in my environment.
It works without a problem when Nvidia Surround is enabled.
But this might not be a solution which everyone prefers.
I had the same problem, but the 2018's answer does not helped to me.
I found another solution and share here, maybe it can help other peoples.
I just changed the GPU Mode to "Software". In my case it was not possible from the AVD settings, so I did it manually.
In my case the phone is Pixel 4 so the config.ini file is located here: C:\Users\myuser.android\avd\Pixel_4_API_30.avd\config.ini
I replaced hw.gpu.mode = auto by hw.gpu.mode = software
I can't change the graphics to software as I'm sure this is the fix for my AVD not launching.
The option is greyed out (see screenshot). Has anyone has experience with this? I couldn't find anyone who had the same issue.
I'm running the latest version of Android Studio on Ubuntu 17.04.
Actually, this problem seems to be limited to devices with Play Store available, so Nexus 5X and Nexus 5 images will be forced to use Automatic Graphics, but all other devices allow you to choose either Automatic, Hardware or Software graphics.
edit: I've just tested this today and it seems to no longer be the case. At least on MacOS with Android Studio 3.3.2, I can now make a Nexus 5X image with Play Store and Hardware Graphics. I'll do more testing at home later, on Windows and Linux to see if it's related to OS or graphics drivers.
I also think it's related to whether the Playstore is contained or not, but I cannot explain why.
Dielson Sales already gave the answer which worked for me - unfortunately only in a comment to this answer. I just thought it's worth to make a "real" answer out of it:
Edit the config.ini file of the AVD. Under Linux it's located under /home/<user>/.android/avd/<AVD-name>/config.ini
(in my case <AVD-name> is Nexus_5X_API_29.avd).
In a text editor change the lines
hw.gpu.enabled=no
hw.gpu.mode=auto
either to
hw.gpu.enabled=no
hw.gpu.mode=off
or to
hw.gpu.enabled=yes
hw.gpu.mode=host
This setting remains even if opened in the Android Virtual Device Manager of Android Studio. It's just not editable there.
I also tried this, which I found in another AVD:
hw.gpu.enabled=yes
hw.gpu.mode=software
But this is then changed to "no" / "off" by the Android Virtual Device Manager.
I didn't look any further so far. hw.gpu.mode=off worked for me. Otherwise my whole Kubuntu hangs (using the Nouveau driver, not the NVidia driver)
Seems like the problem was with the choosen VM. If I choose a Nexus 4, it runs just fine.
I am little late on this thread but following are my findings and solution. I am using Ubunut 18.04 and faced the same issue. The solution is to edit AVD and under Emulated Performance, change the grpahics to Software. The problem was that this option was disabled for me. I was unable to change graphics drop down.
I did some more research and found that while creating AVD if you choose default/existing device definition on first screen, you will not be able to edit graphics drop down.
The solution is to create a "New Hardward Profile" while creating AVD and use your new profile. Now, you will be able to edit "Grahics" drop down.
Hope this helps....
It seems all emulators with Play Store cannot emulated performance. I am using AS 4.0
Open Android Virtual Device Manager Android Studio, change VMHeap to 512, RAM to 4096 MB. Then restart Android Studio.
I think It's just a bug!
Solved the issue by selecting any virtual device had the option enabled and after finishing the installation I just clicked on edit and reselected the device I wanted and the option was still enabled.
Click on edit button from here.
Then change the device to the one you want.
For those who are still searching for solutions on how to make it work with an image containing google play store: install / update your GPU drivers solves the problem. On my Ubuntu 20 this was the issue.
I'm working on mac os - after i upgrade my os my emulator stoped working and one of the solution was to change the graphic settings from hardware to software - since i couldn't - came here ---> turns out Android Emulator HAXM on macOS High Sierra is left out from security reasons
follow this link : https://developer.android.com/studio/known-issues#deploy
The story is that I developed an Android program with Android 4.4.2. But some problems was found after installing the program to a device with Android 5.1.1. So I tried to download Android 5.1.1 for my SDK to debug the problem. Then the AVD I kept on using becomes like a mess no matter I changed to different configuration (see picture 1). My AVD configuration is as picture 2.
Hope someone could help... Thank you so much!
Picture 1
Picture 2
Got a temporary way to solve it and don't know if it is correct.
Set the skin to "no skin".
There is another problem happened now. The control bar of that window shows out of the screen. It makes the window cannot be moved. Anyway, I can continue my development job in this way...