What is Reddit's opinion of ClockSync?

From 3.5 billion Reddit comments

Error 33 can be fixed with an app like ClockSync - just check once a day before a raid your phone's time sync accuracy against atomic time source with this app - if it differs more than 3 secs then error 33 is nearly guaranteed.

Be sure to change settings in ClockSync to rootless mode.

ClockSync: https://play.google.com/store/apps/details?id=ru.org.amip.ClockSync

Since you are on Android, you should download an app called ClockSync and use it to calibrate your clock. If your phone isn't rooted (I have the same problem as you and mine isn't), the app has an unrooted mode that works just fine and only requires a bit of patience and reflexes.

I will take this opportunity to say that in Brazil a lot (and I do mean a lot) of players have the exact same issue. One of our biggest mobile carriers (Claro) has their date and time wrong by 24 seconds and I would guess that anywhere from 15 to 30% of the Brazilian player base uses Claro. The problem is that this sync issue mostly affects casuals (since hardcores have access to groups/reddit and can usually figure a workaround) and they are ultimately giving up raids because of the timer being synchronised the way it is.

I would rather not bother George and Indigo, nonetheless I will tag /u/NianticIndigo here to see if we can get an answer on whether this is a known issue and, if it is, whether there is an incoming fix to it.

Given the opportunity again, if this is not a bug and is not to change, I would humbly propose to Niantic to make an official statement commenting on this, explaining that, for most cases, auto date and time will do the job, but for the lot that this solution doesn't work, they have another solution (that’s up to Niantic).

edit: I wrote this 2 hours ago, but it didn't post due to connection issues ¬¬

Can you go to https://time.is and check your offset? It should normally be within 0.5s. If it's more, then it's probably an issue with the timeserver on your device. In that case, you can use https://play.google.com/store/apps/details?id=ru.org.amip.ClockSync&hl=de to manually set the correct time.

Same here, no time loss to be seen. I got nervous though and installed ClockSync just in case. I can't afford to miss my morning alarm.

double check

go into your settings, date and time, and check if "Automatic date and time" and "Automatic time zone" are enabled

you may also want to check up on ClockSync to verify whether or not your time is set accurately

basically every time someone had issues with stuff like this, i told them to double check their time settings, which usually fixed it

I rely on my cell phone's clock. It is set from the carrier, and they track activity to a small fraction of a second.

If that is not enough, you can use "ClockSync". It can verify the setting to 1 thousands of a second.

Most newer cell towers self sync through GPS.

I think it's this

https://play.google.com/store/apps/details?id=ru.org.amip.ClockSync

It's been years since I used it so good luck

it needs root but like I said it has non root functions too

Depending of the mobile network it won't work. In this case, if it's an Android device, you can use Clock Sync to be sure it's synced.

If you are on Android download 'ClockSync' from the Play Store: https://play.google.com/store/apps/details?id=ru.org.amip.ClockSync

It helps you to check your time offset und set a new time manually with an overlay.

That happened to me (and a bunch of other Verizon users in Western WA) recently.

I turned off network time and timezone and set up ClockSync instead - requires root, but now I won't be fooled again.

Not a new app, but mentioned seldomly: ClockSync, which let's you sync your device clock via NTP. This is - at least with my provider - more exact than the network provided time.

Every phone I have seen gets the time either directly or indirectly from GPS, so all of them are 16 seconds fast. I have no idea why they don't just correct for that.

On my phone I turned off network time and use an app that sets the correct time.

It is actually much simpler - the plot is done manually, though I am pretty sure there are more automated methods of generating them.

I used ClockSync to always show the atomic time on my phone, and just manually noted down the offset and the time, every once in a while. Then I just plotted in Excel.

I do believe there are apps that take a photo using the phone camera, processes the clock hands, and then compares it to the timestamp on the photo. Those make life much easier, but the manual method is more accurate.

I don't think they can actually sync the time on the phone with their servers - clock synchronization apps need root access to do that ~ example: ClockSync.

I think the best they could do is try to calculate the offset and try to factor it in.

I suppose like always, it's a matter of how much risk one is willing to tolerate.

If the problem is the time being out-of-sync on their phones, on Android, there's an app called ClockSync. It will atomically sync your phone's clock and you can set the interval it does it too. (Auto sync requires root though.) I don't know what the iPhone equivalent is.

I realize the security key's battery will eventually die, so we'll all be forced to use alternative methods at some point.

There are apps such as Clock Sync which syncs with NIST for atomic time. It'll display how much time was adjusted, drift etc.

Before starting any raid, use ClockSync, or an equivalent iOS app, to make sure your phone's clock is as accurate as possible, preferably a bit behind. This happens when your clock is a few seconds fast and the game tries to start the raid too early.

I'm not saying this isn't Niantic's fault, because it definitely is. This has been a known issue for weeks and, as always, they have yet to even acknowledge the bug. But if you get another EX pass, or have this issue in a regular raid, that trick should help.

On Android, the ClockSync app helps you to change your phone time to the real (exact) time really easily.

This solved the issue for me months ago.

With the app https://play.google.com/store/apps/details?id=ru.org.amip.ClockSync you can actually see how much difference there is between your time and the correct atomic time.

-

The app is useless for setting time without root though. If you have root, it can set the time for you.

It is not a Kodi add-on, it is an app. Here is a link: https://play.google.com/store/apps/details?id=ru.org.amip.ClockSync&hl=en

I went there and selected Install and selected my Shield TV as the device. The app installed in the background. I then went to Settings > Apps and located ClockSync and ran it. I went through the options and selected any dealing with time (timezone, time offset, etc) and, once all options were selected, I synchronized the time. I then went into Kodi, and time was fixed. I rebooted, still good. I did select, in ClockSync options, to run every time at startup... Let me know if it works for you, as it worked great for me.

I also installed TimeZoneDB for SyncClock (https://play.google.com/store/apps/details?id=ru.org.amip.timezoneservice&hl=en). I have no clue if that helped or not, but I did install both.

On a rooted android phone one could use ClockSync to ensure one's time is regularly (e.g. every hour) synced with an atomic clock. Presumably the same could be said for an Android Wear watch.

It's a bit surprising that this sort of thing, apparently, isn't at least promoted (even if not mandated) for use by the guards.

Assuming you are not using any optimisation/task manager/network management app.

Everyday the phone slips a few seconds. Maybe you could try adjusting the clock time of your phone by using ClockSync or obtain the time from your network.

And you can test if the issue exists on WiFi or not.

If you would like to fix this on your rooted android, this can synchronize your clock with the atomic time.

My friend is using this app to fix the time: https://play.google.com/store/apps/details?id=ru.org.amip.ClockSync&hl=pt_BR

That's strange, mine doesn't require any roots. And if yours does, don't use it.

if your automatic time is wrong you need to set it manually.

Android: https://play.google.com/store/apps/details?id=ru.org.amip.ClockSync&hl=de

https://play.google.com/store/apps/details?id=ru.org.amip.ClockSync&hl=en This is what I use on devices that don't keep good time.

You could install clocksync on your phone and sync your phone regularly to an NTP time server.

Clocksync

https://play.google.com/store/apps/details?id=ru.org.amip.ClockSync

Clocksync should be able to sync your time every so often.

https://play.google.com/store/apps/details?id=ru.org.amip.ClockSync&hl=en

That is your new BFF. you can even set the sync on boot.
https://play.google.com/store/apps/details?id=ru.org.amip.ClockSync

I like this app:

https://play.google.com/store/apps/details?id=ru.org.amip.ClockSync