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
        • Bluetooth profile comparison
        • SCO handshake failures
        • Bluetooth tradeoffs with Vivox
        • Change a Bluetooth profile
        • Troubleshooting Bluetooth SCO underrun issues
      • 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
  3. Android app development

Bluetooth tradeoffs with Vivox

Bluetooth profile behavior in Vivox.
Read time 1 minute
Last updated 8 months ago
Vivox provides the option to opt-out of Bluetooth SCO altogether, and use Bluetooth A2DP instead.
If you use 
vx_bluetooth_profile_hfp
(the default), and the Bluetooth SCO connection fails, the device will route all audio (render and capture) to the speakerphone.
Note
If a Bluetooth device does not have SCO but does have A2DP, then A2DP should still work because it would not be possible to failover from an SCO-connect attempt into speakerphone mode. It is possible to individually disable Bluetooth SCO for devices in the Android Bluetooth settings.
If you use 
vx_bluetooth_profile_a2dp
, then voice and game audio will almost always go through a Bluetooth headset when one is connected. One exception is for headsets without high-quality A2DP audio (like older-style single-ear handsfree headsets). Those older devices will then behave similarly to when an SCO connection fails, so audio will route to the handset speakerphone.
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