DVB-T2 not working, SDR works

[anonimo82]

Hello everyone. I bought a USB DVB-T2 Stick, which is actually detected, but I get an error telling I need an empowered OTG cable. I tried plugging the stick with a USB HUB (one with its own power source), but still getting that error. SDR Touch works perfectly by the way. Unfortunately, I don't know my device' manufacturer or model, and neither its chipset, but it gets detected well, so I guess it's not that my issue.

Edit: Here is my purchase: https://www.wish.com/product/5d560916e2e4b625b34ebfac According to Device Info HW App it's a Astrometa

Thanks for any help.

[anonimo82]

@martinmarinov

[anonimo82]

P.S.: I'd actually point out the same hardware works as a FM radio, but not as a DVB-T2 TV Tuner

SM-G965F device with stock Android Q here

[anonimo82]

lsusb return this:

Bus 001 Device 007: ID 15f4:0131 HanfTek Astrometa DVB-T/T2/C FM & DAB receiver [RTL2832P]

[anonimo82]

@martinmarinov any help?

[anonimo82]

@martinmarinov help?

[martinmarinov]

Hello I'm afraid it's not clear why this is happening. This hardware should be supported. Can you try it on a different Android device (ex. your friend's phone) to eliminate the possibility of your Android device having some weird hardware issue? It is indeed puzzling that everything works fine with SDR Touch but not Aerial TV.

Maybe you can try firing the DVB-T driver app and using its test interface to tune to a local frequency and sending the log.

[anonimo82]

Hello. Tried on my sister's device right now, same result.

[martinmarinov]

Hey the latest release of the driver contains a bug fix that could have impacted some Android devices or some specific tuners. Can you try updating the app and trying again?

[anonimo82]

Tried, same result. =(

[anonimo82]

I tried again some minutes ago, this is the result:

[anonimo82]

@signalwareltd look at the attached screenshot

[martinmarinov]

@anonimo82 can you try launching the DVB Driver standalone app? It has a test interface that allows you to tune your device to a local frequency. If you know your local DVB-T transmitter frequency try tuning on that one, otherwise put any random frequency. Given this seems to be some sort of connection problem it should show clearly what the problem is.

[anonimo82]

@martinmarinov here is the output from such operation

Please give more information about the crash here. We can't promise to respond to every email but your input is very valuable to us and will help improve the driver!
 
 Stack trace and exception (DO NOT EDIT): Cannot send USB control message. Error code -1

info.martinmarinov.drivers.DvbException: Cannot send USB control message. Error code -1
	at info.martinmarinov.drivers.usb.rtl28xx.Rtl28xxDvbDevice.ctrlMsg(Rtl28xxDvbDevice.java:89)
	at info.martinmarinov.drivers.usb.rtl28xx.Rtl28xxTunerType$14.getSlave(Rtl28xxTunerType.java:155)
	at info.martinmarinov.drivers.usb.rtl28xx.Rtl28xxTunerType.detectSlave(Rtl28xxTunerType.java:198)
	at info.martinmarinov.drivers.usb.rtl28xx.Rtl2832DvbDevice$1.run(Rtl2832DvbDevice.java:94)
	at info.martinmarinov.drivers.tools.I2cAdapter$I2GateControl.runInOpenGate(I2cAdapter.java:107)
	at info.martinmarinov.drivers.usb.rtl28xx.Rtl2832DvbDevice.readConfig(Rtl2832DvbDevice.java:90)
	at info.martinmarinov.drivers.usb.DvbUsbDevice$1.run(DvbUsbDevice.java:106)
	at info.martinmarinov.drivers.tools.Retry$1.call(Retry.java:32)
	at info.martinmarinov.drivers.tools.Retry$1.call(Retry.java:29)
	at info.martinmarinov.drivers.tools.Retry.retry(Retry.java:42)
	at info.martinmarinov.drivers.tools.Retry.retry(Retry.java:29)
	at info.martinmarinov.drivers.usb.DvbUsbDevice.open(DvbUsbDevice.java:102)
	at info.martinmarinov.dvbdriver.DeviceController.run(DeviceController.java:67)
 
 Last Device: null
Build.MANUFACTURER: samsung
Build.MODEL: SM-G965F
Build.PRODUCT: star2ltexx
Build.VERSION.SDK_INT: 29
Build.VERSION.RELEASE: 10
Driver versionName: 1.4
Driver versionCode: 18
 
 --------------------------- 

[martinmarinov]

This could be an indication that a different app is trying to use the USB tuner.

I would recommend disconnecting and connecting the tuner back again after being used for SDR before using it for DVB-T. If you have any apps that automatically start the tuner in SDR mode as soon as the tuner is plugged in make sure to disable them.

If the tuner is already put into SDR mode, the DVB Driver may fail to put it back into DVB-T mode. The SDR mode is a special "debug" mode for the chip so it may not be possible to put it back to normal operation. Even if it's possible the rtl-sdr library never had to do it as normally in most set ups on Desktop you cannot have both SDR and DVB-T drivers installed at the same time.

The exception you see is an indication that the tuner is not responding to commands send from Android. This is usually an indication that tuner is in a bad state. I've seen this with some combination of USB-C to USB-A converters as well so it might be this but given SDR works it's unlikely that the cable is the issue.

[anonimo82]

I tried removing SDR Touch and its driver, disabling USB Debug and resetting the DVB Driver App (in combinations), but same result. Yes, I'm using a USB-C to USB-A adapter, I couldn't connect the tuner otherwise. See attached pic.

[martinmarinov]

Hello I'm afraid at this stage it's not clear to me what could be causing the issue. It's possible that this device has some new hardware that has some incompatibilities with the driver.

Unfortunately I'll only be able to order myself this device from Wish in early 2023. I'll leave this issue open in the meantime if you find any solution please feel free to post here.