From: "commerce@hschmitt.de" <commerce@hschmitt.de>
To: linux-bluetooth@vger.kernel.org
Subject: Re: obexd and phonebook-ebook.c (PBAP support)
Date: Mon, 05 Apr 2010 10:36:20 +0200 [thread overview]
Message-ID: <4BB9A104.3050509@hschmitt.de> (raw)
In-Reply-To: <4BB4B789.7070409@hschmitt.de>
commerce@hschmitt.de schrieb:
> Hi,
>
> Is it possible that obexd has to call g_type_init() if phonebook-ebook
> is used?
> I think when you call e_book_new_default_addressbook() somewhere down
> gconf_client_get_default() is called and it insists that g_type_init()
> is called prior to its use.
>
> I tried to make obexd work on my N900, but I did not get there.
> My car kit does not use PBAP because it finds the Nokia SyncML profile
> and uses it, but the N900 does not communicate with bluetooth devices
> other than PC or Mobiles via SyncML.
> Is there a way to unregister a service from SDP?
>
> Regards,
>
> --
> Harald
> --
> To unsubscribe from this list: send the line "unsubscribe
> linux-bluetooth" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
Now I am using pbap-client from the obexd package from my notebook to
test pbap on my N900. I am pretty far. All my contacts are read, but the
obex message is not sent back successfully.
Here is the syslog (I added some messages):
Apr 5 09:56:35 Nokia-N900-51-1 obexd[1203]: pbap_get: pbap_get()
Apr 5 09:56:35 Nokia-N900-51-1 obexd[1203]: phonebook_pullphonebook:
phonebook_pullphonebook
Apr 5 09:56:36 Nokia-N900-51-1 obexd[1203]: pbap_pullphonebook:
phonebook_pullphonebook had no errors
Apr 5 09:56:36 Nokia-N900-51-1 obexd[1203]:
pbap_add_result_apparam_header: pbap_add_result_apparam_header
maxlistcount=65535 rspsize=0
Apr 5 09:56:36 Nokia-N900-51-1 obexd[1203]: pbap_get: pbap_get() no error
Apr 5 09:56:36 Nokia-N900-51-1 obexd[1203]: pbap_get: pbap_get() addbody
Apr 5 09:56:36 Nokia-N900-51-1 obexd[1203]: pbap_get: pbap_get()
OBEX_ObjectSetRsp()
Apr 5 09:56:36 Nokia-N900-51-1 obexd[1203]: PROGRESS(0x0), GET(0x3),
(null)(0x0)
Apr 5 09:56:36 Nokia-N900-51-1 obexd[1203]: ebookpull_cb: ebookpull_cb
count=305 size=42944
Apr 5 09:56:36 Nokia-N900-51-1 obexd[1203]: STREAMEMPTY(0x8),
CONNECT(0x0), (null)(0x0)
Apr 5 09:56:36 Nokia-N900-51-1 obexd[1203]: obex_write_stream:
name=telecom/pb.vcf type=x-bt/phonebook tx_mtu=3896 file=(nil)
Apr 5 09:56:36 Nokia-N900-51-1 obexd[1203]: STREAMEMPTY(0x8),
CONNECT(0x0), (null)(0x0)
Apr 5 09:56:36 Nokia-N900-51-1 obexd[1203]: obex_write_stream:
name=telecom/pb.vcf type=x-bt/phonebook tx_mtu=3896 file=(nil)
Apr 5 09:56:36 Nokia-N900-51-1 obexd[1203]: PROGRESS(0x0),
(null)(0x10), (null)(0x0)
Apr 5 09:56:37 Nokia-N900-51-1 obexd[1203]: REQDONE(0x3), (null)(0x10),
(null)(0x3)
Apr 5 09:57:00 Nokia-N900-51-1 obexd[1203]: obex_handle_input: poll
event HUP ERR
Best,
Harald
next prev parent reply other threads:[~2010-04-05 8:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-01 15:11 obexd and phonebook-ebook.c (PBAP support) commerce
2010-04-05 8:36 ` commerce [this message]
2010-04-12 15:38 ` Harald Schmitt
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=4BB9A104.3050509@hschmitt.de \
--to=commerce@hschmitt.de \
--cc=linux-bluetooth@vger.kernel.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).