Motorola Internal Use Only 1

MDB

<date of report>

Presented by Dan Winsor

Multimedia Applications Component Overview

Motorola Internal Use Only 2

MDB

<date of report>

Multimedia Organization

• “Multimedia” team includes all engine and application pieces in the same organization.– Experts are still generally either focused on applications or

engine areas, though.– CDMA MME is a separate organization, but CDMA-ROW

applications are handled by common Multimedia team.

• Multimedia is currently divided by domain:– Consumption: Media viewing and playback.– Navigation: File listing/navigation, file management.– Capture/Edit: Still/video capture, media editing.– Communications: Video calling and rich voice calls.– Voice Recognition: Voice activation/recognition.– Misc.: Other areas not covered above.

Motorola Internal Use Only 3

MDB

<date of report>

Multimedia Applications

• Applications owned by the Multimedia team and covered by the “MMC” and “FSSA” labels:– Media Player (combines video player and audio player)– Picture Viewer– Camera / Picture Capture– Video Camera / Video Capture– Audio Capture (recent addition, replacing Voice Notes)– Video Calling / Video Telephony– Themes– Fasttrack Content Handler– Media Finder– File System Services– Erase on Power-up (EOPU)– Hotswap Notification– Funlights

Motorola Internal Use Only 4

MDB

<date of report>

Non-Multimedia Apps.

• These pieces are sometimes confused with Multimedia applications, even though they’re not:– MMS – Multimedia applications handle content insertion and

full screen playback, but MMS composition and in-line viewing are handled by a separate MMS team.

– Ring-Vib Alert – The application portion of this is not owned by Multimedia.

– “Multimedia” menu and “mma” application directory – This is actually part of the Main Menu, owned by UPA.

– Java players – Java applications such as iTunes or other Java media players are not supported by the Multimedia application experts.

– Screensaver – Other than allowing this to be set from within Multimedia, not managed by Multimedia.

– Device Layer File System – The UI is part of Multimedia, but the lower layer calls which operate on files are not!

Motorola Internal Use Only 5

MDB

<date of report>

Component Strategy

• Strategy for the MMC and FSSA labels is to cover anything having to do with media and media files.

• Includes providing services for other applications to preview files or select files.– Service mode behavior is different than full mode behavior.

• Specialized behavior for coping with disruptive events.– For example, behavior for automatically pausing media playback

when an incoming call comes in, and then allowing the user to resume afterwards (instead of exiting!).

– When exiting with unsaved content, behavior to save the content automatically when possible.

• Internal conflict resolution between use cases.– Includes cases such as launching a media playback application

when one is already active, or launching one Multimedia application when another is currently using resources which are needed.

Motorola Internal Use Only 6

MDB

<date of report>

Dependencies

• The primary dependency for the Multimedia applications is, unsurprisingly, the Multimedia engine.– Hence why these are now unified under common management.

• Some large number of dependencies on UIS as well.– Specialized dialogs for Multimedia, including for playback, capture,

navigation, and video calls.– Depends on UIS “safeframe” management and covering.– Relies on key and event handling for camera key, video call key.

• Most interactions with other applications are inward.– That is, primarily providing services for other applications, rather

than depending on other application services.– There are exceptions, of course. Video calling relies on other

applications heavily, e.g. MMINS and Phonebook. Most applications rely on the UPA “Backlight Control” (BLC) application.

• Dependency on the flex and file system; bad behavior if flexed improperly, or if pre-loaded system files (e.g. camera shutter tones) are missing.

Motorola Internal Use Only 7

MDB

<date of report>

Sample Use Cases (1)

• Browser-invoked download use case:– User selects and downloads a video file.– Browser uses Content Dispatcher to give video file to Media Player

to preview the video file.– Media Player handles preview, and if required, “storing” the video

(i.e. moving it to the correct directory with the correct name).• MMS “insert new video” use case:

– User is composing an MMS message and decides to insert a new video into the message.

– MMS invokes Video Capture application for “capture as a service”, specifying how much space is available in the message.

– Video Capture application starts and allows user to capture video up to space limit.

– After user finishes capturing and is satisfied, video is saved and filename is returned back to MMS.

Motorola Internal Use Only 8

MDB

<date of report>

Sample Use Cases (2)

• Phonebook picture selection use case:– User is creating a new Phonebook entry and wants to

associated an image with that Phonebook entry.– Phonebook invokes Picture Viewer service to select an

image.– User navigates between images until the desired one is

found, and then selects that one. Selection is returned back to Phonebook.

• Stand-alone use case:– User picks “Media Finder” from Main Menu.– Media Finder displays available media files, allowing user to

navigate through the media.– User finds an audio file to listen to, and selects it.– Media Player is started to play the audio file, while Media

Finder remains in the background.

Motorola Internal Use Only 9

MDB

<date of report>

Common Issues

• Broken camera on early hardware.– Can manifest as “Busy Try Again” when starting capture, or as

various problems in the viewfinder.– New hardware often has issues with the camera lens(es).– In some cases, hardware is actually broken. In other cases, imager

configuration is not completed and hence not yet ready for testing.– Typically nothing the applications can do!

• Incorrect flex, particularly for new products.– Developers don’t necessarily know which features should be

enabled or disabled for each product, or each customer.• Bad or out of date test cases.

– Often receive issues for pre-P05.2 soft key or menu layouts, or for pre-Media Finder requirements when these no longer apply.

• Feature interaction breakages.– Multimedia is very prone to breaking when exercising complex

feature interactions (e.g. incoming phone call during progressive video download).

Motorola Internal Use Only 10

MDB

<date of report>

Application Experts

• The following application experts are available in Libertyville:– Stephen Yu (picture and video capture)– Sachin Doshi (media player)– Lee Klimek (media player and video capture)– Josh Ehlke (media finder)– Tom Courtney (streaming, progressive download, fast track)– Dan Winsor (video calling, UIS/AFW architecture issues)

• Additional application experts available overseas in Turin, Italy, and Vladivostok, Russia.

• Questions or inquiries about Multimedia can always be sent to the “Multimedia Hotline”.– Mailing list: [mmhotlne]