KonstaT

[DEV][ROM][8.5.] LineageOS 13 (Android 6.0.1) for Chuwi Vi10 Plus, Hi10 Plus, Hi10 Pro, Hibook, Hibook Pro & Hi12

Recommended Posts

PalmTrees    26
On 9/13/2017 at 5:45 PM, yener90 said:

I uploaded the version 2017-09-13:

https://mega.nz/#F!R0821JbT!3sv0sYWEsEhpZGH6WqNbXQ

The difference here is that the device is default not rooted. If you want root, you need to install addonsu-13.0-x86-signed.zip.

I will upload a zip file which replaces Home-Key with Back-key.

 

All my thanks to Konstat, who helped me everytime.

Thanks a lot for the update. Just flashed it :) 

Share this post


Link to post
Share on other sites
PalmTrees    26

@KonstaT Lenovo has released the Android N 7.1.1 update for the Yoga Book (Intel Atom x5-Z8550) earlier than planned. It's out now. I don't want to nag you, simply just ask if this is something you're going to look into with regards to the Vi10 Plus? 

 

Share this post


Link to post
Share on other sites

if there are no kernel sources and the sources of the various adaptations to the 7.1.1 aosp tree.. it's unlikely that Konsta will be able to port anything...

Share this post


Link to post
Share on other sites
PalmTrees    26
1 hour ago, fear_factory84 said:

if there are no kernel sources and the sources of the various adaptations to the 7.1.1 aosp tree.. it's unlikely that Konsta will be able to port anything...

Did I adress you? No. Did I talk about porting? No.

I referenced this before, so he knows very well about this. Are "you're going to look into with regards to the Vi10 Plus?" was the question. 

I want to hear @KonstaT's thoughts on this and answers to this despite what it might be. Not yours, mind your own business. 

Edited by PalmTrees

Share this post


Link to post
Share on other sites
KonstaT    3,949
10 hours ago, PalmTrees said:

@KonstaT Lenovo has released the Android N 7.1.1 update for the Yoga Book (Intel Atom x5-Z8550) earlier than planned. It's out now. I don't want to nag you, simply just ask if this is something you're going to look into with regards to the Vi10 Plus? 

Is it available for download somewhere?

Share this post


Link to post
Share on other sites
PalmTrees    26
2 hours ago, KonstaT said:

Is it available for download somewhere?

Yes, I found it over at 4pda (yadi.sk link). https://4pda.ru/forum/index.php?showtopic=798682&st=780#entry65379900 

Boot.img is uploaded in the second post. 

