Bluetooth Everywhere

So, as you already know, alot of the mobile and embedded developers will be at the M3DD conference this week in San Jose, CA. Well, it was announced on the Java Mobility podcast that there will be a special device give-away at the conference. Any guesses on who the provider is and what that device will be? So, let’s see how good my intuition is…

#1. I think that the provider of the give-away will be Sony Ericsson, and
#2. I think that the device will be the C905 phone with Capuchin technology

Stay tuned next week (or come to the conference) to see if I was right!  :-)

Ok don’t laugh, but I kinda did something stupid. I got excited about the new simple pairing feature in Bluetooth 2.1 +EDR, so I rushed out and got one of the first Bluetooth dongles that supported the new spec. I couldn’t wait to receive it. After I opened the package, I realized something. I just got the equivalent of (1) walkie-talkie. The main reason why I got the new dongle was to test out the new simple pairing feature, which would mean that I would (of course) need another Bluetooth device that supported the 2.1 spec.

So, I’ve been on a quest to find a really cool device that supports the 2.1 +EDR spec. So, have you guessed it yet? What’s going to be the first mobile device in 2009 to support Bluetooth 2.1? Is it…

• Apple iPhone? No.
• Blackberry Storm? No.
•  Nokia N97? No.
• Sony Ericsson C905? No.

Its the Palm Pre:

Now before I sing the praises of this device, can I remind us all of a little history? Over 13 years ago, the cellphone market was not the growth sector as it is today, and the mobile and handheld market was really all about PDAs. Toshiba and Sharp introduced one of the first official PDAs in the market, and then Apple stole the show with their PDA, the Apple Newton. All the PDAs on the market had similar capabilities (notetaking, appointment book, calculator, etc) but Apple’s claim-to-fame was the fact that it the best handwriting recognition available. The Netwton became an instant success and completely dominated the market. Unfortunately, Apple didn’t listen to the developer community who wanted better access to the APIs of the system. Apple also ignored the consumers who wanted a smaller form factor and nearly flawless character recognition. So what happened?

A newcomer arose out of nowhere in the PDA market named Palm (at that time it was US Robitics) and introduced a PDA that could comfortably fit in your pocket and could recognize characters 2x faster and more efficient than the big-bad-Newton. Palm also introduced a better synchronization technology that synchronized your desktop and PDA 10-20x faster than anybody else, including Apple. Developers flocked to the Palm platform because it was more open compared to the Newton APIs (even though Palm had the uphill battle of being the new-guy-with-the-new-API).  In a matter of years, Palm became the #1 PDA, and Apple could never catch up because they refused to change.

So what’s the point of all this mobile computing history? I said all this because I think we’re about to see it happen all over again. I like Apple’s products, but as a developer, it can be very frustrating to work with them, especially for the iPhone. The Bluetooth APIs are very restrictive (boo!) and why can’t we do any tethering, Bluetooth or otherwise?. Did you know that you have to own an Apple computer to write code for the iPhone? Consumers want tactile feedback in order to type quickly, but Apple will *never* make a keyboard for the iPhone because they’re too arrogant about their design. Is it too much to ask to get a user replaceable battery?

Now of course, every new smart phone on the market will have the standard touch screen, accelerometer sensor, large display, and GPS chip. The Palm Pre adds the following features, that set it apart from the other contenders:

• Bluetooth 2.1 +EDR (now I have a device to do simple-paring with!)
• Bluetooth tethering (very nice - I have no idea why Apple and RIM refuse to support it)
• A real keyboard (so people can type faster)
• A user replaceable battery
• Wireless power charging!

So, needless to say, I’m excited about this device. I’m anticipating information on the Bluetooth API support (of course).

Ok, so let me start from the beginning. I have an upcoming article this year on java.sun.com on how to use the Sun Java ME SDK 3.0. This SDK is a revolutionary tool since it allows you (the developer) to create all types of Java ME applications including MIDP, CDC, and Blu-ray applications.  One of the coolest features is the on-device debugging feature, which is awesome, but requires a device with Windows Mobile 6 OS.  So, I decided to get one of the best Windows Mobile 6 devices available, which is the HTC Touch Diamond:

This device is no iPhone. Have you noticed that the iPhone doesn’t have a manual? That’s because it’s very intuitive on how to use it. Well, the HTC Touch Diamond not very intuitive at all, and I used to hate it — that is, until today.  Today I found out that the Sprint Titan platform supports Windows Mobile 6, and the platform is free for certain devices, most notably HTC devices. So what exactly is the Sprint Titan platform?

• A single platform that combines CDLC and CDC JVMs
• Support for MIDP and LDCUI
• Support for OSGi and JSR-232 with eRCP
• Support for eSWT GUI application

