For those who don’t know, I was a hardcore Symbian user for years, mostly S60 devices, though I had a fleeting stint using a Nokia 9300 (my only S80 device ever).  That’s what you get when you spend the better part of 10 years working at Nokia.  Nokia has historically done a very good job of producing smartphones – it’s been their bread & butter for years.  I had a brief stint using an N97, followed by a loaner of an N97 Mini from the Womworld guys, and I was never wowed, heck, never even liked S60 v5.  For me, the last great S60 was v3.  FP1 or FP2 were both good to me.  Heck, I still have an N85 that I use for my home line.

These days, it seems like everyone’s in iLove, going absolutely gaga over the iPhone, including the latest incarnation – the iPhone 4.  Deathgrip aside, I was never a huge fan of the iPhone.  I had a 3G for a day, and returned it.  Bad battery life (like in the 3-4 hour range), and the walled garden – don’t get me started about locking out developers – I maintain that it’s bad for business in the long run.

I got my Nexus One in the AT&T variant, so it’s got quad-band GSM/EDGE and tri-band (850/1900/2100) UMTS/HSDPA support, as well as the 802.11g WLAN, Bluetooth and GPS radios.  That’s a lot of RF in a small case.  Physically speaking, the Nexus One feels great in your hand.  There’s some sort of coating on the metal parts that’s just slightly tacky, not metallic at all.  It just feels great in your hands.  The RF performance on the Nexus One is very good in my experience.  I don’t notice any lower coverage than I saw with my prior Nokia E72.  All in all, very good.

Connectivity is where Android 2.2 really shines.  On my Nexus One, I’ve got my home Google Apps account sync’d, as well as my corporate Exchange ActiveSync.  The phone keeps track of where the different bits of data came from and only tries to sync the appropriate data to the various accounts.  It’s very well thought out and I didn’t wind up with lots of data duplication.  Further, Android 2.2 implements the much sought-after mobile hotspot feature.  If you’re unfamiliar, you use your WLAN radio to setup an Access Point, then connect WLAN devices to that AP, which shares your phone’s 3G (or even EDGE) wireless data connection.  Pretty slick.

On the ActiveSync front, the client is very good, and fairly complete, though a couple of what I consider to be key features aren’t there yet.

Rather than the App Store, Android uses the Android Market.  Same idea, essentially, though it seems that you need to do substantially less hoop-jumping to get your app in the Market.  While yes, Apple definitely has a wide margin of available apps, I’ve yet to be disappointed when I got searching for an Android app for a specific task.  This review focuses on the device itself, not the apps, so I’m not going to go too deep there, but suffice it to say that I’m happy with the app selection.

Overall, it’s a great device, and the future for Android is indeed bright.  Go make the jump, you won’t be disappointed.

Physical Attributes

The device’s size is great.  Nice and small.  I had an N97 for a (very) short time not long after it came out, and I was not a fan of the form factor.  It felt almost like carrying around an old 9500.  What a brick that thing was.  Contrasted with this, I’d be totally satisfied with the form factor.  Obviously, thinner would be better, to a point, but I’m not unhappy with the thickness.  In terms of construction, there’s just enough metal to make it feel solid in your hands, like it’s not going to snap in half while you’re typing on it.

One problem I had with the layout – the position of the headphone jack.  On my train ride home from the office yesterday, I had my headphones plugged in while listening to some tunes.  Typing a couple of emails and texts was awkward.  It would have been better if the headphone jack had moved toward the top, but the camera assembly would then need to be relocated.  Typing on the keyboard wasn’t bad, took a bit of getting used to, but nothing ridiculous.

Software

I’ve said it before, and I’ll say it again.  S60 is really showing its age.  Yes, S60 v5 has some advances over v3, even FP2, but it’s still got a lot of the baggage that’s accompanied S60 devices over the years – mostly speed related.  This phone won’t win any UI races.  The device lacks any form of multi-touch capabilities, due to its use of a resistive touchscreen.  Yes, I’ve heard all the arguments about how you can use resistive screens while wearing gloves.  Frankly, I don’t often find myself trying to use my phone while wearing gloves.  I’d rather have a capacitive screen – much more responsive.

As it’s big brother does, the N97 Mini includes Ovi Maps, and is compatible with the new version of Ovi Maps that includes free navigation.  I love the free navigation concept, and expect others to follow suit.  That said, I much prefer using Google Maps.  I find it faster and more responsive than Ovi Maps overall, and think it’s much better at finding things in the area because of its hooks into the Google Search infrastructure.  I’d use something like Ovi Maps in my car for navigation, but I’ve owned a Garmin Nuvi for several years now, and I’m not quite ready to get rid of it.

For email, I’m using Mail for Exchange.  The latest version for S60 v5 does not include HTML mail support, something I miss from my E72.  I’m planning on trying out RoadSync on this phone as well, but since I already know that it doesn’t support network destinations (i.e. access point groups), I’ll be disappointed there as well, though I will get my HTML mail.

