Indeed, @yvmuell. It’s just occurred to me on A14 too:
Additionally, I’ve been contacted by Fairphone, so it’s being officially investigated. If I’m informed that a solution has been located, I’ll post that one has, and mark that post as the solution of the thread.
@UPPERCASE, perhaps this should be added to ✏ Known reproducible and reported issues of the Fairphone 5? It seems improbable that this affects solely @yvmuell and I. Or does reproducibility need to be more specific than “connect Bluetooth device and wait”?
You dont need permission to add to the list you can just add it.
As long as it is reproducible and confirmed by multiple people. The list needs to be of high quality and not simply a wall of shame 
I haven’t followed this thread in detail. But if it’s really just the 2 of you but you can reliably reproduce it, then sure add it. The topic includes details about the conditions for an issue to be added. It’s also important to make sure it’s really a FP issue, not an app or peripheral device. That’s the idea of that list anyway. Other lists can be created if people don’t agree with setting the bar high 
Thanks, @UPPERCASE. I’ll add it when I or @yvmuell have got a logcat that they confirm is useful, then.
Hello,
When I connect my FP5 to a bluetooth device, this works fine. However, when I disconnect it, the speakers don’t work anymore. The mediaplayer (Spotify in this case) still shows that there is a connection to the bluetooth device. Even when I turn of bluetooth the speaker doesn’t work, and the mediaplayer still shows the bluetooth connection.
I’ve observed this behavior with multiple mediaplayers.
When I get a call the speaker is just working fine…
Any ideas?
Thanks!
Pascal.
I have the same issue… except that in my case it is the connection with my car.
So if I use the Bluetooth on my car, I’m forced to reboot my phone almost every day after driving to work.
If someone know a solution to this, I’d be very greatful 
Would this be the same as described here?
It’s the same problem and I have the latest update.
I have contacted support, since it is a very annoying issue, which makes me have to reboot almost every day.
Ok merged the topics
@TurboMcK and @Swamper, since you too can reproduce this, are you able to do so, then provide a sample of your logcat log (via adb) to Support? They really need it, since they and I have not been able to consistently reproduce it thus far.
Unless you want to send it directly to Support (which is probably best) you can post it here as a <pre> with:
```log
content
```
…and I’ll forward it.
I’ll do that the next time it happens, when I have the time.
I have an update on this. I’ve found what triggers the issue (but haven’t had the time to gather the logs yet).
This happens when I switch from bluetooth earphones to the bluetooth connection in the car, during a call. I’m not sure yet if the trigger only happens during the switch or if me leaving the car, get disconnected from the car while talking on the phone, triggers this.
Hi! The problem has been really persistent for a while… And then it disappeared (and I completely forgot about it…). I haven’t experienced the issue for a while, but reading about the trigger below, I’ll see if I can reproduce it. If so, I’ll forward the logs.
@TurboMcK, likewise. And, of course, it disappeared just as I was finally ready to diagnose it.
I experience the same problem on FP4 with Android 13.
Can anyone help provide instructions on about how to do help provide this?
“a sample of your
logcatlog (viaadb) to Support?”
-Mikkel
@mikkelhegn, it’s less complex than you expect, for us lay men aren’t expected to be able to parse logcat to extract the relevant logs.
All you need to do is:
logcat in a terminal on the host (if you use something like logging - Android adb logcat time filter - Stack Overflow, it will only show the logs after the time when you noticed the issue happening – give a few minutes of leeway, though).The way that I recommend you create your ticket is to file a genuine support request for the issue in the OP, and then respond to it with that log. That means that it can be easily triaged as a duplicate of our tickets to Support, without them accidentally ignoring the subsequent log.
Have you been able to consistently reproduce it?
I suggest to not further mix here FP4 and FP5 please.
@mikkelhegn please use the reply in linked topic feature and open a post in the FP4 category
Thank you for the details @rokejulianlockhart.
I’m not aware what an AOSP device is, can you explain? Also what tooling I need to be able to use logcat. I’ll go ahead and open a support ticket and follow the instructions which will be provided there.
I have experienced this twice recently, but does not have a consistent repro.
@mikkelhegn, apologies. I just meant Android. I forget to change terminology for this forum. It means Android Open Source Project.
The most convenient way is always the Android Debug Bridge (ADB) toolset, but what OS do you use? The installation method differs per OS.
Likewise. :<
