Kinhank K9 - SoC S5 S928X-K

I’ve just got hold of one of these for £155. Anyone already got this up and running?

TL:DR - It works with 21.3 stable (NE). Use Tencent Aurora 5x dtb and this remote.conf
Currently on 22 Alpha 2 you need to add a separate dovi.ko and it doesn’t play all DV files. I have problems with Profile 5

hi Mist, please I am new to the forum. Please can you explain to me what is meant by your post. I also have same device, it is doing good with local media but lac in streaming for bitstreaming HD audio

hi D33, did you get it working. I have same device.

As long as no device is on supported list and never tested, nothing is confirmed to work.
Get a storage device, and use latest nightly (NO-generic.img)
CoreELEC nightly builds
-Burn generic.img file on USB drive.
-from device tree folder (copy - tencent_aurora_5x to coreelec root directory and rename it to dtb.img )

Thanks a lot for reply. Ok. I have seen the kernel version, it is 5.4.210. So img should be NE or NO, as i have red somewhere that this kernel version needs NE. Please reply, Thanks in advance. I am getting dolby atmos raw audio to my AVR with excellent sound. This K9 can play all files from local storage with excellent results. but no HD audio from any streaming except zee5, from which it can bitstream some dolby atmos. can i install netflix after coreelec

This topic was automatically closed 91 days after the last reply. New replies are no longer allowed.

Read the forum about Kinhank and why the support for it was canceled.

Thanks for the response. First time using CoreElec so please excuse any idiocy on my part.

I have downloaded the latest stable build, burnt onto a USB stick and put it in the usb 2.0 port. On power up I got the CoreElec boot screen and all seems well. Was able to config to 4k and play movies. Obviously need to play about a bit to understand if all is working as expected but it certainly seems so. BRILLIANT!!!

The thing not working is the Bluetooth remote. I’m using the LG remote (via CEC I assume) to control the interface.

So given the message above about no OpenSource support what is it I should be looking out for and am I ok to use the build I have as-is?

You can use any device you want if you get CE running on it. But don’t expect much help in case of problems.

There is also thread for Kinhank G1 which shares the same.

Great. I’ve got my library synchronising now so will test. Should I share my finding here or create a new thread in Unsupported HW?

I doubt anyone cares for unsupported devices :rofl:

This is an S928-K box and works with the latest stable release (21.3) which appears to be “NE”. I downloaded, used Rufus to format an SD card, copied the Tencent dtb to the root and renamed then plugged into (either of) the USB port at the rear and restarted the box.

All booted up beautifully!

The BT remote can be paired using the bluetooth menu but it crashed the box after a minute or two the first time so I just stuck to using the TV remote (working via CEC) to control.

So far so good.

So on NE (21.3 Omega). I can connect the BT remote, it shows up as XiaoPaiRC_173S. However, it either doesn’t work or works for one or two clicks then crashes the box. Not too much of a problem as I can control most things with my LG remote

I’ve now used a separate usb to test out the NO build Alpha 2 (21.90.702). It say no DV as my kernel is 5.15.70, not 5.4.x

BT is still not working on this build either

I have same your device, I installed NO 22 latest nightly work smoothly no issue. If you want DV you should use this file just put it in configs.

dovi.ko (429.9 KB)

1 Like

You are very kind!

Have you got your BT remote working?

I don’t use remote I’m using keyboard by BT and work without any issue.

Not all DV files play on the NO build - I’ve asked the question in the NO dev thread but assume it’s a ‘tough luck’ sort of thing. I assume it needs a compliant dovi lib file

Just for clarity of any other Kinhank k9 owners. The current NO alpha2 nightlies install perfectly and only require an additional dovi.ko file to be added. Please see the separate thread in Unsupported Hardware

Thanks to all the team for working on this so diligently