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
  2. Android app development

SCO handshake failures

Understand why the SCO handshake sometimes fail.
Read time 1 minute
Last updated 8 months ago

There are a lot of Android devices, Android versions, and Bluetooth devices from different manufacturers. This leads to a lot of combinations. Because of the variation in handset/device combinations, it’s very difficult to say why it happens with any particular set. It could be limited resources, an incompatibility in Bluetooth versions, one of the devices in the wrong mode, or one of many other reasons. In the Vivox SPAM logic, we retry up to three times with a 300 ms delay between each attempt in order to maximize the opportunity for a Bluetooth SCO device to connect correctly.

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