The system configuration I am using is as following:
OS - Windows 7 (64 bit)
RAM - 8GB
Eclipse - Kepler release
Java - 1.6.0_45 (64 bit)
Android SDK - 22.2.1
ADT - 22.2.1.v201309180102-833290
Graphics Card - Intel(R) HD Graphics 400, version - 8.15.10.2696
When I create a new AVD and launch it an error always comes up - 'emulator-arm.exe has stopped working' - with the following details:
Problem signature:
Problem Event Name: APPCRASH
Application Name: emulator-arm.exe
Application Version: 0.0.0.0
Application Timestamp: 5238f89b
Fault Module Name: ig7icd32.dll
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 4f67b1c8
Exception Code: c0000005
Exception Offset: 000256e6
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 16393
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789
I have gone through various other questions addressing this issue as following:
emulator.exe has stop working?
Error Message: emulator-arm.exe has stopped working
emulator-arm.exe has stopped working
I have tried all the following options suggested by them:
Change the RAM value - I have tried with all values ranging from 256 to 1907
Change the target - Have tried the versions from 4.1.2, 4.2.2, 4.2 along with their Google APIs
Change the device - Have tried with various versions of Nexus along with WSVGA
Change the Heap - Have tried with different values of Heap size
Change the resolution - Have tried with various resolutions as per the device
But every time, for every new AVD, as soon as I launch it, I am getting the same error - 'emulator-arm.exe has stopped working' - with exactly the same Problem Signature as shared above.
Could someone point me in the right direction that how can this be resolved?
UPDATE: I invoked Android Debug Monitor to view the LogCat when the device is being launched but there are no log messages getting displayed there.
Any suggestions anyone on how to resolve this?
Try turning off the "Use host GPU" option. Perhaps your computer's GPU is not compatible with the emulator.
This may be due to a compatibility problem with the Intel HD Graphics driver. I would suggest you to update the driver to the latest available version and check.
Related
I installed android studio 2.2 and created emulator nexus 4.
My emulator's details are:
Name: Nexus_4_API_23
CPU/ABI: Google APIs Intel Atom (x86_64)
Path: D:\Programs\Android\.android\avd\Nexus_4_API_23.avd
Target: google_apis [Google APIs] (API level 23)
Skin: nexus_4
SD Card: D:\Programs\Android\.android\avd\Nexus_4_API_23.avd\sdcard.img
hw.dPad: no
runtime.network.speed: full
hw.accelerometer: yes
hw.device.name: Nexus 4
vm.heapSize: 64
skin.dynamic: yes
hw.device.manufacturer: Google
hw.gps: yes
hw.initialOrientation: Portrait
image.androidVersion.api: 23
hw.audioInput: yes
image.sysdir.1: system-images\android-23\google_apis\x86_64\
tag.id: google_apis
showDeviceFrame: yes
hw.camera.back: emulated
hw.mainKeys: no
AvdId: Nexus_4_API_23
hw.camera.front: emulated
hw.lcd.density: 320
avd.ini.displayname: Nexus 4 API 23
hw.gpu.mode: auto
hw.device.hash2: MD5:6930e145748b87e87d3f40cabd140a41
hw.ramSize: 512
hw.trackBall: no
hw.battery: yes
hw.cpu.ncore: 2
hw.sdCard: yes
tag.display: Google APIs
runtime.network.latency: none
hw.keyboard: yes
hw.sensors.proximity: yes
disk.dataPartition.size: 800M
hw.sensors.orientation: yes
avd.ini.encoding: UTF-8
hw.gpu.enabled: yes
When I run simple app it does gradle rebuild and launches it on emulator. And it takes near 2 minutes every time I run it even when emulator is on.
In console, run ends with these messages:
D/OpenGLRenderer: Use EGL_SWAP_BEHAVIOR_PRESERVED: true
I/OpenGLRenderer: Initialized EGL, version 1.4
D/gralloc_ranchu: Emulator without host-side GPU emulation detected.
Haxm is installed and working. Intel virtualization technology is enabled in bios.
What is wrong with my emulator options?
Why is my android studio so slow?
Solved it. In android studio go to Tools>Android>AVD Manager.
Click on edit button of your virtual device
Next find Graphics option and select Hardware - GLES 2.0.
Now running app when emulator is on is very quick.
And in console there is no message: Emulator without host-side GPU emulation detected.
The best android tutorial I've found is at https://www.udacity.com/course/new-android-fundamentals--ud851
There are more free android tutorials at https://www.udacity.com/courses/android
Two suggestions for best performance:
Install Intel HAXM:
https://software.intel.com/en-us/android/articles/intel-hardware-accelerated-execution-manager
Enable Host GPU:
I have recently been attempting to create a GPIO Driver for SBC's using an Intel chipset that run Windows 8.1 and have begun testing it on an actual system. After loading the Driver and updating the Intel chipset I am using, the system appears to hang after loading the BIOS. Unfortunately, this disables my mouse, keyboard, and video, preventing me from entering BIOS or the boot manager.
While it is possible that the chipset update caused the system to become unbootable, it is highly unlikely considering we use that update for our other SBC's running the same chipset.
So my question: Is it possible for a Windows Kernel Mode driver to prevent a system from booting up past BIOS/POST?
I appreciate the help, since, clearly, I am no expert on this topic.
Yes, if your driver is being loaded at boot time it can prevent the booting of the OS and it will end up in BSOD(Blue screen of death) error with related bug check.
According to bugcheck displayed by the OS you can resolve the issues with your driver.
Or sometimes if its not giving any error and just hangs you can use WinDbg to check the bugcheck.
It depends on the error control of the driver service. Boot time drivers can also fail at any point. There is nothing special about the failure happening during boot. Instead, what is relevant under this scenario depends more on the ErrorControl value of the driver service which specifies how to proceed if it fails to load or initialize properly. A value of 3 (critical) would reboot the system to LKGC. Same rules apply to a win32 servic as well..
Here is the situation:
App: C# Platform: X86
DLL: C++ Platform: WIN32
Test1:
(Rugged Tablet PC) with: Windows Embedded 8 Pro
32-bit Operating System, x64-based processor
The app runs fine, but the call to the DLL crash.
Test2:
(Rugged Tablet PC) with: Windows 8 Pro
32-bit Operating System, x86-based processor
All OK! App and call to DLL are fine.
Thank you for helping me to figure what is going on. What is it crashing in Test1?
Thanks.
Windows 8 Embedded is customized to not include all the features that the full version has. This means less stuff running in the background, and less files that may need security updates.
But it also means if you try to use those features you will fail. The exception message should give you information about what was missing. I suggest that you log the exception information, to help you troubleshoot or work around the issue.
The included set of features is fully customizable, so you will need to contact whoever you got the tablet from in order to determine everything that is missing.
The crash details point to ntdll.dll
When I searched on the internet, I see a lot of application problems reported in Windows 20008 Server because of this dll.
My Windows Server 2008 machine is updated with latest packs and updates.
Is this is OS problem or my application which is buggy?
Problem signature:
Problem Event Name: APPCRASH
Application Name: Client.exe
Application Version: 1.3.0.0
Application Timestamp: 51cbcdde
Fault Module Name: ntdll.dll
Fault Module Version: 6.0.6002.18541
Fault Module Timestamp: 4ec3e3d5
Exception Code: c0000005
Exception Offset: 000665c9
OS Version: 6.0.6002.2.2.0.274.10
Locale ID: 1033
Additional Information 1: ccc2
Additional Information 2: 0a07f28ebf2977f2668fa7213522081c
Additional Information 3: 1ac0
Additional Information 4: 79391a57c1698c1550ee327c075e511e
I am trying to fix some error related to a SEGMENTATION FAULT. So when I try to fix the error using by step by step debugging of the code, I got couple of errors:
ERROR: cuda_trace_obj::initialize_cuda_library: Cuda initialize() returned CUDBG_ERROR_INITIALIZATION_FAILURE(20)!
ERROR: cuda_system_status_t::initialize: Error CUDBG_ERROR_UNINITIALIZED(5) getting device count
Any help or pointers regarding the above mentioned errors is appreciated.
This error often occurs when you debug a CUDA application on a computer with a single GPU and an X11 server running.
In a single GPU system, CUDA applications can be used debugged only if no X11 server (on Linux) or no Aqua desktop manager (on Mac OS X) is running on that system.
As far as I know, only the command line debugger CUDA-GDB is able to override this restriction setting software preemption as described in the cuda-gdb documentation, but works only for devices with SM3.5 compute capability and higher.