A long under-utilized feature of the Windows Mobile client is the ability to customize the interface through additional skins. Signal user lampwik decided to make use of this feature, creating his own custom skin to share with other users and finding another on the xda-developers forum:
DarkCarbon by lampwik
MM-Signal by MaxMotus
Enjoy!
Signal 1.2.4 is a bug fix release for Windows users, resolving a potential speaker selection issue and fixing a networking bug that could occur on XP systems with IPv6 enabled. The Windows Mobile client has also been updated as a result of the networking change, just in case there were any devices impacted by this fix. The update is available now on the download page and via software update.
Signal 1.2.3 is now available for Windows users, fixing a bug that could cause a 404 error to be seen in the web interface. The problem did not exist in the Mac version, so for Mac users the current version remains 1.2.2.
Hot on the heels of the last update comes version 1.2.2, a Mac-only release that enables System Preferences on Snow Leopard to load the 64-bit version of the preference pane. With this update you’ll no longer need to relaunch System Preferences in 32-bit mode in order to access Signal, which was annoying. Grab it via software update or on the download page.
Signal 1.2.1 is now available, resolving a potential hang issue with the web interface, a bug preventing folder-based album art from being displayed, and some Unicode compatibility issues for Windows users.
Due to a bone-headed move on my part Windows Mobile users will need to install the updated client through the web access URL or ActiveSync after upgrading to 1.2.1. The 1.2 client has a bug that prevents the automatic update from working on Windows Mobile 5 and later. The worst part is that I specifically tested to make sure over-the-air upgrades were working before shipping 1.2…but on a Windows Mobile 2003 device where the bug does not occur. My sincere apologies for the inconvenience, really kicking myself for letting this one slip through.
The web interface hang issue was a rare but long-standing bug where you’d sometimes see the browser pause for a few seconds before loading the page. The problem was caused by a remote device going to sleep without signaling that it had closed its network connections, then being woken up it up before Signal detected the connection loss itself. When the device came back online the server would try to send information to the inactive connection, delaying the real messages that should have been to the device. Signal now transmits all pending messages at once and sorts out the connection state in the background so nothing is held up.
1.2.1 is available now via the download page and software update.