Jump to content
KonstaT

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

Recommended Posts

@KonstaT

Hi,Thank you for your work. I have a similar device. iWork10 flagship.

Almost everything works with the kernel configs from vi10plus. But my Goodix touch screen is not working.

 I compiled your kernel and add the GT9XX config. No luck.  I have no idea how to fix it.  I try to use the gt9xx driver from other device and the latest kernel. Still no luck. I tried all my idea but still no luck.

 The device in ubuntu is GT9111 . Hope someone can help me.

Share this post


Link to post
Share on other sites
3 hours ago, G.H.Cheng said:

@KonstaT

Hi,Thank you for your work. I have a similar device. iWork10 flagship.

Almost everything works with the kernel configs from vi10plus. But my Goodix touch screen is not working.

 I compiled your kernel and add the GT9XX config. No luck.  I have no idea how to fix it.  I try to use the gt9xx driver from other device and the latest kernel. Still no luck. I tried all my idea but still no luck.

 The device in ubuntu is GT9111 . Hope someone can help me.

I don't know if this can help you in any way, but someone posted a Lineage OS 13 build for the iWork10 (http://bbs.51cube.com/forum.php?mod=viewthread&tid=308541&extra=page%3D1) and a Remix OS build as well (http://bbs.51cube.com/forum.php?mod=viewthread&tid=307920&extra=page%3D1). 

 

Share this post


Link to post
Share on other sites
On 6/21/2017 at 1:45 PM, PalmTrees said:

