Loudtalks for Windows and Windows Mobile

By Alexey Gavrilov on January 26, 2009

Changes list

Windows build:

  1. Fixed error with contacts authorization
  2. Fixed links not working in autoupdate notification dialog
  3. Updated French localization (thanks, Jean Marie!)
  4. Fixed visual artefacts, when running under WINE on Linux
  5. Improved logon performance (p2p core)

The update will be delivered automatically to all existing users.

Windows Mobile build:

  1. Added Options… dialog where you can a) Select UI language, b) Configure sound notifications, c) Configure connection settings (if required)
  2. Improved “joystick” navigation — central button will now work as PTT, and Left-Right to access messages history. Now you can use Loudtalks with hard keys only.
  3. Turn on compression in .CAB file, which greatly reduced its size

Update procedure is manual. Please download and install the latest version from the links below:

Option 1: Installer for the desktop (via ActiveSync)

Option 2: Installer for the device (.cab)

We have more announcements to make later today so stay tuned!

Comments (3)

  1. About those visual artifacts on Wine…
    was that a Wine bug? If so, let us know
    about it by filing a bug at

    Also, if you add wine to the list of
    supported platforms, we can add a link to
    your app in http://wiki.winehq.org/AppsThatSupportWine

    Comment by Dan Kegel — January 27, 2009 @ 4:16 pm

  2. I’m definately loving using this for windows mobile! One question though, is it possible to have it wake up my device if a new message is sent? Right now when my device goes into standby mode, I won’t get any notification of a new message.

    Comment by John — January 29, 2009 @ 9:29 pm

  3. We had a problem with this build, which cased the failed installation on Windows Mobile 2003 devices (they don’t support compressed CAB, which we used for packaging). The setup files are updated now and will install of WM2003.

    Comment by Alexey Gavrilov — January 30, 2009 @ 6:27 pm

RSS feed for comments on this post.

Sorry, the comment form is closed at this time.