Android limitations and restrictions: LNT8521  |
This topic describes known Android device restrictions and limitations with IBM® Lotus Notes® Traveler. |
This topic describes known Android device restrictions and limitations with IBM® Lotus Notes® Traveler.
Android platform
Table 1. Android platform issues
|
|
|
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 Lotus Notes Traveler.
|
Application icons are incorrect and non-functional. Clicking on one of the incorrect icons displays the error, "The Linked program is no longer installed on your phone".
|
On some devices, upgrading from a previous beta version of the client can cause the application icons to be incorrect and non functional. This is a known issue with these devices. To resolve the issue, uninstall the previous version of the application, then install its most recent version.
|
The Lotus Notes Traveler application appears in the wrong location under Manage Applications.
|
In the Menu > Settings > Applications > Manage Applications menu, the Lotus Notes Traveler application may be sorted under 'C'. This appears to be temporary. Pressing back and returning to Manage Applications restores the proper sort order.
|
Install
Table 2. Install issues
|
|
|
A mobile device user cannot complete registration if the user home mail server is down.
|
During the registration of a mobile device with Lotus Notes Traveler, the Lotus Notes® Traveler server reads the user home mail server and mail path name from the Domino® directory. It then attempts to contact this mail server to determine if there are any replica mail databases configured for the user. If this home mail server is down during the registration attempt, registration may fail until this server is brought back online or the home mail server entry for this user is changed to a different mail server in the Domino directory.
Once registration is complete and the Lotus Notes Traveler server learns the locations of the mail replicas, then Lotus Notes Traveler can redirect push and sync operations to other replicas if the home server is down.
|
Uninstall
Table 3. Uninstall issues
|
|
|
After uninstalling Lotus Notes Traveler from the device, some unusable data is left on the SDcard.
|
For Android 2.2, the directory on the SDcard used by Lotus Notes Traveler to store data is specified by the Android OS, and is supposed to be deleted by the OS when the application is uninstalled. On some devices, this data may be left on the SDcard after uninstall. The data that remains on the SDcard is encrypted and inaccessible since the key is removed during the uninstallation. As a result, the data can safely be deleted by the user if they need to regain space on the card.
|
Password policy could be modified after uninstall.
|
For Android 2.2, the length of the password you are required to set may be affected by enabling and disabling the Lotus Notes Traveler device administrator. Some devices may continue to require a long password even after the device administrator is disabled.
|
Contacts
Table 4. Contacts issues
|
|
|
Personal groups do not synchronize to the device contacts application.
|
The contacts application does not support synchronization of groups.
|
Mail
Table 5. Mail issues
|
|
|
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.
|
The trash folder is not synchronized.
|
The Trash folder in Lotus® Domino is a view and not a real folder. Therefore when monitoring folder activity, Lotus Notes Traveler does not receive notifications related to the Trash folder.
|
Limitations with inline images and email body file size.
|
Inline Images greater than 500kb will not be synchronized to the device. In addition, email bodies greater than 500kb will be truncated.
|
Execution Security Alert popup when opening a mail folder using a Notes client.
|
If you create a mail folder on a mobile device that supports mail folder operations using the Lotus Notes Traveler client, the folder will be created in your mail database using the Lotus Traveler server. Since folders are design elements and must be digitally signed, the folder will have the signature of the Lotus Notes Traveler server that created it. By default, your Notes client will warn you when it detects a signature it has not seen before and will ask permission to allow the action requested by the folder. If you see this warning, select Start trusting the signer to execute this action so that you will not see this prompt again for this action.
|
| Mail documents only appear in one folder. | The Lotus Notes Client allows a single mail document to be in multiple folders or views, but the mail application on the device only allows a single mail document in a single folder. Therefore, the device will only show the mail document in the most recent folder. |
Calendar
Table 6. Calendar issues
|
|
|
Cannot create or edit meetings.
|
This will be addressed in a future release.
|
Delegate and Propose new time are not supported.
|
The Notes calendar Delegate and Propose new time actions are not supported for the Lotus Notes Traveler device.
|
Meetings are not ghosted.
|
A ghosted meeting refers to a meeting that is displayed in the calendar that has not been accepted (the meeting information came from an invitation).
|
Multiple instances of a repeating calendar event in Notes that occur within the same day are not supported.
|
If a repeating calendar event contains multiple instances for the same day and in the same time zone that the event occurs, only one of the instances for that day is sent to the mobile device.
|
You cannot change repeat settings for a calendar entry after the repeating entry is created.
|
Notes does not allow you to change the repeat setting for a calendar entry after it has been created. For example, you cannot change a weekly repeating entry to a daily repeating entry or change a non-repeating entry to a repeating entry.
|
Limitations when using Room and Resource information in calendar events.
|
The ROOM and RESOURCE fields do not display in calendar events.
|
Limitations with attendee responses.
|
Attendee responses are not displayed (accepted, declined, tentatively accepted, delegated).
|
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 attachments and calendar events.
|
You cannot add attachments to calendar entries, or view attachments in calendar entries.
|
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 Lotus Notes client to perform this action.
|
| "This document is a meeting notice and requires the use of Lotus Notes or iNotes client to view the content." is displayed as an email when a counter to a meeting invitation is received. | Devices do not support Counter notices and the a Notes client or iNotes must be used to process a counter. |
Month view not available.
|
This will be considered for a future release.
|
Functions not implemented
Table 7. Functions not implemented
|
|
|
|
|
This will be considered for a future release.
|
|
|
This will be considered for a future release.
|
Mail and calendar widgets
|
This will be considered for a future release.
|
|
|
Only supported under Default Settings
|
|
|
Notifications works only for mails received in Inbox
|
Parent topic: Known limitations and restrictions
|
|
|
|
| Version 4 |
April 24, 2012 |
9:40:57 AM |
by Matt S Munse  |
|
|