1.1.18 now released

January 30, 2010

Version 1.1.18 of tiggit mail is now released on tiggit.com, Mobihand and affiliates and BlackBerry App World.

Here is the full list of enhancements and bug fixes

  • Remove artificial limit on mailbox names
  • Add option to set font size on status bar
  • Fixes user difficulties with marking messages as read
  • Adds ability to see attachment file names in composer
  • Adds ability to handle address book groups
  • Adds thumbnails preview for file chooser
  • Adds Internal sent items folder
  • Adds Sent box
  • Connection Failure Notification – warning messages are added to INBOX in the event of connection failure.
  • Ability to edit reply/forward original messages (not HTML messages).
  • Improve original message format when replying ”On MM/DD/YYYY at MM:HH:SS you wrote:”
  • Fixes problem where Reply all doesn’t work
  • Fixes problem where signature is added to a reply message even when replySignature is not selected and text is not added to the composer
  • Adds active hours functionality – tiggit mail does not check mail outside active hours
  • Fixes problem where LED flashes even though it is not selected
  • Fixes problem where LED does not get cancelled when tiggit exits
  • Fixes problem where Replying to a message causes a .txt attachment on Exchange server
  • Adds ability to interrupt send/receive
  • Fixes problem where Leading slash is missing in file name for attachments
  • Adds automatic population of  SMTP fields in wizard
  • Fixes problem where autoload fails over time
  • Fixes problem where adding a BCC field causes corruption of existing message text
  • Fixes problem where settings edit panels requesting unnecessary confirmation
  • Fixes problem where folder names with spaces cause failure when moving messages
  • Fixes problem with file names that stops tiggit mail working with FaceBook mobile
  • Improves users feedback when downloading folder list – shows session errors to user, and stops on an authentication error
  • Fixes problem where Auto startup hangs on welcome screen
  • Fixes problem where sort order does not work for sent time
  • Improves handling for  AKO ALERT messages
  • Fixes problem where start on boot causes phantom process called multiMail to exist
  • Fixes problem where LED does not cancel properly on STORM-2 & Bold
  • Fixes problem causing STORM and STORM device crash
  • Fixes problem where Network presence is not properly detected on start-up
  • Fixes problem where Non-ascii characters are not properly encoded in subject line – especially Euro symbol
  • Fixes problem where non-ascii characters in messages that are saved in the out box prior to sending – tested with German extended characters
  • Fixes problem where address book look up causes reply-to address to be added repeated
  • Adds ability to toggle Thumbnails in file chooser
  • Fixes New Folder Button
  • Adds special WiFi handling on configurator
  • Fixes problem where update does not work via when tunnel is selected

Existing users of tiggit mail can upgrade to 1.1.18 by selecting Update from the Settings menu. Alternatively this latest version can be downloaded from here.



    network access problem with 1.1.18 preview 3

    January 11, 2010

    Tiggit has a problem initiating network access information, and as a result fails to connect to mail servers. When tiggit attempts to download mail you will see a stream of messages at the bottom of the screen flashing by, but no connection will be made.

    To work around this problem, Go to Manage Connections and turn off the cellular connection and then turn it on again. Tiggit mail will now recognise your cellular connection properly.

    This problem will be fixed in the next preview.


    Reply-all problem fixed in preview 3

    January 10, 2010

    Preview 3 of 1.1.18 is now ready for download. This preview includes the long awaited fix for the reply-all problem (tiggit mail not responding to the reply all menu item). This build also rationalises some of the difficulties with the new connections API from RIM and difficulties with WiFi connections. It also makes IMAP sessions more reliable when using online Sent and Draft folders.

    One great feature of 1.1.18 is its new resilience to dropping cellular connections. This afternoon I was on a train and tiggit managed the dropping cellular connection as we travelled, including going through tunnels. I have also tested sending a message whilst on the tube, and confirming that tiggit automatically send the message once it recovered signal, having left the tube station.

    Here is the full list of changes

    • network string “blank” value now only applies to cellular connections
    • tiggit now autoselects properly between cellular and wifi connections, favouring wifi over cellular, and reports availability of networks on status line
    • no longer uses deviceside=false for MDS connections
    • only applies service book details to cellular connections
    • improved network availability checking
    • fixed problem with default character set
    • fixed problem where reply-all menu item does not work
    • improved IMAP session handling for sent folders
    • adds double click action to file chooser when attaching files to messages

    This is a preview release and may contain a number of un-expected defects, and is being released at this time for customer feedback.This is a preview release and may contain a number of un-expected defects, and is being released at this time for customer feedback.

    Registered users can download version 1.1.18, by clicking here and entering the email address that was originally used to register for tiggit mail. Exisiting license tokens will continue to work with this version. Users are advised to take appropriate precautions when upgrading to this version as all messages on the handheld may be lost.

    Build numbers: 4.6 api – 14534, 4.3 api – 14533, 4.2 api – 14532


    Preview 2 of 1.1.18 now available for download

    January 6, 2010

    Preview 2 is now available for download. This fixes up some little bugs in preview 1 and adds the following fixes/features

    • Fixes IMAP protocol handling problems, including U of T implementation.
    • Reverts fix for IMAP protocol handling problem NO No messages have been stored
    • fixes problem with incorrect sort order, when sorted by sent date, or receive time
    • improved draft box and sent box dual line field layout, including correct display of K and M as appropriate

    This is a preview release and may contain a number of un-expected defects, and is being released at this time for customer feedback.This is a preview release and may contain a number of un-expected defects, and is being released at this time for customer feedback.

    Registered users can download version 1.1.18, by clicking here and entering the email address that was originally used to register for tiggit mail. Exisiting license tokens will continue to work with this version. Users are advised to take appropriate precautions when upgrading to this version as all messages on the handheld may be lost.


    Storm and Storm-2 crash problem resolved

    January 6, 2010

    This is worthy of a post on its own: Tiggit mail, under certain configurations, causes the Storm and the Storm 2 to crash for no apparent reason. When the Storm is configured to use direct soscket connections – no tunnel – it would crash within about an hour of starting. This is obviously not really workable, however tiggit was rock solid on a Storm with tunnel selected, so I guess this was a good enough work around.

    I had not been able to isolate this problem as I had to use my Storm (it is configured for BES) with the tunnel, and so it really was like looking for a needle in a haystack. Recently I bought a Storm-2 to resolve problems with Tiggit Controller on Storm-2, these still remain un-fixed, but tiggit mail crashed my Storm 2, which at least gave me the ability to isolate the problem.

    The problem was to do with the re-use of timers, and in particular the autoload timer. There is an immediate work-around for those using 1.1.17 and before:

    set sendReceive Period to zero

    This will stop the autoload timer being initiated which is what causes the problem – the same timer being initiated twice (don’t ask why).

    More adventurous people might care to try preview 2 of 1.1.18 which contains this fix.


    Follow

    Get every new post delivered to your Inbox.

    Join 30 other followers