Thx! Sami . So as I understand, policy unaware apps don't have to request for resources. They just have to start using it? And ohmd will cork or uncork the resources as and when it desires?
-----Original Message----- From: Sami Sirkiä [mailto:sami.sir...@cybercom.com] Sent: Friday, September 23, 2011 4:13 PM To: meego-dev@meego.com Cc: Chanchani, Nimesh Subject: Re: [MeeGo-dev] Audio policy -- Adding one's own resource class Hi, Resource policy daemon (ohmd) has an enforcement module in pulseaudio. A policy-unaware application may play sounds, but the streams are corked if there are higher priority streams playing. This means the audio from anroid app is not audible during phone calls, and the application does not even know this. The musix player in handset images is policy-unavare. It keeps playing happily during phone calls and ringtone, although music does not come out. When ringing or call ends, music is again routed out. If I recall correctly, recording is not enforced. Application can record, but nothing guarantees that some sounds are played simultaneously. "player priority" is just a name, recording is also possible. I don't know of any way to prioritize policy-unaware apps/streams. Instead their audio streams are mixed together. (I think...) But then, I may remember things wrong. -- SSirkia On 09/23/2011 01:04 PM, nimesh.chanch...@accenture.com wrote: > Thanks Tukka . I have aa few questions about policy unaware apps: > > > If the apps don't ask for the permission (policy unaware apps), they are > all going to be treated as media players. In this case, how can they > know if they are granted the permission to use a particular resource > set? For instance let's assume a policy-unaware Android app wants to > play audio through the speakers while the speakers are already in use by > a higher priority app. In this case the policy framework denies the > permission; how does the policy unaware app get notified? > > Is there a way to give different priorities to policy-unaware apps? For > example, an phone call should have higher priority over the audio player. > > What happens if a policy-unaware app wants to record audio? I guess that > is not going to be possible, since all policy unaware apps are treated > as media players by the policy framework. > > > ------------------------------------------------------------------------ > > *From:*meego-dev-boun...@meego.com [mailto:meego-dev-boun...@meego.com] > *On Behalf Of *Tuukka Mäkinen > *Sent:* Thursday, September 22, 2011 6:40 PM > *To:* meego-dev@meego.com > *Subject:* Re: [MeeGo-dev] Audio policy -- Adding one's own resource class > > On 09/22/11 15:44, nimesh.chanch...@accenture.com > <mailto:nimesh.chanch...@accenture.com> wrote: > > Hi guys, > > I want to add my own resource class and alter the priorities of the > existing ones. Can anyone suggest a starting point or a pointer? > > Regards, > > Nimesh > > > Policy settings are in the package policy-settings-basic-{platform} > package. That package contains policy rules (in prolog) and some > settings files. Looking into settings package for N900 resource classes > appear to be defined in resource_classes.pl. > > It would be interesting to see what could be done with policy framework > but unfortunately I haven't quite grasped prolog. > > Tuukka Mäkinen > > > ------------------------------------------------------------------------ > This message is for the designated recipient only and may contain > privileged, proprietary, or otherwise private information. If you have > received it in error, please notify the sender immediately and delete > the original. Any other use of the email by you is prohibited. This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the email by you is prohibited. _______________________________________________ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
