Discussion:
Porting CyanogenMod 12.1 to x86
JJ Meijer
2015-09-29 10:53:53 UTC
Permalink
Hello everybody,

I started a project to learn something more about Linux and Android so I
started to port the Cyanogen project to my HP Omni 10 (Baytrail) tablet.
Many thanks to the Android-x86 project I had relatively quickly my tablet
booting and change_rooting into Android.

At the moment surfaceflinger is crashing because of a missing EGLConfig (No
suitable EGLConfig found). Hints in how this config should be supplied are
very welcome!

I will let you know how it goes... :)

Kind regard, JJ
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at http://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
JJ Meijer
2015-09-29 18:51:10 UTC
Permalink
Ok, so after some digging I found out I forgot to set androidboot.hardware
to load the correct gralloc.$hardware.so. Available are default and drm so
I choose drm although it feels like this is not correct...

Now it's doing a little bit more but i get:
E/GRALLOC-MOD( 4094): failed to add fb
W/EGL-DRI2( 4094): Native format mismatch: 0x1 != 0x5

Here is the old log:

I/SurfaceFlinger( 3248): SurfaceFlinger is starting
I/SurfaceFlinger( 3248): SurfaceFlinger's main thread ready to run.
Initializing graphics H/W...
D/libEGL ( 3248): loaded /system/lib/egl/libGLES_mesa.so
W/EGL-DRI2( 3248): fail to get drm fd
W/libEGL ( 3248): eglInitialize(0xb6867400) failed (EGL_NOT_INITIALIZED)
W/gralloc ( 3248): FBIOPUT_VSCREENINFO failed, page flipping not supported
W/gralloc ( 3248): page flipping not supported (yres_virtual=1200,
requested=2400)
I/gralloc ( 3248): using (fd=11)
I/gralloc ( 3248): id = inteldrmfb
I/gralloc ( 3248): xres = 1920 px
I/gralloc ( 3248): yres = 1200 px
I/gralloc ( 3248): xres_virtual = 1920 px
I/gralloc ( 3248): yres_virtual = 1200 px
I/gralloc ( 3248): bpp = 32
I/gralloc ( 3248): r = 16:8
I/gralloc ( 3248): g = 8:8
I/gralloc ( 3248): b = 0:8
I/gralloc ( 3248): width = 305 mm (159.895081 dpi)
I/gralloc ( 3248): height = 191 mm (159.581146 dpi)
I/gralloc ( 3248): refresh rate = 60.00 Hz
W/hwcomposer( 3248): getting VSYNC period from fb HAL: 16666667
D/hwcomposer( 3248): Intel hwcomposer module
I/SurfaceFlinger( 3248): Using composer version 1.0
W/SurfaceFlinger( 3248): no suitable EGLConfig found, trying a simpler query
F/SurfaceFlinger( 3248): no suitable EGLConfig found, giving up
--------- beginning of crash
F/libc ( 3248): Fatal signal 4 (SIGILL), code 2, fault addr 0xb767f3dc
in tid 3248 (surfaceflinger)

New log:

I/SurfaceFlinger( 4094): SurfaceFlinger is starting
I/SurfaceFlinger( 4094): SurfaceFlinger's main thread ready to run.
Initializing graphics H/W...
D/libEGL ( 4094): loaded /system/lib/egl/libGLES_mesa.so
I/GRALLOC-DRM( 4094): create intel for driver i915
I/ServiceManager( 4023): Waiting for service SurfaceFlinger...
D/GRALLOC-KMS( 4094): supported drm planes and formats
D/GRALLOC-KMS( 4094): plane id 21
D/GRALLOC-KMS( 4094): format RG16
D/GRALLOC-KMS( 4094): format AB24
D/GRALLOC-KMS( 4094): format AR24
D/GRALLOC-KMS( 4094): format XB24
D/GRALLOC-KMS( 4094): format XR24
D/GRALLOC-KMS( 4094): format XB30
D/GRALLOC-KMS( 4094): format AB30
D/GRALLOC-KMS( 4094): format YUYV
D/GRALLOC-KMS( 4094): format YVYU
D/GRALLOC-KMS( 4094): format UYVY
D/GRALLOC-KMS( 4094): format VYUY
D/GRALLOC-KMS( 4094): plane id 22
D/GRALLOC-KMS( 4094): format RG16
D/GRALLOC-KMS( 4094): format AB24
D/GRALLOC-KMS( 4094): format AR24
D/GRALLOC-KMS( 4094): format XB24
D/GRALLOC-KMS( 4094): format XR24
D/GRALLOC-KMS( 4094): format XB30
D/GRALLOC-KMS( 4094): format AB30
D/GRALLOC-KMS( 4094): format YUYV
D/GRALLOC-KMS( 4094): format YVYU
D/GRALLOC-KMS( 4094): format UYVY
D/GRALLOC-KMS( 4094): format VYUY
D/GRALLOC-KMS( 4094): plane id 26
D/GRALLOC-KMS( 4094): format RG16
D/GRALLOC-KMS( 4094): format AB24
D/GRALLOC-KMS( 4094): format AR24
D/GRALLOC-KMS( 4094): format XB24
D/GRALLOC-KMS( 4094): format XR24
D/GRALLOC-KMS( 4094): format XB30
D/GRALLOC-KMS( 4094): format AB30
D/GRALLOC-KMS( 4094): format YUYV
D/GRALLOC-KMS( 4094): format YVYU
D/GRALLOC-KMS( 4094): format UYVY
D/GRALLOC-KMS( 4094): format VYUY
D/GRALLOC-KMS( 4094): plane id 27
D/GRALLOC-KMS( 4094): format RG16
D/GRALLOC-KMS( 4094): format AB24
D/GRALLOC-KMS( 4094): format AR24
D/GRALLOC-KMS( 4094): format XB24
D/GRALLOC-KMS( 4094): format XR24
D/GRALLOC-KMS( 4094): format XB30
D/GRALLOC-KMS( 4094): format AB30
D/GRALLOC-KMS( 4094): format YUYV
D/GRALLOC-KMS( 4094): format YVYU
D/GRALLOC-KMS( 4094): format UYVY
D/GRALLOC-KMS( 4094): format VYUY
I/GRALLOC-KMS( 4094): there are 2 modes on connector 0x26, type 14
I/GRALLOC-KMS( 4094): 1920x1200
I/GRALLOC-KMS( 4094): 1920x1200
I/GRALLOC-KMS( 4094): Established mode:
I/GRALLOC-KMS( 4094): clock: 149900, hdisplay: 1920, hsync_start: 1964,
hsync_end: 1996, htotal: 2064, hskew: 0
I/GRALLOC-KMS( 4094): vdisplay: 1200, vsync_start: 1203, vsync_end: 1208,
vtotal: 1210, vscan: 0, vrefresh: 60
I/GRALLOC-KMS( 4094): flags: 10, type: 72, name 1920x1200
I/GRALLOC-KMS( 4094): the best mode is 1920x1200
W/dex2oat ( 3534): Verification of void
org.ccil.cowan.tagsoup.HTMLSchema.<init>() took 145.974ms
D/GRALLOC-KMS( 4094): will use flip for fb posting
I/GRALLOC-MOD( 4094): mode.hdisplay 1920
I/GRALLOC-MOD( 4094): mode.vdisplay 1200
I/GRALLOC-MOD( 4094): mode.vrefresh 60.000000
I/GRALLOC-MOD( 4094): format 0x5
I/GRALLOC-MOD( 4094): xdpi 221.000000
I/GRALLOC-MOD( 4094): ydpi 217.000000
I/GRALLOC-MOD( 4094): mode.hdisplay 1920
I/GRALLOC-MOD( 4094): mode.vdisplay 1200
I/GRALLOC-MOD( 4094): mode.vrefresh 60.000000
I/GRALLOC-MOD( 4094): format 0x5
I/GRALLOC-MOD( 4094): xdpi 221.000000
I/GRALLOC-MOD( 4094): ydpi 217.000000
W/hwcomposer( 4094): getting VSYNC period from fb HAL: 16666667
D/hwcomposer( 4094): Intel hwcomposer module
I/SurfaceFlinger( 4094): Using composer version 1.0
W/SurfaceFlinger( 4094): no suitable EGLConfig found, trying a simpler query
I/SurfaceFlinger( 4094): EGL information:
I/SurfaceFlinger( 4094): vendor : Android
I/SurfaceFlinger( 4094): version : 1.4 Android META-EGL
I/SurfaceFlinger( 4094): extensions: EGL_KHR_get_all_proc_addresses
EGL_ANDROID_presentation_time EGL_KHR_image_base
EGL_KHR_gl_texture_2D_image EGL_KHR_gl_texture_cubemap_image
EGL_KHR_gl_renderbuffer_image EGL_KHR_create_context
EGL_EXT_create_context_robustness EGL_ANDROID_image_native_buffer
I/SurfaceFlinger( 4094): Client API: OpenGL_ES
I/SurfaceFlinger( 4094): EGLSurface: 8-8-8-8, config=0xb684a660
I/SurfaceFlinger( 4094): OpenGL ES informations:
I/SurfaceFlinger( 4094): vendor : Intel Open Source Technology Center
I/SurfaceFlinger( 4094): renderer : Mesa DRI Intel(R) Bay Trail
I/SurfaceFlinger( 4094): version : OpenGL ES 3.0 Mesa 10.7.0-devel
I/SurfaceFlinger( 4094): extensions: GL_EXT_debug_marker
GL_EXT_blend_minmax GL_EXT_multi_draw_arrays
GL_EXT_texture_filter_anisotropic GL_EXT_texture_compression_dxt1
GL_EXT_texture_format_BGRA8888 GL_OES_compressed_ETC1_RGB8_texture
GL_OES_depth24 GL_OES_element_index_uint GL_OES_fbo_render_mipmap
GL_OES_mapbuffer GL_OES_rgb8_rgba8 GL_OES_standard_derivatives
GL_OES_stencil8 GL_OES_texture_3D GL_OES_texture_float
GL_OES_texture_float_linear GL_OES_texture_half_float
GL_OES_texture_half_float_linear GL_OES_texture_npot GL_OES_EGL_image
GL_OES_depth_texture GL_OES_packed_depth_stencil
GL_EXT_texture_type_2_10_10_10_REV GL_OES_get_program_binary
GL_APPLE_texture_max_level GL_EXT_discard_framebuffer
GL_EXT_read_format_bgra GL_NV_fbo_color_attachments
GL_OES_EGL_image_external GL_OES_EGL_sync GL_OES_vertex_array_object
GL_ANGLE_texture_compression_dxt3 GL_ANGLE_texture_compression_dxt5
GL_EXT_texture_rg GL_EXT_unpack_subimage GL_NV_draw_buffers
GL_NV_read_buffer GL_EXT_draw_buffers GL_EXT_map_buffer_range
GL_OES_depth_texture_cube_map
I/SurfaceFlinger( 4094): GL_MAX_TEXTURE_SIZE = 8192
I/SurfaceFlinger( 4094): GL_MAX_VIEWPORT_DIMS = 16384
E/cutils-trace( 4094): Error opening trace file: No such file or directory
(2)
W/EGL-DRI2( 4094): Native format mismatch: 0x1 != 0x5
D/SurfaceFlinger( 4094): Set power mode=2, type=0 flinger=0xb685c000
D/SurfaceFlinger( 4094): SF. shader cache generated - 26 shaders in
215.846298 ms
E/GRALLOC-MOD( 4094): failed to add fb
W/GraphicBufferAllocator( 4094): alloc(1920, 1200, 1, 00001a00, ...) failed
-22 (Invalid argument)
E/ ( 4094): GraphicBufferAlloc::createGraphicBuffer(w=1920, h=1200)
failed (Invalid argument), handle=0x0
E/BufferQueueProducer( 4094): [FramebufferSurface] dequeueBuffer:
createGraphicBuffer failed
F/libc ( 4094): Fatal signal 11 (SIGSEGV), code 1, fault addr 0x38 in
tid 4094 (surfaceflinger)
I/ServiceManager( 1386): service 'SurfaceFlinger' died
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at http://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
pstglia
2015-09-29 19:29:07 UTC
Permalink
Post by JJ Meijer
Ok, so after some digging I found out I forgot to set androidboot.hardware
to load the correct gralloc.$hardware.so. Available are default and drm so
I choose drm although it feels like this is not correct...
E/GRALLOC-MOD( 4094): failed to add fb
W/EGL-DRI2( 4094): Native format mismatch: 0x1 != 0x5
Apparently he's complaining one format is set to HAL_PIXEL_FORMAT_*RGBA*_8888
(0x1) and another to HAL_PIXEL_FORMAT_*BGRA*_8888 (0x5 - This is the
default format used - see intel_init_kms_features on
hardware/drm_gralloc/gralloc_drm_intel.c)

Suggest you debug these src files:

hardware/drm_gralloc/gralloc_drm_intel.c
external/mesa/src/egl/drivers/dri2/platform_android.c

Regards,
Pstglia
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at http://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
JJ Meijer
2015-09-29 21:17:45 UTC
Permalink
Thanks for the suggestions! I looked into in and it looks like it is just a
warning and not a show stopper.

The (Invalid argument) sounds more serious (or maybe this is related to the
pixel format of course):


W/GraphicBufferAllocator( 4094): alloc(1920, 1200, 1, 00001a00, ...) failed
-22 (Invalid argument)
E/ ( 4094): GraphicBufferAlloc::createGraphicBuffer(w=1920, h=1200)
failed (Invalid argument), handle=0x0
E/BufferQueueProducer( 4094): [FramebufferSurface] dequeueBuffer:
createGraphicBuffer failed
F/libc ( 4094): Fatal signal 11 (SIGSEGV), code 1, fault addr 0x38 in
tid 4094 (surfaceflinger)
Post by pstglia
Post by JJ Meijer
Ok, so after some digging I found out I forgot to set
androidboot.hardware to load the correct gralloc.$hardware.so. Available
are default and drm so I choose drm although it feels like this is not
correct...
E/GRALLOC-MOD( 4094): failed to add fb
W/EGL-DRI2( 4094): Native format mismatch: 0x1 != 0x5
Apparently he's complaining one format is set to HAL_PIXEL_FORMAT_*RGBA*_8888
(0x1) and another to HAL_PIXEL_FORMAT_*BGRA*_8888 (0x5 - This is the
default format used - see intel_init_kms_features on
hardware/drm_gralloc/gralloc_drm_intel.c)
hardware/drm_gralloc/gralloc_drm_intel.c
external/mesa/src/egl/drivers/dri2/platform_android.c
Regards,
Pstglia
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at http://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
pstglia
2015-09-29 22:19:54 UTC
Permalink
Post by JJ Meijer
Thanks for the suggestions! I looked into in and it looks like it is just
a warning and not a show stopper.
The (Invalid argument) sounds more serious (or maybe this is related to
W/GraphicBufferAllocator( 4094): alloc(1920, 1200, 1, 00001a00, ...)
failed -22 (Invalid argument)
E/ ( 4094): GraphicBufferAlloc::createGraphicBuffer(w=1920, h=1200)
failed (Invalid argument), handle=0x0
createGraphicBuffer failed
F/libc ( 4094): Fatal signal 11 (SIGSEGV), code 1, fault addr 0x38 in
tid 4094 (surfaceflinger)
I think they are all related. The first call to
"GraphicBufferAllocator::alloc" is trying to allocate a new buffer on GPU.
This job is done under external/drm_gralloc (which communicates with GPU
through libdrm) and external/mesa.

However, appears to me that the mismatched format avoided it from
allocating this buffer. So, it should have returned an error propagated to
the caller (surfaceflinger)

If you look at frameworks/native/services/surfaceflinger/SurfaceFlinger.cpp
you'll find in certain points it sets format to PIXEL_FORMAT_RGBA_8888

As suggestions, you could try these:

1) Include ""

#include "intel_chipset.h" /* for platform detection macros */
static void intel_init_kms_features(struct gralloc_drm_drv_t *drv,
struct gralloc_drm_t *drm)
{
...
switch (drm->primary.fb_format) {
case HAL_PIXEL_FORMAT_BGRA_8888:
case HAL_PIXEL_FORMAT_RGB_565:
*case HAL_PIXEL_FORMAT_RGBA_8888:*
break;
default:
drm->primary.fb_format = HAL_PIXEL_FORMAT_BGRA_8888;
break;
}

OR

2) Change formats used on SurfaceFlinger from "PIXEL_FORMAT_RGBA_8888" to
"PIXEL_FORMAT_BGRA_8888"



