maemo.org - Talk - [Announce] Bluetooth PBAP and IrMC / Carkit support is coming to N900...

maemo.org - Talk (https://talk.maemo.org/index.php)

- Applications (https://talk.maemo.org/forumdisplay.php?f=41)

- - [Announce] Bluetooth PBAP and IrMC / Carkit support is coming to N900... (https://talk.maemo.org/showthread.php?t=59114)

Re: [Announce] Bluetooth PBAP and IrMC / Carkit support is coming to N900...

Quote:

Originally Posted by luf (Post 1258197)

Hi,

I was on vacation (and still l'm) but I reach the net now.

obexd-0.46 has some initial support for MAP _but_ there is no support for retrieving folder list, SMS list etc as no support is written for N900. As I wrote:

I'm working on it. Right now I merge all patches regarding MAP support from meego but I have to rewrite it to using rtcom-eventlogger.

So no working MAP support for N900 now.

It's not done. It's planned for next release ;)

excellent work! how do i like this x 1000 times? :)

in the meantime, is there a way to temporarily disable the MAP BT profile? the car pops up an error dialog after a few minutes when trying to retrieve SMSes. not really an issue. i can dismiss the dialog manually but i just have to do it everytime.

anyway, keep it up!!!!

Re: [Announce] Bluetooth PBAP and IrMC / Carkit support is coming to N900...

Quote:

Originally Posted by droll (Post 1258851)

in the meantime, is there a way to temporarily disable the MAP BT profile? the car pops up an error dialog after a few minutes when trying to retrieve SMSes. not really an issue. i can dismiss the dialog manually but i just have to do it everytime.

Hmmm, it should be called bug :(

You can test if the MAP (non working) is enabled:

Code:

# sdptool browse local | grep Message

Service Name: Message Access server

You can disable it in /usr/share/dbus-1/services/obexd.service.
Change the line:

Code:

Exec=/usr/lib/obex/obexd --nodaemon --symlinks --root .obex-root --root-setup /usr/bin/obex-root-setup --capability '!/usr/bin/gen-obex-capability.sh'

Code:

Exec=/usr/lib/obex/obexd --nodaemon --noplugin=mas --symlinks --root .obex-root --root-setup /usr/bin/obex-root-setup --capability '!/usr/bin/gen-obex-capability.sh'

(basicaly add the parameter --noplugin=mas to the obexd)

You have to restart obexd after changing this file (reboot your N900 or kill the obexd and run it under user).

Hope it helps.

Re: [Announce] Bluetooth PBAP and IrMC / Carkit support is coming to N900...

Just upgraded to latest CSSU-T, which has pulled in PBAP support. Is it possible to swap the first/last name order? I have an Abarth with Fiat's Blue&Me system which is storing names as Surname, First Name which is quite unnatural when trying to issue voice commands to it.

Re: [Announce] Bluetooth PBAP and IrMC / Carkit support is coming to N900...

Quote:

Originally Posted by Android_808 (Post 1264897)

Just upgraded to latest CSSU-T

Congrats, you're faster me to announce it :)

Quote:

Originally Posted by Android_808 (Post 1264897)

Is it possible to swap the first/last name order? I have an Abarth with Fiat's Blue&Me system which is storing names as Surname, First Name which is quite unnatural when trying to issue voice commands to it.

I'm sorry I understand what you want but I can't get where it's wrong. Can you please try to debug it a little bit? I want to know if Blue&Me is using PullAll or vCard listing. How to debug obexd is few pages back.

Also good for me is if you're able to use pbap-client (python script so it's arch independent) from obexd-client package like:

./pbab-client <BT addr>

to list your contacts and see if it's ok.

I receive from my N900:
BEGIN:VCARD
VERSION:2.1
UID:26
PRODID:-//Synthesis AG//NONSGML SyncML Engine V3.4.0.27//EN
REV:2012-03-13T15:18:43Z
N:Surname;FirstName;;;
FN:FirstName Surname
NICKNAME:Nick
TEL;PREF:+123456789
ADR:;;;;;;
END:VCARD

And it's what is in specification (from PBAP_SPEC_V11r00.pdf):

Code:

3.1.6.1  Name attribute format

The name attribute of the vCard-listing DTD has the same definition as the name attribute of a vCard - i.e., the N attribute. Therefore, the format to be used is the field structure “LastName;FirstName;MiddleName;Prefix;Suffix”

So I have no clue what should I reverse because it will be againist specification and should broke all other handfree. BTW other phone works well with PBAP phone book and Blue&Me?

Re: [Announce] Bluetooth PBAP and IrMC / Carkit support is coming to N900...

it used to store them the other way before using pbab, so it may be the way its configured in the car so i'll try to test it later. if so, i'll just switch back to the old fashion way (petrovich).

Re: [Announce] Bluetooth PBAP and IrMC / Carkit support is coming to N900...

Quote:

Originally Posted by Android_808 (Post 1265145)

it used to store them the other way before using pbab, so it may be the way its configured in the car so i'll try to test it later. if so, i'll just switch back to the old fashion way (petrovich).

Strange. Do you have to change vcards exported when using Petrovich? Because export vcards should be in the same format as PBAP vcards. Please try to debug the PBAP. Maybe the difference is in VCARD version or something like that.

It would be nice if you can compare some vcard from pbap-client and export for Petrovich if it differs or not.

Re: [Announce] Bluetooth PBAP and IrMC / Carkit support is coming to N900...

Ran pbab-client (from 0.47 package) on my laptop using latest versions from Arch Linux. Had to use python2 pbab-client, to avoid the system default of running v3, as the print function failed due to the syntax changes made in v3.

The only differences running pbab-client for me compared to your results is that the VCARD version is reporting 3.0 and I have no PRODID field. I haven't been able to try Petrovich with the car yet to make sure that is still working as it was previously. I have found that the v-card used by Petrovich, generated by the export contacts feature of Contacts, is different for v2.1. It seems to omit the FN: field. I'll keep testing.

Re: [Announce] Bluetooth PBAP and IrMC / Carkit support is coming to N900...

Quote:

Originally Posted by Android_808 (Post 1265425)

Funny they have to change pbap-client in 0.47:

Code:

#!/usr/bin/python



import sys

import dbus



bus = dbus.SessionBus()



client = dbus.Interface(bus.get_object("org.openobex.client", "/"),

                                                "org.openobex.Client")



print "Creating Session"

session_path = client.CreateSession({"Destination": sys.argv[1], "Target": "PBAP"})

pbap = dbus.Interface(bus.get_object("org.openobex.client", session_path),

                                                "org.openobex.PhonebookAccess")

session = dbus.Interface(bus.get_object("org.openobex.client", session_path),

                                                        "org.openobex.Session")



#paths = ["PB", "ICH", "OCH", "MCH", "CCH"]

paths = ["PB"]



for path in paths:

        print "\n--- Select Phonebook %s ---\n" % (path)

        pbap.Select("int", path)



        print "\n--- GetSize ---\n"

        ret = pbap.GetSize()

        print "Size = %d\n" % (ret)



        print "\n--- List vCard ---\n"

        ret = pbap.List()

        for item in ret:

                print "%s : %s" % (item[0], item[1])

                pbap.SetFormat("vcard21")

#                pbap.SetFilter(["VERSION", "FN", "TEL"]);

                ret = pbap.Pull(item[0])

                print "%s" % (ret)



        print "\n--- PullAll ---\n"

        pbap.SetFormat("vcard21")

#        pbap.SetFilter(["VERSION", "FN", "TEL"]);

        pbap.SetFilter([]);

        ret = pbap.PullAll()

        print "%s" % (ret)

You can see pbap-client 0.46 enforce vcard 21: pbap.SetFormat("vcard21")

Quote:

Originally Posted by Android_808 (Post 1265425)

The only differences running pbab-client for me compared to your results is that the VCARD version is reporting 3.0 and I have no PRODID field.

Maybe there is activated filter in newer pbabp-client.

Quote:

Originally Posted by Android_808 (Post 1265425)

I haven't been able to try Petrovich with the car yet to make sure that is still working as it was previously. I have found that the v-card used by Petrovich, generated by the export contacts feature of Contacts, is different for v2.1. It seems to omit the FN: field. I'll keep testing.

Can you please paste here (masked name and number) some vcard from pbap-client and the export so I can see the difference?
It should be the same contact.

Please try also debug the obexd so we know how the Blue&Me is using PBAP (PullAll or VCard listing).
You need installed, configured and started syslog + http://talk.maemo.org/showpost.php?p...&postcount=340 + restart obexd (the easiest way is to reboot the phone)

Re: [Announce] Bluetooth PBAP and IrMC / Carkit support is coming to N900...

I have to use the 0.47 version to get it to work with the installed obexd. 0.47 changes the D-Bus namespace to use org.bluez.obex, messes with the API and sets VCARD 3.0 in pbab-client. I've run with 0.47 returning 2.1 and 3.0.

pbab-client 2.1

Code:

BEGIN:VCARD

VERSION:2.1

N:Last;First;;;

FN:First Last

TEL;CELL:XXXXXXXXXXX

END:VCARD

Exported 2.1

Code:

BEGIN:VCARD

VERSION:2.1

UID:13

REV:2010-02-09T15:51:30z

TEL;CELL:XXXXXXXXXXX

N:Last;First;;;

END:VCARD

pbab-client 3.0

Code:

BEGIN:VCARD

VERSION:3.0

N:Last;First;;;

FN:First Last

TEL;TYPE=CELL:XXXXXXXXXXX

END:VCARD

Exported 3.0

Code:

BEGIN:VCARD

VERSION:3.0

UID:13

REV:2010-02-09T15:51:30z

TEL;TYPE=CELL:XXXXXXXXXXX

FN:First Last

N:Last;First;;;

END:VCARD

Content wise, as stated earlier, the only change is the addition of FN using pbab with VCARD 2.1. The order of the returned items in the VCARD (FN, N, TEL etc.) seems to be vary for each contact but as far as I can see always returns the same for that contact.

Will have to wait till at least tomorrow afternoon to test with car as I'm off to sleep before long.

For syslog, is it as simple as:

Code:

root

apt-get install sysklogd

start sysklogd

Then examine /var/log/syslog?

Re: [Announce] Bluetooth PBAP and IrMC / Carkit support is coming to N900...

Quote:

Originally Posted by Android_808 (Post 1265504)

You're right with the namespace change (I forgot).

Quote:

Originally Posted by Android_808 (Post 1265504)

Will have to wait till at least tomorrow afternoon to test with car as I'm off to sleep before long.

Sure take whatever time you need. I really appreciate your cooperation. I know it's time consuming.

Quote:

Originally Posted by Android_808 (Post 1265504)

For syslog, is it as simple as:

Code:

root

apt-get install sysklogd

start sysklogd

Then examine /var/log/syslog?

You wrote right steps. I only don't remember the default syslog settings. Please take a look into /etc/syslog.conf before you start sysklogd.

You can start sysklogd few seconds before Blue&Me pairing/connecting so the log file will be smaller.

You should see obexd lines in /var/log/syslog. These lines I'm interested in. And of course I'm curious if Petrovich way leads to different behaviour in voice dialing.