May 16, 2009
With the launch of the BlackBerry and Mobihand App Stores, this release is focussed on meeting the App Store requirements imposed by Research In Motion.
There are also some improvements to the add mailbox wizard, including a test phase once the mailbox has been specified. tiggit now has an update facility that allows you to automatically check for new released of tiggit mail. (RIM make a charge of hundreds of dollars to list an application on the App Store, and make a charge for each update!)
This version also makes a better attempt at decoding and displaying partially downloaded messages – reducing the number of messages that need to be more-ed before they can be read.
Here are the details of the changes in this release
- connections are tested at the end of the add mailbox wizard
- data useage warning message as required by RIM
- improved feedback when folder sync fails
- automatic update utility
- fixes incorrect trial license expiry information on license panel
- modest performance improvements when opening messages
- fixes problems with WiFi connections when using service book defined cellular connections
- improved handling of worker thread exits
- sets default character set for MIME decoder
- adds show deleted option, allowing users to see messages that have not been EXPUNGED
- step-back-delete download functionality
- fixes problems with dropCopy
- resolves reliability problems with IMAP APPEND
- fixes problem with incorrect message size display for small messages
Testing this release I have noticed that attention should be paid to blockSize and waitTime. It is suggested that waitTime should not be set below 250, whereas the default settings with release 12 was 100.
Registered users can download version 1.1.14, 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. Users are advised to fully remove the previous version of tiggit mail prior to upgrading to ensure a trouble-free installation.
Here are the build numbers for the various versions
1.1.14.d2 4.2 build 12436
1.1.14.d2 4.3 build 12435
1.1.14.p4 4.6 build 12505
November 21, 2008
I have just finished implementing the seamless-wifi code within version 1.1, but have come across a little problem. The BlackBerry simulators, although providing WiFi functionality do not simulate actual WiFi connections: i.e. it is possible to simulate the absence/presence of a wifi network, but it is not possible to route any data connections over the wifi connection.
I can test the presence/absence of the connection and confirm that the parameters are being passed to the the network objects correctly, but I cannot be certain that the wifi switching is happening as intended. This is an important test, especially for the tunnel – as tunnel connections should switch mid-session between wifi and cellular – i.e. if you are part way through a download on a cellular connection and the wifi connection becomes available, tiggit should switch to the wifi connection for the remainder of the download. This should make things faster and reduce data costs.
I wonder if anyone is prepared to take a pre-release of version 1.1 to work with me to confirm the wifi switching is actually working.
June 13, 2008
For many BlackBerry users the amount of data that is consumed by an application is not an issue, mostly because they have unlimited data plans with their BlackBerry tariff. However there are a growing community of BlackBerry users that do not have an unlimited data plan, and use applications such as tiggit mail to access their email.
The advent of WiFi capabilities within the BlackBerry handheld means that these users would very much prefer to use the much cheaper bandwidth that is available by WiFi to access their email. For them, it is highly desirable for BlackBerry to be able to seamlessly switch between the mobile phone network and WiFi depending on what is available, and making the switch while sessions remain active and with no apparent loss of service.
The BlackBerry API 4.3 documents a very useful class to implement this kind of functionality WAPInfo. This object provides programmatic access to WiFi hardware within the BlackBerry device and provides information such as the SSID of the network that is in use as well as things like signal strength and whether there is an available internet connection.
Further investigation however reveals that most of the devices that have WiFi hardware have an OS built on 4.2 or 4.2.1 of the API, which renders these functions particularly useless. Explaining to a typical BlackBerry user that they need to upgrade the operating system has enough scary words in it that it is highly unlikely they will make the step.
Further and slightly more difficult is the lack of simulators with version 4.3 API and WiFi hardware.
In the meantime it looks like I am going to have to implement a really goofy test to attempt to open a connection via WiFi and if this fails then switch to mobile network. Far from smooth and definitely won’t be seamless. Ho hum.