Are you drooling yet? Below is an image of the Sprint Titan software stack:

Ok,

I’ve been to the JavaOne conference before, and I can say that it’s an awesome experience.  Now, of course, at JavaOne there’s so much going on, that’s easy to get lost in the myriad of speakers, topics, and exhibitors. So, since Sun is running the M3DD (Mobile, Media & Embedded Developer Days) conference, then I have my hopes up that it will be as fun and exciting as JavaOne.

Here’ a list of technologies that I want to get smarter on:

• Java FX mobile
• Tru2way
• MIDP 3 (of course!)
• BUG Platform
• Java ME and OSGi
• Java ME widgets
• Java Card 3
• Squawk
• Capuchin

So this should be an exciting conference next month. Hope to see you there!

Ok, so my wife got one of those Amazon Kindle eBook readers, and I have to admit that it’s pretty nice. I like the fact that you can search in the eBook, as well as look up items on Wikipedia and Dictionary.com with a simple button click. So, I started thinking, since I’m going to be writing the next edition of the best Bluetooth book on the planet, why not release mini-books on the Kindle platform?

This would allow you, the reader to get the new content in “Bluetooth for Java” 2nd ed. within a matter of weeks or months, as compared to waiting for the entire authoring, editing, proofreading, finalizing, printing, packaging, shipping, shelving process to get a book in your hands.

So regardless  if you’re a Kindle owner or not, let me know if you’re interested in mini-books on Bluetooth technology!

Now, here’s something to get excited about. Last week, the Bluetooth SIG made an announcement about the next generation of Bluetooth technology. It’s probably WON’T be named Bluetooth 2.2, and it probably WILL be named Bluetooth 3.0. So why are the details so sketchy at this point? My guess is that they’re going to wait to make the big announcement at the CES show in January 2009. But anyway, here’s what we know:

• Bluetooth 10x will be the name of the spec that will utilize WLAN (802.11) radio technology
• Bluetooth 100x will be the name of the spec that will utilize UWB (Ultra Wide Band) radio technology

Since the radio technology for WLAN is widely available and ubiquitous, it makes sense that the 10x spec (and devices that implement the spec) will come out first. UWB is a tougher nut to crack, and I won’t expect to see any devices that use that technology until 2010 or 2011.

Of course, we have to wait until CES to see if any device manufacturers have done anything promising with UWB or Wireless USB.

Ok,

Here’s your chance to directly influence one of the chapters for “Bluetooth for Java” 2nd edition. Is wireless printing a topic that should be addressed in the new book? If so, then leave a comment describing why you think it needs to be included.

Any comment is fine. You can even say, “Bruce, I work for HP, and my job depends on folks printing more stuff, so please include a chapter on printing”.

:-)

Ok,

So let’s test your Bluetooth knowledge here. First of all, if you don’t know what a Bluetooth Profile is, then you need to go buy a book on Bluetooth (any book will do - but mine is the best). Ok, how many Bluetooth Profiles are there?

Five? Ten? Twenty? Do you give up?

The answer is: 25. Below is the current list of Profiles defined by the Bluetooth SIG:

1. Advanced Audio Distribution Profile 1.2
2. Audio/Video Remote Control Profile 1.4
3. Basic Imaging Profile (BIP)
4. Basic Printing Profile (BPP) 1.2
5. Cordless Telephony Profile (CTP)
6. Device Identification Profile (DI) 1.3
7. Dial-Up Networking Profile (DUN)
8. Fax Profile (FAX)
9. File Transfer Profile (FTP)
10. Generic Audio/Video Distribution Profile 1.2
11. Generic Object Exchange Profile (GOEP)
12. Hands-Free Profile 1.5 (HFP 1.5)
13. Hardcopy Cable Replacement Profile (HCRP) 1.2
14. Headset Profile (HSP)
15. Health Device Profile (HDP)
16. Human Interface Device Profile (HID)
17. Intercom Profile (ICP)
18. Object Push Profile (OPP)
19. Personal Area Networking Profile (PAN)
20. Phone Book Access Profile (PBAP)
21. Serial Port Profile (SPP)
22. Service Discovery Application Profile
23. SIM Access Profile (SAP)
24. Synchronization Profile (SYNC)
25. Video Distribution Profile (VDP)

Over the coming weeks, I’m going to introduce you to each Profile and give you a short description why you should care about it.

See ya later!

Ok, so I finally took the time to start a blog. So why start now in 2008  since my book, “Bluetooth for Java” has been out for 5 years now?

Hmm…

good question…

Well,  maybe because I’m starting to write the 2nd edition to the book. So, I plan to use this blog to talk about everything wireless, but especially stuff that will be in the next edition of the book. So, thanks for stopping by, and of course, stay tuned!