Does not sync with google servers
jyn514 opened this issue · comments
Referenced here. I have two devices, both using the same 2fa keys, but at any given time, they show different passwords. One, a Samsung S7 will sync with google servers and display the message "Time already correct". The other, a Samsung Note (Android version 4.4.2) gives the error "Sync now: There was a problem contacting Google's server. Please check your network settings and try again."
Both devices are connected to the same wifi network and both are using the latest version of the app. Any help is appreciated.
More info about the device not working:
Model number SM-T230NU
Android version 4.4.2
Kernel version 3.10.0-5332174
Build number KOT49H.T230NUOVU0AOG1
App version?
Version 4.74
I have the same issue on my Samsung Galaxy S3. I've tried rebooting the phone, and tried on WiFi and 4G with the same error.
Authenticator version: 5.0.0
Model number: SPH-L710
Android version: 4.4.2
Kernel version: 3.4.0-2851177
Build number: KOT49H.L710VPUDOH1
I have the same issue:
Authenticator version: 5.0.0
Android version: 4.4.4
@ThomasHabets Is this being worked on? This is a very serious issue since I can't use the app to get my codes
@camargo not that I know. Make sure you file feedback from within the app.
I have the same issue:
Authenticator version: 5.0.0
Android version: 7.1.2
same issue here. I noticed it stared the other day. I have searched and search for a fix, but have found none. Is there one?
i am too having the same problem... anyone here to help?
Standard disclaimer:
--
FYI: The version in Google Play Store / Apple App store is not the same as this opensource version. They've diverged. This opensource version is also unlikely to end up in the app stores. This open source version doesn't get much love, but I'll accept well-written pull requests. But don't expect this feature to be implemented by Google.
so @ThomasHabets what we have to do to sync servers seems no one can help people
You don't need to sync with the servers, you just need the time to be correct. There could be a whole bunch of reasons non-Pixel/Nexus phones may have gotten vendor crapware that broke time.
Play with your time settings, timezones, and stuff. Maybe something will work.
i see 100 posts about that problem u think no one should find the aproperiate solution in time settings?
in order to be more clear i install g.auth in a new phone
same problem i try to scan a code and not working
sorry but the word maybe is not right here we need a solution here
i know is not ur buisness but i hope someone fix that problem
@ThomasHabets its weird my other phone got sync problem too
my problem start when i remove battery seems something happen after that
This is hard to troubleshoot remotely. Maybe you can write a javascript thingy that prints the unix timestamp, and confirm that time is up to date. Or register a new second factor to see if that works.
as i tell you i install g .auth in new phone same problem occurs
any program to see timestamp or something
@ThomasHabets i see https://stackoverflow.com/questions/8077530/android-get-current-timestamp
can u tell me if i can run in terminal?
thanks for your time mate and really sorry
That's java, not javascript.
The way to get the timestamp in javascript is:
alert(new Date().getTime())
And compare it with a server with correct time by running:
date +%s
any clue how run javascript?
i cant run webview in 4.4.1
Create a webpage with the javascript, and browse to it with Chrome
i try js code run app
i get an errorreference error cant find variable date
You run date +%s on a unix server, not in JS.
mm ok
but i run alert(new Date().getTime()) in js and get syndax error but says unexpected token ...expected 1.21
so i guess that is time right?
let me sse about unix server
thanks again
I don't know where you're putting that alert(…), but it is valid js.
js code run app from playstore
the code error returns include time ?
what is 1,21?says expected
I have no idea.
date +%s
returns 10 digit number
@ThomasHabets hey anything to do with that number?
ok first command
give alert a 13 digit number
and date command a 10 digit number how to compare and how change
thanks agin for helping
If you run the two at the same time you should get the same number.
If they're off by one or two that's fine. It's number of seconds since 1970, and TOTP allows for some inaccuracy.
If you have ntpdate installed on the unix machine you can run ntpdate -q pool.ntp.org which should confirm if the clock is set correctly.
If unix machine time is set correctly, and differs "too much" from what you see on your phone, well then the time on your phone is wrong. Turn off or on automatic setting of time. Set it manually. Tweak. It's all very phone-dependent, but now you have a way to check if you are getting closer or further away from the right time.
When the time on the phone is right TOTP should work.
If time is right and it doesn't work, try re-adding some TOTP account. If it works, delete the ones that don't work and re-add them.
That's about all I can help you with.
ok first command
give alert a 13 digit number
and date command a 10 digit number how to compare and how change
thanks agin for helping
cant understand
as i say 2 numbers are different
alert:13 digit
date:10 digit
1528216271
1528216227704
Ah. Yeah ignore the last three digits in the longer number.
So 44 seconds difference. That's a bit much. Try to sync them better (and make sure the unix machine is actually correct)
there is no unix machine i install a terminal emulator to run date command
btw what differ is ok 2-3 secs?
i get 7 secs delay same problem
i dont think is possible to get identically numbers
terminal emulator… on the phone? Are you comparing the phone… with the phone?
yes, 7 seconds should be fine.
Try comparing your phone time to time.gov. Like Thomas said, comparing your browser to a different app on your phone will not give you any useful information.
mm yeah my fault comparing phone with phone
i need to run in my pc right?and compare the time with phone?
and yes terminal emulator in phone
time gov shows one hour ahead my pc clock
This is not working. You need to find someone to walk you through this is person.
@jyn514 can u please give me ur email if u solve the problem before?
@ThomasHabets
The way to get the timestamp in javascript is:
alert(new Date().getTime())
And compare it with a server with correct time by running:
date +%s that command must run in pc?
Yes
ok
1.install cygwin in my pc and run date +%s (1528301992)
2.alert(new Date().getTime()) in phone returns (1528301989)
same problem occurs
I actually no longer own the tablet that wasn't working, so I can't help one way or another.
@jyn514 if u resolve that problem before u can tell me how?
guys if uninstall the google auth and reinstall it i lose the tokens?
thanks
Try to reset time setting on phone. I just set the option to synchronize time with the network time and it helps for me.
I went to Date & Time settings and selected the 'Automatic date & time' option, which had been recently unchecked for some reason. This solved the issue for me
I had the same issue, somehow my phone's time got unsynced and set itself to GMT? (weird, one of life's little mysteries I guess), Correcting the time in the phone's settings fixed it. However, if the "Sync Now" button in the app is just going to be broken for what looks like more than a year, it should be removed and replaced with a message that says "Please check the time settings on your phone"
Closing due to no activity, and more of a support thing than a bug thing.