linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Pali Rohár" <pali.rohar@gmail.com>
To: ofono@ofono.org, Denis Kenzior <denkenz@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: HSP/HFP ofono bluetooth support for Linux desktop
Date: Wed, 8 Jan 2020 12:40:59 +0100	[thread overview]
Message-ID: <20200108114059.fbypyps6f3nb4ckv@pali> (raw)
In-Reply-To: <20200107192311.efit6zftt27encdc@pali>

CCing also bluez developers as they may be interested in discussion how
is HSP/HFP going to be implemented and used on Linux desktop.

On Tuesday 07 January 2020 20:23:11 Pali Rohár wrote:
> Hello!
> 
> Denis wanted from me to start a new thread, so I'm doing it.
> 
> As I wrote in different thread current state of HSP and HFP bluetooth
> profiles on Linux desktop is in very bad state, specially usage of SCO
> audio connection for audio applications (e.g. pulseaudio). See all
> details in that email. I proposed a solution for it via hsphfpd daemon
> with its prototype implementation, but Denis wrote that ofono could be a
> better solution.
> 
> Part of HSP and HFP bluetooth profiles is AT socket connection which
> needs to handle, parse and interpret all needed AT commands.
> 
> ofono project seems to be a candidate for handling AT socket on Linux
> desktop, but in current state it is unusable. For audio application
> (pulseaudio) there are required following features which ofono currently
> missing:
> 
> * ability to connect HFP profiles in HF role without any modem
>   (desktop computers do not have to have any modem). ofono currently
>   does not support establishing HFP connection in HF role when computer
>   does not have any modem
> 
> * support for HSP profiles (in both HS and AG roles). ofono currently
>   does not support HSP profile at all
> 
> These two missing features are main blockers why ofono is unusable for
> desktop/laptop usage as AT parser/handler for bluetooth HSP/HFP
> profiles.
> 
> Denis wrote that fixing first issue would be possible by automatically
> registering some fake dummy modem (when there is no in system) and
> connecting it with HFP profile in HF role.
> 
> Do you have a reasonable solution also for second issue?
> 
> If above two issue could be solved I can write a list of all other
> issues which are needed to be solved for providing HSP/HFP support on
> Linux desktops.
> 

-- 
Pali Rohár
pali.rohar@gmail.com

       reply	other threads:[~2020-01-08 11:41 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20200107192311.efit6zftt27encdc@pali>
2020-01-08 11:40 ` Pali Rohár [this message]
     [not found] ` <721332d3-336a-b9d2-f8cd-72da785fb9dc@gmail.com>
2020-01-08 21:25   ` HSP/HFP ofono bluetooth support for Linux desktop Pali Rohár
2020-02-09 13:15     ` Pali Rohár
2020-02-12 21:29     ` Denis Kenzior
2020-02-13 17:46       ` Pali Rohár
2020-02-13 18:14         ` Denis Kenzior
2020-02-13 18:32           ` Pali Rohár
2020-02-13 19:08             ` Denis Kenzior
2020-02-13 19:15               ` Pali Rohár

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200108114059.fbypyps6f3nb4ckv@pali \
    --to=pali.rohar@gmail.com \
    --cc=denkenz@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=ofono@ofono.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).