Bluetooth problems since Android 15 update

Since updating to Android 15 I have found that Bluetooth is causing problems especially with audio playback to a Bluetooth device.

Each time playing an album when moving to the next track play stops. I have to disconnect the Bluetooth device, start audio playback on phone then reconnect the Bluetooth device.

Has anyone else had this problem or know a solution?

Which app do you use for audio playback?

1 Like

I’ve tried BubbleUPNP and Hi-Fi Cast. Both exhibit the same problem.

Could you try the app VLC?

1 Like

VLC does appear to work. However VLC itself seems to be a bit problematic in that it wont scan my music server properly and it stopped playing local music files when focus was taken by my web browser.

This is a different issue to the Bluetooth audio though.

It could be a similar issue to that seen with FP5 when it moved to A15. See this post

I’m also having major Bluetooth problems on my Fairphone 4 since updating to Android 15 with my medical devices (Freestyle Libre, MedTrum Nano Touchcare).

The corresponding apps (LibreLink and EasyPatch) are allowed to run in the background.

The only way I’ve found to temporarily restore connectivity with these devices is to restart my phone. But the connection drops again after a few minutes.

I opened a support ticket over 10 days ago, but I still haven’t received any response.

4 Likes

I have the same issue with my Freestyle Libre 2.

Any update on this?

I am switching to Diaexpert sensors. The hospital gave me 1 to try and works much more reliable. But I still have like 8 of those Libre sensors :frowning:

1 Like

Same issue here with Freestyle Libre 2 and the official LibreLink app. I can scan the sensor with NFC (although the scanning often takes several tries), but connecting over bluetooth fails.
I also tried using Juggluco but get the same results — NFC works, bluetooth doesn’t :frowning:

2 Likes

A post was split to a new topic: After upgrade to Android 15 I can’t stream my amplifon ear divices

Have you tried :

Settings of LibreLink > Battery Usage > Click on the “Allow Background Execution” > Unrestricted

I also found in developers mode :

“Bluetooth search” : reactivate the option if it’s off

All the settings are already configured as you described.

Have you seen this post :

Could you try and tell if this works also for you ?

What worked for me was downgrading to Android 13 which was a hassle as everything is wiped in the process but it was worth it. For @Fairphone_CM sustainability is not just about hardware but perhaps the software is even more important. I personally won’t think I will buy anything from Fairphone again. Even the Fairbuds I have bought
 the software is (equalizer etc) really terrible. The hardware is fine.

Thank you so much for this procedure.

I have tried it, here’s my feedback:

  • step 3 (“Commands 3”) : following command do not work :

adb shell pm grant com.freestylelibre.app.fr android.permission.POST_NOTIFICATION

adb shell pm grant "$package" android.permission.POST_NOTIFICATION

Exception occurred while executing 'grant':
java.lang.IllegalArgumentException: Unknown permission android.permission.POST_NOTIFICATION

No execution problem with others commands

But, I still have same Bluetooth deconnection problems

Just posted it in another thread: the adb so far did not work for me, but still looking - there seems to be a typo in the original post - as far as I found out, the correct call is

android.permission.POST_NOTIFICATIONS

(extra ‘S’ at the end) good luck!

Is anybody test FP4.SREL.15.14.4 released 06 January 2026?

If yes, does it fix this issue ?

Hi jycr,

as this update is announced just as a security update, there should be no fix regarding bluetooth problems included. There was no report about changed behavior in bluetooth connections after installing this patch. See also

Greets Robert

2 Likes

Not sure if it is bluetooth related, but with Android Auto I now often have disconnects or short interrupts.

Here is what I found out debugging an issue when trying to connect Meta Glasses to the Fairphone 4:

Bug Report: BLE L2CAP COC Connection Failure on Fairphone 4 with Android 15

Details

Summary

BLE L2CAP Connection-Oriented Channel (COC) connections fail on Fairphone 4 running Android 15. The secure L2CAP data channel times out after 30 seconds, preventing companion apps from completing pairing with BLE accessories. This is a regression from Android 13 where the same device and accessories worked correctly.

Device Information

  • Device: Fairphone 4 (FP4)
  • Android Version: 15
  • Security Patch: 2026-01-05
  • Hardware: Qualcomm (ro.hardware=qcom)
  • Bluetooth Stack: Qualcomm proprietary (android.hardware.bluetooth@1.0-service-qti)

Affected Accessory

  • Device: Meta Ray-Ban Smart Glasses (Wayfarer)
  • Model: RB Meta 01N3
  • Bluetooth: Dual-mode (BLE + BR/EDR)
  • BLE Service UUID: 0000fd5f-0000-1000-8000-00805f9b34fb
  • L2CAP PSM: 129 (0x81) - Secure LE COC

Problem Description

When attempting to pair Meta Ray-Ban glasses via the Meta AI app (com.facebook.stella), the BLE GATT connection succeeds but the L2CAP COC connection fails. The connection attempt times out after exactly 30 seconds.

What Works

  • BLE scanning and discovery
  • BLE GATT connection
  • GATT service discovery
  • MTU negotiation (517 bytes)
  • PHY update (2M PHY)
  • System Bluetooth bonding (DUAL mode)
  • Companion Device Manager association
  • A2DP audio streaming (Spotify works through glasses)

What Fails

  • L2CAP COC connection to PSM 129
  • Meta AI app cannot complete pairing handshake
  • Camera streaming and smart features unavailable

