Open Source Telephony
 help / color / mirror / Atom feed
From: Georg Chini <georg@chini.tk>
To: ofono@ofono.org
Subject: Re: ofonod crashes during enable-modem.py
Date: Mon, 02 Feb 2015 16:35:24 +0100	[thread overview]
Message-ID: <54CF993C.5070307@chini.tk> (raw)
In-Reply-To: <54CF983B.8070203@chini.tk>

[-- Attachment #1: Type: text/plain, Size: 2642 bytes --]

On 02.02.2015 16:31, Georg Chini wrote:
> Hello Norbert,
>
> you should be using pulseaudio from the current git. Pulseaudio 
> version 5.0 and
> below do not support HFP in combination with Bluez5. I am running 
> Bluez 5.23 from
> Debian unstable and a recent ofono and pulseaudio compiled from 
> source. This
> works fine for my mobiles.
>
> Regards
>              Georg
>
> On 02.02.2015 16:10, Denis Kenzior wrote:
>> Hi Norbert,
>>
>> Please don't top-post on this mailing list.  That's just our 
>> convention here.  Anyway, see below:
>>
>> On 02/01/2015 08:00 AM, Norbert Huffschmid wrote:
>>> Hi Denis,
>>>
>>> now I have installed ofono from the debian jessie testing branch (which
>>> has packaged ofono 1.15-2). Bluez is still version 4.99 and all the 
>>> rest
>>> is debian wheezy as before. Now the list-modems.py script does not show
>>> any modem any more. Are there dependency issues?
>>>
>>
>> BlueZ4 requires --with-bluez4 when configuring oFono.
>>
>>> I already had tried a combination of ofono 1.15-2 and Bluez 5.23, which
>>> was quite promising. I could successfully establish a phone call by
>>> means of the dial-number.py script. But there was no voice connection
>>> established between the endpoints. This was quite astonishing because
>>> A2DP streaming from the smartphone to the Raspberry Pi worked like a
>>> charm. And I don't think that it was a phone issue because a HFP
>>> connection from the phone to a navigation device works well too.
>>>
>>
>> oFono and BlueZ are not the only ones at play.  The audio is handled 
>> by PulseAudio.  So I would check on the PulseAudio mailing list which 
>> version of PulseAudio you need.
>>
>>> I have read somewhere that Bluez5 does not support HFP at all, so I did
>>> not further follow this approach.
>>
>> Correct, sort of.
>>
>>>
>>> Any proposal which combination of ofono and Bluez is most promising in
>>> order to establish a HFP voice connection?
>>>
>>
>> As mentioned before, BlueZ and oFono are not the problem here. Check 
>> back with PulseAudio folks.
>>
>> Regards,
>> -Denis
>> _______________________________________________
>> ofono mailing list
>> ofono(a)ofono.org
>> https://lists.ofono.org/mailman/listinfo/ofono
>
> _______________________________________________
> ofono mailing list
> ofono(a)ofono.org
> https://lists.ofono.org/mailman/listinfo/ofono

Ups, sorry for making the same mistake as Norbert. Anyway, you also have 
to load the
module-bluetooth-discover with the parameter headset=ofono, so add this 
in default.pa

Regards
              Georg


      reply	other threads:[~2015-02-02 15:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-31 16:04 ofonod crashes during enable-modem.py Norbert Huffschmid
2015-01-31 16:22 ` Denis Kenzior
2015-01-31 17:51   ` Norbert Huffschmid
2015-02-01  4:30     ` Denis Kenzior
2015-02-01 14:00       ` Norbert Huffschmid
2015-02-02 15:10         ` Denis Kenzior
2015-02-02 15:31           ` Georg Chini
2015-02-02 15:35             ` Georg Chini [this message]

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=54CF993C.5070307@chini.tk \
    --to=georg@chini.tk \
    --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