Archived:Audio routing limitations on S60 3rd Edition (Known Issue)
m (moved Audio routing limitations on S60 3rd Edition (Known Issue)) to Audio routing limitations on S60 3rd Edition (Known Issue): Fix typo)
m (Removed protection from "Audio routing limitations on S60 3rd Edition (Known Issue)": Merged with wiki)
Revision as of 02:46, 24 February 2012
3rd-party applications cannot control audio routing or mix audio with an active voice call on S60 3rd Edition.
3rd-party applications on S60 3rd Edition have some limitations in their audio routing and playback capabilities.
- VoIP applications: The voice will be directed only to the loudspeaker and not to the earpiece because all 3rd-party audio applications are treated as "Players/Recorders".
- 3rd-party applications cannot mix audio with an ongoing circuit-switched voice call. This is due to a hard-coded Vendor ID check in the mixing policy between 3rd-party "Players" and native telephony application.
- Applications that try to play custom/video ring tones are not able to play the ring tone if the Nokia music player is playing music at the same time when there is an incoming call.
Audio preference and priority values sent by the 3rd-party application are ignored if the application does not have Symbian or Nokia Vendor ID. Typically developers' VID is 0x00000000. Nokia's VID is not available for 3rd parties.
Nokia Developer provides an Audio Proxy Server (APS) wrapper for S60 3rd Edition devices and a VoIP Audio Services APIs (VAS) for S60 3rd Edition, FP1 and FP2 devices that can be used for creating audio streams, such as VoIP applications. APS and VAS are part of the SDK API Plug-in packages for S60 3rd Edition SDKs.
Additionally, Call Audio Control API offers loudspeaker control for GSM calls.
Note that S60 3rd Edition and S60 3rd Edition, FP1 devices require different versions of the APS server binaries.