The Geniatech T230C (also branded as MyGica T230C with a black case instead of a white one) is an evolution of Geniatech T230. Although it has the same external appearence, it uses different hardware. Support for "T230C v2" has made it to the vanilla kernel in the fall of 2019. The MyGica-branded device can be found on websites that ship hardware directly from China.
There is a version without IR called eyeTV T2, eyeTV T2 hybrid and eyeTV T2 lite (three names for the same hardware). Targetting a Mac OS audience, they are 5 to 6 times as expensive as the MyGica T230C which does feature IR support (and comes with a 28-button remote control). These three share the same conic case, while MyGica and GeniaTech devices get wider only around the IEC connector. The T2 lite has a white case (and different EEPROM), the other two have a case that is silver with a transparent cap.  (There is also a bulky eyeTV hybrid, which lacks the "T2" in its name but supports DVB-T2 nonetheless unlike its predecessor of the same name. Its hardware is currently unknown.)
The device can be used with the PadTV HD app on Android if connected via a USB OTG adapter. That app supports H.265, but the phone must be fast enough. On Windows, 28 Jun 2017 drivers (shipped with some devices in 2018, probably ones with updated "T230C2" EEPROM) are required to prevent frequent blue screens in nearly all apps.
The following components are used on the device
- USB interface: Cypress CY7C68013A-56LTXC
- Demodulator: Silicon Labs Si2168-D60
- Tuner: Silicon Labs Si2141-A10
As of kernel 4.4, drivers are not shipped with the kernel (at least not in Raspbian 8).
Kernel 4.9.24 included in Raspbian 8 (installed when upgrading packages through apt-get) does not ship the driver either.
Kernel 4.14 (included in Raspbian 9 in 2019) ships with the correct driver to support the T230C.
Kernel 5.4 vanilla has moved some code about, the T230C and T230C v2 are now supported by driver dvb_usb_dvbsky, rather than the previously responsible dvb_usb_cxusb. For years, CrazyCat has done a patient job of keeping the T230C hardware supported in dvb_usb_cxusb in his own build of the "media" driver subsystem. The list of T230 flavours supported by the vanilla driver dvb_usb_dvbsky as of kernel 5.4 goes like this:
VID PID "Description" 0x0572 0xc688 "MyGica Mini DVB-T2 USB Stick T230" 0x0572 0xc689 "MyGica Mini DVB-T2 USB Stick T230C" 0x0572 0xc68a "MyGica Mini DVB-T2 USB Stick T230C v2" 0x0572 0xc699 "MyGica Mini DVB-T2 USB Stick T230C Lite" (no IR remote sensor) The USB VID=0x0572 means Conexant.
The rest of this paragraph and the whole chapter on Building the driver, contain data that may still be useful, but is starting to feel dated, now with the suport in vanilla. Obviously the vanilla driver is nowadays inherently "in the tree" and builds as part of the kernel, and will eventually make it into distro kernels. The following data is related to the past "CrazyCat solution".
Example device detection in the log:
usb 1-1.3.3: New USB device found, idVendor=0572, idProduct=c689 usb 1-1.3.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3 usb 1-1.3.3: Product: EyeTV Stick usb 1-1.3.3: Manufacturer: Geniatech usb 1-1.3.3: SerialNumber: 160421
To be confirmed: it looks like this device is better integrated into LibreElec system (see here how to use the Crazycat-CC driver pack).
Building the driver
The following procedure works (at least) on a Raspberry Pi running 4.4.43-v7+ or 4.9.30-v7+ kernel (but does not seem to work with the 4.9.24-v7+ kernel). It should be pretty similar on other distros and/or with other kernels.
Run apt-get install raspberrypi-kernel-headers to get the correct headers (i.e. the headers corresponding to your exact current kernel build) into /lib/modules/<some folders about your current $(uname -r) kernel version>/. In my case, 2 folders were created: 4.4.43+ and 4.4.43-v7+. In case it does not download the right kernel version headers (there may be a mismatch between uname -r and the folder names in /lib/modules), you can grab the raspi sources by running:
# get the rpi-source tool wget https://raw.githubusercontent.com/notro/rpi-source/master/rpi-source chmod u+x rpi-source ./rpi-source --dest /somewhere/that/has/free/space # Older versions might need to have linux-headers installed into /usr/src and symlinks everywhere in /lib/modules # This is not needed anymore (since mid-2017? Was it even needed at some point?) ln -s /somewhere/that/has/free/space/linux /usr/src/linux-headers-$(uname -r) ln -s /usr/src/linux-headers-$(uname -r) /lib/modules/$(uname -r)/build ln -s /usr/src/linux-headers-$(uname -r) /lib/modules/$(uname -r)/source ...and do the same with uname -r, but without the trailing -v7+ (eg 4.4.43+ if uname -r is 4.4.43-v7+)
Check that a correct .config file (corresponding to the exact current build of your kernel) is available at /lib/modules/$(uname -r)/build/.config It should normally have been fetched by rpi-source. If it was not the case, run modprobe configs, and the .config file that you want is available in the compressed file /proc/config.gz
Now we have the correct sources and .config file, we can fetch the driver sources and build it by using CrazyCat's media_build tool:
git clone https://bitbucket.org/CrazyCat/media_build cd media_build ./build --main-git
Be sure to have some space left, as it downloads a part of the kernel tree.
In case the build fails about frame_vector.c: No rule to make target '..../v4l/frame_vector.c' , comment the following lines in media_build/v4l/Makefile, so that they appear like this:
#ifeq ($(makefile-mm),1) #-include $(obj)/Makefile.mm #endif
Then you can install the drivers by running sudo make install
The process should have installed the correct corresponding firmwares into /lib/firmware. If it is not the case, grab and install the needed firmwares from https://bitbucket.org/CrazyCat/media_build/downloads/dvb-firmwares.tar.bz2.
The Geniatech T230C and T230C v2 requires these firmwares (available at https://github.com/osmc/dvb-firmware-osmc):
They must be copied in /usr/lib/firmware.
IR Remote Control
The dvbsky driver as of vanilla Linux 5.4 registers a devinput device for the IR sensor and reports support for the RC5 protocol only. The sensor happily picks up codes transmitted by various remote controllers - such as those packaged with TV's and other hardware by Philips or Vestel. Using the ir-keytable command-line tool, these feral scan codes received via the IR sensor can be mapped to meaningful devinput events - these are then directly accepted by the Xwindows xinput layer (which can be prevented via xorg.conf if desired) or can be passed to LIRC for further application steering.
If the device is unable to initialize, you may want to prevent the IR from loading:
# cat /etc/modprobe.d/dvb_usb.conf options dvb-usb disable_rc_polling=1
A reboot is needed to take effect.
This DVB-T stick supports every French DVB-T channel (i.e. both HDTV and SDTV, broadcast as MPEG4). They are succesfully processed through tvheadend.
Another tester reports success in receiving DVB-T and DVB-T2 with MPEG2, MPEG4 and HEVC encodings, in the Czech Republic, played back by VDR 2.4.1 with the softhdvaapi front end.
DVB-C is advertised on the package and is recognized by tvheadend, however this requires the model that includes DVB-C.
Contributions are welcome.