yashsingh1/xdaforums huggingface dataset:
[General Topics] Droid_Nut:
Okay, I have the Chuwi hi10, dual boot Android and Windows 10. I will have to run live CD and run Gparted and take a look at the Partition Structure. I suppose I will be doing a total backup with Clonezilla before I do anything.
[General Topics] silv3rfox:
[MENTION=3816568]Myself5[/MENTION] How's the battery life? And I guess, technically it's possible to install Android-x86 on it right?
[General Topics] Myself5:
That sounds like a good plan. Clonezilla backup is what I went for too.

Battery life is great, i'd say better than Windows. Can't give you any numbers though because I didn't really pay attention to it yet.

Android-x86 is technically possible and with the Linux drivers even easier but I havn't looked into that yet.
[General Topics] Mr. Joop:
Hey guys happy to see there is interest in this tablet. I do got the dualboot version too.

To install Android i found this:

jonathansblog. co.uk/ factory- restore- android- on- chuwi- hi10

After i personally Installed remix OS

konstakang.com /devices /chuwi_vi10plus /RemixOS/

When I installed Ubuntu, just Ubuntu Started, Android stuck, i found a solution here:

github.com /floe /tuxblet
[General Topics] Mr. Joop:
I Just cant figure out this one:

Unfortunately, this still causes the Android install to hang on boot after Linux has been installed. I was assuming, for a very long time, that this is also an EFI-related problem. However, after multiple factory resets (see https://forum.chuwi.com/thread-2341-1-1.html and https://01.org/node/2463 for instructions), I finally found out that the problem is related to the very eager Ubuntu automounter, which grabs any ext4 filesystem it can find and mounts it read-write.

Of course, this shouldn't be a problem in theory, but this also happens for the Android system/data/etc. partitions, and whatever Ubuntu does to the ext4 FS when it's mounted, causes Android to croak. This means that even just booting a Ubuntu Live System from USB one single time will likely render the Android installation unbootable.

I've finally managed to fix this by setting the respective UUIDs to noauto in /etc/fstab as follows:

# do _not_ automount the Android partitions

UUID=57f8f4bc-abf4-655f-bf67-946fc0f9f25b /none ext4 ro,noauto 0 0

UUID=57f8f4bc-abf4-655f-bf67-946fc0f9f25b1 /none ext4 ro,noauto 0 0

UUID=57f8f4bc-abf4-655f-bf67-946fc0f9f25b2 /none ext4 ro,noauto 0 0

UUID=57f8f4bc-abf4-655f-bf67-946fc0f9f25b3 /none ext4 ro,noauto 0 0

If you look closely, you will notice that entries 2-4 are not actually proper UUIDs, they have an additional digit from 1-3 at the very end. The reason for this is that all the Android partitions (system, cache, data, config) have the same UUID and show up with the extra digit when the automounter grabs them. I'm not sure if this UUID duplication might actually be the root cause...

Unfortunately he does not explain how to no auto mount this partitions without a live CD and / or it is going to work even if Ubuntu installed is.
[General Topics] nikmag:
Hi everybody

Did kernel 5.1 resolve any problem. I use mint 19 but it seems that nothing happened
[General Topics] Myself5:
5.1 includes the touchscreen fix on it's own so you don't need to use the kernel I provided anymore.
[General Topics] nikmag:
Thanks for your reply. I had 5.09 and I installed 5.1 but no touchscreen activation. I had to return to 5.09. Any update for Bluetooth drivers? I installed them manual, it seems to be active but cannot see any Bluetooth device . Also the problem with the bios or boot screen is always in vertical position and not touchscreen or other way to select OS. I use windows 10 and Mint 19.1 Thanks again.
[General Topics] Myself5:
So it does work with my 5.09 kernel though, right? Otherwise you'd have forgotten to install the touch drivers (see the OP on how to do that).

Bluetooth works flawless for me on Arch. Maybe Mint has some other packages that don't fully work with the chip yet?

As for Grub: there's nothing we can do about that. As it currently stands grub has no support for touchscreens or screen rotation. You could try different UEFIs (rEFInd comes to mind here) but other than that it's not possible. I thought about possibly mapping the volume buttons to up/down for selection, but that would still leave us without an enter key.

Although, now that I think about it again: it might be possible to register the windows touchkey as "enter". I guess I'll take a look into that
[General Topics] nikmag:
Actually I did not use your 5.09 kernel. I had already done a successful procedure with different kernels before reading your post. Yes probably is Mint issue. I need to find some time to install Arch. If you manage to do something with buttons it will be wonderful. I boot to Mint and then with a command a switch to win10. Are you pleased with the active pen? I really thank you for your support. I would also like to help if I can.
[General Topics] Myself5:
According to a quick Google search custom keymapping for grub seems to be harder than expected. rEFInd seems to have touch support for some tablets though. I might look into that instead.

The "active Pen" on Windows is useless because it's not "active". It does get prefered over your hand, but the Hi10 Air doesn't have proper pen support. So the 256 pressure level touchpen they sell you is effectively as good as your finger. There is no pressure sensitivity support. On Linux this get's even worse because the pen is apparently using a different kind of calibration, so if you use it it's horribly offset. I was looking to use it for Notes during lectures, which is impossible to do. Even on Windows it's just not working. I've been in contact with my contact at Chuwi (who also sent me the device) and he just kept on talking around the topic. He never officially claimed the Pen would be supported but also never denied it. All he did was keep on sending me different touch drivers to "make the pen work" (although the definition of the term "work" can mean everything here).

TL;DR: Not pleased AT ALL.

P.S: I just updated the OP. the 5.1 kernel is released and works flawless on my Hi10 Air.
[General Topics] heenry20:
Hey everyone.

Can't make touchscreen work even on 5.1.2

see some screenshots:

https://imgur.com/598zrHM

kernel version:

https://imgur.com/qGtHJoc
[General Topics] Myself5:
So which tablet do you have? A normal Hi10 Air?
[General Topics] heenry20:
Yes, running kde neon.
[General Topics] nikmag:
M5 you are right, the finger is much better than 'active' pen! I bought also nebo app for recognition but the pen is totally invisible. Probably you checked drivers from you know https://forum.chuwi.com/thread-6861-1-1.html. It will be a big help if you manage to do something with rEFInd . Thanks
[General Topics] nikmag:
Another issue is that the screen in bios and Lightdm (login screen) is always in vertical position. I use keyboard and it is not so easy during booting. Automatic rotation works in Mint 19.1 xfce after login. What I do is to login automatically with no password. Then from Mint I can switch to Windows.
[General Topics] Myself5:
Did you follow the OP instructions for lightdm rotation?
[General Topics] nikmag:
The instructions mention "Now configure the Desktop Manager to start it after login." The problem is before login as well as bios too.
[General Topics] Arxym:
Hello. Its been 3 days I have been trying to fix the touchscreen in various Linux distros. I haven't been successful even once. I do everything you've mentioned and on that link too with the silead firmware. I can't figure out. Can anyone please provide me a simplified way or steps? I will be really thankful to you!
[General Topics] StarClosure:
Hi Arxym. I'm new to troubleshooting hardware on Linux, but I've made some progress. I think I had the same issue as you with the touchscreen. I took a look at the output of dmesg and found that the silead module was expecting a different firmware file name. I went to the /lib/firmware/silead folder and copied the firmware to the expected name:

sudo cp gsl1680-chuwi-hi10-air.fw mssl1680.fw

This got the touchscreen "working", upon reboot. Of course now the mapping is wrong. It maps upside-down and to the top-left corner of the screen :D . I'll keep you posted if I figure out how to fix this.
[General Topics] Myself5:
That would imply that your device isn't detected as a Hi10 Air by the parameters I set.

Can you please PM me the output of

dmidecode | more

?

Preferably post it on some pastebin site like paste.myself5.de. Thanks in advance^
[General Topics] Myself5:
Thanks to [MENTION=9965076]StarClosure[/MENTION]s testing I was able to figure out that there are multiple variants of the Hi10 Air and that some of them are not detected by the Kernel due to different namings in the DMI configs.

Based on information I had for my device and from StarClosure I built a new version with different detection. To everyone having issues please try to install the build from here: https://dl.myself5.de/Hi10Air/

You can install it with

sudo pacman -U *packagename*

and follow it up by updating the grub config (quick google search will help you here).

If this still doesnt work for some people please let me know. Also preferably attach the output of

sudo dmidecode | more

right away on that report.
[General Topics] Arxym:
Hey there mate!

Hello everyone!

So yeah, after that day, I managed to fix the touchscreen on Linux and used it for a while. Disappointed. Very much. None of the Linux distros have a good touch support and the WiFi is pretty awful too.

So, I managed to get Android working on the chuwi hi 10 air. No bugs. Fully functional and rock solid stable android. Touchscreen fully functional. Tutorial coming soon.
[General Topics] JonanomisK:
Hey there [MENTION=5245443]Arxym[/MENTION] , any word on when a tutorial on installing Android in the hi10 air will be out? Thanks!
[General Topics] aveemashfaq:
Hi guys. I am waiting for my chuwi hi10 air to arrive and stumbled upon this thread.

I have some experience with linux on i tel atom tablets as my previous tab was acer switch.

Regarding pen being out of calibration, you need to run

to see what devices are recognized as pointer. Then we can use xinput calibrator package to calibrate all the individual devices. My previous device acer switch had the same silead touchscreen and using evdev driver instead of libinput helped me a lot.

Regarding linux with good touchscreen support, gnome is miles ahead of the competition. I haven't tested fedora or arch but ubuntu was snappy enough to be used as daily driver. It also has support for screen rotation natively. And your login screen will also inherit the same orientation as your desktop.

If you want to implement screen autorotation in other DEs, you need to install iio-sensor-proxy package and then get a script.

You will truly be astounded by using gnome/ubuntu on tablet as far as usability is concerned. Its miles ahead of even windows 10. Glad to help out if any help needed.
[General Topics] Myself5:
Thats not going to work. The device is not separating between Finger and Touchpen input. It doesn't have any special digitizer for this.

TL;DR: Calibrate it for Pen -> Finger will be offset

Calibrate it for Finger -> Pen will be offset

Also with the HiPen 2 (Chuwis recommended Pen) you wont have any Pressure sensitivity or Palm rejection, simply because the panel doesn't support it.
[General Topics] aveemashfaq:
Hmm. Interesting. I am having a tough time believing this because pen uses a different technology from touchscreen. Do you mind sharing the output of xinput --list

And how is the calibration of touchscreen on wayland and what drivers are you using? For me, the touch was not calibrating in libinput driver in xorg. I had to use evdev. BTW, I used the script to extract windows driver and convert it into .fw file. Maybe that was why I had conflict with drivers.

And please try gnome and share results. I think you will find gnome to be awesome with touchscreen. Not sure about if you will face problems with wayland though because ubuntu uses xorg
[General Topics] Myself5:
Would gladly share the xinput output if my tablet didnt decide to kill grub after running out of battery lately. This thing just keeps on giving. Iirc xinput would only report silead_ts though (well and mouse and keyboard and that stuff). I'm using the latest windows drivers converted (the ones linked in OP). Thats the only available driver anyways. I hate gnome as well as Ubuntu with a passion so thats not going to happen. #ArchMasterrace. I experimented with a few DEs in the initial days though. Unity was somewhat fine, Deepin was the best in terms of DPI and rotation friendlyness. HOWEVER: both were TERRIBLE in terms of performance. Couldn't do a single thing without huge lags.

P.S: The touchscreen doesn't have a digitizer. There is no different input technology. Whereas it SOMEHOW detects the Pen which is provable because it prefers the pen input over your finger input and because the evdev border on the pen are offset from the finger (max is 1930 vs 1980) the Pen input is not labeled as such inside the OS on both, Linux and Windows. There is no seperate input device for the Pen listed and Windows does not detect the tablet as "compatible with Pen input".

I spent a lot of time trying to figure exactly this out, so I am 99% sure I am right on this. If there is anything I possibly missed or if you have any other ideas though, please don't hesitate to hit me up because I would love to get this working too.
[General Topics] aveemashfaq:
Today's laptops are making do without in-built battery (CR2032) for maintaining time and keeping BIOS settings alive. This means that whenever your battery falls to zero, the BIOS settings will reset to default and time and date will also vanish. I guess that is the reason grub is not working. The whole setup is present there but boot order is reset and hence you are booting into Windows (maybe)

Unity and Deepin are really very heavy weight so using it is out of contention. I am on the same boat as you and hated gnome a lot. Infact, I use XFCE as my daily driver because for how much screen real estate gnome eats up and the non-conventional layout. But trust me, I have used my tablet with cinnamon, kde, xfce, lxqt and gnome for more than 2 months and once you are on a touchscreen, gnome is a revelation.

And I remember reading somewhere that ubuntu 19.04 has performance optimizations to speed up responsiveness. I did not try fedora or arch to validate this but gnome in ubuntu 19.04 feels very snappy with minimal lags. The only time you are reminded that you are using a low power PC is the app load times. Rest, I dare say it is as good as XFCE in performance.

The finger input is 1930x1080 to accommodate for the touch windows key whereas the pen only reads 1920x1080. This proves that there is a separate technology powering the pen which is different from touch screen. You just have to calibrate individual devices separately in the config files (the 10-evdev.conf file) and it would work.

Can you please post the output of lshw and xinput --list when you manage to get your linux going again. And trust me, try live booting ubuntu 19.04. You are in for a surprise.
[General Topics] Myself5:
myself5@M5Hi10Air ~ $ sudo lshw | haste

https://paste.myself5.de/fVFR3nffEx

myself5@M5Hi10Air ~ $ sudo xinput --list | haste

https://paste.myself5.de/r66vVHi3oj
[General Topics] Lookanio:
[MENTION=3816568]Myself5[/MENTION] Thank you for how-to and all your contribution. Your guide assured me that I can have linux on Hi10 Air and was main reason I bought the tablet. It arrived to me a few days ago and then I started linux installation which mostly went quite smooth. I had only the same problem as StarClosure but with you custom linux kernel, touchscreen is working :)

