Develop Reference

Genymotion crash after start it

After I start it will close immediately and show this log on terminal:
player:
../../../../../../../src/mesa/drivers/dri/i915/i915_fragprog.c:1273:
i915BindProgram: Assertion `p->on_hardware == 0' failed.
I think it due to mesa version: This is my OpenGL and Mesa version
OpenGL version string: 1.4 Mesa 10.1.3

You need to Uncheck the "Use Host GPU" checkbox - in the emulator settings

Why does android emulator show black screen and its not string

Hi i am trying to start my emulator in eclipe but it's not starting. It shows logcat error as below...please help me....how to overcome this problem
09-11 19:13:13.020: I/Netd(622): Netd 1.0 starting
09-11 19:13:13.040: W/InterfaceController(622): Warning (dlopen failed: library"/system/lib/libnetcmdiface.so" not found) while opening the net interface command library
09-11 19:13:13.260: I/SurfaceFlinger(623): SurfaceFlinger is starting
09-11 19:13:13.260: I/SurfaceFlinger(623): SurfaceFlinger's main thread ready to run. Initializing graphics H/W...
09-11 19:13:13.260: D/libEGL(623): Emulator without GPU support detected. Fallback to software renderer.
09-11 19:13:13.300: D/libEGL(623): loaded /system/lib/egl/libGLES_android.so
09-11 19:13:13.380: D/gralloc_goldfish(623): Emulator without GPU emulation detected.
09-11 19:13:13.400: E/SurfaceFlinger(623): hwcomposer module not found
09-11 19:13:13.400: E/SurfaceFlinger(623): ERROR: failed to open framebuffer (No such file or directory), aborting
09-11 19:13:13.400: A/libc(623): Fatal signal 6 (SIGABRT) at 0x0000026f (code=-6), thread 623 (surfaceflinger)

When booting the emulator from Eclipse, look at the Console tab, not the log tab. Console may show error messages. The Log tab only shows logcat, which are messages from Android itself
When you create a new emulator it warns you about assigning it too much RAM if you try anything above 768M the emulator may not start according to the error message at the bottom of the virtual device setup. Do try with 512M of RAM and see if it starts.
While creating emulator check the option "Use Host GPU" at the bottom
or try another API version

Android emulator stuck in boot loop -library "/system/lib/libnetcmdiface.so" not found

I have tried to boot my emulator on three different platforms windows 7, ubuntu 12.04 and kubuntu 13.10(fresh install). However it always stops here with the logcat looping with the output below.
Could anyone help me figure this out. It is quite frustrating and I have lost close to a week of development.
D/AndroidRuntime( 3143): >>>>>> AndroidRuntime START com.android.internal.os.ZygoteInit <<<<<<
D/AndroidRuntime( 3143): CheckJNI is ON
E/dalvikvm( 3143): Can't create markStack
W/dalvikvm( 3143): CreateJavaVM failed: dvmGcStartup failed
E/AndroidRuntime( 3143): JNI_CreateJavaVM failed
I/Netd ( 3161): Netd 1.0 starting
W/InterfaceController( 3161): Warning (dlopen failed: library "/system/lib/libnetcmdiface.so" not found) while opening the net interface command library
D/AndroidRuntime( 3162):

I run into similar issue when I replaced libcrypto.so with my version. As restored /system/lib/libcrypto.so with original copy, things worked fine.

This happened unexpectedly on my Android 12 emulator. It would no longer boot up, and instead just get stuck on the black screen that has the word "android" in white letters, with a gray fade animation over the letters.
The logcat output would just have repeated displays of this every 10 seconds or so:
E/AndroidRuntime( 3143): JNI_CreateJavaVM failed
I couldn't find a way to fix it, so I just deleted the emulator and recreated it again, in Android Studio -> Tools -> Device Manager -> Create Device -> select a suitable screen size and a name -> Next -> press the tab "x86 Images" -> then select the Android 12 API 31 image that you have already downloaded.

Android ADK 2011: IO Exception in run thread

I have an ADK Kit from Google I/O 2011 and I am trying to get the example application to work (Available here: http://developer.android.com/tools/adk/adk.html).
I have programmed the firmware and device as instructed, but cannot get the demo to work. The application starts, and detects the ADK board when plugged in, but then enters a loop in which the device connects then disconnects very rapidly, causing the UI Activity to keep restarting.
I have been debugging this for a few days, and have verified that the device gets an IOException in the run() method of DemoKitActivity.java which causes the thread to terminate, although I am unsure if this is caused by or the cause of the device disconnecting.
The exception thrown is:
06-27 23:21:51.284: E/DemoKit(13573): There was an IO Exception
06-27 23:21:51.284: E/DemoKit(13573): at libcore.io.IoBridge.read(IoBridge.java:435)
06-27 23:21:51.284: E/DemoKit(13573): at java.io.FileInputStream.read(FileInputStream.java:179)
06-27 23:21:51.284: E/DemoKit(13573): at java.io.InputStream.read(InputStream.java:163)
06-27 23:21:51.284: E/DemoKit(13573): at com.google.android.DemoKit.DemoKitActivity.run(DemoKitActivity.java:278)
06-27 23:21:51.284: E/DemoKit(13573): at java.lang.Thread.run(Thread.java:841)
06-27 23:21:51.284: E/DemoKit(13573): Caused by: libcore.io.ErrnoException: read failed: EIO (I/O error)
06-27 23:21:51.284: E/DemoKit(13573): at libcore.io.Posix.readBytes(Native Method)
06-27 23:21:51.284: E/DemoKit(13573): at libcore.io.Posix.read(Posix.java:127)
06-27 23:21:51.284: E/DemoKit(13573): at libcore.io.BlockGuardOs.read(BlockGuardOs.java:149)
06-27 23:21:51.284: E/DemoKit(13573): at libcore.io.IoBridge.read(IoBridge.java:425)
One possible quirk is that my device is set to communicate over PTP (Settings > Storage > Menu > USB Computer Connection > Camera (PTP).
I don't yet have much more information. I am hoping that someone can confirm that the example code provided by Google still works with the ADK, or can provide some insight into where to look next to debug the disconnections.

I can confirm that the example ADK code works with both a Nexus 4 running 4.2.1 and a Galaxy Nexus running 4.0.4.
I've tried both using the Gingerbread compatibility API and using the API 12 classes on the Android DemoKit app successfully.
The ADK 2011 board that I have hasn't been used recently so while it worked with a ICS (4.0.4) device it wasn't working with the Nexus 4 with JB.
The following SO topic covers the issue with JB:
ADK 1.0 devices fail to work with Jelly Bean, why?
Also the CapSense libraries have been renamed in the most recent download from the Arduino site. CapSense.h becomes CapacitorSensor.h and so on.
Otherwise I was able to install the new code onto the Arduino ADK board, install the app on the Android device and run the DemoKit app.
The Nexus 4 was also in PTP mode during my test so I don't that that is your problem.
I'm also assuming you got your logs via adb over wi-fi and not connecting it over usb as that cable should go into the ADK board. Other than making sure the ADK code is correct and perhaps trying it with a different USB cable or PC I don't have anything to suggest. While I did see some errors in the log for one test session, a reset of the ADK and app cleared it up. For reference here is my logcat from a working session hope it can help.
07-06 23:01:02.364 I/ActivityManager( 575): START u0 {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.google.android.DemoKit/.DemoKitLaunch} from pid 899
07-06 23:01:02.404 I/ActivityManager( 575): Start proc com.google.android.DemoKit for activity com.google.android.DemoKit/.DemoKitLaunch: pid=8715 uid=10110 gids={50110, 1028}
07-06 23:01:02.495 I/DemoKitLaunch( 8715): starting phone ui
07-06 23:01:02.925 D/DemoKit ( 8715): accessory opened
07-06 23:01:03.185 I/ActivityManager( 575): Displayed com.google.android.DemoKit/.DemoKitPhone: +692ms (total +795ms)
07-06 23:01:35.690 D/UsbDeviceManager( 575): entering USB accessory mode: UsbAccessory[mManufacturer=Google, Inc., mModel=DemoKit, mDescription=DemoKit Arduino Board, mVersion=1.0, mUri=http://www.android.com, mSerial=0000000012345678]
07-06 23:01:35.690 I/ActivityManager( 575): START u0 {flg=0x10000000 cmp=com.android.systemui/.usb.UsbConfirmActivity (has extras)} from pid 575
07-06 23:01:35.860 I/ActivityManager( 575): Displayed com.android.systemui/.usb.UsbConfirmActivity: +64ms
07-06 23:01:37.782 I/ActivityManager( 575): START u0 {act=android.hardware.usb.action.USB_ACCESSORY_ATTACHED flg=0x10000000 cmp=com.google.android.DemoKit/.UsbAccessoryActivity (has extras)} from pid 748
07-06 23:01:37.912 I/DemoKitLaunch( 8715): starting phone ui
07-06 23:01:37.912 I/ActivityManager( 575): START u0 {flg=0x14000000 cmp=com.google.android.DemoKit/.DemoKitPhone} from pid 8715
07-06 23:01:38.022 D/DemoKit ( 8715): accessory opened

SEandroid Boot Up Problems

I'm currently working on flashing SEandroid (security enhanced Android) onto a Nexus 7, but when I try to boot up, the Nexus 7 just flashes the Google screen and nothing else.
I successfully compiled the SEandroid Source code for both 4.2.1 and 4.1.2 and neither run on the Nexus.
Was wondering what some common errors could be for a device booting up, but the screen not showing anything?
I downloaded and compiled the code according to: http://selinuxproject.org/page/SEAndroid
I am using the tegra3_android_defconfig for my kernel and am using the full_grouper_userdebug.
Any help, even if not related to SEandroid would be helpful.
Here is an output from logcat:
--------- beginning of /dev/log/main
I/Netd ( 124): Netd 1.0 starting
W/InterfaceController( 124): Warning (Cannot load library: load_library(linker.cpp:745): library "/system/lib/libnetcmdiface.so" not found) while opening the net interface command library
I/installd( 130): installd firing up
I/DEBUG ( 125): debuggerd: Jun 12 2013 10:32:23
I/SurfaceFlinger( 126): SurfaceFlinger is starting
I/SurfaceFlinger( 126): SurfaceFlinger's main thread ready to run. Initializing graphics H/W...
E/libEGL ( 126): eglGetDisplay:121 error 300c (EGL_BAD_PARAMETER)
E/libEGL ( 126): eglInitialize:137 error 3008 (EGL_BAD_DISPLAY)
Thanks in advanced.

Rookie mistake. Forgot to add in Google's proprietary drivers for the Nexus 7.
Available here for who ever needs them!
https://developers.google.com/android/nexus/drivers
thanks all