I have been on a couple of other forum sites & have not found a solution yet. I am sure that others must have had this happen. I have to travel a lot for work & do travel between time zones often. The clock on my 8525 will automatically update to the new time zone. However, when this happens it also updates all of my calander appointments to that time too. I have almost missed flights because of this.
I think microsoft really dropped the ball on this one. Most business travelers do travel between times zones. Outlook does not have an option that a particular appoint will occur in a different time zone. I would rather the calander not update when the clock updates. Does anyone know of a way to fix this?
I rarely travel between timezones, so I just time shift various appointments. Plus it makes people that I share my google calendar with know what time an appointment is in their timezone properly
edit: Pocket Informant 8 allows you to specify a timezone, I believe.
jadesse said:
I have been on a couple of other forum sites & have not found a solution yet. I am sure that others must have had this happen. I have to travel a lot for work & do travel between time zones often. The clock on my 8525 will automatically update to the new time zone. However, when this happens it also updates all of my calander appointments to that time too. I have almost missed flights because of this.
I think microsoft really dropped the ball on this one. Most business travelers do travel between times zones. Outlook does not have an option that a particular appoint will occur in a different time zone. I would rather the calander not update when the clock updates. Does anyone know of a way to fix this?
Click to expand...
Click to collapse
You should always enter your calendar entries using the time in your current timezone. So if, say, you live in New York and leave for Los Angeles at 1:00pm New York Time, you enter it as 1:00pm. While you are still in New York you enter your return flight for 7:00pm Los Angeles time, you would enter it as 10:00pm.
Then when you arrive in Los Angeles and your phone jumps back 3 hours to the Pacific Time Zone, your flight will have changed to 7:00pm, the correct time. This way why you are still in New York and tell your wife you will call her before your flight out of LA at 10:00pm, she will be expecting it at 10:00pm her time. If you enter the entry as 7:00pm while in New York then when you look at the appointment you have to think where you might be at that time, instead of where you are now, to know the correct time. I know a flight time isn't so bad because you know where you should be to catch the flight. But say you want to remember to call your daughter before she goes to bed at 8:00pm NY time. If you enter it as 8:00pm in NY and it stays at 8:00pm while your in LA it will be 11:00pm when you call her, oops.
I know I made this more complicated than I should have, but hopefully you could follow my rant. I think you should want your phone to tell you the appointment time at where you are now, and let you figure what the time will be where you might be then, because you might not end up being there when the time comes.
Upon further examination, PI8 only time shifts your entry. Say if you wanted to create "Appointment" at 10AM EDT, and you are in PDT. It will create "Appointment {US Eastern 10:00AM}" at 7AM PDT. I'm sure there's a different mess of issues when you shift to PST, but we won't have to worry about that until later
Related
I just had the rather annoying experience of noticing my G1's clock was a full 5 minutes slow this morning trying to catch my commute light rail train. I was wondering why in blazes the trains were either so late, or so early...until I dialed into the NIST's atomic clock / Radio WWV line (303-499-7111 if you're curious) and got a rude awakening. The trains were on time, _I wasn't_.
Having had a CDMA cellphone of some sort for the last 8 years, I rather expected the phone to keep a reasonable sync to GMT time..(CDMA itself is based off of GPS for synchronization and GPS time is based off of the atomic clocks; every CDMA phone i've owned has been within a second of my ntpd running computer)
This said, I rebooted for the first time in about 4 days and it pulled network time from the towers. I'm reasonably synced now. However, if the clock drift is -5 minutes in 4 days without some provision of re-syncing or keeping time up to date at all times, with a stable enough operating system to not force reboots every day, I need something else.
Has anyone compiled an ntp application for the G1? Either a daemon ntpd or some sort of ntp-client scheduled via a timer/cron or the like would work for me.
Alternatively, is there a way to make the phone re-sync with network time? It seems to do it only once at bootup, never again.
Know this might be obvious, but do you have your clock set to Automatic under settings-->date & time?
I have never had a problem with time on my phone
This has happened to me too but its has gotten as bad as +/- 20 min. It is usually fixed by rebooting or pulling the battery. This has happened with Tmobile's RC30 firmware, JF's 1.42 RC33, and JFMOD 1.42 RC 33 (install apps to sd card).
Here's the sad part, I also have had a drift of upto about 30min slow, I've rand JF since RC30 was downgraded, and I'm now using HARDSPL w/JF ADP1.1h, and unlocked on AT&T. Mines been doing this for about a few weeks. I got so tired of it, that I just set it to my watch witch is realatively close to the internet time servers windows syncs with. Nothing has worked as of yet, I've rebooted, reflashed, wiped, and also asked for AT&T service books, no success.
This morning, I had set the G1 alarm and the alarm on my radio controlled alarm clock at the same time - They fired at exactly the same millisecond! I've never got out of bed that fast. And yes, I've set the G1 to Automatic.
/Mats
not sure if its already implemented or someone has already made it, but would there be a way of adding a google now command like "am i late for work?" or "am i going to be late for my doctors appointment?"
Using the command would search your calendar for what time you start work or have an appointment, then use google maps to find out how long it is going to take you to get there from your current position before determining if you're going to be late or not.
What do you think?
just seen a flaw in this as your phone wont know which mode of transport you're using.
You could add "in a car" or "on foot" to the end of your question.
What if your phone alerted you on your working days (assuming Mon-Fri, but also assignable) if you were "running" late. It would have to collect data to know how long it usually takes you to go get to work and the routes you take. It would also need to collect information about when you left and if you were hadn't left it would alert you that you were running late.
However I guess that most would know if they were running late and probably wouldn't need to be told...
Traffic
Not necessarily. If there was unusual traffic or an accident just happened I would want to know because it would change my commute time.
I.E. If It normally takes me 30 min but an accident on the freeway pushed it back to 45min to get to work I would want to know to leave 15 min earlier than normal.
Maybe Google has plans on adding this in the near future.
Sent from my SPH-D710 using xda premium
magick86 said:
What if your phone alerted you on your working days (assuming Mon-Fri, but also assignable) if you were "running" late. It would have to collect data to know how long it usually takes you to go get to work and the routes you take. It would also need to collect information about when you left and if you were hadn't left it would alert you that you were running late.
However I guess that most would know if they were running late and probably wouldn't need to be told...
Click to expand...
Click to collapse
regulusv7 said:
Not necessarily. If there was unusual traffic or an accident just happened I would want to know because it would change my commute time.
I.E. If It normally takes me 30 min but an accident on the freeway pushed it back to 45min to get to work I would want to know to leave 15 min earlier than normal.
Click to expand...
Click to collapse
Taking these both into consideration, google maps could also look for any traffic news and advise you on a quicker route (which I suppose could be useful for all occasions anyway). This way, I don't think it would need to collect data because it would know the quickest route regardless of how you get there. It would obviously be your choice to either follow the quicker route, or go your usual way and get stuck in traffic.
Hi,
I'm having problems with my HTC ONE S (Stock ROM / The newest OTA available) adapting to normal time (or winter time)... I live in EET time zone (GMT+2) and this morning at 4AM EEST (which is / was, well still is but is not used for ~6 months anywhere around the globe, GMT+3) the clocks were turned back one hour to 3AM EET.
My HTC One S insists on showin EEST, no matter what I do... I have tried to:
reboot it,
change to a city not in my timezone and then back (it does show the right time in the settings dialog to the wrong location, still the system time stays at GMT+3), and
disabling Googles location service (since I had a slight suspicion that the culprit might be there; the location service might be caching some wrong TZ information from EEST dates) and
re-installing location service and data
Combinations of all of the above.
The only thing that would help, is disabling automatic time setting from my GSM network and doing it manually - though I would like not to do just that to ensure my phone stays in the right time in the future! (I know the time provided by my carrier is right since my friend's phones did the transition without any problems!).
Also, I believe I was hit by this bug when I visited GMT+1 timezone in the summer... I thought the problem was with the carrier, but the behaviour is very similar now. There's some bugs with timezone changes and system time, they are not handled correctly...
The question is, does anyone else have problems with the transition - and, also, have you managed to find a workaround?
The next thing I would try, is to put all time settings to manual (time and time zone), disable all location service, change the city to another one not in my time zone, shut down the phone, take the battery away for 30min - and then revert everything. If that doesn't help, then I'm out of ideas - and even if it does, such trickery should not be needed!
Thanks!
It got automatically changed when I woke up!
Sent from my HTC One S using Tapatalk 2
Wrong section to post questions
Sent from my HTC VLE_U using xda app-developers app
Spastic909 said:
Wrong section to post questions
Sent from my HTC VLE_U using xda app-developers app
Click to expand...
Click to collapse
Ah, sorry about the section, you mean this should be in Q&A? I thought this would also have some discussion about a possible bug and walkarounds, so this would be a good section? I though Q&A is for the most common problems... but nevertheless I did think about where to post and it just wasn't clear for me, sorry
Mods, by all means move this if this is in the wrong section.
Thanks!
I was also in different timezones this summer and ive no problems
Maybe a provider related problem?
Sent from my HTC One S using xda premium
Wild Penguin said:
Hi,
I'm having problems with my HTC ONE S (Stock ROM / The newest OTA available) adapting to normal time (or winter time)... I live in EET time zone (GMT+2) and this morning at 4AM EEST (which is / was, well still is but is not used for ~6 months anywhere around the globe, GMT+3) the clocks were turned back one hour to 3AM EET.
Click to expand...
Click to collapse
I have the same issue in GMT+3 zone..
Hi,
I did a little bit more testing, and it seems that in my case the problem arises from the phone inventing this bogus timezone of "GMT+03.00, EET", that according to the phone, exists only in Finland. Of course, there's no such TZ, as EET is GMT+2, EEST is GMT+3, but the latter is not followed anywhere currently!.:laugh:. Changing the TZ manually seems to work around this, but I have also currently set my time to manual (just in case).
Hopefully there's some Android guru reading this: Is there a TZ cache somewhere - with perhaps some bogus TZ information about TZ's used around the world? If there is, is it possible to clear this cache?
I contacted HTC, maybe they can help :laugh:. Anyways I got a nice reply quite promptly. Well, at least now they know about the bug. This is a quote from my reply to them, more thorough about the problem:
I just tested this again. In the "Maailmankello" (i.e. "world clock" from now on, my phone is set to Finnish and I'm not 100% sure if that's what its called in English in the Sense UI), cities in Finland have their time shifted by +1 hours in relation to every other city in the world (according to this "world clock"). So, depending on the settings, either the time in Finland is +1 hour to what it should be (and other cities time is correct), or time in Finland is correct, but all other cities in the world have their time wrong by -1.
Maybe it is easier to explain with these few examples:
1) Time zone set to automatic, time set to automatic:
Time zone (grayed out but readable) shows as "GMT+03.00 EET" - which is wrong as there is no such timezone! EET is GMT+2, EEST is GMT+3, and EEST is not currently followed anywhere
The phone uses this bogus TZ for the main clock (which is +1 hours from real local time).
In the "World Clock": All other cities except those in Finland show the correct time.
2) Timezone set manually to correct( i.e. GMT+2, EET), time set manually to correct (or automatic, since just changing the TZ seems to set the time to my local time):
The main clock shows whatever I set it to show. Provided it's set correctly to the selected timezones time:
In the "World Clock": All cities in Finland show +1 hours to actual local time (i.e. GMT+3). Sometimes they show in GMT (i.e. -2 hours to local time)! Not sure when or why. Never correct time (GMT+2, EET).
In the "World Clock": All other cities (well, those I tested) in the world show the correct time (even those in the same TZ but not in Finland, like Tallinn. In addition I tested at least Stockholm and London).
3) Time zone set to automatic, time set manually to correct local time:
Time zone (grayed out but readable) shows as "GMT+03.00 EET" (as in case 1))
I can set the time to my local time, but if I do this...
In the "World Clock": All other cities in the "world clock" show their time -1 hour from their correct time.
So it seeems that "real time" or "GMT time" is correctly set, but the problem is with this nonsense TZ of "GMT+3, EET", that the phone thinks exists in Finland only. I get this problem even if I set the phone to _not_ use service providers timezone information, so it must be a problem with the phone?
Click to expand...
Click to collapse
I'm on a boat.
No WiFi. No Admin password for reverse tethering. No mobile phone signal for a backup code. I have internet through this shared computer.
I have the Authenticator app installed. The time on the computer matches GMT+1, the same time as "The time brussels" in google search and this matches the time on the phone. As does the timezone. But only to the minute.
Yet the codes aren't working. What can I do? How do I display what the time is on the Google servers to the second? How do I display what the time on the phone is to the second?
It would be great to be able to use the Google support forum for this. Well... XDA is often better anyway.
Nobody knows what the time on the google servers are? Really?
Bit naughty to reply to my own thread but I had the problem again, searched to remind myself how to fix it and this thread came up in one of the first search results. So I want to help anyone who has this problem.
The trick is timezones. The timezone in your phone has to be 100% accurate. To find that you might need to do a bit of Googling since some countries change zones in the summer or may not be the obvious. Then set your time to within 1 minute of what the time is supposed to be in that zone according to a google search. Fortunately within there's a bit of give so if you can't find a per second result you might be OK.
This way it doesn't matter which NTP server Google Auth is using.
In short,
Google Authenticator is using the time your phone is set to. If you have used the sync over the network feature that will take over so to go back to manual you have to change the time. That is a bit opaque. Also another point of failure is when you go to a new country with auto time from network provider set... and the network provider gives you the wrong time! This happened to me in Morroco. It also happened in the UK when I picked up a signal ~80miles away in France, so that my alarm went off an hour late.
I hope this helps people out there. As you can see, just setting the time is not as straightforward as it sounds.
This is all related to daylight saving time. I live in Egypt and we haven't used DST since 2011. It has been used again since the 16th of May 2014.
I've tried setting my phone to automatically retrieve time from my network (I'm on Vodafone). It is always off by 1 hour, meaning it's the old time (before the DST).
My whole phone is acting strange. Some apps behave incorrectly, for example Facebook: Any comment/post posted at this moment, shows "1 hour ago". Even WhatsApp, I've sent a message to someone and they responded 1 hour earlier..
My stock Samsung weather widget shows a DST icon next to the clock and adds an additional hour to my original time whatever I do to change it, and I've even set the widget to use my current GPS location.
Same goes for Google Now (soccer games times).
I've got a couple of questions: 1. Could the network problem be caused by my phone? Because logically all networks in Egypt should have updated this.
2. What should I do at the moment about Facebook and other apps? That's supposedly something that has to do with their servers. Anyway I can contact them about this?