Unfortunately I can't get working automatic rotation :( When I run 2in1screen, I get:

ls: cannot access '/sys/bus/iio/devices/iio:device*/in_accel*': No such file or directory
Unable to find any accelerometer.

I checked dmesg and found:

bmc150_accel_i2c i2c-BOSC0200:00: Invalid chip 3

which, as I suppose, is the root cause. Here is my dmidecode:

hastebin.com/ififexogaq

I would really appreciate any help. I tried to figure out what's wrong but no success.
[General Topics] Myself5:
Can you also get an

sudo lshw

? I've seen zhis issue before on another users device but his eMMC suddently died so we could look into it any further.

From the looks of it, it appears that you have a different rotation sensor than I do.
[General Topics] Lookanio:
Yes, sure, here is my lshw:

https://pastebin.com/vi84zNga
[General Topics] aveemashfaq:
Hi guys. Just got my Chuwi delivered today. I have installed Ubuntu in dual boot mode but I cannot make boot default to Ubuntu. I can manually go to UEFI and select boot to Ubuntu manually but if I change the boot order, it resets everytime and boots to Windows.

Any ideas, guys?
[General Topics] Lookanio:
I had the same issue after installation. I solved it with combination of efibootmgr and AFAIR (but not sure) disabling in BIOS (Advanced -> Trusted Computing): Platform Hierarchy, Storage Hierarchy.
[General Topics] aveemashfaq:
Finally, I backed up the existing file system and Windows and did a deep dive into Linux. I have some strange observations to report. When I installed Ubuntu 18.04 LTS, sound didn't work because of kernel 4.12. Next stop was Fedora. I clean formatted and installed Fedora and ran into strange issues. For some reason, the BIOS assumes that it has Android installed and puts that as boot priority 1 and then comes Fedora. So everytime, boot failed. I had to select at every boot that I want to boot into Fedora. Everything worked fine except for touchscreen. Libinput is a mess. No matter what I do, it would not accept touchscreen calibration. Tried and gave up because even if I could figure it out somehow, I would still have issues with boot failing everytime.

