Author: Roo

Review: Nexus One

Recently one of the guys at work offered me his “old” Nexus One for a crazy price, so crazy I actually talked him into accepting more. I immediately wiped the ROM that was on there and installed cyanogenmod – for this review I’ll stick to my impressions based on using the Nexus One for the first couple of weeks.

First impression: Fast. So very fast. Second impression – argh, no physical keyboard – no buttons either! Then the fact that the Nexus has so much more RAM available than the G1 did starts to sink in, and the speed – did I mention it was fast? I was sold, but really hoped that the keyboard / button thing was going to quickly become a non-issue.

The headline photo is a comparison shot of the Nexus (far left), and iPhone 3G (middle) and the G1 (right). Things get interesting when we look at the side profile.

The Nexus is the thinnest of the bunch. Let’s take a look at some of the specifications

Nexus One HTC G1
CPU 1 GHz Snapdragon 528 MHz ARM11
RAM 512MB 192MB
Screen Size 3.7″ 3.2″
Resolution 480×800 320×480
Weight 130g / 4.6oz 158g / 5.6oz

Some big differences, with twice the CPU frequency and more than twice the RAM – even needing to drive the larger resolution screen isn’t going to be enough to slow it down.

After a few days I got used to the ‘soft’ buttons for home, menu, back and search. The ROM has haptic feedback (it vibrates) when you hit these buttons. Initially the back button gave me some trouble, specifically in twitter where the reply button on screen is just above the back button – I kept hitting reply instead of back. As I got more familiar with the phone this was much less of an issue.  I still manage to hit the home button when using the track ball for some reason.

Having a real headphone jack is very nice, something I really found annoying with the G1. Having the dock to charge means no messing with cables, you just drop it in. The predictive keyboard is actually quite good, and once you get used to using it – the on screen keyboard is just fine. I still sometimes miss the physical keys, but everything else on this phone is so nice I’m willing to live without them.

Review: ADATA microsd 8Gb class 6

Last march when I got a G1 it came with a 1Gb microsd card. That’s enough for some apps and the usual kind of data you might want to carry around, but is isn’t enough if you want music and video (enough to keep you entertained on a cross continent airplane ride). At the time 16Gb cards seemed too expensive, but 8Gb was a nice sweet spot – for under $30 I could get a class 6 card from ADATA (the price has dropped in half since then).

This card worked reliably for me until things went wrong in early January of this year. Luckily I have a couple of 1Gb cards around that I could swap in as substitutes.  A couple of days later after drooling over 16Gb cards which are now reasonably cheap (if you drop to class 4) I realized that ADATA offers a lifetime warranty. There didn’t seem to be any sensible manner to claim this warranty, but I filled in the web based form to get some technical support. A few days went by, but then I got an email back.

The email was quite helpful. It was somewhat a form letter, but pointed me at the SD Formatter tool which in theory knows how to properly format an SD card. I had already tried multiple readers / machines to validate it was really a problem, but I gave the official tool a shot anyways. The same email contained a form document file that I needed to complete and send in to get an RMA #.

It took me a couple of days to get around to filling in the form, but the response with an RMA # was fairly prompt.  I sent off the card (cost me $2.88 postage – but it was well padded) and figured I’d see what happened. Well, today a rather large box (pictured at top of post) arrived. In it was a new card and two ADATA lanyards. Sweet, and I thought I had excessively packaged the card on return.

ADATA is one of the lower cost brands, yet from what I’ve read in various forums those with ADATA cards haven’t had more problems than any other brand. When the card failed, I was planning to just abandon an avoid ADATA in the future – the quality of the customer service (and the warranty) has me sold on ADATA being a good brand to buy. I will without hesitation buy ADATA again, and I’ll recommend it to others.

[Update: June 7, 2011 – I’m no longer using this ADATA card. The replacement started to exhibit strange behaviour in my phone – I replaced it with a 16Gb class 4 Patriot card. Not sure at this point if I’d recommend the ADATA brand]

The Energy Detective

It has been some time since I got a TED 5000 unit (Nov 2009) – being able to visualize the whole house energy usage is pretty neat, and a nice motivator to see what you can do to save energy.  A while back it seems my TED had gotten stuck and was no longer reporting any usage.

Now this type of problem has happened before, so I wasn’t too surprised. I don’t check it regularly (my attention to it tends to be bursty) so it seems like every second time I go to poke at it, something is amiss and there is inevitably another firmware update available too.

The current versions are:

  • Gateway v1.0.383
  • Footprints v1.0.210

The upgrade instructions are clear and easy to follow. However, unlike previous problems a firmware update/reboot/power-cycle has not magically fixed the problem. Guess it’s time to poke around inside my electrical panel [warning – this can be fatal if you don’t know what you’re doing] and see if something is wrong.

There is a fairly good troubleshooting guide available, in my case it seems working through step 4 was was I needed to do. Finding out what was wrong was pretty easy, the red MTU wire was lose in the panel (Rant: why I don’t like having random people doing work in my house! This mistake was related to some renovations we had done).  Once I knew what was wrong with the hardware setup, it was easy to fix.

Then I noticed the new firmware seems to have some problem, here is the resulting graph:

After some further software / network diagnosis it seems that the gateway (webserver) is hanging up every once in a while. It appeared to be alive and responding for 140 seconds, followed by a 170 second period of failure. Looking at the graph, the red (voltage) square wave represents the alive (120V) dead (zero) pattern.

Ok, no problem let me just push the older firmware back on via the web interface. Bad idea – as the update took a bit longer than the 140 second window, and I managed to get the device into a non-responsive state. Now what?

Well, after some head scratching it occurred to me to download the installer program. This is a java based program, but thankfully it was able to find and restore my TED 5000. There were plenty of somewhat scary java error output messages on the console, but it did succeed after some amount of time. I also performed a full reset at one point – this too may have helped the recovery. So yes, I’m guilty of a bit of a hammer approach here – I’m just glad my TED is back to working. I will treat firmware updates with a bit more caution in the future.

I’m now using

  • Gateway v1.0.350
  • Footprints v1.0.185

Which may have bugs, but it seems to be working ok for me at the moment (at least my graphs are coming out ok).

There is a support forum which is somewhat helpful, but didn’t give me a great sense of comfort. There are a lot of very unhappy customers. The TED 5000 device is a very useful device, but has several technical problems.

  • There are many different (and valid) configurations to use the device in. I’m using one of the more simple setups, but the complexity impacts the software (firmware)
  • There are 3 different communication protocols being used: Zigbee wireless, power line communication and ethernet. Each has potential problems.
  • The firmware update is two separate files, and the web interface makes it too easy to do a bad firmware update.
  • The install of the device is non-trivial. So aside from firmware problems, the actual physical installation may be at fault.

External events can cause havoc too: Installing a new electronic device (or halogen light) may cause noise on the power line such that you disrupt power line communication. If you are using weather updates, there is an external web based weather service which needs to be reachable (and providing the service).

I keep meaning to cook up some RRDTool based graphs to track my usage as I really don’t like the built in TED web graphs all that much. There are also some nice DIY solutions out there for whole house power monitoring now.

I still like having the TED 5000, but I’m not sure I’d recommend it to people due to some of the problems. I’d love to see a simpler product that just provided the data stream and used a pogoplug or similar to handle the fancy graphing using an open source stack.