Too early to get excited, but Lenovo is planning to release an Android N 7.0 upgrade for the Yoga book (YB1-X90F/L) with the Intel z8550 SoC. (https://support.lenovo.com/dk/en/solutions/ht501098). Hopefully, this will happen and fingers crossed this will mean Android N on the Chuwi Vi10 Plus at some point, 

I believe it when I see it. AFAIK Intel hasn't released Nougat BSP for Cherry Trail so no idea how Lenovo is going to come up with such update.

18 hours ago, G.H.Cheng said:

@KonstaT

Hi,Thank you for your work. I have a similar device. iWork10 flagship.

Almost everything works with the kernel configs from vi10plus. But my Goodix touch screen is not working.

 I compiled your kernel and add the GT9XX config. No luck.  I have no idea how to fix it.  I try to use the gt9xx driver from other device and the latest kernel. Still no luck. I tried all my idea but still no luck.

 The device in ubuntu is GT9111 . Hope someone can help me.

Check your Ubuntu sources and see which driver it uses there and port it over.

Edited by KonstaT

Share this post


Link to post
Share on other sites
On 2017/6/26 at 3:46 PM, KonstaT said:

 

Check your Ubuntu sources and see which driver it uses there and port it over.

I tried ,the driver loaded but nothing happen. I checked dmesg and I can't find anything related. Sorry to disturb you, I don't have any experiment in porting a driver.

[email protected]_vi10plus:/ $ lsmod
Module                  Size  Used by
goodix                 12932  0
hid_sensor_hub         19171  0
atomisp_css2401a0_v21   835671  0
unicam_driver          99810  0
ov2680                 29099  1
ov2680b                23708  1
videobuf_vmalloc       13417  1 atomisp_css2401a0_v21
videobuf_core          24747  2 atomisp_css2401a0_v21,videobuf_vmalloc
8723bs               1835260  0
cfg80211              492050  1 8723bs
6lowpan_iphc           18591  0
ip6table_raw           12683  1
iptable_raw            12678  1
bt_lpm                 14345  0
rfkill_gpio            13280  0

I tried the driver below. 

android-3.18/drivers/input/touchscreen/goodix.c

kernel-4.0/drivers/input/touchscreen/goodix.c

Do you have any hint? Thanks for your prompt reply.

Share this post


Link to post
Share on other sites
3 hours ago, G.H.Cheng said:

I tried ,the driver loaded but nothing happen. I checked dmesg and I can't find anything related. Sorry to disturb you, I don't have any experiment in porting a driver.

I tried the driver below. 

android-3.18/drivers/input/touchscreen/goodix.c

kernel-4.0/drivers/input/touchscreen/goodix.c

Do you have any hint? Thanks for your prompt reply.

You have enabled CONFIG_TOUCHSCREEN_GT9XX & CONFIG_CC_TOUCHSCREEN_GT9110 in your defconfig, right?

I meant that find the kernel source code for that Ubuntu kernel where it's working(?) with and use the goodix driver from there.

Share this post


Link to post
Share on other sites
1 hour ago, KonstaT said:

You have enabled CONFIG_TOUCHSCREEN_GT9XX & CONFIG_CC_TOUCHSCREEN_GT9110 in your defconfig, right?

I meant that find the kernel source code for that Ubuntu kernel where it's working(?) with and use the goodix driver from there.

Yes, the driver is working in Ubuntu , but not working with this kernel. I don't find any log in dmesg.  I will try to enable CONFIG_TOUCHSCREEN_GT9XX & CONFIG_CC_TOUCHSCREEN_GT9110 in defconfig.

Thanks

Share this post


Link to post
Share on other sites
1 hour ago, G.H.Cheng said:

Yes, the driver is working in Ubuntu , but not working with this kernel. I don't find any log in dmesg.  I will try to enable CONFIG_TOUCHSCREEN_GT9XX & CONFIG_CC_TOUCHSCREEN_GT9110 in defconfig.

Thanks

Where's the source code for that Ubuntu kernel?

You won't see anything in dmesg if you haven't even built the driver into the kernel. Check dmesg on firmware it's actually working to see if there's anything interesting there.

Share this post


Link to post
Share on other sites
1 minute ago, KonstaT said:

Where's the source code for that Ubuntu kernel?

You won't see anything in dmesg if you haven't even built the driver into the kernel. Check dmesg on firmware it's actually working to see if there's anything interesting there.

I did built the driver into the kernel.  I use CONFIG_TOUCHSCREEN_GT9XX=y. Driver that work in ubuntu

130|[email protected]_vi10plus:/ $ dmesg | grep  "i2c"
[    0.486805] i2c_designware 808622C1:06: _SEM=1
[    0.486811] i2c_designware 808622C1:06: Share controller with PUNIT
[    0.531995] intel_soc_pmic_i2c i2c-INT33F4:00: PMIC IRQ Base:456
[    0.618073] intel_soc_pmic_i2c i2c-INT33F4:00: Failed to translate GPIO to IRQ
[    0.780456] i2c i2c-9: normal 7 bit addr failed
[    0.828499] i2c i2c-9: normal 7 bit addr failed
[    1.320752] i2c /dev entries driver
[    1.703461] rt5651_i2c_probe: i2c->addr before: 1a
[    1.703467] rt5651_i2c_probe: i2c->addr after: 1a
[    1.866218] -----cm3218--i2c--test--ok-
[    3.751876] ov2680b i2c-OVB2680:00: ++++ov2680b_probe++++
[    3.751892] ov2680b i2c-OVB2680:00: gmin: initializing atomisp module subdev data.PMIC ID 2
[    3.751896] ov2680b i2c-OVB2680:00: suddev name = ov2680b 0-0036
[    3.774126] ov2680b i2c-OVB2680:00: gmin_subdev_add gpio0 is ok.
[    3.781052] ov2680b i2c-OVB2680:00: gmin_subdev_add gpio1 is ok.
[    3.931881] ov2680b i2c-OVB2680:00: camera pdata: port: 1 lanes: 1 order: 00000002
[    4.035875] ov2680b i2c-OVB2680:00: register atomisp i2c module type 1
[    4.082706] ov2680 i2c-OVTI2680:01: ++++ov2680_probe++++
[    4.082713] ov2680 i2c-OVTI2680:01: gmin: initializing atomisp module subdev data.PMIC ID 2
[    4.082717] ov2680 i2c-OVTI2680:01: suddev name = ov2680 2-0010
[    4.104561] ov2680 i2c-OVTI2680:01: gmin_subdev_add gpio0 is ok.
[    4.111292] ov2680 i2c-OVTI2680:01: gmin_subdev_add gpio1 is ok.
[    4.214602] ov2680 i2c-OVTI2680:01: camera pdata: port: 0 lanes: 1 order: 00000002
[    4.217391] ov2680 i2c-OVTI2680:01: sensor_revision id = 0x2680!
[    4.217398] ov2680 i2c-OVTI2680:01: detect ov2680 success
[    4.217402] ov2680 i2c-OVTI2680:01: ################5##########
[    4.261301] ov2680 i2c-OVTI2680:01: register atomisp i2c module type 1
[    4.476632] i2c i2c-0: Failed to register i2c client rear:36 at 0x36 (-16)
[    4.484648] i2c i2c-0: failed to add I2C device OVB2680:00 from ACPI
[    4.492683] i2c i2c-2: Failed to register i2c client front:10 at 0x10 (-16)
[    4.500877] i2c i2c-2: failed to add I2C device OVTI2680:01 from ACPI

 

Share this post


Link to post
Share on other sites

It's confusing that the dmesg show nothing . So I guess it may related to the log above. Anyway thanks to your reply.

[email protected]_vi10plus:/ $ dmesg | grep  "gtp"
1|[email protected]_vi10plus:/ $ dmesg | grep  "GDIX"
1|[email protected]_vi10plus:/ $ dmesg | grep  "Goodix"
1|[email protected]_vi10plus:/ $ dmesg | grep  "Good"
1|[email protected]_vi10plus:/ $ dmesg | grep  "GTP"
1|[email protected]_vi10plus:/ $

 

Edited by G.H.Cheng
add

Share this post


Link to post
Share on other sites

dmesg : Working firmware 

<7>[    1.625948] Goodix INFO [email protected]: 2991 GTP driver installing...
<7>[    1.626370] Goodix INFO [email protected]: 2401 GTP Driver Version: V2.2<2014/01/14>
<7>[    1.626376] Goodix INFO [email protected]: 2402 GTP Driver [email protected]:21:57, Mar  2 2016
<7>[    1.626381] Goodix INFO [email protected]: 2403 GTP I2C Address: 0x14
<7>[    1.626470] Goodix INFO [email protected]: 1101 Guitar reset
<7>[    1.713855] Goodix INFO [email protected]: 1484 CTP_CONFIG_GROUP1 used, config length: 186
<7>[    1.716014] Goodix INFO [email protected]: 354 Driver send config.
<7>[    1.722593] Goodix INFO [email protected]: 1630 X_MAX: 1920, Y_MAX: 1200, TRIGGER: 0x01
<7>[    1.733881] Goodix INFO [email protected]: 2484 create proc entry gt9xx_config success
<7>[    1.734822] Goodix INFO [email protected]: 2508 GTP works in interrupt mode.
<7>[    1.734870] Goodix INFO [email protected]: 239 Applied memory size:2562.
<7>[    1.734875] Goodix INFO [email protected]: 207 I2C function: without pre and end cmd!
<7>[    1.734890] Goodix INFO [email protected]: 262 Create proc entry success!
<7>[    1.734895] Goodix INFO [email protected]: 2766 Esd started
<4>[    1.735144] i2c-core: driver [Goodix-TS] using legacy suspend method
<4>[    1.742270] i2c-core: driver [Goodix-TS] using legacy resume method
[    0.576092] i2c_designware 808622C1:06: _SEM=1
[    0.576099] i2c_designware 808622C1:06: Share controller with PUNIT
[    0.628037] intel_soc_pmic_i2c i2c-INT33F4:00: PMIC IRQ Base:456
[    0.981734] intel_soc_pmic_i2c i2c-INT33F4:00: Failed to translate GPIO to IRQ
[    1.148321] i2c i2c-9: normal 7 bit addr failed
[    1.197446] i2c i2c-9: normal 7 bit addr failed
[    1.734875] Goodix INFO [email protected]: 207 I2C function: without pre and end cmd!
[    1.735144] i2c-core: driver [Goodix-TS] using legacy suspend method
[    1.742270] i2c-core: driver [Goodix-TS] using legacy resume method
[    1.753621] ######register_i2c_client####
[    2.654659] i2c /dev entries driver
[    3.259871] rt5651_i2c_probe: i2c->addr before: 1a
[    3.259877] rt5651_i2c_probe: i2c->addr after: 1a
[    3.370183] -----cm3218--i2c--test--ok-

 

Share this post


Link to post
Share on other sites
On 28.06.2017 at 0:12 PM, G.H.Cheng said:

dmesg : Working firmware 

<7>[    1.625948] Goodix INFO [email protected]: 2991 GTP driver installing...
<7>[    1.626370] Goodix INFO [email protected]: 2401 GTP Driver Version: V2.2<2014/01/14>
<7>[    1.626376] Goodix INFO [email protected]: 2402 GTP Driver [email protected]:21:57, Mar  2 2016
<7>[    1.626381] Goodix INFO [email protected]: 2403 GTP I2C Address: 0x14
<7>[    1.626470] Goodix INFO [email protected]: 1101 Guitar reset
<7>[    1.713855] Goodix INFO [email protected]: 1484 CTP_CONFIG_GROUP1 used, config length: 186
<7>[    1.716014] Goodix INFO [email protected]: 354 Driver send config.
<7>[    1.722593] Goodix INFO [email protected]: 1630 X_MAX: 1920, Y_MAX: 1200, TRIGGER: 0x01
<7>[    1.733881] Goodix INFO [email protected]: 2484 create proc entry gt9xx_config success
<7>[    1.734822] Goodix INFO [email protected]: 2508 GTP works in interrupt mode.
<7>[    1.734870] Goodix INFO [email protected]: 239 Applied memory size:2562.
<7>[    1.734875] Goodix INFO [email protected]: 207 I2C function: without pre and end cmd!
<7>[    1.734890] Goodix INFO [email protected]: 262 Create proc entry success!
<7>[    1.734895] Goodix INFO [email protected]: 2766 Esd started
<4>[    1.735144] i2c-core: driver [Goodix-TS] using legacy suspend method
<4>[    1.742270] i2c-core: driver [Goodix-TS] using legacy resume method
[    0.576092] i2c_designware 808622C1:06: _SEM=1
[    0.576099] i2c_designware 808622C1:06: Share controller with PUNIT
[    0.628037] intel_soc_pmic_i2c i2c-INT33F4:00: PMIC IRQ Base:456
[    0.981734] intel_soc_pmic_i2c i2c-INT33F4:00: Failed to translate GPIO to IRQ
[    1.148321] i2c i2c-9: normal 7 bit addr failed
[    1.197446] i2c i2c-9: normal 7 bit addr failed
[    1.734875] Goodix INFO [email protected]: 207 I2C function: without pre and end cmd!
[    1.735144] i2c-core: driver [Goodix-TS] using legacy suspend method
[    1.742270] i2c-core: driver [Goodix-TS] using legacy resume method
[    1.753621] ######register_i2c_client####
[    2.654659] i2c /dev entries driver
[    3.259871] rt5651_i2c_probe: i2c->addr before: 1a
[    3.259877] rt5651_i2c_probe: i2c->addr after: 1a
[    3.370183] -----cm3218--i2c--test--ok-

 

I  was adding gt9xx driver to the kernel and works fine.

Try my gt9xx driver 

gt9xx.tar.bz2

Share this post


Link to post
Share on other sites
14 hours ago, mirek190 said:

I  was adding gt9xx driver to the kernel and works fine.

Try my gt9xx driver 

gt9xx.tar.bz2

Thank you very much. This driver loads.  But I still need to find the right configuration. Anyway finding a right driver that loads is a good sign

EDIT:

Fixed by setting #define GTP_DRIVER_SEND_CFG   0      

It can use the config that already have. Now the touchscreen work flawlessly. Thank you.

@mirek190 @KonstaT

Edited by G.H.Cheng
update

Share this post


Link to post
Share on other sites

sorry for getting off topic, but could something like this be done for acer predator 8? there is source code on acer's page but i have no knowledge to do what you did @KonstaT. if you ever decide to give it a try, i'll be your tester

Edited by dvijetrecine

Share this post


Link to post
Share on other sites
17 hours ago, dvijetrecine said:

sorry for getting off topic, but could something like this be done for acer predator 8? there is source code on acer's page but i have no knowledge to do what you did @KonstaT. if you ever decide to give it a try, i'll be your tester

I'm not going to do it of course because I don't have that device. Nothing stopping someone else from stepping up.

Good to know there's yet another Cherry Trail device with kernel source.

56 minutes ago, BacktotheFuji said:

Ooh just seen that Medion have an atom tablet running Marshmallow now with an official OTA upgrade :)

