On 09.02.2015 10:55, Arun Raghavan wrote: > On 9 February 2015 at 14:54, Georg Chini <georg at chini.tk> wrote: >> On 09.02.2015 10:16, Arun Raghavan wrote: >>> On 9 February 2015 at 14:29, Georg Chini <georg at chini.tk> wrote: >>>> On 09.02.2015 09:28, Arun Raghavan wrote: > [...] >>> If you mean that we need to do AT command handling, we now already do >>> a bit of that in PA (we couldn't really agree upon any other place for >>> that once BlueZ dropped it). Is there much we need to support other >>> than volume commands? >>> >>> Assuming it's not too much more complex than the HSP support, we >>> should be able to manage that just fine by extending the native >>> backend. >> >> For audio you probably won't need much more. But if you do not >> support the telephony functions, you are in the same situation as >> ofono is with the AG role. Here ofono supports the AT commands, >> but no audio, and what use is a headset without audio? >> And if you support audio for a phone but not the telephony functions, >> what is phone audio good for where you can't make or receive a call? > You can receive a call (you don't need the headset functions to accept > one), so we've had users using their computer, their Raspberry Pi, or > other devices for such use cases. > Really? Without using ofono? I wonder how this worked. I did already use ofono with bluez4 and it would not have worked without. Who sends the AT command to accept the call to the phone? Or do I have to pick up manually then?
