This device is commonly found on E-commerce sites that ship directly from China. The hardware supports DVB-C, DVB-T and DVB-T2.
DVB-T supported since kernel 3.13, DVB-T2 since 4.6. Drivers being developed support DVB-C with 64QAM/128QAM, but not 256QAM.
The device was usually shipped with these components:
- USB interface: Realtek RTL2832P
- Demodulator: Panasonic MN88473 (2013 revision: MN88472) (2018 revision: Sony CXD2837ER)
- Tuner: Rafael Micro R828D (TVR801: R820T)
The USB interface bridge for all devices are supported by rtl238xx driver. All tuners are supported by the same driver (rt820t). The demulator driver varies from version to version: it can be mn88472, mn88473 or cxd2841er.
The different revisions of the Astrometa DVB-T2 have been released under many different “brand” names. This page cannot list all of them. If you buy a new tuner from an unknown or no brand for under 30 euros or so, you will probably get some Astrometa clone.
2013 and 2014 revision look very similar. Probably, the text on the 2013 revision always reads “FM+DAB+SDR”, while the 2014 one says “DVB-T/T2/C+FM+DAB”. However, seller pictures do not always reflect that change and one could end up buying a random version even years later.
The 2014 revision version is also sold as “Andoer Digital DVBT2 USB TV Stick” or “Docooler YRC1415458446568TZ”. Those devices are identical in appearance to the usual Astrometa devices.
TeVii sells a similar device under the name “H630”. The case is black. The PCB layout is a bit different, e.g. the IR sensor is in a different position.
There is a version of the device called TVR801, which uses an unlabelled Rafael Micro R820T tuner. According to official sources, this one does not support DVB-C.
In late 2015, a version with analog video input and analog tuning capabilities was released, powered by the Conexant CX23102-11Z USB bridge. It has a different device ID (0135) and is a different device. Support is unknown.
In 2017, a clone of the 2014 version with a red PCB (original Astrometa one’s is green) also appeared on E-commerce sites that ship from China. The case looks like the H630’s, but is white with silver text that reads “DVB-T/T2/C/FM/DAB”. This device is shipped in bulk in just a plastic bag with a simple stick antenna, a remote control (21 buttons) and a Mini CD that dates to 09 Jan 2017. Some sellers call it OXA ZC905500 or S SKYEE. It is also sold under the name “iViewHD” inside the case of the TVR801 and its antenna has an USB-powered amplifier. See 2018 update below!
In 2018 several clones are being shipped using the Sony CXD2837 chipset. This has a driver from kernel 4.14 onwards (it is now covered by the cxd2841er driver), but the device as a whole does not work because the RTL2832 driver has not been updated to recognise it. However, updated RTL2832 driver has been accepted to the media_tree (as mentioned here) so you can compile it yourself (see How to Obtain, Build and Install V4L-DVB Device Drivers#Retrieving_from_the_upstream_development_Kernel_tree) or use a specialized distribution such as LibreELEC (kodi appliance) which supports this device out-of-the-box, provided you enable the bundled “DVB drivers from the latest kernel (media_build)” add-on. These changes will most likely be included in the next mainline kernel. In most cases the RTL chip does not appear to be connected to the tuner, so these devices will not work for DVB-T either. Even though the chipset is different and incompatible, the same USB vendor and product IDs are used (15f4:0131). The clones with the Sony demodulator reported so far are:
- Blue coloured PCB either with a white case or a black case, both with silver writing. You (or a potential seller) can tell if this uses an incompatible Sony chip by holding it in front of (or for the black ones: directly under) a light source and see the colour of the PCB through the holes. dmesg output, lsusb -vvv output and PCB photos here
- Green coloured PCB with a case matching the 2014 revision. The only way to tell if this uses the Sony chip (or is the 2014 revision with working Panasonic chipset) is to open the case and read the part number on the chip.
All these models share the same USB IDs.
In 2020 Sam Nazarko Trading Ltd sells “DVB-T2/DVB-C TV dongle” for OSMC supported devices, but it works with most of GNU/Linux platforms. This tuner is detected as same USB ID 15f4:0131
|2013 revision||2014 revision||TVR801||2017 revision||2018 revision||2015 revision: DVB+Analog TV|
(some may look like the 2014 revision)
(some may look like the 2013 revision)
(case also used for other revisions
or devices, often without the text)
or same as 2014 or 2017 revision
|Bottom PCB||same as 2014 revision |
(different demod, no number 1422)
(“1422” and text missing sometimes)
|Top PCB||same as 2014 revision|
|USB Bridge||Realtek RTL2832P||Realtek RTL2832P||Realtek RTL2832P||Realtek RTL2832P||Realtek RTL2832P||Conexant CX23102-11Z|
|Demod||Panasonic MN88472 |
(said to not support DVB-T2 v1.3.1,
which is used in e.g. Germany)
|Panasonic MN88473||Panasonic MN88473||Panasonic MN88473||Sony CXD2837ER||Panasonic MN88473|
|Tuner||Rafael Micro R828D||Rafael Micro R828D||Rafael Micro R820T |
(probably doesn’t support DVB-C)
|Rafael Micro R828D||Rafael Micro R828D or |
AT628 (same as R828D)
|Rafael Micro R828D|
|USB IDs||15f4:0131 (Hanftek)||15f4:0131 (Hanftek)||15f4:0131 (Hanftek)||15f4:0131 (Hanftek)||15f4:0131 (Hanftek)||15f4:0135 (Hanftek)|
|Supported||yes||yes||most likely||yes||most likely since 5.0||yes, since 4.14|
PCBs of TVR801 and 2017 revision have the same color, the difference on the pictures comes from different lighting. There is another rare version described in Antti’s blog, which pretty much the 2017 revision with a green PCB (and has some very little differences).
The RTL2832P has 2 PID filter paths. One for the internal demod and one for a possible external one.
Auzeuner DVB-T2 (Astrometa 2018) driver update #567
Copy link Quote reply
kapitanf commented Jul 5, 2018
here is rtl28xxu.c rtl28xxu.h update with support cxd2837er demodulator for right function Astrometa 2018 dvb-t/t2/c stick. Works for me on linux kernel 4.17.2.
Copy link Quote reply
KernelPRBot commented Jul 5, 2018
Thanks for your contribution to the Linux kernel!
Linux kernel development happens on mailing lists, rather than on GitHub – this GitHub repository is a read-only mirror that isn’t used for accepting contributions. So that your change can become part of Linux, please email it to us as a patch.
Sending patches isn’t quite as simple as sending a pull request, but fortunately it is a well documented process.
- Format your contribution according to kernel requirements
- Decide who to send your contribution to
- Set up your system to send your contribution as an email
- Send your contribution and wait for feedback
How do I format my contribution?
The Linux kernel community is notoriously picky about how contributions are formatted and sent. Fortunately, they have documented their expectations.
Firstly, all contributions need to be formatted as patches. A patch is a plain text document showing the change you want to make to the code, and documenting why it is a good idea.
You can create patches with git format-patch .
Secondly, patches need ‘commit messages’, which is the human-friendly documentation explaining what the change is and why it’s necessary.
Thirdly, changes have some technical requirements. There is a Linux kernel coding style, and there are licensing requirements you need to comply with.
Both of these are documented in the Submitting Patches documentation that is part of the kernel.
Note that you will almost certainly have to modify your existing git commits to satisfy these requirements. Don’t worry: there are many guides on the internet for doing this.
Who do I send my contribution to?
The Linux kernel is composed of a number of subsystems. These subsystems are maintained by different people, and have different mailing lists where they discuss proposed changes.
If you don’t already know what subsystem your change belongs to, the get_maintainer.pl script in the kernel source can help you.
get_maintainer.pl will take the patch or patches you created in the previous step, and tell you who is responsible for them, and what mailing lists are used. You can also take a look at the MAINTAINERS file by hand.
Make sure that your list of recipients includes a mailing list. If you can’t find a more specific mailing list, then LKML – the Linux Kernel Mailing List – is the place to send your patches.
It’s not usually necessary to subscribe to the mailing list before you send the patches, but if you’re interested in kernel development, subscribing to a subsystem mailing list is a good idea. (At this point, you probably don’t need to subscribe to LKML – it is a very high traffic list with about a thousand messages per day, which is often not useful for beginners.)
How do I send my contribution?
Use git send-email , which will ensure that your patches are formatted in the standard manner. In order to use git send-email , you’ll need to configure git to use your SMTP email server.
For more information about using git send-email , look at the Git documentation or type git help send-email . There are a number of useful guides and tutorials about git send-email that can be found on the internet.
How do I get help if I’m stuck?
Firstly, don’t get discouraged! There are an enormous number of resources on the internet, and many kernel developers who would like to see you succeed.
Many issues – especially about how to use certain tools – can be resolved by using your favourite internet search engine.
If you can’t find an answer, there are a few places you can turn:
- Kernel Newbies – this website contains a lot of useful resources for new kernel developers.
- The kernel documentation – see also the Documentation directory in the kernel tree.
If you get really, really stuck, you could try the owners of this bot, @daxtens and @ajdlinux. Please be aware that we do have full-time jobs, so we are almost certainly the slowest way to get answers!
I sent my patch – now what?
You can check that your email has been received by checking the mailing list archives for the mailing list you sent your patch to. Messages may not be received instantly, so be patient. Kernel developers are generally very busy people, so it may take a few weeks before your patch is looked at.
Then, you keep waiting. Three things may happen:
- You might get a response to your email. Often these will be comments, which may require you to make changes to your patch, or explain why your way is the best way. You should respond to these comments, and you may need to submit another revision of your patch to address the issues raised.
- Your patch might be merged into the subsystem tree. Code that becomes part of Linux isn’t merged into the main repository straight away – it first goes into the subsystem tree, which is managed by the subsystem maintainer. It is then batched up with a number of other changes sent to Linus for inclusion. (This process is described in some detail in the kernel development process guide).
- Your patch might be ignored completely. This happens sometimes – don’t take it personally. Here’s what to do:
- Wait a bit more – patches often take several weeks to get a response; more if they were sent at a busy time.
- Kernel developers often silently ignore patches that break the rules. Check for obvious violations of the Submitting Patches guidelines, the style guidelines, and any other documentation you can find about your subsystem. Check that you’re sending your patch to the right place.
- Try again later. When you resend it, don’t add angry commentary, as that will get your patch ignored. It might also get you silently blacklisted.