43 replies to this topic

[Rob van der Does]

cloudibox3 = miraclebox min

No: cloudibox3 = clone of miraclebox min

[mrvica]

yes, could be that way

[mrvica]

I have a workaround, no need to change StbHardware.py at the moment

just put

echo 7200 > /proc/stb/fp/rtc_offset

on starting enigma2, for example in enigma2_pre_start.sh

you can check with

cat /proc/stb/fp/rtc_offset

if it is correctly set

 

#!/bin/sh
# /usr/bin/enigma2_pre_start.sh
echo 7200 > /proc/stb/fp/rtc_offset

 

when the day-light-saving time is over we´ll propably have to put

echo 3600 > /proc/stb/fp/rtc_dffset there

just copy enigma2_pre_start.sh into /usr/bin and make it with

chmod 755 enigma2_pre_start.sh

executable

OpenATV is all OK due to changes in StbHardware.py and somewhere else according to the log on shutdown

------------------------------------------------------------------------------------

[mytest.py] normal shutdown
dvb time sync disabled... so set RTC now to current linux time! 2016/08/20 00:06
set RTC to 2016/08/20 00:06 (rtc_offset = 7200 sec.)

------------------------------------------------------------------------------------

 

Attached Files

•  enigma2_pre_start_sh.zip   350bytes   11 downloads

[littlesat]

Beside this it would be better to have something in the e2 user interface that adjust the rtc offset...

 

So via system info if such proc exists and then some values you can full in... (in steps of 1/2 an hour)...

 

So approx the same as OpenATV does... (or derived from the timezone - then we do not need a setting for it at all)....

 

I think we could also write that offset to the proc during starting of E2 (as in fact the pre start script also does)... so we can go very easy via the UsageConfig "system"... But without a config in setup.xml...

Edited by littlesat, 20 August 2016 - 09:41.