OpenCore has no context to do this, this is managed through application life cycle.
The app is supposed to manage the resources by calling release() on the MediaPlayer. If the screen times out, then the app's onPause() method will be called and it should call the release() method. If the app is not doing this - it's an app problem. On Feb 4, 10:26 pm, hdandroid <[email protected]> wrote: > At the end of audio playback, opencore framework places OMX audio > decoder component in PAUSE state. User may not perform any operation > after the end of playback (may be for several minutes). In case of HW > audio decode, this will hold up resources and continue to drain > current in PAUSE state. To avoid this from happening, opencore can > either move the component to IDLE (or LOADED) state after completing > playback of each song. This will allow the component to release HW > resources and reduce power consumption > > Is it a straight forward change to move the component to idle state > instead of pause state at the end of playback? Any issues with this > approach? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
