HDHR Quatro UK issue

#1

Just got HDHR Quatro (firmware 20180110) UK DVB today to replace my HDHR Connect.

Channels ATV and iOS tunes okay but Channels webui, Android TV and Fire TV do not. Webui just spins. Android and Fire TV display “Weak Signal”

The HDHR app doesn’t display either.

Looks like the ATV and iOS app chooses tuner 3 which works just fine with 100% signal & symbol quality. The webui, android, fire TV and the HDHR apps choose tuner 0 which has “none” signal & symbol quality.

Looks like an issue with the Quatro. I have filed a ticket with SD and will await their response. Will have to go back to the Connect for the time being.

#2

This is a known bug in the firmware that ships with the device. Upgrade to the latest and it should fix the problem.

#3

my.hdhomerun.com says I’m on the latest firmware.

#4

Okay, perhaps a different issue with the DVB models then.

#5

Yea this is the newest firmware I know of.

Let us know what SD says…

#6

They’ve asked me for diagnostics from the device which I have sent them. I’ll let you know their conclusion.

#7

I’m hovering over the buy button for the Quatro so keen to see what they say as the Connect works great in the UK

#8

Haven’t had a reply yet. Hope it’s just a firmware issue rather than a faulty batch. Probably not though. Firmware that didn’t even display an image would surely be a show stopper for shipping.

#9

Probably not what you want to hear, but I’m using the Quatro in the UK (same firmware) and have no issue with Channels on Android TV. Not quite as quick to tune as ATV or iOS (only a second or two more) but once tuned all is good.

This would suggest not firmware issue as you suspect…

#10

SD say the problem is my signal is too strong and is overloading the tuner. I have a roof aerial (virtually all homes in the UK do as we never embraced paid cable and chose OTA as our standard for receiving live TV until Sky came along with satellite). The aerial is in line of sight of Emley Moor.
It has never caused any issues with any TV or DVR I have owned or my HDHR Connect.
I have read scattered reports of this before. I’ve ordered a 10db signal attenuator from Amazon and see how I get on with that.

#11

Curiouser and curiouser said Alice.

Sent the following to SD… Await their response.

Hello,

I’ve done some more experimentation.

The HDHR Quatro displays TV channels perfectly well the FIRST time it tunes after a power cycle. I can watch that channel for as long as I want to. However once I change channels or go back to the menu and attempt to play the same channel again I get the “Weak Signal” error. It cannot tune again until another power cycle.

I have tried a 6db and 12db (and also daisy chained to “18dB”) signal attenuators but the behaviour is exactly the same except that the first time the channel tunes and displays there is digital break up because the attenuators have lowered the signal quality.

Any help would be appreciated.

#12

Strange because this sounds very similar to problem in the original DUO/QUATRO firmware when released in the US. The tuner chip would go into power saving mode and fail to tune channels.

#13

Similar issue: https://forum.silicondust.com/forum/viewtopic.php?f=113&t=68115

#14

Got an email from SD this morning. They confirm it is a firmware bug in the DVB units. Have sent me a link to a beta firmware to try. I’ll install it this evening after work and see how I get on.

#15

The beta firmware they provided for me has fixed the issue with my Quatro DVB. I have tested it with Channels ATV and FTV - with work fine.

1 Like
#16

More woes.

Despite the player working with the Channels clients on ATV and FTV there are issues with the DVR. It won’t start playing on the WebUI and recordings are failing

2018/03/16 18:34:26 [ERR] Failed to start stream on channel 101 via 12501307: got HDHR error: 807 No Video Data
2018/03/16 18:34:26 [DVR] Error running job 1521224970-ch101 BBC London News: could not start stream on channels=[101]: got HDHR error: 807 No Video Data
2018/03/16 18:34:56 [DVR] Starting job 1521224970-ch101 BBC London News on ch=[101]
2018/03/16 18:34:56 [DVR] Waiting 54m33.009005106s until next job 1521228570-28 MasterChef
2018/03/16 18:35:02 [ERR] Failed to start stream on channel 101 via 12501307: got HDHR error: 807 No Video Data
2018/03/16 18:35:02 [DVR] Error running job 1521224970-ch101 BBC London News: could not start stream on channels=[101]: got HDHR error: 807 No Video Data

#17

Now seems to be working okay. Didn’t power off the HDHR after the firmware update. Now I’ve turned it off and on again the web is playing and the recording is working. Hooray.

#18

Strange, the device usually reboots itself during the firmware upgrade process.

