[NOT QUAD+] recording problem

[Joe_90]

@Ojustaboo - I presume you have seen some of the other postings from Sicilian about the temperature readings in the Quad? The reported temp readings seem to be too high and don't reflect the real situation. To me, that makes sense as several Quad owners report these high temps, but without any other symptoms. If the heat sink on your box is only warm and the reported temp is 90C, then it would indicate that either the reading is wrong or that your heatsink is not doing its job. The actual surface area of a processor is very small and will heat up very quickly once it starts to run at a high usage level. If the heatsink is doing its job it should conduct heat away from the processor and become warm. So, assuming the heatsink is mounted correctly and is actually conducting heat away from the processor, it should become very warm or too hot to touch if the processor temp actually rises to 90C.

I still haven't had any issues since Wednesday with my playback glitching and my reported temps are still mid 40s. Like you, I can't go back to a previous bootloader as I don't recall one ever being published on-line by Gigablue for the Quad+, other than the new one. I'm sorry that this doesn't help your issue, though. I did find an older Quad bootloader (not Plus) on

http://archiv.openmips.com/

if you wanted to try. You should verify with other Quad users, though, as a failed bootloader install will brick your box.

[Stanman]

Temp reading are unreliable. Mine has hit 105 and still functions fine. IMHO I think it's a driver issue or bootloader as getting random reboots whilst watching or when three tuners have a recording running.

Could be kernel as well but without crash logs dam difficult to fault find.

Sent from my SM-N9005 using Tapatalk

[Ojustaboo]

Thanks. Stef at world-of-satellite has read this thread and is issueing me an RMA no on Monday.

No box for 2 to 3 weeks as it has to go to Germany. So lots of Netflix for a few weeks.

[thestoress]

It's surely reading wrong?

[Joe_90]

Thanks. Stef at world-of-satellite has read this thread and is issueing me an RMA no on Monday.

No box for 2 to 3 weeks as it has to go to Germany. So lots of Netflix for a few weeks.

Bad news in the short term, but they will get to the bottom of the issue. Stef will look after you

[dwarf]

I flashed build 26 on my Quad plus and was having problems watching one program and streaming another via openwebif or the remotestreamconvertor to my 800ue+.

I rebooted the box several times but I just couldn't get it to work at all. I never tested recording but I would assume it would have been the same if I tested it.

Transcoding wouldn't work at all either just locked the box up.

Was the bootloader flash mandatory to use the new 2.3 based images? I never flashed the bootloader I just went back to build 24 and used the 31/7/14 drivers from the openmips website and the box is performing perfectly. All tuners can stream externally and transcoding works albeit with poor quality.

I never mentioned it as I just assumed that gigablue had made an arse of the drivers for the new kernel (like they normally do with major releases) and in time they would sort it.

[Ojustaboo]

I just went back to build 24 and used the 31/7/14 drivers from the openmips website and the box is performing perfectly.

Why did you use the drivers from the openmip site? I just went back to 24 (just installed the ViX image, no other drivers) and the info says the drivers are 31/7/14

Or am I missing something?

Thanks

[Joe_90]

Why did you use the drivers from the openmip site? I just went back to 24 (just installed the ViX image, no other drivers) and the info says the drivers are 31/7/14

Or am I missing something?

Thanks

The ViX build 024 contains the newer drivers from 31/7. There are older drivers from 10/07 available on the openmips archive. But the bootloader changed from ViX 025 onwards.

As you changed the bootloader, but @dwarf didn't, maybe you should revert? But as I posted before, it's riskier flashing bootloaders so double check everything if you are going to do it.

[dwarf]

Why did you use the drivers from the openmip site? I just went back to 24 (just installed the ViX image, no other drivers) and the info says the drivers are 31/7/14

Or am I missing something?

Thanks

Sorry your right I actually went back to build 23 as that's the build I was on previously and it worked perfectly. Build 24 is probably perfect.

The drivers in build 26 were from August (I'm assuming to support the new kernel) and aren't listed on the openmips archive site.

[steveharman]

I'm getting the pixelated / freeze / resume issue with playback on my GBQuad and have been ever since 025. Now on 026 and it's just the same. ALWAYS when recording one thing and playing back another (from the hdd).

Really disappointed with the 025/6 release - reverting to 024.

Steve

[bellejt]

I started a simular topic for the VU duo2 with same problem for remote streaming.Also went back to 24 .Seems a major problem on several boxes with apollo 26.Just Rob VDD doesn't have the problem.

[Joe_90]

I'm just back online after watching Dr Who recorded earlier. Full of glitches and stutters. At one stage I had frozen video while the audio continued on. Rewound back 30 seconds and the same passage was fine on replay. Continued with glitching all the way to the end.

[Joe_90]

Having looked through the debug logs (which are a PITA because they have no timestamps!) for the time during which I was watching the playback of Dr. Who I can see sections where the following errors are reported in the logs. Anyone hazard a guess as to what they might be?

eFilePushThread WRITE ERROR
eFilePushThread WRITE ERROR
eFilePushThread WRITE ERROR
eFilePushThread WRITE ERROR
eFilePushThread WRITE ERROR
eFilePushThread WRITE ERROR
eFilePushThread WRITE ERROR
eFilePushThread WRITE ERROR
eFilePushThread WRITE ERROR
eFilePushThread WRITE ERROR
eFilePushThread WRITE ERROR
eFilePushThread WRITE ERROR
eFilePushThread WRITE ERROR
eFilePushThread WRITE ERROR
eFilePushThread WRITE ERROR
eFilePushThread WRITE ERROR
eFilePushThread WRITE ERROR
eFilePushThread WRITE ERROR
eFilePushThread WRITE ERROR
eFilePushThread WRITE ERROR
eFilePushThread WRITE ERROR
eFilePushThread WRITE ERROR
eFilePushThread WRITE ERROR
eFilePushThread WRITE ERROR
eFilePushThread WRITE ERROR
eFilePushThread WRITE ERROR
eFilePushThread WRITE ERROR
eFilePushThread WRITE ERROR
eFilePushThread WRITE ERROR
eFilePushThread WRITE ERROR
eFilePushThread WRITE ERROR
eFilePushThread WRITE ERROR
eFilePushThread WRITE ERROR
eFilePushThread WRITE ERROR
eFilePushThread WRITE ERROR
eFilePushThread WRITE ERROR
eFilePushThread WRITE ERROR
eFilePushThread WRITE ERROR

[judge]

kernel & driver issues so.

[thestoress]

Is the temperature actually reading in Fahrenheit instead of Celsius ?