In the browser arena, as expected, I found the Nokia browser to be adequate, but not really as good as I’d like to see it.  I tried out Opera Mobile on the device, and was generally more pleased with its functionality, though I found it to be slightly less responsive than the stock Nokia browser.

Network

I ran a some speed tests from a variety of sites, using both AT&T 3G data as well as via the WLAN in my home.  Over the air, I saw download speeds ranging from 500 – 780 kbps.  Over the WLAN, I saw speeds around 1.2 Mbps.  On my Mac on the same WLAN, I see about 18 Mbps down and 4.2 Mbps up (I have 20/5 FiOS at home).  These performance numbers are consistent with my tests with other S60 phones, like the E71, E72 and my wife’s E75.  It’s also close to what my iPhone toting friends in the area see.

Conclusions

In summary, the N97 Mini is definitely a better choice than the bigger N97.  It’s more pocketable, and has the same features, with a better form factor.  If all you’re after is an S60 v5 touch device, you’d probably be better off with the 5800 Nav Edition, but if you can’t live without a qwerty keyboard, the N97 Mini is a winner.  Will I buy one?  Probably not – I’m satisfied with my E72.  Right now, Android 2.1 has ActiveSync that gets email and contacts.  If they add calender support to it, I’ll be on an Android device before too long.  Why?  Newer devices, more innovation, actual integration with Google Voice – something I actually use on a daily basis and more than one vendor really interested in using it.  Hopefully S60 can turn things around before my next phone purchase.  As a co-worker said the other day, the call quality on Nokia devices is better than anything else I’ve ever used.

Between the N85 and the E72, I tried out the Blackberry 9700, which was lovely, as much as a Blackberry can be, but lacked some of the features I liked, such as a working SIP stack, and especially the ability to tell when my data is moving through the corporate network/BES, vs. WLAN, vs. carrier data that’s not via the BES – I found that utterly impossible on the BB 9700.  Otherwise, a nice phone.  But again, back to the topic at hand.

First, I’ll start with the physical attributes of the E72.  The E72 is a tiny bit wider than the E71, but is the tiniest bit lighter than the E71.  The E72 trades in a good bit of the metal housing for plastic, but gets new & improved features like a 3.5mm headphone jack, instead of the 2.5mm mess that’s on the E71.  Radios are mostly equivalent to the E71.  Mine is the US variant, the E72-2, so it’s a quad-band GSM/EDGE device, with works on UMTS 850/1900/2100 Mhz bands.  The 2100 Mhz band is a nice addition to the device, for users who travel abroad, as is the support for HSPA 7.2 Mbps.  The WLAN in the E72 is essentially the same as the E71 – 802.11b/g. The camera is a nice bump in the E72 as well – a 5MP cam, a step above the E71′s 3.2 MP cam, with a single LED flash.

My favorite part about the phone?  The messaging experience.  At work, one of our options is Exchange ActiveSync, so I’ve been a Mail for Exchange user for quite a while now, even with its deficiencies, like the lack of ability to sync folders other than the Inbox, HTML support, and lack of ability to create a meeting request from the phone.  The device works with Nokia’s Messaging service, which I’m not using at this time.  For my personal mail (hosted by Google Apps), I use the Google Gmail app, which works just as well on the E72 as it did on the E71.

Overall, the E72 is a worthy successor to the E71.  Right now, Amazon’s got it for $369.  If you’re going to buy, please consider using my link to it.

The installer is largely unchanged from Hardy Heron, 8.04.  One new & welcome change is the newly integrated support for installation to dmraid devices.  These devices are largely SATA RAID controllers, such as the Intel Matrix controllers, largely software-driven.  I preferred this to the Linux RAID code, since replacing a drive/rebuilding a mirror seems more straight-forward this way.  As my server includes an Intel Matrix controller onboard, I went for this option.  It worked very well.  The device names are a bit long (/dev/mapper/isw_diaedigfhd_Volume03), but that’s fine.  I did a pretty basic layout, with 250MB of ext3 for /boot, a 4GB swap partition and the rest as JFS for /.

Also new in Intrepid is DKMS.  What’s that, you say?  Your lucky day, I say.  At least, if you use software that requires special kernel modules.  Back in the good old days, when you did something like that, every time you upgraded your kernel, you had to rebuild your custom kernel modules as well, a largely manual process.  DKMS takes the manual part out of the picture here.  You install a DKMS package, and when you update a kernel, the drivers from you DKMS packages are automagically built and installed.  I’m excited about the possibility of vmware module and DAHDI (the new name for zaptel) DKMS packages!

I’ve already installed VMware Server 2.0, which went well, aside from a bit of trouble compiling the vsock module.  I suspect this will get worked out before too long as well..

Intrepid Ibex, it’s worth the trip.  If you’re  looking to update an existing server, change your sources.list and dist-upgrade away.