Tick! A convenient timer!

Hi everybody !

After a year of lurking, i've published my first app !
It's called Tick! and it's a simple timer but i've worked hard on making it easy to launch.

Since there is no wheel selector on the sdk, I've developed one to set the number of minutes wanted. With three clicks, you can launch a timer to remaind you that your pastas or your eggs are ready !

Your comments are welcome !
Since I'm new on the forum, I'm currently not allowed to post external links, so if you want to try it, search for Tick! on the market or SlideMe. I will put images, links and QR-Code as soon as i will be allowed !

RabugenTom

Thanks for the replies ! I've added the apk posted on the market.

I'm working on an improved version !

Thanks for the feedbacks !
I'm working on an improved version with pause mode, multiple timers and 30s increments. I will maybe release the source later, after a lot of cleaning !

For the notifications, it's the behavior of android which works by intents. Theses are sort of messages send to applications. Intents depends on something they call Context. This is very powerful since you can launch (or do whatever you want to) an application in different ways, and the behavior of the application can depend on the intent. For example, when you launch an application from the launcher on the home screen, you actually send an intent to the application.

In the Tick! case, when you click on the notification, you send an intent to bring back to foreground (if hidden) or relaunch (if closed) the application GUI (which is different from the counting "engine" which is a background process called Service). The intent sent from the notification is different from the one you used to launch it, thats why it relaunch the GUI because the system thinks it is a different context (which is the case).

You can try it : launch from the launcher, launch a timer, go back to the home screen. Now, the GUI is no more in foreground. If you open the notification bar an click on the notification it will relaunch the GUI as expected, and if you continue to click on it again, it will do nothing (as expected). That's because the second time you launched the app, you did it by sending an intent from the notificiation bar, which is different from the one from the launcher.

Now, i don't find this behavior very annoying, and I don't want to write 100 lines of code to handle differents cases! A trivial solution may exist, but I'm too novice with Android to look at it. If someone knows this easy solution, it will be a pleasure to implement it !

Hi,

1-I will look on the notification problem. It is quite strange since it always worked for me. Note that the parameter are set for the notification at the launch of the counter. Every change you make will affect only new countdowns. When you exit the app, it always save the last parameters, even made during a countdown, and restore them at a relaunch. So it is strange, and since i've improved again the counting engine, I hope this will be solved in the coming release.

2-You're right, I've found conditions when the wake-lock is not released at the end of the countdown. It's set now. However, the wake-lock requested is partial and does only concern the CPU, not the screen. I've tested again your version on my unplugged G2 and it behave just well.

The CPU is required to fire an alarm even in sleep mode. Thats because i don't use the alarm service of the device which only check every new minute if there is something to do.

And when it's in sleep mode, only a tiny service is counting. The GUI is stopped and it's memory given back.


May I ask what model of phone you use?

I've just added here (and on the market) the version 1.3 which resolves a lot of issues (for exemple, the service exits as soon as it's no more used, thanks to bugmenever) and adds a pause mode (long click on the button)