Kernel version (3.14.79) is the same as Chuwi Vi10 Plus (can be seen in the screenshot here https://4pda.ru/forum/index.php?showtopic=798682&st=780#entry65352949).

All credits and thanks go to tank0412 (4pda/xda) for requesting the file and the uploader titoff1973 (4pda).

Edited by PalmTrees
Found the link and completely rewrote the post

Share this post


Link to post
Share on other sites
KonstaT    3,949
10 hours ago, PalmTrees said:

Yes, I found it over at 4pda (yadi.sk link). https://4pda.ru/forum/index.php?showtopic=798682&st=780#entry65379900 

Boot.img is uploaded in the second post. 

Kernel version (3.14.79) is the same as Chuwi Vi10 Plus (can be seen in the screenshot here https://4pda.ru/forum/index.php?showtopic=798682&st=780#entry65352949).

All credits and thanks go to tank0412 (4pda/xda) for requesting the file and the uploader titoff1973 (4pda).

Cool, I'll check it out when I get around.

Share this post


Link to post
Share on other sites
13 hours ago, PalmTrees said:

Did I adress you? No. Did I talk about porting? No.

I referenced this before, so he knows very well about this. Are "you're going to look into with regards to the Vi10 Plus?" was the question. 

I want to hear @KonstaT's thoughts on this and answers to this despite what it might be. Not yours, mind your own business. 

If this was the purpose you should have used a PM. Try to calm down. Have you eaten something heavy? Peppers at dinner?

Share this post


Link to post
Share on other sites
PalmTrees    26
2 hours ago, KonstaT said:

Cool, I'll check it out when I get around.

Great thanks :) 

1 hour ago, fear_factory84 said:

If this was the purpose you should have used a PM. Try to calm down. Have you eaten something heavy? Peppers at dinner?

How about "Thanks for sharing this. Let's hope for Android N development for Chuwi tablets". 

Share this post


Link to post
Share on other sites

Thanking you if you help to port nougat to these Chuwi tablets is perfectly fine and deserved, but this doesn't authorize you to bull people around.

Share this post


Link to post
Share on other sites
PalmTrees    26
1 hour ago, fear_factory84 said:

Thanking you if you help to port nougat to these Chuwi tablets is perfectly fine and deserved, but this doesn't authorize you to bull people around.

Let's hear the list of people I "bull around". Tell you what, quit your "bull" around here and focus on the real topic. Your rants are pointless and a waste of time, I provided the source, gave proper credit, been discussing this with KonstaT in different posts and know the community has great interest in Android N for the Atom series.

Back on topic. Excited to hear what @KonstaTmakes of it, no matter if it's good or bad news. 

 

Share this post


Link to post
Share on other sites
KonstaT    3,949

Chill guys.

No one is going to give you any ETAs. I'm busy with other things and I said I'll look into it when I get around. Anyone is free to pick this up and do whatever they want with it (there's other people working on Cherry Trail as well). That's the beauty of open source. :)

There's at least few significant issues Nougat bring up is going to introduce. If we want to use binary display drivers from the Lenovo N release (like we have to unless we can somehow shim the M blobs = hacky) we need to switch to building x86_64 Android. Unlike e.g. Qualcomm with open source audio/display/media HALs, Intel BSP uses prebuilt display HALs (gralloc, hwcomposer) which causes all kinds of issues with next Android versions. Lenovo N has 64-bit binary blobs - we end up with a crazy match of 64-bit Android N drivers and device/hardware specific 32-bit Andoid L drivers with some shims (camera) in between (stock firmware on this device is 32-bit Android L). Realtek bluetooth is all blobs from Medion M release in M (open source in L). I'm not aware of any N Realtek bluetooth blobs. That is likely going to be a major issue as well.

This device was meant to run Android 5.1 and CM12.1 is near perfect. Every next Android version has its repercussions (as you can see the list of issues in the OP) and you also need to consider when it's worth the effort (or are we just playing a round of 'will it run' :P). I just don't see the point in releasing something utterly broken.

Edit. XDA recently had a piece about this proprietary blob hell we're dealing with. https://www.xda-developers.com/cameras-custom-roms-developers-make-hardware-work-without-source-code/

Edited by KonstaT

Share this post


Link to post
Share on other sites
PalmTrees    26
On 9/26/2017 at 7:23 PM, KonstaT said:

This device was meant to run Android 5.1 and CM12.1 is near perfect. Every next Android version has its repercussions (as you can see the list of issues in the OP) and you also need to consider when it's worth the effort (or are we just playing a round of 'will it run' :P). I just don't see the point in releasing something utterly broken.

I hope tank0412 gets his AOSP 7.1.1 x86_64 build to boot on the Mi Pad 2 :) Even with those issues at hand, "will it run" would be interesting to find out, though we're not likely to see a stable build. Whatever you want to do is totally up to you - you're the most experienced developer around these parts. 

Share this post


Link to post
Share on other sites
KonstaT    3,949
7 hours ago, PalmTrees said:

I hope tank0412 gets his AOSP 7.1.1 x86_64 build to boot on the Mi Pad 2 :) Even with those issues at hand, "will it run" would be interesting to find out, though we're not likely to see a stable build. Whatever you want to do is totally up to you - you're the most experienced developer around these parts. 

