On Mon, 2012-01-30 at 08:57 +0100, Mikel Astiz wrote: > > Any idea what might be necessary to get access to the phone book? > > There's nothing in the phone's UI to enable it (Android 2.2, HTC > Sense). > > > > You probably need to connect HFP first, otherwise some phones might > reject the PBAP session. If you're interested, I suggest you try oFono. > Just make sure you have "Enable=Gateway" in /etc/bluetooth/audio.conf > and then you can use ofono/test/enable-modem to connect HFP.
Into which section of /etc/bluetooth/audio.conf does the "Enable=Gateway" belong? My copy of it (4.98-2, Debian testing) doesn't have "Enable" anywhere and at first glance I have also not found any documentation about the config files. The "enable-modem" operations fails for me inside "ofonod -n -d" with ofonod[29960]: plugins/hfp_hf.c:hfp_connect_reply() Connect reply: Method "Connect" with signature "" on interface "org.bluez.HandsfreeGateway" doesn't exist There is indeed no such interface on org.bluez on the system bus. I came back to this as part of adapting the PBAP backend to recent changes on the master branch. Code is in the pbap branch (not rebased, just pull): commit 46d7d344f3692c1ec539d5db54ff6944032ac936 Merge: c12cde0 f345038 Author: Patrick Ohly <[email protected]> Date: Tue Feb 21 14:26:56 2012 +0100 PBAB: Merge branch 'master' into pbap + D-Bus method calls The mechanism for making D-Bus method calls changed on the master branch. The normal call operator now does a blocking method call, which breaks code depending on the former non-blocking semantic. All D-Bus methods calls in the PBAB backend are now blocking. This allows removing all callback methods and the start/stop main loop tricks. A lot easier to read and problems while executing the method calls are now properly reported back to the user of the backend via exceptions. Beware, my changes are untested because I don't have PBAP access working here at the moment. -- Best Regards, Patrick Ohly The content of this message is my personal opinion only and although I am an employee of Intel, the statements I make here in no way represent Intel's position on the issue, nor am I authorized to speak on behalf of Intel on this matter. _______________________________________________ SyncEvolution mailing list [email protected] http://lists.syncevolution.org/listinfo/syncevolution
