Seamless WiFi

September 30, 2008

As a previous comment, Amy writes

I recall earlier this year a Tiggit rep telling me you would soon support Wi-Fi/GPRS download without having to make that change in the program. I.e., meaning that if a Wi-Fi network were available, it would be possible to have Tiggit choose that first for send/receive, and if Wi-Fi is not available, then GPRS would be the default for send/receive.

This is an important piece of functionality, so I thought I would take few minutes to explain where I am with this.

Firstly I have changed my approach to releases recently. Originally each new release added functionality and fixed bugs that had been reported. The releases came every couple of weeks, and because the test time was very short, adding new functionality broke things, and so bugs needed to be fixed, and so on. For the last few 1.0 versions there has been no new functionality, just fixes to bugs. This is with the view that the 1.0 functionality will stabilize and allow me to focus on the next (1.1) version. In reality there has been a lot to fix up.

There is now a code branch that is 1.1 and this is where the new functionality is going. This will include the new features that many people have been asking for including seamless wifi and an indicator showing which mailbox has new messages. This along with better IMAP support including the ability to nominate sent and trash folders as well as using the IMAP outbox as a send mechanism.

Seamless WiFi is important, not only because it is a hassle for users to switch between GPRS/EDGE/3G and WiFi, but also because tiggit mail can do it so well. When working via the tunnel, tiggit mail uses a connection-less http session to communicate with the tunnel server. This session can be switched between various networks seamlessly and from one request to another. Compare this to a socket connection that is established over one transport, and needs to be torn down, re-established and authenticated to switch transports. Although this is feasible, it is complex and has a significant overhead.

So, version 1.1 will have dynamic WiFi GPRS switching and hopefully will be out before Christmas. In the near future I anticipate making early versions of 1.1 available to those that want to try it out, whilst continuing to support 1.0 for the less adventurous.


version 1.0.06

September 12, 2008

Version 1.0.06 now released with the following updates

  • fixes bug where reply to field is not respected when replying to a message
  • provides additional user feedback when decoder thread exits unexpectedly
  • adds code to render messages that are not encoded
  • fixes bug in IDLE handler where DONE is not sent after receiving and EXPUNGE notification
  • fixes exception when attempting to follow a link in the message to an illegal phone number

version 1.0.05 released

September 8, 2008

As part of a change of release approach – I am now releasing new versions much more rapidly, with each version targetted on one or two customer reported problems – version 1.0.05 is now available for download.

This version

  • fixes problem with sent messages being reported as failed in the outbox
  • built against API 4.6 and should be suitable for BlackBerry 9000 – Bold
  • changes network configurator to try useMDS first making MDS routing the default
  • makes singlePost not selected by default
  • makes smtp server settings dynamic – i.e. no need to restart after changing an smtp server setting
  • provides user feedback is disk logging is unavailable for some reason.

I am very interested to hear how well this works on a BlackBerry Bold. I expect some problems on earlier versions of tiggit mail as RIM have added a method to the Field class setBackground(). In tiggit mail I have an extension of RichTextField that I use for rendering the display that has a method setBackground() and although the methods in these two classes do different things, and also because setBackground() is protected in Field I would anticipate some trouble.

Anyhow, this has been fixed in 1.0.05 so tiggit is now built on API 4.6 and should run nicely on a Bold.

tiggit on BlackBerry 9000 – Bold

September 6, 2008

Just working through some of the issues building tiggit on the new 4.6 API to support BlackBerry Bold. The new BlackBerry user interface looks very smart, and tiggit mail appears to fit right in. Here are some screen shots of tiggit running on Bold.

version 1.0.04 released

September 5, 2008

Version 1.0.04 has been released. This version provides a fix for POP3 users experiencing -ERR message not found problem.

7000 install problems

August 21, 2008

version 1.0.01 does not appear to install properly on 7000 series devices.

version 1.0.02, now available should install on 7000 series via over-the-air install, and via the web-installer. I have tested the install on a 7290 using the web-installer.

pop3 not bothering to download

August 15, 2008

Users have reported a problem with POP3, where tiggit apparently connects correctly to the POP3 server, but does not actually download any messages.

This is caused by the INBOX folder not being marked for download. 

To workaround this problem users can change the mailbox type to IMAP, go to the Folders panel, set the INBOX folder to “include when receiving mail”, then change the mailbox type back to POP3.

Step by step instructions follow

1. Go to the settings panel and select the settings for the mailbox that is giving problems

2. Change mailServerType from POP3 to IMAP

3. Save the settings.

4. Exit & restart tiggit mail.

5. Open the mailbox and select folders from the menu.

6. Move the highlight to INBOX and then select properties from the menu.

7. Make sure that “include when receiving mail” is selected, and click on OK.

8. Go back to the settings panel and change the mailServerType from IMAP to POP3

9. Save the settings, exit and restart tiggit mail.

10. Perform a ‘receive’ to download mail into the POP3 mailbox.