I came to Ubuntu 19.04 and everything works except for wifi. For some reason, wifi decided to not work at all. It has the firmware binary files, I also tried replacing the firmware files with the ones from Fedora but wifi is not working for some reason no matter what I try. Currently frustrated due to lack of wifi. Any solutions, guys?

It seems that Chuwi actually planned to make an Ubuntu version of their device because Boot priority hard coded in BIOS is Windows > Ubuntu > Android. Any other OS is detected as last. [MENTION=3816568]Myself5[/MENTION], does arch boot directly or did you have to do anything to make it higher up in the boot order
[General Topics] Myself5:
Hum never had issues with that. It could be that at some point I edited the boot order, but I don't recall the BIOS detecting Linux as Android being an issue.

Well just checked: it does detect it, but still prefers booting the proper grub over any Android attempts.
[General Topics] aveemashfaq:
Thanks. I was just trying my hands on arch installation. I think it is too much for me right now. Fedora bootloader is always set at a lower priority than Android. That is irritating. Also, Fedora uses libinput even in XFCE. Because of this, I can't set my calibration for evdev where touchscreen just works.

Ubuntu on the other hand works great out of the box except for wifi drivers. It seems that they made some sort of modification to make bluetooth work and that has ruined wifi. Need to do some more research.

Did you somehow manage to setup touch calibration in libinput?
[General Topics] aveemashfaq:
Not for me. I have tried Arch. Got down the rabbit hole but still it shows Android as first boot option. Can't accept that. Back to Ubuntu for me. Can you try and see if wifi works for you in Ubuntu. Not sure why it won't work because AFAIK, rtl8723bs driver issues were resolved back in 18.04. Not sure why they cropped up again
[General Topics] aveemashfaq:
I solved the wifi problem in Ubuntu by disabling secure boot. Now Ubuntu works smoothly and touch works great. All is well except for screen rotation but I don't use autorotate in my phone, why would I bother solving it for my laptop. All is well right now.
[General Topics] aveemashfaq:
It seems that evdev calibration is a little off at places. Tried playing around with values but could not get it to perfectly align. How is it for you? What is your calibration data. Mine is 60 1980 1260 0.

