[Frosty]

For Jean-Baptiste: I’m not very good with Android and I did not attempt to replace mine. I just found a way to switch it from Chinese to English by clicking on the right icons (even though I could not read the text on the screen). So I just left it with the original Android install. I am sorry if this does not help!

For Frédéric: my serial number starts with Vi10PQ64G2215090**** (same as Jean-Baptiste above)

[Frosty]

I have not been able to solve the last remaining driver issue … still have two objects in Device Manager which don’t have correct drivers. In their Properties I can see these details:

(1) is in Other Devices, named “Generic SDIO Device”, has two Hardware IDs starting with ‘SD\VID’ (Standard Definition video driver?)
(2) is in Other Devices, named “Unknown Device”, has Hardware ID starting with ‘ACPI\BCM2E74’ (Advanced Configuration and Power Interface?)

The other odd thing: if I type in “camera” and open the standard Windows 10 Camera app, it works. There is a Camera object in Device Manager. But in Windows 10 “Scanners and Cameras” area there is no camera evident. I think Windows is using some kind of generic Intel camera driver. Any suggestions as to how I could find the right Camera driver? I’ve tried all the ones posted so far, without success.

[Frosty]

http://techtablets.com/2015/09/chuwi-vi10-windows-10-image-bios-update-and-drivers-released/

[Frosty]

When I talk about “manually installing” the drivers, what I mean is that I am not using a tool like Double Driver that others seem to like.  I’m kinda old-fashioned, so I unpack the .ZIP files, use Windows Explorer to look through the folders, then when I find the .INF file for the driver I want to install (.INF usually shows in Explorer with a file type of “Setup Information”), I right-click and choose the Install option.  The other method I have tried is to type in “DEVMGMT.MSC” and right-click, Run As Administrator … then find the ‘broken’ devices, right-click and select Update Driver Software, then Browse My Computer…, then navigate to the folder(s) where the driver(s) are, select the one which supposedly matches, and follow your nose.  A reboot every now and again helps too.  It still took me a couple of evening’s worth of mucking around to eventually sort it out.  Lots of dead ends.  I had to be persistent.

[Frosty]

I don’t want to give any advice which might involve flashing the BIOS.  I wasn’t prepared to do that sort of thing myself, as I didn’t want to risk a catastrophic problem if it wasn’t the right sort of firmware to match my hardware.  I was lucky that I was already running the latest BIOS version, so didn’t have to update it.

[Frosty]

Google is telling me that:

ACPI = Advanced Configuration and Power Interface

SD\VID might be Standard Definition video (?)

[Frosty]

I think there are different types of hardware.  So a solution which works for one person may not work for another.  I managed to solve my calibration issues and posted here about it:

http://techtablets.com/forums/topic/chuwi-vi10-cwi505-fresh-windows-10-enterprise-x86-driver-issues/

See the posts 4 and 5 in that thread.  Originally touch wasn’t working at all for me.  I had to get Philip’s touch drivers from here:

<span style=”color: #f84103;”>https://drive.google.com/file/d/0B_WhOdPMvW1OdjVic1J2elVGc28/view?usp=sharing</span&gt;

Then some mucking about with manually copying files might have helped.  I also deleted all previous calibration data and rebooted.  Then it all started working fine.

[Frosty]

Calibration done.  Not quite sure what the magic sauce was, but I did try manually copying the ‘icnfirmware.sys’ and ‘MY12C.sys’ files to C:\Windows\System32\drivers\ folder.  After mucking about with that a bit, I went into the Calibration screen of Windows and attempted to tap away on the X to get it calibrated.  Not much success.  Then (I think it was after a reboot) I went back into the Calibration screen, dumped all the previous calibration data, and then was able to very easily re-calibrate it successfully. Works really well now.

I still have two objects in Device Manager which don’t have correct drivers.  In their Properties I can see these details:

(1) is in Other Devices, named “Generic SDIO Device”, has two Hardware IDs starting with ‘SD\VID’ (so is this a video driver???)

(2) is in Other Devices, named “Unknown Device”, has Hardware ID starting with ‘ACPI\BCM2E74’ (Broadcom? bluetooth maybe???)

[Frosty]

Thanks to Phillip for his efforts!  I downloaded his S165 drivers:

https://drive.google.com/file/d/0B_WhOdPMvW1OdjVic1J2elVGc28/view?usp=sharing

Found the Touch driver (in the TP folder) he’d used, manually installed that using the supplied ‘dpinst32.exe’ driver installer package (right-click, Run As Administrator).  This replaced the existing KMDF driver with a new MY12C driver in the Human Interface Devices section.

RESULT:  Touch is now functioning … sort of … calibration is not-quite-right, but at least I am getting some response.

 

[Frosty]

Ahhhhh … PROGRESS!!!

I spent quite a while re-reading in this thread:

http://techtablets.com/forums/topic/vi10-s165c-drivers-available-from-chuwi/

Noticed this download, where someone helpfully made available the Broadcom drivers from their working install:

http://techtablets.com/wp-content/uploads/2015/10/S165-19-10-2015-19-30-57.zip

Downloaded those drivers.  Copied the Broadcom folder over to the tablet (via my USB-Ethernet dongle).  Navigated into the driver folders via Windows Explorer and found the setup file (OEM22.INF), right-click, Install, ignore the warning.  Reboot.  Loaded up Device Manager and AT LAST I can see a functional WiFi Adapter in the Networking section of Device Manager.

RESULT:  after connecting and entering my password, I now have working WiFi at last.

Now I just need to find the magic sauce to get Touch drivers to be recognised.

[Frosty]

Just noticed this thread:

http://techtablets.com/forums/topic/chuwi-vi10-pro-64gb-fix-restore-etc/

Perhaps I will try the approach of reinstalling Windows 8.1 first, then an in-place upgrade to Windows 10.

[Author]

Posts