Daylight Savings came early... - Droid Incredible General

So I woke up this morning at 10, went back to sleep and woke up at 9:30 - according to my phone. It's like daylight savings got triggered a week early, and it's not good, since I use my phone as my alarm clock. Help?
I'm running Virtuous 3.1.0
I don't think I changed any settings (unless I hit anything in my sleep)
I've checked with other Verizon users in my area (greater Chicago), and I'm the only one with the issue
Handcent, oddly enough, shows the correct time, whereas the HTC Lockscreen and Yr.No Weather Widget show the incorrect time (and in the pull down bar too)
Is there any quick setting fix I should know about?
Is anybody else having this problem?
Thanks
EDIT: Well, I fixed my own problem, just went to Settings > Date & time, and unchecked Automatic and set it myself. Doesn't answer the question of why the Automatic setting isn't working, anyone else know why? Also, now Handcent is an hour ahead..

Related

Alarm doesn't work properly

The whole point of setting the alarm is that you can just leave it and know that it will go off at the assigned day and time. Unfortunately, it is just not reliable at the moment. I have already been late for work once, and have gone back to using my WinMo phone for the alarm, as at least that works every time.
It does seem to be an Android issue, I have seen it mentioned on other forums for other handsets, but I want to track down exactly what might be causing it on the Hero, and if there is a work around until HTC/Android releases fix it.
First off, the screen is switched off, but the phone is stil powered on, just like any other phone when you have the alarm set.
When I got the phone on Thursday, I set the alarm for Monday through to Friday, 10.30am.
Friday morning, the phone wakes and the alarm goes off at 10.30. Fine.
Monday morning, nothing happens. Go into the settings, check alarm set for the correct time and day, all is fine, it just didnt go off.
Tuesday morning, it works fine, phone wakes and alarm goes off at 10.30.
Wednesday morning, nothing. WinMo phone alarm wakes me at 10.34. I switch on the Hero's screen, and immediately the alarm goes off, 4 minutes late!
Last night I didnt charge it, thinking it may be an issue when being charged. But this morning it didnt work, so it is not an charging issue.
The Alarm icon was showing the top corner, so the alarm was obviously set, and the Clock App was still running (I checked in Advanced Task Killer). I will try to set it again tonight from scratch, and see if that works.
Having to set it every night would be a pain, but at least it would actually work like it is supposed to.
I've got the same issue and was about to get late for work this very morning just because of it. Luckily me I've got some sleeping disorders so I woke up before the clock should have went of either way...
HTC Needs to fix the clock in their TouchFLO..
Got somewhat the same problem...
Could a hard reset help?
A hard reset didn't do the trick for me. I really need the alarm clock to work so I think I'll buy an alarm clock app on the market, but I shouldn't have to ...
If you are using taskiller or advanced task manager, make sure you exclude the clock app from killed processes. I had this problem, when the clock came back after being killed the alarm wouldn't work even though the icon was there. Excluding it fixed it.
Cheers Ewans, i was killing the clock process and it was this that stopped my alarm this morning. Made me late! Still, i forwarded my boss this link so he could read himself. (Not that he was mad. He's a great boss!)
We should maybe think about making a list of processes, what they do and what you can/can't kill.
For instance, i don't use the Twitter widget as i find the notification bar and having Peep on my home screen just as quick and less resourceful hungry. But if you kill Peep sitting in the background, it will stop any notifications, so this needs to be left alone.
Even if I don't kill it (noticed that too), it still fails to go off sometimes.
Yes, it is not totally obvious what is going on yet.
The fix (based on one days trial!) seems to just before I sleep to go into the clock app, disable the alarm, then immediately enable it again.
This results in the "Your alarm will sound in 7 hours 10 minutes" type message.
That worked this morning, the question is if I leave it alone now, and dont kill the clock app, will it still work tomorrow? And if I restart the phone, will the Clock app and then the alarm still be running or do I have have to go into the Clock App manually?
If my clock is showing on the home page, and the alarm icon is in the top bar, I expect the alarm to go off.
It should not be possible to kill the alarm process, it shouldnt be part of the clock app at all, but a separate background process with settings controlled by the clock app, but not reliant on the clock app running.
This is what I've found out.
When you program your alarm for multiple days, it only sounds the first day.
If you uncheck and check your alarm, it will go of the next day.
This is without using TasKiller or something similar and without resetting. (just did nothing)
It looks like the multiple day option is a fake and you will have to set it every day. Allthough I haven't tried out multiple alarms, thinking about seven alarms, but you'll have to reset at least once a week.
Good luck waking up
Alarm works fine for me now, I use one for weekdays that goes off everyday, and another just on Sundays at a different time. I'm using a standard G2.
Check out the alarm volume settings.
The alarm has its own volume setting which can be change when you are inside the clock app and select the ringtone for an alarm (by pressing the standard volume up/down keys).
By accident mine was set to lowest value so it didn't go off but just vibrated.
Ok, after a week of testing, it seems that if you dont bugger around with killing the clock app via Task Killer or something else, it is fine.
I havent yet seen whether it will still be set if I completely switch off and switch on again. I will try that tonight. Even though alarm icon is shown, will the alarm be set without me going into the Clock app explicitly?
Works for for me, 2 alarms set for 6:15 & 6:30am mon - fri, never had an issue.

Incorrect Clock/Time After Hibernation

Hi,
I checked the web on this issue and have found it being reported on other sites but I can't seem to find the resolution, if there is one....
I received my Nexus 4 last Friday. Been digging it ever since. I came from the SG2 Skyrocket on att. I realized how much I miss the pure Android experience on a phone without the carrier's bloatware and manufacturer software.
however during the Super Bowl, my buddies and I discovered a weird bug on the phone. Upon waking up from a "long" hibernation, my time/clock is off by 20-30 minutes. Once I reboot the phone, the time is corrected. However, it's kinda weird waking up in the morning, my bedside clocks displays the correct time but when i wake up my phone, the time/clock is incorrect.
Has anyone experienced this? Does anyone know the resolution??
Much thanks..........
It happened to me once or twice before on my N4 stock/rooted. What is your setup under Settings>Date and Time ? Sometimes when you have Automatic date & time and Automatic time zone enabled and you are out of mobile network service, the time doesn't get updated until your phone mobile connection is restored. In my opinion, this behavior smells like a bug. Post a screen shot of that settings page if you could....
Hash_Map said:
It happened to me once or twice before on my N4 stock/rooted. What is your setup under Settings>Date and Time ? Sometimes when you have Automatic date & time and Automatic time zone enabled and you are out of mobile network service, the time doesn't get updated until your phone mobile connection is restored. In my opinion, this behavior smells like a bug. Post a screen shot of that settings page if you could....
Click to expand...
Click to collapse
Hi Hash,
Thanks for the feedback. I went into the settings, as you directed, and see that both Automatic date & time (use network provided time) and Automatic time zone (use network provided time zone ) are both checked.
I will try and take a picture tomorrow morning for, again, it was weird looking at my cell phone which says 5:35am when my bedside clock showed 6:00am.
Schwacker
My Issue with Pictures
All,
To document what is happening to my phone, I am attaching pictures to this post. The early morning picture post, I had my Wifi turned on. After the pictures were taken, I turned off WiFi an let it go int hibernation until I woke up at 6am. As you'll see in the second picture, my time/clock was way off.
I am using Beautiful Widgets for the clock but can't see that causing my issues.
Any thoughts? Hate to return the phone for I'm really loving it but don't want the phone if I can't depend on the time!
Thanks!
Schwacker said:
All,
To document what is happening to my phone, I am attaching pictures to this post. The early morning picture post, I had my Wifi turned on. After the pictures were taken, I turned off WiFi an let it go int hibernation until I woke up at 6am. As you'll see in the second picture, my time/clock was way off.
I am using Beautiful Widgets for the clock but can't see that causing my issues.
Any thoughts? Hate to return the phone for I'm really loving it but don't want the phone if I can't depend on the time!
Thanks!
Click to expand...
Click to collapse
Have you tried the stock clock to see if Beautiful widgets is the issue. Try that first. Next thing I would try is to leave WiFi on during sleep and see if the issue is fixed. I would expect to have some lag after a wakeup for the clock to update but no more than 15 seconds. Good luck.
grubbster said:
Have you tried the stock clock to see if Beautiful widgets is the issue. Try that first. Next thing I would try is to leave WiFi on during sleep and see if the issue is fixed. I would expect to have some lag after a wakeup for the clock to update but no more than 15 seconds. Good luck.
Click to expand...
Click to collapse
Thanks Grubbster -- I have to admit and I'm somewhat embarrassed in doing so, I couldn't figure out how to use the stock clock on my home screen and when I couldn't figure it, I thought "hey, I purchased Beautiful Widgets...I'll just add that clock to my screen....".
FYI -- I have always left my wifi on during the night and into hibernation. Last night I had the brain child thinking maybe it's the Wifi that is causing my delays for when I first noticed the time issue on Sunday, it was while I had my Wifi on....so I thought I'd turn it off to see if the time would be correct......freaking weird....
Schwacker said:
Thanks Grubbster -- I have to admit and I'm somewhat embarrassed in doing so, I couldn't figure out how to use the stock clock on my home screen and when I couldn't figure it, I thought "hey, I purchased Beautiful Widgets...I'll just add that clock to my screen....".
FYI -- I have always left my wifi on during the night and into hibernation. Last night I had the brain child thinking maybe it's the Wifi that is causing my delays for when I first noticed the time issue on Sunday, it was while I had my Wifi on....so I thought I'd turn it off to see if the time would be correct......freaking weird....
Click to expand...
Click to collapse
The stock clock is a widget. Just go into your widgets, long press the clock, and drag it to your home screen. Also, does the clock in the status bar show the correct time when waking up?
Check your beautiful widget app settings to see if there is anything related to updating system settings. Maybe a frequency (10 min, 15 min, etc.) that needs to be changed.
grubbster said:
The stock clock is a widget. Just go into your widgets, long press the clock, and drag it to your home screen. Also, does the clock in the status bar show the correct time when waking up?
Check your beautiful widget app settings to see if there is anything related to updating system settings. Maybe a frequency (10 min, 15 min, etc.) that needs to be changed.
Click to expand...
Click to collapse
Ok. Thanks -- duh -- there it is. I'll try this for a day to see if this will resolve the issue.
This has happened to me once, on Faux's kernel. It was my first time ever undervolting my device, and I undervolted by -100 mV (fast binned chip). It did it twice, and both during deep sleep. But the time corrected itself once I go into Settings > Date & Time and unchecking-and-rechecking the Auto Time setting.
Do you use a task killer?
Michealtbh said:
Do you use a task killer?
Click to expand...
Click to collapse
No. No task killer....though I have to admit....I was discussing my issue with a fellow phone geek. He believes my 2 options are: if it's an internal hardware issue, I'll need to get a new phone if it loses connection to the antenna which connects to my att network for the time/clock. Or if it's a software issue, then maybe a flash can resolve it.
I'm also going to contact Google later today and see what my return options are if, by tomorrow, I'm still experiencing this..
Thanks...

Alarms Broken?

So I have been using Timely for quite a while on my HTC One m7 and Nexus 5, but ever since I started using my Nexus 6P as my daily phone, I have noticed that the alarm is hit or miss. I tried the suggestions from here, but that does not seem to have made much of a difference. I have also tried going to the stock Clock app, it seems to be a bit better, but not by much.
What I have been noticing is that the alarm I have set for 5:30AM it will either go off or it will just not go off at all and I will get a notification that the alarm was missed at 5:30AM. If the alarm does go off, I usually hit snooze and just lay in bed until it goes off again checking email or something on my tablet (so the phone should still be locked). When I realize that I have been awake longer than 10 minutes, I look at my phone and there is a notification that the alarm for 5:30AM was missed... So it realized the alarm should have went off, but didn't.
I also have 2 later alarms (9:35AM and 10:20AM) and both of them are still in Timely and they work just fine, so maybe there is something with the deep sleep in Marshmallow?
I am running the stock image, updated to 6.0.1 via OTA, no root, no custom kernel, nothing that IMO should be affecting the operation of this type of stuff.
Just wondering if anybody else is having similar issues or if somebody can recommend an alarm app that is not suffering from this issue.
It seems that any alarm other than stock has issues. I see the post you referenced mentioned adding exceptions for those apps to prevent battery optimization. Did you try that with no luck? I don't know if there has been much luck other than just using the stock alarm if you really need to depend on it to wake up for work or other important events. I have never had stock alarm not go off, but I don't use any other apps.
fury683 said:
It seems that any alarm other than stock has issues. I see the post you referenced mentioned adding exceptions for those apps to prevent battery optimization. Did you try that with no luck? I don't know if there has been much luck other than just using the stock alarm if you really need to depend on it to wake up for work or other important events. I have never had stock alarm not go off, but I don't use any other apps.
Click to expand...
Click to collapse
I did try turning off optimizations for Timely, that did not seem to help much. The funny thing is that the stock alarm is also having similar issues, so either I am that heavy of a sleeper or maybe I just need to try flashing the factory image back to it, which, like I mentioned, I do not think I did anything to cause this type of issue, but it is an OS after all, so who knows what could anger it.
I did just tonight try setting the auto dismissal time to Never as well as maxing out the volume (it was down by about 10%), so maybe that will wake me up.
I'll see what happens tomorrow morning and will report my findings a little later. In the mean time, if anybody can think of something that I could try, it would be greatly appreciated, although a restore is not the end of the world, I would like it if I didn't have to spend the time restoring the apps and accounts and what not.
Does this apply to you?
gotzaDroid said:
Like Red said, you need to have an alarm set first. AND... Any automatic "do no disturb" settings like, "every day from xx : xx to xx : xx" will override the "do not disturb until next alarm". So if you have the phone automatically do not disturb until 8am every day, but you need to wake up at 6am and set the do not disturb to until next alarm before your usual rules kick in... at 6am, do not disturb will not automatically turn off with the alarm. It'll stay on until 8am. Just FYI.
Click to expand...
Click to collapse
Sent from my Nexus 5X using Tapatalk
I'm on 6.0.1 stock and I use Timely, have no issues at all...
For what it is worth, after I set it that the Stock Clock Alarm Never gets dismissed and made sure the alarm volume was set to 100%, it has been going off like... umm, clock work. I tried doing Timely last night and made sure I had another alarm setup just in case, I noticed the Stock Clock alarm went off on the other device, but my 6P with Timely, did not go off.
I'm just going to give up on Timely for now, maybe they will release an update and I will give that a shot, but for now, Stock it is.
The new doze mode will impact any alarms apps that are not updated for android M to use GCS etc. that's why your alarms are not firing.
For now you have to use the stock google alarm which correctly works with doze mode.

Network set time is an hour behind after Nougat update

After my update yesterday my phone's clock is now an hour behind, I'm using the time set by the network feature, and prefer to use this over the manual time and date. Rebooting the phone fixes the problem temporarily, but it eventually switches back. Has anyone else experienced this issue or know how to fix it?
I did see this, yesterday, but only the clock in the notifications bar though. The clock widget continued to display the proper time.
First I thought I was misreading the tiny clock digits, but no.
Restarted the phone and it hasn't appeared again since.
Yes, the clock on my weather widget was correct, but my task bar clock and side bar clock were wrong, even after a reboot it was correct, but eventually go back to being wrong. I just turned of the feature to have the time set by the network for a day, and when I turned it back on the clock has been correct ever since. I find that to be strange, but it's fine now so I'm not going to sweat it.

No incoming texts over night until morning; they never show up

Hi folks,
I've got the 6013 model in the US, running on AT&T, completely stock never rooted, fully updated to 10.3.11. Either the most recent update, or the one before that, seems to have caused an issue where texts sent to me overnight or in early morning before I first use the phone never show up. I've missed some important notifications due to this. The worst thing is they NEVER show up... they aren't just delayed until I wake the phone up. After I start using the phone, new texts make it through just fine. The phone seems to be sleeping deeper or something and not getting any of these cellular-based texts. Emails and other notifications based on wifi internet seem to be showing up fine.
Do not disturb is NOT enabled (and, I've tried toggling it on and off without change). This has been going on for weeks or longer, multiple reboots, etc.. I've checked my default texting app (Textra) and the phone's built-in Messages app... the texts aren't in either app. They just never show up.
What else can I look into to check the cause of this and hopefully a fix?
Thanks!
As a test today, I sent a text from my work phone to my personal OnePlus when I got up (late! Father's Day!) before interacting with my OnePlus at all. It did receive the text just fine. I think the cellular radio may be on some timer and going to sleep / waking up on some sort of schedule. Where are the settings for controlling this kind of thing? I haven't messed with this phone's settings much... it just worked fine out of the box and ever since for the last two and a half years until recent update messed this text thing up.
Further information: In Settings, Battery, Battery Saver is OFF (I've never enabled this) and under battery optimization I noticed Textra was set for Intelligent Control; I've toggled this to Don't Optimize. "Messages" was not present; I never use it.
Is there anything else to try? Note that the phone is plugged in and fully charged at the time these issues are occurring.
Frankenscript said:
Is there anything else to try?
Click to expand...
Click to collapse
Dude, not sure but hope it will work,
anyway trying will cost nothing...
Go to settings > battery > battery optimization >
hit on upper right 3 dots and select advanced optimization,
then be sure " SLEEP STANDBY OPTIMIZATION"
is toggled OFF.
Try again and cross your finger...
Cheers
Dadditz said:
Dude, not sure but hope it will work,
anyway trying will cost nothing...
Go to settings > battery > battery optimization >
hit on upper right 3 dots and select advanced optimization,
then be sure " SLEEP STANDBY OPTIMIZATION"
is toggled OFF.
Try again and cross your finger...
Cheers
Click to expand...
Click to collapse
Thanks @Dadditz , that was already off. Sigh. Not sure why this happens. I've tested when I get up at 7 am, sending a text from another phone, and my 6T receives it, but during the darker hours of the night, no joy. Thanks for the reply, though.
Just as a follow up, the problem seems intermittent. I got some 4 am texts from my sump alarm when the wifi went down briefly. No idea what's going on, but it's intermittent rather than constant.

Resources