Ken, thanks for your input. I will consider this in the next releases. Probably the application usage gets broader then.

Do you have a specific demand? What do you plan to do with it?

Could you add an option to execute an arbitrary script as the action, rather than placing a phone call?

Cool app. Some comments/feedback:

• The UI is very cool - the "Audio Level" and "Treshold Counter" graphs show the user what's going on and how sensitive the app is set up at the moment
• Wouldn't it make more sense to flip the color of the bottom button (green as in "ready to start" for inactive and red for "if you press now, the running task will be stopped")

Some feature requests that I didn't see on the website yet:

• Add a record-only mode (without calling) - also good for brainstorming in a silent room
• Add the website URL (at least the URL or even better: a button) to the about dialog
• Add the version number and a button to open the bug tracker to the about dialog
• In the settings dialog: Make the check button span the whole width, and place the "Reject Incoming Phone Calls" inside the button
• Allow Skype / GTalk contacts to be entered into the "Parent's Phone Number" field (maybe this can be solved with the contact list selector)

I'm not sure what "Audio Time Influence" means (from the text alone) - maybe you can clarify this in a help button on the settings dialog (maybe adding the "Adjusting the Settings" part of the website to a HTML view in the app would be enough).

As all these items are only wishlist items, and the app fulfills all other QA criteria, +1 from me.

Ian, thanks for your valuable feedback!

Concerning warning on battery usage: I added a hint on the project's website. Not sure whether to bother the user within the application? Maybe some hint in an about dialog or the settings?

Concerning UI stopping: I already planned to add a similar feature to stop the graphs once the application is active. I think the normal usage is to setup the amplitudes, then activate it without the need afterwards to see the graphs anymore. But I think it is an even better idea to add this option for blanked screen, as you suggest.

As this is likely to be left 'idle' for long periods of time, it would be a good idea to inform the user that it will run the battery flat in about 10-12 hours, as the device isn't very 'idle' in this state, though the screen may be locked.

On another note - perhaps 20% of the battery use could be eliminated if the UI stopped updating when the screen was blanked. Top says - with screen blanked -

PID PPID USER STAT RSS %MEM %CPU COMMAND

799 1 pulse S < 5376 2.1 24.9 /usr/bin/pulseaudio --system --high-pri

847 692 root S < 14968 6.0 14.1 /usr/bin/Xorg -logfile /tmp/Xorg.0.log

4201 1144 user S 19552 7.9 13.9 /usr/bin/babyphone