Technical Analysis

Socket Events from dumpsys bluetooth_manager

00:01:08.669  xx:xx:xx:xx:29:67  STATE_CONNECTING    ROLE_CONNECTION  129  L2CAP_LE
00:01:38.672  xx:xx:xx:xx:29:67  STATE_DISCONNECTING ROLE_CONNECTION  129  L2CAP_LE
00:01:38.672  xx:xx:xx:xx:29:67  STATE_DISCONNECTED  ROLE_CONNECTION  129  L2CAP_LE

The connection stays in STATE_CONNECTING for exactly 30 seconds before timing out.

Logcat Errors

E BleConnection-Supernova: Failure to connect to l2cap
E BleConnection-Supernova: com.facebook.wearable.connectivity.bluetooth.api.BleL2CapException: Unable to connect to l2cap
E BleConnection-Supernova: Caused by: android.bluetooth.BluetoothSocketException: A Bluetooth Socket failure occurred
E BleConnection-Supernova:     at android.bluetooth.BluetoothSocket.connect(BluetoothSocket.java:475)
I ConnectivityStartupLogger: markConnectionAttemptPoint CONNECT_L2CAP_FAILED
I BluetoothAdapterService: Statslog L2capcoc client connection. metricId 24 port 129 isSecured true result 0 endToEndLatencyMillis 30011 socketCreationLatencyMillis 0 socketConnectionLatencyMillis 30010

Bluetooth Stack Details

I BtSocketManagerBinder: connectsocket: device=XX:XX:XX:XX:66:9D, type=4, uuid=00000000-0000-0000-0000-000000000000, port=129
I bt_btif_sock: btsock_connect: Attempting socket connection for device: xx:xx:xx:xx:29:67, type: 4, channel: 129
I bluetooth: btsock_l2cap_alloc_l: Allocated l2cap socket structure
I bt_l2cap: L2CA_RegisterLECoc: Registered service LE COC PSM: 0x0081

Root Cause Analysis

Based on research (Google Issue Tracker #371713238), the Android Bluetooth stack sends L2CAP extended flow control packets and blocks waiting for a response. Some BLE devices (including Meta glasses and AirPods) do not respond to these packets, causing the connection to hang until timeout.

The problematic code is in:

  • system/stack/l2cap/l2c_link.cc (line 118)
  • system/stack/l2cap/l2c_fcr.cc (lines 1605-1610)

Attempted Workarounds (All Failed)

Workaround Result
Grant all location permissions Required but not sufficient
Factory reset glasses No effect
Clear app data and bonds No effect
Toggle Bluetooth off/on No effect
Adjust BLE scan parameters No effect
device_config L2CAP flags Cannot persist without root
Disable A2DP hardware offload No effect
Change AVRCP version (1.4) No effect
Change MAP version (1.2) No effect

Device Config Flags Examined

com.android.bluetooth.flags.bt_socket_api_l2cap_cid=false
com.android.bluetooth.flags.higher_l2cap_flush_threshold=false
com.android.bluetooth.flags.l2cap_le_do_not_adjust_min_interval=false
com.android.bluetooth.flags.l2cap_p_ccb_check_rewrite=false
com.android.bluetooth.flags.l2cap_tx_complete_cb_info=false

These flags cannot be modified without root access.

Regression Information

  • Working: Android 13 on the same Fairphone 4
  • Broken: Android 15 on the same Fairphone 4
  • Same accessory: Meta Ray-Ban glasses worked on Android 13

Impact

  • Users cannot pair BLE accessories that require L2CAP COC data channels
  • Affects Meta Ray-Ban glasses, likely AirPods, and other BLE accessories
  • Smart features requiring data transfer are completely non-functional
  • Basic audio (A2DP) works, but companion app features do not

Related Issues

  • Google Issue Tracker #371713238: L2CAP extended flow control packet blocks socket
  • Google Issue Tracker #36976247: Support Bluetooth L2CAP
  • Fairphone Forum: Bluetooth problems since Android 15 update

Bluetooth problems since Android 15 update

  • LibrePods GitHub Issues:
    #232: L2CAP Connection Fails on Fairphone 5
    #229: L2CAP Connection Fails on Pixel 7a

Suggested Fix

Per Google Issue #371713238, the fix requires modifying the Bluetooth stack to:

  1. Not block when sending extended flow control packets
  2. Return gracefully if no response is received from the peer device
    Temporary workaround (requires root): Comment out the extended flow control checks in l2c_fcr.cc and rebuild libbluetooth_jni.so.

Steps to Reproduce

  1. Use Fairphone 4 with Android 15
  2. Install Meta AI app (com.facebook.stella)
  3. Factory reset Meta Ray-Ban glasses
  4. Open Meta AI app and initiate pairing
  5. Glasses appear and GATT connects
  6. Observe pairing stuck at “connecting” for 30+ seconds
  7. Pairing fails with L2CAP connection error

Expected Behavior

L2CAP COC connection should establish within a few seconds, allowing the companion app to complete the pairing handshake.

Actual Behavior

L2CAP COC connection times out after 30 seconds. App reports pairing failure despite successful GATT connection and system-level Bluetooth bond.

Attachments

Logcat output and dumpsys bluetooth_manager output available upon request.

just to make that clear, you cant send bug reports to FP using the forum.