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.
Related
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 updated Android Studio and now I got some problems. My emulator is pink and is zooming in automatically.
The pink and zooming in effect You experienced is a result of Skin. You can change the skin inside Android Virtual Device Manager, under Edit of Your emulator.
In Android Studio go to,
Tools\Android\AVD Manager\
In AVD Manager window, edit the desired emulator, then as below shot illustrates choose "No Skin".
Android Default Emulator is very slow.
Try Genymotion with android studio plugin.
It is faster than default and easy to use. You just have to create a free Individual account.
Also to increase speed of default emulator increase the heap size
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...
I have used Eclipse to write apps for android multiple times without issue but I am now trying the new Android Studio which I like but here is my problem.
When I run the app I pick my AVD and then tell it to start. The emulator starts loading and then says paired. Then it starts telling me to swipe up and left and right to display and remove cards. Then it says to put hand on screen to dim the screen, ok well I'm on a MacBook Pro so that don't work I swipe to get past that part sometime I can others I can't. Next it says to touch the clock and say some words which also can't do on my Mac, and that is where the emulator stay it never goes to a home screen and it does this no matter what AVD I choose. How can I get the Emulator to just plain open to the home screen like it should.
Thanks for any help.
In your AVD Manager, edit your AVD and make sure your Target is "Android L" and not "Android X.XW". The "W" stands for "wear" and that is causing your issue.
Alright I figured it out. I remember having a similar problem recently when I was taking an android development class for college using eclipse and sure enough that was it.
So here was the solution eclipse gave same problem. for some reason if you have caught exemptions such as hard coding a string etc. the emulator will not run till you ignore these exemptions or fix every last ! mark in your code. Once you do this the emulator will load and run properly.
I also had the same problem with my AVD. The Android Emulator window just used to pop us and the green bars flowed infinitely. After lots of trial and error I arrived at a solution for my problem. the problem was with the Heap size and the RAM size.
Initially the default heap size was 128 MB and RAM was 1563 , I just changed the heap size to 512 MB and reduced the RAM size( high RAM was making my PC run slow) also I enabled hardware acceleration. And Yipeee, it worked.
Well? I've tried increasing the RAM size of the emulator to 1024 MB and there was little improvement on the speed, however, it's still unusable. It has the speed of a turtle.
Anyone got better ideas to make it faster? Is there something I'm not doing correctly?
Check out the android developer documentation regarding 3.0 emulator performance. Scroll down to About Emulator Performance.
Copied tip for convenience:
Tip: To improve the startup time for the emulator, enable snapshots for the AVD when you create it with the SDK and AVD Manager (there's a checkbox in the AVD creator to Enable snapshots). Then, start the AVD from the AVD manager and check Launch from snapshot and Save to snapshot. This way, when you close the emulator, a snapshot of the AVD state is saved and used to quickly relaunch the AVD next time. However, when you choose to save a snapshot, the emulator will be slow to close, so you might want to disable Save to snapshot after you've acquired an initial snapshot (after you close the AVD for the first time).
Seems like everything 3.0 and beyond is slow for me. Everything before that runs very fast in emulator for me. However, I have an Intel integrated graphics card in my laptop. When I turn 3D setting to "Application Settings," I get relatively decent performance from the emulator, at least when it starts up, but then when I try to start any app from the default main app menu (contacts, for example) I get launcher errors. That happens for me on 3.0, 3.1 and 3.2. The one thing I'm suspicious of is that I'm running 64-bit Java SDK. Seem to be a number of posts out there related to 64-bit, but mostly they seem to be point to using 64-bit SDK with 32-bit Eclipse or vice versa, but in my tests, I am not even running Eclipse, haven't even reinstalled the ADT yet, just the Android SDK and created a few emulator instances. Again, prior to 3.0 everything is fast. 3.0 and beyond not good, but A LOT better with graphics settings as I mentioned above. If I could get past the launcher issues, I think I might be all set. Oh, btw also, for 3.0 and beyond, I bumped the memory up to 1024. I've tried increasing the heap for apps to double the default (from 48 to 96) but that doesn't seem to have alleviated my launcher problems.
It is slow. You can try creating a new Emulator with a smaller resolution.
I remember someone at google I/O saying that the HoneyComb emulator will run really really slow due to hardware acceleration turned on.
The PC may use software rendering for OpenGL hence the bad performance. The almost everything you see on the HoneyComb screen is rendered using OpenGL ES.
감사합니다,
Reno