Bootsettings : Fwd/Back skip times ?

[bob_a_builder]

And another thing ......

My box has been working fine for a good number of years, using a Fwd skip of 60, Back skip of 30
I now find that the Fwd skip is ALWAYS 2 mins per button press - regardless of the number of seconds I input - yes, I reboot after each setting change

I have tried removing the Fwd / Back skip entries and re-instating them in the boot-time setting section,
Not sure if relevant but have also run the Fix-Flash-packages
Tired a different remote
Switched box off for 10 mins/restart

But Fwd still skips 2 mins each time

for the record I did upgrade from 3.13 to 3.14 yesterday, but can't be sure if this problem occurred prior to that or not, but its certainly a very recent issue

Your suggestions welcome, thanks

 

[prpr]

What does it say on the On-screen Menu? Have you tried changing it there and seeing what happens?
For the record, the /tmp/xinit.log file shows what the boot-settings package is trying to do. e.g.

[/var/lib/humaxtv/mod/xinit.d/ahw]
Micom Timestamp: 27462 - Thu Jan  1 07:37:42 1970
Power cycle detected.
Boot: 4
[/var/lib/humaxtv/mod/xinit.d/bootset]
Setting MENUCONFIG:DMS_START_ON = (Value)1
Setting MENUCONFIG:INSTANT_REPLAY = (Value)30
Setting MENUCONFIG:SKIP_FORWARD = (Value)60
[/var/lib/humaxtv/mod/xinit.d/dbupdate]
...

Do the values in the Database Browser for setup.db correspond with what you set here?

 

[bob_a_builder]

Forward skip
Onscreen said 120
xinit.log and setup.db both said 60
Although my xinit.log at that time said "AHW already done" rather than your lines 2,3,4

I think I then set it Onscreen to 60, and then also did a number of tests of different Fwd skip times made via the Web IF, and haven't seen it get out of step again since

So problem seems to have cleared for now, but I know where to look for those things now, thanks

Oddly my Xinit log last modified stamp randomly alternates between Jan 1 2000 and the correct 2026 timestamp

 

[prpr]

Oddly my Xinit log last modified stamp randomly alternates between Jan 1 2000 and the correct 2026 timestamp

The device doesn't contain a battery backed Real-Time-Clock, so it depends on whether anything's written an updated timestamp to the front-panel controller before you reboot as to what it's going to report.
The Humax software receives time off-air once it starts up (you can also use the NTP package), but it only updates the front-panel clock when going to Standby.