Related
Hi,
I've began to have a weird problem with my Touch Pro since about a few days ago. The "Next Alarm" on the TouchFlo 3D "home" screen does not update accurately. For example, I have an alarm set now for 6 AM next morning, but the line says "Alarm Off".
I've had an alarm set today for 6AM and another for 7AM. After the 6AM alarm went off, I dismissed it, but the screen kept showing 6AM as the next alarm.
Also, I don't get a pop-up when the alarm comes off. The sound plays, the device vibrates, the bell icon appears in the title bar, but no notification pops up.
I'm using the stock ROM that was on my device (1.90.401.1 WWE, ROM date 08/01/08).
Things I tried that didn't help:
- Soft reset - the problem reappears after a while. TouchFLO 3D sometimes restarts if the device is turned on after a long period of inactivity by sliding the keyboard out. After the restart the alarm line says "Alarm Off" even though I have an alarm for the next day at 6 AM.
- Clearing the notification queue doesn't seem to have any effect at all.
Any ideas? Thanks for any help.
Any ideas anyone? Pleeease! This bug annoys me and I don't want to do a hard reset :-(
i have the same rom and tha same problem
its strange cos i tink at the start i did get a dismiss button, but now i only get the icon and the ring/vibration
i tink htc still need to fix alot of problems
I was just going a search for this same problem.
When I first got my Touch Pro less than 2 weeks ago, I got a dismiss button. Now it's gone and I have to go diving for my stylus on a morning to open up the alarm thing at the top, then wait for the next screen, then choose the alarm, THEN I can dismiss it.
REALLY annoying.
Anyone know what this is?
I actually fixed that one. It seems that something (Advanced Config?) caused my notification settings to be reset. After changing them back in Start->Settings->Sounds & Notifications it all went back to normal. However the next alarm is still not accurate sometimes. Seems like it's only update occasionally and not immediately.
justme84 said:
After changing them back in Start->Settings->Sounds & Notifications it all went back to normal.
Click to expand...
Click to collapse
I've tried this a few times, and the alarm still doens't pop to the front.
Last night I turned TouchFlo off alltogether, and it STILL doesn't pop to the front.
So it *MUST* be something in Windows Mobile somewhere.
Does anyone else have any clue?
You know what, I just did some intensive Googling and found this
https://forums.microsoft.com/WindowsMobile/ShowPost.aspx?PostID=3951579&SiteID=65
To summarise
Start -> Settings -> Sounds & Notifications
Choose Notifications Tab
Change the dropdown to Reminders (the bit I missed)
Now you can see a checkbox for Display message on screen
Check the box, click OK, close settings.
Fixed
The clock & alarms has been a problem since Windows Mobile saw daylight.
I don't use it anymore as my alarm, I use pTravelAlarm instead.
Works like the alarms on WM should: Dependable, and a BIG snooze button
I wanted to use the stock alarm for my X10 mini pro, but it ONLY sounded off once and DOES NOT REPEAT. As a result, I got a warning letter from my work for going to work late.
Now, I'm having trouble finding a good alarm clock, that sounds off the alarm and repeats UNTIL dismissed.. can anyone reccommend me?
if you Snooz it and not Dismiss it will go off again in 15min, that is all i do with my X10
Try kaloer clock
Sent from my X10i using XDA App
or digital clock by social & mobile.
Mobzter said:
Try kaloer clock
Sent from my X10i using XDA App
Click to expand...
Click to collapse
Yeah, Kaloer clock is amazing. Check it out
Android Variations: Check em out!
Math Alarm Clock (the one I use)
One of the best apps EVER.
Also, if you can get good night sleeps get Smart Alarm Clock (it detects by movements the phase of sleep you are so I wakes you up on REM ) (it kindda work, but BLOWS MY BATTERY)
i use "Alarm Klock"(free on the market) :
you can param snooze timer, use MP3 as sound, progressive volume(settable), vabrate (or not), set label name for each alarm ...
For snooze : there a giant button
to stop the alarm, there a button ton slide (like to unlock an iPhone)
im having the same problem after i got the OTA update (on rogers network in canada btw)
the alarm would go silence on its own after a minute of going off, and then it doesnt repeat
:S
How about setting a couple of alarms with the stock app instead of one?
I use shaketowake.
Have to shake every morning about 20 times, and shake it hard for 1 alarm. Believe me you will wake up. First time it took 5 min to shake.
Kaloer clock was working perfectly before the OTA update.
After the update....its a bit slow and not as responsive.
Do you guys have the same issue with it?
royalbloodvi said:
As a result, I got a warning letter from my work for going to work late.
Click to expand...
Click to collapse
Geesus, how late were you...?!?
k1sr said:
Geesus, how late were you...?!?
Click to expand...
Click to collapse
Dont think he went in till the next day rflmao!!
Which update version you running? I didn't know this issue cos I always wake up after first alarm, if the alarm really only go off once and nvr repeat, I have to start using new alarm.
Sent from my X10i using XDA App
Since the JB update, the standard clock's alarm has stopped working properly. Prior to JB if an alarm was set and the tab was closed/charging the alarm would go off continuously and the tab would vibrate, I would unlock with my PIN and there would be a dialog up to either hit "dismiss" or "snooze".
Since JB, if the tab is locked (open or closed) it just beeps once very briefly (sounds like it is being "caught" and cut short), does not vibrate at all, and when I unlock and open it, there is a little notification on the notifications menu with the alarm info. If I click on that, it opens a dialog that says "dismiss" or "snooze". If the screen is not locked, it behaves exactly like it did above with no notification.
Anyone else see this or who could try reproducing it? I have not messed with any settings, when I look at them everything is like I would expect. I have never seen an alarm sent to the notification tray rather than sounding and this behavior strikes me as a bug.
Anyone have an alternate alarm clock they use with TF and JB?
You are not alone. I've deleted the clock cache, done a hard reboot and still the alarm only gives a brief "chirp" and is heard no more.
I had come to rely on the alarm in my travels as it has worked without fail whether on or in sleep mode- until the jelly bean update.
BoulderBill said:
You are not alone. I've deleted the clock cache, done a hard reboot and still the alarm only gives a brief "chirp" and is heard no more.
I had come to rely on the alarm in my travels as it has worked without fail whether on or in sleep mode- until the jelly bean update.
Click to expand...
Click to collapse
Thanks for the confirmation of the issue. At least I know someone else is seeing this and it is not some crazy setup issue. I am disappointed too. I've been using this in lieu of a real alarm clock while in a temporary living situation, so it's something I want to find a solution for...
Tested same thing, I dont use the feature but it is broke how you described it.
zenaxe said:
Since the JB update, the standard clock's alarm has stopped working properly. Prior to JB if an alarm was set and the tab was closed/charging the alarm would go off continuously and the tab would vibrate, I would unlock with my PIN and there would be a dialog up to either hit "dismiss" or "snooze".
Since JB, if the tab is locked (open or closed) it just beeps once very briefly (sounds like it is being "caught" and cut short), does not vibrate at all, and when I unlock and open it, there is a little notification on the notifications menu with the alarm info. If I click on that, it opens a dialog that says "dismiss" or "snooze". If the screen is not locked, it behaves exactly like it did above with no notification.
Anyone else see this or who could try reproducing it? I have not messed with any settings, when I look at them everything is like I would expect. I have never seen an alarm sent to the notification tray rather than sounding and this behavior strikes me as a bug.
Anyone have an alternate alarm clock they use with TF and JB?
Click to expand...
Click to collapse
It's not a bug since it's working fine on by tablet. My clock version is 2.03 and default ringtone is celsium. Did you tried to wipe DATA and CACHE, then reboot? Did you freeze any system app? Could you try the same ringtone as mine?
It is a bug or an intended feature to save power. It only beeps correctly if the clock is on the screen, either bright or dim. If the screen is off as in sleep mode, then it beeps once only then stops.
My wife certainly noticed yesterday morning! Good thing that i had an alarm set also!
Sent from my ASUS Transformer Pad TF700T using xda premium
Also confirmed the issue
I have the same exact problem
The day after the update I set it to wake me up the next morning and it didnt work either so now I leave it plugged in and the screen open in the dock and it works. I dont know what I did the first night but I almost didnt wake up. I also noticed if you put the volume all the way down to vibrate the alarm doesnt go off aswell but ICS work fine. All other sounds on silent but alarm still sounded off on ICS.
Sent from my ASUS Transformer Pad TF700T using XDA Premium HD app
Me too. So, anyone let Asus know about this bug yet?
haha just found out this morning too. i had set the infinity alarm as my backup alarm because i just flashed a new rom on my phone. good thing the phone alarm still works. that could have been nasty
ya found this out the hard way this morning, when I was 45 minutes late for work.
is it due to the tablet going to sleep? I know in ICS i had the power settings set to never sleep if plugged in. cant find the equivalent 'if plugged in' settings. so for now I will test it if i set it just never sleep ever.
Here's a fix until Asus sort it out - keep the clock app open when you shut the tablet off. I think it's something to do with the alarm's Snooze/Dismiss notification. I'd keep a backup alarm set even using the fix,though - at least for a little bit.
I don't even have a TF700, but my fellow editor over at Pocketables does and wrote about this issue. I threw together a Tasker project that sort of fixes this, at least makes the alarm make some noise again. Exported it as a standalone app and he tells me it works. Details and download here if anyone would like to try it out: http://www.pocketables.com/2012/10/transformer-pad-infinity-temporary-alarm-fix-app-download.html
Details about what it does and disclaimer is in that post as well.
I have the same issue. Anyone here try working around this bug via another market alarm app? I'm at work at the moment so can't try -_-
Same problem here. I've stopped using it until this problem is resolved.
bluejay2345 said:
Same problem here. I've stopped using it until this problem is resolved.
Click to expand...
Click to collapse
Feel free to try the fix I stated in the comment above, it does work.
I'm using Alarm Clock Extreme Free until this gets sorted out.
I tried flashing DeskClock.apk from several diff JB roms (stock/AOKP/CM10) but it keeps giving force close :\
All of my all day calendar notifications go off hours after they are suppose to. I have tried using multiple different calendar apps (stock, google calendar, today calendar, etc). They all do the exact same thing. If an all day notification is suppose to go off at 9AM it will alert me at 6PM. Calendar events that are set for a certain time work fine. Anyone have a fix for this?
UDM2004 said:
All of my all day calendar notifications go off hours after they are suppose to. I have tried using multiple different calendar apps (stock, google calendar, today calendar, etc). They all do the exact same thing. If an all day notification is suppose to go off at 9AM it will alert me at 6PM. Calendar events that are set for a certain time work fine. Anyone have a fix for this?
Click to expand...
Click to collapse
I have similar problem! I haven't found any fix. Seems like firmware bug.
SW Version FRD-L09C432B120
chocholousek said:
I have similar problem! I haven't found any fix. Seems like firmware bug.
SW Version FRD-L09C432B120
Click to expand...
Click to collapse
That is what I'm thinking too.
UDM2004 said:
All of my all day calendar notifications go off hours after they are suppose to. I have tried using multiple different calendar apps (stock, google calendar, today calendar, etc). They all do the exact same thing. If an all day notification is suppose to go off at 9AM it will alert me at 6PM. Calendar events that are set for a certain time work fine. Anyone have a fix for this?
Click to expand...
Click to collapse
You need to go in Advanced setting>Battery Manager>Protected Apps and turn protection on for the Application in question or it won't run i the back ground.
Backup, Hard reset, restore.
Try setting battery mode to performance to see if it still happens.
Protect app in phone manager, battery.
zinko_pt said:
Backup, Hard reset, restore.
Try setting battery mode to performance to see if it still happens.
Protect app in phone manager, battery.
Click to expand...
Click to collapse
I don't think that it helps. Reminders of "usual" events works perfectly. Only reminders of All-day events are notified in wrong times. Of course, Google calendar is set as protected app..
You could try it to rule those causes out.
UDM2004 said:
All of my all day calendar notifications go off hours after they are suppose to. I have tried using multiple different calendar apps (stock, google calendar, today calendar, etc). They all do the exact same thing. If an all day notification is suppose to go off at 9AM it will alert me at 6PM. Calendar events that are set for a certain time work fine. Anyone have a fix for this?
Click to expand...
Click to collapse
If you have them set on onther devices: on other devices do they work correctly?
malnabokor said:
If you have them set on onther devices: on other devices do they work correctly?
Click to expand...
Click to collapse
Yes, on all of my other devices they work correctly.
Pretty sure it's a bug with the software app, as mine is experiencing it as well. Hopefully can be fixed with a software update.
dmooney7291 said:
Pretty sure it's a bug with the software app, as mine is experiencing it as well. Hopefully can be fixed with a software update.
Click to expand...
Click to collapse
Are you still experiencing this problem?
Sent from my FRD-L04 using Tapatalk
Today I did a factory reset to see if that would help my time delay problem. Unfortunately, it did not. However what I did notice is that when I set a calendar reminder to go off at 9AM on my phone it shows up as 12AM on my Google Calendar.
UDM2004 said:
Today I did a factory reset to see if that would help my time delay problem. Unfortunately, it did not. However what I did notice is that when I set a calendar reminder to go off at 9AM on my phone it shows up as 12AM on my Google Calendar.
Click to expand...
Click to collapse
Is your phone's time zone the same as your Google calendar?
I don't experience such issue on my phone, so I guess it's not really a software bug.....
ykkhern said:
Is your phone's time zone the same as your Google calendar?
I don't experience such issue on my phone, so I guess it's not really a software bug.....
Click to expand...
Click to collapse
The time zone is correct. I called Huawei and they said they did not know why it was happening and that I would have to send my phone in. However, they could to guarantee anything.
The issue is still not fixed....
I also have an Honor 8 and when I set an alarm for an all-day event, the alarm goes off 9 hours after the initial setting. For example, if I set an alarm to go off at 6pm it will actually go off at 3am which is annoying and woke me up in the middle of the night. I am glad I am not the only person with this problem. Hopefully there will be a fix. In the meantime, I just have to adjust the alarm to a time that is 9 hours before I actually want it to go off.
natecube23 said:
I also have an Honor 8 and when I set an alarm for an all-day event, the alarm goes off 9 hours after the initial setting. For example, if I set an alarm to go off at 6pm it will actually go off at 3am which is annoying and woke me up in the middle of the night. I am glad I am not the only person with this problem. Hopefully there will be a fix. In the meantime, I just have to adjust the alarm to a time that is 9 hours before I actually want it to go off.
Click to expand...
Click to collapse
That issue drives me nuts, to the point I got a new phone. Problem Solved! I will never buy another Honor phone.
the all day events have a notification time calculated as in "X day(s) before the event, at specific hour Y" ....from what I can see on my notifications huawei wrongly interpret this as "X day(s) before the event + Y hour(s) before the event" . In my case, for example, when I set on Google Calendar (web) for an all day event notification for that specific day at 9AM setting "0(zero) days before , at 10AM" huawei calendar show it as "0 days before and -10 hours before" (-10 hours before should be exactly 10 hours after which is 10AM) but the notifications is displayed 9 hours later than it should (7PM). Also the "at the start of the event" seems to be 9 hours off ( notification at 9AM ). I had no time to do extensive testing , but seems to be something wrong with the calendar backend on the huawei phones firmware as installing different Calendar apps (including the official Google Calendar app) don't solve the "all day events" notification problem (I have a P10 , bug is present in both 7.0 and 8.0beta Android versions) .....And , it seems that "all day events" that have notifications set 1 (or more) days before and no specific hour, work as expected (or maybe I just didn't noticed the bug on this ones due to not being so critical to have a specific hour 1 week before the event for example ) .
Most of the days, my morning alarm doesn't go off. The alarms during the day are ok, but when I'm sleeping in bed doesn't work. Always with AOD off and do not disturb (programmed) on.
Anyone else experiencing? Any solution?
Enviado desde mi SM-G930F mediante Tapatalk
One time only - last week - my morning alarm (is set fro Mon-Fri at same time) just buzzed for half a second then stopped by itself. Never happened before or since, but a bit worrying that I'm already starting to see some bugs with my S3 - as my notifications about new emails now only work intermittently
My alarm also is no longer working reliably. I can test it and it works. I set my Gear S3 into do not disturb mode before going to bed and then the alarm never goes off at the set time in the morning. I have tried both auto scheduled do not disturb mode and manual do not disturb and alarm fails to work in both. For the first month I never had an issue.
Come on Samsung! This is the most basic feature. Smart Watch??
Same here. The only way I can get alarm to work is if it is running in the background the app that is that I open it to make sure it's running before I go to bed then it would work for me.
Same here gutted the vibrate only function is one of the main features I use. Got in trouble with the boss due to this watch lol. Hopefully it something fixable via firmware update.
marcgear said:
Same here gutted the vibrate only function is one of the main features I use. Got in trouble with the boss due to this watch lol. Hopefully it something fixable via firmware update.
Click to expand...
Click to collapse
Yes, should be fixed soon, the problem is that Samsung support is awfull! I have tried to report this and some other (proved) bugs and they always respond with: restart your device, reset to factory default, etc. And if it doesnt work, send it to technical repair! They should listen their customer and look/check bugs in forums like this also...
Enviado desde mi SM-G930F mediante Tapatalk
Hi all, I had the same issue. Updated the alarm app to 1.0.28, still the issue. Then I read a comment from someone that it could be a conflict with watchfaces that are not Samsung original (stock). And indeed I had installed a purchased watchface a few weeks back when the problem started. Tried switching back to a Samsung stock watchface before going to bed, and for the last 3-4 mornings, alarm has been working fine!
So I can't say for sure it's the issue, but in my case, the non-original Samsung watchface seems to conflict with the alarm function. Back to Sansung face for the night and the bug is fixed. I hope this can help others!
Happy Easter