TouchScreen Goodix GDIX1002:00 and Accel BOS0200 in Lenovo D330

[Carlos Lopez]

Hi,

I'm trying to build the OREO-x86_64 8.1 rc2 with the updated drivers (including the  updated goodix.c with the GDIX1002:00 stanza from the linux kernel and marking in the defconfig the bmc150 as it seems to be the driver of the accel)

Everithing works in Ubuntu 18.04 (despite a 90º off orientation already fixed with a udev quirk) but in ANDROID it boots and the lsmod shows both modules (goodix and bmc150accel) but they don't work at all.

In the dmesg both devices are shown as ACPI devices but that's it . no more entries appart from that.

I already tried to rmmod and modprobing both drivers (and the hid_multitouch) but no luck so far.

The build of the source doesn't throw nothing significant (AFAIK) but an error with a broadcom wifi module which i don't need and therefore I disabled in the configdef.

Appart from that and a problem i had with the aftergrub boot scrambling the image in the installation option and every TTY messages (which i solved adding in grub [set gfxpayload=1200x1920]), my native res,  the system boots ok and almost everything works (wifi, bluettooth, GPU, keyboard, usb, mouse/trackpad). Only the sleep don't seems to turn off the screen (just blacking it).

Any advice about the touchscreen and the accelerometer.

Thank you folks, and good work!

[Chih-Wei Huang]

Carlos Lopez <carloscar...@gmail.com> 於 2018年11月28日 週三 下午8:20寫道：

>
> I'm trying to build the OREO-x86_64 8.1 rc2 with the updated drivers (including the updated goodix.c with the GDIX1002:00 stanza from the linux kernel and marking in the defconfig the bmc150 as it seems to be the driver of the accel)
>
> Everithing works in Ubuntu 18.04 (despite a 90º off orientation already fixed with a udev quirk) but in ANDROID it boots and the lsmod shows both modules (goodix and bmc150accel) but they don't work at all.
> In the dmesg both devices are shown as ACPI devices but that's it . no more entries appart from that.

Check if you have these files after installed the drivers?

ls /sys/bus/iio/devices/iio:device*/in_accel_*

Do the files exist in Ubuntu 18.04?

Also check 'getprop ro.hardware.sensors'.

> I already tried to rmmod and modprobing both drivers (and the hid_multitouch) but no luck so far.
>
> The build of the source doesn't throw nothing significant (AFAIK) but an error with a broadcom wifi module which i don't need and therefore I disabled in the configdef.
>
> Appart from that and a problem i had with the aftergrub boot scrambling the image in the installation option and every TTY messages (which i solved adding in grub [set gfxpayload=1200x1920]), my native res, the system boots ok and almost everything works (wifi, bluettooth, GPU, keyboard, usb, mouse/trackpad). Only the sleep don't seems to turn off the screen (just blacking it).
>
> Any advice about the touchscreen and the accelerometer.

Does touchscreen work in Ubuntu 18.04?

--
Chih-Wei
Android-x86 project
http://www.android-x86.org

[Carlos Lopez]

