hollorol/Clockplus
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Added todo

Browse Source
This commit is contained in:
Phillip Hsu 2016-09-10 02:36:37 -07:00
parent bf381a05f1
commit 02fbee2f7b
1 changed files with 7 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
app/src/main/java/com/philliphsu/clock2/timers/TimerNotificationService.java
View File

@ -66,6 +66,13 @@ public class TimerNotificationService extends Service {
context.getSystemService(Context.NOTIFICATION_SERVICE); context.getSystemService(Context.NOTIFICATION_SERVICE);
nm.cancel(TAG, (int) timerId); nm.cancel(TAG, (int) timerId);
context.stopService(new Intent(context, TimerNotificationService.class)); context.stopService(new Intent(context, TimerNotificationService.class));
// After being cancelled due to time being up, sometimes the active timer notification posts again
// with a static 00:00 text, along with the Time's up notification. My theory is
// our thread has enough leeway to sneak in a final call to post the notification before it
// is actually quit().
// TODO: Write an API in MyHandlerThread that removes its messages. Then, write and
// handle a service command that calls that API. Alternatively, we may not need the
// command because we could just call that API in your quitThread() helper method.
} }
@Override @Override