Documentation

​
​

Development

User Acquisition

Monetization

Industry

Vivox Core SDK

Vivox Core SDK

Vivox
​
​
Vivox Core SDK
  • Overview
  • Before you begin
  • Get started
  • Release notes
  • Developer Guide
    • Client SDK basics
    • Channels
    • Presence management
    • Messaging
    • Manage audio
    • Couch co-op
    • Android app development
      • Bluetooth profile management
      • Android SDK permission requirements
      • Android library requirements
      • Initialize Vivox Android services
      • Android speakerphone audio: Mono or stereo
      • Update the ProGuard rule file
      • Smart Platform Audio Management
      • Acoustic echo cancellation
      • Disable the Vivox SDK internal AEC
      • Hardware echo cancellation
      • Absolute paths for native libraries
      • Reduce Opus CPU load on low-powered Android devices
    • iOS app development
    • macOS app development
    • Windows app development
    • Real-time recording
    • Speech-to-text audio transcription
    • Text-to-speech
    • Troubleshooting
  • Reference
  • Privacy overview
  1. Vivox Core SDK documentation
  2. Android app development

Android speakerphone audio: Mono or stereo

Configure mono or stereo audio output for Android speakerphone.
Read time 1 minute
Last updated 8 months ago

On Android, Vivox downmixes stereo output into mono output when it detects that the speakerphone is in use. Vivox downmixes the audio output because many Android devices play mono in speakerphone mode. Some devices only play one channel when provided with stereo audio, which makes the panning of 3D channels detrimental.
You can control whether speakerphone downmixing occurs for all devices by providing a list of exceptions by listing which brands, models, and devices to exclude. To change the default speakerphone downmix behavior, add an Android meta-data name-value pair to your application's AndroidManifest.xml. You can learn more about Android meta-data tags in the official Android documentation (Android Developer Documentation).
The metadata name to use is:
"com.vivox.sdk.downmix_speakerphone_enabled"
Note
There is a default exception that disables speakerphone downmix for Meta/Oculus devices. Changing this value overwrites this default exception.
The value must be a string starting with either true or false. To add a list of exceptions, add a comma after true or false and start a comma-delimited list of substrings to search for in the string generated for the current device, formatted as "BRAND MODEL DEVICE". The value string is case-insensitive.
The following are examples of valid value strings:
  • "true"
  • "false"
  • "true,brand,brand_two model,model_two"
  • "false,model_three device,device_two"
Note
Replace the example brands, models, and devices with values retrieved by android.os.Build.* strings.
The following is an example of disabling downmixing on Samsung devices:
“true,samsung"

Copyright © 2026 Unity Technologies
LegalPrivacy PolicyCookiesDocumentation Terms of UseDo Not Sell or Share My Personal InformationYour Privacy Choices (Cookie Settings)

"Unity", Unity logos, and other Unity trademarks are trademarks or registered trademarks of Unity Technologies or its affiliates in the U.S and elsewhere (more info here). Other names or brands are trademarks of their respective owners.

Some pages are machine-translated for convenience, and may contain inaccuracies. In the event of conflicting information, the English version is authoritative.


    Report a problem with this page