Android limitations and restrictions

This topic describes known Android device restrictions and limitations with IBM Traveler.

For limitations and restrictions that apply to all device clients, refer to General limitations.

Android platform

Table 1. Android platform issues

Problem

Details

Dates are not formatted according to user's format selection.

The Java date formatting API may ignore the Android Date & time settings > Select date format setting. As a result, Android platform applications (such as Calendar) may not respond to changes in this setting. Use the Android Language & keyboard settings > Select language setting to select your language and locale. The selected locale is used within IBM Traveler.

Mail

Table 2. Mail issues
Problem Details

Soft reset may cause mail syncing and refresh.

Performing a soft reset of the client device may cause mail to sync with the server and refresh.

Size limitations with inline images and message bodies.

The file size limit for inline images depends on the device's available memory. The limit can range from 1MB for older devices to 10MB for newer devices. Message bodies can be truncated based on device attributes and, regardless of device attributes, can be no larger than 2MB. If a message body or inline image exceeds these limits, a message in the mail body stating that it has reached its maximum size displays.

Limitations with attachments.

Attachments greater than 10MB will not be synced to the device. In addition, mail message bodies greater than 10MB will be truncated.

Mail synchronized to the Drafts folder on the device lose any formatting.

When mail is synchronized to the Drafts folder on the IBM Verse Mobile client, the content is synchronized as plain text. Any rich text formatting within the document is not included. Editing the draft content on the device and/or sending the mail removes any formatting from the mail document. Use IBM Notes, IBM iNotes, or IBM Verse web clients when editing or sending drafts.

Calendar

Table 3. Calendar issues
Problem Details

Limitations with contact names in calendar events.

No actions can be taken on attendee contact names. In addition, available actions on meetings do not include an option to send comments to the meeting chair.

Limitations with searching calendar events.

You cannot search calendar entries.

Privacy information is not displayed.

Information regarding whether an event is public or private is not available.

Event descriptions cannot display rich text.

Event descriptions are currently not sent as HTML formatted strings to the Android client. As a result, event descriptions cannot be displayed in rich text.

Cannot reschedule all instances of a recurring event to a different date.

This feature is unavailable in this release. Use the IBM® Notes® client to perform this action.

Not all instances of a repeating meeting display.

If the user creates an event from the device, the IBM Traveler server truncates the event to either 10 instances if there is a yearly repeat rule, or 250 instances otherwise.

Calendar entries past the year 2067, on both the device and the server, are not synchronized.

Invites are not sent to personal groups.

Because we do not support the synchronization of groups, calendar invites sent to a personal group (one not defined in the Domino® server's address book) are not delivered and are not able to be sent.

Attachments are missing from calendar notices.

Calendar attachments are not yet supported by IBM Traveler Server. As a result, attachments have been removed from calendar notices in the IBM Verse Mail inbox until calendar attachments are fully supported by the server.

Contacts

Table 4. Contacts issues
Problem Details
Limitations with Contacts phone sync For phone numbers to sync correctly to Verse Android Contacts, they must map to supported fields in Domino directory Person documents. For more information, see Field mapping supported for phone numbers in Contacts.
Limitations with Contacts email sync For email addresses to sync to correctly to Verse Android Contacts, they must map to supported fields in Domino directory Person documents. For more information, see Field mapping supported for email addresses in Contacts.

Functions not implemented

Table 5. Functions not implemented
Problem Details

Journal

This will be considered for a future release.