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.
Related
Apologies if this is handled elswhere I've search and not found it.
What can I do to change the standard alarm "snooze" defaults?
They are rather poorly set at 5 mins before, 5, 10, 15 mins, 1hr, 1 day, dismiss all.
So it would be entirely sensible to have 3 hrs, 12 hrs, 3 days and some other options etc...
This means "snoozing" business things until later the same day, the next day morning, past the weekend etc...
Am I looking for a Microsoft miracle or is this possible somehow?
p.s. Running HTC Touch HD....extremely pleased with it.
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
Hi,
since some days I have a strange problem on my Samsung Galaxy Note 2 running Jelly Bean:
After I booted my device, I do some things like E-Mail and so and then (after 5 minutes) I just switch the display off.
But after some time, the display is switched on again (by itself, without me even touching the device) and off again.
This happens 5x during the first hour after booting.
I have watched this now for some days and detected a pattern:
Example:
Device booted exactly at 14:00 p.m.
After approx. 3 minutesafter booting: Display switched off manually.
1st Display-On: 14:12:24 till 14:15:32
2nd Display-On: 14:23:33 till 14:26:41
3rd Display-On: 14:34:43 till 14:37:51
4th Display-On: 14:45:52 till 14:49:00
5th Display-On: 14:57:01 till 14:59:06
What I noticed is:
1.) The first 4 Display-On-times always last exactly 3:08, but the last one only 2 minutes (as in the settings) plus the 5 seconds during which the display is dimmed befor switching off.
2.) During the first 4 times the clock stops running approx. 5x for approx. 5-6 seconds and then jumps to the exact time again. Looks as if there is a process or app runnning which is so CPU-intensive that the clock is stopped for some seconds. During the 5th Display-On, the clock keeps running okay.
3.) Time between every Display-Off and the next Display-On is exactly 8 minutes.
4.) After the 5th Display-On the "game" is over and display stays dark as it should (unless I switch it on by myself).
5.) The whole game starts over again exactly 12 hours after I first booted the device with the same routine of 5x Display-On etc.
Does anyone have a clue what could trigger this behaviour which is not only battery-draining but also annoying?
Or does somebody know an App with which I could trace down what causes it?
Just for clarification:
Neither Lookout, TrustGo, Bitdefender or Avira have detected a virus or malware on my device (quadruple-checked!).
Would be thankful for any help!
Hi,
In my calender widget, I use
Code:
$#C0SRd#>0?#C0SRdd#$$#C0SRd#=0&&#C0SRh#>0?#C0SRhh#$$#C0SRd#=0&&#C0SRh#=0&&#C0SRm#>0?#C0SRmm#$
Basically, I want to see time left from my next meeting.
The problem is, in my calander, I have both start time and end time. ( For example, Meeting with John, start-14:00, end-15:00).
The problem is with this code, as soon as start time begins(i.e. at 14:00), zooper possibly takes the end time (i.e. 15:00) as my C0SRmm and starts showing time left with that respect. So, w.r.t. the example above, if it is 13:05 on the meeting day, it will show 55 min. Which is expected.
But then, if the time is 14:00<current time< 15:00 , e,g. 14:25, it will show 35 min, i.e. time left from the end time...which I don't want.
Any help please?
Are you sure that's the behavior? For me, during an event, #C0SRm# counts the number of minutes from the event's starting time. In your example, for an event starting at 14:00, at 14:25 it will show 25 (really 26 as I see in practice).
ewcrider said:
Are you sure that's the behavior? For me, during an event, #C0SRm# counts the number of minutes from the event's starting time. In your example, for an event starting at 14:00, at 14:25 it will show 25 (really 26 as I see in practice).
Click to expand...
Click to collapse
Sorry...you are right...thats exactly what I get......and I don't want it. I just want to know when my meeting is....not how long the meeting is going.
Barud said:
Sorry...you are right...thats exactly what I get......and I don't want it. I just want to know when my meeting is....not how long the meeting is going.
Click to expand...
Click to collapse
Ok, what do you want it to say instead? Or do you want it to say nothing, or say something like "ongoing"?
I also have a countdown to my next event. I solved this problem using two copies of the countdown, one using event 0 and one using event 1. When event 0 is going on, I hide the countdown for 0 (by setting font size to zero using conditionals in the advanced parameters) and show the countdown for event 1. Otherwise, I hide countdown 1 and show countdown 0.
My test if event is occurring: #DyyyyMMddHHmm#>#C0SyyyyMMddHHmm#
If you just want to hide the countdown, you could add this to your existing conditionals.
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.