Well, mine at least 'boots'. There's something seriously off with the display drivers, though.

09-29 13:27:47.371  2433  2433 E ufoGralloc: Driver() failed to open drm driver i915
09-29 13:27:47.371  2433  2433 I ufoGralloc: Hello, this is UFO GRALLOC/Intel Corporation
09-29 13:27:47.371  2433  2433 I ufoGralloc:  ro.camera.rec.pixel_format = 0x10f (271)
09-29 13:27:47.371  2433  2433 I ufoGralloc:  ro.ycbcr.pixel_format = 0x10f (271)
09-29 13:27:47.371  2433  2433 E ufoGralloc: perform() wrong module 0x7f6d7d2611e8
09-29 13:27:47.371  2433  2433 E grallocClient: FATAL: mismatched gralloc module: UFO GRALLOC/Intel Corporation, -19
09-29 13:27:47.371  2433  2433 W libEGL  : eglInitialize(0x7f6d7e20c500) failed (EGL_NOT_INITIALIZED)
09-29 13:27:47.372  2433  2433 E ufoGralloc: open() wrong module 0x7f6d7d2611e8
09-29 13:27:47.372  2433  2433 W ufoGralloc: open() attempted with module UFO GRALLOC
09-29 13:27:47.439  2433  2433 E hwc     : Persistent registry load failed to open file /cache/hwc.reg
09-29 13:27:47.440  2433  2433 E grallocClient: getFd() failed, -38/Function not implemented
09-29 13:27:47.440  2433  2433 F hwc     : Unable to query shared Gralloc DRM handle
--------- beginning of crash
09-29 13:27:47.440  2433  2433 F libc    : Fatal signal 6 (SIGABRT), code -6 in tid 2433 (surfaceflinger)
09-29 13:27:47.441  2370  2370 W         : debuggerd: handling request: pid=2433 uid=1000 gid=1003 tid=2433
09-29 13:27:47.445  2457  2457 E         : debuggerd: Unable to connect to activity manager (connect failed: No such file or directory)
09-29 13:27:47.497  2457  2457 F DEBUG   : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
09-29 13:27:47.497  2457  2457 F DEBUG   : LineageOS Version: '14.1-20170928-UNOFFICIAL-KonstaKANG-chuwi_vi10plus'
09-29 13:27:47.497  2457  2457 F DEBUG   : Build fingerprint: 'intel/cht_cr_mrd_w/cht_cr_mrd_w:5.1/LMY47I/softteam08031045:userdebug/release-keys'
09-29 13:27:47.497  2457  2457 F DEBUG   : Revision: '0'
09-29 13:27:47.497  2457  2457 F DEBUG   : ABI: 'x86_64'
09-29 13:27:47.497  2457  2457 F DEBUG   : pid: 2433, tid: 2433, name: surfaceflinger  >>> /system/bin/surfaceflinger <<<
09-29 13:27:47.497  2457  2457 F DEBUG   : signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr --------
09-29 13:27:47.498  2457  2457 F DEBUG   : Abort message: 'Unable to query shared Gralloc DRM handle'
09-29 13:27:47.498  2457  2457 F DEBUG   :     rax 0000000000000000  rbx 00007f6d7f51dbe8  rcx ffffffffffffffff  rdx 0000000000000006
09-29 13:27:47.498  2457  2457 F DEBUG   :     rsi 0000000000000981  rdi 0000000000000981
09-29 13:27:47.499  2457  2457 F DEBUG   :     r8  0000000000000001  r9  0000000000002d4a  r10 0000000000000008  r11 0000000000000206
09-29 13:27:47.499  2457  2457 F DEBUG   :     r12 0000000000000981  r13 0000000000000006  r14 00007f6d7ce1fb1c  r15 00007f6d7ce460a8
09-29 13:27:47.499  2457  2457 F DEBUG   :     cs  0000000000000033  ss  000000000000002b
09-29 13:27:47.499  2457  2457 F DEBUG   :     rip 00007f6d7f088bf7  rbp 0000000000000000  rsp 00007ffedb27fc38  eflags 0000000000000206
09-29 13:27:47.513  2457  2457 F DEBUG   : 
09-29 13:27:47.513  2457  2457 F DEBUG   : backtrace:
09-29 13:27:47.513  2457  2457 F DEBUG   :     #00 pc 0000000000090bf7  /system/lib64/libc.so (tgkill+7)
09-29 13:27:47.513  2457  2457 F DEBUG   :     #01 pc 000000000008d612  /system/lib64/libc.so (pthread_kill+66)
09-29 13:27:47.513  2457  2457 F DEBUG   :     #02 pc 00000000000303f1  /system/lib64/libc.so (raise+17)
09-29 13:27:47.513  2457  2457 F DEBUG   :     #03 pc 00000000000287de  /system/lib64/libc.so (abort+78)
09-29 13:27:47.513  2457  2457 F DEBUG   :     #04 pc 0000000000010e9f  /system/lib64/libcutils.so (__android_log_assert+287)
09-29 13:27:47.513  2457  2457 F DEBUG   :     #05 pc 000000000005c85c  /system/vendor/lib64/hw/hwcomposer.gmin.so
09-29 13:27:47.513  2457  2457 F DEBUG   :     #06 pc 000000000006100c  /system/vendor/lib64/hw/hwcomposer.gmin.so
09-29 13:27:47.513  2457  2457 F DEBUG   :     #07 pc 000000000005c769  /system/vendor/lib64/hw/hwcomposer.gmin.so
09-29 13:27:47.513  2457  2457 F DEBUG   :     #08 pc 000000000005e7e3  /system/vendor/lib64/hw/hwcomposer.gmin.so
09-29 13:27:47.513  2457  2457 F DEBUG   :     #09 pc 0000000000060ed9  /system/vendor/lib64/hw/hwcomposer.gmin.so
09-29 13:27:47.513  2457  2457 F DEBUG   :     #10 pc 000000000005dea2  /system/vendor/lib64/hw/hwcomposer.gmin.so
09-29 13:27:47.513  2457  2457 F DEBUG   :     #11 pc 0000000000027102  /system/vendor/lib64/hw/hwcomposer.gmin.so
09-29 13:27:47.513  2457  2457 F DEBUG   :     #12 pc 00000000000195bf  /system/vendor/lib64/hw/hwcomposer.gmin.so
09-29 13:27:47.513  2457  2457 F DEBUG   :     #13 pc 0000000000012426  /system/bin/linker64 (__dl__ZN6soinfo10call_arrayEPKcPPFvvEmb+390)
09-29 13:27:47.513  2457  2457 F DEBUG   :     #14 pc 0000000000010233  /system/bin/linker64 (__dl__Z9do_dlopenPKciPK17android_dlextinfoPv+2755)
09-29 13:27:47.513  2457  2457 F DEBUG   :     #15 pc 000000000000c37a  /system/bin/linker64 (__dl_dlopen+42)
09-29 13:27:47.513  2457  2457 F DEBUG   :     #16 pc 0000000000000bdc  /system/lib64/libhardware.so (hw_get_module_by_class+604)
09-29 13:27:47.513  2457  2457 F DEBUG   :     #17 pc 0000000000057155  /system/lib64/libsurfaceflinger.so
09-29 13:27:47.513  2457  2457 F DEBUG   :     #18 pc 0000000000056daa  /system/lib64/libsurfaceflinger.so
09-29 13:27:47.513  2457  2457 F DEBUG   :     #19 pc 00000000000445d5  /system/lib64/libsurfaceflinger.so
09-29 13:27:47.513  2457  2457 F DEBUG   :     #20 pc 0000000000047188  /system/lib64/libsurfaceflinger.so (_ZN7android14SurfaceFlinger4initEv+936)
09-29 13:27:47.513  2457  2457 F DEBUG   :     #21 pc 000000000000130a  /system/bin/surfaceflinger
09-29 13:27:47.513  2457  2457 F DEBUG   :     #22 pc 000000000001c9ec  /system/lib64/libc.so (__libc_init+108)
09-29 13:27:47.513  2457  2457 F DEBUG   :     #23 pc 00000000000011c7  /system/bin/surfaceflinger
09-29 13:27:47.513  2457  2457 F DEBUG   :     #24 pc 0000000000000000  <unknown>
09-29 13:27:47.558  2370  2370 W         : debuggerd: resuming target 2433

