Release Notes of the QtMobility Project release

These Release Notes cover what's new, download and installation instructions and known issues for QtMobility 1.1.0 final release. An up-to-date list of known issues with the release can be found via the Qt Bug Tracker which provides additional information about known issues and tasks related to Qt and the QtMobility Projects. The new Qt APIs are typically supported by backends for each platform. For overall summary of the completeness/compatibility of support for a given API see Platform Compatibility.

What's New in QtMobility 1.1.0

Qt Mobility 1.1.0 final is part of our ongoing program providing new Qt APIs for mobile application development. This release contains a number of new APIs and also improvements and bug fixes since the Qt Mobility 1.0.2 release. For more details, please refer to the online documentation included in this distribution and the change log file.

Downloading and Installing

System Requirements

Qt 4.7.0 should be used.

http://qt.nokia.com/downloads

Latest QtMobility packages can be found here:

Please follow the installation procedure.

Known issues with this final package:

Camera

• Maemo5: Unable to save images other than in default resolution.

Landmarks

• Maemo5: Unable to write data/export to /opt

Organizer

• There is no QML example for organizer

Document Gallery

• - The document gallery backend for Symbian S60 is disabled in pre-built packages due to limited deployment of a dependent library on 3.1 and 3.2 devices, and library version conflict between 5.0 devices.
• - Document gallery items of type Album, Artist, AlbumArtist, and Genre cannot be queried on Symbian platforms.
• - Symbian: mediabrowser example application does not display items in panels other than Songs.
• - Symbian: documentproperties example application not usable, crashes on exit.

Maps and Navigation

• At the time of the Qt Mobility 1.1.0 release the QML support for the Maps and Navigation API is incomplete and will be improved in the next patch release. Therefore the QML API will be subject to potentially incompatible changes.

Feedback

• - Not all vibration settings may result in distinct vibration patterns due to limitations in individual vibration actuators.
• - Feedback example applications are not functioning on S60.
• - Maemo5: Hapticsquare and hapticsplayer example applications have no haptic feedback.

Messaging

• Maemo5: keepintouch example application displays a list of same contacts and emails.