Bluetooth blues



commentary Bluetooth promises the world, or the operation of all within it -- that is, if you can get it to work in the first place.

A Google search for "Bluetooth" and "frustration" returns 35,900 hits. A surprisingly low number, considering how much frustration I've had actually getting my "Personal Area Network" or piconet to provide some kind of productivity gain. (Apparently a "piconet" is a Bluetooth PAN consisting of up to eight active devices in a master-slave relationship -- I'd be happy to get two devices talking to each other in any kind of relationship. I'd be even more amazed if anyone's found a useful reason for a "scatternet", consisting of up to 10 overlapping piconets.)

The concept of a Personal Area Network came from MIT's Media Labs, developed by Thomas Zimmerman and other researchers, and later supported by IBM. The initial method of connecting the increasing number of personal devices -- mobile or smart phones, personal digital assistants, and pagers -- was based on the principle of "capacitive coupling", or using the natural conductivity of the human body to transmit data. From this came inventive concepts such as wearable computer devices.

At around the same time as Thomas Zimmerman's idea (in 1994), Bluetooth was developed in Sweden by Ericsson, joined by Nokia, Toshiba, Intel, and IBM. The technology is now used by thousands of companies, and has been standardised as IEEE 802.15. Recent Gartner research suggests that more than 65 million phones will support Bluetooth by the end of 2004. Take-up is slower than first expected, but as prices for Bluetooth chips fall, the number of devices with this technology will start to increase. Early adoption has been slowed by incompatibility between devices, and there's still no "killer application" to drive the technology.

I question the vision that "the power of the Bluetooth vision begins to really emerge when you consider a world of devices intelligently connected and carrying much of their communication load automatically". Most of the time, my Bluetooth phone establishes a connection with the Bluetooth car kit, but sometimes it doesn't -- for no particular reason. Restarting the phone generally fixes this problem.

I feel we're still a long way from the halcyon scenarios the Bluetooth technology suggests.
Getting the phone to establish a meaningful dialogue with my notebook is a different matter. Three Bluetooth wireless cards later, still no success. Although there is an IEEE standard for Bluetooth, there are different Bluetooth "protocol stacks". They are not, according to Nokia, all the same and not all will work with my Nokia phone. They can't recommend a card that will work, but they can recommend a compatible stack -- it's my responsibility to work out what cards are best to purchase.

But maybe it is the phone that is the problem? Some Bluetooth cards specifically state they won't work with Nokia phones. A number of Web sites have documented the incompatibilities between different Nokia phones, especially when it involves Bluetooth connections between different manufacturers. This is a new phone that (should) be running the latest version of Bluetooth though.

It could also be a telco problem, since the phone does -- for a short time -- manage to establish a Bluetooth connection while dialling the Internet, before returning an error. Optus has been very helpful, but they suggest that it could be the phone, or the Bluetooth card itself.

I feel we're still a long way from the halcyon scenarios Bluetooth technology suggests. I'd be happy if I could just place the phone next to my notebook and synchronise my contacts. Then again, maybe that's just me. I've always thought there's something very wrong with IKEA's approach of selling people a bunch of timber pieces, with instructions in Swedish and an Allen key. Having conquered the furniture world with complexity, Bluetooth could be their assault on technology.

Oliver Descoeudres is marketing manager at network IP/Internet network infrastructure builder and solutions provider NetStar Australia. He can be contacted at marketing@netstarnetworks.com or on 02 9805 9759.

This article was first published in Technology & Business magazine.
Click here for subscription information.

Advertisement

