Re: Connecting cell phones via bluetooth
Chris <[email protected]>
| Newsgroups | gmane.linux.mandrake.newbie |
|---|---|
| Message-ID | <[email protected]> |
On Mon, 2009-10-05 at 21:07 +0100, [email protected] wrote: > Hi Chris > > I don't have mini usb cable for my Nokia 2630 phone. I can browse my > phone's folders from my dell netbook using bluetooth. Now I think I'm > using obexftp bluetooth. I found a link which might or might not work for > you. I tried this on my Mandriva 2009.1 but didn't have any joy. I will > need to try this on my netbook which is configured correctly. > > Do you know whether pictures can be posted to this forum? > > Here's the link I found: > http://www.go2linux.org/transfer-files-with-bluetooth-Linux > > Regards > kevin Thanks Kevin, I'm at the link. Here's what happens with the Motorola: On device history the Motorola shows both localhost-0 and the Nokia 2600c-2b so it 'sees' the computer because in Applications > Tools > Gnome > Bluetooth both phones are recognized as known devices and have the "friendly name" of localhost-0. Scanning the Motorola with "hcitool scan" nets this: [chris@localhost ~]$ hcitool scan Scanning ... (nothing) Scanning the Nokia gives this: [chris@localhost ~]$ hcitool scan Scanning ... 00:21:FE:89:34:0A Nokia 2600c-2b Running sdptool browse 00:21:FE:89:34:0A gives me this: [chris@localhost ~]$ sdptool browse 00:21:FE:89:34:0A Browsing 00:21:FE:89:34:0A ... Service Name: OBEX Object Push Service RecHandle: 0x10000 Service Class ID List: "OBEX Object Push" (0x1105) Protocol Descriptor List: "L2CAP" (0x0100) "RFCOMM" (0x0003) Channel: 9 "OBEX" (0x0008) Language Base Attr List: code_ISO639: 0x656e encoding: 0x6a base_offset: 0x100 Profile Descriptor List: "OBEX Object Push" (0x1105) Version: 0x0100 Service Name: OBEX File Transfer Service RecHandle: 0x10001 Service Class ID List: "OBEX File Transfer" (0x1106) Protocol Descriptor List: "L2CAP" (0x0100) "RFCOMM" (0x0003) Channel: 10 "OBEX" (0x0008) Language Base Attr List: code_ISO639: 0x656e encoding: 0x6a base_offset: 0x100 Profile Descriptor List: "OBEX File Transfer" (0x1106) Version: 0x0100 Service Name: Nokia PC Suite Service RecHandle: 0x10002 Service Class ID List: "Serial Port" (0x1101) Protocol Descriptor List: "L2CAP" (0x0100) "RFCOMM" (0x0003) Channel: 15 Language Base Attr List: code_ISO639: 0x656e encoding: 0x6a base_offset: 0x100 Service Name: COM 1 Service RecHandle: 0x10003 Service Class ID List: "Serial Port" (0x1101) Protocol Descriptor List: "L2CAP" (0x0100) "RFCOMM" (0x0003) Channel: 3 Language Base Attr List: code_ISO639: 0x656e encoding: 0x6a base_offset: 0x100 Service Name: Voice Gateway Service RecHandle: 0x10004 Service Class ID List: "Handsfree Audio Gateway" (0x111f) "Generic Audio" (0x1203) Protocol Descriptor List: "L2CAP" (0x0100) "RFCOMM" (0x0003) Channel: 13 Language Base Attr List: code_ISO639: 0x656e encoding: 0x6a base_offset: 0x100 Profile Descriptor List: "Handsfree" (0x111e) Version: 0x0105 Service Name: Audio Gateway Service RecHandle: 0x10005 Service Class ID List: "Headset Audio Gateway" (0x1112) "Generic Audio" (0x1203) Protocol Descriptor List: "L2CAP" (0x0100) "RFCOMM" (0x0003) Channel: 12 Language Base Attr List: code_ISO639: 0x656e encoding: 0x6a base_offset: 0x100 Profile Descriptor List: "Headset" (0x1108) Version: 0x0100 Service Name: SyncML Client Service RecHandle: 0x10007 Service Class ID List: UUID 128: 00000002-0000-1000-8000-0002ee000002 Protocol Descriptor List: "L2CAP" (0x0100) "RFCOMM" (0x0003) Channel: 11 "OBEX" (0x0008) Language Base Attr List: code_ISO639: 0x656e encoding: 0x6a base_offset: 0x100 Service Name: SIM ACCESS Service RecHandle: 0x1000c Service Class ID List: "SIM Access" (0x112d) "Generic Telephony" (0x1204) Protocol Descriptor List: "L2CAP" (0x0100) "RFCOMM" (0x0003) Channel: 4 Language Base Attr List: code_ISO639: 0x656e encoding: 0x6a base_offset: 0x100 Profile Descriptor List: "SIM Access" (0x112d) Version: 0x0101 Using the link you provided I can get the Nokia to work just fine now but still no joy at all with the Motorola. It's like it doesn't even exist as far as connecting via bluetooth is concerned. Any other suggestions? Thanks very much for the link, much appreciated. Chris -- KeyID 0xE372A7DA98E6705C
signature.asc
(application/pgp-signature, 197 B)
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iEYEABECAAYFAkrKdpMACgkQ43Kn2pjmcFx18gCeKERC3lWiTxt9gDfwgsiJJ7VM ZFMAn0tIlK7TA80em2A94QG2Hgw665oU =O2Ar -----END PGP SIGNATURE-----