After using the Lambda BL@ST (product of Lambda Mobile Apps), I submitted the problems I faced with the product to the customer service via email:

Old Review: http://zonelance.spaces.live.com/blog/cns!8AB1DFD374276C25!600.entry

Reviewing equipment -

1. Earphone: Westone 3 with dual-flange stem-cut canal tips
2. Source: Nokia N82
3. Reference: Nokia N82 3.5mm output
4. Monitoring Hardware: SigmaTel HD CoDec 3.5mm Line-in
5. Monitoring Software: Adobe Soundbooth CS4, Foobar

Problem #1 – Bluetooth Initiation Popping Sound

Every time the device gets from sleep mode to active bluetooth, it emits a noticeable discharge to the earphone. In fact, the magnitude is high enough to clip the monitoring equipment (out of scale, shown in ~0.10s to ~0.35s). If you have a sensitive earphone under 32 ohms, the noise can scare the living hell out of you, or it might damage sensitive listening equipment (imagine this get passed onto an amplifier).

There is also a bluetooth active-to-sleep discharge (shown in ~2.05s to ~2.10s), which is noticeable but with significantly less magnitude.

Problem #2 – Hissing Noise

Audible hissing noise is observed when connected to low impedance earphones. This affects overall audio quality.

Problem #3 – Uneven Frequency Distribution

 

(Left: White Noise Output from Lambda BL@ST; Right: White Noise Reference)

This is a rather serious issue that prevents this product from entering the “audiophile” category. Lower frequencies are significantly attenuated on the BL@ST. Having even frequency distribution output is fundamental in audio products.

Reply from Customer Service

So the next day (which is today) I got a reply from their office at Centrepoint. I’m surprised they actually identified the receipt number just from the information I submitted. Sadly, they called me and told me there is no solution for the problems I posted.

When asked if their company will look into this matter, I got a classic Bolehland response: “it is not a serious issue”, which translates to – “we don’t plan on fixing it, kthxbai”.

Conclusions

I take back some of my comments posted on my previous reviews (apparently because I don’t have access to more accurate earphones, now I do :D).

1. The Nokia N82 has an almost even frequency distribution output.
2. Turning on the ‘loudness’ option in Nokia N82 will deteriorate the audio quality instead of improving (my bad), unless you’re using lower quality earphones.
3. Both Sigmatel HD CoDec and Lambda BL@ST have unevenly distributed frequency output, which benefits lower quality earphones, but distorts sonic accuracy.
4. The Ultimate Ears triple.fi 10 Pro has unevenly distributed frequency output (colorful output), results in ‘boxy’ mids and shallow bass.

And, back to the Lambda BL@ST, using audiophile rating, by judging solely from one point of view:

1. The discharging noise is the major issue here since audiophile equipments is either headphone amplifier + high impedance headphones, or low-impedance earphones. Risk of damaging expensive listening equipment is relatively high.
2. The unevenly distributed frequency output is one major drawback that keeps audiophiles away from this product. (I rather use the stock wired Nokia handsfree kit.)
3. The hissing noise is another problem, it attenuates and distorts the audio output.

As well as normal consumers’ point of view (apart from stated in the previous review):

1. The volume controller’s “beep” sound always operates at maximum volume, regardless of the current volume, making previewing of current volume impossible.
2. The company’s unwillingness to improve the product is a huge disappointment.

So I conclude Lambda BL@ST in audiophile’s rating – 5/10

It has been 20 years since this all began. Every time I think about my past, mashed up feelings of embarrassment – for the mistakes I made, regret – for the wrong decisions I made, joy – of looking at how naive I previously was, and of course, nostalgia – for the carefree days and people who left.

Gifts from family members, who treat me as an adult; and buddies – who still recognize the kid in myself.

Here’s a short review on the Picoo Z Sidewinder (Mini R/C Helicopter):

First of all, the Picoo Z is an incredibly small and light self-balancing (full-cyclic-authority airfoil-type stabilizer bar), Guinness-record-holding, award-winning miniature remote controlled helicopter. The delicate electronics, lithium polymer (Li-Poly) battery, and powerful MCU controlled servos are housed inside lightweight Styrofoam (expanded polypropylene for you chemistry geeks).

The Picoo Z’s internal Li-Poly battery is recharged using the controller, with the controller requiring 6 AA batteries. One full charge requires approximately 20-30 minutes, providing around 5-10 minutes of air time. The 6 AA batteries must be quite fresh or else the charging will fail. (Note: It is not stated in the manual, but you’ll have to turn on the controller to charge the helicopter)

One thing great about the controller/charger is its automatic-shutdown system. If you leave the charger/controller unattended, it will switch itself off completely a few minutes after charging is complete, saving precious power.

Due to the nature of having 2 separately controlled servos for the main rotor blades and tail rotors instead of mechanically controlled tail rotors, the helicopter relies on the microcontroller to determine the optimum speed of the tail rotor to provide counter-torque, preventing the helicopter from spinning (due to the main rotors, Newton’s third law). The ST Trimming buttons on the controller is to increase/decrease the output of the tail rotors, in case the electronic mixing provided by the MCU is insufficient.

My first flight results in slight counter-clockwise spinning of the helicopter. So I followed what the manual said and apply ST Trimming. The result is quite disappointing, even though I applied maximum trimming, the helicopter still rotates slightly to the left, which I have to tilt the yaw-stick slightly to the right to compensate, and the helicopter is flying stably… Until…

“Someone” stepped in and asked me to lend him the toy. Despite a clear “please-handle-with-care” warning to him, the first thing he did was crank up the throttle (main rotors) to the max, resulting in the helicopter shooting straight up and crashing into the ceiling; then he released the throttle, letting the helicopter crash into the ground at full gravitational force; then he applied full throttle again, despite having the helicopter lying tilted on the ground, resulting in the rotors cutting into the marble floor.

Ouch, yes. The end result? The “spin-anti-clockwise” problem developed into “spin-anti-clockwise-wildly” problem, maximum output on the tail rotors still couldn’t stop the spinning.

Usually the presents given by people are cared, used and kept until it either blown into smitherins or until that person gives a replacement. For someone (including myself, if it’s my fault) to damage it, on the first day, is totally unforgivable.

Instead of punching him straight in the face (bad idea, seriously), I quickly snatched back my toy and shooed him out of my room. After spending on a few hours checking on the official websites and forums, trying to bend the tail and tail rotors, applying lubricant to the tiny bearings in the tail servo, and a few times of test flights – it finally worked. And I’m proud to say, it worked better than before.

Currently, the helicopter only requires slight ST Trimming to stop its spinning. WOOT! I can play with this shit all day long (minus the charging time), practicing the delicate process navigating in my room without crashing into things. Though I’m reluctant to admit: this toy has successfully transform a 20 year old to a 5 year old.

Good stuff guys, I’m pretty sure this thing is not cheap. ;)

Today I drove alone to Carrefour Ampang (with GPS), then drove alone to MYDIN KL (with GPS, took me near 45 minutes to find a parking lot), having my phone battery deplete to zero despite a night of full charge, couldn’t find my car at night (but found it with a stroke of luck), having to find my way home at night (without GPS) and nearly causing a few accidents (escaped unscathed).

*EXP +100000*

I’m glad to be alive.

p.s. here are your photos. :P

Working is a pain in the arse, in one way or another – either the pay is too low, or the actual job is significantly not as described, or you’re getting tight timings (or a combination of them). After 2 years of “monking”, I have an additional handful of stress to worry about. Thank you KBU.

Anyhow, the client’s client probably hired the worst marketing strategists on the planet, we ended up running around getting shooed away by authorities, or “cosplaying” a walking talking brick wall which nobody gives a shit about, or standing-by for extended periods of time waiting for the higher-ups to re-cogitate (which most often didn’t work).

To whom it may concern (you know who you are) – sorry, no photos for you, yet. Your request is of high difficulty, the “post-monking-syndrome” is still in effect, please give me some time to get over with it. Thanks.

 

p.s. My wallet broke, my sling-bag broke, my belt broke. Darn (?!)

Naïve, you’ve yet to see how twisted this world is. You’ve let him come too close, letting his pathetic tears compromise your emotions. And soon, you will sink too deep, too late, beyond regret. O’ naïve soul, I shall show you the real truth, I shall be the darkness, I shall bear all sins – all to protect you, even if it costs me my honor, my life, my soul – I shall become your dark knight.