Olli Salonen wrote:
> Hi,
>
> I compiled a copy of OpenELEC 4.0.3 with the patch included (just Generic 64-bit, hopefully that's ok for you guys):
> http://trsqr.net/olli/OpenELEC-Generic.x86_64-devel-20140603185742-r18390-g61f17d8.tar
Works for me on an Acer Revo RL80- though the OpenElec / TV Headend combo crashes quite a lot in that build I can scan both UK T2 muxes from Crystal Palace in London within TV Headend (I leave everything on Auto other than Mux bandwidth for the T2 channels. The all of the T muxes are automatically added by network discovery after adding a single T mux manually).
PSB3 (545800kHz 32k 256QAM) channels (BBC One, BBC Two, BBC Three/CBBC, ITV and Channel Four - all HD) tune OK and are viewable - though not always consistently. For some reason COM7 (570000kHz 32k 256QAM) channels (BBC Four/CBeebies HD, BBC News HD, Al Jazeera Eng HD and Al Jazeera Arabic SD) scan - but OpenElec crashes when I try to watch them.
>
> For me the patched version does not work, but even the media build drivers patched with CrazyCat's patch on top of my Ubuntu 14.04 on another PC do not work. So it might be that I have a faulty device or something. When I say it does not work, it seems to me as if the signal quality would be very low. It does not find any DVB-T2 channels and only sporadically the normal DVB-T channels (I should have 40+ channels and w_scan finds 19-38 channels). w_scan also throws me several errors like: "WARNING: received garbage data: crc = 0xbb7ef20f; expected crc = 0x00000000. increasing filter timeout."
>
I got those messages with an unpatched driver on T2 channels only - but with the patched version they went away. This was on a simple Ubuntu 13.10 install on an x86 Acer C720 Chromebook running Chrubuntu.
> From the same cable, I get all channels consistently with good signal quality using a PCTV 290e. I suppose that there could be something wrong with the device too, since this behaviour was observed also earlier using this stick. Anyway, let me know how does it work for you.
>
> -----
>
> Question: Since kernel 3.14.4 includes the T220 support, shouldn't it be ok to just patch the files there with the t220-fix.patch? At least the resulting files were identical with the media-build ones after patching (they included the ts_clock_inv things).