https://www.medion.com/gb/shop/tablets-medion-tablet-lifetab-p10505-md-99928-titan-130020481.html

That's exactly where binary drivers in this ROM are extracted from...

Edited by KonstaT

Share this post


Link to post
Share on other sites
On 02/07/2017 at 7:06 PM, KonstaT said:

I'm not going to do it of course because I don't have that device. Nothing stopping someone else from stepping up.

Good to know there's yet another Cherry Trail device with kernel source.

That's exactly where binary drivers in this ROM are extracted from...

Doh! :D

Share this post


Link to post
Share on other sites

Finally fixed camera :-)

- fixed focusing

- color spots

- distortions

- quality

Like see one the screen after and before - the same distance from the wall ...

Fixed files soon

 

20170724_024108.jpg.c7ec600e30939d88b9208b2f08341d29.jpg

Edited by mirek190
  • Upvote 4

Share this post


Link to post
Share on other sites

hi,

any update regarding this rom? is it stable to install?

another thing. i have hi10 pro (dual boot) and removed android and now have only windows10, how to install TWRP to install the rom?

Share this post


Link to post
Share on other sites
12 hours ago, samnasser said:

hi,

any update regarding this rom? is it stable to install?

another thing. i have hi10 pro (dual boot) and removed android and now have only windows10, how to install TWRP to install the rom?

It's perfectly usable as a daily driver IMO. Take note that this ROM only works on the first batch (of three or more) Hi10 Pro devices.

Depending on how you converted your device into single boot, you probably need to install stock firmware with Intel Platform Flash Tool first.

Share this post


Link to post
Share on other sites
6 hours ago, KonstaT said:

It's perfectly usable as a daily driver IMO. Take note that this ROM only works on the first batch (of three or more) Hi10 Pro devices.

Depending on how you converted your device into single boot, you probably need to install stock firmware with Intel Platform Flash Tool first.

+1 it is working really well. 

Are you going to keep updating the security patch/merge latest commits? Not on a montly basis, but just every once in a while? 

Share this post


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

Are you going to keep updating the security patch/merge latest commits? Not on a montly basis, but just every once in a while? 

Yes, probably as long as I have the device.

Security patch level is somewhat artificial if kernel is not patched against all the CVEs. Cherry Trail devices run rather strange Linux version (3.14 non-LTS) so it's massive PITA to track down those patches. cm-13.0 branch is already dead what comes to fixes and features (mostly just translations and security patches merged these days) and it's only going to get worse with Android O being out soon.

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.