Regards,
Pstglia
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at http://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
pstglia
2015-09-29 22:24:25 UTC
Permalink
Post by JJ Meijer
Thanks for the suggestions! I looked into in and it looks like it is just
a warning and not a show stopper.
The (Invalid argument) sounds more serious (or maybe this is related to
W/GraphicBufferAllocator( 4094): alloc(1920, 1200, 1, 00001a00, ...)
failed -22 (Invalid argument)
E/ ( 4094): GraphicBufferAlloc::createGraphicBuffer(w=1920, h=1200)
failed (Invalid argument), handle=0x0
createGraphicBuffer failed
F/libc ( 4094): Fatal signal 11 (SIGSEGV), code 1, fault addr 0x38 in
tid 4094 (surfaceflinger)
I think they are all related. The first call to
"GraphicBufferAllocator::alloc" is trying to allocate a new buffer on GPU.
This job is done under external/drm_gralloc (which communicates with GPU
through libdrm) and external/mesa.

However, appears to me that the mismatched format avoided it from
allocating this buffer. So, it should have returned an error propagated to
the caller (surfaceflinger)

If you look at frameworks/native/services/surfaceflinger/SurfaceFlinger.cpp
you'll find in certain points it sets format to PIXEL_FORMAT_RGBA_8888

As suggestions, you could try these:

1) Include "*HAL_PIXEL_FORMAT_RGBA_8888*" as a valid format for buffer
creation:

#include "intel_chipset.h" /* for platform detection macros */
static void intel_init_kms_features(struct gralloc_drm_drv_t *drv,
struct gralloc_drm_t *drm)
{
...
switch (drm->primary.fb_format) {
case HAL_PIXEL_FORMAT_BGRA_8888:
case HAL_PIXEL_FORMAT_RGB_565:
*case HAL_PIXEL_FORMAT_RGBA_8888:*
break;
default:
drm->primary.fb_format = HAL_PIXEL_FORMAT_BGRA_8888;
break;
}

OR

2) Change formats used on SurfaceFlinger from "PIXEL_FORMAT_RGBA_8888" to
"PIXEL_FORMAT_BGRA_8888"



Regards,
Pstglia
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at http://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
JJ Meijer
2015-09-30 17:09:42 UTC
Permalink
Thanks for the help! I tried both but it didn't change anything for some
reason, the log is still exactly the same.

I also tried to change
frameworks/native/libs/ui/FramebufferNativeWindow.cpp but it looks like the
code isn't even executed because I don't see the added debug lines.

/*
* This does not actually change the framebuffer format. It merely
* fakes this format to surfaceflinger so that when it creates
* framebuffer surfaces it will use this format. It's really a giant
* HACK to allow interworking with buggy gralloc+GPU driver
* implementations. You should *NEVER* need to set this for shipping
* devices.
*/
#ifdef FRAMEBUFFER_FORCE_FORMAT
*((uint32_t *)&fbDev->format) = FRAMEBUFFER_FORCE_FORMAT;
ALOGE("-----Detected force format");
#endif
*((uint32_t *)&fbDev->format) = 5; // Just to be sure
ALOGE("--------Force format set");
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at http://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
JJ Meijer
2015-10-05 19:11:12 UTC
Permalink
After creating a giant mess of it all I started over..

Basically this is my configuration regarding HW / GPU, for now it would be
nice if SurfaceFlinger would fling a surface :o)

Sadly I'm ending up with a blanked screen and a flashing cursor. The logs
show SurfaceFlinger is crash-looping becouse of the 'no suitable EGLConfig
found, giving up' error. What could I be missing?

BoardConfig.mk
# Video
BOARD_GPU_DRIVERS := i915 i965
TARGET_HARDWARE_3D := true
USE_OPENGL_RENDERER := true
BOARD_EGL_CFG := device/hp/omni/gpu/egl_mesa.cfg



device.mk

# Get the hardware acceleration libraries
$(call inherit-product-if-exists,$(LOCAL_PATH)/gpu/gpu_mesa.mk)



local_manifest:

<!-- mesa -->
<remove-project name="platform/external/mesa3d" />
<project path="external/mesa" name="platform/external/mesa" remote="x86"
revision="lollipop-x86" />
<project path="external/drm" name="platform/external/drm" remote="x86"
revision="lollipop-x86" />
<project path="hardware/drm_gralloc" name="platform/hardware/drm_gralloc"
remote="x86" revision="lollipop-x86" />
<project path="hardware/intel/hwcomposer" name=
"platform/hardware/intel/hwcomposer" remote="x86" revision="lollipop-x86" />
<project path="external/libpciaccess" name="platform/external/libpciaccess"
remote="x86" revision="lollipop-x86" />

tombstone:
*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
Build fingerprint:
'hp/cm_omni/omni:5.1.1/LVY48F/82b51dd96d:userdebug/test-keys'
Revision: '0'
ABI: 'x86'
pid: 22725, tid: 22725, name: surfaceflinger >>>
/system/bin/surfaceflinger <<<
signal 4 (SIGILL), code 2 (ILL_ILLOPN), fault addr 0xb765aedd
Abort message: 'no suitable EGLConfig found, giving up'
eax fffffffe ebx b7664e2c ecx 2b9ac182 edx 2b9ac182
esi 00000000 edi 00000005
xcs 00000073 xds 0000007b xes 0000007b xfs 00000000 xss 0000007b
eip b765aedd ebp bfabb95c esp bfabb930 flags 00010282

backtrace:
#00 pc 0000cedd /system/lib/libcutils.so (__android_log_assert+125)
#01 pc 0003e7db /system/lib/libsurfaceflinger.so
#02 pc 0003e12c /system/lib/libsurfaceflinger.so
#03 pc 00022bb0 /system/lib/libsurfaceflinger.so
(android::SurfaceFlinger::init()+320)
#04 pc 00000b51 /system/bin/surfaceflinger
#05 pc 000106aa /system/lib/libc.so (__libc_init+106)
#06 pc 00000ced /system/bin/surfaceflinger

stack:
bfabb8f0 0000000f
bfabb8f4 bfabb95c [stack]
bfabb8f8 00000034
bfabb8fc bfabb8ac [stack]
bfabb900 00000000
bfabb904 00000000
bfabb908 b6873140
bfabb90c 2b9ac182
bfabb910 b6873260
bfabb914 b6c00170
bfabb918 bfabb92c [stack]
bfabb91c b7664e2c /system/lib/libcutils.so
bfabb920 00000000
bfabb924 00000005
bfabb928 bfabb95c [stack]
bfabb92c b765aedd /system/lib/libcutils.so
(__android_log_assert+125)
#00 bfabb930 00000007
bfabb934 b760118a /system/lib/libsurfaceflinger.so
bfabb938 bfabb95c [stack]
bfabb93c bfabbd8c [stack]
bfabb940 00000005
bfabb944 b760118a /system/lib/libsurfaceflinger.so
bfabb948 bfabb95c [stack]
bfabb94c b760118a /system/lib/libsurfaceflinger.so
bfabb950 6f632067
bfabb954 736f706d
bfabb958 76207265
bfabb95c 73206f6e
bfabb960 61746975
bfabb964 20656c62
bfabb968 434c4745
bfabb96c 69666e6f
........ ........
#01 bfabbd80 00000000
bfabbd84 b760118a /system/lib/libsurfaceflinger.so
bfabbd88 b7603e6e /system/lib/libsurfaceflinger.so
bfabbd8c b7589dec /system/lib/libEGL.so
bfabbd90 00003055
bfabbd94 b7589dec /system/lib/libEGL.so
bfabbd98 00000000
bfabbd9c b74e741c /system/lib/libEGL.so
(eglQueryStringImplementationANDROID(void*, int)+124)
bfabbda0 b7590ed8 /system/lib/libEGL.so
bfabbda4 b760118a /system/lib/libsurfaceflinger.so
bfabbda8 55555555
bfabbdac 416fca05
bfabbdb0 00000780
bfabbdb4 000004b0
bfabbdb8 431fe524
bfabbdbc 00000005
........ ........
#02 bfabbdd0 00000001
bfabbdd4 00000005
bfabbdd8 00000000
bfabbddc b7652623 /system/lib/libcutils.so
(android_atomic_inc+35)
bfabbde0 00000001
bfabbde4 b6839114
bfabbde8 b75bae6c /system/lib/libutils.so
bfabbdec b75a66f5 /system/lib/libutils.so
(android::RefBase::weakref_type::decWeak(void const*)+37)
bfabbdf0 b6839114
bfabbdf4 b6839110
bfabbdf8 b75bae6c /system/lib/libutils.so
bfabbdfc b7652623 /system/lib/libcutils.so
(android_atomic_inc+35)
bfabbe00 00000001
bfabbe04 b75bae6c /system/lib/libutils.so
bfabbe08 b6839110
bfabbe0c b75a67d0 /system/lib/libutils.so
(android::RefBase::decStrong(void const*) const+64)
........ ........
#03 bfabbe40 00000001
bfabbe44 00000005
bfabbe48 b685c014
bfabbe4c b7687068 /system/lib/libc.so (pthread_once+232)
bfabbe50 000000f0
bfabbe54 b76650c4 /system/lib/libcutils.so
bfabbe58 00000081
bfabbe5c 7fffffff
bfabbe60 00000000
bfabbe64 b6839114
bfabbe68 b75bae6c /system/lib/libutils.so
bfabbe6c b7652623 /system/lib/libcutils.so
(android_atomic_inc+35)
bfabbe70 b76885c4 /system/lib/libc.so (__set_errno_internal+20)
bfabbe74 b6839160
bfabbe78 b76885b6 /system/lib/libc.so (__set_errno_internal+6)
bfabbe7c b685c018
........ ........
#04 bfabbf10 b685c000
bfabbf14 00000001
bfabbf18 fffffff8
bfabbf1c b768cbcd /system/lib/libc.so (_thread_atexit_unlock+29)
bfabbf20 b7750508
bfabbf24 00000009
bfabbf28 b77a41f4 /system/bin/linker
bfabbf2c b77a4200 /system/bin/linker
bfabbf30 bfabbf50 [stack]
bfabbf34 b768cbb6 /system/lib/libc.so (_thread_atexit_unlock+6)
bfabbf38 bfabbf4c [stack]
bfabbf3c b76da72a /system/lib/libc.so (__cxa_atexit+234)
bfabbf40 b7253000
bfabbf44 00001000
bfabbf48 00000001
bfabbf4c b684e400
........ ........
#05 bfabbf90 00000001
bfabbf94 bfabbff4 [stack]
bfabbf98 bfabbffc [stack]
bfabbf9c 00000000
bfabbfa0 00000000
bfabbfa4 00000000
bfabbfa8 00000000
bfabbfac 8007cf90 /system/bin/surfaceflinger
bfabbfb0 bfabbff0 [stack]
bfabbfb4 00000000
bfabbfb8 bfabbfec [stack]
bfabbfbc 8007acee /system/bin/surfaceflinger
#06 bfabbfc0 bfabbff0 [stack]
bfabbfc4 00000000
bfabbfc8 8007aa80 /system/bin/surfaceflinger
bfabbfcc bfabbfd0 [stack]
bfabbfd0 8007ce38 /system/bin/surfaceflinger
bfabbfd4 8007ce40 /system/bin/surfaceflinger
bfabbfd8 8007ce4c /system/bin/surfaceflinger
bfabbfdc bfabbff0 [stack]
bfabbfe0 00000000
bfabbfe4 00000000
bfabbfe8 b77bbfec /system/bin/linker
bfabbfec bfabbfec [stack]
bfabbff0 00000001
bfabbff4 bfabdc34 [stack]
bfabbff8 00000000
bfabbffc bfabdc4f [stack]

