Archived:Resources cannot be prefetched after deallocation in Java ME on S60 1st and 2nd Editions (Known Issue)

Comments

(no comments yet)

Log in or Join to leave comments.

Archived: This article is archived because it is not considered relevant for third-party developers creating commercial solutions today. If you think this article is still relevant, let us know by adding the template {{ReviewForRemovalFromArchive|user=~~~~|write your reason here}}.

The article is believed to be still valid for the original topic scope.

Article Metadata

---

Compatibility

Platform(s): S60 1st and 2nd Edition

---

Article

Created: User:Technical writer 1 (21 Apr 2005)

Last edited: hamishwillee (28 Jun 2012)

Overview

If you have released resources by using the deallocate() method, you cannot use the prefetch() method anymore to get the player to PREFETCHED state.

Description

A Player has five states: UNREALIZED, REALIZED, PREFETCHED, STARTED, and CLOSED. If the player is in PREFETCHED state, you can release the reserved resources by calling the deallocate() method. After that you cannot prefetch the resources anymore. If you call the prefetch() method after calling the deallocate() method, you will get MediaException. Note that this concerns S60 devices. Calling prefetch() is working in Series 40 devices with the MMAPI implementation.

How to reproduce

If your player is in the PREFETCHED state, call deallocate() and after that call prefetch().

Solution

If your player is in the PREFETCHED state, don't call deallocate() and after the prefetch() method.