In EU countries, British summer time ended last night and the clocks went back 1 hour. My phone shows the correct time and changed automatically. I use an app called Tasks https://play.google.com/store/apps/details?id=ch.teamtasks.tasks.paid that I have been using for a while is now, and it's now longer working correctly (and another similar app is doing the same). When I input a time for the task to alarm the time displayed goes back one hour, so for example I have a task that will sound at 6:15 am tomorrow, but the time that it will go off is 5:15 am. Any idea's why this is happening, I thought it might have been the app, but I have tried tow different ones. They both synchronise with Google. The only way to 'fix' it would be to set the time to remind me at 7:15 am.
My phone is rooted on stock rom.
Related
I recently went to another country and the time zone was 2 hours difference.
I had not updated the clock on the wm6 device because I was only away for 4 days.
Well all was well on day till day 2 when I was catching various trains and wondering why they were not on time e.t.c as in my head I was adding 2 hours the what the clock said.
Well low and behold It must have auto updated itself, because I am pretty sure it wasnt me!
the same happened when I got back to the UK.
has anyone else has this ?
Pretty cool though tbh did throw me off balance though that night.
This is an option. I think the default value varies between different ROMs, but you can check it by going to Start-Settings-Phone and selecting the Time Zones tab. If it's not there, you can use HTweakC to get it to show up.
Can anyone shed some light on this for me?
I live in the US Eastern time zone (GMT -5), some how the phone switched to US Pacific (GMT -8). In the process of switching it back I fat-fingered my way into the visiting time zone of Paris, Madrid (GMT +1). Problem with that is I had three alarms set for work that I use Monday through Friday at 3am, 3:15am, and 3:25am. Those still go off as normal and I can change them and turn them off, but now I have two more sets of alarms that I can’t get rid of that go off for the other two time zones.
So I have my normal alarms that go off at 3am, 3:15am, and 3:25am
Then the ones at 6am, 6:15am, and 6:25am that I can’t turn off
And then three more at 9pm, 9:15pm, and 9:25pm that I can’t turn off
Is there a way in the registry or something that I can disable the ones that go off in the 6am hour and the 9pm hour? I would really like to be able to do this without hard restarting the phone.
Any help is greatly appreciated.
you have to clean up the notification queue.
there are tools like dotfreds task manager which can do these tasks for you.
Thanks, cleared them out. hopefully the fix is that easy!
What would cause the clock to be incorrect? It's happened several times and I don't know why. I thought that the current time was supplied by the network. It always was on my previous phones. I completed a call a few minutes ago and when I set the phone down I noticed it said 10:00 am when it was actually 1:58 pm. I did a soft reset and it is now correct, but what would cause this?
What country you got it set on?
United States, Pacific time zone. If it were a simple issue with the region the minutes would still be correct. When it happens the whole time is off.
This has happened to me also. I have double and triple checked my time settings - daylight savings time is enables, the correct time zone (the correct country), etc.
I was late for work this morning since my cell time was incorrect and the alarm sounded 2 hours late.
M
EDIT: Please see this thread for possible solutions.
Hmmm...reading through that thread it seems like it is more a phone issue than network issue. I'm going to try the regedit and see if that works. It's only happened twice, but I use my phone for a wake up alarm, so it could be a potential disaster if it happened during the night.
All, i'm having a huge problem. beginning last weekend, whenever I wake up I find my phone clock has become nearly 5 minutes slower.
Because of my sleep schedule on the weekdays, its always 5 minutes late by the time i wake up. strange thing is, within 10-15 min of my phone being "awake" I assume the auto clock sync corrects the wrong time and by the time i'm i'm driving to work the clock's time is right.
i tried turning off wifi one night i think a couple days ago to see if it was some type of strange wifi issue and i found that with wifi turned off, my phone was almost 20 minutes off on the time.
This has affected strangely my alarm clock as well and sometimes it doesn't even go off and i naturally wake up and check and it shows the screen where the alarm clock is running, asking me to "dismiss" or "snooze"
This is super cumbersome, is ANYONE else having this issue with the hox? my only conclusion is while i am sleeping and my phone is on standby for many hours something isn't quite doing its job. maybe something like the phone time being off, i don't know, like 30 seconds an hour or something. I'm still on 1.73.
during the day while my phone is turned on every 30 min to an hour, my clock is perfectly sync'ed.
please help.
turn off auto updating and manually set it - does it still happen?
it could be a conflict between phone time and network time, and the phone stops checking when asleep?
phil112345 said:
turn off auto updating and manually set it - does it still happen?
it could be a conflict between phone time and network time, and the phone stops checking when asleep?
Click to expand...
Click to collapse
that's a good test to try. will do that tonight, turning off network sync and leaving it on manual. will report back tomorrow AM
chillsen said:
All, i'm having a huge problem. beginning last weekend, whenever I wake up I find my phone clock has become nearly 5 minutes slower.
Because of my sleep schedule on the weekdays, its always 5 minutes late by the time i wake up. strange thing is, within 10-15 min of my phone being "awake" I assume the auto clock sync corrects the wrong time and by the time i'm i'm driving to work the clock's time is right.
i tried turning off wifi one night i think a couple days ago to see if it was some type of strange wifi issue and i found that with wifi turned off, my phone was almost 20 minutes off on the time.
This has affected strangely my alarm clock as well and sometimes it doesn't even go off and i naturally wake up and check and it shows the screen where the alarm clock is running, asking me to "dismiss" or "snooze"
This is super cumbersome, is ANYONE else having this issue with the hox? my only conclusion is while i am sleeping and my phone is on standby for many hours something isn't quite doing its job. maybe something like the phone time being off, i don't know, like 30 seconds an hour or something. I'm still on 1.73.
during the day while my phone is turned on every 30 min to an hour, my clock is perfectly sync'ed.
please help.
Click to expand...
Click to collapse
Are you using a custom kernel? Some kernels can have time slew issues. Most people don't notice it. I use Clocksync from the market to keep synced.
Sent from my HTC One X using Tapatalk 2
Evil-Dragon said:
Are you using a custom kernel? Some kernels can have time slew issues. Most people don't notice it. I use Clocksync from the market to keep synced.
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
i've only rooted it for titanium back up. kernel is factory. i am definitely going to look into clocksync as well after tonight's test. thank you.
i can confirm after i turned off network clock sync that it indeed was not the problem and that there is something inherent in the software that is slowing down my clock on my phone overnight. thing is i don't have any crazy apps. this is so strange.
anyways i have downloaded ClockSync and seeing if this will fix the problem. thanks
Hello everyone,
I know the alarm free date #SAD...# is a beta feature at the moment, but I've run into a bug with it that I thought you should know about.
I have a section on a widget where I show the next alarm date and time, but I want to also show bedtime, which would be the alarm minus 8 hours. I know for standard dates, I can do something like #D-480...# if I want to subtract 8 hours. I can even do math within the variable, such as #D-$(8*60)$...# to subtract 8 hours. When I try this same sort of thing with the alarm free date variable, I find that it compounds amount added or subtracted each minute until something causes it to reset.
To make a simple example, if my alarm is set for 3:30 on Monday, and if I want to display the alarm time with 1 minute subtracted from it, I use #SAD-1 P:mm p#, and I should get 3:29am on Monday. It works correctly for the first minute, but as soon as another minute passes, I see that the the adjusted alarm time now shows 3:28am. So every time a minute passes, the adjusted alarm time gets multiplied by the number of minutes passed since I saved the widget. If I subtract 2 minutes at a time, then I see the time drop by 2 minutes as each minute passes. If I do 8 hours, then, well, it gets very strange very quickly.
I have noticed that the adjusted alarm time will reset from time to time, going back to the correct calculation for a minute, but I'm not sure of what causes the reset. Sometimes it will go back to the correct calculation after editing the widget, and sometimes it won't. Other times it will go back to the correct calculation after my screen has been off for a little bit and then I turn the screen back on, but not every time. Also, it looks like it may not add or subtract additional increments while the screen is off. Again, with my example of subtracting 1 minute, if my screen timeout is 2 minutes, then by the time the screen turns off, I'll see 3 minutes subtracted in total. If I turn the screen back on 10 minutes later, it will still show the 3 minutes subtracted. The next minute that the screen is on, it will either reset to 1 minute being subtracted, or it will continue to 4 minutes subtracted.
FYI, I'm on a Samsung Galaxy Note 3, Android version 4.4.2, Sprint, rooted, but I am running on stock ROM and kernel.
I hope that this helps pinpoint where the bug may be. Please let me know if any other information is required.
Thanks,
Jeremy
Same problem here.