[Q] Time server thrown off by router? - Nexus 4 Q&A, Help & Troubleshooting

Hi everyone and thanks for this great site, I learned so many things here.
I stumbled across a curious issue: when I received my new Nexus 4 yesterday the time was set wrong, about 33 minutes ahead. No problem I thought, unchecked and checked "automatic time", but it stayed incorrect. I punched in the correct time manually, set it to automatic again, and it "corrected" to the wrong time again. Since I wanted to install PA anyway I did exactly that, restoring factory settings in the process, and the problem persisted.
Starting to wonder I found this a (can't post links yet) very long thread on Google's product forums, tried several of the suggested fixes to no avail and concluded (as some people there have) there must be a hardware problem. Still I didn't want to send in my shiny new toy and installed ClockSync, hoping to work around the issue. To my utter surprise, even this utility displayed the wrong time. I changed the default NTP server for Apple's and still the same result: An NTP fetching app told me a clearly incorrect time, about 33 minutes ahead. Now I really didn't know what to think anymore: how could the hardware affect the NTP results. (btw going to any "time" website proved that NTP and Android's sync where wrong).
It was late and I had classes early today, so I took it with me to university. There I connected to the WiFi, re-enabled automatic clock and got set 33 minutes ahead, just as I had expected. I still wanted to try ClockSync again, and, lo and behold, now the NTP server gave me the correct time. Having read that rebooting fixed things for people with clocks slowly running late I did just that, re-enabled auto-time - and it got set correctly.
Now I was suspecting my network at the student residence to be the culprit. When I came back I started ClockSync and, like I expected, it showed the incorrect time again. The minute-part of the wrong time seems to correspond to the minutes in the log of my AirportExpress WiFi Base station that I use here to use my wired network with multiple devices. I tried to set it to fetch NTP itself, but that doesn't seem to work (presumably because it only does at startup, before my credentials are punched in at any client device which "enables" web access for my assigned IP.) So, no way for me to test my whole theory, still the fact that it's ok at uni makes me think so. There is no difference between setting the Base station to NAT or bridge mode.
What I don't get at all though:
Why would the wrong time in my router affect NTP results?
Why doesn't it for my Notebook or my HTC Legend? (that's the reason I thought I'd post this in the Nexus 4 subforum)
Why does it only set to the wrong minute, but always less than an hour ahead of actual time, on the right date no less?
tl;dr: In my private WiFi with the router set to the wrong time my Nexus 4 gets set to the wrong time automatically and also gets incorrect, corresponding NTP results in ClockSync.
Any ideas? A solution would be nice, but at the moment I'd be happy with an attempt at an explanation, because to me this doesn't make any sense at all.

some further tests:
it does not seem to be my router. I tried resetting it at a "full hour" in order to get correct sync, that didn't change a thing: android's auto-sync as well as Clocksync still think it's 33 minutes in the future. Maybe it's the router of the residence, I have no clue.
Also, deactivating wifi and activating mobile data, rebooting afterwards doesn't change a thing neither: what's strange about that is that afterwards even ClockSync still reports the wrong time, confirming that it get's NTP data. I'm at the end of my wits really.
Furthermore I installed ClockSync on my HTC Legend, and also there it does report the wrong time. It doesn't, however, change to the wrong time in android's auto.sync.
Now I got another idea: I unchecked auto-time on my Notebook, changed the time and re-set auto: the result was: nothing! The notebook doesn't seem to reach the timeserver (time.euro.apple.com), it does not report any error however (I'm not sure if it's supposed to), contrary to the android devices it will not take the wrong time however... stranger and stranger.
Please somebody, do you have any idea what's going on here?
Will I be stuck with manual time which is known to get very imprecise over short periods...?
EDIT:: as I expected, Port 123 is closed in the network of my residence. That still doesn't explain why android AND ClockSync would just report the wrong time instead of telling me that the timeserver could not be reached...
thanks!

just a question:
does your silence indicate that you have no clue either or am I missing something obvious here?
please somebody answer just to tell me that I am not going mad!
(also, if someone would be willing to investigate this with me, could you try to close Port 123 on your router and tell me how your device reacts regarding auto-time and ClockSync. Thanks!)

Does ClockSync show the correct NTP server details if you long tap of the atomic time?
It looks like your router is intercepting NTP requests and is handling them itself.
Does it help if you specify IP address of the correctly working NTP server instead of pool.ntp.org in ClockSync settings?