memory map: (fault address prefixed with --->)
8007a000-8007bfff r-x 8192 /system/bin/surfaceflinger
8007c000-8007cfff r-- 4096 /system/bin/surfaceflinger
8007d000-8007dfff rw- 4096
b5702000-b5702fff --- 4096
b5703000-b57fffff rw- 1036288 [stack:22739]
b5800000-b5bfffff rw- 4194304
b5cb6000-b5cb7fff rw- 8192
b5cb8000-b5cb8fff --- 4096
b5cb9000-b5db5fff rw- 1036288 [stack:22738]
b5db6000-b5db8fff r-x 12288 /system/lib/hw/hwcomposer.omni.so
b5db9000-b5db9fff r-- 4096 /system/lib/hw/hwcomposer.omni.so
b5dba000-b5dbafff rw- 4096 /system/lib/hw/hwcomposer.omni.so
b5dbb000-b6684fff rw- 9216000 /dev/graphics/fb0
b6685000-b6687fff r-x 12288 /system/lib/hw/gralloc.default.so
b6688000-b6688fff r-- 4096 /system/lib/hw/gralloc.default.so
b6689000-b6689fff rw- 4096 /system/lib/hw/gralloc.default.so
b668a000-b66bbfff r-x 204800 /system/lib/libdrm_intel.so
b66bc000-b66bcfff r-- 4096 /system/lib/libdrm_intel.so
b66bd000-b66bdfff rw- 4096 /system/lib/libdrm_intel.so
b66be000-b66fdfff r-x 262144 /system/lib/libglapi.so
b66fe000-b6700fff r-- 12288 /system/lib/libglapi.so
b6701000-b6701fff rw- 4096 /system/lib/libglapi.so
b6702000-b6702fff --- 4096
b6703000-b67fffff rw- 1036288 [stack:22733]
b6800000-b7005fff rw- 8413184
b7006000-b700dfff r-x 32768 /system/lib/libnetutils.so
b700e000-b700efff r-- 4096 /system/lib/libnetutils.so
b700f000-b700ffff rw- 4096 /system/lib/libnetutils.so
b7010000-b7015fff r-x 24576 /system/lib/libhardware_legacy.so
b7016000-b7016fff r-- 4096 /system/lib/libhardware_legacy.so
b7017000-b7017fff rw- 4096 /system/lib/libhardware_legacy.so
b7018000-b7018fff rw- 4096
b7019000-b7021fff r-x 36864 /system/lib/libgralloc_drm.so
b7022000-b7022fff r-- 4096 /system/lib/libgralloc_drm.so
b7023000-b7023fff rw- 4096 /system/lib/libgralloc_drm.so
b7024000-b7032fff r-x 61440 /system/lib/libdrm.so
b7033000-b7033fff r-- 4096 /system/lib/libdrm.so
b7034000-b7034fff rw- 4096 /system/lib/libdrm.so
b7035000-b704ffff r-x 110592 /system/lib/egl/libGLES_mesa.so
b7050000-b7050fff r-- 4096 /system/lib/egl/libGLES_mesa.so
b7051000-b7051fff rw- 4096 /system/lib/egl/libGLES_mesa.so
b7052000-b7052fff rw- 4096
b7053000-b7053fff --- 4096
b7054000-b7150fff rw- 1036288 [stack:22732]
b7151000-b724efff r-- 1040384 /dev/binder
b724f000-b7250fff r-x 8192 /system/lib/libnetd_client.so
b7251000-b7251fff r-- 4096 /system/lib/libnetd_client.so
b7252000-b7252fff rw- 4096 /system/lib/libnetd_client.so
b7253000-b7253fff r-- 4096
b7254000-b7273fff r-- 131072 /dev/__properties__
b7274000-b7275fff r-x 8192 /system/lib/libunwind-ptrace.so
b7276000-b7276fff r-- 4096 /system/lib/libunwind-ptrace.so
b7277000-b7277fff rw- 4096 /system/lib/libunwind-ptrace.so
b7278000-b7290fff r-x 102400 /system/lib/libunwind.so
b7291000-b7291fff r-- 4096 /system/lib/libunwind.so
b7292000-b7292fff rw- 4096 /system/lib/libunwind.so
b7293000-b72a1fff rw- 61440
b72a2000-b72aefff r-x 53248 /system/lib/libgccdemangle.so
b72af000-b72affff --- 4096
b72b0000-b72b0fff r-- 4096 /system/lib/libgccdemangle.so
b72b1000-b72b1fff rw- 4096 /system/lib/libgccdemangle.so
b72b2000-b72b2fff r-x 4096 /system/lib/libsync.so
b72b3000-b72b3fff r-- 4096 /system/lib/libsync.so
b72b4000-b72b4fff rw- 4096 /system/lib/libsync.so
b72b5000-b7399fff r-x 937984 /system/lib/libGLES_trace.so
b739a000-b739afff r-- 4096 /system/lib/libGLES_trace.so
b739b000-b739bfff rw- 4096 /system/lib/libGLES_trace.so
b739c000-b7417fff r-x 507904 /system/lib/libstlport.so
b7418000-b7419fff r-- 8192 /system/lib/libstlport.so
b741a000-b741afff rw- 4096 /system/lib/libstlport.so
b741b000-b7427fff r-x 53248 /system/lib/libbacktrace.so
b7428000-b7428fff r-- 4096 /system/lib/libbacktrace.so
b7429000-b7429fff rw- 4096 /system/lib/libbacktrace.so
b742a000-b743bfff r-x 73728 /system/lib/libui.so
b743c000-b743cfff --- 4096
b743d000-b743dfff r-- 4096 /system/lib/libui.so
b743e000-b743efff rw- 4096 /system/lib/libui.so
b743f000-b7441fff r-x 12288 /system/lib/libpowermanager.so
b7442000-b7442fff r-- 4096 /system/lib/libpowermanager.so
b7443000-b7443fff rw- 4096 /system/lib/libpowermanager.so
b7444000-b7444fff r-x 4096 /system/lib/libhardware.so
b7445000-b7445fff r-- 4096 /system/lib/libhardware.so
b7446000-b7446fff rw- 4096 /system/lib/libhardware.so
b7447000-b74aafff r-x 409600 /system/lib/libgui.so
b74ab000-b74b3fff r-- 36864 /system/lib/libgui.so
b74b4000-b74b4fff rw- 4096 /system/lib/libgui.so
b74b5000-b74b5fff r-- 4096
b74b6000-b74c3fff r-x 57344 /system/lib/libGLESv2.so
b74c4000-b74c4fff --- 4096
b74c5000-b74c5fff r-- 4096 /system/lib/libGLESv2.so
b74c6000-b74c6fff rw- 4096 /system/lib/libGLESv2.so
b74c7000-b74cefff r-x 32768 /system/lib/libGLESv1_CM.so
b74cf000-b74cffff r-- 4096 /system/lib/libGLESv1_CM.so
b74d0000-b74d0fff rw- 4096 /system/lib/libGLESv1_CM.so
b74d1000-b7587fff r-x 749568 /system/lib/libEGL.so
b7588000-b7589fff r-- 8192 /system/lib/libEGL.so
b758a000-b7590fff rw- 28672 /system/lib/libEGL.so
b7591000-b7593fff rw- 12288
b7594000-b7594fff r-- 4096
b7595000-b75b8fff r-x 147456 /system/lib/libutils.so
b75b9000-b75b9fff --- 4096
b75ba000-b75bafff r-- 4096 /system/lib/libutils.so
b75bb000-b75bbfff rw- 4096 /system/lib/libutils.so
b75bc000-b760efff r-x 339968 /system/lib/libsurfaceflinger.so
b760f000-b760ffff --- 4096
b7610000-b7614fff r-- 20480 /system/lib/libsurfaceflinger.so
b7615000-b7615fff rw- 4096 /system/lib/libsurfaceflinger.so
b7616000-b7618fff r-x 12288 /system/lib/libstdc++.so
b7619000-b7619fff r-- 4096 /system/lib/libstdc++.so
b761a000-b761afff rw- 4096 /system/lib/libstdc++.so
b761b000-b7640fff r-x 155648 /system/lib/libm.so
b7641000-b7641fff r-- 4096 /system/lib/libm.so
b7642000-b7642fff rw- 4096 /system/lib/libm.so
b7643000-b764bfff r-x 36864 /system/lib/liblog.so
b764c000-b764cfff r-- 4096 /system/lib/liblog.so
b764d000-b764dfff rw- 4096 /system/lib/liblog.so
--->b764e000-b7662fff r-x 86016 /system/lib/libcutils.so
b7663000-b7663fff --- 4096
b7664000-b7664fff r-- 4096 /system/lib/libcutils.so
b7665000-b7665fff rw- 4096 /system/lib/libcutils.so
b7666000-b7748fff r-x 929792 /system/lib/libc.so
b7749000-b774bfff r-- 12288 /system/lib/libc.so
b774c000-b774efff rw- 12288 /system/lib/libc.so
b774f000-b7758fff rw- 40960
b7759000-b7792fff r-x 237568 /system/lib/libbinder.so
b7793000-b7797fff r-- 20480 /system/lib/libbinder.so
b7798000-b7798fff rw- 4096 /system/lib/libbinder.so
b7799000-b7799fff r-x 4096 /system/lib/libsigchain.so
b779a000-b779afff r-- 4096 /system/lib/libsigchain.so
b779b000-b779bfff rw- 4096 /system/lib/libsigchain.so
b779c000-b779cfff r-- 4096
b779d000-b779dfff rw- 4096
b779e000-b779efff r-- 4096
b779f000-b77a0fff rw- 8192
b77a1000-b77a2fff r-- 8192 [vvar]
b77a3000-b77a3fff r-x 4096 [vdso]
b77a4000-b77b9fff r-x 90112 /system/bin/linker
b77ba000-b77bafff r-- 4096
b77bb000-b77bbfff r-- 4096 /system/bin/linker
b77bc000-b77bcfff rw- 4096 /system/bin/linker
b77bd000-b77bdfff rw- 4096
bfa9d000-bfabdfff rw- 135168 [stack]
Error while reading log: No such file or directory
Error while reading log: No such file or directory
--- --- --- --- --- --- --- --- --- --- --- --- --- --- --- ---
pid: 22725, tid: 22732, name: Binder_1 >>> /system/bin/surfaceflinger <<<
eax fffffe00 ebx 00000003 ecx c0186201 edx b7150c08
esi b58240c0 edi b7150c08
xcs 00000073 xds 0000007b xes 0000007b xfs 00000000 xss 0000007b
eip b76df226 ebp b58240f0 esp b7150bb0 flags 00000292

backtrace:
#00 pc 00079226 /system/lib/libc.so (__ioctl+22)
#01 pc 000b82da /system/lib/libc.so (ioctl+42)
#02 pc 00021e24 /system/lib/libbinder.so
(android::IPCThreadState::talkWithDriver(bool)+212)
#03 pc 00022822 /system/lib/libbinder.so
(android::IPCThreadState::getAndExecuteCommand()+50)
#04 pc 000228df /system/lib/libbinder.so
(android::IPCThreadState::joinThreadPool(bool)+95)
#05 pc 0002be5e /system/lib/libbinder.so
(android::PoolThread::threadLoop()+46)
#06 pc 00016284 /system/lib/libutils.so
(android::Thread::_threadLoop(void*)+308)
#07 pc 00015892 /system/lib/libutils.so
(thread_data_t::trampoline(thread_data_t const*)+130)
#08 pc 0001f1b8 /system/lib/libc.so (__pthread_start(void*)+56)
#09 pc 00019cb9 /system/lib/libc.so (__start_thread+25)
#10 pc 00010816 /system/lib/libc.so (__bionic_clone+70)

stack:
b7150b70 b7757ea0
b7150b74 00000000
b7150b78 00000000
b7150b7c b7686f9e /system/lib/libc.so (pthread_once+30)
b7150b80 00000004
b7150b84 b6c07eb0
b7150b88 b6c07f74
b7150b8c 00000000
b7150b90 00000000
b7150b94 00000000
b7150b98 00000000
b7150b9c b774bfdc /system/lib/libc.so
b7150ba0 b76885c4 /system/lib/libc.so (__set_errno_internal+20)
b7150ba4 b5824120
b7150ba8 b76885b6 /system/lib/libc.so (__set_errno_internal+6)
b7150bac 00000029
#00 b7150bb0 00000003
b7150bb4 00000003
b7150bb8 b774bfdc /system/lib/libc.so
b7150bbc b771e2db /system/lib/libc.so (ioctl+43)
#01 b7150bc0 00000003
b7150bc4 c0186201
b7150bc8 b7150c08 [stack:22732]
b7150bcc b7654f03 /system/lib/libcutils.so (set_sched_policy+179)
b7150bd0 00000029
b7150bd4 00000000
b7150bd8 b7797e00 /system/lib/libbinder.so
b7150bdc b777ae25 /system/lib/libbinder.so
(android::IPCThreadState::talkWithDriver(bool)+213)
#02 b7150be0 00000003
b7150be4 c0186201
b7150be8 b7150c08 [stack:22732]
b7150bec 00000000
b7150bf0 00000000
b7150bf4 00000001
b7150bf8 b5824120
b7150bfc 01010c1b
b7150c00 00000029
b7150c04 00000000
b7150c08 00000000
b7150c0c 00000000
b7150c10 b5827200
b7150c14 00000100
b7150c18 00000000
b7150c1c b5827100
........ ........
#03 b7150c40 b58240c0
b7150c44 00000001
b7150c48 00323337
b7150c4c 2b9ac182
b7150c50 b5824120
b7150c54 00000004
b7150c58 b7654e59 /system/lib/libcutils.so (set_sched_policy+9)
b7150c5c b7797e00 /system/lib/libbinder.so
b7150c60 b58240c0
b7150c64 b5824120
b7150c68 b683622c
b7150c6c b777b8e0 /system/lib/libbinder.so
(android::IPCThreadState::joinThreadPool(bool)+96)
#04 b7150c70 b58240c0
b7150c74 00000001
b7150c78 b7685df9 /system/lib/libc.so (pthread_key_create+9)
b7150c7c b7797e00 /system/lib/libbinder.so
b7150c80 b58240c0
b7150c84 b6836220
b7150c88 b683622c
b7150c8c b777ab66 /system/lib/libbinder.so
(android::IPCThreadState::self()+182)
b7150c90 b58240c0
b7150c94 b777afd0 /system/lib/libbinder.so
(android::IPCThreadState::threadDestructor(void*))
b7150c98 b683622c
b7150c9c 015ab139
b7150ca0 b7797e00 /system/lib/libbinder.so
b7150ca4 00000001
b7150ca8 b6836220
b7150cac b7784e5f /system/lib/libbinder.so
(android::PoolThread::threadLoop()+47)
#05 b7150cb0 b58240c0
b7150cb4 00000001
b7150cb8 000058cc
b7150cbc 00680c14
b7150cc0 b75bae6c /system/lib/libutils.so
b7150cc4 b75bae6c /system/lib/libutils.so
b7150cc8 b683623c
b7150ccc b75ab285 /system/lib/libutils.so
(android::Thread::_threadLoop(void*)+309)
#06 b7150cd0 b6836220
b7150cd4 b683623c
b7150cd8 00000001
b7150cdc b6839100
b7150ce0 00000000
b7150ce4 00000000
b7150ce8 b75bae6c /system/lib/libutils.so
b7150cec 0174bfdc
b7150cf0 b6836220
b7150cf4 00000000
b7150cf8 b6836220
b7150cfc b68390e0
b7150d00 b6839100
b7150d04 00000000
b7150d08 b7654e59 /system/lib/libcutils.so (set_sched_policy+9)
b7150d0c b75bae6c /system/lib/libutils.so
........ ........
#07 b7150d20 b6836220
b7150d24 00000001
b7150d28 00000000
b7150d2c 00000022
b7150d30 ffffffff
b7150d34 00000000
b7150d38 b6854308
b7150d3c b6836220
b7150d40 b6854340
b7150d44 b7002000
b7150d48 00000000
b7150d4c b774bfdc /system/lib/libc.so
b7150d50 b6854300
b7150d54 b6854340
b7150d58 b6854308
b7150d5c b76851b9 /system/lib/libc.so (__pthread_start(void*)+57)
#08 b7150d60 b68390f0
b7150d64 00000000
b7150d68 00000000
b7150d6c 00000000
b7150d70 b774bfdc /system/lib/libc.so
b7150d74 bfabbda0 [stack]
b7150d78 b6854308
b7150d7c b767fcba /system/lib/libc.so (__start_thread+26)
#09 b7150d80 b6854300
b7150d84 00000000
b7150d88 00000000
b7150d8c 00000000
b7150d90 00000000
b7150d94 00000000
b7150d98 003d0f00
b7150d9c b7676817 /system/lib/libc.so (__bionic_clone+71)
#10 b7150da0 b7685180 /system/lib/libc.so (__pthread_start(void*))
b7150da4 b6854300
b7150da8 00000000
b7150dac 00000000
b7150db0 b7150db0 [stack:22732]
b7150db4 b6854300
b7150db8 00000016
b7150dbc 00000000
b7150dc0 00000000
b7150dc4 2b9ac182
b7150dc8 00000000
b7150dcc 00000000
b7150dd0 00000000
b7150dd4 00000000
b7150dd8 00000000
b7150ddc 00000000
cannot get siginfo for 22732: Invalid argument
--- --- --- --- --- --- --- --- --- --- --- --- --- --- --- ---
pid: 22725, tid: 22733, name: DispSync >>> /system/bin/surfaceflinger <<<
eax fffffe00 ebx b684c228 ecx 00000080 edx 00000000
esi 00000000 edi 00000001
xcs 00000073 xds 0000007b xes 0000007b xfs 00000000 xss 0000007b
eip b76769f2 ebp b75bae6c esp b67ffbac flags 00000246

backtrace:
#00 pc 000109f2 /system/lib/libc.so (syscall+34)
#01 pc 000fcdb7 [stack:22733]

stack:
b67ffb6c b76865e4 /system/lib/libc.so (pthread_mutex_unlock+20)
b67ffb70 00000000
b67ffb74 00000000
b67ffb78 00000000
b67ffb7c 00000000
b67ffb80 00000000
b67ffb84 00000000
b67ffb88 00000000
b67ffb8c 00000000
b67ffb90 00000000
b67ffb94 00000000
b67ffb98 00000000
b67ffb9c 00000000
b67ffba0 00000000
b67ffba4 00000000
b67ffba8 00000000
#00 b67ffbac b67ffdb8 [stack:22733]
#01 b67ffbb0 00000080
b67ffbb4 b684c228
b67ffbb8 b774bfdc /system/lib/libc.so
b67ffbbc b7684c45 /system/lib/libc.so (pthread_cond_wait+117)
b67ffbc0 000000f0
b67ffbc4 b684c228
b67ffbc8 00000080
b67ffbcc 00000000
b67ffbd0 00000000
b67ffbd4 00000001
b67ffbd8 b75bae6c /system/lib/libutils.so
b67ffbdc b75ab3f1 /system/lib/libutils.so (systemTime+65)
b67ffbe0 00000001
b67ffbe4 b67ffbf8 [stack:22733]
b67ffbe8 00000000
b67ffbec 00000016
cannot get siginfo for 22733: Invalid argument
--- --- --- --- --- --- --- --- --- --- --- --- --- --- --- ---
pid: 22725, tid: 22738, name: vsync_thread >>> /system/bin/surfaceflinger
<<<
eax fffffe00 ebx b68503ac ecx 00000080 edx 00000000
esi 00000000 edi 00000000
xcs 00000073 xds 0000007b xes 0000007b xfs 00000000 xss 0000007b
eip b76769f2 ebp b6839000 esp b5db5bec flags 00000246

backtrace:
#00 pc 000109f2 /system/lib/libc.so (syscall+34)
#01 pc 000fcdb7 [stack:22738]
#02 pc 00000019 <unknown>
#03 pc 00038fff <unknown>

