futeko.com FORUM

Product Support => HiMedia Q10 Pro, Q5 Pro => Topic started by: Mount81 on July 24, 2016, 06:45:22 AM

Title: Manually setted Date and Time will always be resetted on Q10 Pro
Post by: Mount81 on July 24, 2016, 06:45:22 AM
Hello!

If I set the Date and Time to manual, and set the correct values manually, it will be diplayed both in on the screen and on the LCD of the Q10 Pro, but only till next boot. If I power off the Box and power on again, after the boot the whole date and time settings are gone and resetted back to 1970 jan 1 (time setting also gone). I guess this must be some kind of bug, and it shouldn't forget the manually setted time and date after every  power off.  ??? Can you confirm it, and/or advice me a solution? (Other than set it to automatic, couse untill I don't have a router I rarely connect the Q10 Pro to the internet).

Thanks!
Title: Re: Manually setted Date and Time will always be resetted on Q10 Pro
Post by: stack on July 24, 2016, 08:14:30 AM
Confirm that HM box is returning back to the factory settled time and date after restart.
I mean date and time in manual mode.
Result:
January 1, 1970.
02:00h.
Title: Re: Manually setted Date and Time will always be resetted on Q10 Pro
Post by: pcristi on July 24, 2016, 12:23:42 PM
HiMedia not use/have internal clock, always try to sync from internet

FW HMD 1.0.1 / HMD 1.0.3
- default is January 1, 1970. 00:00
- default time zone Asia/Shanghai
- change to January 1, 2015. 00:00 (VFD disp 08 : 00 : 00)
- when Android is load apply GMT zone set in Android settings
- sync to internet when Ethernet ready

FW HMD 1.0.5
- default is January 1, 1970. 00:00
- default time zone Asia/Shanghai
- not change to January 1, 2015. 00:00 (VFD disp --  --  --)
- when Android is load apply GMT zone set in Android settings
- sync to internet when Ethernet ready
Title: Re: Manually setted Date and Time will always be resetted on Q10 Pro
Post by: Mount81 on July 24, 2016, 12:41:49 PM
HiMedia not use/have internal clock, always try to sync from internet

So it's not a bug at all? Thanks, thats at least reassuring!