Related
My lockscreen disappeared a few days after flashing Tweaked 2.1. When you push the wake button the screens flickers then goes black. To wake the phone you then touch the black screen after the flicker and it wakes to the desktop. Would flashing the rom again help? I made sure I do not have the disable lockscreen option selected.
Sent from my SCH-I510 using xda premium
Try rebooting first ...
And if that doesn't work
Then flash the rom over the top....
SENT FROM THE DOG POUND
Crazy stuff man. I found the problem. It was the new miui launcher in the market that was causing the issue even though that wasn't my default launcher. Uninstalled and lockscreen came back.
Sent from my SCH-I510 using xda premium
Apparently Samsung doesn't know how to make a snooze feature as snoozing the alarm will cancel it when it tries to come out of snooze the first time. After Googling it it sounds like other people found out the hard way that snoozing doesn't work.
Imatoasta said:
Apparently Samsung doesn't know how to make a snooze feature as snoozing the alarm will cancel it when it tries to come out of snooze the first time. After Googling it it sounds like other people found out the hard way that snoozing doesn't work.
Click to expand...
Click to collapse
Works for me. Just not a 100% of the time kinda deal as I've noticed. Only failed once so far, and I can't rule out operator error on that one.
Lol. That explains last Wednesday morning.
Sent from my SCH-I535 using Tapatalk 2
I might be having a similar issue. I am terrible at waking up in the morning and I set the snooze limit to 5 times. Most of the time I am not sure if it goes off after I snooze it.
Kinda makes me wonder how long the alarm goes off before it stops.
Sent from my SCH-I535 using xda premium
Stock alarm is terrible, it auto snoozes after 1 minute and there is no way to change it. If you are a heavy sleeper better change it to something else ASAP. I'm using alarm clock extreme and all is taken care of now.
Sent from my SCH-I535 using xda app-developers app
I have had no problem with the stock alarm so far. I have only had it snooze once but that was the auto snooze and it went off again. I don't normally let it snooze though since I have it on the other side of the room and have to get up to turn it off.
I've had issues with every phones stock alarm. Well not the S3.....because I'll never take the chance. I use Gentle Alarm and have never had a single issue. Great app!
Currently not being productive on my S3.
Ive been using Alarm Clock Xtreme(paid) for almost 2 years without a single problem.
I play the piano for a church and overslept the entire morning... lost a whole days pay... crappy.
Sent from my SCH-I535 using xda premium
I've used extreme alarm but I really wish the stock app worked because all of the 3rd party apps are hideous looking and the stock one has all the timer and world clocks integrated into it.
I turn the phone over to snooze and this works.
On another note, when the alarm rings, it gives two choices - swipe one way to cancel the alarm and swipe the other way to snooze.
On my old Droid X, it was swipe to cancel the alarm touch anywhere else to snooze. This worked real well for me. First thing in the morning, I don't want to wake up enough to find the right place to swipe. Turning it over is a good alternative.
Works for me
michael* said:
I turn the phone over to snooze and this works.
On another note, when the alarm rings, it gives two choices - swipe one way to cancel the alarm and swipe the other way to snooze.
On my old Droid X, it was swipe to cancel the alarm touch anywhere else to snooze. This worked real well for me. First thing in the morning, I don't want to wake up enough to find the right place to swipe. Turning it over is a good alternative.
Click to expand...
Click to collapse
You can also press either volume button to snooze it.
I've been using the stock alarm ever since I got the phone, and across multiple ROMs. Never once had it miss an alarm/snooze.
At first it wasn't waking me up because it doesn't run very long before it shuts itself off. Then I set it to auto snooze up to ten times and haven't had any problems. I also use the smart alarm (that I love by the way) which starts 3 minutes before your regular alarm. I also really love the peaceful tones that don't jerk me out of sleep like buzzers and what not.
Yea the stick one has done glitches. The most annoying thing for me is the stupid nature sounds lol . They make me want to sleep more. I transferred the rooster call from my MAXX
Sent from my SCH-I535 using Tapatalk 2
Just turn it off and get up, works perfect for me
Sent from my Who gives a FU€K if it's locked SGS3
I have my phone on the charger across the room, so I have to get up to turn it off. That's usually all I need to get me out of bed.
And I love the default nature melody...
Most of the time tho, my dogs are waking me up wanting to go outside!
jeriel05 said:
Stock alarm is terrible, it auto snoozes after 1 minute and there is no way to change it. If you are a heavy sleeper better change it to something else ASAP. I'm using alarm clock extreme and all is taken care of now.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
I've had issues with alarm clock xtreme. Twice it has failed to go off and it's very laggy when it is going off. I don't do anything funky with it and used the same app for over a year on my HTC thunderbolt
Sent from my SCH-I535 using Tapatalk 2
Gentle alarm user here. Just out of curiosity, is there any way to get S Voice to set the alarm for 3rd party alarm apps?
You can completely change everything on the stock alarm. You can change the snooze duration and everything.
Look harder next time :sly:
Sent from my SCH-I535 using Tapatalk 2
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 :\
I use Sleep as Android as my alarm and have never had an issue until the N5. Every other morning the alarm doesn't sound but the vibrate does work. I'm not sure what to do here. Is the app just not optimized for 4.4 yet?
That could be it. I haven't had too many issues though.
Sent from my Nexus 5 using Tapatalk
Same issue here with Sleep As Android, obviously can't use an alarm that doesn't work. Hopefully, they find what's going on and fix this soon.
After the last OTA update in version 5.1.1 on my SM-G920I I have this problem with Timely Alarm Clock:
Alarm (Timely application) is set at 7:00 am and sometimes does not ring exactly at 8:00 but at 8:04 or 8:07 or something like that.
Exactly the same here. Also after hitting the snooze button the alarm doesn't go off again!
Sent from my SM-G920F using XDA Free mobile app
MAkS1 said:
Exactly the same here. Also after hitting the snooze button the alarm doesn't go off again!
Sent from my SM-G920F using XDA Free mobile app
Click to expand...
Click to collapse
I havent problems with the snooze button, work ok. But the alarm sound 3 or more minutes late, and the snooze too.
I tried restarting and clear cache from recovery.
I tried factory reset, no luck...
Sent from my SM-G920F using XDA Free mobile app
I believe that is the Samsung traditional and cannot be changed, they always late to push updates so as their alarm clock.
MAkS1 said:
Exactly the same here. Also after hitting the snooze button the alarm doesn't go off again!
Sent from my SM-G920F using XDA Free mobile app
Click to expand...
Click to collapse
TheEndHK said:
I believe that is the Samsung traditional and cannot be changed, they always late to push updates so as their alarm clock.
Click to expand...
Click to collapse
The problem is with Timely Alarm clock is not the official samsung alarm.
Qix84 said:
The problem is with Timely Alarm clock is not the official samsung alarm.
Click to expand...
Click to collapse
Indeed, no kidding, this is not my first time to hear it with Samsung phones. It must be also happened in some other models. So it is real a Samsung traditional.
Same problem here. Timely works only sporadically after the latest 5.1.1 update. Very annoying.
Other timed apps such as Tasker periodic time profiles have the same problem.
Anyone found any solution?
I'm in the same boat, and trying out different solutions as days pass by, without much luck so far.
My simple hour chime task became a bloated piece of code with many different triggers, trying to wake-up the device in time for the task at hand.
On the sad side I also checked other apps out (Macrodroid, E-Robot, Automate) but non of them come near the power and ease of use of Tasker.
I really hope that someone can find a solution soon!
Here is the solution to the time-based profile not triggered: http://forum.xda-developers.com/showpost.php?p=62018672&postcount=196.
It's not hard but requires root and build.prop editing by the way.
I am having this same problem in Timely and am not ready to root my phone yet. Has there been any other news about the issue?