stack:
b5db5bac b76865e4 /system/lib/libc.so (pthread_mutex_unlock+20)
b5db5bb0 b6803160
b5db5bb4 00000022
b5db5bb8 00000000
b5db5bbc b76efb9c /system/lib/libc.so (je_arena_malloc_small+268)
b5db5bc0 b6c00184
b5db5bc4 00000000
b5db5bc8 00000000
b5db5bcc 00000000
b5db5bd0 00000000
b5db5bd4 00000000
b5db5bd8 00000000
b5db5bdc 00000008
b5db5be0 b680300c
b5db5be4 00000000
b5db5be8 00000001
#00 b5db5bec b5db5db8 [stack:22738]
#01 b5db5bf0 00000080
b5db5bf4 b68503ac
b5db5bf8 b774bfdc /system/lib/libc.so
b5db5bfc b7684c45 /system/lib/libc.so (pthread_cond_wait+117)
b5db5c00 000000f0
b5db5c04 b68503ac
b5db5c08 00000080
b5db5c0c 00000000
b5db5c10 00000000
b5db5c14 00000000
b5db5c18 b6839000
b5db5c1c b76865e4 /system/lib/libc.so (pthread_mutex_unlock+20)
b5db5c20 b7757c20
b5db5c24 b6c001dc
b5db5c28 00000000
b5db5c2c 00000016
........ ........
#02 b6839008 000000e7
b683900c fd023000
b6839010 ffffffff
b6839014 ffffffff
b6839018 ffffffff
b683901c ffffffff
b6839020 ffffffff
b6839024 ffffffff
b6839028 1fffffff
b683902c 000000ff
b6839030 b7419308 /system/lib/libstlport.so
b6839034 00000001
b6839038 b74085c0 /system/lib/libstlport.so
b683903c 00000000
b6839040 b7419388 /system/lib/libstlport.so
b6839044 00000001
........ ........
#03 b6c001e4 b6c001e8
b6c001e8 b6c001e8
b6c001ec b6c001e8
b6c001f0 00000000
b6c001f4 00000160
b6c001f8 0000001c
b6c001fc 00000000
b6c00200 00000006
b6c00204 00000000
b6c00208 00000018
b6c0020c 00000000
b6c00210 00000007
b6c00214 00000000
b6c00218 00000000
b6c0021c 00000000
b6c00220 00000001
cannot get siginfo for 22738: Invalid argument
--- --- --- --- --- --- --- --- --- --- --- --- --- --- --- ---
pid: 22725, tid: 22739, name: Binder_2 >>> /system/bin/surfaceflinger <<<
eax fffffe00 ebx 00000003 ecx c0186201 edx b57ffc08
esi b68703c0 edi b57ffc08
xcs 00000073 xds 0000007b xes 0000007b xfs 00000000 xss 0000007b
eip b76df226 ebp b68703f0 esp b57ffbb0 flags 00000292

backtrace:
#00 pc 00079226 /system/lib/libc.so (__ioctl+22)
#01 pc 000b82da /system/lib/libc.so (ioctl+42)
#02 pc 00021e24 /system/lib/libbinder.so
(android::IPCThreadState::talkWithDriver(bool)+212)
#03 pc 00022822 /system/lib/libbinder.so
(android::IPCThreadState::getAndExecuteCommand()+50)
#04 pc 000228df /system/lib/libbinder.so
(android::IPCThreadState::joinThreadPool(bool)+95)
#05 pc 0002be5e /system/lib/libbinder.so
(android::PoolThread::threadLoop()+46)
#06 pc 00016284 /system/lib/libutils.so
(android::Thread::_threadLoop(void*)+308)
#07 pc 00015892 /system/lib/libutils.so
(thread_data_t::trampoline(thread_data_t const*)+130)
#08 pc 0001f1b8 /system/lib/libc.so (__pthread_start(void*)+56)
#09 pc 00019cb9 /system/lib/libc.so (__start_thread+25)
#10 pc 00010816 /system/lib/libc.so (__bionic_clone+70)

stack:
b57ffb70 b7757ea0
b57ffb74 00000000
b57ffb78 00000000
b57ffb7c b7686f9e /system/lib/libc.so (pthread_once+30)
b57ffb80 00000004
b57ffb84 b6c00430
b57ffb88 b6c004f4
b57ffb8c 00000000
b57ffb90 00000000
b57ffb94 00000000
b57ffb98 00000000
b57ffb9c b774bfdc /system/lib/libc.so
b57ffba0 b76885c4 /system/lib/libc.so (__set_errno_internal+20)
b57ffba4 b6870420
b57ffba8 b76885b6 /system/lib/libc.so (__set_errno_internal+6)
b57ffbac 00000029
#00 b57ffbb0 00000003
b57ffbb4 00000003
b57ffbb8 b774bfdc /system/lib/libc.so
b57ffbbc b771e2db /system/lib/libc.so (ioctl+43)
#01 b57ffbc0 00000003
b57ffbc4 c0186201
b57ffbc8 b57ffc08 [stack:22739]
b57ffbcc b7654f03 /system/lib/libcutils.so (set_sched_policy+179)
b57ffbd0 00000029
b57ffbd4 00000000
b57ffbd8 b7797e00 /system/lib/libbinder.so
b57ffbdc b777ae25 /system/lib/libbinder.so
(android::IPCThreadState::talkWithDriver(bool)+213)
#02 b57ffbe0 00000003
b57ffbe4 c0186201
b57ffbe8 b57ffc08 [stack:22739]
b57ffbec 00000000
b57ffbf0 00000000
b57ffbf4 00000001
b57ffbf8 b6870420
b57ffbfc 0101fc1b
b57ffc00 00000029
b57ffc04 00000000
b57ffc08 00000000
b57ffc0c 00000000
b57ffc10 b687a200
b57ffc14 00000100
b57ffc18 00000000
b57ffc1c b687a100
........ ........
#03 b57ffc40 b68703c0
b57ffc44 00000001
b57ffc48 00393337
b57ffc4c 2b9ac182
b57ffc50 b6870420
b57ffc54 00000004
b57ffc58 b7654e59 /system/lib/libcutils.so (set_sched_policy+9)
b57ffc5c b7797e00 /system/lib/libbinder.so
b57ffc60 b68703c0
b57ffc64 b6870420
b57ffc68 b582c04c
b57ffc6c b777b8e0 /system/lib/libbinder.so
(android::IPCThreadState::joinThreadPool(bool)+96)
#04 b57ffc70 b68703c0
b57ffc74 00000001
b57ffc78 00000000
b57ffc7c b7797e00 /system/lib/libbinder.so
b57ffc80 b68703c0
b57ffc84 b582c040
b57ffc88 b582c04c
b57ffc8c b777ab66 /system/lib/libbinder.so
(android::IPCThreadState::self()+182)
b57ffc90 b68703c0
b57ffc94 b582c040
b57ffc98 b582c04c
b57ffc9c 005ab139
b57ffca0 b7797e00 /system/lib/libbinder.so
b57ffca4 00000000
b57ffca8 b582c040
b57ffcac b7784e5f /system/lib/libbinder.so
(android::PoolThread::threadLoop()+47)
#05 b57ffcb0 b68703c0
b57ffcb4 00000000
b57ffcb8 000058d3
b57ffcbc 00680c14
b57ffcc0 b75bae6c /system/lib/libutils.so
b57ffcc4 b75bae6c /system/lib/libutils.so
b57ffcc8 b582c05c
b57ffccc b75ab285 /system/lib/libutils.so
(android::Thread::_threadLoop(void*)+309)
#06 b57ffcd0 b582c040
b57ffcd4 b582c05c
b57ffcd8 00000001
b57ffcdc b582d050
b57ffce0 00000000
b57ffce4 00000000
b57ffce8 b75bae6c /system/lib/libutils.so
b57ffcec 0174bfdc
b57ffcf0 b582c040
b57ffcf4 00000000
b57ffcf8 b582c040
b57ffcfc b582d030
b57ffd00 b582d050
b57ffd04 00000000
b57ffd08 b7654e59 /system/lib/libcutils.so (set_sched_policy+9)
b57ffd0c b75bae6c /system/lib/libutils.so
........ ........
#07 b57ffd20 b582c040
b57ffd24 00000001
b57ffd28 00000000
b57ffd2c 00000022
b57ffd30 ffffffff
b57ffd34 00000000
b57ffd38 b582e088
b57ffd3c b582c040
b57ffd40 b582e0c0
b57ffd44 b7000000
b57ffd48 00000000
b57ffd4c b774bfdc /system/lib/libc.so
b57ffd50 b582e080
b57ffd54 b582e0c0
b57ffd58 b582e088
b57ffd5c b76851b9 /system/lib/libc.so (__pthread_start(void*)+57)
#08 b57ffd60 b582d040
b57ffd64 00000000
b57ffd68 00000000
b57ffd6c 00000000
b57ffd70 b774bfdc /system/lib/libc.so
b57ffd74 b7150a00 [stack:22732]
b57ffd78 b582e088
b57ffd7c b767fcba /system/lib/libc.so (__start_thread+26)
#09 b57ffd80 b582e080
b57ffd84 00000000
b57ffd88 00000000
b57ffd8c 00000000
b57ffd90 00000000
b57ffd94 00000000
b57ffd98 003d0f00
b57ffd9c b7676817 /system/lib/libc.so (__bionic_clone+71)
#10 b57ffda0 b7685180 /system/lib/libc.so (__pthread_start(void*))
b57ffda4 b582e080
b57ffda8 00000000
b57ffdac 00000000
b57ffdb0 b57ffdb0 [stack:22739]
b57ffdb4 b582e080
b57ffdb8 00000016
b57ffdbc 00000000
b57ffdc0 00000000
b57ffdc4 2b9ac182
b57ffdc8 00000000
b57ffdcc 00000000
b57ffdd0 00000000
b57ffdd4 00000000
b57ffdd8 00000000
b57ffddc 00000000
cannot get siginfo for 22739: Invalid argument
Error while reading log: No such file or directory
Error while reading log: No such file or directory
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at http://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
JJ Meijer
2015-10-06 07:06:11 UTC
Permalink
Thanks for the help but your link does not work, I get a "404 - Unknown
commit object". I will check all the commits on framework/native.
Post by JJ Meijer
Post by JJ Meijer
After creating a giant mess of it all I started over..
Basically this is my configuration regarding HW / GPU, for now it would
be
Post by JJ Meijer
nice if SurfaceFlinger would fling a surface :o)
Sadly I'm ending up with a blanked screen and a flashing cursor. The
logs
Post by JJ Meijer
show SurfaceFlinger is crash-looping becouse of the 'no suitable
EGLConfig
Post by JJ Meijer
found, giving up' error. What could I be missing?
http://git.android-x86.org/?p=platform/frameworks/native.git;a=commitdiff;h=39aa8695464e496ec4f6d22e9af54457bcfdf4ae
Also check other opengl fix under frameworks/native
of lollipop-x86 branch.
--
Chih-Wei
Android-x86 project
http://www.android-x86.org
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at http://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
JJ Meijer
2015-10-06 07:27:03 UTC
Permalink
Thanks for the help but your link does not work, I get a "404 - Unknown
commit object". I will check all the commits on framework/native.

For reverence I also compiled the full Android-x86 project and I just
noticed that I also need to boot with androidboot.hardware=drm to get to
the logo, at which it will be stuck.
Post by JJ Meijer
Post by JJ Meijer
After creating a giant mess of it all I started over..
Basically this is my configuration regarding HW / GPU, for now it would
be
Post by JJ Meijer
nice if SurfaceFlinger would fling a surface :o)
Sadly I'm ending up with a blanked screen and a flashing cursor. The
logs
Post by JJ Meijer
show SurfaceFlinger is crash-looping becouse of the 'no suitable
EGLConfig
Post by JJ Meijer
found, giving up' error. What could I be missing?
http://git.android-x86.org/?p=platform/frameworks/native.git;a=commitdiff;h=39aa8695464e496ec4f6d22e9af54457bcfdf4ae
Also check other opengl fix under frameworks/native
of lollipop-x86 branch.
--
Chih-Wei
Android-x86 project
http://www.android-x86.org
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at http://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
JJ Meijer
2015-10-06 08:15:29 UTC
Permalink
Thanks for that! I noticed they added:
ifeq ($(BOARD_EGL_WORKAROUND_BUG_10194508),true)
LOCAL_CFLAGS += -DWORKAROUND_BUG_10194508=1
endif

So I thought it would be cleaner just to add it to the boardconfig.

I was a little lazy and just copied your init.sh and little bit more basic
version of your initrd script. I will look into that further :)

Also I noticed you added some nice consolemanager functionality to
Surfaceflinger, should I look into this to?
Post by JJ Meijer
Thanks for the help but your link does not work, I get a "404 - Unknown
commit object". I will check all the commits on framework/native.
Then refer to the mirror
https://github.com/pstglia/frameworks-native/commit/39aa8695464e496ec4f6d22e9af54457bcfdf4ae
Post by JJ Meijer
For reverence I also compiled the full Android-x86 project and I just
noticed that I also need to boot with androidboot.hardware=drm to get to
the
Post by JJ Meijer
logo, at which it will be stuck.
Actually android-x86 chooses the hal at runtime.
Refer to /system/etc/init.sh
to understand how it works.
--
Chih-Wei
Android-x86 project
http://www.android-x86.org
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at http://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
JJ Meijer
2015-10-06 20:15:11 UTC
Permalink
I finally got to the boot animation and as far as I can tell with HW
accelleration. Only with androidboot.hardware = drm, but this creates other
problems because it can't find the .rc / fstab files any more.

At the moment only without CONSOLE_MANAGER because Surfaceflinger cannot
access tty (and after chmod it can't create VT) so I need to change the
permissions somewhere.
Post by JJ Meijer
ifeq ($(BOARD_EGL_WORKAROUND_BUG_10194508),true)
LOCAL_CFLAGS += -DWORKAROUND_BUG_10194508=1
endif
So I thought it would be cleaner just to add it to the boardconfig.
OK, agree.
Post by JJ Meijer
I was a little lazy and just copied your init.sh and little bit more
basic
Post by JJ Meijer
version of your initrd script. I will look into that further :)
You don't need the whole init.sh,
but you have to set the correct name for each hal.
Post by JJ Meijer
Also I noticed you added some nice consolemanager functionality to
Surfaceflinger, should I look into this to?
Depends on you.
It's good for debugging.
--
Chih-Wei
Android-x86 project
http://www.android-x86.org
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at http://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
JJ Meijer
2015-10-06 21:05:12 UTC
Permalink
I'm setting ro.hardware.gralloc=drm at the moment directly in init.sh but
it doesn't seem to have effect. As soon as I have Surfaceflinger running as
root I will check.

Also with the original Android-x86 build I have to set
boardconfig.hardware=drm. Renaming gralloc.drm.so to
gralloc.$(TARGET_BOARD_PLATFORM).so seems an easy fix for now.
Post by JJ Meijer
I finally got to the boot animation and as far as I can tell with HW
accelleration. Only with androidboot.hardware = drm, but this creates
other
Post by JJ Meijer
problems because it can't find the .rc / fstab files any more.
As I've said, you have to set the hal property correctly.
(i.e., ro.hardware.gralloc=drm)
Do not change androidboot.hardware.
It must be set to your target name.
(unless your target name is just drm)
Post by JJ Meijer
At the moment only without CONSOLE_MANAGER because Surfaceflinger cannot
access tty (and after chmod it can't create VT) so I need to change the
permissions somewhere.
Surfaceflinger has to be run with root permission.
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at http://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
JJ Meijer
2015-10-06 21:50:06 UTC
Permalink
It looks like early-boot is not working any more, readprops is not
recognized as a function? All props are written to the file by init.sh but
they are not read back. If I set ro.hardware.gralloc=drm in build.prop
manually everything is working as expected.

on early-boot
readprops /$platform.prop
Post by JJ Meijer
I finally got to the boot animation and as far as I can tell with HW
accelleration. Only with androidboot.hardware = drm, but this creates
other
Post by JJ Meijer
problems because it can't find the .rc / fstab files any more.
As I've said, you have to set the hal property correctly.
(i.e., ro.hardware.gralloc=drm)
Do not change androidboot.hardware.
It must be set to your target name.
(unless your target name is just drm)
Post by JJ Meijer
At the moment only without CONSOLE_MANAGER because Surfaceflinger cannot
access tty (and after chmod it can't create VT) so I need to change the
permissions somewhere.
Surfaceflinger has to be run with root permission.
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at http://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
JJ Meijer
2015-10-07 11:02:10 UTC
Permalink
Thank! But I realize there is still a long way to go. For instance de VM
won't start because of wrong parameters and it cannot mount rootfs. At
least now I have a boot animation and console for debugging :)

My goal is mainly to learn what is minimally needed to get Android working
on my tablet. Also it would be nice to be able to use the same source for
my Samsung Note 4.

Of course merging or just merge the mods into Android-x86 would be easier
but that is no fun :). So I will keep on struggling and all help is very
welcome!
Post by JJ Meijer
It looks like early-boot is not working any more, readprops is not
recognized as a function? All props are written to the file by init.sh
but
Post by JJ Meijer
they are not read back. If I set ro.hardware.gralloc=drm in build.prop
manually everything is working as expected.
on early-boot
readprops /$platform.prop
Fine. You are on the path to port android-x86. :)
Now you should realize these functions are not
born-in in AOSP codebase, but added by this project.
Read the lollipop-x86 patches in system/core to
understand how it works.
Or simpler, just merge the lollipop-x86 branch with cm-12.1
and resolve the conflict if you can.
--
Chih-Wei
Android-x86 project
http://www.android-x86.org
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at http://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
JJ Meijer
2015-10-07 23:03:02 UTC
Permalink
Ok, I forgot to make android root a mount point and for some reason I can't
mount data as a tmpfs. But at least I'm past the boot animation and now
it's crashing during app optimizing, maybe a SELinux thing...

