The one feature this app is missing is to have alarm settings for each day. I don't have a m-f, 8-5 job where I have to wake up the same time every day. This would be a sweet addition to this app.
The one feature this app is missing is to have alarm settings for each day. I don't have a m-f, 8-5 job where I have to wake up the same time every day. This would be a sweet addition to this app.
This is on our list of things to do. It is highly requested, so it will probably be one of the next features we work on.
Odd it should have still read your news and weather on the old versions...
Not sure what happened then, I just thought that the update messed up the settings. It just greeted me good morning. Things worked fine as the updated state this morning.
Updated and I now receive popup "The Wakeful application requires Bluetooth to be enabled. Enable Bluetooth? Yes or No" if I choose Turn Off or Snooze.
Ok, that's really wierd. I know we added some code to turn Bluetooth on and off when the alarm plays, because a lot of our users were complaining about it coming out of their bluetooth headsets.
I got that message also when I updated. I turned bluetooth on, even thought I don't use bluetooth, and then I turned it off after one day. Everything still seems to work with BT turned off. I only got that message when I first installed the update. It's never appeared since.
Hey guys,
As a side note, you would be surprised at how many apps you have on your device that have BT enabled.
I went through my list of 3rd party apps and open each "edit permission" window and I had at least five that showed BT enabled.
None of these apps requires any BT connection.
So I tested it it wrkd the first time, no popup. Then I tested it agn and the alarm didn't go off. Also I can't seem to get the app to close it keeps running even after I close it. Log sent
Ok here's the final analysis : once the alarm is set the log is opened and stays open till the alarm goes off. Also u cannot cancel the alarm once its been set. Even after setting it to never it will still go off at the time it was originally set for. But the original issue with the bluetooth has been solved LOL
Posted from my CrackBerry at wapforums.crackberry.com
I think I'm going to pass on this one. The only issue I have is that I have to answer "no" to the blue tooth notification every morning after the alarm goes off. It's such a minor thing I don't even think about it any more.
Wow. I've had my complaints about price drops, new updates and new update frequency, but the core functionality has always worked for me from the beginning. V1.1.6.1 works great for me as the early builds did. I have not had any of these problems whatsoever. I wish the rest of you did not either. Glad they are looking into it for you.
**One pet peeve though... They have taken out the ads at the end of the talking alarm and replaced it with the name of the user. Great! The only thing that bothers me is that the name is a bit too close to the end of the sentence. Ex: It sounds like there is no pause after the sentence.. Instead of saying "Have a great day, Brad", it sounds like "Have a great dayBrad".
Maybe a few milliseconds of a pause added between the last sentence and the name at the server level would sound better.
I'm running this app for about a month or more and never had any problem and always was accurate until this morning @9AM alarm went on and it says 6:45 AM when actual time was 9AM, is anybody got this wrong time also ?
**One pet peeve though... They have taken out the ads at the end of the talking alarm and replaced it with the name of the user. Great! The only thing that bothers me is that the name is a bit too close to the end of the sentence. Ex: It sounds like there is no pause after the sentence.. Instead of saying "Have a great day, Brad", it sounds like "Have a great dayBrad".
Made some changes on the server. Let me know if this helps at all.
I'm running this app for about a month or more and never had any problem and always was accurate until this morning @9AM alarm went on and it says 6:45 AM when actual time was 9AM, is anybody got this wrong time also ?