danielotero / linux-on-hi10 Goto Github PK

I thought it'd help to have somewhere to collect details on the remaining sound issues

PA crashing because of LPE: Upstream bug to watch is https://bugs.freedesktop.org/show_bug.cgi?id=100488

No speaker audio: Needs further investigation

• Either we need to figure out the correct UCM to route to the speakers
• or speakers are actually muxed outside the codec, like in previous Chuwi hardware: https://bugzilla.kernel.org/show_bug.cgi?id=189261

I'm led to believe that it's not the former, since the UCM is reported to work with other similar devices. Also an UCM for the rt5651 has recently been added to upstream alsa-libs, but it's not changing anything for me.

See also plbossart/UCM#13

I don't have Windows anymore, but still have Android, I would like to use rEFInd to boot Android and Arch instead.

I know that you can use a tool by Chuwi themselves to disable it, but I don't want to make a Windows To Go drive, and there's no way to change the boot order.

Arch Linux Kernel 4.13.3-1 is online, and 4.13.4-1 is testing.
Would you please do some update?

I m doing a fresh Ubuntu 18.04 on my Chuwi HI 10 Plus.
Kernel is 4.15.0-20-generic #21-Ubuntu SMP
Under pulse audio pavucontrol i have only a virtual device and no physical one.
When playing music with audacious i get no sound neither from internal speaker or from head set despite pavucontrol vumeter show sound activity.

inxi -xxAv6

System: Host: Chwui Kernel: 4.15.0-20-generic x86_64 bits: 64 gcc: 7.3.0
Desktop: Gnome 3.28.1 (Gtk 3.22.30-1ubuntu1) dm: gdm3
Distro: Ubuntu 18.04 LTS
Machine: Device: desktop System: CHUWI INNOVATION AND (SHENZHEN) product: Hi10 plus tablet v: Hampoo_reserve serial: N/A
Mobo: Hampoo model: Cherry Trail CR v: V100 serial: N/A
UEFI: American Megatrends v: 5.11 date: 10/12/2017
CPU: Quad core Intel Atom x5-Z8350 (-MCP-)
arch: Airmont rev.4 cache: 1024 KB
flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 11520
clock speeds: min/max: 480/1920 MHz 1: 1674 MHz 2: 1520 MHz
3: 1319 MHz 4: 1226 MHz
Memory: Using dmidecode: root required for dmidecode
Graphics: Card: Intel Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers
bus-ID: 00:02.0 chip-ID: 8086:22b0
Display Server: x11 (X.Org 1.19.6 ) driver: i915
Resolution: [email protected]
OpenGL: renderer: Mesa DRI Intel HD Graphics (Cherrytrail)
version: 4.5 Mesa 18.0.0-rc5 (compat-v: 3.0) Direct Render: Yes
Audio: Card bytcr-rt5651 driver: bytcr-rt5651
Sound: Advanced Linux Sound Architecture v: k4.15.0-20-generic

I saw tips regarding speaker activation and got following results
sudo ./chuwispeaker
[sudo] Mot de passe de jpm :
Using gpio 362
Could not write gpio pin: Operation not permitted
ls -l /sys/class/gpio
total 0
--w------- 1 root root 4096 mai 6 09:33 export
lrwxrwxrwx 1 root root 0 mai 6 15:24 gpio362 -> ../../devices/platform/INT33FF:01/gpiochip1/gpio/gpio362
lrwxrwxrwx 1 root root 0 mai 6 09:33 gpiochip225 -> ../../devices/platform/INT0002:00/gpio/gpiochip225
lrwxrwxrwx 1 root root 0 mai 6 09:33 gpiochip228 -> ../../devices/platform/INT33FF:03/gpio/gpiochip228
lrwxrwxrwx 1 root root 0 mai 6 09:33 gpiochip314 -> ../../devices/platform/INT33FF:02/gpio/gpiochip314
lrwxrwxrwx 1 root root 0 mai 6 09:33 gpiochip341 -> ../../devices/platform/INT33FF:01/gpio/gpiochip341
lrwxrwxrwx 1 root root 0 mai 6 09:33 gpiochip414 -> ../../devices/platform/INT33FF:00/gpio/gpiochip414
--w------- 1 root root 4096 mai 6 09:33 unexport

cat /sys/class/gpio/gpio362/direction
in
bytcr-rt5651