I/SystemServer( 3997): Entered the Android system server!
I/ServiceManager( 3765): Waiting for service batterystats...
V/Fingerprint-JNI( 3997): FingerprintManager JNI ready.
I/ ( 3997): System server: starting sensor init.
D/SensorService( 3997): nuSensorService starting...
E/SensorService( 3997): couldn't load sensors module (No such file or
directory)
I/ ( 3997): System server: sensor init done.
I/SystemServiceManager( 3997): Starting com.android.server.pm.Installer
I/Installer( 3997): Waiting for installd to be ready.
I/InstallerConnection( 3997): connecting...
I/InstallerConnection( 3997): disconnecting...
E/InstallerConnection( 3997): connection failed
I/SystemServiceManager( 3997): Starting
com.android.server.am.ActivityManagerService$Lifecycle
I/XXXXXX ( 3997): choosing minFree values for 32 Bit
I/XXXXXX ( 3997): choosing minFree values for 32 Bit
I/XXXXXX ( 3997): choosing minFree values for 32 Bit
I/XXXXXX ( 3997): choosing minFree values for 32 Bit
I/XXXXXX ( 3997): choosing minFree values for 32 Bit
I/XXXXXX ( 3997): choosing minFree values for 32 Bit
I/ActivityManager( 3997): Memory class: 192
I/AppOps ( 3997): No existing app ops /data/system/appops.xml; starting
empty
I/IntentFirewall( 3997): Read new rules (A:0 B:0 S:0)
D/AppOps ( 3997): AppOpsService published
I/SystemServiceManager( 3997): Starting
com.android.server.power.PowerManagerService
W/libsuspend( 3997): Error writing 'on' to /sys/power/state: Invalid
argument
I/libsuspend( 3997): Selected wakeup count
I/SystemServiceManager( 3997): Starting
com.android.server.display.DisplayManagerService
I/SystemServiceManager( 3997): Starting phase 100
I/DisplayManagerService( 3997): Display device added:
DisplayDeviceInfo{"Built-in Screen": uniqueId="local:0", 1920 x 1200,
60.000004 fps, supportedRefreshRates [60.000004], density 240, 221.0 x
217.0 dpi, appVsyncOff 0, presDeadline 17666666, touch INTERNAL, rotation
0, type BUILT_IN, state UNKNOWN, FLAG_DEFAULT_DISPLAY,
FLAG_ROTATES_WITH_CONTENT, FLAG_SECURE, FLAG_SUPPORTS_PROTECTED_BUFFERS}
I/SystemServer( 3997): Package Manager
W/SELinuxMMAC( 3997): Error opening /data/system/seapp_hash. Assuming first
boot.
W/PackageManager( 3997): No security bridge jar found, using default
W/SystemConfig( 3997): No directory /system/etc/sysconfig, skipping
D/SELinuxMMAC( 3997): Using policy file
/system/etc/security/mac_permissions.xml
D/PackageManager( 3997): No files in app dir /vendor/overlay
I/PackageManager( 3997): SELinux relabeling of cyanogenmod.platform issued.
I/InstallerConnection( 3997): connecting...
I/InstallerConnection( 3997): disconnecting...
E/InstallerConnection( 3997): connection failed
W/PackageManager( 3997): Failed to parse /system/framework/x86: Missing
base APK in /system/framework/x86
I/PackageManager( 3997): SELinux relabeling of org.cyanogenmod.audiofx
issued.
I/InstallerConnection( 3997): connecting...
I/InstallerConnection( 3997): disconnecting...
E/InstallerConnection( 3997): connection failed
I/PackageManager( 3997): SELinux relabeling of com.android.backupconfirm
issued.
I/InstallerConnection( 3997): connecting...
I/InstallerConnection( 3997): disconnecting...
E/InstallerConnection( 3997): connection failed
I/PackageManager( 3997): SELinux relabeling of com.cyanogenmod.account
issued.
I/InstallerConnection( 3997): connecting...
I/InstallerConnection( 3997): disconnecting...
E/InstallerConnection( 3997): connection failed
I/PackageManager( 3997): SELinux relabeling of org.cyanogenmod.cmsettings
issued.
I/InstallerConnection( 3997): connecting...
I/InstallerConnection( 3997): disconnecting...
E/InstallerConnection( 3997): connection failed
I/PackageManager( 3997): SELinux relabeling of com.cyanogenmod.updater
issued.
I/InstallerConnection( 3997): connecting...
I/InstallerConnection( 3997): disconnecting...
E/InstallerConnection( 3997): connection failed

..........................
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at http://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
JJ Meijer
2015-10-06 20:23:04 UTC
Permalink
I finally got to the boot animation and as far as I can tell with HW
accelleration. At the moment only without CONSOLE_MANAGER because
Surfaceflinger cannot access tty (and after chmod it can't create VT) so I
need to change the permissions somewhere. So it's a bit hard to debug why
it's stuck at the moment :o)


It seems gralloc.drm.so is named wrong, I needed to change it to
gralloc.$(TARGET_BOARD_PLATFORM).so. Could this be a bug?
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at http://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
JJ Meijer
2015-10-08 23:34:42 UTC
Permalink
I forgot to overlay a suitable storage_list.xml, I'm booting into Android
now.

If anybody is interested in testing I can upload an image (Bay Trail only).
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at http://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
György Pejović
2015-10-09 14:01:51 UTC
Permalink
I would like test your ISO
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at http://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
JJ Meijer
2015-10-14 10:57:38 UTC
Permalink
I will but first I'll try to get basic functionality (WiFi) which is taking
me a bit longer than expected.

Working:
Multitouch
Audio
HW acceleration
Home + Power button
CM Gapps x86
Backlight control

Not working
WiFi
Vol_keys (detected by platform gpio-keys but no output)
Suspend
sensors

WPA_Supplicant is working with private_lib when I use wpa_cli manually (I
can scan and view scan_results). If I enable it from Android it just keeps
scanning. I'm using stock hardware_legacy wifi.c with hardcoded module
path. Anybody any idea what could be wrong? If needed I will generate some
logs.
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at http://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
JJ Meijer
2015-10-14 23:26:55 UTC
Permalink
I upoaded the image but you will have to bootable stick yourself for now.
It's expecting the system.img and ramdisk.img with a dir called data on
/dev/sda2 (ext4). It will go with the Android-x86 4.0.9 (5.1.1 r1) kernel
with androidboot.hardware=omni

https://drive.google.com/open?id=0B9vJ9JSuyPijaVNZZHNuaDJDWUE
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at http://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
György Pejović
2015-10-18 11:22:03 UTC
Permalink
Ive tried it the way youve explained but its not working for me,only the boot animation plays over and over.
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at http://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
JJ Meijer
2015-10-19 23:14:02 UTC
Permalink
I upoaded a new image. This time it is a disk image so you can easily put
it on a USB drive with *dd* or win32diskimager. Also the device and
location are now configurable from Grub.

Working
Multitouch
WiFi (will stop working if you disable it, will fail to reload
firmware/module?)
sensors (not every boot for some reason I don't understand yet)
backlight
H/W acceleration
audio
Home+Power buttons
Battery status
Media players ( Kodi, VLC, MX, ..)
Youtube ((within browser) with software rendering but unsupported YV12
format?)
Logitech HID++ devices

Not working
Bluetooth
Camera
Volume buttons
Suspend
Some apps ( Gallery, AnTuTu, .. )


Using HAL, graphics and kernel from Android x86. Open Gapps mini x86
included.

https://drive.google.com/open?id=0B9vJ9JSuyPijaVNZZHNuaDJDWUE
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at http://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
Karol Putra
2015-10-20 10:59:31 UTC
Permalink
Hey man. I'm happy to see that someone is porting CM to Android-x86. Good luck with the work. I'll try too give your builds a test in free time.

Have you heard about RemixOS? There are rom's released for Nexus 9 and 10 - these could be ported and would be better than CM - we'd have a true PC UI. Even better thing would be a combo of CM-RemixOS-Android-x86.
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at http://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
Oussama Lahmidi
2015-10-27 13:07:43 UTC
Permalink
Me too i want to try it on my pc I think it's much better than CyanogenMod
because it's designed for computers.
Post by Karol Putra
Hey man. I'm happy to see that someone is porting CM to Android-x86. Good
luck with the work. I'll try too give your builds a test in free time.
Have you heard about RemixOS? There are rom's released for Nexus 9 and 10
- these could be ported and would be better than CM - we'd have a true PC
UI. Even better thing would be a combo of CM-RemixOS-Android-x86.
--
You received this message because you are subscribed to the Google Groups
"Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an
Visit this group at http://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at http://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
Oussama Lahmidi
2015-10-27 16:32:16 UTC
Permalink
Thanks a lot for the build. I'm sorry I'm new to this, I put the image on
my usb using Win32diskimager, it created two partitions on my usb but when
I boot my computer from it It gives me a black screen and nothing happen.
Did I do something wrong ?
Post by JJ Meijer
I upoaded a new image. This time it is a disk image so you can easily put
it on a USB drive with *dd* or win32diskimager. Also the device and
location are now configurable from Grub.
Working
Multitouch
WiFi (will stop working if you disable it, will fail to reload
firmware/module?)
sensors (not every boot for some reason I don't understand yet)
backlight
H/W acceleration
audio
Home+Power buttons
Battery status
Media players ( Kodi, VLC, MX, ..)
Youtube ((within browser) with software rendering but unsupported YV12
format?)
Logitech HID++ devices
Not working
Bluetooth
Camera
Volume buttons
Suspend
Some apps ( Gallery, AnTuTu, .. )
Using HAL, graphics and kernel from Android x86. Open Gapps mini x86
included.
https://drive.google.com/open?id=0B9vJ9JSuyPijaVNZZHNuaDJDWUE
--
You received this message because you are subscribed to the Google Groups
"Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an
Visit this group at http://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at http://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
JJ Meijer
2015-10-28 19:36:25 UTC
Permalink
I want to take a look for you but I need some more information. Also I can
take a look at this mod but first I want to solve the remaining hardware
issues.
Post by Oussama Lahmidi
Thanks a lot for the build. I'm sorry I'm new to this, I put the image on
my usb using Win32diskimager, it created two partitions on my usb but when
I boot my computer from it It gives me a black screen and nothing happen.
Did I do something wrong ?
Post by JJ Meijer
I upoaded a new image. This time it is a disk image so you can easily put
it on a USB drive with *dd* or win32diskimager. Also the device and
location are now configurable from Grub.
Working
Multitouch
WiFi (will stop working if you disable it, will fail to reload
firmware/module?)
sensors (not every boot for some reason I don't understand yet)
backlight
H/W acceleration
audio
Home+Power buttons
Battery status
Media players ( Kodi, VLC, MX, ..)
Youtube ((within browser) with software rendering but unsupported YV12
format?)
Logitech HID++ devices
Not working
Bluetooth
Camera
Volume buttons
Suspend
Some apps ( Gallery, AnTuTu, .. )
Using HAL, graphics and kernel from Android x86. Open Gapps mini x86
included.
https://drive.google.com/open?id=0B9vJ9JSuyPijaVNZZHNuaDJDWUE
--
You received this message because you are subscribed to the Google Groups
"Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an
<javascript:>.
Visit this group at http://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at http://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
JJ Meijer
2015-10-28 19:36:38 UTC
Permalink
I want to take a look for you but I need some more information. Also I can
take a look at this mod but first I want to solve the remaining hardware
issues.
Post by Oussama Lahmidi
Thanks a lot for the build. I'm sorry I'm new to this, I put the image on
my usb using Win32diskimager, it created two partitions on my usb but when
I boot my computer from it It gives me a black screen and nothing happen.
Did I do something wrong ?
Post by JJ Meijer
I upoaded a new image. This time it is a disk image so you can easily put
it on a USB drive with *dd* or win32diskimager. Also the device and
location are now configurable from Grub.
Working
Multitouch
WiFi (will stop working if you disable it, will fail to reload
firmware/module?)
sensors (not every boot for some reason I don't understand yet)
backlight
H/W acceleration
audio
Home+Power buttons
Battery status
Media players ( Kodi, VLC, MX, ..)
Youtube ((within browser) with software rendering but unsupported YV12
format?)
Logitech HID++ devices
Not working
Bluetooth
Camera
Volume buttons
Suspend
Some apps ( Gallery, AnTuTu, .. )
Using HAL, graphics and kernel from Android x86. Open Gapps mini x86
included.
https://drive.google.com/open?id=0B9vJ9JSuyPijaVNZZHNuaDJDWUE
--
You received this message because you are subscribed to the Google Groups
"Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an
<javascript:>.
Visit this group at http://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at http://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
Karol Putra
2015-10-30 23:54:52 UTC
Permalink
Android RemixOS 2.0 for Nexus 10 - you can extract all files you need from this image - https://drive.google.com/file/d/0B6QbFTXmsda3VDhCMUU3OVg1S2s/view

Details here: https://forum.jide.com/index.php?p=%2Fdiscussion%2F601%2Fnexus-10-rom-available-here#Head
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at http://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
György Pejović
2015-12-21 18:29:06 UTC
Permalink
<Loading Image...>
I've tried to port cm 12.1 to x86 aswell. Now this is the problem what you
can see on this picture. How can i fix this problem?
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
Supercilious Dude
2015-12-21 18:41:32 UTC
Permalink
Its pretty clear from the screenshot that you ran out of disk space.
Enlarge your partition or migrate it to a bigger drive.
Post by György Pejović
<https://lh3.googleusercontent.com/-PJ5PXi_-mTI/VnhDX_NZoUI/AAAAAAAAAMU/9_3lanEZ5GE/s1600/K%25C3%25A9perny%25C5%2591k%25C3%25A9p%2B%25E2%2580%2593%2B2015-12-21%2B17%253A19%253A09.png>
I've tried to port cm 12.1 to x86 aswell. Now this is the problem what you
can see on this picture. How can i fix this problem?
--
You received this message because you are subscribed to the Google Groups
"Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
György Pejović
2015-12-21 19:24:04 UTC
Permalink
I have 263.9 GB free disk space on my partition

2015. december 21., hétfő 18:42:02 UTC időpontban Supercilious Dude a
Post by Supercilious Dude
Its pretty clear from the screenshot that you ran out of disk space.
Enlarge your partition or migrate it to a bigger drive.
Post by György Pejović
<https://lh3.googleusercontent.com/-PJ5PXi_-mTI/VnhDX_NZoUI/AAAAAAAAAMU/9_3lanEZ5GE/s1600/K%25C3%25A9perny%25C5%2591k%25C3%25A9p%2B%25E2%2580%2593%2B2015-12-21%2B17%253A19%253A09.png>
I've tried to port cm 12.1 to x86 aswell. Now this is the problem what
you can see on this picture. How can i fix this problem?
--
You received this message because you are subscribed to the Google Groups
"Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an
<javascript:>.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
JJ Meijer
2015-12-21 21:28:56 UTC
Permalink
You should enlarge the system partition from your device config, it's a fixed size defined over there.

Also, you could just try my latest cm builds from here: https://groups.google.com/forum/m/#!topic/android-x86/kJfT5eKJ-RA there has been a lot of improvement since this thread.
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
JJ Meijer
2015-12-22 07:23:35 UTC
Permalink
Thanks for pointing out this nice patch! Maybe it would be a nice addition to make the spare space configurable.
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
György Pejović
2015-12-22 16:50:30 UTC
Permalink
Thanks for the help!
I made a device tree from android-x86's device tree and I put
device/generic/android_x86 but sometimes the compiler used the standard
aosp BoardConfig.mk (BOARD_SYSTEMIMAGE_PARTITION_SIZE := 576716800) - and i
don't know why?!


JJ Meijer, i will try that.
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
Shubham Karande
2015-12-22 12:49:10 UTC
Permalink
Post by JJ Meijer
Hello everybody,
I started a project to learn something more about Linux and Android so I started to port the Cyanogen project to my HP Omni 10 (Baytrail) tablet. Many thanks to the Android-x86 project I had relatively quickly my tablet booting and change_rooting into Android.
At the moment surfaceflinger is crashing because of a missing EGLConfig (No suitable EGLConfig found). Hints in how this config should be supplied are very welcome!
I will let you know how it goes... :)
Kind regard, JJ
Glad to see someone porting CM 12.1 to x86. Can you make a build with BCM43142 wifi adapter support?I tried making a build but my PSU overheated and crashed.I was trying to boot my Dell Inspirion 3148 but couldn't get wifi working because Android x86 doesn't support Broadcom cards. Thanks a lot!
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
JJ Meijer
2015-12-26 21:04:22 UTC
Permalink
Hello everybody,

There are some new builds available.

-Last time I seem to have forgotten to add the firmware so the latest
package is in now, should add a lot of HW support.
-Thanks to holzingerm Marvell WiFi chips are supported now.
-Thanks to cwm9 MS Surface 3 accessories is supported now.
-The init scripts was updated to make it drop in replaceable with
Android-x86, just change androidboot.hardware=omni
-Thanks to Mauso MESA 10.6.X is used to make Google Maps not freeze, also
nice AnTuTu scores.
-Thanks to Android-x86 and the CM team for most of the rest :).

Also there is an EXPERIMENTAL Intel UFO gen7 build available.

Still working on
-Bluetooth
-Camera
-Youtube HD

https://drive.google.com/open?id=0B9vJ9JSuyPijaVNZZHNuaDJDWUE
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
Povilas Staniulis
2015-12-26 21:24:01 UTC
Permalink
Source ?
Post by JJ Meijer
Hello everybody,
There are some new builds available.
-Last time I seem to have forgotten to add the firmware so the latest
package is in now, should add a lot of HW support.
-Thanks to holzingerm Marvell WiFi chips are supported now.
-Thanks to cwm9 MS Surface 3 accessories is supported now.
-The init scripts was updated to make it drop in replaceable with
Android-x86, just change androidboot.hardware=omni
-Thanks to Mauso MESA 10.6.X is used to make Google Maps not freeze,
also nice AnTuTu scores.
-Thanks to Android-x86 and the CM team for most of the rest :).
Also there is an EXPERIMENTAL Intel UFO gen7 build available.
Still working on
-Bluetooth
-Camera
-Youtube HD
https://drive.google.com/open?id=0B9vJ9JSuyPijaVNZZHNuaDJDWUE
--
You received this message because you are subscribed to the Google
Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
JJ Meijer
2015-12-26 21:29:15 UTC
Permalink
You can find my manifests on my Google Drive. If you need something else
just let me know.
Post by Povilas Staniulis
Source ?
Hello everybody,
There are some new builds available.
-Last time I seem to have forgotten to add the firmware so the latest
package is in now, should add a lot of HW support.
-Thanks to holzingerm Marvell WiFi chips are supported now.
-Thanks to cwm9 MS Surface 3 accessories is supported now.
-The init scripts was updated to make it drop in replaceable with
Android-x86, just change androidboot.hardware=omni
-Thanks to Mauso MESA 10.6.X is used to make Google Maps not freeze, also
nice AnTuTu scores.
-Thanks to Android-x86 and the CM team for most of the rest :).
Also there is an EXPERIMENTAL Intel UFO gen7 build available.
Still working on
-Bluetooth
-Camera
-Youtube HD
https://drive.google.com/open?id=0B9vJ9JSuyPijaVNZZHNuaDJDWUE
--
You received this message because you are subscribed to the Google Groups
"Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an
<javascript:>.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
paul17
2015-12-27 06:45:59 UTC
Permalink
I guess HD Video playback is somewhat related to the Marshmallow source.
Because when i was on 5.1 (Native android-x86 or CM12,1) i wasn't able to
play any HD videos (local or YouTube). On Marshmallow (20151202 or the
latest test build) i was able to play HD Videos on both local video player
and YouTube. I know it isn't easy porting CM to x86. But my guess is that
HD Video playback might work on CM13. And the camera problem might be
related to kernel 4.1.15. Because camera was working on native android-x86
5.1.1 which was on kernel 4.0.9.
Just a guess, if that might help you in any way

Requesting an iso (directly installable) file for CM12.1 (because just
copying the CM12.1 files is not reliable and it sometimes doesn't boot).
Thanks a lot :)
Post by JJ Meijer
Hello everybody,
There are some new builds available.
-Last time I seem to have forgotten to add the firmware so the latest
package is in now, should add a lot of HW support.
-Thanks to holzingerm Marvell WiFi chips are supported now.
-Thanks to cwm9 MS Surface 3 accessories is supported now.
-The init scripts was updated to make it drop in replaceable with
Android-x86, just change androidboot.hardware=omni
-Thanks to Mauso MESA 10.6.X is used to make Google Maps not freeze, also
nice AnTuTu scores.
-Thanks to Android-x86 and the CM team for most of the rest :).
Also there is an EXPERIMENTAL Intel UFO gen7 build available.
Still working on
-Bluetooth
-Camera
-Youtube HD
https://drive.google.com/open?id=0B9vJ9JSuyPijaVNZZHNuaDJDWUE
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
JJ Meijer
2015-12-28 01:09:22 UTC
Permalink
A new build is up, it includes full language support and RTL8723BS support
from Hadess.

