So, a couple weeks ago I got a couple of new phones: a Galaxy S2 and an iPhone 5.  This pair is replacing the Nexus S and the HTC Legend.  Why a Galaxy S2?  Isn’t there an S3 and an S4 out there?  Yes, and here’s why I got the S2.

First, I really like my Nexus S.  It’s the right size, has a nice display and does everything I need. But, it’s been doing these things at a progressively slower rate, and was becoming increasingly frustrating.  Initially, I took a look at the HTC One, Galaxy S4 and the Nexus 4 as replacements.  Both the HTC One and the S4 were way too big, and the Nexus 4′s somewhat dated specs and glass back didn’t seem like a great idea.  Like the S4, the S3 was also way too big, but the S2 and it’s 4.3″ screen seemed a bit more reasonable, at least at the time.

I don’t like the Galaxy S2.  Despite it’s comparatively small size, it’s too wide, feels bad in my hand, it’s corners are too squared-off and it’s generally terrible to use.  Believe it or not, the iPhone 5 is a great size and these monster Galaxy phones make it all the more obvious.  Specifically, the narrower form factor of the iPhone 5 really works well,  and with the exception of the Nexus S, makes these other phones look like poorly-designed, poorly-thought-out alternatives.  Thanks to the S2, I now have a chronically sore thumb from the too-wide screen and a slight scowl from repeated exposure to an offensive UI.

More complaints.  While Jelly Bean on the Nexus S offers a well-designed UI that both looks good and is easy to use, the Samsunged version of Jelly Bean offers almost none of this.  TouchWiz UX Nature is an awful name befitting an awful product.  Where Google’s Jelly Bean UI is clean, simple and nice, Samsung substitutes clutter, unnecessary crap and a UI seemingly designed by several groups unaware of the others existence.  What’s worse?  It’s very difficult and time consuming to remove most of this damage, and even then some of it remains.  In my efforts to make the phone tolerable, I’m using Holo Launcher HD, SwiftKey, Camera ICS+ and a few other small apps.  I tried a few other launchers (Apex, Go Launcher EX, Launcher Pro), but Holo Launcher HD is the most Jelly-Bean-like out of all of them.  Like the rest of the Samsung software, both the camera app and the keyboard in the  TouchWiz UX whatever are terrible.  In both cases, the stock alternatives are much better, and their absence is stupefying.  However, the single most annoying aspect of the phone (and one that I get to look at dozens of times per day) is Samsung’s cobbled-together notifications layout.  Green buttons, blue sliders and randomly shaded buttons?  What’s the second most annoying aspect of the S2?  That would be the notification sound (that cannot be disabled) when I plus the charger in every night.  It often seems like Samsung went out of their way to make every little last detail of the phone make you dislike it that much more.

Almost done.  My experience with the S2 has convinced me that Nexus phones are definitely the way to go.  I have no idea how so many people tollerate Samsung’s needlessly ugly, awful and generally infuriating changes to Android.  Assuming the next Nexus phone isn’t fatally flawed, the S2 is going straight to eBay once the Nexus 4′s sucessor is available.

Finally, the iPhone 5.  There’s not much to say here.  It’s an iPhone, it works, it’s well made, and despite iOS’s shortcomings, it’s very nice to use.  The iPhone 5′s biggest letdown is iOS. When compared to stock Jelly Bean, iOS seems dated and boring.  However, when compared to TouchWiz Nature UX, iOS is both refreshing and so much nicer to use.  Yes, TouchWiz is that bad.  Anyway, iOS’s grid of icons and the lack of configurability (Why can’t I set Chrome as my default browser???) need to go.  If Apple can address this with iOS 7, the iPhone would become a great alternative to a Nexus phone.

Neat: Strava Multiple Ride Mapper

I installed a new 10-speed Shimano Dura-Ace (CN-7901) chain on the 1994 Trek 2120 in February 2012, and in the following year I rode it 2,743km (1,705 miles).  Durring that year I only used Rock ‘n Roll Red lube, every other ride, or so.  I also adopted the no-solvent, lube-only style of chain maintenance, so the chain was never removed or degreased.  If the chain was gritty from a wet ride, I just flushed it with more lube until it was clean.

How did it do?  Well, according to my Pro-Link chain wear gauge, the chain is showing 1 / 10 wear, with 0 being new and 10 being worn.  Some have demonstrated that this type of gauge over estimates chain wear.  According to my ruler it has no discernable wear.   I’m going to continue the same maintenance regiment.  At this rate, the chain could possibly outlast the 18-year-old Trek.

According to a recent test from Bike Rumor, Shimano 10-speed chains tend to last longer than their 9-speed equivalents.  I don’t have any 9-speed road bikes to directly compare, but I do have a 2×9 cyclocross and a 1×9 hardtail MTB.  The Shimano Ultegra/XT HG-93 chain has been on the cyclocross bike since November 2011 and has be used for 1415km (880 miles).  The hardtail’s chain, also a Shimano Ultegra/XT HG-93, was installed in December 2011, has gone through some often dusty and sometimes muddy 1153km (716 miles).  It has had similar maintenance to the Dura-Ace chain, but with Rock ‘n Roll Gold.  The cyclocross chain is showing 1 / 10, and the hardtail is at  6 / 10.  While the HG-93 chain on the cyclocross seems to be doing well, the  hardtail’s chain will probably need to be replaced around the 2000km mark.  Fortunately, I have a Dura-Ace/XTR 7701 chain to go on the hardtail when the time comes.

The singlesspeed has a 1/8″ SRAM PC-1 chain, and is showing 5 / 10 wear after one month and 55km (34 miles) of use.  Why?  I have no idea.  The last chain was on for just under a year and just over 900km (560 miles).  It was replaced when it was showing 10/10 wear.  Both the cog and chainring are also about a year old with the same use as the chain, and are in very good shape.  I would swap the PC-1 for a 10-speed Dura-Ace 7901, but I unfortunately have a 1/8″ chainring.

Yep , that’s a 4:47am start time.  Route Map

How did 2012 go? It looks like 6427.8km in 320.6 hours with 71067.0m of climbing.  If that doesn’t work for you, 3,994.0 miles in 13 days, 8 hours, 35 minutes, 24 seconds and 233,159′, 5 25/64″ of climbing.

If you’re really bored, head over to Strava and see it in detail.