So, I have this issue with my emulators on Android Studio, sometimes they doesn't render the font
My emulators sometimes doesn't render the font, this happens with the keyboard, app names but it does not happen with the content of these.
I haven't found a solution other than delete the emulator and create a new one. I've tried different APIs and again it happens, it shows them well the first launches and then nothing.
Does anyone know why it happens or any way to repair them?
image1, image2, image3
This can sometimes be caused by the renderer / GPU having some sort of incompatibility.
Try changing your OpenGL ES renderer in the emulator settings. I've found "Desktop native OpenGL" to resolve the issue before.
Related
I have an issue all of a sudden where I am getting a weird black flickering at the bottom of the screen (as shown in the video below). I had no problem earlier also this happened after I removed android emulator and rechecked it (Reinstalled it ) under the setting “Tools” ->” SDK Manager” -> “SDK Tools” tab.
Video Link - https://vimeo.com/manage/videos/739329236
Computer Specs -
I7 - 10750h,
Nvidia 1650 Ti - 4GB,
16 GB Ram,
1 TB SSD (443 GB free)
Also, I have noticed the screen goes most of the part blank when I am not touching the screen.
I had the same problem recently after create a emulator with API level 33,
Then I've tried to used API level 31 and emulator works normally.
I tried giving more memory to my emulator and the issue disappeared.
https://i.stack.imgur.com/QHSIK.png
It seems there is a problem with the x86_64 images. If Software GLESS is turned on then the flicker goes away but the graphics are little laggy.
x86 images works well smooth but out-dated.
I just installed Android Studio first time for a while and noticed the flickering problem right away. I have NVIDIA GPU which most likely contributes into this problem. In the AVD options inside the Android Studio device manager I tried switching the Graphics setting from automatic to "Software GLES 2.0" and it fixed the flickering. No way using software acceleration is optimal in any way but it could be a workaround until the root cause is fixed.
EDIT: found the issue posted about this behavior confirming it is a GPU driver related issue https://issuetracker.google.com/issues/246917660
I had a same issue in my new laptop. I have fixed it by changing one parameter in the emulator's config file.
Go to C:\Users\USER_NAME.android\avd\Pixel_5_API_31.avd
Edit the config.ini file.
Find the "hw.gpu.mode = auto" and change it to the "hw.gpu.mode = guest" and save the changes.
Restart the emulator.
Same here. After one of the latest Emulator (in SDK tools) updates virtual device with API level 31 or above show same issues. Devices with API level 30 or below work fine.
Tried to completely clean and re-install Studio and Video drivers. No effect.
So since it started right after update i believe it's Emulator component issue.
I just switched to a Pixel 5 with API 33 and it seems to have resolved my flickering problem..
Since I upgraded my Android Studio installation to Bumblebee, the emulator has become unusable. It either crashes during startup or gets itself stuck so that the UI is unresponsive and the debugger either cannot install or cannot launch an app. The way in which it fails varies from time to time for no reason that I can understand. although different virtual devices seem to behave differently. I tried deleting my old virtual devices and creating new ones, but that didn't help.
I can't debug my code on a real phone because of a different problem, see my recent answer to Source code does not match the bytecode for Android's View.java.
When it crashes I send a crash report to Google, but they don't seem to be fixing it. The problems started with the first official Bumblebee release 2021.1.1, which seemed to have a complete new version of the emulator, and I'm now on the latest stable version 2021.1.1 Patch 2.
My environment is a Dell Precision M4800 with 16GB of RAM and an 8-core Intel processor, using an external 4K monitor and an external full-size keyboard, running Linux openSUSE Leap 15.3 with all recommended patches installed.
Does anyone have any suggestion short of throwing away my entire Android Studio installation and reverting back to Arctic Fox? Has anyone else seen similar problems?
Tintin's answer didn't work for me: Device Frame wasn't enabled anyway because I had noticed that it had caused problems before.
However the following sequence rather surprisingly, at least to me, did fix the problem.
First make sure that the toolbar is visible at the top of the emulator window: if it isn't, click on the gear settings icon at the top right of the emulator window and enable Show Toolbar.
Start up an emulated virtual device, and before it crashes click on the three dots at the right hand end of the toolbar: this will bring up the extended controls window.
Choose Settings from the list at the left of the extended controls list.
Set the OpenGL ES renderer to Desktop native OpenGL, and the OpenGL ES API to Compatibility (OpenGL ES 1.1/2.0).
Close the extended controls window and then close the Android Emulator window.
Check if there are any zombie emulator or qemu processes still running. If there are, kill them: you'll need kill -9 on Linux.
Try to cold boot an emulated virtual device: it will probably crash before it even gets started up properly.
Close the Android Emulator window and repeat step 6
Try to cold boot an emulated virtual device again, but click on the three dots quickly before it crashes.
When the extended controls list comes up, choose Settings from the list at the left.
Set the OpenGL ES renderer back to SwiftShader, and the OpenGL ES API back to Renderer maximum (up to OpenGL ES 3.1).
Repeat steps 5 and 6.
Now try to boot up an emulated virtual device again. It should work: at least it does for me.
If it doesn't work on your configuration, try all possible combinations of the OpenGL ES settings: you may find one that works.
Logically, changing the OpenGL ES settings and then changing them back again shouldn't do anything, but it does. My guess is that perhaps some needed bit of initialisation for the OpenGL isn't being done by the installer, but it gets done when you change the configuration.
I also faced this problem in both updates in 2021.1.1 it was not working at all. Updated to patch 2 again faced problems turned off Enabled Device Frame it is working OK now
I've Installed the newest version of Android studio, including the newest version of HAXM, ndk, sdk and whatever other related dependencies it installs. Intel Virtualization bios setting thingy I can't remember the name of is enabled and I have no trouble in virtual box and such.
I created an empty activity and tried testing it on the phone, works perfectly. Then I tried it on the emulator and there is a problem when it is hardware accelerated. It just opens a white window. The android studio displays 0 errors and thinks it ran the app properly. The graphics card I have is a gtx 1060 6gb. When it is software accelerated it works but is so slow I would rather use a chisel on a rock to draw the application usage.
So if someone knows a fix it would be nice.
Thanks
Well I have discovered that in order to solve the issue you have to go to the sidebar menu click More>Settings>OpenGL ES Renderer and(in my case) set it to Angle(D3D11) or Angle(D3D9) or Swiftshader. After that you simply restart the emulator and the issue should be gone.
For me Desktop native OpenGL and Autodetect based on host(which probably sets it to the first thing) don't work and leave you with a white screen.
In case someone finds this useful, you can set software acceleration as below and this solved the issue for me on Mac OS. (OP also mentions it works with software acceleration)
Tools > AVD Manager
Select virtual device
Click on Edit (pencil icon for me)
Click "Show Advanced Settings"
Look for Emulated Performance - Graphics
Select "Software" option
Current version of the emulator (27.1.3) doesn't work for me. The emulator just shows a white screen. Even playing with the gpu in the .ini configuration didn't work.
Once I downgraded to 26.1.4 (https://dl.google.com/android/repository/emulator-darwin-4266726.zip) the emulator started working again.
It seems that the Android Emulator is somehow conflicting with the NVidia Web driver on Mac OS. I had the latest NVidia Web driver (378.05.05.25f04) installed and I was having this same problem - the white screen whenever I used Desktop Native rendering (or left it at the automatic default which selects that as well).
I tried the Swift Shader as well, it works but the performance is abysmal!
On a hunch, I switched back to the OS X Default Graphic Driver from the Nvidia Pref Pane in Apple menu settings, and the Desktop Native driver is now working great after the computer restart!
The same problem can happen to the lightning fast Microsoft Android Emulators utilizing Hyper-V that work on both Intel and AMD CPU based PCs. The solution is in the same line as the accepted answer. For those who use Microsoft Android Emulators and land here by searching "android emulator white screen", here is the screenshot showing how to solve the problem by changing the default hw.gpu.mode from the default "auto" to "mesa":
So sorry
Check your onCreate method in your MainActivity.java, it should have setContextView(R.layout.activity_main)
I wanted to develop my own watchface for my Gear S2. I found some good documentation on downloading and using the Tizen IDE. All is well, but I'm finding the tweak css/html5-run/upload-switch faces-view-wash-rinse-repeat to be very tedious and time-consuming.
I know I can point my browser (Chrome) to my development workspace and load the index.html up and I surmise that I could tweak what I have, which came from the template to work in the browser if I made the sizes in the css static vs dynamic (absolute vs percentages). But is there a better way? Scouring the Internets Googles have yielded nothing too helpful yet.
moderators: this might be OT for this particular SO. If that's the case, I apologize. A nudge in the right direction would be greatly appreciated, if so.
So, I was able to make a little progress on this myself. I am using Chrome in developer mode, which almost works perfectly when using the developer device emulator. To toggle the device emulator, open developer mode (windows: ctrl+shift+I, OS X: cmd+option+i) and when the tool window opens up, look for the little device button next to the element button in the upper left corner of the developer tools window. When the device emulator open, switch the resolution to 320x320 (top of the window next to "screen").
Now, open your index.html file for your project in Chrome, and you can at least muck around with your css styling.
Now to get around the whole issue of reloading your clock with the default clock in the Java emulator for Tizen, I was able to get my changes to automatically assert when running the new code. The way I did it, though I'm not sure if all of these steps were necessary was:
In the emulated watch:
1. set the screen timeout to 15 mins.
2. set the watch face to your development watch face
In the IDE:
1. when ready, use the button for smart launch (it's the blue button just to the left of the bug button in the tizen web IDE). This is in the Tizen SDK version 2.3.1 build 20150721-1440.
At the time of running your code -- making sure both your emulated watch is running too:
1. In the IDE, click the smart launch button
2. Click over to your emulated watch and make sure it's in focus.
It should update the watch face with your latest changes in realtime. This worked for me, so YMMV, but at least I didn't have to reload the watch face after asserting the latest version.
After migrate Xamarin iOS project to Unified API, the app shows black screen only.
Apparently all resources are not loaded at all.
Not only all images including icon, splash are not loaded, but also all XIBs are not loaded.
Now only default black window screen is shown.
Any advice to solve this?
In some cases XI 8.6.0 new msbuild-based build system can forget to copy some files into the app bundle.
This is fixed in the service release (8.6.1) which is in the alpha channel (right now). You might want to try it to see if this is the issue (if not then please file a bug report so it can be investigated).