https://drive.google.com/folderview?id=0B9vJ9JSuyPijWTRpU2VLUkVhYkE&usp=drive_web#list

At the moment I'm still struggling with Bluetooth and camera. Also trying
to build CM13.0 but having some issues building cmsdk.
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
paul17
2015-12-28 12:08:10 UTC
Permalink
Where is the new build? I can't see any new builds in the link
Post by JJ Meijer
A new build is up, it includes full language support and RTL8723BS support
from Hadess.
https://drive.google.com/folderview?id=0B9vJ9JSuyPijWTRpU2VLUkVhYkE&usp=drive_web#list
At the moment I'm still struggling with Bluetooth and camera. Also trying
to build CM13.0 but having some issues building cmsdk.
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
Antony Stone
2015-12-28 12:17:35 UTC
Permalink
Post by paul17
Where is the new build? I can't see any new builds in the link
Post by JJ Meijer
A new build is up, it includes full language support and RTL8723BS
support from Hadess.
https://drive.google.com/folderview?id=0B9vJ9JSuyPijWTRpU2VLUkVhYkE&usp=d
rive_web#list
I see 5 tgz files there, one dated 26th December, and one within the past 24
hours (labelled "4:43pm" but with no indication of timezone).


Regards,


Antony.
--
"Linux is going to be part of the future. It's going to be like Unix was."

- Peter Moore, Asia-Pacific general manager, Microsoft

Please reply to the list;
please *don't* CC me.
youling 257
2015-12-28 04:35:54 UTC
Permalink
this my grub.cfg
set DIR=/cm12.1
search --set=root --file /cm12.1/kernel
linuxefi $DIR/kernel quiet root=/dev/ram0 androidboot.hardware=omni
DEV=/dev/mmcblk0p3 DIR=$DIR
initrdefi $DIR/initrd.img
CM12.1-x86_kernel-4.1.15_mesa-10.6.X_intel-drm_cgapps_img.tar.gz it can
work

butthe latest CM12.1-x86_kernel-4.1.15_mesa-10.6.X_cgapps_int.tar.gzit
can not work.
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
youling 257
2015-12-28 05:00:55 UTC
Permalink
This CM12.1-x86_kernel-4.1.15_mesa-10.6.X_intel-drm_cgapps_img.tar.gz
<Loading Image...>

<Loading Image...>
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
youling 257
2015-12-28 05:06:49 UTC
Permalink
the latest CM12.1-x86_kernel-4.1.15_mesa-10.6.X_cgapps_int.tar.gz
<Loading Image...>
the latest CM12.1-x86_kernel-4.1.15_mesa-10.6.X_cgapps_int.tar.gz
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
JJ Meijer
2015-12-28 09:29:09 UTC
Permalink
Hi Youling,

Please change DIR= to SRC= than it should work.
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
Christian P
2015-12-28 12:44:00 UTC
Permalink
Just a Question, how to create an bootable usb stick with the .tar file
under Windows?
Post by JJ Meijer
Hello everybody,
I started a project to learn something more about Linux and Android so I
started to port the Cyanogen project to my HP Omni 10 (Baytrail) tablet.
Many thanks to the Android-x86 project I had relatively quickly my tablet
booting and change_rooting into Android.
At the moment surfaceflinger is crashing because of a missing EGLConfig
(No suitable EGLConfig found). Hints in how this config should be supplied
are very welcome!
I will let you know how it goes... :)
Kind regard, JJ
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
paul17
2015-12-28 13:21:18 UTC
Permalink
You cannot. You have to extract the tar file then copy it's contents to the
partition where you had previously installed android-x86( create a
directory named cm12.1). Then, create a boot entry in GRUB with the same
lines as that of android-x86, the only change you have to make in these
lines is to change androidboot.hardware=android_x86 to
androidboot.hardware=omni. Also change the SRC= value to SRC=/cm12.1
Post by Christian P
Just a Question, how to create an bootable usb stick with the .tar file
under Windows?
Post by JJ Meijer
Hello everybody,
I started a project to learn something more about Linux and Android so I
started to port the Cyanogen project to my HP Omni 10 (Baytrail) tablet.
Many thanks to the Android-x86 project I had relatively quickly my tablet
booting and change_rooting into Android.
At the moment surfaceflinger is crashing because of a missing EGLConfig
(No suitable EGLConfig found). Hints in how this config should be supplied
are very welcome!
I will let you know how it goes... :)
Kind regard, JJ
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
youling 257
2015-12-28 18:11:24 UTC
Permalink
yesthe latest cm12.1need ext4 Partition Main directoryand mount loop
system.img systemcp to ext4 Main directory 's system folder
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
György Pejović
2015-12-28 21:25:29 UTC
Permalink
Hi guys!

First time I have a problem with hardware/drm_gralloc/drm_gralloc.h
/home/cng/cm12.1/out/target/product/x86/obj/SHARED_LIBRARIES/libgralloc_drm_intermediates/import_includes
target C: libgralloc_drm <= hardware/drm_gralloc/gralloc_drm.c
'HAL_PIXEL_FORMAT_DRM_NV12' undeclared (first use in this function)
^
hardware/drm_gralloc/gralloc_drm.h:75:14: note: each undeclared identifier
is reported only once for each function it appears in
hardware/drm_gralloc/gralloc_drm.h: In function
'HAL_PIXEL_FORMAT_DRM_NV12' undeclared (first use in this function)
^
make: ***
[/home/cng/cm12.1/out/target/product/x86/obj/SHARED_LIBRARIES/libgralloc_drm_intermediates/gralloc_drm.o]
Error 1
#### make failed to build some targets (40:50 (mm:ss)) ####
After I added this line: *#include "gralloc_drm_formats.h"* in the
drm_gralloc.h


#ifndef _GRALLOC_DRM_H_
#define _GRALLOC_DRM_H_
#include <hardware/gralloc.h>
#include "gralloc_drm_formats.h"
#include <system/graphics.h>
Now i have a problem with mesa.
unused parameter 'drv' [-Wunused-parameter]
droid_add_configs_for_visuals(_EGLDriver *drv, _EGLDisplay *dpy)
^
external/mesa/src/egl/drivers/dri2/platform_android.c: In function
'GRALLOC_MODULE_PERFORM_GET_DRM_FD' undeclared (first use in this function)
err = gr->perform(gr, GRALLOC_MODULE_PERFORM_GET_DRM_FD, &fd);
^
external/mesa/src/egl/drivers/dri2/platform_android.c:592:32: note: each
undeclared identifier is reported only once for each function it appears in
make: ***
[/home/cng/cm12.1/out/target/product/x86/obj/STATIC_LIBRARIES/libmesa_egl_dri2_intermediates/platform_android.o]
Error 1
#### make failed to build some targets (40:13 (mm:ss)) ####
Somebody know how can I fix this problem?
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
JJ Meijer
2015-12-29 20:58:54 UTC
Permalink
CyanogenMod 13.0 build is up.

Kernel enabled built-in NTFS driver so you can put your CM installation on
your Windows partition. (maybe Android-x86 external ntfs-3g implementation
is better but I didn't try it)
Kernel Crystal Cove PMIC opregions enabled. (Bay Trail stuff)
Basic keyboard (ATKBD) and Logitech wireless HID++ built-in to make
debugging easier.
Surfaceflinger ConsoleManager implementation from Android-x86. (alt + f1 to
access root shell)
External storage is now supported out of the box, tested FAT and EXT4.
Probably also NTFS as Android Vold supports it but have not tested it yet.
Youtube HD is working (out of the box)
CM root (out of the box, enable from developer options menu)
Further stripped down OpenGapps Pico, just enough to get the Play store
working (based on A-Gapps)
MESA 11.0.7 from Mauro

Not working:
Bluetooth
Camera
Native ARM dependent apps like Netflix (need to implement Native bridge
from Android-x86 to get it working)
You tell me...

Also included a EFI boot partition example on the G drive.

https://drive.google.com/open?id=0B9vJ9JSuyPijaVNZZHNuaDJDWUE
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
Povilas Staniulis
2015-12-29 23:33:12 UTC
Permalink
Nice.
Would be nice to get the manifest/source. I would like to tinker with this.

As for Bluetooth, does CM 13.0 use Bluez or Bluedroid stack ?
Bluez supports more devices than Bluedroid stack.

As for NTFS, last time I checked, the kernel NTFS driver was read-only.
Ntfs-3g is better but it's FUSE based.
There's also a free Paragon driver but it doesn't build with recent kernels.
Post by JJ Meijer
CyanogenMod 13.0 build is up.
Kernel enabled built-in NTFS driver so you can put your CM
installation on your Windows partition. (maybe Android-x86 external
ntfs-3g implementation is better but I didn't try it)
Kernel Crystal Cove PMIC opregions enabled. (Bay Trail stuff)
Basic keyboard (ATKBD) and Logitech wireless HID++ built-in to make
debugging easier.
Surfaceflinger ConsoleManager implementation from Android-x86. (alt +
f1 to access root shell)
External storage is now supported out of the box, tested FAT and EXT4.
Probably also NTFS as Android Vold supports it but have not tested it yet.
Youtube HD is working (out of the box)
CM root (out of the box, enable from developer options menu)
Further stripped down OpenGapps Pico, just enough to get the Play
store working (based on A-Gapps)
MESA 11.0.7 from Mauro
Bluetooth
Camera
Native ARM dependent apps like Netflix (need to implement Native
bridge from Android-x86 to get it working)
You tell me...
Also included a EFI boot partition example on the G drive.
https://drive.google.com/open?id=0B9vJ9JSuyPijaVNZZHNuaDJDWUE
--
You received this message because you are subscribed to the Google
Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
JJ Meijer
2015-12-29 23:53:57 UTC
Permalink
Thanks, I'll be checking that out next, I want to get a Bluetooth speaker
working... :o) I see there is some work done for Asus AT100 devices with
BCM432141 in Android-x86 but for some reason it didn't work for my HP
Omni10 with the same chip.

Actually there now is NTFS RW support in kernel with some limitations but
that shouldn't give any limitation to us if we use raw EXT4 disk images on
these partitions. I actually got it working already (nice and fast) but it
gets fucked up very easy when not properly unmounted or crash or Windows
fast reboot / hibernation....
Post by Povilas Staniulis
Nice.
Would be nice to get the manifest/source. I would like to tinker with this.
As for Bluetooth, does CM 13.0 use Bluez or Bluedroid stack ?
Bluez supports more devices than Bluedroid stack.
As for NTFS, last time I checked, the kernel NTFS driver was read-only.
Ntfs-3g is better but it's FUSE based.
There's also a free Paragon driver but it doesn't build with recent kernels.
CyanogenMod 13.0 build is up.
Kernel enabled built-in NTFS driver so you can put your CM installation on
your Windows partition. (maybe Android-x86 external ntfs-3g implementation
is better but I didn't try it)
Kernel Crystal Cove PMIC opregions enabled. (Bay Trail stuff)
Basic keyboard (ATKBD) and Logitech wireless HID++ built-in to make
debugging easier.
Surfaceflinger ConsoleManager implementation from Android-x86. (alt + f1
to access root shell)
External storage is now supported out of the box, tested FAT and EXT4.
Probably also NTFS as Android Vold supports it but have not tested it yet.
Youtube HD is working (out of the box)
CM root (out of the box, enable from developer options menu)
Further stripped down OpenGapps Pico, just enough to get the Play store
working (based on A-Gapps)
MESA 11.0.7 from Mauro
Bluetooth
Camera
Native ARM dependent apps like Netflix (need to implement Native bridge
from Android-x86 to get it working)
You tell me...
Also included a EFI boot partition example on the G drive.
https://drive.google.com/open?id=0B9vJ9JSuyPijaVNZZHNuaDJDWUE
--
You received this message because you are subscribed to the Google Groups
"Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an
<javascript:>.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
spin877
2015-12-29 23:58:45 UTC
Permalink
I used this rom
CM13.0-x86_kernel-4.1.15_mesa-11.0.7_A-GAPPS_int.tar.gz

as usual on my tablet baytrail cpu it z3735f not working.
1 ) problems initrd.img con usb live (replaced with a version andorid-x86)
2 ) rtl8723bs wifi
3 ) goodix touch screen
4 ) accelerometer sensor ( please implement libiio )