cat /proc/asound/cards
0 [bytcrrt5651 ]: bytcr-rt5651 - bytcr-rt5651
Hampoo-Hi10plustablet-Hampoo_reserve-CherryTrailCR
cat /proc/asound/modules
0 snd_soc_sst_bytcr_rt5651
jpm@Chwui:~$ ls -al /proc/asound
total 0
dr-xr-xr-x 5 root root 0 mai 14 16:37 .
dr-xr-xr-x 247 root root 0 mai 14 16:36 ..
lrwxrwxrwx 1 root root 5 mai 14 17:20 bytcrrt5651 -> card0
dr-xr-xr-x 5 root root 0 mai 14 17:20 card0
-r--r--r-- 1 root root 0 mai 14 17:20 cards
-r--r--r-- 1 root root 0 mai 14 17:20 devices
-r--r--r-- 1 root root 0 mai 14 17:20 modules
dr-xr-xr-x 2 root root 0 mai 14 17:20 oss
-r--r--r-- 1 root root 0 mai 14 17:20 pcm
dr-xr-xr-x 2 root root 0 mai 14 17:20 seq
-r--r--r-- 1 root root 0 mai 14 17:20 timers
-r--r--r-- 1 root root 0 mai 14 17:20 version
Any help regarding investigation direction will be appreciated.Thank you for reading.

Hello
I made my SDHC sard working by changing sdcard from ACPI mode to PCI in bios under bridges settings
:) try it yourself

I managed to get the headphone jack working, using the UCM files from https://github.com/plbossart/UCM/tree/master/bytcr-rt5651

The files may have to be renamed to Hampoo-Hi10protablet-Hampoo_reserve-CherryTrailCR/Hampoo-Hi10protablet-Hampoo_reserve-CherryTrailCR.conf and Hampoo-Hi10protablet-Hampoo_reserve-CherryTrailCR/HiFi(.conf) for it to work.

After copying the asound.state like in the README, one can run 'alsactl restore' to apply it.

You might also have to blacklist snd_hdmi_lpe_audio (and therefore disable HDMI audio) to keep pulseaudio from being killed on startup thanks to a bug in the current version in regards to assumptions that don't hold true with hdmi_lpe. Alternatively, PA can be started with --realtime=false

Unfortunately, I haven't been able to figure out how to get the speakers to work. Maybe someone else will have more luck. Working speakers would make this pretty workable as a daily driver (for me anyway)

Besides that, both microSD and USB Type-C work flawlessly for me, though I may have a different model (Hi10 Pro; Late 2016 I believe)

Hello
I can't figure out where to paste it

CONFIG_PWM=y
CONFIG_PWM_CRC=y
CONFIG_I2C_DESIGNWARE_PLATFORM=y
CONFIG_I2C_DESIGNWARE_PCI=y
CONFIG_INTEL_SOC_PMIC=y
CONFIG_DRM_I915=m

hello
i've just installed driver from this repo and it works actually, but I cant get it calibrated using xinput_calibrator, anyone made it working well??

Hi, maybe some people here may know how to fix this :-)

I've been playing around with Ubuntu 18.04 on my Hi10 Pro, which I installed in place of the old Windows partition (everything else untouched). This works more or less, but I currently can't boot back into Android. I can get the original boot selection screen with Android or Windows, but this just causes a reboot.

I suspect that this is just a messed-up EFI entry which could be fixed with efibootmgr, any suggestions how to directly boot to Android without the selector?

Hi, I have a Chuwi Hi10 Pro runing Manjaro-Arch linux.
In Current Status, the Active Stylus is listed as working.
I have the touchscreen working with touch gestures but, the stylus (on) is not detected.
Was there a specific driver to install to get the stylus to work?
It is an H2 stylus https://www.gearbest.com/tablet-accessories/pp_435776.html?wid=1433363

In case anyone else is still watching this repo and comes across this while digging out their Hi10s like me, the current release of alsa-lib in Arch has a bug affecting a lot of Atom devices including the Hi10pro. It's already been fixed but no release with the fix has come out yet.

PulseAudio will not be able to detect anything unless an asound.state is left from back when it was needed, but that will cause all sound through PA to be broken (aplay works though with the old asound.state). This is because with alsa-lib 1.2, the ucm stuff was moved to a new version and a bug in the parser prevents those new files to be read correctly, preventing PA from settin up the device correctly.

The commit fixing it is alsa-project/alsa-lib@e59034a
I made a PKGBUILD for alsa-lib from git to keep me afloat until the next alsa-lib release: https://github.com/Orochimarufan/custom-pkgbuilds/blob/master/alsa-lib-git/PKGBUILD

For future reference it should also be noted that the "alsaucm" utility is useful for these kinds of devices.

Hi guys,

First of all, thank you all for your awesome work. I have been working on a guide of how to install Lubuntu in the Chuwi and I have encountered some information that may be useful for ArchLinux.

Bluetooth adapter works after installing Larry Finger's drivers:

cd /tmp
git clone https://github.com/lwfinger/rtl8723bs_bt
cd rtl8723bs_bt
make
sudo make install

Every time you need to activate bluetooth, a script must be run, so I think is a good idea to set a root cron job to do so at startup.