left ingrizidu
Thank you very much for trying to help me!
CrazyCoder said:
Does ClockSync show the correct NTP server details if you long tap of the atomic time?
Click to expand...
Click to collapse
I think not. No matter which server is specified, the output looks alway like the attached screenshot - with 73.78.73.84 in the reference ID field. Calling that url from a browser gives me "Le site que vous souhaitez interroger est actuellement indisponible." - The site you're trying to reach is unavailable at the moment.
Also notice file name and creation date of that screenshot file.
The file name corresponds to actual time, supposedly because I have set my time to manual.
The creation date is 3/29/2010. Why is that now...?
CrazyCoder said:
It looks like your router is intercepting NTP requests and is handling them itself.
Does it help if you specify IP address of the correctly working NTP server instead of pool.ntp.org in ClockSync settings?
Click to expand...
Click to collapse
it's not, sadly, still the same output and wrong time.
Thanks!

Do you mean that even if you specify a different IP address for the NTP server, ClockSync still shows 73.78.73.84 address?
If it's the case, then something in your network hijacks all the NTP requests and redirects them to 73.78.73.84 server which provides incorrect time.
You should talk to the network administrator.

sorry for getting back to you only now, the internet in the residence just went completely away yesterday.
now it's back, painfully slow at times but it works and
TADA
auto-time works, clocksync shows the right time (as well as the right IP, the answer to your question was yes the day before yesterday)
even my notebook can reach it's time server.
thank you very much for your help, if it happens again I shall talk to the network admin here.
aside.:I'm still not sure if it's expected behaviour, certainly not best practice, of ANdroid to be derailed that way. OSX isnt.

Related

VPN driving me crazy...

OK, I don't knkow what else to try here, hence the post!
I'm trying to get my XDA exec (Universal?) to connect to my work VPN. I've entered all the details exactly the same as they are on my laptop (which works) and yet when I try to connect, I get an error message saying "VPN Server problems. Verify your username and password, and try again. If the problem persists, turn the device off and try again." This message appears instantly, as though it is not even trying, and my GPRS connection terminates, without an error message, without a warning. What I think is happening is that as soon as I ask to activate the VPN, it disconnects the GPRS, and then the VPN won't work because of that. Which seems rather stupid.
I've tried rebooting, I've tried changing every setting in the VPN connection, I've tested the GPRS connection by visiting websites, I don't know what I can possibly be missing. Any advice would be greatly appreciated.
This has absolutely killed my faith in this device. It stops synchronising my mail at least once a day, without warning, it has crashed in the past, destroying mails I was writing at the time, and I find it generally unreliable, unfriendly and considerably less useful than a BlackBerry. Sorry, but I had to say that, I'm tearing my hair out here...
im not sure if you can do VPN over GPRS you may require a wifi connection for that.
Hello faethor, fancy meeting you here!
I know on the XDA IIs it worked over GPRS, so it would surprise me if it didn't on the Exec, but perhaps you're right...
I don't care any more, fed up with the damn thing for today...
This is possible, but there are various possible problems.
It could be something as basic as you need to add your company web-site in the 'exceptions' list (Start, Setting. Connection (tab), Connections (icon) advanced, exceptions). e.g *.companyname.co.uk.
It is worth checking with your IT people if certain IP address ranges are also blocked (e.g. for extra security).
Network tech support are quite rubbish on this, and it took me, my former MD and our IT company several hours to get it sorted last time we tried this!!
The queston is do you need VPN for document view / transfer or is it just for email / contacts on the move (you mentioned Blackberry)?
If your company has MS exchange 2003 the exec sync's straight in using yout outlook web access settings (a tick box also needs to be enabled in the server) or you could use something like www.seven.com which I have had both personally and corporate which works brilliantly.
If it is full VPN you need, I can provide documentation or contact numbers which may help.
It may be that your VPN connection needs to be the GPRS settings (and using the APN vpn.o2.co.uk (you said you were using an XDA which is an o2 branded HTC device) and your conx to your server via proxy is your home server details?

Need someone familiar with services running on the android kernel (cm6 specifically)

So I'm a network admin. I use strong passwords, alphas, numerics, etc.. keep a tight lid on what i install. AVs, spyware scans, etc.. no crap gets on my systems. Its been quite a number of years since I've had to clean out any of my systems.
Moving on...
My boss hands me a mini today from one of her family members - supposedly it has a bug and they didn't want to pay the geeksquad people.
Hearing that it has a bug, I didn't want to put it on the work network so I decided to hook it up to the wifi tether on my phone and download malware bytes via that. I figured - no windows bug is getting on my linux phone. I didn't think about any network-based attacks.
Few hours later, I turn my tether off and go to lunch when I visit my chiro twice a week. I'm laying down getting my back all jazzed up when my phone pops up with a "sign-in" error to my gmail. The password that I knew to be true didn't work. I hop on the bike and rush back to work.
I find all my googles signed out. I attempt to sign back in and get prompted with "suspicious activity detected, please verify". I did so through SMS and was prompted for my OLD password - which worked to my surprise (hacking 101: when you get in, first thing you do is change the pass). I was then prompted to change the pass which I did. I logged in to my gmail and saw a mobile login from an IP in peru. I also found quite a number of NDRs in my inbox (20 or so) with just a URL in it - so it was compromised for spam purposes.
Doing scans on all my systems, no sniffers or keyloggers running. They never had a chance to but just in case, i ran the scans anyway. My only thought is that mini connected to the net through my phone.
I'm thinking that since the phone presents itself as a wireless router and hands out DHCP, whatever local IP the phone sets itself to becomes the default gateway for the mini. If that mini is truly infected (at the moment, I'm not finding anything on it), and it does a network scan type of thing - could it have picked up some SMTP port that our android kernel keeps open? At that point, it wouldn't need my password (which would make sense that my old password worked). I didn't give it much thought at the time but I did think that a few hundred MBs of download was kinda high while the tether was connected.
So thats my question to anyone familiar with the kernel - network wise, are there any open, unsecured (smtp is unsecure in its nature..) services ran by the kernel? Once the phone goes into router mode and gives itself a local ipv4 address and a node (in this case the mini) hops onto the same subnet - those services would be readily accessible to that node.
IE: this bug scanned for port 25 or something.

