The reason that the above occurred was that I had downloaded the 1.02.32 firmware by mistake, on installing the correct version 1.03.12 I was back to the original problem. As get_iplayer works for me I am no longer bothering to spend any time trying to get the portal working.
I have now re-installed the standard firmware and I now can get the Portal up but when I click on iplayer I get a message saying device is not recognised.
Will investigate further at the weekend.
While it was in this loading state I tried connecting into the box with web-if, the normal screen icons came up along with a message saying the the box had crashed. The crash.log just said Humax crashed at Mon Nov 3 21:46:19 UTC 2014 - Uptime: 3855 and on exiting TV Portal web-if then worked o/k
What I get is the normal rotating sign with a black rectangle behind it, the rotating sign then disappears leaving the black rectangle with Loading displayed in it and an outline of a small square. If I press TV Portal again the outline of a small square changes to a small triangle with lines in...
I ran diagnostic remove_portals which said no portals have been found and tried Black Hole's option to clear DRM data but still the same result. The only change I noticed was that I accidentally pressed Humax Portal twice and a an extra small blue triangle appeared on the Loading Image.
Is the Portal down today as it justs stays at Loading?
Web Interface 1.0.17-7
Custom Firmware 3.00 (Build 2137)
Humax Version 1.03.12 ( Kernel HDR_CFW_3.00)
Still not working as per 1900 1/11
Ezra nothing is being recorded at these times, Black Hole I use Scart as when using HDMI I was getting intermittent lockups when changing channels i.e picture locked and unable to change channel but anything that was being recorded was o/k, this problem has never shown up on Scart. I might HMDI...
My HDR-FOX T2 intermittently switches the TV to the Scart I/F when in Standby ( Note - its still stays in Standby it doesn't power up). This usually happens at 18-40 or 19-10 and I have only noticed this happening since the OTA 1.03.12 firmware upgrade. Any ideas what to look for that might...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.