Lenovo k860i Transplant Android 4.4 Cm11 progress Record "next-real-time Update"

Source: Internet
Author: User
Tags lenovo




2014.8.24
k860i of the cm11 of the transplant in the interruption of nearly two or three months after the beginning of the continuation of the log on the progress record has nothing to write about, the end of it, re-open a log to do the next article good. The recent situation is, in the efforts of Scue classmate, device parts can be compiled, but also get the official to some of the source (there is no use still not know, but can be compiled through), but, bad news is scue classmate due to work relatively busy, has completely abandoned the efforts of k860i.
now encountered some problems, the use of the official source code, compiled on CM11, after the brush will appear on the second screen black screen problems, grabbed the logcat, found that should be surfaceflinger and Hwcomposer part did not get up, Surfaceflinger has been crashing so loop, part Logcat as follows:
---------beginning Of/dev/log/systemI/AUDITD (1372): Starting up---------beginning Of/dev/log/maini/cm (1367): ____ _ _ ____ _ _ ____ ____ ____ _ _ _ _ ____ ___i/cm (1383): | \_/|__| |\ | | | | __ |___ |\ | |\/| | | |i/cm (1384): |___ | | | | \| |__| |__] |___ | \| | | |__| |__/i/cm (1387): Welcome to Android 4.4.4/cyanogenmod-11-20140822-unofficial-stuttgart I/debug (1374): debuggerd:aug 21:12:40 I/installd (1380): Installd firing upI/audit_log (1372): Previous Audit logfile detected, rotatingi/vold (1370): Vold 2.1 (The Revenge) firing up... ...I/surfaceflinger (1376): Surfaceflinger is startingI/surfaceflinger (1376): Surfaceflinger ' s main thread ready to run. Initializing Graphics h/w ...D/libegl (1376): loaded/system/lib/egl/libegl_mali.soD/libegl (1376): loaded/system/lib/egl/libglesv1_cm_mali.soD/libegl (1376): loaded/system/lib/egl/libglesv2_mali.soe/(1376): Device driver API matche/(1376): Device driver API version:20e/(1376): User space API version:20e/(1376): Mali:revision=linux-r3p2-01rel2 build_date=thu 15:22:27 CSTI/gralloc (1376): using (fd=16)I/gralloc (1376): id = S3CFBI/gralloc (1376): xres = 720 pxI/gralloc (1376): yres = pxI/gralloc (1376): xres_virtual = 720 pxI/gralloc (1376): yres_virtual = 2560 px I/gralloc (1376): BPP =I/gralloc (1376): R = 16:8I/gralloc (1376): g = 8:8I/gralloc (1376): b = 0:8I/gralloc (1376): width = mm (160.421051 dpi)I/gralloc (1376): height = 203 mm (160.157639 dpi)I/gralloc (1376): Refresh rate = 60.38 HzI/surfaceflinger (1376): Using Composer version 1.0 W/surfaceflinger (1376): Getting VSYNC period from FB hal:16561775W/surfaceflinger (1376): no suitable EGLConfig found, trying a simpler queryI/surfaceflinger (1376): EGL informations:I/surfaceflinger (1376): Vendor:androidI/surfaceflinger (1376): version:1.4 Android Meta-eglI/surfaceflinger (1376): extensions:egl_khr_get_all_proc_addresses egl_android_presentation_time EGL_KHR_image Egl_khr_image_base egl_khr_image_pixmap egl_khr_gl_texture_2d_image egl_khr_gl_texture_cubemap_image EGL_KHR_gl_ Renderbuffer_image Egl_khr_reusable_sync Egl_khr_fence_sync egl_ext_create_context_robustness EGL_ANDROID_image_ Native_buffer egl_android_recordableI/surfaceflinger (1376): Client api:opengl_esI/surfaceflinger (1376): eglsurface:8-8-8-0, config=0x60000012I/surfaceflinger (1376): OpenGL ES informations:I/surfaceflinger (1376): Vendor:armI/surfaceflinger (1376): renderer:mali-400 MPI/surfaceflinger (1376): Version:opengl ES 2.0I/surfaceflinger (1376): Extensions:gl_ext_debug_marker gl_oes_texture_npot gl_oes_compressed_etc1_rgb8_ Texture gl_oes_standard_derivatives gl_oes_egl_image gl_oes_depth24 gl_arm_rgba8 gl_arm_mali_shader_binary GL_OES_ Depth_texture gl_oes_packed_depth_stencil gl_ext_texture_format_bgra8888 Gl_ext_blend_minmax GL_OES_EGL_image_ External Gl_oes_egl_sync gl_oes_rgb8_rgba8 gl_ext_multisampled_render_to_texture gl_ext_discard_framebuffer GL_OES_ Get_program_binary gl_arm_mali_program_binary Gl_ext_shader_texture_lod gl_ext_robustness GL_OES_depth_texture_ Cube_mapI/surfaceflinger (1376): Gl_max_texture_size = 4096I/surfaceflinger (1376): Gl_max_viewport_dims = 4096E/cutils-trace (1376): Error opening trace file:no such file or directory (2)E/[egl-error] (1376): mali_surface* __egl_platform_create_surface_from_native_buffer (android_native_buffer_t* , egl_surface*, Mali_base_ctx_handle): 614:invalid buffer handle given (0X411008F0)E/[egl-error] (1376): void __egl_platform_dequeue_buffer (egl_surface*): 1629:failed to create a surface from native b Uffer (0x41100860)E/libegl (1376): eglmakecurrent:784 error 3003 (egl_bad_alloc)E/libegl (1376): Call-to-OpenGL ES API with no current context (logged once per thread)D/surfaceflinger (1376): Screen acquired, type=0 flinger=0x414c7450f/libc (1376): Fatal signal (SIGSEGV) at 0x00000000 (code=1), Thread 1376 (Surfaceflinger)D/libegl (1459): loaded/system/lib/egl/libegl_mali.soD/libegl (1459): loaded/system/lib/egl/libglesv1_cm_mali.soD/libegl (1459): loaded/system/lib/egl/libglesv2_mali.soe/(1459): Device driver API matche/(1459): Device driver API version:20e/(1459): User space API version:20e/(1459): Mali:revision=linux-r3p2-01rel2 build_date=thu 15:22:27 CSTE/cutils-trace (1459): Error opening trace file:no such file or directory (2) E/[egl-error] (1459): mali_surface* __egl_platform_create_surface_from_native_buffer (android_native_buffer_t* , egl_surface*, Mali_base_ctx_handle): 614:invalid buffer handle given (0X40092360) E/[egl-error] (1459): void __egl_platform_dequeue_buffer (egl_surface*): 1629:failed to create a surface from native b Uffer (0x40092230) E/libegl (1459): eglmakecurrent:784 error 3003 (egl_bad_alloc)I/debug (1374): * * * * * * * * * * * * * * * * * * * * * * * * * * * *I/debug (1374): Build fingerprint: ' Lenovo/cm_stuttgart/stuttgart:4.4.4/ktu84q/149b325933:userdebug/test-keys ' I/debug (1374): Revision: ' 0 'I/debug (1374): pid:1376, tid:1376, Name:surfaceflinger >>>/system/bin/surfaceflinger <<<I/debug (1374): Signal (SIGSEGV), Code 1 (segv_maperr), fault addr 00000000

