chicostate / smart-nap Goto Github PK

This crash is caused because of a NULL exception error. The current list is attempting to return an ArrayList of Long but the list is size 0. Flash card ID's are properly being passed from fcpop to AlarmEdit activity, but there is no storage of the card ID's to the AlarmClock when saving it.

They should be able to be stored, retrieved, and modified from our database.

Currently there is an onTouchListener setup on the AlarmEdit page which waits for user to edit the alarm name field. If it is the first time editing it, the field is cleared and waits for input. However, the issue arises here with getting the keyboard to move away from the screen following input.

Ideally, to make this intuitive, after the user is done with input, it should remove the keyboard from the screen. In addition, as it does already, it is important that the field does continually erase itself if the user attempts to make edits.

Currently alarm ringtone continues to play. Desired behavior is to start a 3 minute timer upon the last interaction from the user in which the alarm tone is silent. However, if 3 minutes has passed and there is no further user interaction, while the alarms condition of being satisfied is not met, then the alarm tone should resume playing.

If you make an alarm right now, the homepage textclock does not update with the alarm time. Right now, the home text clock is just displaying the current time. We need it to display the information reflecting the current alarm that the user sets. If we keep the toggle-bar, then we would want that bar to automatically switch to ON also once the alarm is set.

If you set an alarm for a specified time, then that time happens while app is closed or phone is in 'sleep' mode, notification fails to be received until app is reopened. While not a bug per se, it is definitely an issue to address due to the very nature of what an alarm needs to be.

Alarm currently does NOT activate or play any sound notification upon actual time of alarm happening. As addressed in Issue #2, notification to user happens almost immediately after creation of alarm, so perhaps alarm is not being created properly.

UPDATE: The alarm now waits for an appropriate time as outlined in Issue #2.

On current Home the alarm clocks displayed have a toggle button with the intended use being to control the active state of the alarm. Currently the buttons do nothing, and this functionality is not implemented.

Implement on/off control of saved alarm clocks by setting functionality on the toggle switch for each alarm listed.

Further implement this control by adding the toggle switch to the AlarmEdit activity as well

When creating a new alarm, the notification to a users device happens almost immediately upon creation of the alarm. Instead, it should be waiting to send notification upon the actual alarm event taking place at the specified time. I am unsure as to whether or not this issue is related to the alarm not properly being created, or if it is an issue with the AlarmReceiver or AlarmService.

This issue is an extension of Issue #3 which has been fixed. The alarm dialog pops up and plays a ringtone as a sound, but does not play if the volume is silenced on phone. This should be fixed to play the sound regardless of whether the phone is muted or not. Think about an alarm clock to wake you up, but you silence your phone overnight, and the alarm sound doesn't play. This is how the dialog currently acts, but is not desired.