Difference between revisions of "DVB-T2 USB Devices"

From LinuxTVWiki
Jump to: navigation, search
(Supported by 3rd Party Drivers)
(Supported by 3rd Party Drivers)
Line 30: Line 30:
* [[Sundtek MediaTV Pro III|Sundtek MediaTV Pro III (DVB-C/T/T2/AnalogTV/FM Radio/Composite/S-Video)]]
* [[TBS5220_USB_DVB-T2/T/C_Freeview_HD_TV_stick|TBS5220]]
* [[TBS5220_USB_DVB-T2/T/C_Freeview_HD_TV_stick|TBS5220]]
* [[Technotrend_TT-Connect_CT2-4650|Technotrend TT-Connect CT2-4650]]
* [[Technotrend_TT-Connect_CT2-4650|Technotrend TT-Connect CT2-4650]]

Revision as of 22:09, 13 December 2013

On this page you will find information regarding DVB-T2 USB devices.

Please be aware that:
  • The information contained here is likely non-exhaustive and, despite best efforts to do otherwise, may contain errors. (Please help to keep these lists up-to-date so that they are useful for everyone!)
  • If your device is not listed, try:
    • searching the existing mailing list archives:
      • Linux-Media Mailing List (LMML) archives (via vger or .... )
      • or from the older mailing lists (now largely deprecated in favour of the LMML):
        • dvb mailing list archives (via spinics or MARC ... )
        • v4l mailing list archives (via .... )
    • searching for information with Google or other internet search engine
    • by posting a question about the device directly to the LMML (but please do conduct a search first, as it may already have been discussed!)
    • Note: when it comes to support, it is generally a good idea to try the current V4L-DVB sources because some device drivers can be very new and thus may have not made their way into the mainstream kernel.
In any regard, in respect to the above listed suggestions, you may find it to be the case that your device is actually already supported or that experimental support is available.
  • Because the component constitution on many devices are often similar or identical, there may be devices that are unlisted but may actually work with the existing driver framework for previously supported devices. In such a case, your non-listed but working device will likely be reported in your system messages as being one of those previously supported devices. If you encounter such an occurrence, please do report your success on the LMML so that proper detection/identification of your device can be added within the drivers.
  • Lastly, it bears worth repeating the request: Please help to keep these lists up-to-date so that they are useful for everyone!

DiB0700 USB2.0 DVB-T devices