Create a new directory, copy contents in it:

sudo mkdir /opt/rtl8723bs/
sudo cp * /opt/rtl8723bs/
sudo crontab -e

Then write the cron job:

@reboot cd /opt/rtl8723bs/ && ./start_bt.sh 

Regarding the light sensor, if anyone is interested in reading information from it, I made it work by installing more drivers (found in a Nextbook Flexx 10 guide):

cd /tmp
git clone https://github.com/burzumishi/linux-baytrail-flexx10/ -b Readme-stage --single-branch
cd linux-baytrail-flexx10/kernel/modules/cm3218_light_sensor
make
sudo make install
sudo modprobe cm3218

Once installed, you can read sensor value like this:

sudo cat /sys/bus/iio/devices/iio\:device1/in_illuminance0_input

I have also being working on a way to automatically rotate the screen based on accelerometer information (repo here), but it is not working fine with the touchscreen.

I hope this helps

Is there anyway to get the Windows capacitive button to work? I plan to use it for a custom function. The tablet is Chuwi Hi10 Plus.

EDIT: I forgot to mention that the touch screen driver was gslx680-acpi.

I have the Hi10 Pro Stylus, HiPen H2, it works in Windows but not Ubuntu 19.04.
This is a long shot but, is there a digitizer driver for Linux? The capacitive touch works, the stylus was never as good as Wacom, NTrig or, Windows Surface pen but, it was better than trying to use a capacitive stylus. Since I am no-longer taking courses, this is a minor nuisance.

I bricked my tablet by sending the tablet to hibernate mode.
When I boot after hibernate, it works fine until you load to Arch, showing some kernel information, and then it loads to blankness, nothing on screen, even the lcd panel shut off, I tried hard power off and turn on with nothing, not even a red led.

I hold the power button for a while trying to reset the CMOS, and then it starts working again.
Does anyone have this problem?

I'm on Arch Linux, kernel 4.18.7-arch1-1-ARCH

Just leaving this as a note here, for Hi10Plus the touchscreen fw file needs to be named slightly different now, some patches got merged into linux mainline recently.

wget "https://github.com/onitake/gsl-firmware/blob/master/firmware/linux/silead/gsl1680-chuwi-hi10plus.fw?raw=true"
--->
/lib/firmware/silead/mssl0017.fw

Also here is a working touchscreen calibration (i.e. touch input works with that as one would expect it):

$ cat /etc/udev/rules.d/50-touchscreen.rules
DRIVERS=="silead_ts" ENV{LIBINPUT_CALIBRATION_MATRIX}="2.15 0 0 -0.04 3.25 0 0 0 0"
#                                                       xH +H     +V   xV
$ udevadm control --reload-rules && udevadm trigger

Infos for calib:

https://wiki.archlinux.org/index.php/Calibrating_Touchscreen#Calculate_the_Coordinate_Transformation_Matrix


xinput list-props "silead_ts"
Device 'silead_ts':
        Device Enabled (169):   1
        Coordinate Transformation Matrix (171): 1.000000, 0.000000, 0.000000, 0.000000, 1.000000, 0.000000, 0.000000, 0.000000, 1.000000  <--- original value
        libinput Calibration Matrix (568):      2.150000, 0.000000, 0.000000, 0.000000, 3.150000, 0.000000, 0.000000, 0.000000, 1.000000 <--- adjustead values show up here

I case anyone is still watching this repo,

• (At the very least Arch) kernel 5.12 has moved from the SST to the SOF based driver by default (snd-sof-acpi-intel-byt). This requires the 'sof-firmware' package to be installed to work. Kconfig added Arch Kconfig change
• There is an incompatibility of (unpatched) alsa-* 1.2.5 with pipewire if the hardware uses UCM (which this does). Getting alsa-* from git or holding alsa-ucm-conf back at 1.2.4 circumvents the issue. Pulseaudio is unaffected. Pipewire bug

Is there a way to get the touchscreen working for the regular hi10 (no plus, pro)? So far I have everything working on Manjaro minus the touchscreen. It's the only thing I can't figure out. Any tips?

Hello
i'm able to connect to my android phone ap with chuwi, my work wi-fi but not my home wi-fi.
After entering password it's connecting and after 2 mins it ask for password again. I'm sure password is okay because I tested it on my phone
Anyone experienced this issue? Is there fix?

My Hi10pro recently stopped connecting to one of my APs. Turns out the manufacturer had enabled PMF in an OTA update. My other devices have no problem with this and it appears that not supporting 802.11w outright should just fall back to standard management frames. However, it seems that the rtl8723bs (hw/fw/driver?) does implement 802.11w but has some kind of implementation bug that causes the connection attempt to fail.

Can anyone else report any experience related to this?