I'm not sure what you mean by "cached" in this context, but what happens with the standard music player applications is that it has a service that does the playback (this allows "background" playback to work), and that service stops itself after 30 seconds if the foreground UI is gone and the music is paused. Once the service is stopped, the system eventually kills that process to free up resources, at which point the "media server" is notified and will destroy the associated playback session. The call sequence on the opencore/omx side should be the same as when you pause the music player and then "kill -9" it.
On Mon, Feb 9, 2009 at 11:27 AM, chrisk_ti <[email protected]> wrote: > > Hi all, > > I am experiencing a problem when trying to resume a cached music > playback session. I am using my OMX components, the "Music" > application and all the latest source. > > I have several questions on the states of opencore and the music > player application that will help me debug the error from my DSP/OMX > layer. > > 1. When playback is paused by pushing the "pause" button, is the OMX > component transitioned to pause at that point? I know this is true. > Typical pause/resume case works well with my codecs. > > 2. When the music application is left to work in a different > application, the current song and the location with in that song are > cached. When this happens, what is the expected call sequence and > state transitions for OMX and opencore? > > Thanks for any insight- > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "android-framework" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-framework?hl=en -~----------~----~----~----~------~----~------~--~---
