I remember that tune; we are probably of a similar vintage. GCHQ/ NSA bots, probably scraping this forum while I type, must be asssembling detailed profiles of our some of our members: I wonder what they make of The Hummy Arms?!peterpi said:To quote a Beggar and Co number from the eighties, "Somebody help me out".
I remember that tune; we are probably of a similar vintage. GCHQ/ NSA bots, probably scraping this forum while I type, must be asssembling detailed profiles of our some of our members: I wonder what they make of The Hummy Arms?!
Ah. Hence why mine updated because it is almost permanently on and would not have had the update event deleted.As I have mentioned many times before, there is a slim chance that disable-ota will still allow one through. The OTA searches are added to the schedule from time to time by the standard Humax firmware, when it finds the schedule item is not there already. The disable-ota package deletes the schedule entry when it finds one, but can only queue a deletion pending request for when the schedule database is not locked - ie at the next boot. If an OTA search is added to the schedule and then acted on without a reboot in between, and happens to coincide with when an OTA is being transmitted, the OTA gets through.
I'll set such.The solution is a manual reminder entry, full details by following the reference in Things Every... (click) section 1.
As some people seem to have problems with this. Perhaps the disable-ota package should also schedule a reminder event if it does not already exist.
Good idea - another possible option I've been considering is to tweak the REGULAR_AUTO_UPDATE variables in the setup database. In particular REGULAR_AUTO_UPDATE_TARGET could be changed to something high so that the OTA wakeup isn't recognised as such.. I think the reminder option is safest and covers all bases though.As some people seem to have problems with this. Perhaps the disable-ota package should also schedule a reminder event if it does not already exist.
The WebIF and RS cannot modify the schedule without reboots occurring. It used to be thought that the HDR is more prone to crashing and misoperation if run continuously, I have left mine on quite a lot and sometimes find them frozen.My box is permanently on - should I schedule a reboot once a week?
If a reminder is built-in to the Disable-OTA package, would the Humax be able to cope with a reminder for the same time that a user may have already have set?Good idea - reminder option is safest and covers all bases though.
if it does not already exist.
humax# ./xota
Opening /var/lib/humaxtv/rsv.db
XOTA: Removed auto-update scheduled events.
Did not find a reminder, setting.
Setting reminder on channel ITV2 (65537)