I solved this by compiling the kernel and modules
https://github.com/pstglia/linux

I added
ro.sf.lcd_density=160 build.prop


now it seems to work

finally Youtube in HD ..... :-)

thank you.
Post by JJ Meijer
CyanogenMod 13.0 build is up.
Kernel enabled built-in NTFS driver so you can put your CM installation on
your Windows partition. (maybe Android-x86 external ntfs-3g implementation
is better but I didn't try it)
Kernel Crystal Cove PMIC opregions enabled. (Bay Trail stuff)
Basic keyboard (ATKBD) and Logitech wireless HID++ built-in to make
debugging easier.
Surfaceflinger ConsoleManager implementation from Android-x86. (alt + f1
to access root shell)
External storage is now supported out of the box, tested FAT and EXT4.
Probably also NTFS as Android Vold supports it but have not tested it yet.
Youtube HD is working (out of the box)
CM root (out of the box, enable from developer options menu)
Further stripped down OpenGapps Pico, just enough to get the Play store
working (based on A-Gapps)
MESA 11.0.7 from Mauro
Bluetooth
Camera
Native ARM dependent apps like Netflix (need to implement Native bridge
from Android-x86 to get it working)
You tell me...
Also included a EFI boot partition example on the G drive.
https://drive.google.com/open?id=0B9vJ9JSuyPijaVNZZHNuaDJDWUE
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
youling 257
2015-12-30 00:15:07 UTC
Permalink
me toocan you share yours kernel and modules ?

圚 2015幎12月30日星期䞉 UTC+8䞊午7:58:46spin877写道
Post by spin877
I used this rom
CM13.0-x86_kernel-4.1.15_mesa-11.0.7_A-GAPPS_int.tar.gz
as usual on my tablet baytrail cpu it z3735f not working.
1 ) problems initrd.img con usb live (replaced with a version andorid-x86)
2 ) rtl8723bs wifi
3 ) goodix touch screen
4 ) accelerometer sensor ( please implement libiio )
I solved this by compiling the kernel and modules
https://github.com/pstglia/linux
I added
ro.sf.lcd_density=160 build.prop
now it seems to work
finally Youtube in HD ..... :-)
thank you.
Post by JJ Meijer
CyanogenMod 13.0 build is up.
Kernel enabled built-in NTFS driver so you can put your CM installation
on your Windows partition. (maybe Android-x86 external ntfs-3g
implementation is better but I didn't try it)
Kernel Crystal Cove PMIC opregions enabled. (Bay Trail stuff)
Basic keyboard (ATKBD) and Logitech wireless HID++ built-in to make
debugging easier.
Surfaceflinger ConsoleManager implementation from Android-x86. (alt + f1
to access root shell)
External storage is now supported out of the box, tested FAT and EXT4.
Probably also NTFS as Android Vold supports it but have not tested it yet.
Youtube HD is working (out of the box)
CM root (out of the box, enable from developer options menu)
Further stripped down OpenGapps Pico, just enough to get the Play store
working (based on A-Gapps)
MESA 11.0.7 from Mauro
Bluetooth
Camera
Native ARM dependent apps like Netflix (need to implement Native bridge
from Android-x86 to get it working)
You tell me...
Also included a EFI boot partition example on the G drive.
https://drive.google.com/open?id=0B9vJ9JSuyPijaVNZZHNuaDJDWUE
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
STORatt
2015-12-29 22:17:22 UTC
Permalink
Could you m8 make an IMG or ISO file so it easyer, i'm trying this from
yesterday and still no boot LOL.

TNX.
Post by JJ Meijer
CyanogenMod 13.0 build is up.
Kernel enabled built-in NTFS driver so you can put your CM installation on
your Windows partition. (maybe Android-x86 external ntfs-3g implementation
is better but I didn't try it)
Kernel Crystal Cove PMIC opregions enabled. (Bay Trail stuff)
Basic keyboard (ATKBD) and Logitech wireless HID++ built-in to make
debugging easier.
Surfaceflinger ConsoleManager implementation from Android-x86. (alt + f1
to access root shell)
External storage is now supported out of the box, tested FAT and EXT4.
Probably also NTFS as Android Vold supports it but have not tested it yet.
Youtube HD is working (out of the box)
CM root (out of the box, enable from developer options menu)
Further stripped down OpenGapps Pico, just enough to get the Play store
working (based on A-Gapps)
MESA 11.0.7 from Mauro
Bluetooth
Camera
Native ARM dependent apps like Netflix (need to implement Native bridge
from Android-x86 to get it working)
You tell me...
Also included a EFI boot partition example on the G drive.
https://drive.google.com/open?id=0B9vJ9JSuyPijaVNZZHNuaDJDWUE
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
JJ Meijer
2015-12-30 09:17:28 UTC
Permalink
I won't because there are just two step to the whole installation process
but there are a lot of different ways do to it. If someone else would like
to do it, please do!

Short description, I would recommend getting an Ubuntu Live cd and go the
EXT4 partition way.

1. Choose a storage device / create it
-Use existing Linux partition
-Create a new EXT4 partition
-Use your Windows partition

2. Copy all the files to that partition, optionally into a folder on that
device
-For Linux/EXT4 partition create an empty data folder for storage, called
"data".
-For Windows create a raw disk image called data.img with a EXT4 partition
in it. I created one on me G Drive for your confidence

3. Install Grub
-Edit the grub.cfg directly
-For existing Linux distro: append to /etc/grub.d/40_custom and run
update-grub

Example if it's in the root:
menuentry "CM13.0-x86" {
search --no-floppy --set=root --file /ramdisk.img
linux /kernel CMDLINE androidboot.hardware=omni
initrd /initrd.img
}

Example if it's in a folder:
menuentry "CM13.0-x86" {
set DIR=/cm13.0
search --no-floppy --set=root --file $DIR/ramdisk.img
linux $DIR/kernel CMDLINE androidboot.hardware=omni SRC=$DIR
initrd $DIR/initrd.img
}

If you don't understand these steps, just use Google because this is not
Android-x86 specific and there are A LOT of nice how-to's.
Post by STORatt
Could you m8 make an IMG or ISO file so it easyer, i'm trying this from
yesterday and still no boot LOL.
TNX.
Post by JJ Meijer
CyanogenMod 13.0 build is up.
Kernel enabled built-in NTFS driver so you can put your CM installation
on your Windows partition. (maybe Android-x86 external ntfs-3g
implementation is better but I didn't try it)
Kernel Crystal Cove PMIC opregions enabled. (Bay Trail stuff)
Basic keyboard (ATKBD) and Logitech wireless HID++ built-in to make
debugging easier.
Surfaceflinger ConsoleManager implementation from Android-x86. (alt + f1
to access root shell)
External storage is now supported out of the box, tested FAT and EXT4.
Probably also NTFS as Android Vold supports it but have not tested it yet.
Youtube HD is working (out of the box)
CM root (out of the box, enable from developer options menu)
Further stripped down OpenGapps Pico, just enough to get the Play store
working (based on A-Gapps)
MESA 11.0.7 from Mauro
Bluetooth
Camera
Native ARM dependent apps like Netflix (need to implement Native bridge
from Android-x86 to get it working)
You tell me...
Also included a EFI boot partition example on the G drive.
https://drive.google.com/open?id=0B9vJ9JSuyPijaVNZZHNuaDJDWUE
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
paul17
2015-12-30 09:57:05 UTC
Permalink
Mounting Partitions doesn't work. Neither on the boot screen, nor using StickMount.
StickMount just mounts empty folders. The only accessible partition using StickMount is the partition on which CM13 is installed. Any fix?
Thanks in advance. Root access on MM :)
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
JJ Meijer
2015-12-30 10:58:31 UTC
Permalink
It works just fine, check the screenshots. Also don't use stickmount. Did
you forget to replace the ramdisk.img?

I seem to have uploaded an old kernek without ntfs support and maybe some
issues for non EFI devices, new build is up. Audio I have to check.

https://drive.google.com/open?id=0B9vJ9JSuyPijMUJrQUdWXzgwRGs
Post by paul17
Mounting Partitions doesn't work. Neither on the boot screen, nor using StickMount.
StickMount just mounts empty folders. The only accessible partition using
StickMount is the partition on which CM13 is installed. Any fix?
Thanks in advance. Root access on MM :)
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
paul17
2015-12-30 13:26:56 UTC
Permalink
I did a fresh install. I did not have the old CM12.1 running. So I copied all the files (including kernel and ramdisk) from the new CM13 tar file. I'll try using the kernel without ntfs and I'll report soon. I don't know why I always have some or the other problems. Maybe I do something wrong. Sorry for the trouble.
Thanks :)
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
paul17
2015-12-30 14:31:58 UTC
Permalink
Can you please reupload the old kernel without ntfs support?
Post by JJ Meijer
It works just fine, check the screenshots. Also don't use stickmount. Did
you forget to replace the ramdisk.img?
I seem to have uploaded an old kernek without ntfs support and maybe some
issues for non EFI devices, new build is up. Audio I have to check.
https://drive.google.com/open?id=0B9vJ9JSuyPijMUJrQUdWXzgwRGs
Post by paul17
Mounting Partitions doesn't work. Neither on the boot screen, nor using StickMount.
StickMount just mounts empty folders. The only accessible partition using
StickMount is the partition on which CM13 is installed. Any fix?
Thanks in advance. Root access on MM :)
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
JJ Meijer
2015-12-30 14:52:59 UTC
Permalink
@Paul, you could try this one:
https://drive.google.com/open?id=0B9vJ9JSuyPijSDhPZmthVkllaVk

@Youling, please send me a pull request for additional hw support:
https://github.com/meijjaa/linux/tree/android-longterm or just send me a
link to a commit and I'll cherry-pick it.
Post by paul17
Can you please reupload the old kernel without ntfs support?
Post by JJ Meijer
It works just fine, check the screenshots. Also don't use stickmount. Did
you forget to replace the ramdisk.img?
I seem to have uploaded an old kernek without ntfs support and maybe some
issues for non EFI devices, new build is up. Audio I have to check.
https://drive.google.com/open?id=0B9vJ9JSuyPijMUJrQUdWXzgwRGs
Post by paul17
Mounting Partitions doesn't work. Neither on the boot screen, nor using StickMount.
StickMount just mounts empty folders. The only accessible partition
using StickMount is the partition on which CM13 is installed. Any fix?
Thanks in advance. Root access on MM :)
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
paul17
2015-12-30 14:57:26 UTC
Permalink
I'm already running the same version, and encountered the listed problems
on the same
Post by JJ Meijer
https://drive.google.com/open?id=0B9vJ9JSuyPijSDhPZmthVkllaVk
https://github.com/meijjaa/linux/tree/android-longterm or just send me a
link to a commit and I'll cherry-pick it.
Post by paul17
Can you please reupload the old kernel without ntfs support?
Post by JJ Meijer
It works just fine, check the screenshots. Also don't use stickmount.
Did you forget to replace the ramdisk.img?
I seem to have uploaded an old kernek without ntfs support and maybe
some issues for non EFI devices, new build is up. Audio I have to check.
https://drive.google.com/open?id=0B9vJ9JSuyPijMUJrQUdWXzgwRGs
Post by paul17
Mounting Partitions doesn't work. Neither on the boot screen, nor using StickMount.
StickMount just mounts empty folders. The only accessible partition
using StickMount is the partition on which CM13 is installed. Any fix?
Thanks in advance. Root access on MM :)
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
youling 257
2015-12-30 17:14:28 UTC
Permalink
in my google drive linkmodules files is Onda V891w Dual OS 2GB/64GB Win8.1
& Android4.4 Tablet PC Intel Z3735F 's. But my tablet is v891w 32GBno dual
os with Android 4.4soplease add kernel and modules support for v891w 32GB.

