Touchscreen for Win11 on HP C1030

Support Windows Support
1

Hi, i’am new to this forum.

I’ve purchased the HP C1030, got the coolstar’s drivers, including the bought SOF audio drivers. Everything except touchscreen is working. I’ve tried to reinstall multiple times, but no success. I know the hardware is working properly, in Chrome OS it worked fine.

I’ve checked the forum and couldn’t find this issue adressed before. Can you please help me?

With regards,
Henk

2

Touchscreen worked on Jinlon on Windows 11 OOTB. Didn’t have to install any drivers. Windows 11 installed the touchscreen driver for me and it worked.

3

Please be sure to read the documentation on asking for information, I have no idea what device this is.

Did you install the driver linked in coolstars guide?

https://github.com/coolstar/driverinstallers/raw/master/crostouchscreen/crostouchscreen.2.9.5-installer.exe

You also need chipset drivers, also linked in coolstars guide

4

Thank you for your reply. I followed the complete coolstar guide and installed chipset drivers and the touchscreen and touchpad drivers. I got everything working, except touchscreen.

I’ve already tried a couple of times with reinstalls of windows.
I’v tried to state the type of device as well as I can. How can I provide you with more info?

5

SMH, why would you do that?

This is Windows 101 stuff, but is the touchscreen listed in Device Manager? If so, what is the status? Error message?

6

Thanks for asking. I am Dutch, so my English is not native :wink:

I am aware of the Windows 101 stuff, hence why I tried multiple windows reinstalls. I have 4 different devices. 3 HP C640 Pro’s and one C1030.

  1. I used a generic image on the C640 (Aomei backup of a sysprepped working system) to be able to use all my programs instantly. After the install, I had to install the drivers from the Coolstar’s site and purchase an audio driver. It worked.
  2. I used the same method for the C1030, but it didn’t work. So I created a sysprepped image off the C640 and tried that one. Wasn’t completely working with touchpad, touchscreen and audio. I installed the Jinlon drivers from the Cool star’s website, but it still didn’t work.
  3. I thought my image was defective, so I used a clean install of win11, windows update and then the Coolstar’s website drivers. Still no luck.

So that’s why multiple Win11 installs. The C640 are wrking great, but on the C1030 there are some devices that show errors.

I hope I described it better now :slight_smile:

7

well we can’t help if we don’t know what those are

8

2024-07-26_15-49-39
It’s in Dutch, but it says:
unknow device on the top one’s and the error is at the Elan touch screen

9

ok, well what’s the error (in English) for the Elan touchscreen?

and what are the 3 unknown devices?

10

I have installed the sound drivers and some of the unknown devices are gone. Here are the one’s that are left:

In Human interface devices:
I2C HID-device
The device doesn’t start (code10)
the device returned an invalid HID descriptor

in “other devices”
location: at Intel(R) Serioal IO SPI Host Controller - 02AA
The drivers for this device are not installed. (code 28)
there are no compatible drivers for this device
Click update driver to search for a driver for this device

11

Jinlon has 5 different touchscreen options. What is the BIOS_DEVICE_NAME property for yours?

12

For the HID device: _SB.PCI0.I2C1.H05D

For the “unknown device” _SB.PCI0.SPI0.S001

13

that’s less than helpful.

cbmem log?

14

I am sorry, I am not sure how to generate a log…
I’ve downloaded the console and the driver, unpacked and run the following command:
cbmem.c
But I only get a question with which program to open the file. Can you help me please?

15

From windows, simply open a command prompt, navigate to the crosec dir under program files, and run cbmem.exe -1 > cbmem.log

16

Yeey! Thank you for your help.
Here is the doc. I couldn’t paste a file, so here is the text of the parts mentioned above:
[INFO ] _SB.PCI0.I2C1.H05D: Goodix Touchscreen at I2C: 00:5d
[INFO ] _SB.PCI0.SPI0.S001: SPI Device at SPI: 00

17

Only thing I can think of is that it needs longer delays for the driver under Windows. Ping me on Discord for a test build

18

I’ve tried pinging you on Discord, can’t send a DM :frowning:
But I think you are busy?