기술 자료

​
​

Development

User Acquisition

Monetization

산업 분야

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

Bluetooth profile comparison

A comparison between using A2DP or SCO profiles.
읽는 시간 2분
최근 업데이트: 8달 전

The Bluetooth API provides implementations for the following Bluetooth profiles that are relevant to Vivox:

Bluetooth A2DP

The Advanced Audio Distribution Profile (A2DP) profile defines how high-quality audio can be streamed from one device to another over a Bluetooth connection. It defines how multimedia audio can be streamed from one device to another over a Bluetooth connection (it is also called Bluetooth Audio Streaming). For example, music can be streamed from a mobile phone to a wireless headset, hearing aid/cochlear implant streamer, or car audio. A2DP is uni-directional. There is no support for capturing audio on a Bluetooth device at the same time as rendering audio.

Bluetooth SCO(HFP)

The Bluetooth Hands-Free Profile (HFP) allows the Bluetooth device to make and receive voice calls via a connected handset. Synchronous Connection-Oriented (SCO) is the type of radio link used for voice data.

Tradeoffs of using SCO or A2DP

A2DP audio is rendered on the Bluetooth headset. Because there’s no support for capture and render at the same time using this profile, most handsets will capture audio from the microphone on the phone. The rendered audio is high quality and stereo. Game audio will remain high quality and will play through the headset along with voice.
SCO voice audio is both rendered and captured from the Bluetooth device. The rendered audio is of lower quality (similar to that of a standard phone call) and mono. Depending on the Android device, game audio will either:
  • Play as low-quality and mono audio through the Bluetooth headset along with voice. Or,
  • Play from the phone with standard quality.

Latency

A2DP tends to have more latency than SCO, but not too much more (100 - 200 ms). The extra audio quality of A2DP is notable.
Because of Bluetooth’s inherent low-power requirements, low latency, two-way communication is provided through SCO by reducing the sample rate and the number of channels rendered which leaves bandwidth for a microphone channel.

Implications of using the handset microphone

With A2DP, having the microphone on the handset means that hand noises and screen taps may be audible, so extra rustling and thumping is expected. The hands holding the device can cause muffling of captured audio because they occlude the microphone or completely cover it. With SCO the audio is captured from the Bluetooth device, so no hand noise is typically captured.
Another concern is that the handset can be put down and end up far from the user. With A2DP, as the user moves away from the handset, they will get further from the microphone, and be more difficult to capture. With SCO, they can still be heard clearly no matter how far the user is from their phone (within Bluetooth range).

Copyright © 2026 Unity Technologies
법률 정보개인정보 처리방침쿠키Documentation Terms of Use개인 정보 판매 또는 공유 금지개인정보 보호 선택(쿠키 설정)

'Unity', Unity 로고 및 기타 Unity 상표는 미국 및 기타 지역 내 Unity Technologies 또는 그 계열사의 상표 또는 등록상표입니다(자세한 내용은 여기에서 확인하세요). 기타 명칭 또는 브랜드는 해당 소유자의 상표입니다.

일부 페이지는 편의를 위해 기계 번역되었으며 부정확한 내용이 있을 수 있습니다. 정보가 상충되는 경우, 영어 버전을 우선으로 참조하세요.

  • 보고 있는 페이지
    • Bluetooth A2DP

    • Bluetooth SCO(HFP)

    • Tradeoffs of using SCO or A2DP

      • Latency

      • Implications of using the handset microphone


이 페이지의 문제 보고