Many thanks I had another go at after removing all the extra stuff I had added at the bottom /etc/bluetooth/rfcomm.conf and I'm pleased to say it worked fine
(that turned out to be bogus for Jaunty) many thanks dave 2009/7/27 Craig Falconer <[email protected]> > It's entirely commented out by the # at the start of the line. > You need to look elsewhere, or its all dynamically handled by udev or > hotswap or some other daemon. > > > chris wrote, On 27/07/09 16:10: > > Hi, >> here is the etc file >> # >> # RFCOMM configuration file. >> # >> >> #rfcomm0 { >> # # Automatically bind the device at startup >> # bind no; >> # >> # # Bluetooth address of the device >> # device 11:22:33:44:55:66; >> # >> # # RFCOMM channel for the connection >> # channel 1; >> # >> # # Description of the connection >> # comment "Example Bluetooth device"; >> #} >> >> >> >> No, I just plugged it in and it went. >> Didn't follow any guides at all. >> >> A friend from Dunedin was visiting with an early HP laptop, and I >> bluetoothed files over to his beast (running 8.04 I think) no problems. >> Haven't tried it from windows however. >> I notice our rf files are identical. >> Could there be an issue with your usb port? >> >> Hope the file helps >> Cheers Chris >> On Mon, 2009-07-27 at 12:58 +1200, Dave G wrote: >> >>> Chris >>> >>> did you use any particular guide to set it up? >>> >>> I've tried varios goodled options including: >>> >>> http://crunchbanglinux.org/forums/topic/742/howto-bluetooth/ & >>> >>> http://ubuntuforums.org/showthread.php?t=368069&page=1 & >>> http://ubuntuforums.org/showthread.php?t=712968&highlight=gps >>> +bluetooth >>> >>> and also could you post your /etc/bluetooth/rfcomm.conf file? >>> >>> mine looks like this (and works well on Interpid) >>> # >>> # RFCOMM configuration file. >>> # >>> >>> #rfcomm0 { >>> # # Automatically bind the device at startup >>> # bind no; >>> # >>> # # Bluetooth address of the device >>> # device 11:22:33:44:55:66; >>> # >>> # # RFCOMM channel for the connection >>> # channel 1; >>> # >>> # # Description of the connection >>> # comment "Example Bluetooth device"; >>> #} >>> rfcomm4 { >>> bind yes; >>> device 11:22:33:44:55:66; >>> channel 1; >>> #comment "Holux M-241"; >>> } >>> >>> cheers........dave >>> >>> >>> >>> 2009/7/27 chris <[email protected]> >>> Hi, >>> I have it working in Intrepid 9.04 no problems, and have used >>> it to >>> exchange files with 8.04, and my laptop which is intrepid. >>> All the hardware is HP if that helps >>> regards Chris Thimas >>> On Mon, 2009-07-27 at 11:50 +1200, Dave G wrote: >>> > Hi all >>> > >>> > I bought one of the bluetooth dongles that Stephen referred >>> to and >>> > after a bit more experimenting I can confirm that it appears >>> to >>> > behave >>> > the same ( and has the same chipset as the dearer Jaycar >>> model) >>> > >>> > The bad news is that despite quite a bit of experimentation >>> I can not >>> > get it to >>> > transfer any data despite Jaunty recognising (and pairing?) >>> to it >>> > >>> > It works fine in Intrepid and Crunchbang 8.10 however >>> > >>> > Has anyone else had more luck? >>> > >>> > cheers....dave >>> > >>> > 2009/6/20 Dave G <[email protected]> >>> > Hi Stephen >>> > >>> > I have the same what appears to be the same dongle >>> that I >>> > bought from JayCar (part: "Tiny Bluetooth Adaptor >>> CAT. NO. >>> > XC4892") >>> > which incidently was a lot dearer than your TradeMe >>> deal >>> > >>> > My "lspci" is: Bus 003 Device 003: ID 0a12:0001 >>> Cambridge >>> > Silicon Radio, Ltd Bluetooth Dongle (HCI mode) >>> > >>> > I use it to download a Holux M-241 GPS datalogger on >>> my EeePC >>> > 900 netbook and on Crunchbang and Ubuntu Intrepid it >>> works >>> > perfectly. (I use gpsbabel) >>> > >>> > It pairs perfectly etc. as you describe on Jaunty >>> but refuses >>> > to work and will not download any data >>> > >>> > It appears to be a bug in the later versions of >>> bluetooth and >>> > there are bugs logged against that >>> > I'm not that tech but some of the googling referred >>> with >>> > problems in the updated bluetooth stack in Jaunty >>> > >>> > I have spent ages googling and checking forums and >>> as yet have >>> > not found a fix as yet >>> > but it is recognised etc. and pairs etc. as you have >>> described >>> > >>> > In the meantime I am not updating to Jaunty on my >>> netbook the >>> > netbook because of this problem and >>> > would suggest you try Interpid and see how you go >>> > >>> > cheers............dave >>> > >>> > >>> > 2009/6/18 chris <[email protected]> >>> > >>> > >>> > hi Stephen, >>> > i notice that bug was for the alpha6 ver of >>> jaunty. >>> > i am to assume form your post that it is >>> still present >>> > in jaunty then? >>> > >>> > Cheers chris >>> > On Thu, 2009-06-18 at 13:06 +1200, Stephen >>> Irons >>> > wrote: >>> > >>> > >>> > > chris wrote: >>> > > >> >>> > > >> Perhaps I was not quite clear: I can >>> browse files >>> > on the phone from the >>> > > >> PC, and, as you say, it looks just like >>> another >>> > directory. >>> > > >> >>> > > >> The thing that does not work is to use >>> the phone >>> > to initiate the >>> > > >> transfer of a file to the PC. By >>> default, Ubuntu >>> > does not install a >>> > > >> Bluetooth receiving daemon. This comes >>> as part of >>> > the package >>> > > >> 'gnome-user-share', which also installs >>> > capabilities that I do not want. >>> > > >> >>> > > >> Stephen Irons >>> > > >> >>> > > >> >>> > > > I have Bluetooth on my laptop, and under >>> Ubuntu >>> > 9.04 have no issues. >>> > > > Could it be a version problem? >>> > > > >>> > > > Cheers Chris T >>> > > > >>> > > > >>> > > >>> > > I also use 9.04. I based my observation on >>> four >>> > things: >>> > > >>> > > * I could not send a file from the >>> phone to the >>> > PC >>> > > * My phone reports the PC's bluetooth >>> services >>> > as 'network'. >>> > > Bluetooth devices that I can send >>> files to >>> > include the service >>> > > name 'transfer'. I have tried >>> deleting the PC >>> > device from the >>> > > phone and making it rediscover. >>> > > * Bug report >>> > >>> https://bugs.launchpad.net/ubuntu/+bug/349330 >>> > describes >>> > > my problem, and says that the >>> solution is to >>> > install >>> > > 'gnome-user-share' >>> > > * I do not have 'gnome-user-share >>> installed' >>> > > >>> > > I have installed 'gnome-user-share'. A new >>> > configuration menu item >>> > > appears: System > Preferences > Personal >>> File >>> > Sharing. After enabling >>> > > 'Receive Files over Bluetooth', it works >>> as >>> > expected. My phone now >>> > > reports the PC's bluetooth services as >>> 'network; >>> > capture; transfer'. I >>> > > think 'capture' means that the phone >>> thinks that the >>> > PC can act as a >>> > > camera or scanner, but my bluetooth >>> knowledge is a >>> > bit rusty. >>> > > >>> > > I then uninstalled 'gnome-user-share', >>> purely >>> > because it offends my >>> > > sensibilities to have to install a web >>> server for my >>> > computer to receive >>> > > files over Bluetooth. >>> > > >>> > > Perhaps you already have >>> 'gnome-user-share' >>> > installed? Or perhaps KDE >>> > > does something different? >>> > > >>> > > Also there used to be a package called >>> something >>> > like >>> > > 'gnome-obex-server' that provided a >>> Bluetooth file >>> > receiving daemon, but >>> > > it has disappear. I think that it was not >>> part of >>> > Bluez, so it has been >>> > > removed in a general Bluetooth brushing. >>> > > >>> > > Stephen Irons >>> > > >>> > > >>> > > >>> > >>> >>> ======================================================================= >>> > > This email, including any attachments, is >>> only for >>> > the intended >>> > > addressee. It is subject to copyright, is >>> > confidential and may be >>> > > the subject of legal or other privilege, >>> none of >>> > which is waived or >>> > > lost by reason of this transmission. >>> > > If the receiver is not the intended >>> addressee, >>> > please accept our >>> > > apologies, notify us by return, delete all >>> copies >>> > and perform no >>> > > other act on the email. >>> > > Unfortunately, we cannot warrant that the >>> email has >>> > not been >>> > > altered or corrupted during transmission. >>> > > >>> > >>> >>> ======================================================================= >>> > > >>> > >>> > >>> > >>> > >>> >>> >> >> >> > > -- > Craig Falconer > >
