Java ME Developer Guide

Chapter 30 - Motorola Secondary Display API

30.3 Exception Handling

For portability purposes, the design of the API will allow the developer to handle Ex- ceptions related to the instantiation of the secondary display context. Appropriate ex- ceptions should be generated for invocation of methods not supported by secondary display.

30.4 Push enabled applications

While the flip is closed, it is desirable to start up MIDlets if a push is received on a re- gistered port and the associated MIDlet can run on secondary display. This will be subject to user confirmation.

This feature need not be implemented for the first version of API.

30.5 Feature interaction

Any incoming call, message or any scheduled native application should have priority over MIDlet running on secondary display. If any native application requests focus, the running MIDlet shall be suspended.

30.6 Low power requirements

It is desirable that the VM runs on low-power mode while using the secondary dis- play.

30.7 Security

Secondary Display API shall follow MIDP 2.0 security model.

DRAFT - Subject to Change [192/201]

Page 192
Image 192
Motorola maxx V6 manual Exception Handling, Push enabled applications, Feature interaction, Low power requirements