# Bluetooth audio bug on Android 12

**URL:** <https://forum.fairphone.com/t/bluetooth-audio-bug-on-android-12/92932>\
**Category:** Fairphone 4\
**Tags:** bluetooth\
**Created:** [February 1, 2023, 12:52pm UTC](https://forum.fairphone.com/t/bluetooth-audio-bug-on-android-12/92932 "2023-02-01T12:52:37Z")\
**Posts on this page:** 20\
**Page:** 9

<div class="post-metadata">

**Author:** ![anon73661646](https://forum.fairphone.com/letter_avatar/anon73661646/32/6_449c533f586939b6e5f246632a46421f.png) [@anon73661646](https://forum.fairphone.com/u/anon73661646)\
**Post date:** [April 21, 2023, 11:22am UTC](https://forum.fairphone.com/t/bluetooth-audio-bug-on-android-12/92932/163 "2023-04-21T11:22:49Z")

</div>

If they updated to the Android 12 blobs and haven’t found a workaround, yes.

Since most are based on Lineage or at least adjacent to it (Calyx is AOSP with some LOS), once there is a fix everyone should benefit, but if Calyx doesn’t ship a fix, there probably isn’t one yet.

---

<div class="post-metadata">

**Author:** ![Spongebob](https://forum.fairphone.com/user_avatar/forum.fairphone.com/spongebob/32/34780_2.png) [@Spongebob](https://forum.fairphone.com/u/Spongebob)\
**Post date:** [April 21, 2023, 11:27am UTC](https://forum.fairphone.com/t/bluetooth-audio-bug-on-android-12/92932/164 "2023-04-21T11:27:36Z")

</div>

So if it’s possible and others can manage it, shouldn’t Fairphone also be able to solve the problem?

---

<div class="post-metadata">

**Author:** ![Lars\_Hennig](https://forum.fairphone.com/user_avatar/forum.fairphone.com/lars_hennig/32/34036_2.png) [@Lars\_Hennig](https://forum.fairphone.com/u/Lars_Hennig)\
**Post date:** [April 21, 2023, 11:30am UTC](https://forum.fairphone.com/t/bluetooth-audio-bug-on-android-12/92932/165 "2023-04-21T11:30:02Z")

</div>

Yes, of course. But if I understood right, there is no solution from others, yet.

BTW: some short research brought up, that there are Aptx (HD) failures in Android 12 also with other devices. For example OnePlus 8T had a problem with Aptx HD. So this does not seem to be solely Fairphone specific. Of course I do not know wether the other producers already fixed it. Oneplus had the problem in April 2022, though.  
And Samsung does not provide the support at all for Aptx HD, at least for the rather old S20, if I remember correctly.

---

<div class="post-metadata">

**Author:** ![yvmuell](https://forum.fairphone.com/user_avatar/forum.fairphone.com/yvmuell/32/26928_2.png) [@yvmuell](https://forum.fairphone.com/u/yvmuell)\
**Post date:** [April 24, 2023, 10:49am UTC](https://forum.fairphone.com/t/bluetooth-audio-bug-on-android-12/92932/166 "2023-04-24T10:49:05Z")

</div>

A post was merged into an existing topic: [Remarks by the software update FP4 20230318](https://forum.fairphone.com/t/remarks-by-the-software-update-fp4-20230318/95349/31)

---

<div class="post-metadata">

**Author:** ![yvmuell](https://forum.fairphone.com/user_avatar/forum.fairphone.com/yvmuell/32/26928_2.png) [@yvmuell](https://forum.fairphone.com/u/yvmuell)\
**Post date:** [April 24, 2023, 10:48am UTC](https://forum.fairphone.com/t/bluetooth-audio-bug-on-android-12/92932/167 "2023-04-24T10:48:23Z")

</div>

2 posts were merged into an existing topic: [Remarks by the software update FP4 20230318](https://forum.fairphone.com/t/remarks-by-the-software-update-fp4-20230318/95349/29)

---

<div class="post-metadata">

**Author:** ![yvmuell](https://forum.fairphone.com/user_avatar/forum.fairphone.com/yvmuell/32/26928_2.png) [@yvmuell](https://forum.fairphone.com/u/yvmuell)\
**Post date:** [April 24, 2023, 8:14am UTC](https://forum.fairphone.com/t/bluetooth-audio-bug-on-android-12/92932/168 "2023-04-24T08:14:53Z")

</div>

2 posts were merged into an existing topic: [Remarks by the software update FP4 20230318](https://forum.fairphone.com/t/remarks-by-the-software-update-fp4-20230318/95349/24)

---

<div class="post-metadata">

**Author:** ![yvmuell](https://forum.fairphone.com/user_avatar/forum.fairphone.com/yvmuell/32/26928_2.png) [@yvmuell](https://forum.fairphone.com/u/yvmuell)\
**Post date:** [April 24, 2023, 8:16am UTC](https://forum.fairphone.com/t/bluetooth-audio-bug-on-android-12/92932/170 "2023-04-24T08:16:01Z")

</div>

A post was merged into an existing topic: [Remarks by the software update FP4 20230318](https://forum.fairphone.com/t/remarks-by-the-software-update-fp4-20230318/95349/26)

---

<div class="post-metadata">

**Author:** ![ElieBgln](https://forum.fairphone.com/user_avatar/forum.fairphone.com/eliebgln/32/36042_2.png) [@ElieBgln](https://forum.fairphone.com/u/ElieBgln)\
**Post date:** [May 3, 2023, 11:52am UTC](https://forum.fairphone.com/t/bluetooth-audio-bug-on-android-12/92932/171 "2023-05-03T11:52:28Z")

</div>

It worked for me, thanks a lot !

---

<div class="post-metadata">

**Author:** ![sweisgerber](https://forum.fairphone.com/letter_avatar/sweisgerber/32/6_449c533f586939b6e5f246632a46421f.png) [@sweisgerber](https://forum.fairphone.com/u/sweisgerber)\
**Post date:** [May 8, 2023, 3:48pm UTC](https://forum.fairphone.com/t/bluetooth-audio-bug-on-android-12/92932/172 "2023-05-08T15:48:43Z")

</div>

Is there any information if the AptX/AptX adaptive bug has been fixed with B.065? Desperately waiting…

---

<div class="post-metadata">

**Author:** ![sweisgerber](https://forum.fairphone.com/letter_avatar/sweisgerber/32/6_449c533f586939b6e5f246632a46421f.png) [@sweisgerber](https://forum.fairphone.com/u/sweisgerber)\
**Post date:** [May 8, 2023, 9:15pm UTC](https://forum.fairphone.com/t/bluetooth-audio-bug-on-android-12/92932/173 "2023-05-08T21:15:53Z")

</div>

Could now test it myself. Bug is NOT fixed. Neither AptX nor AptX adaptive work. VERY disappointing. 😠

---

<div class="post-metadata">

**Author:** ![anon9989719](https://forum.fairphone.com/letter_avatar/anon9989719/32/6_449c533f586939b6e5f246632a46421f.png) [@anon9989719](https://forum.fairphone.com/u/anon9989719)\
**Post date:** [May 8, 2023, 9:37pm UTC](https://forum.fairphone.com/t/bluetooth-audio-bug-on-android-12/92932/174 "2023-05-08T21:37:23Z")

</div>

> [@Software update: FP4.SP28.B.065.20230420](https://forum.fairphone.com/t/software-update-fp4-sp28-b-065-20230420/95855/1):
>
> List of changes  
> Further personalize your Fairphone with accent colors. System menus and buttons will automatically change color, depending on your Home Screen wallpaper.

It wasn’t in the script, . . . . slowly slowly

---

<div class="post-metadata">

**Author:** ![Lars\_Hennig](https://forum.fairphone.com/user_avatar/forum.fairphone.com/lars_hennig/32/34036_2.png) [@Lars\_Hennig](https://forum.fairphone.com/u/Lars_Hennig)\
**Post date:** [May 9, 2023, 1:19pm UTC](https://forum.fairphone.com/t/bluetooth-audio-bug-on-android-12/92932/175 "2023-05-09T13:19:40Z")

</div>

> [@sweisgerber](#):
>
> Bug is NOT fixed. Neither AptX nor AptX adaptive work. VERY disappointing.

This was not mentioned in the change log, so it was pretty obvious, that this bug is not yet fixed, IMHO.

---

<div class="post-metadata">

**Author:** ![sweisgerber](https://forum.fairphone.com/letter_avatar/sweisgerber/32/6_449c533f586939b6e5f246632a46421f.png) [@sweisgerber](https://forum.fairphone.com/u/sweisgerber)\
**Post date:** [May 11, 2023, 6:35am UTC](https://forum.fairphone.com/t/bluetooth-audio-bug-on-android-12/92932/176 "2023-05-11T06:35:00Z")

</div>

Many thanks for your enlightning comment. Now I finally understand what this change log is good for. Thanks! Thanks! Thanks!

However, I’ve been waiting to use my fine in-ears at full potential again without needing the transmitter case since FP4 got the upgrade to A12. Reason enough to check if something has happened without notice. The partial fix of the AptX bug was incorrectly reported as well.

You’re used to mansplaining in real life, right?

---

<div class="post-metadata">

**Author:** ![Lars\_Hennig](https://forum.fairphone.com/user_avatar/forum.fairphone.com/lars_hennig/32/34036_2.png) [@Lars\_Hennig](https://forum.fairphone.com/u/Lars_Hennig)\
**Post date:** [May 11, 2023, 7:25am UTC](https://forum.fairphone.com/t/bluetooth-audio-bug-on-android-12/92932/177 "2023-05-11T07:25:28Z")

</div>

> [@sweisgerber](#):
>
> You’re used to mansplaining in real life, right?

What is your problem?

If you know how to read a changelog your comment here is completely unnecessary.  
And yes you are right, that the fix for AptX was announced but not done for all codecs. But this time there was not even a mention of any other error fixed in this release.

---

<div class="post-metadata">

**Author:** ![yvmuell](https://forum.fairphone.com/user_avatar/forum.fairphone.com/yvmuell/32/26928_2.png) [@yvmuell](https://forum.fairphone.com/u/yvmuell)\
**Post date:** [May 11, 2023, 8:32am UTC](https://forum.fairphone.com/t/bluetooth-audio-bug-on-android-12/92932/178 "2023-05-11T08:32:47Z")

</div>

> [@sweisgerber](#):
>
> The partial fix of the AptX bug was incorrectly reported as well.

It was announced only for the correction made ( Aptx HD) and not overall for all AptX codecs.

> A bug that was causing the Bluetooth audio to stop working when the aptX HD codec was selected, has been fixed.

---

<div class="post-metadata">

**Author:** ![Spongebob](https://forum.fairphone.com/user_avatar/forum.fairphone.com/spongebob/32/34780_2.png) [@Spongebob](https://forum.fairphone.com/u/Spongebob)\
**Post date:** [May 11, 2023, 8:43am UTC](https://forum.fairphone.com/t/bluetooth-audio-bug-on-android-12/92932/179 "2023-05-11T08:43:20Z")

</div>

Are you kidding us right now?

 ![image](https://forum.fairphone.com/uploads/default/original/3X/7/4/747fbf47065febf20dfc3f291ba6bb7be6f69c90.png)

Where does it say that only PART of the problem should be solved?  
It was clearly stated that the fault was taken care of. And the error is still there!  
The fact that only aptx HD was fixed does NOT mean that the problem has been fixed. The feedback from the forum should be more than clear that it is not so.

No one complained that aptx HD didn’t work, only that their headphones with HD audio stopped working.  
The underlying protocol cannot be less important for the user. He just wants to be able to use his expensive headphones to the full extent with his even more expensive Fairphone 4, just like he did with Android 11. Is that an exaggerated demand from the customer?

---

<div class="post-metadata">

**Author:** ![yvmuell](https://forum.fairphone.com/user_avatar/forum.fairphone.com/yvmuell/32/26928_2.png) [@yvmuell](https://forum.fairphone.com/u/yvmuell)\
**Post date:** [May 11, 2023, 8:58am UTC](https://forum.fairphone.com/t/bluetooth-audio-bug-on-android-12/92932/180 "2023-05-11T08:58:35Z")

</div>

> [@yvmuell](#):
>
> A bug that was causing the Bluetooth audio to stop working **when the aptX HD** codec was selected, has been fixed.

 ![Screenshot_20230511-105559](https://forum.fairphone.com/uploads/default/original/3X/a/4/a411970e685864f94c80c6c01c6ddfe30dd67706.png)

> [@Spongebob](#):
>
> Where does it say that only PART of the problem should be solved?

No one says is should only, the only I said is, it was only…

---

<div class="post-metadata">

**Author:** ![Spongebob](https://forum.fairphone.com/user_avatar/forum.fairphone.com/spongebob/32/34780_2.png) [@Spongebob](https://forum.fairphone.com/u/Spongebob)\
**Post date:** [May 11, 2023, 10:41am UTC](https://forum.fairphone.com/t/bluetooth-audio-bug-on-android-12/92932/181 "2023-05-11T10:41:04Z")

</div>

We need a solution to the problem for our headphones!  
Completely independent of which version aptx is required. The feature was available in Android 11.

I really have the impression that only aptx HD protocol was fixed because the new Fairphone XL headphones support this feature. So far, this is the only bug that was fixed directly after the Android 12 update.

[Fairbuds XL: Fairphone bringt reparier­baren, mo­du­laren ANC-Kopf­hörer - ComputerBase](https://www.computerbase.de/2023-05/fairbuds-xl-fairphone-bringt-den-reparierbaren-modularen-anc-kopfhoerer/)

> Als Audio-Codec werden AAC, SBC und aptX HD geboten – uneingeschränkter HD-Klang wird somit nicht plattformunabhängig geboten, ein freier HD-Codec nicht unterstützt.

---

<div class="post-metadata">

**Author:** ![user0815](https://forum.fairphone.com/letter_avatar/user0815/32/6_449c533f586939b6e5f246632a46421f.png) [@user0815](https://forum.fairphone.com/u/user0815)\
**Post date:** [May 14, 2023, 5:28pm UTC](https://forum.fairphone.com/t/bluetooth-audio-bug-on-android-12/92932/182 "2023-05-14T17:28:49Z")

</div>

Have you tried to re-do the bluetooth pairing (i.e., in Android Settings, list the previously connected devices. Click on the gear icon, then on the trash symbol (English label: “Forget”). Then pair your bluetooth device again.

This step was necessary for me after the latest update (Build number `FP4.SP28.B.065.20230420`) with my Sony WH 1000 XM3, now they are working fine. Please note that they are using aptX HD, not aptX.

---

<div class="post-metadata">

**Author:** ![Kruse](https://forum.fairphone.com/letter_avatar/kruse/32/6_449c533f586939b6e5f246632a46421f.png) [@Kruse](https://forum.fairphone.com/u/Kruse)\
**Post date:** [May 16, 2023, 5:09pm UTC](https://forum.fairphone.com/t/bluetooth-audio-bug-on-android-12/92932/183 "2023-05-16T17:09:56Z")

</div>

High togerher, my FP4 worked well with my son’s JBL Bluetooth Headphones. Now I got Sennheiser Momentum True Wireless 3 (AS a birthday-present) and have an interesting phenomenon: I can use the earphones for phonecalls but not for listening to music. The Sennheiser- App says “Codec: keine Audioübertragung”. Strange… Have you got a hint how to solve it??

[Previous page](https://forum.fairphone.com/t/bluetooth-audio-bug-on-android-12/92932.md?page=8)

[Next page](https://forum.fairphone.com/t/bluetooth-audio-bug-on-android-12/92932.md?page=10)