I feel that if the problem is solved, the CM11 into the desktop should be not far away.
Of course there have been some good news lately.
accidentally found a lot of good things from the commit record of the smdk4412 kernel of the CM GitHub, such as the kernel to turn on selinux (for 4.3, 4.4 is important), or to solve the use of ARM-LINUX-GCC Version 4.7 Compiled this kernel appears a bunch of inline function definition of the compiler error resolution and so on, the power of open source is powerful ah, this kernel commit the number of more than 250,000 times .... The address is https://github.com/CyanogenMod/android_kernel_samsung_smdk4412/tree/stable/cm-11.0.
prior to using ARM-LINUX-GCC 4.7 to compile the kernel will have the inline function definition of the error, so the compilation of CM11 can only use the precompiled kernel, Because the CM11 compile process will use version 4.7 of the ARM-LINUX-GCC, and Lenovo to the kernel source code before the use of only 4.6 version of the ARM-LINUX-GCC is not a problem. CM official is recommended to use the kernel source with Cm11 source tree compiled together, the official explanation is here http://wiki.cyanogenmod.org/w/Doc:_integrated_kernel_building. After resolving the 4.7 version of the Toolchain compiler kernel error, you can let the kernel source code with CM11 compiled together. The related commit is here https://github.com/CyanogenMod/android_kernel_samsung_smdk4412/commit/ 49C33DAB8B7A57780AFFEA28DB976CCAB8DC345B, it should be noted that the filenames are not exactly the same, drivers/media/video/exynos/fimc-lite/ Fimc-lite-core.c and Fimc-lite.core.h are right, and deleting the definition of inline is the same, but the other two files mentioned in this commit, drivers/video/samsung_extdisp/ S3cfb_extdsp.h and S3CFB_EXTDSP_MAIN.C, filenames are different, in the Lenovo kernel source code, should be drivers/video/samsung/s3cfb.h and s3cfb_ MAIN.C, the number of rows modified is slightly different, but in fact, the definition of inline is removed.

The other one is the selinux problem, and the related commit is here https://github.com/CyanogenMod/android_kernel_samsung_smdk4412/commit/ 84C11BAF1CD2873665C9BD51F720EE3D83FAEFA2, this commit contains a plurality of machine kernel defconfig, in fact, only need to modify the Ki's official kernel source code kernel/arch/arm/ Configs/stuttgart_android_defconfig This file, you can add a change to the defconfig leaf out of one of the kernels in the above commit. In fact, can also be in the kernel root directory using make menuconfig or make Nconfig own manual selinux support, but since there are ready to use directly, that also can not need to modify their own.

still have to learn git use Ah, want to upload these things to GitHub above, otherwise manage these things is too troublesome.






Lenovo k860i Transplant Android 4.4 Cm11 progress Record "next-real-time Update"

Related Article

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.