V2 Signal & Quality meters

[dRdoS7]

HI,

I received a replacement V2 yesterday. SD slot is working OK on this one.

I had noticed with the previous V2 that the signal meter showed very low, and the quality indicated zero. I didn't bother about it at the time, as I was more concerned with having the SD working. The U4 showed good readings, the T2 also shows good (that's in in another room, but same antenna).

V2:

U4:

To be sure it was the V2, I swapped antenna cables, and the meters showed the same values.


V2:

U4:

There's no break up of the picture on any channels. Can this be fixed?

Thanks,

dRdoS7

[prl]

This appears to be an issue either with the V2 tuners' capabilities, or with the kernel level drivers. I see the same results on my test V2's built-in tuners (sensible-looking signal strength and 0% for signal quality), but different incorrect strength and quality indications on the Hauppauge! USB dual tuners (strength always 0%, quality always 100%).

So there's probably nothing that can be done in the enigma2 code. It's possible that if it's a problem with the kernel drivers, that might be fixable, but if the data isn't available from the device, there's nothing that can be done.

[MrQuade]

The 0 signal quality has been reported several times in the firmware thread, so this is a known issue.

[dRdoS7]

Hi,

This appears to be an issue either with the V2 tuners' capabilities, or with the kernel level drivers. I see the same results on my test V2's built-in tuners (sensible-looking signal strength and 0% for signal quality), but different incorrect strength and quality indications on the Hauppauge! USB dual tuners (strength always 0%, quality always 100%).

So there's probably nothing that can be done in the enigma2 code. It's possible that if it's a problem with the kernel drivers, that might be fixable, but if the data isn't available from the device, there's nothing that can be done.

Hopefully, Mr Wiz HQ will will have a look at it, and see what can be done.

The 0 signal quality has been reported several times in the firmware thread, so this is a known issue.

OK, so now it's in Bugs as well.

dRdoS7