Galaxy Static IP Setup

OK, I've been messing around with this for the past 2 hours and nothing.
At my work, I have a static IP setup (I'm the one that manages all that and sets up each computer, etc.)
I also have a COBY MID7015 and I was able to set-up and use the tab successfully.
I brought in the Galaxy Tab to work (I used it last night at home Dynamic IP with no problems) and tried to set it up. I inputed all the static IP settings and when I click "Connect" it starts scanning and briefly flashes "Obtaining IP address, then "Disconnects" and continues Scanning.
I've gone over it a dozen times and everything is entered correctly. Any help would be appreciated!
OK, I've just done a Factory Reset and still nothing
Probably, the static address youve set up is already reserved.
Yeah I wish it was that simple: I've gone through a number of IP's (ones that I know are definitely not in use), and still nothing. I've attempted again to connect my laptop and it worked flawlessly.
I don't know what else to try...
OK I feel like a complete idiot!
The Gateway and Subnet Mask when reading it off the computer is in a different order on the Tablet.
WOW! ... well hopefully this will help out someone going through the same thing
I'll give you a thanks, because that one must have been hard to admit
Oh yeah...I'm crossing my name off of the IT Department: well when you always have to do stuff in a hurry, you miss some stupid stuff like that

[Q] New S5 not automatically connecting to WiFi

Hello everyone,
Last week I upgraded my S4 to a brand new S5 on T-Mobile and currently it's stock and unrooted. It works great, except it won't automatically connect to WiFi. Every time I encounter a known WiFi it'll say Sign in Required. I'll press Connect and it'll then connect and function perfectly.
This smells like a software bug to me, but then I'd expect more posts on this topic (I didn't see any posts on XDA, and posts elsewhere were unhelpful).
What I'd ultimately like to know is if this is a hardware defect and I should get my phone replaced before it's too late, or if this is something that a software update (or rooting and flashing) will fix. Or of course it could be neither...
Thanks!
I have the same probblem and I am dying for a solution. I've spent hours googling and testing different things to no avail.
I am going to try to bring as much detail as I can, hopefully someone can pitch in.
Things I have read might work:
"forgetting" the connection and recreating it
Turning off and turning back on
Turning off, removing the battery
Turning off, removing the battery and the sim and waiting a minute (seems like voodoo to me)
Factory reset
I've tried everything, bar the factory reset which I am reluctant to do, specially when people's answers on forums said it wasn't a solution.
To try and shed more light, I would also add that:
It does this with any network (so it's not channel/router issue)
It does this consistently (and since I got my phone)
It finds networks, but just won't connect
It always connects fine if I pick the network (so it's not a distance/bad reception issue)
My phone is unrooted and stock and I have no weird apps (only popular/regular ones, social media, news, and so on)
My options are set correctly (notifications for open networks is checked and wifi is on)
I really hope someone can help as I rely on wifi a lot, and this is kind of a deal-breaker for me.
So I found a psuedo-fix here: http://forum.xda-developers.com/showthread.php?t=2723486
The key part being:
1. >Wifi >Advanced >Disable (uncheck) Smart network switch.
2. Forget connection, then establish connection again. Works no issues.
Click to expand...
Click to collapse
This has "fixed" it for me, but it also means I no longer have Smart Network Switch which is kinda annoying, albeit less annoying.
A true solution would be lovely.
ForestHunter said:
So I found a psuedo-fix here: http://forum.xda-developers.com/showthread.php?t=2723486...
Click to expand...
Click to collapse
Tried, didn't work for me.
I now have factory reset and let google reinstall all my apps.
Until now, auto-connect works.
The only thing I didn't do this time that I did last time is deactivate a bunch of samsung apps that come pre-installed.
wi-fi won't auto connect to S5
ForestHunter said:
Hello everyone,
Last week I upgraded my S4 to a brand new S5 on T-Mobile and currently it's stock and unrooted. It works great, except it won't automatically connect to WiFi. Every time I encounter a known WiFi it'll say Sign in Required. I'll press Connect and it'll then connect and function perfectly.
This smells like a software bug to me, but then I'd expect more posts on this topic (I didn't see any posts on XDA, and posts elsewhere were unhelpful).
What I'd ultimately like to know is if this is a hardware defect and I should get my phone replaced before it's too late, or if this is something that a software update (or rooting and flashing) will fix. Or of course it could be neither...
Thanks!
Click to expand...
Click to collapse
I have been having the same issue. I can't get any answers either. It really is frustrating. I am going to keep trying to find out. When I called the T-Mobile store they said that I could bring it back w/in the 14 days & replace it and I may do that if I can't get an answer for the problem! If you happen to find out what the answer is PLEASE post and let us know! Thanks
My wife has the same issue with not auto connecting. She has a AT&T S5 that is not rooted....thanks to AT&T putting her in prison lockdown. I think it could be something with the last update because her phone used to auto connect just fine and now it doesn't. The strange thing is that she just now noticed it not connecting and she had took an update that was a few weeks ago or whenever it actually was and now we don't really know for sure if it's really just now an issue or has been since the update....imo I think it could be something with the update.
I have an S5 as well with no issues, but then again, I have the TMO that's rooted and carrier unlocked running custom rom.....thanks TMO for not being D***'s like at&t
Solution!
Long story short, there's a problem with Android and DHCP. Specifically, an IP associated with a router doesn't die when it should and attempting another connection goes back to this IP instead of using the correct (new) IP.
The good news is to forget the problematic wifi connection, head into /data/misc/dhcp/ and remove the files, reboot then connect to wifi. That flushes the DHCP lease information and life should be good.
omarriachi said:
Long story short, there's a problem with Android and DHCP. Specifically, an IP associated with a router doesn't die when it should and attempting another connection goes back to this IP instead of using the correct (new) IP.
The good news is to forget the problematic wifi connection, head into /data/misc/dhcp/ and remove the files, reboot then connect to wifi. That flushes the DHCP lease information and life should be good.
Click to expand...
Click to collapse
I seem to be having this problem now, however I tried doing what you suggested and I don't have the path you mentioned, how do you get to it?
cgdart said:
I seem to be having this problem now, however I tried doing what you suggested and I don't have the path you mentioned, how do you get to it?
Click to expand...
Click to collapse
use a program like "root explorer" or "ES file explorer" and navigate to your root folder ( / )
then follow the path /data/misc/dhcp/ , you will find the files i mentioned there.
omarriachi said:
Long story short, there's a problem with Android and DHCP. Specifically, an IP associated with a router doesn't die when it should and attempting another connection goes back to this IP instead of using the correct (new) IP.
The good news is to forget the problematic wifi connection, head into /data/misc/dhcp/ and remove the files, reboot then connect to wifi. That flushes the DHCP lease information and life should be good.
Click to expand...
Click to collapse
Im reviving this thread, I have this issue also. And with my "unlimited" tmobile bandwidth of 2gb, this bug is completely screwing me over.
I quoted this post since you just claim its Android and DHCP, if thats the case, wouldnt all android phones just not work like the S5?
omarriachi said:
Long story short, there's a problem with Android and DHCP. Specifically, an IP associated with a router doesn't die when it should and attempting another connection goes back to this IP instead of using the correct (new) IP.
The good news is to forget the problematic wifi connection, head into /data/misc/dhcp/ and remove the files, reboot then connect to wifi. That flushes the DHCP lease information and life should be good.
Click to expand...
Click to collapse
Finally..it's work for me..tqvm
Hey I'm having the same issue, only with my work open wifi. The phone will be aware there is a wifi and it tells me to sign in. I go to the wifi settings and tell it to connect it does, but if it drops for any reason it won't automatically connect again, I have to go through the same thing every time.
I read this in a previous post:
"use a program like "root explorer" or "ES file explorer" and navigate to your root folder ( / )
then follow the path /data/misc/dhcp/ , you will find the files i mentioned there."
I have X-plore and went to the root/data folder, but there was nothing in the data folder - Do you have to be rooted for this to work?
Any help would be appreciated.
Samsung Galaxy S5 - Koodo - Unrooted
solved mine by follow this guide
http://forum.xda-developers.com/showthread.php?t=2547356
Sent from my SM-N9005 using Tapatalk
It works fine on my home network and others that I have a username and password for. The issue is WIFI hotspots at coffee shops and work and such, where I don't have access to the router settings.
I have an app that does an auto login when it recognizes that you need to sign in once it connects to wifi, and it works when I tell the phone to connect, but the phone will never connect automatically - I have to go into the WIFI settings and tell it to connect manually every time.
I have the 'Smart Network Switch" unchecked, and I have 'forgotten' and reconnected several times but it still happens.
Samsung Galaxy S5 (SM-G900W8)- Koodo - Unrooted
omarriachi said:
Long story short, there's a problem with Android and DHCP. Specifically, an IP associated with a router doesn't die when it should and attempting another connection goes back to this IP instead of using the correct (new) IP.
The good news is to forget the problematic wifi connection, head into /data/misc/dhcp/ and remove the files, reboot then connect to wifi. That flushes the DHCP lease information and life should be good.
Click to expand...
Click to collapse
Thanks. This solved my problem ?
I had a corrupt .keystore on my S5 and the fix I found by googling was to do a reset of the device.

Captive Portal issue with Pixel 6P

I haven't been able to get anywhere with this issue I've been having for a few weeks, so I figured I'd fire up my old xda account and see if anyone on here can help since this is a more techy crowd. I've searched and searched but I haven't found anything similar unfortunately.
Tl;dr I have to log in to my work's guest wifi every day, but I didn't before. Nobody else does. Auto connect is set to on, but it doesn't work like it used to/is supposed to.
Longer: I connect to a guest network at work every day that's meant for employee personal devices. (I use a homebrew VPN for this.) Before the issue started, I'd periodically (maybe once/month if that) have a notification when I arrived to sign in, and you click agree in a captive portal and you're on your way. Other than that it auto connects just like at home. A few weeks (?) ago however, I've started having to do this every day. If I'm disconnected for over roughly an hour (say if I leave and come back during the day) I have to do it again, and if I reboot my device I also have to sign in again. If I just toggle wifi on and off quickly then it automatically connects just fine.
Ordinarily this wouldn't be a huge deal, but where I work I basically get no cell coverage. I also have a couple tasker profiles that I've been using for years to do stuff (vibrate mode, silence media, etc) when I arrive to work, and these don't/won't trigger until I have a minute to log in. Ideally these would trigger as soon as I'm within range of the building, as I've been doing for years now.
None of my coworkers have this issue, everyone that I've asked all say their devices automatically connect just fine, as mine used to.
I'm assuming this is something related to my device. Because it happens if I reboot, but not if I quickly disconnect and reconnect, I'm imagining maybe something isn't being cached correctly?
If anyone can help me fix this I'd be very grateful!
Solved: dev setting for non-persistent Mac address randomization was on.

Categories

Resources