Return to site

Windows 10 A2dp Driver

broken image


-->
  1. A2dp Bluetooth Windows 10
  2. Windows 10 A2dp Drivers

With Windows 10 version 2004, Microsoft has restored the A2DP Sink for Bluetooth in Windows 10. It was removed in Windows 8, making Windows 7 the last OS version with A2DP Sink support. Now, things has changed, and it is finally possible to use A2DP for Bluetooth in Windows 10.

Note Looking for drivers for your Bluetooth audio device? See Fix connections to Bluetooth audio devices and wireless displays.

Note For information about Bluetooth support prior to Windows 10, see Bluetooth Support in Previous Windows Versions.

Which Bluetooth versions does Windows 10 support?

Windows 10 for desktop editions (Home, Pro, Enterprise, and Education) and Windows 10 Mobile support the following Bluetooth versions:

  • Version 1.1
  • Version 2.0
  • Version 2.0 with EDR
  • Version 2.1
  • Version 2.1 with EDR
  • Version 4.0
  • Version 4.1
  • Version 5.0

Windows Server 2016 does not support Bluetooth.

Which Bluetooth profiles have in-box support in Windows 10?

Windows 10 for desktop editions in-box Bluetooth profiles:

Windows 10 (Version 1803) supports Bluetooth version 5.0 and the following Bluetooth user profiles:

  • Advanced Audio Distribution Profile (A2DP 1.2)
  • Audio/Video Control Transport Protocol Target (AVCTP 1.4)
  • Audio/Video Distribution Transport Protocol (AVDTP 1.2)
  • Audio/Video Remote Control Profile (AVRCP 1.6.1)
  • Battery Service over GATT Profile (1.0)
  • Bluetooth LE Generic Attribute (GATT) Client
  • Bluetooth LE Generic Attribute (GATT) Server
  • Bluetooth Network Encapsulation Protocol (BNEP 1.0)
  • Device ID Profile (DID 1.3)
  • Device Information Service over GATT Profile (DIS 1.1)
  • Dial-up Networking Profile (DUN 1.1)
  • Generic Access Profile (GAP)
  • Generic Audio/Video Distribution Profile (GAVDP 1.2)
  • Hands-Free Profile (HFP 1.6)
  • Hardcopy Cable Replacement Profile (HCRP 1.2)
  • HID over GATT Profile (HOGP 1.0)
  • Human Interface Device (HID 1.1)
  • Human Interface Device Service (HIDS)
  • Interoperability (IOP)
  • Logical Link Control and Adaptation Protocol (L2CAP)
  • Object Push Profile (OPP 1.1)
  • Personal Area Networking User Profile (PANU 1.0)
  • RFCOMM (1.1 with TS 07.10)
  • Scan Parameters Profile Client over GATT Profile (ScPP 2.1)
  • Security Manager Protocol (SMP)
  • Serial Port Profile (SPP 1.2)
  • Service Discovery Protocol (SDP)

Windows 10 Mobile in-box Bluetooth profiles:

  • Advanced Audio Distribution Profile (A2DP 1.2)
  • Audio/Video Remote Control Profile (AVRCP 1.3)
  • Bluetooth LE Generic Attribute (GATT) Client
  • Device ID Profile (DID 1.3)
  • Hands-Free Profile (HFP 1.6)
  • HID over GATT Profile (HOGP 1.0)
  • Human Interface Device (HID 1.1)
  • Message Access Profile (1.1)
  • Object Push Profile (OPP 1.1)
  • Personal Area Network Access Point (PAN NAP 1.0)
  • Phone Book Access Profile (PBAP 1.1)
  • Serial Port Profile (SPP 1.2)

Windows 10 for desktop editions in-box Bluetooth profiles:

ProfileDescription

GATT

Bluetooth LE Generic Attribute (GATT) Client

A2DP 1.2

Advanced Audio Distribution Profile

AVRCP 1.3

Audio/Video Remote Control Profile

DI 1.3

Device ID Profile

DUN 1.1

Dial-Up Networking

HCRP 1.0

Hardcopy Cable Replacement Profile

HFP 1.5

Hands-Free Profile

HID 1.1

Human Interface Device

HOGP 1.0

HID over GATT Profile

OPP 1.1

Object Push Profile

The best part, it works in the background and thus does not affect your tasks.It has powerful tools to manage calendars, tasks, and contacts. Em client 7 serial key. EM Client 8.1.876 License Key helps you to unlock its pro features for the whole life. You can utilize this tool for your commercial uses too. However, it allows you to schedule backups by defining a suitable time. No matter you're a student or a teacher, a businessman, or a novice person, this is the best ever email client for you.

PANU 1.0

Personal Area Network User

SPP 1.2

Serial Port Profile

Reddit windows 10 serial key. How to install hping3 on windows. Windows 10 Mobile in-box Bluetooth profiles:

ProfileDescription

GATT

Bluetooth LE Generic Attribute (GATT) Client

A2DP 1.2

Advanced Audio Distribution Profile

AVRCP 1.3

Audio/Video Remote Control Profile

DI 1.3

Device ID Profile

HFP 1.6

Hands-Free Profile

HID 1.1

Human Interface Device

HOGP 1.0

HID over GATT Profile

MAP 1.1

Message Access Profile

OPP 1.1

Object Push Profile

PAN NAP 1.0

Personal Area Network Access Point

PBAP 1.1

Phone Book Access Profile

SPP 1.2

Serial Port Profile

New features and recommendations for Windows 10 and later

