Bluetooth for phone calls

[Stray]

I've had my PinePhone Pro for a few months, and tinker with it on occasion, mostly trying to get my Bluetooth headsets to work with it. I can get the phone to output media, and even the recorder does pickup the microphone when I set the audio profile to HFP. However, when I make a phone call, it reverts back to using the phone's speaker and microphone. The past 2 days I have been really trying hard to force it, with the help of ChatGPT, and deciphering the differences it was advising me to do to the device (such as telling me to restart Pipewire service using systemctl when it should be rc-service in the case of using PostmarketOS). I have searched, and thought I would get the PineBuds, but I don't want to get them if it's not going to work, considering I don't really like earbuds, but I would deal with it if it worked. In my searches, I have seen a lot of people are happy with their PineBuds, but they all mention just media playback, no mention of making phone calls (unless I'm not searching in the right places?) I've been using it lately just as a glorified music streamer connected directly to my trucks aux input, but I would actually like to use it, as a phone, and Bluetooth connectivity is very important to me as I am a truck driver, and spend most of my day driving. A wired headset does work as it should, but I would much rather not have a wire dangling limiting my maneuverability, or having the wire in my field of view (I have my existing phone on a mount on the top shelf above the windshield, so if I daily the PinePhone, it would go in that spot).

So, my question is, are there any reports of working Bluetooth headsets that work for calls on any OS? I have tried PostmarketOS (with plasma-mobile, as Plasma is my preferred DE), Mobian (Phosh and Plasma), Arch (Phosh), Ubuntu Touch, Manjaro, and the factory installed SailfishOS (although, not very thoroughly as for some reason or another it won't accept my APN settings for AT&T, so that was a quick jump off)

[mikehenson]

(although, not very thoroughly as for some reason or another it won't accept my APN settings for AT&T, so that was a quick jump off)

1. AT&T has a white list for phones. The PinePhone/PinePhonePro only shows up as an EG25 modem. Years ago, I had AT&T and was told they can not throttle/control the EG25 modem. So they kicked my pinephone off their network. I suggest moving to T-Mobile or a virtual network that uses T-Mobile.

A wired headset does work as it should, but I would much rather not have a wire dangling limiting my maneuverability, or having the wire in my field of view.

2. I have a pinephone pro and I have not tried to setup Bluetooth. I would look into this post and mess with the VoiceCall.conf file to see it you can make it go to Bluetooth.

[Stray]

1. AT&T has a white list for phones. The PinePhone/PinePhonePro only shows up as an EG25 modem. Years ago, I had AT&T and was told they can not throttle/control the EG25 modem. So they kicked my pinephone off their network. I suggest moving to T-Mobile or a virtual network that uses T-Mobile.

I've not had any problems at all with AT&T. Phone calls work, data works at full speed on LTE when compared to my LTE hotspot. In fact, it seems to have better signal out on the road than my Pixel 8 Pro (but I feel that is actually a 5G problem as I had the same problems with a 5G hotspot and it all went away when I got my LTE hotspot). Seems to be a configuration problem with SailfishOS. It doesn't accept the APN settings, or it pretends to accept them but quietly errors out, and when attempting to connect, it just gives me an endless loop of attempting.

2. I have a pinephone pro and I have not tried to setup Bluetooth. I would look into this post and mess with the VoiceCall.conf file to see it you can make it go to Bluetooth.

I will give that a go and see if I can make it work with Bluetooth, but that post is about connecting the 3.5 mm plug, which I have no issues with.

Thank you for your reply.