...and if you're an insomniac with the TV on in the middle of the night (0430 to be exact), it's bloody annoying that the Humax goes out of service for a period.
Preventing External Events from Disturbing the CF (click)
"Until 30th October" – but which year?! It's hardly moot if BBC were supposed to be supporting iPlayer on HD-FOX but weren't.
Sure, but I'm talking about the difference between a casual consumer and an enthusiast. Casual consumers are not likely to be cobbling together kit which can rip...
So pretty much what I said then. "Not certified" means limited capability no longer able to keep up. "Was" is true – it was iPlayer-capable in the past. And why would you expect any manufacturer to expend effort and cost revising an obsolete unit? It did what it was supposed to do when sold...
The Humax black box is known to respond to situations not anticipated by the programmers with misleading messages (and potentially actions). In a case where the CF is active, for example, we know the standard firmware gets confused and claims a HDD can't be formatted because it's too big (when...
More weirdness has presented this morning:
The same is shown in SUI. I have no idea where the duplicated Breakfast reminder came from, most (if not all) methods for adding it would detect the duplication. Other entries are not duplicated.
Hmm. Auto schedule backups have a gap, last one...
What is this, exactly? The disable-ota checking the schedule database for the 4.30 OTA check and removing it if found? If so, how about "Anti-OTA" (and the other one "Anti-DSO")?
These logs are now showing as complete, with entries showing in the intervening period, and there is a smoking gun:
4274 30/10/2024 08:12:02 - Unscheduled --- Auto Update --- @ 1730345400
4273 30/10/2024 08:06:49 - System booted (Power cycle).
4272 30/10/2024 03:04:02 - Unscheduled...
I guess fix-flash-packages (etc) will fix the logging. It seems a blunt instrument though, in as much as it provides no report on whether anything actually needed fixing.
I'm getting this on a frequent basis, on a HDR-FOX and a HD-FOX, but the HD-FOX is the current case in point. I'm posting in the CF section only because CF will be involved in the process of diagnosis.
Left to its own devices over the weekend (not in standby), the unit in question recorded on...
...and if you're an insomniac with the TV on in the middle of the night (0430 to be exact), it's bloody annoying that the Humax goes out of service for a period.
Preventing External Events from Disturbing the CF (click)
"Until 30th October" – but which year?! It's hardly moot if BBC were supposed to be supporting iPlayer on HD-FOX but weren't.
Sure, but I'm talking about the difference between a casual consumer and an enthusiast. Casual consumers are not likely to be cobbling together kit which can rip...
So pretty much what I said then. "Not certified" means limited capability no longer able to keep up. "Was" is true – it was iPlayer-capable in the past. And why would you expect any manufacturer to expend effort and cost revising an obsolete unit? It did what it was supposed to do when sold...
The Humax black box is known to respond to situations not anticipated by the programmers with misleading messages (and potentially actions). In a case where the CF is active, for example, we know the standard firmware gets confused and claims a HDD can't be formatted because it's too big (when...
More weirdness has presented this morning:
The same is shown in SUI. I have no idea where the duplicated Breakfast reminder came from, most (if not all) methods for adding it would detect the duplication. Other entries are not duplicated.
Hmm. Auto schedule backups have a gap, last one...
What is this, exactly? The disable-ota checking the schedule database for the 4.30 OTA check and removing it if found? If so, how about "Anti-OTA" (and the other one "Anti-DSO")?
These logs are now showing as complete, with entries showing in the intervening period, and there is a smoking gun:
4274 30/10/2024 08:12:02 - Unscheduled --- Auto Update --- @ 1730345400
4273 30/10/2024 08:06:49 - System booted (Power cycle).
4272 30/10/2024 03:04:02 - Unscheduled...
I guess fix-flash-packages (etc) will fix the logging. It seems a blunt instrument though, in as much as it provides no report on whether anything actually needed fixing.
I'm getting this on a frequent basis, on a HDR-FOX and a HD-FOX, but the HD-FOX is the current case in point. I'm posting in the CF section only because CF will be involved in the process of diagnosis.
Left to its own devices over the weekend (not in standby), the unit in question recorded on...
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.