Guest Metztli Posted March 29, 2015 Report Posted March 29, 2015 Has this happened to anyone else? The time problem had become a rare thing for me but it's been all over the place today so far.
Guest pudpoh Posted March 29, 2015 Report Posted March 29, 2015 No issues here, only ever saw the time problem once, months ago, rebooted and it hasn't done it again.
Guest neson Posted March 31, 2015 Report Posted March 31, 2015 Yes, the BST change has completely tumbled the clock on our Hudl2. Even manually setting the time is pointless, as it drifts erratically. Worryingly the non-charging issue also recurred on Sunday for the first time since the big update...
Guest Metztli Posted March 31, 2015 Report Posted March 31, 2015 Mine has settled again after a drain to 0 and a couple of reboots.
Guest Posted April 7, 2015 Report Posted April 7, 2015 ....... back on topic ....... BST change not been an issue from my experience. My hudl2 is set to obtain it's time from my local NTP server (just an extra function added to a debian file server). The only 'odd' time issue I've occasionally observed over time has only ever been at power on - once booted up, on the initial lock screen, the time can be presented for a split couple of seconds as '12:00' until the wireless network connects and is then automatically corrected to the correct time i.e. it's queried the NTP time server on my network - this I've proved through network sniffing and packet capture on the debian server network port. ;) I don't know enough about the internal circuity of the unit to understand if this is an occasional issue or a feature. :ninja:
Guest mhardyman Posted April 13, 2015 Report Posted April 13, 2015 My clock is all over the place, totally inaccurate. (Rooted) I've been using Clocksync to keep it roughly in order. Didn't notice if BST was the trigger but noticed around that time. Have had no success with reboots etc.
Guest crusader58 Posted April 13, 2015 Report Posted April 13, 2015 (edited) I've not had clock issues since changing to a UK server in the gps.conf file which can be found within the system\etc folder. here are the settings I use:- NTP_SERVER=uk.pool.ntp.org XTRA_SERVER_1=http://xtra1.gpsonextra.net/xtra.bin XTRA_SERVER_2=http://xtra2.gpsonextra.net/xtra.bin XTRA_SERVER_3=http://xtra3.gpsonextra.net/xtra.bin SUPL_HOST=supl.google.com SUPL_PORT=7276 backup your gps.conf to a safe location and then replace the current entries with those given above then reboot EDIT: the link formatting in the text above should be plain text, I can't prevent it from displaying as a link rather than plain text. Edited April 13, 2015 by crusader58
Guest mhardyman Posted April 13, 2015 Report Posted April 13, 2015 (edited) Thanks for the info, went via a cut and paste into a google doc to remove link formatting. Not sure how necessary, but didn't fancy risking it. Will post back results in a few days. ******* 2Days later All working perfectly, many thanks for the tip. Edited April 15, 2015 by mhardyman
Guest crusader58 Posted April 26, 2015 Report Posted April 26, 2015 For those of you who don't wish to manually edit your gps.conf file but are rooted there is an app on the Play Store that will do it for you, plus it backs up your original file. it's called topNTP, there are various settings you can choose from till you find the best one for you...it also optimises the file so that you get a faster GPS fix (for those of you that use GPS.)
Guest mhardyman Posted May 8, 2015 Report Posted May 8, 2015 Sadly seems to have gone wrong. Seems to be losing time. Might have a go with topNTP. Don't really want to do a factory rest. Only thing I have done recently is freeze hudl updates and install kodi. (xmbc)
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now