圚 2015幎12月30日星期䞉 UTC+8䞋午10:52:59JJ Meijer写道
Post by JJ Meijer
https://drive.google.com/open?id=0B9vJ9JSuyPijSDhPZmthVkllaVk
https://github.com/meijjaa/linux/tree/android-longterm or just send me a
link to a commit and I'll cherry-pick it.
Post by paul17
Can you please reupload the old kernel without ntfs support?
Post by JJ Meijer
It works just fine, check the screenshots. Also don't use stickmount.
Did you forget to replace the ramdisk.img?
I seem to have uploaded an old kernek without ntfs support and maybe
some issues for non EFI devices, new build is up. Audio I have to check.
https://drive.google.com/open?id=0B9vJ9JSuyPijMUJrQUdWXzgwRGs
Post by paul17
Mounting Partitions doesn't work. Neither on the boot screen, nor using StickMount.
StickMount just mounts empty folders. The only accessible partition
using StickMount is the partition on which CM13 is installed. Any fix?
Thanks in advance. Root access on MM :)
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
JJ Meijer
2015-12-30 17:39:28 UTC
Permalink
I don't think that will work with this kernel. Can you check which kernel
version it is?
Post by youling 257
in my google drive linkmodules files is Onda V891w Dual OS 2GB/64GB
Win8.1 & Android4.4 Tablet PC Intel Z3735F 's. But my tablet is v891w
32GBno dual os with Android 4.4soplease add kernel and modules support
for v891w 32GB.
圚 2015幎12月30日星期䞉 UTC+8䞋午10:52:59JJ Meijer写道
Post by JJ Meijer
https://drive.google.com/open?id=0B9vJ9JSuyPijSDhPZmthVkllaVk
https://github.com/meijjaa/linux/tree/android-longterm or just send me a
link to a commit and I'll cherry-pick it.
Post by paul17
Can you please reupload the old kernel without ntfs support?
Post by JJ Meijer
It works just fine, check the screenshots. Also don't use stickmount.
Did you forget to replace the ramdisk.img?
I seem to have uploaded an old kernek without ntfs support and maybe
some issues for non EFI devices, new build is up. Audio I have to check.
https://drive.google.com/open?id=0B9vJ9JSuyPijMUJrQUdWXzgwRGs
Post by paul17
Mounting Partitions doesn't work. Neither on the boot screen, nor using StickMount.
StickMount just mounts empty folders. The only accessible partition
using StickMount is the partition on which CM13 is installed. Any fix?
Thanks in advance. Root access on MM :)
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
youling 257
2015-12-30 17:58:36 UTC
Permalink
my tablet v891w 32GBwifi 8723bstouchscreen may be atmel_mxt_ts. Oki
need modules support for v891w 32GB with cm13also 4.1.15 kernel or latest
kernel will nice.
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
Balkan Clash
2015-12-30 18:18:57 UTC
Permalink
Well i already try that why, and even now i have done exactly what you sad
and i get error that linux and initrd command are unknown so i enter
linuxefi and initrdefi, but then i get black screen and my pc freeze ( i
know its frozen by caps/num. lock. )
Post by JJ Meijer
I won't because there are just two step to the whole installation process
but there are a lot of different ways do to it. If someone else would like
to do it, please do!
Short description, I would recommend getting an Ubuntu Live cd and go the
EXT4 partition way.
1. Choose a storage device / create it
-Use existing Linux partition
-Create a new EXT4 partition
-Use your Windows partition
2. Copy all the files to that partition, optionally into a folder on that
device
-For Linux/EXT4 partition create an empty data folder for storage, called
"data".
-For Windows create a raw disk image called data.img with a EXT4 partition
in it. I created one on me G Drive for your confidence
3. Install Grub
-Edit the grub.cfg directly
-For existing Linux distro: append to /etc/grub.d/40_custom and run
update-grub
menuentry "CM13.0-x86" {
search --no-floppy --set=root --file /ramdisk.img
linux /kernel CMDLINE androidboot.hardware=omni
initrd /initrd.img
}
menuentry "CM13.0-x86" {
set DIR=/cm13.0
search --no-floppy --set=root --file $DIR/ramdisk.img
linux $DIR/kernel CMDLINE androidboot.hardware=omni SRC=$DIR
initrd $DIR/initrd.img
}
If you don't understand these steps, just use Google because this is not
Android-x86 specific and there are A LOT of nice how-to's.
Post by STORatt
Could you m8 make an IMG or ISO file so it easyer, i'm trying this from
yesterday and still no boot LOL.
TNX.
Post by JJ Meijer
CyanogenMod 13.0 build is up.
Kernel enabled built-in NTFS driver so you can put your CM installation
on your Windows partition. (maybe Android-x86 external ntfs-3g
implementation is better but I didn't try it)
Kernel Crystal Cove PMIC opregions enabled. (Bay Trail stuff)
Basic keyboard (ATKBD) and Logitech wireless HID++ built-in to make
debugging easier.
Surfaceflinger ConsoleManager implementation from Android-x86. (alt + f1
to access root shell)
External storage is now supported out of the box, tested FAT and EXT4.
Probably also NTFS as Android Vold supports it but have not tested it yet.
Youtube HD is working (out of the box)
CM root (out of the box, enable from developer options menu)
Further stripped down OpenGapps Pico, just enough to get the Play store
working (based on A-Gapps)
MESA 11.0.7 from Mauro
Bluetooth
Camera
Native ARM dependent apps like Netflix (need to implement Native bridge
from Android-x86 to get it working)
You tell me...
Also included a EFI boot partition example on the G drive.
https://drive.google.com/open?id=0B9vJ9JSuyPijaVNZZHNuaDJDWUE
--
You received this message because you are subscribed to a topic in the
Google Groups "Android-x86" group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/android-x86/EQR7dqArcXg/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
JJ Meijer
2015-12-30 18:38:57 UTC
Permalink
There seems tot be a problem loading this kernel on x64 hardware, I can reproduce it. Strange enough it does load from grub on my Linux Mint 17.3 installation.

So why not install Linux Mint and put it on the same partition? It has a nice installer. It will take me some time to find out the real problem and I really don't have time.
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
STORatt
2015-12-30 18:58:15 UTC
Permalink
Well m8, if that is your attitude about it...then there is no sense
continuing this project, something that is working only on your pc setup
and non other is just not useful.
Post by JJ Meijer
There seems tot be a problem loading this kernel on x64 hardware, I can
reproduce it. Strange enough it does load from grub on my Linux Mint 17.3
installation.
So why not install Linux Mint and put it on the same partition? It has a
nice installer. It will take me some time to find out the real problem and
I really don't have time.
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
JJ Meijer
2015-12-30 19:08:01 UTC
Permalink
Please read what I said, it takes time. This really is not ready for mainstream users like yourself.
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
paul17
2015-12-31 07:52:47 UTC
Permalink
Can you please provide the ntfs-3g files for this? I need to get my partitions mounted on this system. Thanks a lot
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
Jianlong Liu
2015-12-30 23:55:07 UTC
Permalink
If that's your attitude, nobody would mind if you showed yourself the door.
People are working on this in their spare time, and it's holiday season.
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
paul17
2015-12-31 07:40:19 UTC
Permalink
Don't you have any respect for the developers? They are not your servants! They work in their spare time. They do have a life besides Android-x86. And it's your problem that it isn't working on your device.
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
Ventricle Vioner
2015-12-30 21:31:42 UTC
Permalink
Well m8, if that is your attitude about it...then there is no sense continuing this project, something that is working only on your pc setup and non other is just not useful.
STORatt, please read carefully, he said it takes time, he didn't say he won't try to handle the problem. I'm sure he will try to solve the issue.

JJ Meijer thanks for porting CM to Android-x86. It's essential work in this environment and means a lot.

As soon as I can, I'll test your builds on my Asus T100TA.

Thanks again! Have a good one, and also a good year 2016 :)
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
paul17
2015-12-30 10:27:37 UTC
Permalink
I also don't have any audio output
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
youling 257
2015-12-29 21:52:38 UTC
Permalink
prefectcm13base on 6.0.1can work on my bay trail tabletwonderful.
can you add this modules
? https://drive.google.com/open?id=0B1HDhURlGNctczBvRFQ3OWF3OHc
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
youling 257
2015-12-29 23:58:17 UTC
Permalink
https://drive.google.com/open?id=0B1HDhURlGNctNXlQSG5aWi15MTg

圚 2015幎12月30日星期䞉 UTC+8䞊午5:52:38youling 257写道
Post by youling 257
prefectcm13base on 6.0.1can work on my bay trail tabletwonderful.
can you add this modules ?
https://drive.google.com/open?id=0B1HDhURlGNctczBvRFQ3OWF3OHc
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
youling 257
2015-12-30 13:39:21 UTC
Permalink
wifitouchscreenand morenot working.

圚 2015幎12月30日星期䞉 UTC+8䞊午7:58:17youling 257写道
Post by youling 257
https://drive.google.com/open?id=0B1HDhURlGNctNXlQSG5aWi15MTg
圚 2015幎12月30日星期䞉 UTC+8䞊午5:52:38youling 257写道
Post by youling 257
prefectcm13base on 6.0.1can work on my bay trail tabletwonderful.
can you add this modules ?
https://drive.google.com/open?id=0B1HDhURlGNctczBvRFQ3OWF3OHc
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
youling 257
2015-12-31 19:03:28 UTC
Permalink
can you add this modules  if no,please build latest cm13 with 4.0.9
kernel. on my tablet,4.0.9 kernel,wifi can work, touchscreen yet can not
work,As long as wifi can work,it is enoughso,please build cm13 with 4.0.9
kernel. CM13.0-x86_kernel-4.1.15_mesa-11.0.7_A-GAPPS_int.tar.gz,latest
build,plese 4.0.9 kernel . Future updatesbuild two,one 4.1.15 kernel,one
4.0.9 kernel,will nice.

圚 2015幎12月30日星期䞉 UTC+8䞊午7:58:17youling 257写道
Post by youling 257
https://drive.google.com/open?id=0B1HDhURlGNctNXlQSG5aWi15MTg
圚 2015幎12月30日星期䞉 UTC+8䞊午5:52:38youling 257写道
Post by youling 257
prefectcm13base on 6.0.1can work on my bay trail tabletwonderful.
can you add this modules ?
https://drive.google.com/open?id=0B1HDhURlGNctczBvRFQ3OWF3OHc
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
Jim
2015-12-31 08:28:50 UTC
Permalink
Hello, is there anyone try this on Surface Pro 3, Surface 3 or Surface Pro
4?

touchscreen, keyboard, wifi/bluetooth, sound and so on work?

Thanks JJ Meijer to start this project.

JJ Meijeræ–Œ 2015幎9月29日星期二 UTC+8䞋午6時53分53秒寫道
Post by JJ Meijer
Hello everybody,
I started a project to learn something more about Linux and Android so I
started to port the Cyanogen project to my HP Omni 10 (Baytrail) tablet.
Many thanks to the Android-x86 project I had relatively quickly my tablet
booting and change_rooting into Android.
At the moment surfaceflinger is crashing because of a missing EGLConfig
(No suitable EGLConfig found). Hints in how this config should be supplied
are very welcome!
I will let you know how it goes... :)
Kind regard, JJ
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
rbg
2015-12-31 15:06:40 UTC
Permalink
all the Surface patches have been ported to the android-x86 git sources
also,
have you actually tried them and given a report to help the developers??


https://drive.google.com/folderview?id=0B2evBKvIpdYkTHNoblBZRlBDSnc&usp=sharing#list
Post by Jim
Hello, is there anyone try this on Surface Pro 3, Surface 3 or Surface Pro
4?
touchscreen, keyboard, wifi/bluetooth, sound and so on work?
Thanks JJ Meijer to start this project.
JJ Meijeræ–Œ 2015幎9月29日星期二 UTC+8䞋午6時53分53秒寫道
Post by JJ Meijer
Hello everybody,
I started a project to learn something more about Linux and Android so I
started to port the Cyanogen project to my HP Omni 10 (Baytrail) tablet.
Many thanks to the Android-x86 project I had relatively quickly my tablet
booting and change_rooting into Android.
At the moment surfaceflinger is crashing because of a missing EGLConfig
(No suitable EGLConfig found). Hints in how this config should be supplied
are very welcome!
I will let you know how it goes... :)
Kind regard, JJ
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
Eric Beier
2015-12-31 16:38:46 UTC
Permalink
Heyho guys,

I've tested the "android_x86_64-6.0.1_r3-20151230.img" on my Surface Pro 3
from this link:
https://drive.google.com/folderview?id=0B2evBKvIpdYkTHNoblBZRlBDSnc&usp=sharing#list

Everything except the rotation works very well, but only in the live
session mode and the first boot after the installation.
After the installation it only boots one more time correctly. In the second
boot there is the message "Apps optimizing" and when it finished the
Android boot logo appears.
After that there is the message "Apps optimizing" again. It's a loop.

Greetings Eric Beier

(sorry for the bad english)
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
rbg
2015-12-31 16:44:37 UTC
Permalink
to help the developers could you

Please provide more info including the hardware spec,

test environment and procedure, and the (most important)

logs (dmesg & logcat)."
Post by Eric Beier
Heyho guys,
I've tested the "android_x86_64-6.0.1_r3-20151230.img" on my Surface Pro 3
https://drive.google.com/folderview?id=0B2evBKvIpdYkTHNoblBZRlBDSnc&usp=sharing#list
Everything except the rotation works very well, but only in the live
session mode and the first boot after the installation.
After the installation it only boots one more time correctly. In the
second boot there is the message "Apps optimizing" and when it finished the
Android boot logo appears.
After that there is the message "Apps optimizing" again. It's a loop.
Greetings Eric Beier
(sorry for the bad english)
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
youling 257
2015-12-31 19:14:47 UTC
Permalink
android_x86_64-6.0.1_r3-20151230.imgwith 4.0.9 kernelcan work on my bay
trail tabletniceonly wifi can workbut it is enough. Future
updatesplease build one version with 4.0.9 kernel,will nice

圚 2016幎1月1日星期五 UTC+8䞊午12:44:38rbg写道
Post by rbg
to help the developers could you
Please provide more info including the hardware spec,
test environment and procedure, and the (most important)
logs (dmesg & logcat)."
Post by Eric Beier
Heyho guys,
I've tested the "android_x86_64-6.0.1_r3-20151230.img" on my Surface Pro
https://drive.google.com/folderview?id=0B2evBKvIpdYkTHNoblBZRlBDSnc&usp=sharing#list
Everything except the rotation works very well, but only in the live
session mode and the first boot after the installation.
After the installation it only boots one more time correctly. In the
second boot there is the message "Apps optimizing" and when it finished the
Android boot logo appears.
After that there is the message "Apps optimizing" again. It's a loop.
Greetings Eric Beier
(sorry for the bad english)
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
rbg
2015-12-31 17:26:01 UTC
Permalink
did you enable apps compatibility in settings???
Post by Eric Beier
Heyho guys,
I've tested the "android_x86_64-6.0.1_r3-20151230.img" on my Surface Pro 3
https://drive.google.com/folderview?id=0B2evBKvIpdYkTHNoblBZRlBDSnc&usp=sharing#list
Everything except the rotation works very well, but only in the live
session mode and the first boot after the installation.
After the installation it only boots one more time correctly. In the
second boot there is the message "Apps optimizing" and when it finished the
Android boot logo appears.
After that there is the message "Apps optimizing" again. It's a loop.
Greetings Eric Beier
(sorry for the bad english)
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
Eric Beier
2015-12-31 18:30:54 UTC
Permalink
Hey, i will do this tomorrow ;)

I wish you a happy new year!
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
JJ Meijer
2015-12-31 14:27:16 UTC
Permalink
Thanks for the support! But we shouldn't waste time on people like that.

I uploaded a now build. It should fix external device mount issues and
camera is working now (when supported). Still no audio or Bluetooth but
working on it.

https://drive.google.com/open?id=0B9vJ9JSuyPijdHh6T3o3WW02eWM


New EFI x64 + x86 example (Based on Arch-Boot):

https://drive.google.com/open?id=0B9vJ9JSuyPijR2NZYXNIek5iVFU


Also there is an flashable image available now for EFI x86 and x64 devices.
Just flash it on an USB drive with Linux dd or Windows win32diskimager
https://sourceforge.net/projects/win32diskimager/

https://drive.google.com/open?id=0B9vJ9JSuyPijZUFuSnJYVnYwZVE
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
paul17
2015-12-31 15:08:46 UTC
Permalink
Thanks a lot sir. I will install this tomorrow and report asap Hope you're enjoying the holiday season :)
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
Jon West
2015-12-31 22:16:52 UTC
Permalink
After testing quite a few options, I was able to get your CM13 builds to start booting. But they always stick at the boot animation, looping for an hour or more if I let it. Is there something I am missing getting these to work on the SP3?
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
JJ Meijer
2016-01-01 00:08:59 UTC
Permalink
Could it be you forgot to add a data folder or a data.img? I probably should add some more error checking for things like that.



Happy new year!
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
Jon West
2016-01-01 02:57:06 UTC
Permalink
I didn't specify a data.img file, just the directory it can be found in. So
that could be it
Post by JJ Meijer
Could it be you forgot to add a data folder or a data.img? I probably
should add some more error checking for things like that.
Happy new year!
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
JJ Meijer
2016-01-01 12:37:20 UTC
Permalink
If you are using a ext4 partition you only need to create a folder called data. If you use NTFS you need to add a raw ext4 disk img called data.img. It will be picked up automatically. This will be used for data storage, if it can't find it you will get this boot loop.
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
Jon West
2016-01-01 13:56:39 UTC
Permalink
Yeah, I made an ext4 data.IMG and left it in the folder, but it still never boots all the way :(
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
JJ Meijer
2016-01-01 20:44:10 UTC
Permalink
Could you please hit alt+f1 during boot and than type the logcat command? You should be seeing a log with errors flow by, it can take some time for it to catch up. Also you should try my USB image.

Ms surface 3 support should be there but I think kernel 4.4 will work better.
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
Ventricle Vioner
2016-01-01 14:07:19 UTC
Permalink
If you make a data.img you must store it in the root folder, not in data folder.
So you either
1. EXT4 partition for android: make Empty data folder in root dir
Or
2. For NTFS partition put data.img in root directory
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
paul17
2016-01-03 17:30:08 UTC
Permalink
i'm running the build now. Partition mounting issue has been fixed. Camera works. Waiting for audio to work
Thanks a lot :)
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
Jaap Jan Meijer
2016-01-03 19:33:57 UTC
Permalink
I found the audio issue, it was completely unrelated to audio. Apparently
CM13 now uses Toybox instead of Busybox as default which breaks the init
script. Please run "alsa_amixer set Master unmute" and "alsa_amixer set
Master 100%" to get audio working.

I will upload a new build next week with audio, the android-x86 native ARM
support and ntfs-3g. Built-in NTFS driver gives to much problems because
the dirty bit is always set and chkdsk needs to clear it before Android can
be booted again.
After that only Bluetooth needs to be fixed but that is a bit of a
challenge because the cm implementation is quite different.
Post by paul17
i'm running the build now. Partition mounting issue has been fixed. Camera
works. Waiting for audio to work
Thanks a lot :)
--
You received this message because you are subscribed to a topic in the
Google Groups "Android-x86" group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/android-x86/EQR7dqArcXg/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
John Denn Sinlao
2016-01-02 09:43:14 UTC
Permalink
Wow! Thank you for your build it is very fast but brightness, sound, autorotation and bluetooth are not working.

Can you teach me how to fix this?
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
JJ Meijer
2016-01-04 11:53:07 UTC
Permalink
Post by John Denn Sinlao
Wow! Thank you for your build it is very fast but brightness, sound,
autorotation and bluetooth are not working.
Can you teach me how to fix this?
Thanks! I will try to upload all the source asap so you guys can compile it
yourself and play with it :)

Sound is already fixed (but not yet released), the other issues might be
related to missing kernel drivers. They should be added to the kernel over
here: https://github.com/meijjaa/linux/tree/android-longterm
If you send me some more specifications I'll see if I can add the support
also. This is also for everybody else of course.
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
Loading...