I first built x86_64 cm-13.0 with 64-bit display blobs from Teclast Tbook 16 Power Marshmallow (also tried blobs from Yoga Book Marshmallow) and it works fine what comes to display (there's other issues, though). No idea what's going on with cm-14.1 and N blobs...

Edit. Got a bit further. Might be down to kernel driver now.

09-29 20:09:34.210  2435  2435 I ufoGralloc: Hello, this is UFO GRALLOC/Intel Corporation
09-29 20:09:34.210  2435  2435 I ufoGralloc:  ro.camera.rec.pixel_format = 0x10f (271)
09-29 20:09:34.210  2435  2435 I ufoGralloc:  ro.ycbcr.pixel_format = 0x10f (271)
09-29 20:09:34.279  2435  2435 E hwc     : Persistent registry load failed to open file /cache/hwc.reg
09-29 20:09:34.280  2435  2435 I surfaceflinger: type=1400 audit(0.0:24): avc: denied { write } for name="i915_videostatus" dev="sysfs" ino=12999 scontext=u:r:surfaceflinger:s0 tcontext=u:object_r:sysfs:s0 tclass=file permissive=1
09-29 20:09:34.280  2435  2435 E hwc     : Failed drmGetCap( 17 ), ret:0
09-29 20:09:34.280  2435  2435 I hwc     : NOT AVAILABLE: DMR/KMS Render Compression support
09-29 20:09:34.284  2434  2434 E SELinux : avc:  denied  { add } for service=hwc.info pid=2435 uid=1000 scontext=u:r:surfaceflinger:s0 tcontext=u:object_r:default_android_service:s0 tclass=service_manager permissive=1
09-29 20:09:34.285  2435  2435 D hwc     : DRM connector 29 Panel CONNECTED DynamicMode:0 SeamlessDRRS:0 PanelFitter:1 DPMS:1
09-29 20:09:34.285  2435  2435 D hwc     : DRM connector 34 External DISCONNECTED DynamicMode:0 SeamlessDRRS:0 PanelFitter:1 DPMS:1
09-29 20:09:34.286  2435  2435 D hwc     : DRM connector 38 External DISCONNECTED DynamicMode:0 SeamlessDRRS:0 PanelFitter:1 DPMS:1
09-29 20:09:34.286  2435  2435 D hwc     : DisplayCaps creating caps for device 0x22b0 pipe 0
09-29 20:09:34.286  2435  2435 I hwc     : DisplayCaps construct Baytrail class caps for display pipe 0
09-29 20:09:34.286  2435  2435 D hwc     : Selected mode for Connector:29 [Connector 0x7fce21472180 Connected, CrtcID 6, PipeIdx 0] is Mode:0 1920x1280 60Hz Preferred 164.4MHz (2055x1334)
09-29 20:09:34.286  2435  2435 I libva   : VA-API version 0.99.0
09-29 20:09:34.287  2435  2435 I libva   : va_getDriverName() returns 0
09-29 20:09:34.287  2435  2435 I libva   : Trying to open /vendor/lib64/i965_drv_video.so
09-29 20:09:34.325  2435  2435 I libva   : Found init function __vaDriverInit_0_32
09-29 20:09:34.326  2435  2492 D ufo     : Detected device 22B0:34 family 17:11
09-29 20:09:34.326  2435  2492 E ufoGralloc: failed to perform fallocate (0, 0, 9830400), -38/Function not implemented
09-29 20:09:34.326  2435  2492 E ufoGralloc: perform(33) failed, -38/Function not implemented
09-29 20:09:34.326  2435  2492 E grallocClient: fallocate(0x7fce21a372d0) failed, -38/Function not implemented
09-29 20:09:34.326  2435  2492 E hwc     : Fallocate not implemented. Expect a higher memory footprint until its supported
09-29 20:09:34.332  2435  2492 D hwc     : Testing Drm atomic API
09-29 20:09:34.334  2435  2435 I libva   : va_openDriver() returns 0
09-29 20:09:34.350  2435  2492 D hwc     : Drm atomic API is available
09-29 20:09:34.360  2435  2435 V IVP     : iVP_create_context: Create Context success: ctx_id=0x70000000, vp_context=0x7fce21440240
09-29 20:09:34.360  2435  2435 D ufoEGL  : droid_create_context : config id = 1 conf->NativeVisualID=1
09-29 20:09:34.360  2435  2435 I ufoEGL  : Requested context : GLES 2.0
09-29 20:09:34.391  2435  2435 I         : GL_VERSION: OpenGL ES 3.1 - Build 4.70.60868-R
09-29 20:09:34.391  2435  2435 I         : GL_SHADING_LANGUAGE_VERSION: OpenGL ES GLSL ES 3.10 - Build 4.70.60868-R
09-29 20:09:34.487  2435  2435 D ufoEGL  : Pixel Format : GGL_PIXEL_FORMAT_RGBA_8888
--------- beginning of crash
09-29 20:09:34.504  2435  2435 F libc    : Fatal signal 11 (SIGSEGV), code 1, fault addr 0x8 in tid 2435 (surfaceflinger)
09-29 20:09:34.504  2370  2370 W         : debuggerd: handling request: pid=2435 uid=1000 gid=1003 tid=2435
09-29 20:09:34.510  2520  2520 E         : debuggerd: Unable to connect to activity manager (connect failed: No such file or directory)
09-29 20:09:34.513  2520  2520 F DEBUG   : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
09-29 20:09:34.513  2520  2520 F DEBUG   : LineageOS Version: '14.1-20170928-UNOFFICIAL-KonstaKANG-chuwi_vi10plus'
09-29 20:09:34.513  2520  2520 F DEBUG   : Build fingerprint: 'intel/cht_cr_mrd_w/cht_cr_mrd_w:5.1/LMY47I/softteam08031045:userdebug/release-keys'
09-29 20:09:34.513  2520  2520 F DEBUG   : Revision: '0'
09-29 20:09:34.513  2520  2520 F DEBUG   : ABI: 'x86_64'
09-29 20:09:34.513  2520  2520 F DEBUG   : pid: 2435, tid: 2435, name: surfaceflinger  >>> /system/bin/surfaceflinger <<<
09-29 20:09:34.513  2520  2520 F DEBUG   : signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x8
09-29 20:09:34.513  2520  2520 F DEBUG   :     rax 0000000000000000  rbx 00007fce1c7b2000  rcx 0000000000000010  rdx 0000000000000100
09-29 20:09:34.513  2520  2520 F DEBUG   :     rsi 00007fce213f7740  rdi 0030306100007f00
09-29 20:09:34.513  2520  2520 F DEBUG   :     r8  0000000000000010  r9  0000000000000000  r10 00007fce213f7740  r11 0000000000000000
09-29 20:09:34.513  2520  2520 F DEBUG   :     r12 00007fce21a26980  r13 0000000000000001  r14 00007fce213f7740  r15 0000000000000001
09-29 20:09:34.513  2520  2520 F DEBUG   :     cs  0000000000000033  ss  000000000000002b
09-29 20:09:34.513  2520  2520 F DEBUG   :     rip 00007fce20c7fbda  rbp 00007fffb640a0e0  rsp 00007fffb640a070  eflags 0000000000010206
09-29 20:09:34.538  2520  2520 F DEBUG   : 
09-29 20:09:34.538  2520  2520 F DEBUG   : backtrace:
09-29 20:09:34.538  2520  2520 F DEBUG   :     #00 pc 00000000001c1bda  /system/vendor/lib64/egl/libGLES_intel8.so
09-29 20:09:34.538  2520  2520 F DEBUG   :     #01 pc 0000000000385a75  /system/vendor/lib64/egl/libGLES_intel8.so
09-29 20:09:34.538  2520  2520 F DEBUG   :     #02 pc 0000000000386631  /system/vendor/lib64/egl/libGLES_intel8.so
09-29 20:09:34.538  2520  2520 F DEBUG   :     #03 pc 0000000000395a05  /system/vendor/lib64/egl/libGLES_intel8.so
09-29 20:09:34.538  2520  2520 F DEBUG   :     #04 pc 000000000039d077  /system/vendor/lib64/egl/libGLES_intel8.so
09-29 20:09:34.538  2520  2520 F DEBUG   :     #05 pc 00000000001771eb  /system/vendor/lib64/egl/libGLES_intel8.so
09-29 20:09:34.538  2520  2520 F DEBUG   :     #06 pc 0000000000522c13  /system/vendor/lib64/egl/libGLES_intel8.so
09-29 20:09:34.538  2520  2520 F DEBUG   :     #07 pc 000000000052387b  /system/vendor/lib64/egl/libGLES_intel8.so
09-29 20:09:34.538  2520  2520 F DEBUG   :     #08 pc 0000000000520554  /system/vendor/lib64/egl/libGLES_intel8.so
09-29 20:09:34.538  2520  2520 F DEBUG   :     #09 pc 00000000001441b9  /system/vendor/lib64/egl/libGLES_intel8.so
09-29 20:09:34.538  2520  2520 F DEBUG   :     #10 pc 00000000000dedc4  /system/vendor/lib64/egl/libGLES_intel8.so
09-29 20:09:34.538  2520  2520 F DEBUG   :     #11 pc 00000000000dfd6d  /system/vendor/lib64/egl/libGLES_intel8.so
09-29 20:09:34.538  2520  2520 F DEBUG   :     #12 pc 00000000000e71e4  /system/vendor/lib64/egl/libGLES_intel8.so (eglMakeCurrent+740)
09-29 20:09:34.538  2520  2520 F DEBUG   :     #13 pc 0000000000012414  /system/lib64/libEGL.so (_ZN7android13egl_display_t11makeCurrentEPNS_13egl_context_tES2_PvS3_S3_S3_S3_S3_+260)
09-29 20:09:34.538  2520  2520 F DEBUG   :     #14 pc 0000000000015e30  /system/lib64/libEGL.so (eglMakeCurrent+432)
09-29 20:09:34.538  2520  2520 F DEBUG   :     #15 pc 0000000000055eeb  /system/vendor/lib64/hw/hwcomposer.gmin.so
09-29 20:09:34.538  2520  2520 F DEBUG   :     #16 pc 000000000005637d  /system/vendor/lib64/hw/hwcomposer.gmin.so
09-29 20:09:34.538  2520  2520 F DEBUG   :     #17 pc 00000000000564e2  /system/vendor/lib64/hw/hwcomposer.gmin.so
09-29 20:09:34.538  2520  2520 F DEBUG   :     #18 pc 000000000005cbcf  /system/vendor/lib64/hw/hwcomposer.gmin.so
09-29 20:09:34.538  2520  2520 F DEBUG   :     #19 pc 000000000002ba1e  /system/vendor/lib64/hw/hwcomposer.gmin.so
09-29 20:09:34.538  2520  2520 F DEBUG   :     #20 pc 000000000005719a  /system/lib64/libsurfaceflinger.so
09-29 20:09:34.538  2520  2520 F DEBUG   :     #21 pc 0000000000056daa  /system/lib64/libsurfaceflinger.so
09-29 20:09:34.538  2520  2520 F DEBUG   :     #22 pc 00000000000445d5  /system/lib64/libsurfaceflinger.so
09-29 20:09:34.538  2520  2520 F DEBUG   :     #23 pc 0000000000047188  /system/lib64/libsurfaceflinger.so (_ZN7android14SurfaceFlinger4initEv+936)
09-29 20:09:34.538  2520  2520 F DEBUG   :     #24 pc 000000000000130a  /system/bin/surfaceflinger
09-29 20:09:34.538  2520  2520 F DEBUG   :     #25 pc 000000000001c9ec  /system/lib64/libc.so (__libc_init+108)
09-29 20:09:34.538  2520  2520 F DEBUG   :     #26 pc 00000000000011c7  /system/bin/surfaceflinger
09-29 20:09:34.538  2520  2520 F DEBUG   :     #27 pc 0000000000000000  <unknown>
09-29 20:09:34.597  2370  2370 W         : debuggerd: resuming target 2435

 

Edited by KonstaT

Share this post


Link to post
Share on other sites
PalmTrees    26
4 hours ago, KonstaT said:

Well, mine at least 'boots'. There's something seriously off with the display drivers, though.

I first built x86_64 cm-13.0 with 64-bit display blobs from Teclast Tbook 16 Power Marshmallow (also tried blobs from Yoga Book Marshmallow) and it works fine what comes to display (there's other issues, though). No idea what's going on with cm-14.1 and N blobs...

I'm not surprised you got it to boot :D

Didn't know the Tbook 16 Power was running Android 6 out-the-box, but good that you got the blobs from both devices working on cm-13.0.

Unfortunately, I don't have enough knowledge to suggest any fancy solutions to the cm-14.1/N blobs problem. Which annoys me, just got to keep studying :) 

Share this post


Link to post
Share on other sites
ViAlexSt    1
10 hours ago, Hi12Guy said:

I succesful boot BLISS ROM 7.x Nougat X86 on The Chuwi Hi12

Great news! Where can download your ROM? I have Chuwi HiBook Pro, will try to do the same...

Share this post


Link to post
Share on other sites
ViAlexSt    1

This link is known to me. It seems that I was happy too early: I thought that the Rom made for installation in TWRP. As Phoenix for Tbook 10S.
 

Share this post


Link to post
Share on other sites
Hi12Guy    1
21 hours ago, Hi12Guy said:

https://forum.xda-developers.com/android/software/x86-bliss-x86-pc-s-t3534657

 

 

Also the new Android X86 ISO boots fine... even more stable than bliss... Sound/Touch not working atm. Last Version I tried didn#t even boot. Now boots :)

 

7 hours ago, ViAlexSt said:

Patches for Linux 4.12 which on Chuwi Hi12 works sound and touch: https://github.com/kernins/linux-chwhi12

 

Thanks for the share, do you know how to merge it?

Share this post


Link to post
Share on other sites
THEHOLYG0D    0

I have a Hi10 Plus and I've already started syncing the Android-x86 Because it boots and there is issue only of touch, apart everything is stable. I found some various .fw files for touch support also I'll sync, but if someone would tell me how do I merge or build a kernel with these files, that'd be great..

23 hours ago, ViAlexSt said:

Patches for Linux 4.12 which on Chuwi Hi12 works sound and touch: https://github.com/kernins/linux-chwhi12

 

Share this post


Link to post
Share on other sites
KonstaT    3,949

Please take your Android-x86 (and Remix OS/Phonix OS/Bliss ROM/etc based on that) discussion somewhere else (e.g. open a new thread or something). It has nothing to do with what we're trying to achieve here.

Edited by KonstaT

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now


MoDaCo is part of the MoDaCo.network, © Paul O'Brien 2002-2016. MoDaCo uses IntelliTxt technology.