Supported ID on
Hardware Firmware Comment / Pictures URL E
Anysee E7 No 1c73:861f USB2.0 N/A This is a generic entry for the Anysee E7 line. If you have details for a particular device, please feel free to clone this entry and add the details. Anysee E7 T2C [1] Jump to the place where you can edit this entry
GoTView MasterHD 3 Yes 5654:ca42 USB2.0 RealTek RTL2832U [2] [3] Jump to the place where you can edit this entry
Geniatech T220 Yes, in kernel since 3.14, Users reporting errors with DVB-T2 1f4d:d220 USB2.0 Sony CXD2820R / NXP TDA18271HD/C2 / Cypress CY7C68013A N/A Looks like August DVB-T210 is a rebranded device with the same usbids. [4] Jump to the place where you can edit this entry
PCTV Systems nanoStick T2 290e Yes, in kernel since 3.0 2013:024f USB2.0 eMPIA em28xx, Sony CXD2820R, NXP TDA18271HD/C2 N/A First DVB-T2 capable receiver with Linux support. Kernel 3.2+ or latest media-build may be needed for multiple Empia-based devices to work together. Details on development history. PCTV nanoStick T2 290e PCB em28xx demod.jpg [5] Jump to the place where you can edit this entry
Astrometa DVB-T2 DVB-T Yes, in kernel since 3.13, DVB-T2 Yes, in kernel since 4.6 15f4:0131 USB2.0 RealTek RTL2832P, Panasonic MN88472 or MN88473, Rafael Micro R828D Popular generic DVB-T2 USB tuner from different Chinese suppliers Astometa HD-901T2 [6] Jump to the place where you can edit this entry
Geniatech T230 Yes 0572:c688 USB2.0 Silicon Labs Si2148, Silicon Labs Si2168, Cypress EZ-USB FX2 CY7C68013A dvb-demod-si2168-b40-01.fw, dvb-tuner-si2158-a20-01.fw kernel >= 3.19, remote control supported. Geniatech-t230.jpg [7] Jump to the place where you can edit this entry
TerraTec Cinergy T2 Stick HD Yes eb1a:8179 USB2.0 Silicon Labs Si2146, Silicon Labs si2168, Empia EM28178 dvb-demod-si2168-a30-01.fw kernel >= 3.19, remote control supported. TerraTec Cinergy T2 Stick HD.jpg [8] Jump to the place where you can edit this entry
PCTV Systems tripleStick 292e Yes 2013:025f USB2.0 Silicon Labs Si2157, Silicon Labs Si2168, eMPIA em28174 dvb-demod-si2168-b40-01.fw First version of the driver has been released, look here [9] Jump to the place where you can edit this entry
TechnoTrend TVStick CT2-4400 Yes 0b48:3014 USB2.0 Silicon Labs Si2158, Silicon Labs Si2168, Cypress CY7C68013A dvb-demod-si2168-a30-01.fw [10] Jump to the place where you can edit this entry
TechnoTrend TT-connect CT2-4650 CI Yes 0b48:3012 USB2.0 Silicon Labs Si2158, Silicon Labs Si2168, Cypress CY7C68013A dvb-demod-si2168-a20-01.fw, dvb-tuner-si2158-a20-01.fw [11] Jump to the place where you can edit this entry
TechnoTrend TT-connect CT2-4650 CI v1.1 Yes 0b48:3015 USB2.0 Silicon Labs Si2157, Silicon Labs Si2168, Cypress CY7C68013A dvb-demod-si2168-b40-01.fw, dvb-demod-si2168-02.fw, dvb-tuner-si2158-a20-01.fw [https://www.mail-archive.com/linux-media@vger.kernel.org/msg94927.html [12] Jump to the place where you can edit this entry
Hauppauge Hauppauge_WinTV-dualHD Model 01590 ~ Partial 2040:0265 USB2.0 Silicon Labs Si2157, Silicon Labs Si2168,Empia EM28274 dvb-demod-si2168-b40-01.fw Kernel >=4.7 first tuner only, kernel patch for both tuners [13] Jump to the place where you can edit this entry

Supported DVB-T2 USB Devices

Currently no device

Experimental Support

Currently no device

Currently Unsupported DVB-T2 USB Devices

If you own one or more devices from the following list and you want to help with support development, please contact the Linux-Media Mailing List (LMML). Note that if your device is similar to or contains components for which driver development is currently being undertaken, then it is possible that you will pique the developers' interest and can obtain some assistance that, possibly, leads to full support for your device.

However, please note that inquiries to the mailing list:

  • Should NOT be treated as an order drop-off queue. You're soliciting help from volunteer developers who work on V4L-DVB matters in their spare time, and such work can be non-trivial (i.e. requiring even thousands of hours work). So being demanding is one sure route to being ignored. (Honestly, this point really shouldn't even need to be written, but you'd be surprised at the number of irrational individuals who write into the mailing list demanding this or that).
  • May pass without garnering a response—a distinct byproduct of the fact that there are a limited number of developers, whom might be able to help, that are associated with the project. Often times, even if they wished to help, their energies are entirely tied up with other projects. In such cases, the best path might be to try to spearhead the driver development for your device yourself, or hire someone who can.
  • Anysee E7
  • Supported by 3rd Party Drivers

    Sometimes a manufacturer forks v4l-dvb all on their own and writes a driver for their device so they can claim Linux support.

    In-Kernel 3rd party Drivers


    1. It's possible your device will work.. for the moment.
    2. If the manufacturer provides open source drivers with an acceptable license, volunteers could technically implement this code in the Linux kernel for true support. However.. :


    1. The quality of the code (if open, there are also cases where you just get a binary blob) too often just isn't good enough and there's still too much work to be done to make the device work. There was probably a reason the manufacturer didn't just send their patches to the linux-media mailinglist.
    2. Depending on what exactly the manufacturer did, you may have to reinstall the drivers every time your kernel is updated.
    3. When the manufacturer stops updating the drivers, the drivers will quickly refuse to install as newer kernels are released.

    In case a manufacturer provides open source drivers the patches can be sent to the linux-media mailinglist Linux-Media Mailing List (LMML). Keep in mind however that if the license isn't compatible with the Linux kernel or the quality of the code isn't good enough, these will not become a part of the Linux kernel.

    NOTE: As linux media drivers are character based, drivers can be also written using libfuse's character device in userspace example. If written that way, an out-of-kernel driver can be written, which fully integrates to udev without the disadvantage of closed source or incompatibility to other drivers. Such driver would rely on kernel fuse and character device in user space support as well as libfuse.

    Closed source userspace drivers (mostly Sundtek)


    1. Same driver may be usable for different Linux versions, depending on what vendor did.
    2. No need to reinstall drivers when your kernel is updated.
    3. Drivers can be profiled easily and more accurately than in kernelspace.
    4. If the driver crashes, it won't crash the system or kernel, only the driver and applications using the driver will be affected. Userspace drivers can also be used when debugging drivers for USB host controllers, as the userspace driver can't crash the system, making debugging easier.
    5. If the manufacturer would stop to support the drivers, the userspace driver may still continue to work with newer Linux systems


    1. You can't look into the sources. While this may be not a problem for end-users, it prevents hacking devices and trying to fix bugs (usually not a problem for endusers)

    Also See