Hello, when I start pulseaudio I get this error: > org.freedesktop.DBus.Error.UnknownMethod: Method "Register" with > signature "oay" on interface "org.ofono.HandsfreeAudioManager" doesn't > exist

I'm running ofono 1.17 and pulseaudio 8.0. Please, would you help me to understand if the problem is related to the compilation of ofono or to the dbus policies?

Il 12/05/2016 16:09, Denis Kenzior ha scritto: > Are you running BlueZ 5 on your system? This interface is only > available if BlueZ5 support has been enabled. E.g. > plugins/hfp_ag_bluez5.c or plugins/hfp_hf_bluez5.c I found the problem: there was a dependency from bluez4 instead of bluez5 and then the it was compiled with --disable-bluetooth. Now the error about the dbus is gone! Thanks for putting me on the right direction. I also verified now the phone is connecting also for headset. But where I can find the documentation about ofono? I mean, where I can learn how to receive and make calls, etc...

For example: I want to make a call. I need to enable the modem first or I can just dial the number? It is just an example to explain my difficulties to understand how to use ofono!

There isn't an in-depth tutorial available unfortunately. If someone wants to contribute it to the project, that would be appreciated.

So roughly: test/enable-modem test/online-modem test/dial-number test/hangup-call

argument: ""). I: [pulseaudio] module.c: Loaded "module-bluetooth-policy" (index: #12; argument: ""). I: [pulseaudio] module.c: Loaded "module-bluez5-discover" (index: #14; argument: "headset=auto"). I: [pulseaudio] module.c: Loaded "module-bluetooth-discover" (index: #13; argument: "headset=auto"). I: [pulseaudio] main.c: Daemon startup complete. I: [pulseaudio] card.c: Created 2 "bluez_card.08_FD_0E_5A_90_3B" W: [pulseaudio] core-error.c: Unable to convert error string to locale, filtering. E: [pulseaudio] backend-ofono.c: Deferred setup failed on fd -1: Transport endpoint is not connected

Il 14/05/2016 22:43, Stephan Schmolke ha scritto: > > Hi, > > I assume you don't hear the audio on your PC. It's been 3 years since > I last used ofono but at that time it was necessary to create a > loopback connecting your Bluetooth audio sink and your audio sink > (e.g. speakers) so that the incoming audio is routed to your speakers > or headphone. > If I understand correctly you're saying the "Transport endpoint not connected" error is not significant, because I manually need to create a loopback? I understand are the pulseaudio modules which should create the loopback automatically, shouldn't they?

For me the integration of bluez5/pulseaudio/ofono is very hard. Is there any alternative? Or there are any companies which offer a technical support?

Thanks Marco _______________________________________________ ofono mailing list ofono(a)ofono.org https://lists.ofono.org/mailman/listinfo/ofono

Il 15/05/2016 12:32, Georg Chini ha scritto: > Yes, loopback modules are created automatically. The error message > you are getting is relevant, > but the problem is rather somewhere on the bluetooth side. From my > experience the fact that > you get A2DP connected does not mean that HFP is working as well. > Take a look at the debug > logs of ofono, pulseaudio and bluetoothd and at the dbus messages > that are passing between > the different components. Maybe you'll find a hint there what is > going wrong. I sent the logs on the pulseaudio mailing-list. Unfortunately I haven't enough knowledge to understand what's happening. I will try again to get fresh logs and I will post them here.

> Did you set headset=ofono for module-bluetooth-discover? Yes, I did _______________________________________________ ofono mailing list ofono(a)ofono.org https://lists.ofono.org/mailman/listinfo/ofono

Il 15/05/2016 12:39, Georg Chini ha scritto: > I've only seen the pulseaudio logs. ofono and bluetoothd also might > provide some information. > Try also dbus-monitor --system. You should see the messages passing > between the components. Attached there are all the logs: - pulseaudio - bluez - dbus - ofono I also attached the dbus policy configuration - perhaps there is something wrong there. What I did: 1. launched all services: dbus, bluetooth, ofono, pulseaudio 2. connected the phone for both a2dp and hfp profiles 3. from ofono/test: a) enable-modem b) online-modem c) dial-number What happened: - the phone recognized both bluetooth profiles (it said: connected to multimedia audio and phone) - when I dialed the number, the phone actually made the call - the bluetooth audio icon on the phone was highlighted - but the audio was coming from the phone's speakers About the last point: sometimes (but I really don't know when) I don't hear nothing, neither from the phone nor from the raspberry. Other times (like now) the audio is coming from the phone. Thank you for you support Marco

Of course! I added the linne, rebooted and followed again the procedure. It seems the errors are still there.

Did you try to run pulseaudio as normal user? You should avoid system mode if possible. It still looks like there is something wrong with your dbus access rights, this time the reply from pulseaudio is denied.

Maybe you could try and add something like <policy user="pulse"> <allow send_destination="org.ofono"/> </policy> to your ofono.conf, but that is just a wild guess. I am not too familiar with dbus.

Not sure if the other daemons must be run as root, but at least it works for me to start ofono and bluetooth during system startup and run pulseaudio as a normal user (not as user pulse)

To me it still looks like this is an issue with your dbus access rights. Everything else looks fine - even the loopback modules are loaded but don't receive / send any audio.

Something else I noticed: It looks like you can't get high priority and also no timer based scheduling for pulseaudio. This means that your audio quality will probably be really bad.

Also there are lots of other errors in the PA log. It seems that there is still something broken in your build. Or is that due to the embedded system?

Might be missing dependencies, see above, then it is not only configuration.