03-20-2024, 01:59 AM
JohnA, I'm sorry I didn't answer sooner, I'm pretty swamped.
Yes, exactly. I've got a bluetooth device paired with the pinephone. You dial the number on the device, it signals the pinephone, the pinephone makes the call as if you had dialed the number on it, but you don't have to touch the pinephone at all.
Assuming someone answers at the called number, you should be able to talk through the device. Instead the audio never gets routed over bluetooth so you have to pickup the pinephone to carry on the conversation (which mostly defeats the purpose). Then you can hangup via the device and the pinephone ends the call.
From the other direction, someone can call, the pinephone signals the bluetooth device which rings. You pickup using the bluetooth device, but again the audio doesn't get routed so you have to pick up the pinephone to carry on the conversation, (again defeating the purpose).
This all works perfectly on android. All you have to do is pair the phone with the device and the rest is automatic.
It's been quite a while since I've messed with this but as I remember, all of the signaling between the phone and the bluetooth device are supposed to be handled by AT signals (See https://dylanvanassche.be/blog/2022/blue...ux-mobile/ reference in this thread https://forum.pine64.org/showthread.php?...etooth+hfp) and I think all of that is probably working. Just the audio rerouting over bluetooth isn't working.
It was all supposedly in pulse audio, but my understanding of the audio systems is very minimal and I could never get it to work. It is also supposedly in pipewire/wireplumber, which I got to work only as far as I describe above. I'm convinced it would be trivial to fix for someone familiar with either of those systems, but they would have to work out the specific configuration for the pinephone or pro. As far as I understand it, the configuration details will be different between the two.
No special package. Everything is handled by the bluetooth system and the audio system. But it is so abstracted and so poorly documented I gave up trying to figure it out. I'm running a pretty old version of Mobian. It's stable for what I need so I've not wanted (or had time) to mess with it until I see that there is a solution to this in some newer version or other OS.
It sounds like you could easily minimize whatever load your approach has if needed. I can certainly understand the advantages for debugging and generally leaving it as is unless you had time or a good reason to change it.
Quote:but are you saying you can type in the number to call from an external bluetooth device?
Yes, exactly. I've got a bluetooth device paired with the pinephone. You dial the number on the device, it signals the pinephone, the pinephone makes the call as if you had dialed the number on it, but you don't have to touch the pinephone at all.
Assuming someone answers at the called number, you should be able to talk through the device. Instead the audio never gets routed over bluetooth so you have to pickup the pinephone to carry on the conversation (which mostly defeats the purpose). Then you can hangup via the device and the pinephone ends the call.
From the other direction, someone can call, the pinephone signals the bluetooth device which rings. You pickup using the bluetooth device, but again the audio doesn't get routed so you have to pick up the pinephone to carry on the conversation, (again defeating the purpose).
This all works perfectly on android. All you have to do is pair the phone with the device and the rest is automatic.
It's been quite a while since I've messed with this but as I remember, all of the signaling between the phone and the bluetooth device are supposed to be handled by AT signals (See https://dylanvanassche.be/blog/2022/blue...ux-mobile/ reference in this thread https://forum.pine64.org/showthread.php?...etooth+hfp) and I think all of that is probably working. Just the audio rerouting over bluetooth isn't working.
It was all supposedly in pulse audio, but my understanding of the audio systems is very minimal and I could never get it to work. It is also supposedly in pipewire/wireplumber, which I got to work only as far as I describe above. I'm convinced it would be trivial to fix for someone familiar with either of those systems, but they would have to work out the specific configuration for the pinephone or pro. As far as I understand it, the configuration details will be different between the two.
Quote:Which app is doing this? Are there details of the installation anywhere?
No special package. Everything is handled by the bluetooth system and the audio system. But it is so abstracted and so poorly documented I gave up trying to figure it out. I'm running a pretty old version of Mobian. It's stable for what I need so I've not wanted (or had time) to mess with it until I see that there is a solution to this in some newer version or other OS.
It sounds like you could easily minimize whatever load your approach has if needed. I can certainly understand the advantages for debugging and generally leaving it as is unless you had time or a good reason to change it.