Slashdot Mirror


Nokia's Wibree Takes on Bluetooth

narramissic writes "Nokia has developed a new, short-range wireless technology, called Wibree, that it says is a lot more power efficient than Bluetooth, which means it could be used in smaller and less costly devices. It can also use the same radio and antenna components as Bluetooth, helping keep costs down further. Wibree could compete with Bluetooth in the workplace as a way to link keyboards and other peripherals to computers. But it could also have more interesting applications for consumers, in devices such as wrist watches, toys and sports equipment." What does this say about Bluetooth, considering Nokia is a member of the Bluetooth Promoters group?

120 comments

  1. It's probably too late by Colin+Smith · · Score: 4, Insightful

    The network effect is cementing bluetooth in place. I can buy bluetooth keyboards, mice, earpieces already. OTOH, like Sony's memory stick, this may just be a way of locking dumb Nokia customers into a proprietary solution.

    --
    Deleted
    1. Re:It's probably too late by ne0nimda · · Score: 2, Funny
      But it could also have more interesting applications for consumers, in devices such as wrist watches, toys and sports equipment.


      SWEET! I can sync my wrist watch with my computer now? I've always thought that networking a watch to connect w/ my computer and transferring the time over was soooo much more efficient than using those little dials.

      Now imagine the new hacking vulnerabilities! Millions of corporate workers late; all of whome blame hackers for altering their alarm clocks!
    2. Re:It's probably too late by HerrGoober · · Score: 1

      Seems bluetooth may have suffered from design by committee, ie too many conflicting requirements limiting its longevity.Whereas this oddly named contender is claimed not only to be much lower power (definitely a powerful factor in mobile tech) but also higher bandwidth and channel hopping, a la UWB. This, combined with the ability to reuse existing design of antennas etc, may well make it a winner.

    3. Re:It's probably too late by Colin+Smith · · Score: 1

      Read up on the Network Effect:
      http://en.wikipedia.org/wiki/Network_effect

      It also happens to be a standard:
      http://www.ieee802.org/15/pub/TG1.html

      It doesn't matter so much whether this new system is better or even marginally cheaper. What matters is, the number of people and devices which support it. By being bluetooth compatible, device manufacturers are also compatible with almost every mobile phone, most PCs, earpieces, printers etc.

      --
      Deleted
    4. Re:It's probably too late by TheRaven64 · · Score: 2, Insightful

      You laugh, but I would find it useful for my watch alarm to be sync'd with events in my calendar. My mobile 'phone does this already, but I am more likely to have my watch with me than my mobile.

      --
      I am TheRaven on Soylent News
    5. Re:It's probably too late by kevinadi · · Score: 1

      Nokia is not a charity organization. It'll do lock ins if it's possible. Considering the amount of backstabbing that happens in wireless standardization, I'm not surprised Nokia is hiding this until the last moment and caught everyone by surprise. If this "proprietary solution" intending to lock "dumb users" actually works better than bluetooth, me and a million other people will buy it.

      I think bluetooth sucks. The best technology (like wlan) is there without me noticing it, but if it's not there, it's annoyingly obvious. OTOH, bluetooth is glaringly in the way, it sort of makes sure that I know I'm using bluetooth technology(tm). Add defective security (visible/hidden bullshit that everyone have to deal with), slow connection handshake, really slow discovery (at least in phones) and high power consumption, then bluetooth is ripe for a fall.

      What's important to remember is that this is hardware technology. It's not that easy to update like software, people have to BUY new stuff if they want to update their bluetooth. I think even in its 2.0 incarnation, bluetooth is not good enough. If Nokia can get their wibree right the first time (fast discovery, fast handshake, no-hassle security and low power) then I say we'll see bluetooth disappearing within 5 years or so.

  2. Stupid name kills technology by BadAnalogyGuy · · Score: 5, Interesting

    Sounds like they are trying to succeed in a non-existant market. The actual applications of Bluetooth are few and far between. The 'wireless' office never amounted to much and you know you look like an idiot with that earpiece and talking to yourself at Starbucks.

    So what is a company to do? How about rebrand the technology with a worse name than it originally had? That's the ticket!

    1. Re:Stupid name kills technology by __aaclcg7560 · · Score: 1

      Nokia's has fallen under the influence of Nintendo's marketing department. Although it should be the Wiibre if they're going to name it correctly.

    2. Re:Stupid name kills technology by aadvancedGIR · · Score: 2, Interesting

      Funny enough, one of the few clever (and relatively sucessful) application of bluetooth was an universal handfree kit for cars. BTW, we are talking about a phone manufacturer that tells us that soon, the devices they sell will do almost anything except voice calls, so I'm not that surprised.

    3. Re:Stupid name kills technology by richdun · · Score: 4, Funny

      [Mister Ed voice] Whoa Wiibre! [/Mister Ed voice]

    4. Re:Stupid name kills technology by Anonymous Coward · · Score: 0

      hahahahaha

      i miss mister ed.

    5. Re:Stupid name kills technology by bazorg · · Score: 2, Insightful

      you know you look like an idiot with that earpiece and talking to yourself at Starbucks.The first time I visited a cold snowy place, a lot of people seemed comfortable about walking around with their hands in their pockets and using bluetooth headsets.

    6. Re:Stupid name kills technology by R2.0 · · Score: 1

      Can you send a memo to al of the dumbass OSS names out there? they don't seem to have gotten the message.

      --
      "As God is my witness, I thought turkeys could fly." A. Carlson
    7. Re:Stupid name kills technology by R2.0 · · Score: 1

      And yet they still look like idiots. Go figure.

      --
      "As God is my witness, I thought turkeys could fly." A. Carlson
    8. Re:Stupid name kills technology by Skreems · · Score: 1

      How stupid did people look when they first started using a handset? Most new technology looks odd until it's been around for a while.

      --
      Slashdot needs a "-1, Wrong" moderation option.
      The Urban Hippie
    9. Re:Stupid name kills technology by nasch · · Score: 1

      Besides, anybody who rejects a useful device because they're afraid they'll look stupid using it deserves to keep using the old tech.

    10. Re:Stupid name kills technology by LarsWestergren · · Score: 1

      Sounds like they are trying to succeed in a non-existant market. The actual applications of Bluetooth are few and far between. The 'wireless' office never amounted to much and you know you look like an idiot with that earpiece and talking to yourself at Starbucks.

      Maybe in the US, but Bluetooth is pretty popular in Europe actually. It is very common for blue collar workers to have handsfree headsets for instance. Very handy to be able to talk to your colleagues on the roof and still have your hands free.

      --

      Being bitter is drinking poison and hoping someone else will die

    11. Re:Stupid name kills technology by tehcyder · · Score: 1
      you know you look like an idiot with that earpiece and talking to yourself at Starbucks
      I find it helps with that whole "pretending you're a secret agent to impress the chicks" thing like the guy in "True Lies".
      --
      To have a right to do a thing is not at all the same as to be right in doing it
  3. What does this say about Bluetooth? by Reality+Master+201 · · Score: 2, Informative

    Uh, that Nokia would rather sell a technloogy that's all their own than promote one they don't completely control?

    1. Re:What does this say about Bluetooth? by jspayne · · Score: 4, Informative
      Uh, that Nokia would rather sell a technloogy that's all their own than promote one they don't completely control?
      ...especially one that was originally developed by rival Ericsson, who is the #1 seller of Bluetooth chipsets?
    2. Re:What does this say about Bluetooth? by IAmTheDave · · Score: 1
      ...especially one that was originally developed by rival Ericsson, who is the #1 seller of Bluetooth chipsets?

      If the new tech is compatable with bluetooth radios and antennas, how does this rage against the Ericsson machine?

      Further, I wonder if it's simply a matter of a software change on the hardware - which would make manufacturing of this stuff a no-brainer, and bluetooth receivers could quickly become dual-mode receivers.

      --
      Excuse my speling.
      Making The Bar Project
    3. Re:What does this say about Bluetooth? by lawpoop · · Score: 3, Informative

      I got modded down as 'troll' and 'offtopic' for stating this ealier, but aside from the corporate competition, there is also the social/ethnic competition between Swedes and Finns. Actually, I think it is felt more by the Finns that they are in the shadow of Sweden. Sweden ruled Finland for a long time, and Sweden is wealthier than Finland, and Finns sort of have this complex about not being wholly Scandinavian.

      I am not just making this up. If you read the Finnish epic, which is said to characterize the finnish temperament, the hero Vainamoinen is actually an anti-hero. He is born old, never in his prime. One of the first stories about him is when he approaches a young bathing maiden and she runs away screaming. In the climax of the story, he rallies the troops to win back a magical device from a tribe of harpies, only to lose it in the sea during the epic battle. He's just not a winner.

      The parent I posed my original topic had said that 'a better tech had come along'. What a socially naive geek perspective. Sure, new things just drop out of the sky like clockwork. People are never motivated by petty social identies, like Ohio State vs. Michigan, US vs. Canada, MS vs. Apple, Ericsson vs. Nokia, or Finland vs. Swedend.

      So my votes goes for a Nokia vs. Ericsson, Finland vs. Sweden thing.

      --
      Computers are useless. They can only give you answers.
      -- Pablo Picasso
    4. Re:What does this say about Bluetooth? by lawpoop · · Score: 1

      Sorry, I missed a word: the name of the Finnish epic is the 'Kalevala'.

      --
      Computers are useless. They can only give you answers.
      -- Pablo Picasso
    5. Re:What does this say about Bluetooth? by caluml · · Score: 1

      And one other thing - language. Finnish is pretty much only spoken by them and Hungary. Swedish has commonalities with Danish and Norwegian, I'm lead to believe.
      So, if I had to learn either Swedish or Finnish, it'll be .se for me.

    6. Re:What does this say about Bluetooth? by lawpoop · · Score: 1

      To get a bit more specific, Finnish and Hungarian belong to the Finno-Ugric language family. Most of the rest of Europe speak languages in the Indo-European family.

      Hungarian and Finnish are mutually unintelligible. They look pretty dissimilar in written form. The closest language to Finnish is Estonian -- I'm not sure if Estonia is considered Europe. It was part of the Soviet Union; now it is independent and a member of the EU. Finns and Estonians can *basically* understand each other and the written languages look pretty similar.

      I think that the most commonly accepted theory is that the Finns are descendant from the Mongolian Huns who conquered a lot of Asia and Eastern Europe.

      As far as the impact for Finns, it just makes them harder to pigeon-hole. People usually think they are just another group of Scandinavians, like Danes or Norwegians, but then they find out that they speak a totally different language. Then, people usually assume that they must be Russian or Slavic. But they aren't. They are Finnish ;)

      It is true that Finland has been heavily influenced by Russia and Sweden, but still they are fairly unique. It is an interesting culture.

      --
      Computers are useless. They can only give you answers.
      -- Pablo Picasso
    7. Re:What does this say about Bluetooth? by marsu_k · · Score: 1
      I don't deny the rivalry between Finns and Swedes (as a Finn, I have experienced it first hand many many times - I find it both immature and irritating, but these things don't change very quickly), but I don't think that plays any role in this. While Nokia has its headquaters in Finland (which they've threatened to move abroad several times when there have been discussions about raising some taxes and/or lowering others), it is a multinational corporation that doesn't have a national identity.

      Rather, I think this is an attempt of embrace-and-extend, kind of like they did with J2ME(*). The idea here would be that Nokia can say "if you want to use the latest and greatest Mobil-O-Gadget, you'll have to have a Nokia headset" - unlike with Bluetooth gadgets, which (in theory) work with any headset that supports Bluetooth. Of course they will licence it to other manufacturers... but for example Series60 can be licenced as well; apart from Siemens SX-1 (I don't think that's manufactured anymore), I don't recall any other non-Nokia models that support it.

      Having said that, the basic concept from this press release disguised as an article seems reasonable. While Bluetooth is certainly an improvement over WLAN WRT power usage, there's always room for improvement. We'll see how it turns out.

      (* When MIDP 1.0 came, Nokia felt, somewhat rightfully, that the spec was lacking some essential features, so they created their own extension, i.e. Nokia UI API. This, combined with the market share of Nokia at least here, led to some developers writing games for only Nokia phones, so the plan was a partial success. With MIDP 2.0 the situation has got a bit better. Now who in their right mind would want to play games on their cell phone is another discussion...)

    8. Re:What does this say about Bluetooth? by ladoga · · Score: 1
      I think that the most commonly accepted theory is that the Finns are descendant from the Mongolian Huns who conquered a lot of Asia and Eastern Europe.

      Finnish has been spoken in finland atleast about 3000 years, long before Huns (which actually invaded middle and southern europe in 4th century, never scandinavia).

      If any "european" people would be related to Huns it would be Turks (which originate from same area in central asia). Together cooperating with Huns were also some southern fenno-ugric tribes (in addition to mongolian, tungusian, caucasian, turkish and iranian ones), but this has more to do with the fact that Huns needed allies and steppe warriors from areas under their rule.

      Fenno ugric languages closely related to finnish (closer than sàmi or estonian) can and could be found in northern russia, but most of population has been russianized during the last century.

      http://upload.wikimedia.org/wikipedia/commons/8/81 /Finno-Ugric_languages.png
    9. Re:What does this say about Bluetooth? by ladoga · · Score: 1

      Here is illustrated Kalevala for those interested: (sorry about the clutter)

    10. Re:What does this say about Bluetooth? by ladoga · · Score: 1

      Damn! Slahsdot ate my link! :E

      Another try:
      http://altreligion.about.com/library/texts/kaleval a/bl_kalevala.htm
      *will use the preview next time*

  4. Too many technologies by ocdude · · Score: 5, Interesting
    While it's always cool to hear about new tech coming out, it makes me crazy when I hear about a new tech that is going to replace an "older" tech when the "older" tech hasn't even been around for too long. So, right now, I don't even own any bluetooth things. If this new Wibree thing starts to proliferate as much as bluetooth, does that mean that now I will have to monitor everything I buy to make sure that it works with my particular hardware? IE will I have to make sure my new laptop has both bluetooth (for "legacy devices) and wibree for whatever nokia throws at us?

    The same can be said about just about any new tech that is to replace and not be compatible with old tech. USB, IMHO, did it right. USB2.0 is backwards compatible with USB1.1

    1. Re:Too many technologies by QuasiEvil · · Score: 1

      It's like they introduce new "standards" for the sake of having new standards, not because they address any particular problem. I have bluetooth crap all over the place (scanners, headsets, printers, telemetry nodes), and I have no intention of changing it all over. Much like anything that takes a Sony memory stick, it's just another reason to avoid certain vendors and products.

  5. Nintendo? by pipatron · · Score: 2, Funny

    Nintendo Wiibree anyone?

    --
    c++; /* this makes c bigger but returns the old value */
  6. It tell me that ... by Anonymous Coward · · Score: 1, Interesting

    ... there is going to be one more application in the ISM band. Not that it is overcrowded already, no.

  7. Bluetooth 2.0? by erroneus · · Score: 4, Insightful

    Perhaps in the same way USB 2.0 emerged, Bluetooth 2.0 is due? Faster, lower power requirements, backward compatibility. Seems like the natural and sensible thing to do.

    1. Re:Bluetooth 2.0? by skuzz03 · · Score: 1

      Bluetooth 2.0 has been around for a while...

    2. Re:Bluetooth 2.0? by Andy+Dodd · · Score: 4, Informative

      Been around for a while.

      Higher data rates, higher sound quality for headsets, error correction for headset audio (read: significantly increased range and quality).

      They still haven't fixed the compatibility nightmares of Bluetooth. God forbid you might want to use a Motorola headset with a Treo for example! It'll work, but barely, and most functionality (such as picking up a call from the headset) won't work.

      The state of Bluetooth stacks for Windows is even worse. Microsoft's stack doesn't seem to support anything other than the serial profile - no headset audio, no AD2P. Only 50% of the stacks available a few months ago supported headset audio, even fewer supported AD2P (high quality stereo audio). Every single Bluetooth stack insists on making the headset the default audio device for the entire system, which is useless (and incredibly annoying) when you only want to use it for a SIP/IAX softphone, Skype, Teamspeak, Ventrilo, or similar stuff. Last but not least, even though most Bluetooth stacks support the majority of hardware chipsets out there, every single one is locked to a specific device vendor. i.e. if you buy a Dell with a CSR chipset, it'll come with the Toshiba bluetooth stack (worthless since it puts all serial devices at COM40 or above which most apps don't support). The WIDCOMM stack works with CSR chipsets, but is locked to whatever vendor's CSR-based dongle you got the stack with. You can't even upgrade to a recent version in most cases. (Buy a dongle with a WIDCOMM 3.x stack, and you can't upgrade to 5.x legally).

      From what I've heard, both Microsoft and Logitech BT keyboards/mice don't work well unless you use the dongle and BT stack that came with the hardware - what's the point of being Bluetooth in that case?

      About the only Bluetooth device I've ever used that worked well is my GPS receiver. I've tried 3 different headsets with my Treo and 2-3 different BT stacks on my PC for use with those headsets and have never been satisfied with the results.

      --
      retrorocket.o not found, launch anyway?
    3. Re:Bluetooth 2.0? by _marshall · · Score: 1

      There already is a Bluetooth 2.0, and beyond that, there is an Enhanced Data Rate(EDR) expansion that improves bandwidth speeds. I'm curious how effecient the Nokia solution will be, as bluetooth chips are getting more and more power friendly. I bought a Plantronics 645 with DSP (bluetooth headset) recently, and this thing gives me several days of standby time and at the very least 7-8 hours of talk time. I end up charging it like twice per week... if it could be moved down to "once" per week, that would be really nice. I've also seen that newer bluetooth stereo headsets (A2DP profile) are getting better with battery life as well.. I currently have a set of Plantronics P590s.. they give me about 8 hours of uninterrupted wireless stereo, but I've seen new headphones from Logitech and Motorola that are supposedly giving up to 18 hours of continuous playback!

      Another concern is range.. there are basically 2 range sets in bluetooth as we know it today: Class 1 (100 meters) and Class 2 (10 meters). Class 2 is pretty much every device on the market right now, save a few bluetooth adapters that are trying to be ambitious. I would be interested in seeing a Class 1 implementation that mobile devices (such as headsets and cellphones) could use, that offers the same (or similar) power requirements as today's Class 2 devices.

  8. Doesn't say much by AlastairMurray · · Score: 3, Interesting

    From the summary:

    "What does this say about Bluetooth, considering Nokia is a member of the Bluetooth Promoters group?"

    It says that Bluetooth is years old and now some that is (possibly) better has come along, nothing more.

  9. It says our worst fears were true... by ivan256 · · Score: 1, Insightful

    What does this say about Bluetooth

    It says that the stupid Trademarkable Name(TM) thing wasn't a one off, and we can expect all future networking interfaces to have some stupid name in the future. Not only will that be insanely annoying, but it will allow companies to collect royalties to be able to claim compatability with 'open' protocols indefinatly. Yes, technology companies have finally found a direct revenue way to exploit the previously harmless trademark laws, and to bypass that pesky patent term length limit.

  10. Weary. by Anonymous Coward · · Score: 0, Funny

    I'm kind of tired of talking about this. We talk about it every week. Let's talk about something else.

  11. Security this time? by RedDirt · · Score: 4, Insightful

    One can only hope they've invested more time in securing the communications channel than in Bluetooth. Bluesnarfing for the win! Or something. =/

    --
    James
  12. Wibree vs ZigBee? by uss_valiant · · Score: 2, Interesting
    From TFA:
    Wibree isn't the only contender for use in wireless sensors, however. Zigbee is an ongoing standardization project and has similar characteristics to Wibree.
    I know BT and ZigBee (about ZigBee), but never heard about Wibree. I'm pretty disappointed that Nokia wants to go with this proprietary approach.
    Anyway, there's a lot going on in IEEE 802.15 (Personal Area Network).
    1. Re:Wibree vs ZigBee? by Hamoohead · · Score: 1

      Wibree make your time -- take out every Zig.

      --
      "If your parents never had children, chances are you wonât either." -Dick Cavett
  13. I've got Bluetooth on my phone, and never use it. by PHAEDRU5 · · Score: 4, Interesting

    I have a Nokia phone, and it has Bluetooth.

    When I bought the phone, I also bought a Bluetooth headset. I gave up on the Bluetooth pretty quickly: The headset would only run for about five hours before needing to be recharged, and the phone's standby time was cut down massively.

    This isn't a complaint about Bluetooth as such. It's more that current devices, as delivered, don't provide long-enough standby time, never mind talk time, when Bluetooth is enabled.

    --
    668: Neighbour of the Beast
  14. Re:I've got Bluetooth on my phone, and never use i by SenseiLeNoir · · Score: 1

    SOme nokia handsets/headsets keep the bluetooth connection on continously. This was a major complaint about the Nokias.

    Sony Ericssons tend to pulse/ping the connection, only turning on the full link when there is a call, giving far greater standby times.

    Again, its more a case of different devices doing different things. Each has its advantages and disadvantages

    --
    Have a nice day!
  15. Golden golf clubs by maubp · · Score: 1

    Quoting, Wibree sensors could also be placed in a gold club and used to upload data to the Internet about a player's swing, again via a mobile phone, where a golf instructor could offer advice about improving his or her game.

    Would that gold club be an iron or a wood? Maybe its a putting club?

    Anyway, I guess any rich golfers that have a gold golf club won't mind the extra expense of a radio linked computer sensor... but it would spoil their boast of "My club is solid gold!".

    1. Re:Golden golf clubs by Anonymous Coward · · Score: 0

      Hi, George. This is your golf instructor. Chunk the heavy gold clubs and get some titanium/carbon fiber clubs, already. Your drive will thank you.

    2. Re:Golden golf clubs by Anonymous Coward · · Score: 0

      Years ago I knew of someone who sold gold clubs. Not to be ostentatious, he chrome-plated them too. Puzzling how many rich customers managed to lose them while on trips abroad.

  16. Bluetooth is way too power consuming by Anonymous Coward · · Score: 0

    I attended the press conference Nokia held this morning in Finland and published Wibree. It sounded very interesting. Nokia is very often innovating new technologies which make their phones different from competitors. Making them wide known hasn't always succeed, but I think this will. And you in North America, understand if you don't agree but your mobile phone offering and services are a bit behind Europe.

    All of you who really use Bluetooth daily to connect your car handsfree, synchronize your calendar and contacts, messages etc. on your phone, know that Bluetooth takes quite a lot power out of the battery. This might be a solution for this for everything else as well. I don't want to always disable the Bluetooth on my phone just to save battery.

  17. Bluetooth works fine on a Mac... by SuperKendall · · Score: 2, Interesting

    Hate to bring up the "it just works" thing but Bluetooth works fine on a Mac, with headsets or keyboards or whatever. All new macs come with Bluetooth 2.0 integrated already, and have since the Intel switch (plus a bit before that).

    --
    "There is more worth loving than we have strength to love." - Brian Jay Stanley
    1. Re:Bluetooth works fine on a Mac... by dfghjk · · Score: 1

      Most of the bluetooth phones i've tried don't "just work" with a mac.

    2. Re:Bluetooth works fine on a Mac... by aclarke · · Score: 1

      The only one I tried worked great, although it didn't "just work" in the usual Mac way. I had to do some non-standard setup for some of this but I used it as a wireless GPRS modem, synced via bluetooth, and had Salling Clicker installed giving me all sorts of fun goodies. It was an Ericsson something-or-other. I'm back to CDMA land now so I don't use it any more.

      Currently I use a Logitech bluetooth mouse which "just works", as well as an Apple bluetooth keyboard which "just works", as one would expect.

    3. Re:Bluetooth works fine on a Mac... by s4ck · · Score: 1
      Hate to bring this up but the bluetooth on the iMac has been nothing but nightmares. the mouse and keyboard bluetooth is riddle with problems. after too many phone calls to apple support and hardware exchange i switched to whole damn thing to good old usb cable...

      now THAT works.

    4. Re:Bluetooth works fine on a Mac... by unPlugged-2.0 · · Score: 1

      Also Mac has known problems with supporting AD2P (audio over bluetooth).

      Not flaming the Mac as I own one but their bluetooth support is not much better than Windows.

    5. Re:Bluetooth works fine on a Mac... by Moofie · · Score: 1

      My Treo 650 works great with my Powerbook. Zero drama.

      --
      Why yes, I AM a rocket scientist!
    6. Re:Bluetooth works fine on a Mac... by dfghjk · · Score: 1

      Mice and keyboards "just work" in Windows, too, as do phones once you go through the effort of installing software. The point is that there isn't a difference. I use a MS BT mouse with my MBP. It just worked just as it did with my Windows notebook.

    7. Re:Bluetooth works fine on a Mac... by dfghjk · · Score: 1

      Don't know in what way. The Treo 650 in particular is incompatible with address book standards due to it's categories tag. When I had a Treo 650 (which I gave up because it was so unstable) it would not work with Tiger out of the box. That may have changed at this point. More likely, you've installed the Palm software and use BT with that. When I owned both, in order to support the 650 on mac through mac's address book, you had to install the Palm software PLUS a 3rd party bridge--- hardly "it just works".

      I'm not suggesting this is Apple's fault but I do object to the claim that the 650 works with zero drama. Cell phones vary in their support of BT standards and the Treo 650 is specifically one of those.

    8. Re:Bluetooth works fine on a Mac... by Moofie · · Score: 1

      Hmm. I happen to use the Missing Sync software, which adds some handy features, but before I installed that, I was able to sync with iCal and Address Book without a problem. I don't know if categories are supported out of the box, but it did work fine.

      I don't believe address book synchronization is part of the Bluetooth standard, so I definitely agree with you that compatibility is an issue. However, it's not an issue with Bluetooth.

      --
      Why yes, I AM a rocket scientist!
    9. Re:Bluetooth works fine on a Mac... by dfghjk · · Score: 1

      Did you also install Palm Sync first?

      Yes, Missing Sync is the software but it isn't part of OS X and the claim was that BT "just worked" with a mac. That is not true for cell phones. Some do work, Moto and some SE in my experience, and address sync *should* be part of that. Ideally, you should be able to sync *any* BT cell phone address book to mac and then back to any other cell phone. That most definitely does not work. It doesn't work in Windows either, but then again Windows isn't the one that advertises how well it "just works" with arbitrary peripherals. Windows doesn't talk to Japanese digital cameras apparently either. ;-) Could have fooled me.

      Address book formats are defined in the BT standard (although I'm not an expert on BT). The category field has always been dropped for me when syncing a 650 to another BT address book because that field is undefined in the standard. Too bad because I like it. :-( The best way to sync a Treo 650 is with the Palm software so the issue is really moot.

      Ever tried syncing a WM5 phone to OS X? Yeah, I know, who would want to. Nevertheless, it doesn't "just work" either. I get tired of importing my addresses one vCard at a time each time I change phone platforms.

    10. Re:Bluetooth works fine on a Mac... by TheRaven64 · · Score: 1
      My last three 'phones have been an Ericsson T68, a Sony Ericsson T610 and a Nokia N70. All of these have sync'd with iCal and Address Book correctly, they have allowed me to transfer files between the Mac and 'phone easily via Bluetooth and have functioned as a wireless modem over Bluetooth with minimal configuration.

      Perhaps you could be more specific?

      --
      I am TheRaven on Soylent News
    11. Re:Bluetooth works fine on a Mac... by dfghjk · · Score: 1

      My Nokia E61, Treo 650 and my WM5 phone (Tmobile MDA) have all not worked. My SE's and Moto's have.

      I think it's well known that cell phones are problematic. If they weren't, Apple wouldn't feel the need to enumerate the ones that were supported.

      http://www.apple.com/macosx/features/isync/devices .html

      BTW, this is not a list of BT supported phones, it's a list of ALL supported phones. Some don't work with BT. Not a very big list is it?

    12. Re:Bluetooth works fine on a Mac... by Moofie · · Score: 1

      "Did you also install Palm Sync first?"

      Nope. iSync in Tiger doesn't need a separate conduit, although it used to. Having said that, I don't necessarily understand why installing drivers/software for a phone would not be a part of a reasonable "what is necessary to make it work" rigamarole.

      I mean, if I want to use a printer, I have to install drivers, right? Some drivers are bundled with the OS, some are not. Not a big deal.

      "Ever tried syncing a WM5 phone to OS X?" Eww. No. Why?

      --
      Why yes, I AM a rocket scientist!
    13. Re:Bluetooth works fine on a Mac... by dfghjk · · Score: 1

      "Having said that, I don't necessarily understand why installing drivers/software for a phone would not be a part of a reasonable "what is necessary to make it work" rigamarole."

      I think it is reasonable, yet mac people like to make a point of "it just works". If you install phone drivers on Windows then "it just works" too. Getting phones supported in Windows and OS X requires basically the same effort and that was my point. I think integrated PIM apps and iSync is a great feature of OS X but I'd like to see more stuff work out of the box. After all, BT defines profiles for that reason (although honestly it's probably more the fault of the phones).

      ""Ever tried syncing a WM5 phone to OS X?" Eww. No. Why?"

      Hehe. Why indeed. I try to keep an open mind so I tried one. It was absolutely horrid though probably not worse than my Nokia E61 that I have now. One thing good about WM phones---they have best of breed 3rd party apps and lots of them. Too bad WM5 itself is so bad.

      You know what burns me about the current state of the art PDA phones besides that they all suck is that none are supported by OS X. I would include the Treo 650/700, Nokia E61, Moto Q, SE P990, the Blackberry's, and any WM phone. Not one of those works without additional software. :-( Of course, Windows is no different, but macs *try* to get that right and fail. I'd like a seemless transfer of contacts from one phone to another but that has never worked for me.

    14. Re:Bluetooth works fine on a Mac... by Moofie · · Score: 1

      "yet mac people like to make a point of "it just works"."

      Uh, OK. Like I said, sometimes the drivers are bundled, sometimes they're not. Where do you find drivers for syncing say, a Sony Ericsson phone with Windows?

      "I'd like to see more stuff work out of the box."

      Well, sure. But you're not seriously trying to say that OS X's syncing system is the same as Windows', are you? Because that'd be pretty silly.

      "phones besides that they all suck is that none are supported by OS X"

      Huh. My perspective is different. I have one address book that's shared by my PDA and my Mac, which runs my IM client, my mail client, even syncs a spare copy to my iPod. I can make a change on the PDA or the computer, and it propagates fine. It just works.

      Hey, there's that phrase again.

      --
      Why yes, I AM a rocket scientist!
    15. Re:Bluetooth works fine on a Mac... by dfghjk · · Score: 1

      "Uh, OK. Like I said, sometimes the drivers are bundled, sometimes they're not. Where do you find drivers for syncing say, a Sony Ericsson phone with Windows?"

      If what you're saying is that OS X is better than Windows for cell phone because a small number of phones are supported out of the box, that's pretty weak argument. Neither system meets the needs of the typical user without 3rd party software. With 3rd party software they are essentially the same except that Windows supports more phones overall than OS X does. Where do you find drivers for syncing, say, a Moto Q with OS X?

      "Well, sure. But you're not seriously trying to say that OS X's syncing system is the same as Windows', are you? Because that'd be pretty silly."

      No, I'm saying that mac's "it just works" claim is a fallacy when it comes to cell phones. My comparisons to Windows (which I didn't originally make) have always been that it is no different in reality, not that they are the same. You are the one that brought up a specific phone that is explicitly NOT supported by OS X as an example of how it works with "zero drama". You didn't offer up that fact that you purchased additional drivers to make it so until asked, then you claimed that it worked anyway in direct contradiction to Apple's statement and my direct experience. You've also admitted to being unfamiliar with the complications of the Treo 650's address book changes compared to previous Treo products.

      "I have one address book that's shared by my PDA and my Mac, which runs my IM client, my mail client, even syncs a spare copy to my iPod. I can make a change on the PDA or the computer, and it propagates fine. It just works."

      Yes, after you installed 3rd party software to make that happen. When I owned your phone, I accomplished the same thing (except for the odd iPod sync which is uninteresting to me) using Windows and I didn't have to buy any additional software. Running an IM client and mail client are unrelated as they are nothing more than Palm apps. Nevertheless, your Treo 650 didn't "just work" until you added software by someone other than Apple.

      http://www.apple.com/macosx/features/isync/devices .html

      Apple themselves say that the Treo 650 requires the purchase of mark/space software in order to be supported my Tiger. Don't know why you insist otherwise.

    16. Re:Bluetooth works fine on a Mac... by Moofie · · Score: 1

      "If what you're saying is that OS X is better than Windows for cell phone because a small number of phones are supported out of the box,"

      Mmmmmkay. I don't recall ever saying that, but whatever floats your boat.

      "Apple themselves say that the Treo 650 requires the purchase of mark/space software in order to be supported my Tiger"

      Mmmmmkay. Worked fine for me, before installing MarkSpace. It works BETTER with MarkSpace, which is why I bought it, but it works adequately...right out of the box. Or you could install Palm Desktop, and sync with that.

      --
      Why yes, I AM a rocket scientist!
    17. Re:Bluetooth works fine on a Mac... by dfghjk · · Score: 1

      "Mmmmmkay. I don't recall ever saying that, but whatever floats your boat."

      And I wasn't saying OS X and Windows were the same, either, but whatever floats your boat.
      I'm glad you're not saying that. Just what, then, makes OS X superior to Windows for cell phones then?

      "Worked fine for me, before installing MarkSpace."

      OK. It didn't work fine for me nor does it for Apple. That's why Apple says it doesn't work and I know precisely why. Palm changed the interface to their syncing to support certain enhancements that they made since the Treo 600. One of those was the address book category field. I brought that up for a reason. Apparently you don't mind losing data when you sync. Either that or you don't really pay attention when things "just work".

      "Or you could install Palm Desktop, and sync with that."

      Yep, just like with Windows. There really is no difference in this case. Have you tried using the 650 with Windows? Works just like in OS X except for the MDI interface. I've used both platforms and two things are clear. First, you have to install extra software in either case, and second, you really want to sync with the Palm app. It seems clear that you don't do that.

      Perhaps you haven't had to deal with the hourly or minute-by-minute resets with the 650 yet. Until you do, you can't appreciate the need to wipe the 650 clean and reinstall the software every few weeks. iSync doesn't help you with that. The 650 isn't a device worth owning in any case, so how it works with OS X vs. Windows is really moot. The thing is that any phone in the Treo 650 class has the same issues. None will work with iSync without additional software. That was my original point (this is a bluetooth discussion after all, not an iSync one).

    18. Re:Bluetooth works fine on a Mac... by Moofie · · Score: 1

      "Just what, then, makes OS X superior to Windows for cell phones then?"

      OK, that wasn't my initial contention, but whatever. I just don't happen to think that the problems of syncing phones is a Bluetooth specific issue. The interconnection works, the software support just isn't there. In my personal experience, the software support is better on OSX than on Windows, but you seem to have a different opinion, which is great.

      "Perhaps you haven't had to deal with the hourly or minute-by-minute resets with the 650 yet"

      No, I haven't. I've had my Treo for a year. My fiancee has had one for three months. I have a few applications that can be relied upon to reset the Treo, but I've not had an issue of just letting the thing boot back up, and I'm right where I started. Non-volatile storage is cool.

      Your mileage may vary.

      Yes, you need smartphone-specific software to do all the stuff that smartphones can do. Why is the Bluetooth spec supposed to be responsible for handling all those details? Does your Ethernet card configure your POP email box?

      --
      Why yes, I AM a rocket scientist!
    19. Re:Bluetooth works fine on a Mac... by dfghjk · · Score: 1

      "...I just don't happen to think that the problems of syncing phones is a Bluetooth specific issue."

      I'm not an expert on BT but I think it's complicated. BT defines device profiles which are very specific things. If the profiles are sufficient and are supported properly on both sides, then it works. Because of that, I think it may be a BT-specific issue but I don't know.

      "In my personal experience, the software support is better on OSX than on Windows,..."

      Actually, I think I do agree with you regarding BT but I'm not an expert. It's clear that Apple is trying there but just not succeeding with a lot of cell phones. Why that is idk but I think it's likely NOT Apple's fault. What I do think is that the limited device support makes the platforms more alike than different, that's all. I believe that OS X tries to be a superior platform in this regard with limited success.

      "Your mileage may vary."

      Yes, it does! I owned 3 Treo 650's and have had 3 friends who've owned them with universally bad results. Haven't used one in about a year because i gave up on the instability. Perhaps they've finally gotten it right. The builtin mail app is a real killer as far as triggering memory problems. I'm glad it works for you, because the 650 really is the best device of its type otherwise. I'd never buy another because I won't trust Palm again.

      "Yes, you need smartphone-specific software to do all the stuff that smartphones can do."

      My point was that a number of things that you quoted "just working" have nothing to do with OS X at all. Specifically email and IM. Perhaps you sync email with OS X (you can with Windows too) but I use IMAP and avoid the issue. IM doesn't sync. You don't have to sell me on a cell phone/PDA with a QWERTY keyboard. I love them! I just wish I could find one that works well. Obviously, none of that has anything to do with bluetooth :-)

    20. Re:Bluetooth works fine on a Mac... by kevinadi · · Score: 1

      Well you can't really say "switch to a mac" to millions of windows users if they want to use bluetooth, no? It's obvious that it's not mac is better than windows, but it's bluetooth that sucks.

      I think in any wireless technology (802.11, bluetooth) we see a fine example of corporate greed, backstabbing & "screw the customer" mentality in its purest form.

  18. The problem with Bluetooth.. by pablo_max · · Score: 4, Insightful

    The main problems with Bluetooth in my mind are complexity and cost. Qualifying a Bluetooth chip is a major pain in the butt. You need to qualify the radio part, the stack and profiles separately depending on what kind of product you have. And speaking of profiles, there are something like 30 Bluetooth profiles. Most of which overlap! So often time when you are implementing one profile you also cover all the mandatory features of another so you have to claim that one as well since you are seen as using that profiles IP! It's crazy.
    Then there is the cost. 10k to list your product. If you want to add something to it after you listed it...10k please. Not to mention the testing. 30k please.
    Bluetooth was going to be less then 2 bucks per radio. It's still almost double that. The Bluetooth SIG is way out of control.
    IMO Nokia is smart to jump ship. However, they cant go it alone. If they were able to get Motorola on board and perhaps Samsung, I can see no reason why a lower cost alternative would not work. Assuming that data rates are there.

    1. Re:The problem with Bluetooth.. by Snotnose · · Score: 1
      The main problems with Bluetooth in my mind are complexity and cost.


      In a cell phone, the main problem with BT is battery life. Simplified, a cellphone spends most of it's life in deep sleep mode, with all radios turned off. Every 1.28 second (google Slot Cycle Index) the phone wakes up and looks for a page. If it doesn't get one it goes back to sleep. The entire process takes 10-20 ms. When the radios are on the phone draws about 80 ma from the battery, when sleeping 1-5 ma (depending on the phone).

      Bluetooth wants to look for a page much more often. Worse, the interval when BT wants to wake up, and when the phone wants to wake up, don't have much in common. The upshot is with BT it's a lot harder for phone makers to maintain their standby time.

      Without reading TFA, I'm guessing Nokia's new standard syncs the 2 wakeup times.

      Caveat. I know CDMA. I don't know GSM. I've worked on minimizing current draw during deep sleep on a handful of phones. My only experience with BT was figuring out how to disable it while I did my job on the CDMA side of things.
    2. Re:The problem with Bluetooth.. by pablo_max · · Score: 1

      Actually. as long as the two BT's are bonded they can enter a sleep mode which pumps up the battery time...It's not BT in general thats bad for batteries, it's mis-implimentation of the spec.(much like my spelling)

    3. Re:The problem with Bluetooth.. by Eustace+Tilley · · Score: 1

      Does that mean "visible to all" prevents deep sleep?

  19. Bluetooth 2? by Midnight+Thunder · · Score: 2, Interesting

    Maybe they would have more luck trying to integrate this into the Bluetooth standard and proposing this as Bluetooth 2, ensuring that it stays compatible. While I understand Nokia trying to provide a new and improved technology, it needs to be done in a way not to confuse the already semi-confused buying public. By making it work with Bluetooth, in the same way as USB 1 and USB 2 or the B, G and A versions of the 802.11 standard.

    --
    Jumpstart the tartan drive.
    1. Re:Bluetooth 2? by tao · · Score: 1

      Because making it backwards compatible with Bluetooth would have nullified the major gains of the new technology; lower cost, and lower power consumption...

    2. Re:Bluetooth 2? by maxume · · Score: 1

      B+g are compatible with each other, but not A. They often get packaged together, even on the same card, but you can't mix a+b or a+g on the same network the way you can with b+g.

      --
      Nerd rage is the funniest rage.
    3. Re:Bluetooth 2? by jonathanhowell · · Score: 1

      If this new "Bluetooth killer" takes off, Nokia would be able to collect royalties on the products licensed, rather than just paying into the Bluetooth consortium like everyone else.

      If they named it Bluetooth 3.0 or whatever, they'd still have to license it through the consortium.

      - Jonathan

    4. Re:Bluetooth 2? by kevinadi · · Score: 1

      No. Bluetooth needs to die a quick death. They're not kidding when they named it "Bluetooth special interest group", which is all they did, serve their own special interest. The amount of money that you have to spend to license bluetooth is enormous. This is why you see a bluetooth mouse cost 3x a regular wireless mouse, it's due to the licensing cost.

      Half of the people in here don't know bluetooth 2.0 has been out since 2004. Talk about confusion. If half of slashdot don't even know about it, forget about the public. Also I have to say that bluetooth as a standard is quite brain dead by itself. It's painfully slow to do anything, the concept of visibility is half-baked at best (most likely an afterthought), pairing is a stupid concept (password for connecting? WTF? it's SHORT RANGE so the device would likely be next to me), security is almost non-existant, too many profiles that needs to be hard-coded into the hardware, eats battery like no tomorrow, I can go on and on. I can pretty much tell that the standard was created by greedy companies that have no clue how people will use it.

      Bluetooth is in really bad shape. It's expensive, hard to use, eats batteries and incompatible. Which is the exact opposite of what bluetooth supposed to be. This is due to their own greed, so let it die.

    5. Re:Bluetooth 2? by Midnight+Thunder · · Score: 1

      Bluetooth is in really bad shape. It's expensive, hard to use, eats batteries and incompatible. Which is the exact opposite of what bluetooth supposed to be. This is due to their own greed, so let it die.

      Immediate solutions include reducing license costs and better marketing. Does Wibree solve any of the issues or is it just another nice sounding technology with the same limitations?

      BTW not sure what you meant by hard to use or incompatible. If you are talking about the Windows implementation then it sucks 100%. If you are talking about the Mac then its incredibly easy. This is not based on some bias, but on personal experience of mine and other people I know. One example was trying to get the Motorola RAZR to sync with Windows XP, where we were pulling out our hair trying to work out what voodoo we needed to perform. The guy's girl-friend had a Mac and it worked straight-away with the phone. This suggests one of two things: Apple somehow made Bluetooth easy to use or Microsoft just has a shoddy implementation.

      --
      Jumpstart the tartan drive.
  20. Re:I've got Bluetooth on my phone, and never use i by uradu · · Score: 1

    My SE T610 runs for 2-3 days in standby with BT on plus several short calls a day. But since I charge it nightly anyway, that's a non-issue. Phones that can't even standby a single day with BT on have a serious issue.

  21. They should've called it Bluetooth 2.0 by davidwr · · Score: 1

    That way everyone would want to upgrade.

    --
    Knowledge is how to play a game, intelligence is how to win, wisdom is knowing what game to play.
    1. Re:They should've called it Bluetooth 2.0 by pablo_max · · Score: 1

      Except they have bluetooth 2.0 (http://en.wikipedia.org/wiki/Bluetooth_2.0#Blueto oth_2.0) It's basically the same unless you have the EDR part in which case it uses two new modualations.

  22. Re:I've got Bluetooth on my phone, and never use i by traveller604 · · Score: 0

    I sync my Nokia with my computer over bluetooth, can't be bothered to use that USB cable all the time, actually only if I want to transfer really big files like movies..

  23. Re:I've got Bluetooth on my phone, and never use i by danpsmith · · Score: 1
    When I bought the phone, I also bought a Bluetooth headset. I gave up on the Bluetooth pretty quickly: The headset would only run for about five hours before needing to be recharged, and the phone's standby time was cut down massively.

    Not to mention you look like some kind of massive dork from a sci-fi movie and are usually perceived by the general public as talking to yourself.

    --
    Judges and senates have been bought for gold; Esteem and love were never to be sold.
  24. my $0.02 of opinion by Goeland86 · · Score: 3, Insightful

    Having seen a few presentations about network standards, and especially wireless network standards, I think that Nokia is just trying to enhance the existing technology. Granted, there may not be a strong commercial gain to it, but the fact remains that bluetooth has been a more or less static protocol since its inception. Wifi on the other hand went through several revisions: 802.11a, b/g, now the upcoming n... There's a lot of development put into wifi. I attended a conference from Intel researchers saying they were working on enhancing the 802.11 protocol to work in a de-centralized manner, so I'm looking at this, and I'm thinking: well Wibre might just push Bluetooth further than it is. Using the same hardware base is also good, because it'll bring down manufacturing costs. I'm willing to bet we'll see the Bluetooth consortium jump on the bandwagon and help nokia widespread Wibre under a label like "Bluetooth 2.0" or something similar. Hardware and software updates all the time, why wouldn't protocols?

    --
    ---- I am certain of only one thing : I know nothing else.
  25. Re:I've got Bluetooth on my phone, and never use i by PHAEDRU5 · · Score: 1

    I must confess that I am a little taken aback by the sight of people who seem to be having conversations with themselves.

    Nonetheless, I wanted to try it so I could have recordings of "Champs Elysees" (s French current affairs CD I get every month) play with the ability to interrupt on an incoming call. I thought Bluetooth is expensive in standby, then I tried using it to play MP3s. That was a power hog, let me tell you.

    --
    668: Neighbour of the Beast
  26. Wibreee vs UWB? by braindead_in · · Score: 2, Insightful

    With Wireless USB http://en.wikipedia.org/wiki/Wireless_USB based on MB-OFDM on the way and backed by big names like Intel, I dont think it stands a chance. The days of proprietary technologies are over. Nobody wants to pay licensing fees anymore.

  27. I think that radio != chipset. by Kadin2048 · · Score: 1

    I'm not totally sure here, but it's my understanding that the "chipset" may (depending on context) not include the radio.

    So saying that it uses the same radio as Bluetooth may not mean that it's just a drop-in software change; the chipset which actually decodes what the radio recieves and does useful things with it, may be totally different.

    I assume that the radios are basically off-the-shelf items; I'm sure you can go to any number of manufacturers and get them (Motorola, Analog Devices, National, etc.); the chipset is probably where most of the design work, and the intellectual property / patents, goes.

    If we think of a wireless device as a chain, going (antenna) -> (radio) -> (decoding chipset) -> (computer), they are using the same antenna and radio, which are basically generic, and inserting their proprietary gear instead of the BT parts behind it.

    --
    "Ladies and gentlemen, my killbot features Lotus Notes and a machine gun. It is the finest available."
  28. Maybe brand-specific? by Kadin2048 · · Score: 1

    Not sure what you've been using, but I've used a variety of Motorola phones and they all seem to "just work" fine. Address Book sync, Object transfer for photos and video ... getting it working as a data modem was a bit of a pain but 95% of that was T-Mobile's fault; the phone talked to the Mac from the first moment onwards without problems. The computer doesn't give me crap about using some crummy generic USB BT dongle, either. (Unlike Windows where I'd need to install vendor-supplied drivers.)

    Then again, the phone has also worked pretty well with my IBM laptop and its BT implementation, so maybe more credit is due to Motorola than Apple.

    In either case, the whole system worked well enough to convince me that my next computer will be a Mac, and my next phone will be a Motorola.

    --
    "Ladies and gentlemen, my killbot features Lotus Notes and a machine gun. It is the finest available."
    1. Re:Maybe brand-specific? by dfghjk · · Score: 1

      Yep, Moto's have worked for me.

      "The computer doesn't give me crap about using some crummy generic USB BT dongle, either. (Unlike Windows where I'd need to install vendor-supplied drivers.)"

      I assume that's because you're using Apple's builtin BT? Fair comparison. Windows notebooks come with BT built in frequently as well. You don't get the problem you describe with those either.

      "Then again, the phone has also worked pretty well with my IBM laptop and its BT implementation, so maybe more credit is due to Motorola than Apple."

      I think it's more a matter of all three adhering to standards.

    2. Re:Maybe brand-specific? by Andy+Dodd · · Score: 1

      As I mentioned in my post, you DO get lots of problems with built-in Bluetooth depending on which stack the laptop vendor chose. It's all in the stack, and not the hardware for the most part.

      To my knowledge, both Apple and Dell use Cambridge Silicon Radio (CSR) chipsets. There is basically no difference between the two in terms of the BT hardware, and a large portion of the USB BT dongles out there (which use the exact same CSR hardware). In fact, in the case of Dell's Bluetooth modules (at least the 350, there's a 355 out now which might use different silicon), they are just an internal USB dongle with a different form factor.

      All CSR hardware I've used works great with BlueZ under Linux. While the front ends and user interfaces still need lots of work and support for AD2P and the Headset and Handsfree profiles are still under heavy development, BlueZ works great with CSR chipsets. (Not so well with Broadcom chipsets, but is that any surprise when talking about Broadcom?)

      Under Windows, the main problem seems to be multiple different BT stacks all of which stink for one reason or another. This is one case where I actually hope MS drives the "competition" out of the market by integrating a highly functional Bluetooth stack into Vista - While the default stack in XP SP2 is incredibly limited in terms of which profiles it supports, there is one good thing to say about it - it works with any hardware. In terms of quality, it blows away the other stacks for the profiles it does support. Unfortunately it just doesn't support some common profiles such as Headset, Handsfree, and AD2P. Other vendor stacks (WIDCOMM/Broadcom, BlueSoleil, Toshiba) do, but they are all of low quality and all of them are locked to the dongle they came with. (Guess what - in typical Broadcom fashion, they started the trend with the WIDCOMM stacks after they bought out WIDCOMM. Broadcom doesn't even allow the user to download upgrades to their stack!). In this case, the third-party vendors deserve to be pushed out of the market because their greed is making users' lives miserable with all of the compatibility problems.

      There's also the huge variation in terms of actual functionality of devices that claim to support a particular profile. For example, some Handsfree 1.1-compliant headsets play much better with PCs and Treos than others do. Motorola headsets claim compliance, but don't seem to exhibit compliant behavior with anything other than Motorola phones for example. They behave badly with WIDCOMM, they behave badly with BlueSoleil, they behave badly with Treos, they even misbehave with BlueZ + bluetooth-alsa.

      --
      retrorocket.o not found, launch anyway?
  29. It says.. by NekoXP · · Score: 3, Insightful

    That Bluetooth isn't cheap or power efficient enough for certain devices.

    That's about all :)

    Not that Bluetooth isn't good and that Nokia don't like promoting it or using it, but Bluetooth is not a panacea - just a standard.

    1. Re:It says.. by mspohr · · Score: 2, Interesting
      There is already a standard to take care of these issues (IEEE_802.15 and ZigBee) http://en.wikipedia.org/wiki/IEEE_802.15

      We don't need another proprietary standard... it looks like Nokia is just trying to have some standard that they can own so we'll buy more of their stuff... time to run away from this.

      --
      I don't read your sig. Why are you reading mine?
    2. Re:It says.. by NekoXP · · Score: 1


      Firstly, there can't be one standard which fits all devices. It's impossible to define without creating a bunch of semi-compatible subsets which need bridging devices.. which would defeat the object of a standard for all.

      Secondly, Wibree is also Bluetooth compatible, but lower data rate, and lower range than the higher end protocols.

      Thirdly, ZigBee is for *extremely* low data rates and focussed on home automation.

    3. Re:It says.. by mspohr · · Score: 1
      The ZigBee is designed for very low power consumption and data rates up to 250 kbits/sec which is plenty for voice and even low res video.

      TFA states that Wibree requires "dual mode" chips to be compatible with Bluetooth... sounds like two different protocols on one chip. ZibBee also can use the 2.4 Gig band so I guess it is as "compatible" with Bluetooth as Wibree.

      It still looks to me that Nokia is trying to design a new proprietary standard and force it on the market so they can make big bucks from licensing.

      --
      I don't read your sig. Why are you reading mine?
    4. Re:It says.. by Anonymous Coward · · Score: 0

      Zigbee and Bluetooth use different modulation techniques, QPSK and GFSK, and is not compatible at the physical layer. Low power consumption is a relative term, both Bluetooth and Zigbee say they are designed for low power consumption. If you look at certain applications like mouse, keyboards, heart rate monitors and so on, you find that neither Bluetooth or Zigbee is fits that purpose. The strength of Zigbee is complex network structures. And one more thing... The standard is to be published, it is not proprietory,

    5. Re:It says.. by kevinadi · · Score: 1

      It still looks to me that Nokia is trying to design a new proprietary standard and force it on the market so they can make big bucks from licensing.

      Which is what Ericsson did with Bluetooth, way back then. They even went to the trouble of passing it through IEEE as 802.15.1

    6. Re:It says.. by NekoXP · · Score: 1

      What's wrong with making money?

      If Wibree is dual-mode then it's not bad, is it? Nobody is going to lose Bluetooth on Wibree devices, in fact they are going to gain battery life. Which is good!!

      ZigBee using the 2.4Ghz band does not mean it is "compatible". Wibree is compatible in that it HAS Bluetooth functionality, not that it is going to further clutter the 2.4GHz band with more devices..

    7. Re:It says.. by mspohr · · Score: 1
      My argument is that this is a completely redundant "standard" which is created for commercial purposes and which will cost consumers extra money (as they pay for devices that run the new standard).

      I'll all for innovation and I'm happy to see companies making money but there is no benefit to consumers here since the functionality can be addressed with the 802.15.1 through 5 devices. In this case Nokia will stuff the channel with this equipment and consumers will have to buy new peripherals, etc. I'd rather see Nokia spend their engineering time and marketing effort on something truly of benefit to consumers (which would also benefit Nokia).

      --
      I don't read your sig. Why are you reading mine?
  30. Maybe They Can Get Bluetooth to Work Now... by Anonymous Coward · · Score: 0

    Well, since the geniuses that came up with bluetooth used the exact same frequencies as 802.11g and they don't work together I'll be glad to welcome someone else into the market. I don't care what anyone says, it doesn't work. If I turn on bluetooth and wireless at the same time then every 5 seconds my bluetooth mouse stops working for a second or two. How clever.

  31. Ericsson is not "#1 seller of Bluetooth chipsets" by holgie · · Score: 0
    ... rival Ericsson, who is the #1 seller of Bluetooth chipsets?
    That is not correct - IRC. Ericsson chipsets have a reputation for lacking features and consuming too much power.
    Again IRC CSR (Cambridge Silicon Radio) and BroadCom are the leaders in this market, with regards to features and sales volume.
    --
    Chuck Norris can divide by zero.
  32. Confusing Users 2.0 by chord.wav · · Score: 1

    Another acronym to confuse users. Wich BTW still don't get that a BT device may not have the same services as another BT device. For example, a BT camera phone may let you use its camera as webcam while another one won't. But still both advertise as BT devices. Why do they/us let them do this??

  33. Re:I've got Bluetooth on my phone, and never use i by TheRaven64 · · Score: 1
    I've never used a Bluetooth headset, but I use Bluetooth regularly for a few things:
    • Syncing my address book with my computer.
    • Syncing my calendar with my computer so I can check appointments while mobile.
    • Connecting to the Internet from my laptop while I am mobile.
    • Transferring pictures from my 'phone to my computer.
    Activating Bluetooth doesn't have much of an effect on the standby time of my 'phone, although it was a bit worse on my last one.
    --
    I am TheRaven on Soylent News
  34. Now I'm really confused by Hillgiant · · Score: 1

    I thought this was for Nintendo's new cheese-based controller. The WiiBrie.

    --
    -
  35. Re:I've got Bluetooth on my phone, and never use i by flyingfsck · · Score: 1

    I'm a scizophrenic, hiding behind a bluetooth headset, you insensitive clod!

    --
    Excuse me, but please get off my Pennisetum Clandestinum, eh!
  36. I use bluetooth keyboard/mice on a mac by SuperKendall · · Score: 1

    I'm not sure why you were having problems, I use only bluetooth mice/keyboards with a Mac and have not had a problem for months - that includes turning them off and on with great regularity, so it's not like the connection is constant and easy to maintain.

    --
    "There is more worth loving than we have strength to love." - Brian Jay Stanley
  37. Some facts, some opinions by gjh · · Score: 1
    Body area networking can and will succeed
    1. Bluetooth is used a lot more outside the US. Most US operators cripple bluetooth on the phones they sell. Try buying direct.
    2. Despite this, it is already the preferred method for phone sync, phone management, wireless keyboards and some mice, headsets, sending business cards and photos mobile to mobile and for using your phone as a modem to your laptop.
    Bluetooth is not perfect for lots of low power cheap devices
    1. Every bluetooth device sold requires payment of a license fee to Ericsson.
    2. It is all point to point. PC implementations end up layered over com ports. IP ends up layered over PPP. Many devices end up only being able to talk to a single partner device at one time. Pairing is painful, and other trust models could usefully be used. 802.11 WLAN is much easier to code for. Any bluetooth successor should start with IP on a broadcast WLAN, rather than IP being an afterthought. Bluetooth suffers from lots of stupid non-IP protocols being developed from scratch that noone can agree on for things that would be trivial over IP like filesharing, management, messaging and so on.
    3. Per the article, battery usable could usefully be lower.
    4. Per the article - the bluetooth PC, Mac and Linux software experiences areare substandard in one way or another
    1. Re:Some facts, some opinions by danamln · · Score: 1

      If body area networking is to succeed wouldn't the goal be to develop mobile device to use one of these techs to search for other phones directly, taking the peer to peer network mobile (ie placing a call by bluetooth instead of cell network).

  38. Netcraft confirms it! by Anonymous Coward · · Score: 0

    Bluetooth is dying... ...as it has been for the past 4 years ...at least here on Slashdot ...only

  39. Same antenna and radio means ... by Tjp($)pjT · · Score: 1

    That it is software driving the radio most likely that makes the difference. That means a BT device can support Wibree in all likelyhood simultaneously. Just like the degradation of WiFi connection when a WiLAN has mixed 11 Mbps and 54 Mbps ... So keep the BT support for ahtw is there already and have a gentle migration through attrition.

    --
    - Tjp

    I am in wallow with my inner money grubbing capitalistic pig. ... Oink!

  40. Successors to Bluetooth by billstewart · · Score: 1
    I agree - unlike our neighbor the troll (trolls are of course Norse...) I don't see this as any silly Scandinavian rivalry; technology companies are always working on the next generation of technology, except when they're trying to kill it because it's interfering with what they currently sell, and even then they're usually still working on the next generation. Bluetooth had lots of things wrong with it - it was supposed to use very low power and cost very little, but never really performed on those goals; it's got a heavyweight security stack that doesn't seem to provide usable security, but does provide enough options that it's easy to make incompatible devices. Zigbee was a later system that was supposed to be lower power and lower cost, but I haven't seen evidence that it's done anything other than being slower. This standard is trying to be faster, while still cheap and presumably trying to be secure, at least if they've got somebody who understands security better than the people who did the previous standards.


    Harald Bluetooth the king is also dead - his grave's at the cathedral in Roskilde, near the music festival and the Viking ship museum, and you can get there with a Copenhagen city bus/train pass, so you don't need to burn Eurail/Scanrail pass trips.

    --

    Bill Stewart
    New Fast-Compression-only CPR http://preview.tinyurl.com/dy575ks
  41. Bluetooth 3? by Anonymous Coward · · Score: 0

    Why don't they just make it Blue Tooth 3 since it uses all the same hardware and save a bunch of confusion

  42. Doesn't compute by SuperKendall · · Score: 1

    Well you can't really say "switch to a mac" to millions of windows users if they want to use bluetooth, no?

    Why not? They could still run Windows.

    It's obvious that it's not mac is better than windows, but it's bluetooth that sucks.

    If the only place Bluetooth falters is in fact on Widnows, I think you can draw your own conclusions about the origins of the sucking.

    If 100 million people use the same brand of vaccuum cleaner, it doesn't mean that wouldn't suck either. In probabalistic terms were talking independant trials here.

    --
    "There is more worth loving than we have strength to love." - Brian Jay Stanley
  43. Re:Ericsson is not "#1 seller of Bluetooth chipset by ansible · · Score: 1

    Yup. Ericsson is hardly a player these days. CSR and Broadcom are the biggies.