To learn more about the new features and hardware developer recommendations for the different versions of Windows 10, see Bluetooth in the Hardware component guidelines section.

Related topics

Bluetooth is a flexible standard. It defines various profiles that operate on top of the Bluetooth networking protocol stack and implement specific services, such as hands-free communications. Bluetooth devices each support a small subset of profiles, typically only one or two, according to their designated function.

Bluetooth headphones and speakers implement the advanced audio distribution profile (A2DP). The A2DP profile transports encoded audio streams from one device to another. To guarantee compatibility between devices, any device implementing the A2DP profile needs to offer a common codec, SBC. However, A2DP supports additional codecs that may increase audio quality or reduce latency compared to SBC. One of those optional codecs is aptX. In this article, I am looking at aptX benefits and I am describing how to get aptX on Windows 10.

What is aptX?

aptX is an alternative codec for the Bluetooth A2DP protocol. It comes in multiple flavors:

  • aptX
  • aptX LL (low latency)
  • aptX HD

Is aptX better than SBC?

Qualcomm, who acquired the aptX company CSR in 2015, claims that aptX offers 'superior audio'. Figuring out whether that is actually true is harder than expected. Let's break this quality question down into two different aspects: fidelity and latency.

Audio Fidelity

As this overview shows, the technical specifications of the base aptX code are similar to that of SBC. Specifically, the maximum bitrate of 352 kb/s is not much higher than SBC's 320-345 kb/s (SBC depending on implementation).

Windows 10 A2dp Driver

The bitrate by itself does not tell us anything about a codec's fidelity, however. Different codecs can be very different in encoding efficiency, as are H.264 and its successor H.265 for video (the latter only needs about half as many bits for the same visual quality). Fidelity can only be determined by double-blind listening tests. Unfortunately, nobody seems to have performed such listening tests in a scientific, reproducible manner (at least I could not find any information). Please let me know by commenting below if you know of any publications.

Another aspect influencing fidelity is that implementations do not always use a codec's maximum bitrate. SBC, for example, comes with three quality modes, low (201 kb/s), middle (229 kb/s) and high (328 kb/s). Devices may select lower-quality modes to favor a stable connection over sound quality (example: these Sony headphones).

Audio Latency

When watching a video, you do not want the audio to lag behind. In other words: the audio latency should ideally be small enough to not be noticeable. Unfortunately, that is often not the case.

Bluetooth audio introduces significant latency, the exact amount of which depends on the codec as well as its implementations in the sending and receiving devices. Most Bluetooth headphone reviews do not include latency measurements, with the notable exception of rtings.com. They even have a list with latencies for all the headphones they ever tested. Plain aptX seems to be slightly better than SBC, but only aptX LL seems to be good enough to not be noticeable.

While, however, the number of devices supporting base aptX is steadily growing, support for aptX LL is still extremely rare (see rtings.com or bluetoothcheck.com).

Audio Quality Summary

There do not seem to be any objective comparisons between the aptX variants and SBC. From my experience it should be safe to say the following:

  • SBC offers pretty good fidelity at maximum bitrate.
  • aptX might be slightly better than SBC at maximum bitrate.
  • Both SBC and aptX introduce significant latency in the range of 150-200 ms.
  • aptX LL drastically reduces latency but is only supported by a handful of devices.

aptX on Windows 10

OS Support

If Microsoft wanted to hide this piece of information, they could not be doing a better job. A single page on microsoft.com mentions aptX. Apparently, Windows 10 has supported the aptX codec since the first release (1507). According to this Reddit thread, Windows 10 aptX support does not require any drivers in addition to what is part of the OS. I am mentioning that because numerous forum posts state you need to install special drivers. That does not seem to be true.

As for aptX HD or aptX LL (low latency): those codecs do not seem to be supported. If you would like to have them in Windows – especially aptX LL would be great when watching video – make sure to vote for this item in Feedback Hub: please add aptX Low Latency codec support to the Bluetooth A2DP driver.

For a list of supported Bluetooth versions and profiles see this page.

External USB Adapter

The Avantree Audicast is a flexible Bluetooth transmitter that can be connected to a PC (via USB) or a TV (via optical input or headphone jack). The Audicast has several neat features:

  • Support for aptX LL (low latency) in addition to regular aptX and, of course, SBC
  • LEDs indicate which codec is being used
  • Two receiving headphones can be connected
  • Small and light
  • No additional power source except for USB required
  • All cables are included

Please note that when connected to a PC, the Audicast does not work as a generic Bluetooth adapter (in which case the OS drivers would be used). Instead, it registers as a USB audio device. No drivers are required.

Which Codec and Bitrate are Being Used?

Amazingly, Windows does not provide any tool or API for monitoring the codec used by A2DP. Whether it is SBC, aptX or something different – users are left completely in the dark. To help change that and encourage Microsoft to provide more visibility, please vote for please let users see what Bluetooth A2DP codec is used.

For the sake of completeness, I spent several hours capturing and analyzing ETW logs as indicated at the following sources, but none of the generated logs seemed to indicate the A2DP codec being used.

A2dp Bluetooth Windows 10

  • Matthew van Eerde: Collecting audio logs the old-fashioned way
  • GitHub microsoft/busiotools
  • Windows KB3029606: Update to improve Bluetooth driver diagnosis in Windows 8.1

Update 2020-09-09

Windows 10 A2dp Drivers

Based on the info provided by commenter eluxe below I figured out how to determine which A2DP codec is used and documented it here: How to Check Which Bluetooth A2DP Audio Codec Is Used on Windows.





broken image