The touchscreen and the accelerometer works in ubuntu 18.04 by default. (the only thing that doesn't is the rotation that has to be adjusted via UDEV rule cause the orientation is 90º off.)

I'll try the commands at home later and I'll post a dmesg in both systems. (tell me if i can post anything else that could be useful.

thanks folks.

[Carlos Lopez]

> Check if you have these files after installed the drivers?
>
>
>
> ls /sys/bus/iio/devices/iio:device*/in_accel_*
>

They exist in android

ls -l /sys/bus/iio..
-rw-r--r-- 1 system system 4096 2018-11-29 19:19 /sys/bus/iio/devices/iio:device0/in_accel_scale
-rw-r--r-- 1 system system 4096 2018-11-29 19:19 /sys/bus/iio/devices/iio:device0/in_accel_x_raw
-rw-r--r-- 1 system system 4096 2018-11-29 19:19 /sys/bus/iio/devices/iio:device0/in_accel_y_raw
-rw-r--r-- 1 system system 4096 2018-11-29 19:19 /sys/bus/iio/devices/iio:device0/in_accel_z_raw

>
>
> Do the files exist in Ubuntu 18.04?
>
>
>
> Also check 'getprop ro.hardware.sensors'.
>
>

This returns
"iio"

> Does touchscreen work in Ubuntu 18.04?
>
>

Yep, the dmesg tells in UBUNTU (attached)

[   11.364807] Goodix-TS i2c-GDIX1002:00: ID 927, version: 105b
[   11.369328] input: Goodix Capacitive TouchScreen as /devices/pci0000:00/0000:00:16.3/i2c_designware.1/i2c-2/i2c-GDIX1002:00/input/input19

in Android it doesn't show up (attached)

thanks in advance  Folks,

[Chih-Wei Huang]

Carlos Lopez <carloscar...@gmail.com> 於 2018年11月30日 週五 上午3:51寫道：

> > Check if you have these files after installed the drivers?
> > ls /sys/bus/iio/devices/iio:device*/in_accel_*
> >
> They exist in android
>
> ls -l /sys/bus/iio..
> -rw-r--r-- 1 system system 4096 2018-11-29 19:19 /sys/bus/iio/devices/iio:device0/in_accel_scale
> -rw-r--r-- 1 system system 4096 2018-11-29 19:19 /sys/bus/iio/devices/iio:device0/in_accel_x_raw
> -rw-r--r-- 1 system system 4096 2018-11-29 19:19 /sys/bus/iio/devices/iio:device0/in_accel_y_raw
> -rw-r--r-- 1 system system 4096 2018-11-29 19:19 /sys/bus/iio/devices/iio:device0/in_accel_z_raw
>

> > Also check 'getprop ro.hardware.sensors'.
>
> This returns
> "iio"

That's fine. The driver is loaded and the
sensor HAL is set up correctly.

Install a sensors testing app and see
what values was retrieved from g-sensor.
You may need to calibrate it.

> > Does touchscreen work in Ubuntu 18.04?
> >
> Yep, the dmesg tells in UBUNTU (attached)
> [ 11.364807] Goodix-TS i2c-GDIX1002:00: ID 927, version: 105b
> [ 11.369328] input: Goodix Capacitive TouchScreen as /devices/pci0000:00/0000:00:16.3/i2c_designware.1/i2c-2/i2c-GDIX1002:00/input/input19

Nice. Maybe Ubuntu has applied additional patches.
Let me check.

> in Android it doesn't show up (attached)

[Carlos Lopez]

no luck with the sensor

El viernes, 30 de noviembre de 2018, 1:38:50 (UTC+1), Chih-Wei Huang escribió:

Carlos Lopez <carloscar...@gmail.com> 於 2018年11月30日 週五 上午3:51寫道：
> > Check if you have these files after installed the drivers?
> > ls /sys/bus/iio/devices/iio:device*/in_accel_*
> >
> They exist in android
>
> ls -l /sys/bus/iio..
> -rw-r--r-- 1 system system 4096 2018-11-29 19:19 /sys/bus/iio/devices/iio:device0/in_accel_scale
> -rw-r--r-- 1 system system 4096 2018-11-29 19:19 /sys/bus/iio/devices/iio:device0/in_accel_x_raw
> -rw-r--r-- 1 system system 4096 2018-11-29 19:19 /sys/bus/iio/devices/iio:device0/in_accel_y_raw
> -rw-r--r-- 1 system system 4096 2018-11-29 19:19 /sys/bus/iio/devices/iio:device0/in_accel_z_raw
>
> > Also check 'getprop ro.hardware.sensors'.
>
> This returns
> "iio"

That's fine. The driver is loaded and the
sensor HAL is set up correctly.

Install a sensors testing app and see
what values was retrieved from g-sensor.
You may need to calibrate it.

The apps tell me "waiting for the sensor to be available " or related.

So no available sensor 

 

> > Does touchscreen work in Ubuntu 18.04?
> >
> Yep, the dmesg tells in UBUNTU (attached)
> [   11.364807] Goodix-TS i2c-GDIX1002:00: ID 927, version: 105b
> [   11.369328] input: Goodix Capacitive TouchScreen as /devices/pci0000:00/0000:00:16.3/i2c_designware.1/i2c-2/i2c-GDIX1002:00/input/input19

Nice. Maybe Ubuntu has applied additional patches.
Let me check.

Any news with this ?

Thanks folks

[Ikhsan Setiawan]

hey carlos,

i got the same d330 but when boot i just got black screen,it can only boot with nomodeset.

any advise to get hwaccel to work?

thank you,

[Carlos Lopez]

Weird. 

Are you using the 64 rc2 image ?

To correct the resolution I edit grub and add a line with

Set gfxpayload=1200x1920

I saw in a forum that some people used another sentence to ensure the brightness wasn't zeroing after grub bit I never had that problem. I'll try to find the line. 

Secure boot disabled I guess 

--
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 andro...@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.

[Carlos Lopez]

Before any other test check you disabled Secure boot in your bios.

After that

Set gfxpayload=1200x1920 to correct the resolution  (in the next line of options, don't put this in the same line of "nomodeset")

you can try "acpi_osi=Linux" and/or "acpi_backlight=vendor"   instead of "nomodeset"

The HWAccel works for me but as you can see in the thread the touchscreen doesn't.

Tell me in you get to make it work and you find something about the touchscreen.

If you try ubuntu i can pass you a quirk to fix the wrong orientation sensor behaviour

[Ikhsan Setiawan]

im using the latest rc2 64, and pretty sure secure boot was disabled.

 

 in ubuntu with default kernel everything was working fine except for sleep, but if i upgrade the kernel to 4.16 onward i'll also got the black screen.

will try your advice in a moment, i'll get back after that.

thank you,