GTMedia V8 Finder Pro 2 Some Questions

[MrToy]

Hello everyone!

I bought GTMedia V8 Finder Pro 2. This is a great device! I immediately updated the device to the latest firmware version GTMedia_V8FinderPro2_V377_20251210.zip (10/12/2025).

But it seems to me that there are some annoying bugs in the firmware.

1. The buttons are too noisy or too sensitive. Sometimes they trigger twice. The buttons need to be corrected in the software (increase the keystroke recognition time) in the next firmware update.

2. The supply voltage and polarization switching of the 13/18V for LNB is not completely switched off. I do it in the settings "LNB Power" Off, in this case the polarization switching voltage 13/18V on LNB IN connector, does not down to 0V, but remains at 7V.

This is a bug needs to be fixed so that the voltage down to 0V.

Also need to fix the operation of the 13V/18V LED, which lights up and continues to change its state from red to green when switching polarization from V to H when LNB Power Off. In this case, you need to make LED light yellow and not change color when switching polarization from V to H and back. Because when the supply voltage and polarization switching are turned off, and the LED continues to light red or green and change its state when selecting polarization, this is confusing and misleading. Or turn off the LED altogether when LNB Power Off.



3. It seems logical that at a lower voltage of 13V for vertical polarization, the 13V/18V LED would light green, and at a higher voltage of 18V for horizontal polarization, the 13V/18V LED would light red. However, the logic is currently reversed. This can be easily corrected with software.

4. The internet works, but YouTube doesn't work. It doesn't even work with search. Apparently, the device isn't processing YouTube links of the video correctly.

For example, similarly, It happens to me an alternative YouTube client, NewPipe, for the Android.

Initially, NewPipe shows YouTube videos.
Then YouTube changes something in the links, and NewPipe stops showing videos.
Then, NewPipe's author fixes the program's method for obtaining YouTube links, and NewPipe starts showing videos again.
This has happened several times already.
Please fix YouTube's behavior in the next firmware version.




5. There are many reports the internet about the poor performance of the DVB-T2 in the device. The photo from the Spectrum Analyzer shows a signal at 690MHz, 48 Ch. However, the device doesn't process it. Please improve the DVB-T2 performance in the device, in the next firmware update.




6. Green scale signal quality of the multiplex (MER parameter) in DVB-T2 is always shows 97% and does not change. This error can be viewed at the link starting at 01:50 (in Russian language).
https://rutube.ru/video/7b0bed857b44255 ... 3f1d5ea5f/



7. Incorrect Spectrum Analyzer readings in Terrestrial mode. When parameters Bandwidh in Full and Mode in Full are selected in the Spectrum Analyzer, everything is displayed correctly, and the cursor accurately displays the frequency. But when parameters Bandwidh in Full and Mode in Ch, then the cursor points to 40MHz on the scale to the left from the frequency of the multiplex. This error for the 610MHz frequency, can be viewed at the link from 03:40 (in Russian language).
https://rutube.ru/video/7b0bed857b44255 ... 3f1d5ea5f/




Dear developers, GTMedia V8 Finder Pro 2 is truly great device! Please don't be lazy; fix these minor but annoying bugs in the next firmware update. After all, Chinese technology - is a Great technology!

Best Regards!

[MrToy]

Update

For 48Ch, 690MHz

Carrier Level: 62,32dBμV


Noise Level: 40,30dBμV


The difference between Carrier Level and Noise Level makes up 22,02dBμV and it works.


For 31Ch, 554MHz

Carrier Level: 65,79dBμV


Noise Level: 43,82dBμV


The difference between Carrier Level and Noise Level makes up 21,97dBμV and it don't works.


Maybe, to make the device more sensitive, it is necessary to configure the videoprocessor settings so that the videoprocessor begins decoding the T2 signal when the difference between the Carrier Level and Noise Levels is 10dBμV?

Dear developers, I have a big request for you: please do something... It's a shame that this device isn't a TV T2 signal finder at the moment. It's just a small, insensitive television at the moment. If you were able to design and build such a complex device, then surely you could perfect it to the point where its performance as a TV T2 signal finder would be simply brilliant?

[CAJE]

10 dB is such a bad signal that you won't see anything.
You should use the Finder to get better readings; you can buy a better antenna or use a good amplifier

[MrToy]

In the photo of 31Ch, 554 MHz, it's clear that the T2 signal is present, but the device isn't decoding it, and I think you understand this perfectly well. After reading the forum, it seems to me that you're acting like a psychotherapist there. But I think you should try to improve the device's performance, since we paid you money. And it's a shame that such a wonderful device has such an annoying flaw, how bad sensitivity T2.

A regular TV, under the same conditions and with the same antenna, decoded this T2 signal 31Ch 554MHz...

[CAJE]

-80 dBm is sufficient; the Finder has no problems. It's the installation you need to improve.

[MrToy]

Look at the photo. There's a high T2 signal level here. Why isn't the finder decoding the signal?