Talkback 8 comments

    I'd have to agree, I had no en ...Anonymous -- 16/03/05

    I'd have to agree, I had no end of drama with the ericsson and windows, but when I switched to MAC, I still use the same ericsson T39 (oldie!) and it really opened the advantage of bluetooth. Although I've a CDMA phone I still use the T39 because of the bluetooth, and iPaq 1940, and bluetooth keyboard, it now works seamlessly!

    The lack of a standard stack o ...Anonymous -- 16/03/05

    The lack of a standard stack on Windows is really the cause of much of the pain. As Mark stated in his comment, on the Mac Bluetooth is very easy and works well. This is mostly because Apple have included a Bluetooth stack - all that the hardware vendors have to do is write a hardware device driver. The situation on Windows is that the vendor has to integrate a hardware device driver, a Bluetooth stack and some form of User Interface - all while trying to ship a product for $50.

    Simple DONT BUY A NOKIA PHONE. ...Anonymous -- 17/03/05

    Simple DONT BUY A NOKIA PHONE. Nokia don't adhere to the standards ( i remember hearing something on the news about a legal case against them). This forces users to purchase certain bluetooth head sets that cost 3 times as much as the generics.

    I have a sony ericsson phone with bluetooth and it works seamlesly with my palm pilot and my computer. I can sync it with outlook to back up my contacts. and use bluetooth to connect to the internet through the phones GPRS service.

    I also have a bluetooth headset that works fine.

    Mr Oliver is right about [A Go ...Anonymous -- 17/03/05

    Mr Oliver is right about [A Google search for "Bluetooth" and "frustration" returns 35,900 hits...]

    The reason: Bluetooth is new to Internet, howerver, I like Bluetooth Network for its short range and about 100K cycles of codes per minutes for "personal computer". I could share internet connection from 2 computers with 2 USB bluetooth adapters by dial-up network without any expensive router.

    Another reason is palmOne didn't show how to hookup for ICS from Tungsten T3 and other desktop computers from their PDF manual. If you know better, can you show it here, step by step, with the answer for such question as:

    Should we setup ICS in dial-up Network from ISP or in Bluetooth Network or in the bridge from desktop Windows XP?

    The problem probably isnt your ...Anonymous -- 19/03/05

    The problem probably isnt your bluetooth connection, rather your cellular provider. I found that my provider (cingular) actually actively blocks data communications other than those they provide with their service (ie. trying to dial a dial up isp, or faxing). on the other hand, if you tell your phone to dial a specific code, i can't remember what mine was, like #767 something, it instructs the phone to use the carriers data capability, and it works fine...of course your carrier will definetly bill you per kilobyte for this type of usage.

    I'm not disagreeing that bluetooth needs some work, i know i've had to detach\reattach my adapter many times just to get the computer to recognize it, then finding good software to make it mate with my phone is a whole other nightmare.

    My buddy just got a Chrysler 3 ...Anonymous -- 22/03/05

    My buddy just got a Chrysler 300C. He came in to the office, with the 300C's manual in hand, asking about "Bluetooth". I recommended the Motorola Razr that came up as supporting the protocol, and now he can do voice activated dialing on his cell through his car. As he is in pharmaceutical sales, and always in and out of the car/ driving, this was an invaluable tool.
    Granted, he had to return te Razr to Cingular to get a replacement phone (low to no signal, dropped calls), but all is well in his world now. :)

    Having been an avid user of bl ...Anonymous -- 24/03/05

    Having been an avid user of bluetooth functionality since the my Ericsson T68, I feel I should share some of my interesting experiences with the standard.

    Firstly, I should mention that I have never at any point been able to seamlessly syncronize my handset with my PC, no matter what manufacturer. I've had Ericsson, Nokia, Motorola, Siemans, and Sony Ericsson, and never have any of them been able to complete the most simple of Bluetooth based tasks. I've gone through about a dozen bluetooth dongles, and countless hours of attempting to set-up the correct com ports and what not.

    My view on bluetooth was much the same as yours in your article, that is, until I purchased my first Apple computer in May of last year. Having never have owned an Apple in my life, it was a huge move for me, and I must say, if not to be impressed by the speed, reliability, stability, etc... The bluetooth ease of use and compatibility on OS X is absolutely astounding. If any PC user has experienced "bluetooth" on their Wintel machine (or I should say, lack of experience), should really go to their nearesst Apple reseller, and ask to have bluetooth demonstrated. Not with some salesman pre-loaded bluetooth device in store, but get them to do it with your own phone, there and then, and see what Bluetooth is all REALLY about. Its really a cool technology that allows you to do much more than you'd think it can do... It just needs to be implemented right, which Apple did, and did it damn well.

    WOW great to see it's not just ...Anonymous -- 18/05/05

    WOW great to see it's not just me who got an extra few grey hairs with my attempt at connecting Bluetooth. What was I trying to do? simple I thought.. I have a Nokia phone, a Sony Ericsson headset and a HP notebook. Phone and headset connect, phone and notebbok connect but no connection with notebook and headset! Thanks to hours and hours of chat with our good friends in India (HP) and not taking "no" for an answer at three different levels YES it finally works. No it wasn't incompatibale, no the headset doesn't need driver software and no I don't want to "Just not use it" it was simply a difficulty in getting the setting right! Anyway love being totally handsfree about the house and chatting to a mate in Thailand via Skype for free :)

Add your opinion

Latest Videos

Sponsored content

Power Centre - Content from our premier sponsors

Blogs

Tags

Back to top

Featured