#19

The HDHR crashed mid stream watching the 6 Nations Rugby taking the whole debian server down. Restarted but the HDHR still wont serve up a stream. Got the following from the DVR log.

2018/03/17 14:32:17 [ERR] Failed to start stream for ch103: got HDHR error: 807 No Video Data

2018/03/17 14:32:17 [Recovery] panic recovered:
GET /devices/ANY/channels/103/hls/start.ts? HTTP/1.1
Host: 192.168.86.40:8089
Accept: /
Accept-Language: en-gb
Connection: keep-alive
Referer: http://192.168.86.40:8089/admin/guide/now
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_1) AppleWebKit/604.3.4 (KHTML, like Gecko) Version/11.0.1 Safari/604.3.4
X-Playback-Session-Id: 9F157CD4-B905-46AF-BD35-503083D746CD

runtime error: invalid memory address or nil pointer dereference
/home/vagrant/go/src/runtime/panic.go:491 (0x42cc02)
/home/vagrant/go/src/runtime/panic.go:63 (0x42bb0d)
/home/vagrant/go/src/runtime/signal_unix.go:367 (0x4441bb)
/home/vagrant/channels-server-x86_64/http.go:3440 (0xb6e4a0)
/home/vagrant/channels-server-x86_64/http.go:3111 (0xb947cf)
/home/vagrant/channels-server-x86_64/.go/src/github.com/gin-gonic/gin/context.go:104 (0x940382)
/home/vagrant/channels-server-x86_64/http.go:2823 (0xb9155f)
/home/vagrant/channels-server-x86_64/.go/src/github.com/gin-gonic/gin/context.go:104 (0x940382)
/home/vagrant/channels-server-x86_64/http.go:209 (0xb64cdb)
/home/vagrant/channels-server-x86_64/.go/src/github.com/gin-gonic/gin/context.go:104 (0x940382)
/home/vagrant/channels-server-x86_64/http.go:189 (0xb63eac)
/home/vagrant/channels-server-x86_64/.go/src/github.com/gin-gonic/gin/context.go:104 (0x940382)
/home/vagrant/channels-server-x86_64/.go/src/github.com/gin-gonic/gin/recovery.go:45 (0x951dc9)
/home/vagrant/channels-server-x86_64/.go/src/github.com/gin-gonic/gin/context.go:104 (0x940382)
/home/vagrant/channels-server-x86_64/.go/src/github.com/gin-gonic/contrib/sessions/sessions.go:65 (0xb0932f)
/home/vagrant/channels-server-x86_64/.go/src/github.com/gin-gonic/gin/context.go:104 (0x940382)
/home/vagrant/channels-server-x86_64/http.go:253 (0xb75c7e)
/home/vagrant/channels-server-x86_64/.go/src/github.com/gin-gonic/gin/context.go:104 (0x940382)
/home/vagrant/channels-server-x86_64/.go/src/github.com/gin-gonic/gin/gin.go:332 (0x948d23)
/home/vagrant/channels-server-x86_64/.go/src/github.com/gin-gonic/gin/gin.go:296 (0x9484ba)
/home/vagrant/go/src/net/http/server.go:2619 (0x6a30f3)
/home/vagrant/go/src/net/http/server.go:1801 (0x69f1dc)
/home/vagrant/go/src/runtime/asm_amd64.s:2337 (0x45e6b0)

#20

Even after a second beta this isn’t working and I’m back to using my Connect. It’s such a fundamental problem that it can’t possible have affected all the DVB units or the SD forums would be awash with refund requests!!

However SD sent me some instructions to get more info for them…

Effectively use the hdhomerun_config_gui app (which is within the package contents of the HDHR app on a Mac). This allows you to tune each tuner by number (0-3 on a Quatro) rather than get the first available - which I think is what the HDHR/Channels client asks for. It also lets you set the tuner to power saving mode by selecting channel 0. This is what I found and posted back to SD…

The problem affects tuner 0 and tuner 2. Tuners 1 and 3 work normally. I can tune any channel and get 100 signal strength and quality. I can switch them in and out of power saving mode.

On tuners 0 and 2 the first time the unit turns on they come out of power saving mode and tune correctly. If I switch channels without going back to power saving mode they tune correctly. However once I set them back to power saving mode (channel 0) they are never able to come out of it again to retune a channel. The signal strength does read 100% but the underlying barber pole is grey instead of green and the signal quality and symbol quality bars are 0%.

1 Like