* [Bluez-users] Object Push from Nokia N93 to BlueZ fails
@ 2007-01-13 6:16 Prabhunath G
2007-01-15 13:27 ` Marcel Holtmann
0 siblings, 1 reply; 5+ messages in thread
From: Prabhunath G @ 2007-01-13 6:16 UTC (permalink / raw)
To: bluez-users
[-- Attachment #1.1: Type: text/plain, Size: 1295 bytes --]
Dear All,
I am doing an experiment to transfer file from Cellphones to Linux over BT
using BlueZ stack available in Linux.
Object Push from Nokia 93 to BlueZ fails.
1) I am able to push a file from Motorola to Linux BlueZ.
2) But I am unable to push a file from Nokia N93 to Linux BlueZ.
Error message displayed on Nokia 93 is "Unable to Connect".
Can anyone help me, in identifying what's going wrong from the log attached
below? Since I am new to BT, I am not yet become expert in understanding the
BT protocol. There is something going wrong from Linux BlueZ stack, when
Nokia
cellphone is sending file transfer request.
3) I also tried transferring files from Linux to Nokia, which works fine.
HciDumps for both the file pushes are given below
Note : I added a service OPUSH using "sdptool add OPUSH"
Linux Kernel : 2.6.18.1
BlueZ tools : bluez-libs-3.7
bluez-utils-3.7
openobex-1.3
obexftp-0.21
I have attached a Advik Bluetooth USB dongle
Note : File transfers work between Nokia 93 and MotoQ and also
File transfers work between Nokia 93 and BlueSoleil on WinXP
Attached are the 2 logs with names: Nokia_to_BlueZ
MotoQ_to_BlueZ
Thanks,
Prabhu
[-- Attachment #1.2: Type: text/html, Size: 2147 bytes --]
[-- Attachment #2: Nokia_to_BlueZ.txt --]
[-- Type: text/plain, Size: 5425 bytes --]
Logs for Nokia to Linux BlueZ
-----------------------------
HCI sniffer - Bluetooth packet analyzer ver 1.33
device: hci0 snap_len: 1028 filter: 0xffffffff
> HCI Event: Connect Request (0x04) plen 10
< HCI Command: Accept Connection Request (0x01|0x0009) plen 7
> HCI Event: Command Status (0x0f) plen 4
> HCI Event: Connect Complete (0x03) plen 11
< HCI Command: Read Remote Supported Features (0x01|0x001b) plen 2
> HCI Event: Max Slots Change (0x1b) plen 3
> HCI Event: Command Status (0x0f) plen 4
> ACL data: handle 1 flags 0x02 dlen 12
L2CAP(s): Connect req: psm 1 scid 0x0040
< ACL data: handle 1 flags 0x02 dlen 16
L2CAP(s): Connect rsp: dcid 0x0040 scid 0x0040 result 0 status 0
Connection successful
< HCI Command: Write Link Policy Settings (0x02|0x000d) plen 4
> HCI Event: Command Complete (0x0e) plen 6
< HCI Command: Change Connection Packet Type (0x01|0x000f) plen 4
> HCI Event: Command Status (0x0f) plen 4
> HCI Event: Connection Packet Type Changed (0x1d) plen 5
> HCI Event: Number of Completed Packets (0x13) plen 5
> ACL data: handle 1 flags 0x02 dlen 10
L2CAP(s): Info req: type 2
< ACL data: handle 1 flags 0x02 dlen 12
L2CAP(s): Info rsp: type 2 result 1
Not supported
> HCI Event: Number of Completed Packets (0x13) plen 5
> ACL data: handle 1 flags 0x02 dlen 12
L2CAP(s): Config req: dcid 0x0040 flags 0x00 clen 0
< ACL data: handle 1 flags 0x02 dlen 14
L2CAP(s): Config rsp: scid 0x0040 flags 0x00 result 0 clen 0
Success
< ACL data: handle 1 flags 0x02 dlen 12
L2CAP(s): Config req: dcid 0x0040 flags 0x00 clen 0
> HCI Event: Read Remote Supported Features (0x0b) plen 11
> HCI Event: Number of Completed Packets (0x13) plen 5
> HCI Event: Number of Completed Packets (0x13) plen 5
> ACL data: handle 1 flags 0x02 dlen 17
> ACL data: handle 1 flags 0x01 dlen 1
L2CAP(s): Config rsp: scid 0x0040 flags 0x00 result 0 clen 4
Success
MTU 672
> ACL data: handle 1 flags 0x02 dlen 17
L2CAP(d): cid 0x0040 len 13 [psm 1]
SDP SS Req: tid 0x1 len 0x8
pat uuid-16 0x1105 (OBEXObjPush)
max 65535
cont 00
< ACL data: handle 1 flags 0x02 dlen 18
L2CAP(d): cid 0x0040 len 14 [psm 1]
SDP SS Rsp: tid 0x1 len 0x9
count 1
handle 0x10001
cont 00
> HCI Event: Number of Completed Packets (0x13) plen 5
> ACL data: handle 1 flags 0x02 dlen 17
> ACL data: handle 1 flags 0x01 dlen 4
L2CAP(d): cid 0x0040 len 17 [psm 1]
SDP SA Req: tid 0x2 len 0xc
handle 0x10001
max 1024
aid(s) 0x0004 (ProtocolDescList)
cont 00
< ACL data: handle 1 flags 0x02 dlen 36
L2CAP(d): cid 0x0040 len 32 [psm 1]
SDP SA Rsp: tid 0x2 len 0x1b
count 24
aid 0x0004 (ProtocolDescList)
< < uuid-16 0x0100 (L2CAP) > <
uuid-16 0x0003 (RFCOMM) uint 0x9 > <
uuid-16 0x0008 (OBEX) > >
cont 00
> HCI Event: Number of Completed Packets (0x13) plen 5
> ACL data: handle 1 flags 0x02 dlen 12
L2CAP(s): Connect req: psm 3 scid 0x0041
< ACL data: handle 1 flags 0x02 dlen 16
L2CAP(s): Connect rsp: dcid 0x0041 scid 0x0041 result 0 status 0
Connection successful
> HCI Event: Number of Completed Packets (0x13) plen 5
> ACL data: handle 1 flags 0x02 dlen 12
L2CAP(s): Config req: dcid 0x0041 flags 0x00 clen 0
< ACL data: handle 1 flags 0x02 dlen 14
L2CAP(s): Config rsp: scid 0x0041 flags 0x00 result 0 clen 0
Success
< ACL data: handle 1 flags 0x02 dlen 16
L2CAP(s): Config req: dcid 0x0041 flags 0x00 clen 4
MTU 1013
> HCI Event: Number of Completed Packets (0x13) plen 5
> HCI Event: Number of Completed Packets (0x13) plen 5
> ACL data: handle 1 flags 0x02 dlen 18
L2CAP(s): Config rsp: scid 0x0041 flags 0x00 result 0 clen 4
Success
MTU 672
> ACL data: handle 1 flags 0x02 dlen 8
L2CAP(d): cid 0x0041 len 4 [psm 3]
RFCOMM(s): SABM: cr 1 dlci 0 pf 1 ilen 0 fcs 0x1c
< ACL data: handle 1 flags 0x02 dlen 8
L2CAP(d): cid 0x0041 len 4 [psm 3]
RFCOMM(s): UA: cr 1 dlci 0 pf 1 ilen 0 fcs 0xd7
> HCI Event: Number of Completed Packets (0x13) plen 5
> ACL data: handle 1 flags 0x02 dlen 18
L2CAP(d): cid 0x0041 len 14 [psm 3]
RFCOMM(s): PN CMD: cr 1 dlci 0 pf 0 ilen 10 fcs 0x70 mcc_len 8
dlci 18 frame_type 0 credit_flow 15 pri 0 ack_timer 0
frame_size 667 max_retrans 0 credits 3
< ACL data: handle 1 flags 0x02 dlen 8
L2CAP(d): cid 0x0041 len 4 [psm 3]
RFCOMM(s): DM: cr 1 dlci 18 pf 1 ilen 0 fcs 0x18
> HCI Event: Number of Completed Packets (0x13) plen 5
> ACL data: handle 1 flags 0x02 dlen 12
L2CAP(s): Disconn req: dcid 0x0041 scid 0x0041
< ACL data: handle 1 flags 0x02 dlen 12
L2CAP(s): Disconn rsp: dcid 0x0041 scid 0x0041
> HCI Event: Number of Completed Packets (0x13) plen 5
> ACL data: handle 1 flags 0x02 dlen 12
L2CAP(s): Disconn req: dcid 0x0040 scid 0x0040
< ACL data: handle 1 flags 0x02 dlen 12
L2CAP(s): Disconn rsp: dcid 0x0040 scid 0x0040
> HCI Event: Number of Completed Packets (0x13) plen 5
< HCI Command: Disconnect (0x01|0x0006) plen 3
> HCI Event: Command Status (0x0f) plen 4
> HCI Event: Disconn Complete (0x05) plen 4
-----------------------------------------------------------------------------
[-- Attachment #3: MotoQ_to_BlueZ.txt --]
[-- Type: text/plain, Size: 7849 bytes --]
Logs for Motorola to Linux BlueZ
---------------------------------
HCI sniffer - Bluetooth packet analyzer ver 1.33
device: hci0 snap_len: 1028 filter: 0xffffffff
> HCI Event: Connect Request (0x04) plen 10
< HCI Command: Accept Connection Request (0x01|0x0009) plen 7
> HCI Event: Command Status (0x0f) plen 4
> HCI Event: Connect Complete (0x03) plen 11
< HCI Command: Read Remote Supported Features (0x01|0x001b) plen 2
> HCI Event: Command Status (0x0f) plen 4
< HCI Command: Write Link Policy Settings (0x02|0x000d) plen 4
> HCI Event: Command Complete (0x0e) plen 6
< HCI Command: Change Connection Packet Type (0x01|0x000f) plen 4
> HCI Event: Command Status (0x0f) plen 4
> HCI Event: Max Slots Change (0x1b) plen 3
> ACL data: handle 5 flags 0x02 dlen 12
L2CAP(s): Connect req: psm 1 scid 0x0042
< ACL data: handle 5 flags 0x02 dlen 16
L2CAP(s): Connect rsp: dcid 0x0040 scid 0x0042 result 0 status 0
Connection successful
> HCI Event: Number of Completed Packets (0x13) plen 5
> ACL data: handle 5 flags 0x02 dlen 17
> ACL data: handle 5 flags 0x01 dlen 3
L2CAP(s): Config req: dcid 0x0040 flags 0x00 clen 8
MTU 512 FlushTO 65535
< ACL data: handle 5 flags 0x02 dlen 14
L2CAP(s): Config rsp: scid 0x0042 flags 0x00 result 0 clen 0
Success
< ACL data: handle 5 flags 0x02 dlen 12
L2CAP(s): Config req: dcid 0x0042 flags 0x00 clen 0
> HCI Event: Max Slots Change (0x1b) plen 3
> HCI Event: Number of Completed Packets (0x13) plen 5
> HCI Event: Number of Completed Packets (0x13) plen 5
> ACL data: handle 5 flags 0x02 dlen 14
L2CAP(s): Config rsp: scid 0x0040 flags 0x00 result 0 clen 0
Success
> ACL data: handle 5 flags 0x02 dlen 17
L2CAP(d): cid 0x0040 len 13 [psm 1]
SDP SS Req: tid 0x0 len 0x8
pat uuid-16 0x1002 (PubBrwsGrp)
max 20
cont 00
< ACL data: handle 5 flags 0x02 dlen 18
L2CAP(d): cid 0x0042 len 14 [psm 1]
SDP SS Rsp: tid 0x0 len 0x9
count 1
handle 0x10000
cont 00
> HCI Event: Number of Completed Packets (0x13) plen 5
> HCI Event: Read Remote Supported Features (0x0b) plen 11
> ACL data: handle 5 flags 0x02 dlen 23
L2CAP(d): cid 0x0040 len 19 [psm 1]
SDP SA Req: tid 0x1 len 0xe
handle 0x10000
max 496
aid(s) 0x0000 - 0xffff
cont 00
< ACL data: handle 5 flags 0x02 dlen 96
L2CAP(d): cid 0x0042 len 92 [psm 1]
SDP SA Rsp: tid 0x1 len 0x57
count 84
aid 0x0000 (SrvRecHndl)
uint 0x10000
aid 0x0001 (SrvClassIDList)
< uuid-16 0x1106 (OBEXObjTrnsf) >
aid 0x0004 (ProtocolDescList)
< < uuid-16 0x0100 (L2CAP) > <
uuid-16 0x0003 (RFCOMM) uint 0xa > <
uuid-16 0x0008 (OBEX) > >
aid 0x0005 (BrwGrpList)
< uuid-16 0x1002 (PubBrwsGrp) >
aid 0x0009 (BTProfileDescList)
< < uuid-16 0x1106 (OBEXObjTrnsf) uint 0x100 > >
aid 0x0100 (SrvName)
str "OBEX File Transfer"
cont 00
> HCI Event: Number of Completed Packets (0x13) plen 5
> ACL data: handle 5 flags 0x02 dlen 12
L2CAP(s): Disconn req: dcid 0x0040 scid 0x0042
< ACL data: handle 5 flags 0x02 dlen 12
L2CAP(s): Disconn rsp: dcid 0x0040 scid 0x0042
> HCI Event: Number of Completed Packets (0x13) plen 5
> HCI Event: Disconn Complete (0x05) plen 4
> HCI Event: Connect Request (0x04) plen 10
< HCI Command: Accept Connection Request (0x01|0x0009) plen 7
> HCI Event: Command Status (0x0f) plen 4
> HCI Event: Connect Complete (0x03) plen 11
< HCI Command: Read Remote Supported Features (0x01|0x001b) plen 2
> HCI Event: Max Slots Change (0x1b) plen 3
> HCI Event: Command Status (0x0f) plen 4
< HCI Command: Write Link Policy Settings (0x02|0x000d) plen 4
> HCI Event: Command Complete (0x0e) plen 6
< HCI Command: Change Connection Packet Type (0x01|0x000f) plen 4
> HCI Event: Command Status (0x0f) plen 4
> HCI Event: Command Complete (0x0e) plen 6
< HCI Command: Change Connection Packet Type (0x01|0x000f) plen 4
> HCI Event: Command Status (0x0f) plen 4
> HCI Event: Connection Packet Type Changed (0x1d) plen 5
> ACL data: handle 6 flags 0x02 dlen 12
L2CAP(s): Connect req: psm 1 scid 0x0043
< ACL data: handle 6 flags 0x02 dlen 16
L2CAP(s): Connect rsp: dcid 0x0040 scid 0x0043 result 0 status 0
Connection successful
> HCI Event: Max Slots Change (0x1b) plen 3
> HCI Event: Number of Completed Packets (0x13) plen 5
> ACL data: handle 6 flags 0x02 dlen 17
> ACL data: handle 6 flags 0x01 dlen 3
L2CAP(s): Config req: dcid 0x0040 flags 0x00 clen 8
MTU 512 FlushTO 65535
< ACL data: handle 6 flags 0x02 dlen 14
L2CAP(s): Config rsp: scid 0x0043 flags 0x00 result 0 clen 0
Success
< ACL data: handle 6 flags 0x02 dlen 12
L2CAP(s): Config req: dcid 0x0043 flags 0x00 clen 0
> HCI Event: Read Remote Supported Features (0x0b) plen 11
> HCI Event: Number of Completed Packets (0x13) plen 5
> HCI Event: Number of Completed Packets (0x13) plen 5
> ACL data: handle 6 flags 0x02 dlen 14
L2CAP(s): Config rsp: scid 0x0040 flags 0x00 result 0 clen 0
Success
> ACL data: handle 6 flags 0x02 dlen 17
L2CAP(d): cid 0x0040 len 13 [psm 1]
SDP SS Req: tid 0x0 len 0x8
pat uuid-16 0x1106 (OBEXObjTrnsf)
max 20
cont 00
< ACL data: handle 6 flags 0x02 dlen 18
L2CAP(d): cid 0x0043 len 14 [psm 1]
SDP SS Rsp: tid 0x0 len 0x9
count 1
handle 0x10000
cont 00
> HCI Event: Number of Completed Packets (0x13) plen 5
> ACL data: handle 6 flags 0x02 dlen 23
L2CAP(d): cid 0x0040 len 19 [psm 1]
SDP SA Req: tid 0x1 len 0xe
handle 0x10000
max 496
aid(s) 0x0000 - 0xffff
cont 00
L2CAP(d): cid 0x0040 len 19 [psm 1]
SDP SA Req: tid 0x1 len 0xe
handle 0x10000
max 496
aid(s) 0x0000 - 0xffff
cont 00
< ACL data: handle 6 flags 0x02 dlen 96
L2CAP(d): cid 0x0043 len 92 [psm 1]
SDP SA Rsp: tid 0x1 len 0x57
count 84
aid 0x0000 (SrvRecHndl)
uint 0x10000
aid 0x0001 (SrvClassIDList)
< uuid-16 0x1106 (OBEXObjTrnsf) >
aid 0x0004 (ProtocolDescList)
< < uuid-16 0x0100 (L2CAP) > <
uuid-16 0x0003 (RFCOMM) uint 0xa > <
uuid-16 0x0008 (OBEX) > >
aid 0x0005 (BrwGrpList)
< uuid-16 0x1002 (PubBrwsGrp) >
aid 0x0009 (BTProfileDescList)
< < uuid-16 0x1106 (OBEXObjTrnsf) uint 0x100 > >
aid 0x0100 (SrvName)
str "OBEX File Transfer"
cont 00
> HCI Event: Number of Completed Packets (0x13) plen 5
> ACL data: handle 6 flags 0x02 dlen 12
L2CAP(s): Disconn req: dcid 0x0040 scid 0x0043
< ACL data: handle 6 flags 0x02 dlen 12
L2CAP(s): Disconn rsp: dcid 0x0040 scid 0x0043
> HCI Event: Number of Completed Packets (0x13) plen 5
> ACL data: handle 6 flags 0x02 dlen 12
L2CAP(s): Connect req: psm 3 scid 0x0044
< ACL data: handle 6 flags 0x02 dlen 16
L2CAP(s): Connect rsp: dcid 0x0040 scid 0x0044 result 0 status 0
Connection successful
> HCI Event: Number of Completed Packets (0x13) plen 5
> ACL data: handle 6 flags 0x02 dlen 16
L2CAP(s): Config req: dcid 0x0040 flags 0x00 clen 4
MTU 1691
< ACL data: handle 6 flags 0x02 dlen 14
L2CAP(s): Config rsp: scid 0x0044 flags 0x00 result 0 clen 0
Success
< ACL data: handle 6 flags 0x02 dlen 16
L2CAP(s): Config req: dcid 0x0044 flags 0x00 clen 4
MTU 1013
> HCI Event: Number of Completed Packets (0x13) plen 5
[-- Attachment #4: Type: text/plain, Size: 347 bytes --]
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
[-- Attachment #5: Type: text/plain, Size: 164 bytes --]
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [Bluez-users] Object Push from Nokia N93 to BlueZ fails
2007-01-13 6:16 [Bluez-users] Object Push from Nokia N93 to BlueZ fails Prabhunath G
@ 2007-01-15 13:27 ` Marcel Holtmann
2007-01-16 14:23 ` Prabhu nath
0 siblings, 1 reply; 5+ messages in thread
From: Marcel Holtmann @ 2007-01-15 13:27 UTC (permalink / raw)
To: BlueZ users
Hi,
> I am doing an experiment to transfer file from Cellphones to Linux
> over BT
> using BlueZ stack available in Linux.
>
> Object Push from Nokia 93 to BlueZ fails.
>
> 1) I am able to push a file from Motorola to Linux BlueZ.
>
> 2) But I am unable to push a file from Nokia N93 to Linux BlueZ.
>
> Error message displayed on Nokia 93 is "Unable to Connect".
>
> Can anyone help me, in identifying what's going wrong from the log
> attached
> below? Since I am new to BT, I am not yet become expert in
> understanding the
> BT protocol. There is something going wrong from Linux BlueZ stack,
> when Nokia
> cellphone is sending file transfer request.
>
> 3) I also tried transferring files from Linux to Nokia, which works
> fine.
>
> HciDumps for both the file pushes are given below
the MotoQ dump doesn't show any OBEX nor RFCOMM activity. The Nokia dump
indicates that no RFCOMM server is listening on channel 9.
Regards
Marcel
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [Bluez-users] Object Push from Nokia N93 to BlueZ fails
2007-01-15 13:27 ` Marcel Holtmann
@ 2007-01-16 14:23 ` Prabhu nath
2007-01-16 14:30 ` Marcel Holtmann
0 siblings, 1 reply; 5+ messages in thread
From: Prabhu nath @ 2007-01-16 14:23 UTC (permalink / raw)
To: BlueZ users
[-- Attachment #1.1: Type: text/plain, Size: 2384 bytes --]
Hi Marcel,
I started the rfcomm to listen on channel 9. Now, when I transfer
file from Nokia N93 to my
PC.
It hangs. hcidump will give a segmentation fault.
My configuration : http://gprabhunath.googlepages.com/bluez_conf
hcidump : http://gprabhunath.googlepages.com/home
I did the following.
* Edited rfcomm.conf and hcid.conf (Ref: My configuration)
* started hcid and sdpd (service bluetooth start)
* started rfcomm to listen on channel 9 (rfcomm -i hci0 listen 2
9)
* started obexftpd (obexftpd -b -c /tmp/inbox)
output of hciconfig, hcitool scan, and sdptool browse can be
viewed at
http://gprabhunath.googlepages.com/bluez_conf
Thanks,
Prabhu
On 1/15/07, Marcel Holtmann <marcel@holtmann.org> wrote:
>
> Hi,
>
> > I am doing an experiment to transfer file from Cellphones to Linux
> > over BT
> > using BlueZ stack available in Linux.
> >
> > Object Push from Nokia 93 to BlueZ fails.
> >
> > 1) I am able to push a file from Motorola to Linux BlueZ.
> >
> > 2) But I am unable to push a file from Nokia N93 to Linux BlueZ.
> >
> > Error message displayed on Nokia 93 is "Unable to Connect".
> >
> > Can anyone help me, in identifying what's going wrong from the log
> > attached
> > below? Since I am new to BT, I am not yet become expert in
> > understanding the
> > BT protocol. There is something going wrong from Linux BlueZ stack,
> > when Nokia
> > cellphone is sending file transfer request.
> >
> > 3) I also tried transferring files from Linux to Nokia, which works
> > fine.
> >
> > HciDumps for both the file pushes are given below
>
> the MotoQ dump doesn't show any OBEX nor RFCOMM activity. The Nokia dump
> indicates that no RFCOMM server is listening on channel 9.
>
> Regards
>
> Marcel
>
>
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share
> your
> opinions on IT & business topics through brief surveys - and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> Bluez-users mailing list
> Bluez-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-users
>
[-- Attachment #1.2: Type: text/html, Size: 3964 bytes --]
[-- Attachment #2: Type: text/plain, Size: 347 bytes --]
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
[-- Attachment #3: Type: text/plain, Size: 164 bytes --]
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [Bluez-users] Object Push from Nokia N93 to BlueZ fails
2007-01-16 14:23 ` Prabhu nath
@ 2007-01-16 14:30 ` Marcel Holtmann
2007-01-17 16:03 ` Prabhu nath
0 siblings, 1 reply; 5+ messages in thread
From: Marcel Holtmann @ 2007-01-16 14:30 UTC (permalink / raw)
To: BlueZ users
Hi Parbhu,
> I started the rfcomm to listen on channel 9. Now, when I
> transfer file from Nokia N93 to my
> PC.
> It hangs. hcidump will give a segmentation fault.
> My configuration :
> http://gprabhunath.googlepages.com/bluez_conf
>
> hcidump : http://gprabhunath.googlepages.com/home
>
> I did the following.
> * Edited rfcomm.conf and hcid.conf (Ref: My configuration)
> * started hcid and sdpd (service bluetooth start)
> * started rfcomm to listen on channel 9 (rfcomm -i hci0
> listen 2 9)
> * started obexftpd (obexftpd -b -c /tmp/inbox)
you should only use obexftpd and not "rfcommm listen". The rfcomm
command will only create a TTY on successful connect, but then don't do
the needed OBEX connection for the push.
Regards
Marcel
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [Bluez-users] Object Push from Nokia N93 to BlueZ fails
2007-01-16 14:30 ` Marcel Holtmann
@ 2007-01-17 16:03 ` Prabhu nath
0 siblings, 0 replies; 5+ messages in thread
From: Prabhu nath @ 2007-01-17 16:03 UTC (permalink / raw)
To: BlueZ users
[-- Attachment #1.1: Type: text/plain, Size: 1934 bytes --]
Hi Marcel,
This time I am running only obexftpd, I even tried by removing all
conf from rfcomm.conf but No Luck, I am running into same issue, Yet again I
am not able to push file from Nokia to BlueZ, but I am able to Push file
from Motorola to BlueZ.
hcidump :- Nokia_to_BlueZ :
http://brochevarevarura.googlepages.com/n93_to_bluez
hcidump :- Moto_to_BlueZ :
http://brochevarevarura.googlepages.com/motoq_to_bluez
Thanks,
Prabhu
On 1/16/07, Marcel Holtmann <marcel@holtmann.org> wrote:
>
> Hi Parbhu,
>
> > I started the rfcomm to listen on channel 9. Now, when I
> > transfer file from Nokia N93 to my
> > PC.
> > It hangs. hcidump will give a segmentation fault.
> > My configuration :
> > http://gprabhunath.googlepages.com/bluez_conf
> >
> > hcidump : http://gprabhunath.googlepages.com/home
> >
> > I did the following.
> > * Edited rfcomm.conf and hcid.conf (Ref: My configuration)
> > * started hcid and sdpd (service bluetooth start)
> > * started rfcomm to listen on channel 9 (rfcomm -i hci0
> > listen 2 9)
> > * started obexftpd (obexftpd -b -c /tmp/inbox)
>
> you should only use obexftpd and not "rfcommm listen". The rfcomm
> command will only create a TTY on successful connect, but then don't do
> the needed OBEX connection for the push.
>
> Regards
>
> Marcel
>
>
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share
> your
> opinions on IT & business topics through brief surveys - and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> Bluez-users mailing list
> Bluez-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-users
>
[-- Attachment #1.2: Type: text/html, Size: 3479 bytes --]
[-- Attachment #2: Type: text/plain, Size: 347 bytes --]
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
[-- Attachment #3: Type: text/plain, Size: 164 bytes --]
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2007-01-17 16:03 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2007-01-13 6:16 [Bluez-users] Object Push from Nokia N93 to BlueZ fails Prabhunath G
2007-01-15 13:27 ` Marcel Holtmann
2007-01-16 14:23 ` Prabhu nath
2007-01-16 14:30 ` Marcel Holtmann
2007-01-17 16:03 ` Prabhu nath
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox