Archive for October, 2011

Here is a quick review and summary of use of the Cardo S-800 Bluetooth Headset.

Image of Cardo S-800 Bluetooth Earpiece

Cardo S-800 Bluetooth Earpiece

I bought this on January 1, 2009 for about $15 with shipping form So I wasn’t sure what to expect.

I had a Blackberry Pearl and it paired and worked wonderfully. It has 3 extra programmable buttons and saves up to 3 last numbers. I was actually very pleased with it. It was lightweight, fit well, good sound both ways, loved the options. Coupled with RIM’s Pearl’s voice dial interface, it was awesome.

Then when I switched to a G1 Google phone, I was immediately less pleased. It became pretty useless. The G1 also had a very hard time pairing with my car’s Magellan GPS and the quality was equivalent to trying to talk to someone in a pool where you are both underwater. Pretty useless. Donut 1.6 did NOT help. I quickly became accustomed to pretending BlueTooth did not exist because as far as I could use it, it did not…. BOO ON GOOGLE! (The voice dialer on the Google phones is still pretty crappy, not hands free at all! Yet another issue)

So, other than that, great little piece of hardware. However by the time I got an excellent HTC G2 phone (preceded by a MyTouch Slide 3G, not a bad phone, not incredible, also had hard time with Bluetooth/voice dialer / genius button), the Cardo S-800 battery life had died and it would not charge after being in my electronics cabinet for the better part of a year or so.

Cardo no longer makes these little guys. They seem to specialize in cycling Bluetooth gear now.

No replacement parts, out of warranty, yada yada yada. I tried taking it apart to see if I could possibly replace the battery. It was hard-wire soldered to several wires and components… hum.. Guess not.

I guess for $15 I got my couple of months of use with the Blackberry out of it and that was it.

Trash binned.

So I recently bought a Motorola HK-100 for about $14.00… A simpler device than the Cardo S-800. I’ll let you know how that works out.


Yesterday evening after getting home from work, after what seems like three months, because it has been three months of working long days of overtime and weekends on most occasions, I decided to take a quick nap in our ‘Beach Room’ before doing some more work for another client. I lay down on the day bed and remember trying to wake up several times and remember vividly fighting with the sleep of arrays within arrays within arrays. And I had to map the nested arrays to another set of arrays before I could get up. I guess I finally did it by 7am or so as that is when I was able to push through the foggy cloud of arrays and structures in my head and get up. This happens occasionally. When I am working a lot on a problem or a project, it bleeds into my dreams as code. In this case, we have been working on some XML xPath parsing and mappings and it has been a ‘critical’ issue. Happy to report that the real life issue was resolved Tuesday morning by about 5:30am. The issue? A certain size of record processing was taking between 45m to 1.5hrs to process, if and when it finished at all. Most of the time it would fail and kill the server. After effectively rewriting it, the same XML record set now takes 41 seconds to process. Amazing what proper design and proper use of functions will do for you… And the server concurrency issue is negligible (you can put a load on the server while the record set processes and it runs fine).