Android Emulator is not working after update - android

Recently I updated my Android SDK and emulator. After that I'm not able to run the 'Hello world' program. While loading the emulator I am getting warnings and error like this.
OpenGL backend 'angle' without OpenGL ES 1.x library detected. Using GLESv2 only.
emulator: WARNING: encryption is off
TextureDraw: Could not create/link program: Failed to create D3D shaders.
Hax is enabled
Hax ram_size 0x40000000
HAX is working and emulator runs in fast virt mode.
audio: Failed to create voice `goldfish_audio'
qemu-system-i386.exe: warning: opening audio output failed
audio: Failed to create voice `goldfish_audio_in'
qemu-system-i386.exe: warning: opening audio input failed
audio: Failed to create voice `dac'
audio: Failed to create voice `adc'
draw: no program
draw: no program
.
.
.
ANGLE: egl::`anonymous-namespace'::CreateDisplayFromAttribs: make D3D display
ANGLE: D3D9: rx::Renderer9::generateConfigs
I tried lots of uninstall and update, downgrade of sdk, etc., but nothing is working and I'm not able to get the exact problem.
I have installed 2 SDK platforms:
Android 7.0
Android 4.2
My SDK tools are:

I had the same problem, the solution is to change "the amount of physical RAM" when you create a virtual device android... make 512 MB because your computer can't read a space (1.5 GB ) in RAM.
How to create a virtual device correctly to solve this problem?
First, open Android Studio, then click Tools > Android > AVD Manager.
Second, click Create virtual Device after choose a device (for example : nexus 4) and click Next and Select a system Image, then click Next.
Third, click Show Advanced Settings; scroll until you see "RAM" and change the value to a lower value, for example 512MB.

Related

Android Virtual Device OpenGL ES Failed to Initialize

I have been repeatedly trying to get an Android Virtual Device working with Hardware Acceleration on my laptop with a GTX 1650 Ti. The Android Virtual Device works with Swiftshaeder (running with -gpu swiftshader_indirect) with huge lag and running very slowly, but whenever I run it with the gpu, it gives me an error that OpenGLES failed to inialize. My Graphics Card should support OpenGLES, but I can not get it working.
The Error Message:
init: Could not find wglGetExtensionsString! arbFound 0 listarbNull/empty 1 0 extFound 0 extNull/empty 1 0 remote 0
OpenGL Core Profile not supported.
getGLES2ExtensionString: Could not find GLES 2.x config!
Failed to obtain GLES 2.x extensions string!
Could not initialize emulated framebuffer
Failed to open /qemu.conf, err: 2
HAX is working and emulator runs in fast virt mode.
emulator: ERROR: OpenGLES emulation failed to initialize. Please consider the following troubleshooting steps:
1. Make sure your GPU drivers are up to date.
2. Erase and re-download the emulator ($ANDROID_SDK_ROOT/emulator).
3. Try software rendering: Go to Extended Controls > Settings > Advanced tab and change "OpenGL ES renderer (requires restart)" to "Swiftshader".
Or, run emulator from command line with "-gpu swiftshader_indirect". 4. Please file an issue to https://issuetracker.google.com/issues?q=componentid:192727 and provide your complete CPU/GPU info plus OS and display setup.
crashhandler_die: fatal: OpenGLES emulation failed to initialize. Please consider the following troubleshooting steps:
1. Make sure your GPU drivers are up to date.
2. Erase and re-download the emulator ($ANDROID_SDK_ROOT/emulator).
3. Try software rendering: Go to Extended Controls > Settings > Advanced tab and change "OpenGL ES renderer (requires restart)" to "Swiftshader".
Or, run emulator from command line with "-gpu swiftshader_indirect". 4. Please file an issue to https://issuetracker.google.com/issues?q=componentid:192727 and provide your complete CPU/GPU info plus OS and display setup.
Note: I know similar questions have been asked, but every solution is saying use Software Encoding. That is not what I am looking for, as Hardware Encoding should work. Software Encoding has terrible performance, and with a dedicated Graphics Card, there should be no issue for hardware encoding, especially with one as modern as the GTX 1650 Ti.

What my causes junk keyboard input in Android Studio, after running Flutter project

I'm trying to run the Flutter examples provided with flutter in Android Studio (linux).
I seem to be getting junk when I type text into the keyboard (at least in the ('Pixel 2 API 29' emulator).
I don't think there's anything wrong with my settings (attached, below).
The is what I get if I type 'abcdef' from the host's keyboard. Any idea how to fix?
Other symptoms:
The problem appears after running some Flutter project (e.g. ones from the Flutter sample library -- not very interesting). It doesn't seem to matter which project.
After running (and debugging) a Flutter app, the keyboard input permanently borked both for the app I am debugging, and also within Android in general, until the VM is rebooted.
UPDATE: Output of the Event Log window:
9/14/19 7:42 PM Emulator:
statvfs('/home/me/.android/avd/Pixel_2_API_29.avd/snapshots/default_boot/ram.img')
failed: No such file or directory
7:42 PM Emulator: Xlib: extension "NV-GLX" missing on display ":0".
8:42 PM Emulator: Trying to erase a non-existent color buffer with
handle 0
8:52 PM Emulator: Trying to erase a non-existent color buffer with
handle 0
9/16/19 10:24 AM Emulator: Trying to erase a non-existent color buffer
with handle 0
10:26 AM Emulator: Trying to erase a non-existent color buffer with
handle 0
10:28 AM Emulator: Process finished with exit code 0
I saw it today too. I have not points to answer you, but i found the solution: Open your Android Studio and update the emulator (mine ask to update)

Emulator: Process finished with exit code -1073741676 (0xC0000094)

When trying to launch Emulator from AVD Manager. Getting this error:
Emulator: Process finished with exit code -1073741676 (0xC0000094)
Already tried:
Added fresh emulator
Device Wipe out
Cold Start
Increase / Decrease RAM allowcation
Change Resolution (Low and High)
Sometimes it may be an issue with the Visual C++ runtime. If it is not installed please install Visual C++ and check.
Please find the link below to download latest Visual C++.
https://support.microsoft.com/en-in/help/2977003/the-latest-supported-visual-c-downloads

New AVD takes a picture saves to clipboard

When I create a new Android Virtual Device and run it for the first time in Eclipse, I have noticed that it activates my webcam and takes a picture. This picture is saved to my clipboard.
But I was wondering if this is normal and happens to anyone?
INFO:
Android Development Toolkit Version: 16.0.1.v201112150204-238534
Android 4.0.3 API level 15
Running on Windows XP
EDIT: Tracked it down to what I think is the SDL_app process.
Also when I disabled my clipboard and started it up I got this printed to the terminal:
[2012-01-26 05:12:12 - Emulator] emulator: ERROR: camera_device_start_capturing: Device 'AndroidEmulatorVC0' is unable to save frame to the clipboard: 0

Audio not working in the android emulator (win7)

When starting my emulator from Eclipse or from the command line (Win7x32), I see no emulator window popup and the process hangs.
From the command-line, with -verbose, I see logs until the two lines:
emulator: using 'winaudio' audio input backend
emulator: using 'winaudio' audio output backend
... and then nothing.
When I start from the command line with -verbose and -noaudio options, the emulator starts up.
I can modify the Eclipse avd startup settings to have -noaudio, but I'd like to find a way to get audio working.
The commands emulator -help-audio-in and emulator -help-audio-out show winaudio and winaudio & sdl, available, respectively.
Does anyone have pointers as to how to get audio working with my emulator?
Edit
After this happened again, I discovered it was a faulty audio driver - basically a Windows audio driver issue. Reinstalling the driver (and removing any usb-attached audio hardware like webcams, etc.) allowed the emulator to start w/o hanging # winaudio statements.
As above, after this happened again, I discovered it was a faulty audio driver - basically a Windows audio driver issue.
Reinstalling the driver (and removing any usb-attached audio hardware like webcams, etc.) allowed the emulator to start w/o hanging # winaudio statements.

Categories

Resources