From: Ethan B. <ebl...@cs...> - 2005-10-11 20:15:29
|
Hi all, =46rom browsing the list archives, I get the feeling that questions much like this one are very common, but most of the answers I saw were things like "upgrade to <some dev release>, it's fixed for your phone", so I guess I'll ask anyway. I recently got a Motorola v551, and I'm trying to get obexftp working with it without much success. I've tried the released 0.10.6, development release 0.10.7, the prerelease 0.10.8_9, and even 0.10.8_5 with the Motorola patch provided by Philip Kovacs on 2005-09-08; all exhibit the same behavior. When I try basically any obexftp command, I get a result like this: elb@colt:~$ obexftp -b 00:14:9A:AA:8C:3B -l / Browsing 00:14:9A:AA:8C:3B ... Channel: 9 No custom transport Connecting...failed: connect Still trying to connect Connecting...failed: connect Still trying to connect Connecting...failed: connect Still trying to connect Channel 9 does appear to be the correct channel, based on the output of hcitool browse. (Interestingly, whatever channel I provide with -B, obexftp says "Channel: 9".) If the phone is not paired, I get prompts to pair it, etc., so I don't think pairing is the problem. Likewise, the gnome-bluetooth gnome-obex-{send,server} tools seem to work. I glanced through the output of hcidump, but it didn't really mean anything to me. I suspect there's not enough information here for this problem to be fixed, but I'm not sure what information you might need. In the interest of not pasting tons of irrelevant junk, I'll leave off here -- however, if there is any information in particular that would be useful, I'd be more than happy to provide it. Ethan --=20 The laws that forbid the carrying of arms are laws [that have no remedy for evils]. They disarm only those who are neither inclined nor determined to commit crimes. -- Cesare Beccaria, "On Crimes and Punishments", 1764 |
From: Philip K. <kov...@co...> - 2005-10-12 00:02:18
|
Is the OBEX FTP profile enabled for the phone? I see the phone has a K12 qualification, but that doesn't mean it shipped with the profile active. There may be a "seem edit" involved. If the PUSH is working (gnome-bt uses PUSH not FTP), as you say, it _probable_ that FTP is active too. What is the output of sdptool browse <addr>? You might also use the software and drivers for the dongle on a Windoze box, just to get confirmation that the profile is active. BTW, after pairing, when you hit the FTP channel on the phone, it should display: "OBEX FTP TRANSFER, grant or deny?" Does it say that? Phil Ethan Blanton wrote: >Hi all, > >From browsing the list archives, I get the feeling that questions much >like this one are very common, but most of the answers I saw were >things like "upgrade to <some dev release>, it's fixed for your >phone", so I guess I'll ask anyway. > >I recently got a Motorola v551, and I'm trying to get obexftp working >with it without much success. I've tried the released 0.10.6, >development release 0.10.7, the prerelease 0.10.8_9, and even 0.10.8_5 >with the Motorola patch provided by Philip Kovacs on 2005-09-08; all >exhibit the same behavior. > >When I try basically any obexftp command, I get a result like this: > >elb@colt:~$ obexftp -b 00:14:9A:AA:8C:3B -l / >Browsing 00:14:9A:AA:8C:3B ... >Channel: 9 >No custom transport >Connecting...failed: connect >Still trying to connect >Connecting...failed: connect >Still trying to connect >Connecting...failed: connect >Still trying to connect > >Channel 9 does appear to be the correct channel, based on the output >of hcitool browse. (Interestingly, whatever channel I provide with >-B, obexftp says "Channel: 9".) > >If the phone is not paired, I get prompts to pair it, etc., so I don't >think pairing is the problem. Likewise, the gnome-bluetooth >gnome-obex-{send,server} tools seem to work. I glanced through the >output of hcidump, but it didn't really mean anything to me. > >I suspect there's not enough information here for this problem to be >fixed, but I'm not sure what information you might need. In the >interest of not pasting tons of irrelevant junk, I'll leave off here >-- however, if there is any information in particular that would be >useful, I'd be more than happy to provide it. > >Ethan > > > |
From: Ethan B. <ebl...@cs...> - 2005-10-12 01:47:42
Attachments:
browse
|
Philip Kovacs spake unto us the following wisdom: > Is the OBEX FTP profile enabled for the phone? I see the phone has a > K12 qualification, but that doesn't mean it shipped with the profile > active. There may be a "seem edit" involved. If the PUSH is working > (gnome-bt uses PUSH not FTP), as you say, it _probable_ that FTP is > active too. What is the output of sdptool browse <addr>? You might > also use the software and drivers for the dongle on a Windoze box, > just to get confirmation that the profile is active. BTW, after > pairing, when you hit the FTP channel on the phone, it should display: I *think* it's enabled, based on the output of hcitool browse (attached), but I'm not sure how to tell for sure. I don't have easy access to a Windows box, but I'll see if I can find one ... alternately, I can get access to an OSX box pretty easily, but I couldn't find an obex tool installed on it. I'll look again. As best I've been able to tell, seem edits require a link cable and trickery, is that the case? Can I do a seem edit via bluetooth in some fashion? > "OBEX FTP TRANSFER, grant or deny?" Does it say that? I never see this, no. It gets through pairing, and then the host PC gives an error. The phone doesn't display anything at all. Ethan -- The laws that forbid the carrying of arms are laws [that have no remedy for evils]. They disarm only those who are neither inclined nor determined to commit crimes. -- Cesare Beccaria, "On Crimes and Punishments", 1764 |
From: Ethan B. <ebl...@cs...> - 2005-10-12 02:14:20
|
Ethan Blanton spake unto us the following wisdom: > I *think* it's enabled, based on the output of hcitool browse > (attached), but I'm not sure how to tell for sure. I don't have > easy access to a Windows box, but I'll see if I can find one ... > alternately, I can get access to an OSX box pretty easily, but I > couldn't find an obex tool installed on it. I'll look again. Sorry to reply to myself ... I can use "Browse Device" from the OSX Bluetooth menu to view the files on the phone. Ethan --=20 The laws that forbid the carrying of arms are laws [that have no remedy for evils]. They disarm only those who are neither inclined nor determined to commit crimes. -- Cesare Beccaria, "On Crimes and Punishments", 1764 |
From: Philip K. <kov...@co...> - 2005-10-12 02:34:29
|
Looks like the OBEX FTP service is being advertised properly and your channel is 9, so the syntax: obexftp -b 00:14:9A:AA:8C:3B -B 9 -l / should work if everything is set up properly. Are you using a fairly recent kernel and did you configure the needed bluetooth modules, esp. rfcomm? Did you load the bluetooth modules? I see your carrier is Cingular. I do not believe that they are in the habit (as is Verizon Wireless) of "crippling" bluetooth functionality. Seem edits are not necessary if the profile is active (otherwise you have to cable up the phone and use software to edit the seems and turn on the bluetooth bits.) Seem edits can only be done with a cable, but again, only Verizon Wireless, to my knowledge, goes out of their way to cripple bluetooth. I am certain that your phone, will ask you to grant/deny obex file transfer after pairing successfully. Your problem may be that your bluez setup may not be config'd properly (assuming you are using that stack). Phil Ethan Blanton wrote: >Philip Kovacs spake unto us the following wisdom: > > >>Is the OBEX FTP profile enabled for the phone? I see the phone has a >>K12 qualification, but that doesn't mean it shipped with the profile >>active. There may be a "seem edit" involved. If the PUSH is working >>(gnome-bt uses PUSH not FTP), as you say, it _probable_ that FTP is >>active too. What is the output of sdptool browse <addr>? You might >>also use the software and drivers for the dongle on a Windoze box, >>just to get confirmation that the profile is active. BTW, after >>pairing, when you hit the FTP channel on the phone, it should display: >> >> > >I *think* it's enabled, based on the output of hcitool browse >(attached), but I'm not sure how to tell for sure. I don't have >easy access to a Windows box, but I'll see if I can find one ... >alternately, I can get access to an OSX box pretty easily, but I >couldn't find an obex tool installed on it. I'll look again. > >As best I've been able to tell, seem edits require a link cable and >trickery, is that the case? Can I do a seem edit via bluetooth in >some fashion? > > > >>"OBEX FTP TRANSFER, grant or deny?" Does it say that? >> >> > >I never see this, no. It gets through pairing, and then the host PC >gives an error. The phone doesn't display anything at all. > >Ethan > > > >------------------------------------------------------------------------ > >Browsing 00:14:9A:AA:8C:3B ... >Service RecHandle: 0x0 >Service Class ID List: > "SDP Server" (0x1000) >Protocol Descriptor List: > "L2CAP" (0x0100) > "SDP" (0x0001) >Profile Descriptor List: > "" (0x1000) > Version: 0x0100 > >Service Name: Dial-up networking Gateway >Service Description: Dial-up networking Gateway >Service Provider: Cingular >Service RecHandle: 0x10001 >Service Class ID List: > "Dialup Networking" (0x1103) >Protocol Descriptor List: > "L2CAP" (0x0100) > "RFCOMM" (0x0003) > Channel: 1 >Language Base Attr List: > code_ISO639: 0x656e > encoding: 0x6a > base_offset: 0x100 > code_ISO639: 0x6672 > encoding: 0x6a > base_offset: 0xd800 > code_ISO639: 0x6573 > encoding: 0x6a > base_offset: 0xd803 > code_ISO639: 0x7074 > encoding: 0x6a > base_offset: 0xd806 >Profile Descriptor List: > "Dialup Networking" (0x1103) > Version: 0x0100 > >Service Name: Voice Gateway >Service Description: Headset Audio Gateway >Service Provider: Cingular >Service RecHandle: 0x10003 >Service Class ID List: > "Headset Audio Gateway" (0x1112) > "Generic Audio" (0x1203) >Protocol Descriptor List: > "L2CAP" (0x0100) > "RFCOMM" (0x0003) > Channel: 3 >Language Base Attr List: > code_ISO639: 0x656e > encoding: 0x6a > base_offset: 0x100 > code_ISO639: 0x6672 > encoding: 0x6a > base_offset: 0xd800 > code_ISO639: 0x6573 > encoding: 0x6a > base_offset: 0xd803 > code_ISO639: 0x7074 > encoding: 0x6a > base_offset: 0xd806 >Profile Descriptor List: > "Headset" (0x1108) > Version: 0x0100 > >Service Name: Hands-Free voice gateway >Service Description: Hands-Free voice gateway >Service Provider: Cingular >Service RecHandle: 0x10007 >Service Class ID List: > "" (0x111f) > "Generic Audio" (0x1203) >Protocol Descriptor List: > "L2CAP" (0x0100) > "RFCOMM" (0x0003) > Channel: 7 >Language Base Attr List: > code_ISO639: 0x656e > encoding: 0x6a > base_offset: 0x100 > code_ISO639: 0x6672 > encoding: 0x6a > base_offset: 0xd800 > code_ISO639: 0x6573 > encoding: 0x6a > base_offset: 0xd803 > code_ISO639: 0x7074 > encoding: 0x6a > base_offset: 0xd806 >Profile Descriptor List: > "" (0x111e) > Version: 0x0101 > >Service Name: OBEX Object Push >Service Description: OBEX Object Push >Service Provider: Cingular >Service RecHandle: 0x10008 >Service Class ID List: > "OBEX Object Push" (0x1105) >Protocol Descriptor List: > "L2CAP" (0x0100) > "RFCOMM" (0x0003) > Channel: 8 > "OBEX" (0x0008) >Language Base Attr List: > code_ISO639: 0x656e > encoding: 0x6a > base_offset: 0x100 > code_ISO639: 0x6672 > encoding: 0x6a > base_offset: 0xd800 > code_ISO639: 0x6573 > encoding: 0x6a > base_offset: 0xd803 > code_ISO639: 0x7074 > encoding: 0x6a > base_offset: 0xd806 >Profile Descriptor List: > "OBEX Object Push" (0x1105) > Version: 0x0100 > >Service Name: OBEX File Transfer >Service Description: OBEX File Transfer >Service Provider: Cingular >Service RecHandle: 0x10009 >Service Class ID List: > "OBEX File Transfer" (0x1106) >Protocol Descriptor List: > "L2CAP" (0x0100) > "RFCOMM" (0x0003) > Channel: 9 > "OBEX" (0x0008) >Language Base Attr List: > code_ISO639: 0x656e > encoding: 0x6a > base_offset: 0x100 > code_ISO639: 0x6672 > encoding: 0x6a > base_offset: 0xd800 > code_ISO639: 0x6573 > encoding: 0x6a > base_offset: 0xd803 > code_ISO639: 0x7074 > encoding: 0x6a > base_offset: 0xd806 >Profile Descriptor List: > "OBEX File Transfer" (0x1106) > Version: 0x0100 > > > |
From: Ethan B. <ebl...@cs...> - 2005-10-12 02:44:58
|
Philip Kovacs spake unto us the following wisdom: > Looks like the OBEX FTP service is being advertised properly and your=20 > channel is 9, so the syntax: obexftp -b 00:14:9A:AA:8C:3B -B 9 -l / > should work if everything is set up properly. Are you using a fairly > recent kernel and did you configure the needed bluetooth modules, esp. > rfcomm? Did you load the bluetooth modules? I see your carrier is > Cingular. I do not believe that they are in the habit (as is Verizon > Wireless) of "crippling" bluetooth functionality. Seem edits are not > necessary if the profile is active (otherwise you have to cable up the > phone and use software to edit the seems and turn on the bluetooth > bits.) Seem edits can only be done with a cable, but again, only > Verizon Wireless, to my knowledge, goes out of their way to cripple=20 > bluetooth. That command gives the same error I reported in my original message. I have tried on both a Fedora box with a stock kernel (2.6.12-1.1372_FC3smp) and an Ubuntu box with 2.6.13.2 (not stock). In both cases the bluetooth, hci_usb, l2cap, and rfcomm modules are loaded. The Fedora box is using bluez 2.10, and the Ubuntu box 2.20. > I am certain that your phone, will ask you to grant/deny obex file=20 > transfer after pairing successfully. Your problem may be that your > bluez setup may not be config'd properly (assuming you are using that > stack). I was not asked to grant/deny obex file transfer for browsing from the OSX box after pairing. I *think* bluez is set up correctly, as I can use gnome-obex-send to send files to the phone, and I can send files from the phone to the computer using either obexserver or gnome-obex-server. Ethan --=20 The laws that forbid the carrying of arms are laws [that have no remedy for evils]. They disarm only those who are neither inclined nor determined to commit crimes. -- Cesare Beccaria, "On Crimes and Punishments", 1764 |
From: Philip K. <kov...@co...> - 2005-10-12 17:56:59
|
These are the last things I can think of offhand to check: after you configure obexftp, does the config.h include: #define HAVE_BLUETOOTH 1 (it should); does the command: "obexftp -b" discover your phone and present its address (it should). finally try configuring for debugging: CFLAGS="-DOBEXFTP_DEBUG=5" ./configure; make; etc. Phil Ethan Blanton wrote: >That command gives the same error I reported in my original message. I >have tried on both a Fedora box with a stock kernel >(2.6.12-1.1372_FC3smp) and an Ubuntu box with 2.6.13.2 (not stock). In >both cases the bluetooth, hci_usb, l2cap, and rfcomm modules are >loaded. The Fedora box is using bluez 2.10, and the Ubuntu box 2.20. > > > >>I am certain that your phone, will ask you to grant/deny obex file >>transfer after pairing successfully. Your problem may be that your >>bluez setup may not be config'd properly (assuming you are using that >>stack). >> >> > >I was not asked to grant/deny obex file transfer for browsing from the >OSX box after pairing. I *think* bluez is set up correctly, as I can >use gnome-obex-send to send files to the phone, and I can send files >from the phone to the computer using either obexserver or >gnome-obex-server. > >Ethan > > > |
From: Ethan B. <ebl...@cs...> - 2005-10-13 01:16:13
|
Philip Kovacs spake unto us the following wisdom: > These are the last things I can think of offhand to check: after you=20 > configure obexftp, does the config.h include: #define HAVE_BLUETOOTH 1 > (it should); does the command: "obexftp -b" discover your phone and > present its address (it should). finally try configuring for > debugging: CFLAGS=3D"-DOBEXFTP_DEBUG=3D5" ./configure; make; etc. HAVE_BLUETOOTH is indeed defined. The output of 'obexftp -b' is: Scanning ... Using 00:14:9A:AA:8C:3B elb Browsing 00:14:9A:AA:8C:3B ... Channel: 9 Nothing to do. Use --help for help. This looks correct to me. Defining OBEXFTP_DEBUG=3D5 seems to have no effect on output in this case. If this is a problem which must be "fixed" by changing openobex or obexftp (whether it is a phone bug or an obexftp bug or what), is there any information I can provide to help get it straightened out? Ethan --=20 The laws that forbid the carrying of arms are laws [that have no remedy for evils]. They disarm only those who are neither inclined nor determined to commit crimes. -- Cesare Beccaria, "On Crimes and Punishments", 1764 |
From: Philip K. <kov...@co...> - 2005-10-29 19:05:39
|
Here's a bit of serendipity. A neighbor was keen on showing me his new cellphone and, lo and behold, it was a new Motorola V551 from Cingular. He was interested in the Bluetooth aspects of the phone, so I shuffled him into my computer room for ten minutes. Here's what I discovered with this phone: it works perfectly with the latest obexftp dev snapshot! The only difference I observed in using it versus the Motorols v710/e815 is this: for the v710/e815 you only need to turn the Bluetooth ON. For the v551 you need to do two things: 1) turn Bluetooth ON and 2), activate the "Find me" cycle on the phone. It seems the v551 only permits connections on its obex channel (9) during its 60 second "find me" cycle. With "find me" running, a root listing with the command: obexftp -b <> -B 9 -l / reported the phone as having three directories: audio, video and picture. Transfers worked fine and you should have no problems with it. Sorry I neglected get his phone's firmware version. Philip Ethan Blanton wrote: >If this is a problem which must be "fixed" by changing openobex or >obexftp (whether it is a phone bug or an obexftp bug or what), is >there any information I can provide to help get it straightened out? > >Ethan > > |
From: Ethan B. <ebl...@cs...> - 2005-10-30 03:17:51
|
Philip Kovacs spake unto us the following wisdom: > Here's what I discovered with this phone: it works perfectly with the=20 > latest obexftp dev snapshot! The only difference I observed in using > it versus the Motorols v710/e815 is this: for the v710/e815 you only > need to turn the Bluetooth ON. For the v551 you need to do two > things: 1) turn Bluetooth ON and 2), activate the "Find me" cycle on > the phone. It seems the v551 only permits connections on its obex=20 > channel (9) during its 60 second "find me" cycle. With "find me" > running, a root listing with the command: obexftp -b <> -B 9 -l /=20 Interesting ... Is this obexftp 0.10.8_9? I cannot list with this version, using 'Find Me' or not. (However, I can list from an OSX box across the room with or without Find Me.) Ethan --=20 The laws that forbid the carrying of arms are laws [that have no remedy for evils]. They disarm only those who are neither inclined nor determined to commit crimes. -- Cesare Beccaria, "On Crimes and Punishments", 1764 |
From: Philip K. <kov...@co...> - 2005-10-30 16:57:18
|
Ethan Blanton wrote: >Interesting ... Is this obexftp 0.10.8_9? I cannot list with this >version, using 'Find Me' or not. (However, I can list from an OSX box >across the room with or without Find Me.) > > Yes, 0.10.8_9. Given the relative ease I had using bluetooth and obexftp with the v551 phone, for the few minutes I had with it, and given that the phone is able to communicate via bluetooth on another computer with another operating system, I would say you probably have some sort of configuration problem. Perhaps your kernel config or bluez. I really don't think obexftp is the problem.... Phil . |
From: Ethan B. <ebl...@cs...> - 2005-10-30 17:29:39
|
Philip Kovacs spake unto us the following wisdom: > Yes, 0.10.8_9. Given the relative ease I had using bluetooth and=20 > obexftp with the v551 phone, for the few minutes I had with it, and > given that the phone is able to communicate via bluetooth on another > computer with another operating system, I would say you probably have > some sort of configuration problem. Perhaps your kernel config or > bluez. I really don't think obexftp is the problem.... All right, I've done some more playing ... did you do anything but the listing of /? If not, was that listing of / at the same time you paired with the phone? I can successfully use obexftp with the phone if I delete the pairing from the phone after every use. It doesn't seem to matter if 'Find Me' is on or not, if I do this. If I first pair with any other application, or even with obexftp, it won't work and I get the same error I was reporting before. Maybe this is my stack, but I don't know where to look for configuration problems... Ethan --=20 The laws that forbid the carrying of arms are laws [that have no remedy for evils]. They disarm only those who are neither inclined nor determined to commit crimes. -- Cesare Beccaria, "On Crimes and Punishments", 1764 |