Did you figure out how to calibrate touchscreen in libinput. Apparently that is the future.
[General Topics] Lookanio:
Thank you for sharing this hardware hack. Can you estimate max. thickness of heat sink you can fit inside the case?
[General Topics] aveemashfaq:
My heat sink was approx 2mm thick with the residue of the fins that I chopped off. That squeezed in tightly touching both ends. Ideally, you want that to happen. If our heatsink plate touches the processor as well as the aluminium plate, it allows for the transfer of heat from the processor onto the much bigger surface of aluminium back panel. Any gap between the plate and the aluminium back panel creates an air gap and that reduces the heat dissipation capacity of the setup.

If you can only find a thinner plate, you can stuff the gap with thermal glue buy that is not the ideal solution.
[General Topics] Arxym:
Hello Everyone! Here I am with TUTORIAL TO INSTALL ANDROID ON CHUWI HI10 AIR TABLET.

Mind me and confront me as I don't know the rules of the forum. However I respect it a lot. Thank you.

So follow-on,

Format a usb pen drive to FAT32 and name it 'WINPE'.

copy all the files from the cross-bios folder to the 'WINPE' drive.

Connect Chuwi Hi-10 air to the keyboard or an external keyboard via usb.

When chuwi boot appears, press F7 to enter boot selection menu

