View Full Version : [GiGaBlue QUAD+ PLUS] 4.2.003 Unable to tune with Cable Tuner
Hi Guys
Has anyone tried 4.2.003 on the Gigablue Quad Plus with a Cable Tuner on Virgin yet?
It instantly comes up saying cannot tune. Settings all exactly the same as 4.1.016 (flashed back and forth to compare). As soon as I restore the imagine backup for 4.1.016 it works, back to 4.2.003 and it doesn't.
Satellite 28.2 channels are tuning fine.
Thanks
Tried updating to 4.2.004 this morning just to check but knew it would fail as there is no changes specific to the box.
Some other information:
ABM works fine and finds all the channels
Automatic scan menu takes about 2 minutes to load, but eventually does
Automatic scan with the DVB-C tuners works and finds 561 channels
Zapping still fails instantly. Not like the old Cannot find PAT or whatever it was which took a second or two, just an instant:
"Service unavailable!
Check tuner configuration!"
Anybody have any ideas?
Thanks for the bit of info bout restoring box to 4.1.016. Was having same issue with a gblue x3 but restoring to an older build has it working. Thanks
Sent from my Nexus 6 using Tapatalk
Sounds like a driver issue. Has Gigablue changed drivers.
I've tested a X3 with a twin hybrid tuner and build 4.2.004 no issues, I'll test single hybrid later in the week.
Looking at the release notes there is only this with giga in it:
[gigablue] add first working driver 73625 model
[tbsdtv] add support for gigablue kernel 3.9.6
oe-alliance-wifi - preinstall enigma2-plugin-drivers-network-usb-rtl8812au for GigaBlue
[GigaBlue] add dvb-module gb73625
[gigablue] kernel add patch for 73625
The Quad+ isn't bcm73625 though, it's bcm7356. This only throws up one item in the change log:
[dags] update drivers optimise framebuffer support 7362 and 7356 mode hd and fullhd skin 7335 hd skin only !
No idea what dags is though, assuming another brand completely.
Is it possible to take drivers from 4.1.016 via FTP and load into 4.2 to test somehow or is it all embedded?
Looking at the release notes there is only this with giga in it:
[gigablue] add first working driver 73625 model
[tbsdtv] add support for gigablue kernel 3.9.6
oe-alliance-wifi - preinstall enigma2-plugin-drivers-network-usb-rtl8812au for GigaBlue
[GigaBlue] add dvb-module gb73625
[gigablue] kernel add patch for 73625
The Quad+ isn't bcm73625 though, it's bcm7356. This only throws up one item in the change log:
[dags] update drivers optimise framebuffer support 7362 and 7356 mode hd and fullhd skin 7335 hd skin only !
No idea what dags is though, assuming another brand completely.
Is it possible to take drivers from 4.1.016 via FTP and load into 4.2 to test somehow or is it all embedded?
Dags encompasses the Technomate E2 brand and 2 other OEM's such the Edison Optimus OS receivers (there is a third brand but I can't remember the name). There all built in the same factory but intended for different markets. TM (uk) Optimus (Germany and the continent) and the third one is pretty much only sold in Scandinavia but there all pretty much identical image / driver wise.
Ok thanks, that makes more sense now.
Just flashed back and forth to check driver versions:
4.1.016 Driver date: 20160301
4.2.004 Driver date: 20160301
I think we might be barking up the wrong tree with it being drivers?
Any other ideas of things to check?
Sorry for the spam - just flashed 4.2.005 and all I did was run through the wizard, did not restore settings, configured tuners, configured ABM and scanned to get the channels. Exactly the same, DVB-S is fine and all the DVB-C get a tune error immediately. I tested with the FTA channels in case something else was messing it up.
Also having the same issue, i thought it was just my receiver but thankfully it's not just me :-) back to a previous image i go
martin20009
24-09-16, 19:50
I'm having the same issue with my quad, just started a new thread, didn't see this at first.
See screenshot for working settings.
It's ok to use up to build 4.2.002. There is an issue in build 4.2.003 onwards with Qaud+ and hybrid tuners.
Only issue noted is on giga hybrid single T/C tuner.
No other brand or tuner affected.
Thanks for confirmation. Could someone post when it's fixed please (or just let me know if it will be fixed in 4.2.006 and I'll keep an eye out)? I have set up 4.2.005 image already so will just restore that image backup and update when available.
No idea when this will be fixed. Needs tracking down and that is a lot of work, not trivial. Right now there is nothing to tell us what is causing this. Settings are identical on both images (before and after). As this is the only tuner suffering this out of all the receivers supported it is likely due to a driver acting in a non-standard way.
Twin PnP Gigablue tuner works fine, which confirms there is nothing wrong with the code in Enigma2.
Flashes 4.2.002 everything worked fine but then same issue again aftet switching the box on from deep standby. Using gigablue hdx3.
Sent from my Nexus 6 using Tapatalk
guys is this problem just on cable tuners ?
About to buy the quad+ with 4 x DVB-S2 tuners , dont want to be buying into any hassle
abu baniaz
28-09-16, 20:47
guys is this problem just on cable tuners ?
About to buy the quad+ with 4 x DVB-S2 tuners , dont want to be buying into any hassle
Only cable tuners affected
tiggerbiker
28-09-16, 21:01
Only cable tuners affected
and only the newer tuners at that.
the older ones work fine
This issue is fixed. You just need to wait for the next update. You'll see the fix in the changelog.
Powered by vBulletin® Version 4.2.5 Copyright © 2024 vBulletin Solutions Inc. All rights reserved.