Handango is pretty close to 15,000 downloads of WolfClock -- much more popular than I imagined. Now if I only made $1 for every download :)
The feedback I've gotten has been great. There's been one persistent bug that I cannot get ironed out, mainly because it's partly an OS issue: an alarm
may not wake the device up when it's time to sound.
This problem is not native to WolfClock; rather, it seems native to the PPC 2003 OS. I experienced this problem on my device (an IPaq 2215), but have a workaround that has worked on every device (to my knowledge, at least) except the O2 XDA.
Unfortunately, I do not have an O2 device for testing, so I've continued to try different hacks to make the application wake the device properly. To make matters more complicated, the Compact Framework is a bit limited so, from a high level point of view, there isn't much that can be done except P/Invoking native calls.
In fact, that's what the current version does, and has for some time (probably since the version 1.0 days). To see if it makes any difference, I've changed the device wake-up code to a completely unmanaged C++ executable. This will help isolate whether the problem lies in the .NET framework or with the device itself. Included in the install is PowerUp.exe; when WolfClock registers itself with OS to launch at a specific time, this executable is also registered.
To download this beta, click here:
WolfClockSetup-v31b4.exe (1.5 MB)
Feel free to post feedback here on whether or not this version makes any difference, as well as sugestions for future revisions.
Note: This version also enables Debug Mode by default, writing events/errors to a log.xml file located in the installation folder. This file may contain useful information, so include it if possible.
** UPDATE **
Oops! I goofed on the the latest build. I had been tweaking the application for Microsoft "Compliance" and in doing so, broke one of the alarm pages. The latest is beta 3, and is available above!
Subscribe