Please don't use the setParameter interface. It will be removed in the next release.
We will be adding an improved mechanism for tunneling device specific parameters through the framework to the HAL that is consistent throughout the media framework (audio, camera, mediaplayer, etc). The problem with setParameter is that you can't set multiple parameters as an atomic commit. It was an API added as a stopgap measure to solve a specific problem in 1.0 and was never intended to be used a public API. On Apr 2, 12:26 pm, SS <[email protected]> wrote: > Hello, > > We want to have a table of (key,value) shared between App layer and > Audio HAL. (key, value) will be passed down to the HAL layer using the > Audio SetParameter function. More than one app (in Java space) will be > talking to the Audio HAL (Native space) using that function so, the > table will shared between multiple components. What is the preferred > way of creating and maintaining this table? > Any help is appreciated. > > Thanks. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
