Foxtrot204
Member
I have observed this happen two or three times before and it required retuning etc. Does anyone have any ideas as to why this is happening please?.
...but it has been suggested that it is triggered if the databases become corrupt. All the configuration data is held in SQLite data structures, and rebuilding them from scratch may be the best way.No-one has yet found the root cause
Restoring User Settings after Restore Factory DefaultsIf you have the cutomised firmware installed there are some packages available that make it easier to restore your recording schedule and other settings after you experience the Wizzard,
Very possible - I guess setup.db, freq.db and channel.db would be the key databases....but it has been suggested that it is triggered if the databases become corrupt. All the configuration data is held in SQLite data structures, and rebuilding them from scratch may be the best way.
So, like, you've not bothered with Restoring User Settings after Restore Factory Defaults then? (yes, that is a link)This may expedite initial settings after random start wizard (I've only tested this method with the manual factory reset option)
Requires Custom Firmware with boot-settings, virtual-disk2 (or real USB drive attached)
Set WebIF/settings/Settings for boot-settings package with something like
- Content Sharing
- Volume
- Screen Resolution
- Standby Power Saving
- Automatic Power Down
- Sound Output
- OSD Transparency
I have wondered if forcing WIZARD_CMPLTD to 1 [would help]
# ls /var/lib/humaxtv
TZ dtcp.rng resolv.conf rsv_fail.db udhcpc.wlan0.pid
bootset.db ext_hdd_info resolv.conf.bak rsvp.db
browser freq.db route.eth0.conf setup.db
channel.db mm.db route.wlan0.conf setup1.db
drm mod rsv.db tempsetup.db
#
mod
)# ls -l /var/lib/humaxtv_backup
total 0
drwxr-xr-x 6 root root 0 Sep 23 16:02 mod
#
In my recent occurrence, setup.db had become long-term locked for whatever reason. In trying to ascertain why, and learn more, I managed to stuff it completely. Attempts to restore a backup failed, as I found out when I next rebooted - I knew what was probably coming and wasn't disappointed (well I was, but you know what I mean).but it has been suggested that it is triggered if the databases become corrupt.
freq.db is an invention of tunefix, so is not at all key. It just stores the backup signal strength/quality data.I guess setup.db, freq.db and channel.db would be the key databases.
Would it perhaps have worked if restored early in bootup prior to start of humaxtv as suggested in #6Attempts to restore a backup failed, as I found out when I next rebooted
Probably need to check that it is immediately after boot timeHow to avoid also catching a manual factory reset?
And even if you do get a random restore defaults, it's easy to restore user settings (with the correct preparation): Restoring User Settings after Restore Factory Defaults
That won't work if you've done a system flush.bottletop has also proposed a means to auto-restore the database files from backup
What part of:read everything but no wiser