Select WINPE Drive and wait for bios to get installed.

After Reboot- the screen will look messed up and thats okay.

That's how it will be for bios and boot but it won't matter to the OPERATING SYSTEM/ANDROID.

Shutdown the device.

PRESS VOLUME UP + VOLUME DOWN + POWER BUTTON TOGETHER UNTIL DMX MODE APPEARS.

Connect via usb to computer and start intel platform flash tool.

Make sure usb drivers are installed lol

In the flash tool, select browse and browse to unzipped Chuwi hi10 android folder that has flash.json file. Select the file.

Make sure device can be seen connected in the flash tool.

Flash. Relax.

Wait for device to boot -reboot - boot a few times on its own until REMIX OS boot appears.

During installation, do not connect to wifi because Remix OS behaves stupid. Connect later after installation and setup. Keep some patience and trust me.

HAVE FUN!

Ask me further if you need some help with the Android. I'll help you make it perfect that you'll love the Tablet.

File Links - ( Files belong to me and are uploaded by me to my g-drive- citing myself and not breaking laws)

The Android Zip - https://drive.google.com/file/d/1DDdHoHk9UsvbYYyRLrnxDpxxvG6Pmk60/view?usp=sharing

Extract it. It contains a flash.json file that needs to be located and used by flash tool.

Bios and installer zip (also contains README for help) - https://drive.google.com/file/d/1h7bsoiBYOd23MI03_Cs6rpWmDSilLm9d/view?usp=sharing

The folder has the bios for the WINPE drive and Intel's flashtool for installing android.
[General Topics] nikmag:
Thanks all for your great job and support. There is a amazing progress. I think that there are issues with bios. Is your version 5.011 09/29/2018? I was wondering if somebody could give the right configuration. I still cannot arrange the boot order as bios change it by itself.. From a Russian site I found the following configuration for Chuwi Hi10 PRO

Chipset-North Bridge-Intel IGD Configuration

GFX Boost on Enable (Increases the video core frequency from 400 to 500 MHz)

PR3 for Win 10 only on Enable (Enable Decoder Pro mode)

DVMT Pre-Allocated to 256MB

DVMT Total GFX Mem on Max

To increase the speed of writing to a USB flash drive, enable the following:

Chipset-South Bridge-LPSS & SCC Configuration

SSC SDIO Mode for WIFI with default on DDR50

Memory

DDR DVFS - Enabled

Frequency A selection - 1600

Frecuency B selectiin - 1067

Channel selection - Single Channel

DRAM Speed ​​Grade - Fast
[General Topics] nikmag:
I installed Ubuntu 19.04 but does not work. Wifi ok, bluetooth ok. any idea?