Since iodé 6.7 I have heavy problems using headphones via the audiojack on the Fairphone 3. When receiving or making calls having the headphones plugged in, the phone soft reboots. This is reproducible and sometimes even results in a boot loop until I remove the headphones.
I also realised that the music app displays another name for the headphone device when playing audio. It used to be something like “Headphones” (not sure, but it was human readable), now it says “h2w”. Maybe that hints somewhere.
I had already problems on iodé 6.6 when using headphones while calling. Sometimes (I think when the headphones were plugged in while the phone was booting) the speaker was turned on by default when getting calls and the headphones were not connected when the call started. It was not possible to turn the speaker off. Only a reboot resolved the situation. Plugging in the headphones also worked.
Does anyone have similar problems? Currently, I cannot make calls using headphones which is very inconvenient.
I have a brax3 running v6.7 with a wired headphone port, and just successfully placed a call with a wired headset with no issues. So this may possibly be a FP3 only issue, I am going to add that to the title (thanks for adding the tag already).
Was this working fine under v6.6 (and / or earlier builds)?
A developer did reply they don’t have any issue on their FP3 with iodé 6.8 (beta) and making wired headset phone calls. I don‘t think anything changed between 6.7 and 6.8 however, so it is hard to say why you are experiencing the issue, but possibly the 6.8 update will magically fix it? It is in beta now, out soon to stable.
I’ve installed 6.8 and had still the same problem. I now tried a different set of headset and surprisingly it worked. I couldn’t it imagine being a hardware issue since listening to music worked. But maybe the mic is broken and then causes the soft reboot.
So problem solved, sorry for causing noise.
Well I am glad you “solved it”, it is a very surprising bug, but yes possibly hardware related. Possibly there was a broken wire in the headset causing a short / surge or something along those lines? Anyway, once again I am glad that you found a solution.