[davidmanpearl]

I thought that JSR-135 is an automatic ticket to the getSnapshot() method. This does not seem to be the case. On Nokia 6102i (Series 40, 2nd ed, JSR-135), System.getProperty("video.snapshot.encodings") returns null and I can't setup the Player or VideoControl.

I read evidence that Series 40, 2nd edition devices do not support getSnapshot at all. In a response to the thread: "Image capture midlet with Nokia 6020" (http://discussion.forum.nokia.com/fo...ad.php?t=85003), hartti writes:

snapshop (sic) is not supported on Nokia Series 40 2nd Edition devices

a. hartti, do you mean "getSnapshot" is not supported?
b. Would someone please point me to documentation that verifies this?
c. This indicates that it is impossible to capture images in a S40, 2nd ed handset. Is this true?
d. What about Series 40, 3rd ed.?

- Sincerely, David Manpearl dmanpearl_at_imatte_dot_com

[peterblazejewicz]

hi David,

here is a matrix-feature document for Nokia devices - it includes s40 capabilities (camera snapshot):
http://www.forum.nokia.com/info/sw.n..._0_en.pdf.html

hth,
regards,
peter

[hartti]

Nice catch with the typo...Thanks David :-)

The JSR-135 in general leaves a lot of implementation details up to the handset manufacturers. This is one of those things among others (for example supported audio and video formats).

Snippet from MMAPI spec
"Optionality and Implementation Requirements

Not all implementations of MMAPI support all multimedia types and input protocols. Some implementations may support only a few selected types and protocols. For example, some may support only playback of local audio files. The design of MMAPI allows implementations to provide optional support for different media types and protocols.
Manager provides getSupportedContentTypes and getSupportedProtocols to query for supported media types and protocols. An application can also attempt to create a Player from Manager given the media input. If the content type or the protocol specified is not supported, the Player creation methods throw an Exception.

Since MMAPI is an optional package, it does not mandate any particular media types or protocols. Required types and protocols are to be determined by the appropriate profiles adopting MMAPI (e.g. JSR 118). However, an implementation must guarantee support of at least one media type and protocol.

MMAPI also allows implementations to support optional features. For example, some implementations may support only media playback, but not recording. Or some devices may support volume control while others may not. MMAPI allows implementations to expose these optional features as applicable.

Optional features are organized as Controls. A Player can be queried for all of its supported Controls by using getControls or a particular type of Control by using getControl. "

Hartti