OK guys updated the image successfully to 5.1.006.
Now the timer is wrong, the correct time should be 11.26 but it shows on the solo2 box 14.23
Help
OK guys updated the image successfully to 5.1.006.
Now the timer is wrong, the correct time should be 11.26 but it shows on the solo2 box 14.23
Help
VU+ Solo2, Vix 6.2.005. (miss Apollo.153 though)
Triax TD110
Darkmotor Superior
Inverto Black Ultra
TH50PF10
Lumagen 2021
Arcam 888/ P7
Harmony Elite
B&W 803N, HTM2, 805N, AWS800
Have you checked your time settings are correct in the menu/setup/time?
Octagon SF8008 4K, VU+Duo 2..
Edision OS MINI,
Just move to a country where the time would be correct
Gigablue Quad 4K & UE 4K
.........FBC Tuners:
------------------> GT-Sat unicable LNB to 1.5M dish(28.2E)
------------------> Gigablue unicable LNB to 80 cm dish(19.2E)
.......................> FBC & DVB-S2X into 90cm dish (27.5W) Opticum robust Unicable LNB
AX HD61, Edision Osmio 4K+, Zgemma H9Combo, Octagon SF8008 , gbtrio4k, h9se using unicable ports
Zgemma H9 C/S into Giga4K
I think it is the fake hardware clock commits.
Hiya all seemed to have sorted itself out about 12.15pm. The time is currently now correct. Cheers
VU+ Solo2, Vix 6.2.005. (miss Apollo.153 though)
Triax TD110
Darkmotor Superior
Inverto Black Ultra
TH50PF10
Lumagen 2021
Arcam 888/ P7
Harmony Elite
B&W 803N, HTM2, 805N, AWS800
had the same last week and needed to just choose right time zone and reboot box.
VU+ DUO2 quad tuner with HDD 1 TB + Latest Openvix and VU+ DUO2 FB tuner + Octagon SF8008 FB tuner
Triax 88 cm rotor single LNB 30 E- 40 W
1 Gibertini 1.00 m fixed - 3 quad LNB 19E-23.5E-28.2E
Waking up from deep sleep = wrong time.
Perform an E2 restart after this, time corrects itself.
E2 never syncs time if the time appears plausible (year is 2004 or later) on boot.
Either switch to NTP sync (which I would recommend after seeing the code in dvbtime.cpp) and/or wait for OpenViX to merge latest changes to dvbtime.cpp from OpenATV or OpenHDF.
During the holidays I didn't manage to create a pull for OpenViX, but the team should be able to pick it up.
The change makes E2 always try to sync with the transponder time, no matter what time/date the box has at boot.
Gesendet von meinem SM-N910F mit Tapatalk
Receiver/TV:Pay TV: Redlight Mega, Brazzers TV Europe, XXL, HD-, Sky
- Vu+ Duo² 4*S2+2*C / 1.8TB HDD / OpenATV 6.1@Samsung 50" Plasma
- AX Quadbox 2400 / 2*S2/2*C / 930GB HDD / OpenATV 6.1@Samsung 32" LCD
- Vu+ Solo² / 465GB HDD / OpenATV 6.1
- Vu+ Solo² / 230GB HDD / OpenATV 6.1
- DVBSky S2-Twin-Tuner PCIe@Samsung SyncMaster T240HD (PC)
Internet: Unitymedia 1play 100 / Cisco EPC3212 + Linksys WRT1900ACS + Fritz!Box 7390 / IPv4 (UM) + IPv6 (HE)
There is a pull request against branch Dev now: https://github.com/OpenViX/enigma2/pull/205
Receiver/TV:Pay TV: Redlight Mega, Brazzers TV Europe, XXL, HD-, Sky
- Vu+ Duo² 4*S2+2*C / 1.8TB HDD / OpenATV 6.1@Samsung 50" Plasma
- AX Quadbox 2400 / 2*S2/2*C / 930GB HDD / OpenATV 6.1@Samsung 32" LCD
- Vu+ Solo² / 465GB HDD / OpenATV 6.1
- Vu+ Solo² / 230GB HDD / OpenATV 6.1
- DVBSky S2-Twin-Tuner PCIe@Samsung SyncMaster T240HD (PC)
Internet: Unitymedia 1play 100 / Cisco EPC3212 + Linksys WRT1900ACS + Fritz!Box 7390 / IPv4 (UM) + IPv6 (HE)
Sicilian (26-12-17)
Is this pull request going to fix the problems fake hardware clock has introduced?
Apart from Tm twin + Vhannibal +10e, never had a problems with transponder time.
Last edited by abu baniaz; 26-12-17 at 18:41.
in first vix images we could choose to set time ourselfs.Maybe that should be re-enterred in image.
PS: did not have any problems besides the one 2 weeks ago and solution was mentioned.
VU+ DUO2 quad tuner with HDD 1 TB + Latest Openvix and VU+ DUO2 FB tuner + Octagon SF8008 FB tuner
Triax 88 cm rotor single LNB 30 E- 40 W
1 Gibertini 1.00 m fixed - 3 quad LNB 19E-23.5E-28.2E
It removes the assumption that ANY time later 2004 is a correct one, so that E2 will wait for the first transponder sync again.
So yes, it should result in the old behaviour (Which wasn't good either, but I'm not capable of coming up with something better).
Gesendet von meinem SM-N910F mit Tapatalk
Receiver/TV:Pay TV: Redlight Mega, Brazzers TV Europe, XXL, HD-, Sky
- Vu+ Duo² 4*S2+2*C / 1.8TB HDD / OpenATV 6.1@Samsung 50" Plasma
- AX Quadbox 2400 / 2*S2/2*C / 930GB HDD / OpenATV 6.1@Samsung 32" LCD
- Vu+ Solo² / 465GB HDD / OpenATV 6.1
- Vu+ Solo² / 230GB HDD / OpenATV 6.1
- DVBSky S2-Twin-Tuner PCIe@Samsung SyncMaster T240HD (PC)
Internet: Unitymedia 1play 100 / Cisco EPC3212 + Linksys WRT1900ACS + Fritz!Box 7390 / IPv4 (UM) + IPv6 (HE)
I thought about that. It would easily be possible to patch in the build time at build.
But that would only be of limited use, as the image build time would be later, not to talk about last shutdown.
Additionally, systemd as well advances the system time to its build time if its 1970, so in the future we would always need to take care that the E2 build time is later than that of systemd (later) or the image.
The current patch changes, that the system time doesn't matter at all, the first sync is always performed, which equals the previous behavior.
Gesendet von meinem SM-N910F mit Tapatalk
Receiver/TV:Pay TV: Redlight Mega, Brazzers TV Europe, XXL, HD-, Sky
- Vu+ Duo² 4*S2+2*C / 1.8TB HDD / OpenATV 6.1@Samsung 50" Plasma
- AX Quadbox 2400 / 2*S2/2*C / 930GB HDD / OpenATV 6.1@Samsung 32" LCD
- Vu+ Solo² / 465GB HDD / OpenATV 6.1
- Vu+ Solo² / 230GB HDD / OpenATV 6.1
- DVBSky S2-Twin-Tuner PCIe@Samsung SyncMaster T240HD (PC)
Internet: Unitymedia 1play 100 / Cisco EPC3212 + Linksys WRT1900ACS + Fritz!Box 7390 / IPv4 (UM) + IPv6 (HE)