Nexus 6P Flashing Charge Icon

Recently the USB-C quick charger that came with my Huawei Nexus 6P appeared to stop working. I normally leave the phone charging over night, but one morning I found its battery charge was low and it hadn’t been charging. When I disconnected and reconnected it to the cable (which is reversible with USB-C connectors on both ends), the lightning bolt inside the battery charge indicator kept blinking (flashing on and off), rather than being solid on as it normally would while the device is charging.

Disconnecting and reconnecting the device or unplugging and reconnecting the charger to the wall socket made no difference whatsoever. Reversing the cable direction did not help either.

My only way to still charge the phone was to use a USB-A to USB-C cable that draws power from a PC USB socket, which is a much slower way to charge the phone. So I decided that the charger must have failed after less than a year of use. I already started looking for USB-C quick chargers on Amazon (they exist but are much more pricey than USB-A chargers), but didn’t order one yet.

Today I decided to Google for the problem and found others who had the exact same issue. It turned out that simply powering down the phone and powering it up again will fix the problem: Yepp, it will charge again!

I’m not sure what the fundamental issue is, but it seems I won’t have to rush out and buy a new charger (which wouldn’t have helped anyway!), as the issue is on the phone side.

If a simple phone reboot fixes it and it doesn’t happen too often, I guess I can live with that. The Nexus 6P has worked great for me so far.

Porting iptables to ip6tables

A couple of days ago I received an email notification by the Berkeley Security Notifications Team that a Linux server of mine had less restrictive firewall rules for IPv6 than it had for IPv4. This prompted me to update my ip6tables settings on that host to make it is as secure via IPv6 as it was for IPv4.

If you have a dual stack server with IPv4 A records and IPv6 AAAA records published in DNS, you should have it protected with firewall rules on both protocols. Even if you only publish A records and not AAAA ones, you should secure IPv6 access because its address may leak to potential attackers in other ways.

The ip6tables tool is installed as part of iptables on recent distributions, but you need to set up one set of rules for each protocol. They’re independent of each other. A (not very secure) default ip6tables configuration might look like this:

# Generated by ip6tables-save v1.4.21 on Thu Sep 24 11:17:56 2015
*filter
:INPUT ACCEPT [0:0]
:FORWARD ACCEPT [0:0]
:OUTPUT ACCEPT [1456:118498]
-A INPUT -m state –state RELATED,ESTABLISHED -j ACCEPT
-A INPUT -p ipv6-icmp -j ACCEPT
-A INPUT -i lo -j ACCEPT
-A INPUT -p tcp -m state –state NEW -m tcp –dport 22 -j ACCEPT
-A INPUT -j REJECT –reject-with icmp6-adm-prohibited
-A FORWARD -j REJECT –reject-with icmp6-adm-prohibited
COMMIT
# Completed on Thu Sep 24 11:17:56 2015

It’s relatively easy to port additional settings from iptables to ip6tables (e.g. in /etc/sysconfig/iptables and /etc/sysconfig/ip6tables for CentOS).

Below are some of the changes needed when porting common entries. As you can see, some names are replaced with those of IPv6 equivalents. Any IP addresses and CIDRs for ip6tables need to be written in IPv6 notation.

To easily port over IPv4 addresses, simply prefix them with “::ffff:”. If they’re followed by a bit count such as /24 (the routing prefix size), add 96 to that number (IPv6 addresses are 128 bits each versus 32 bits for IPv4). Add equivalent rules for the corresponding native IPv6 addresses as needed.

  1. Accept ping from any source:

    IPv4:

    -A INPUT -p icmp -j ACCEPT

    IPv6:

    -A INPUT -p ipv6-icmp -j ACCEPT

  2. Accept connection from white-listed address:

    IPv4:

    -A SSH-IN -s 123.45.67.89/32 -j ACCEPT

    IPv6:

    -A SSH-IN -s ::ffff:123.45.67.89/128 -j ACCEPT
    -A SSH-IN -s 2345:abcd:678:42::/64 -j ACCEPT

  3. Rule to block access (after all the exceptions):

    IPv4:

    -A INPUT -j REJECT –reject-with icmp-host-prohibited
    -A FORWARD -j REJECT –reject-with icmp-host-prohibited

    IPV6:

    -A INPUT -j REJECT –reject-with icmp6-adm-prohibited
    -A FORWARD -j REJECT –reject-with icmp6-adm-prohibited

Filco Majestouch-2 [FKBN104M/EB2]

Recently, the space bar of the keyboard on my main machine developed a problem, so I ordered a Filco Majestouch-2 (US layout, USB version with PS/2 adapter). It uses brown Cherry MX switches.

I have always liked the feel and feedback of the original IBM PC and IBM PC/AT keyboards (which I first used in 1981). If you’re a fan of the original IBM keyboards, you’ll love this one. The Filco keyboards are not cheap, but you get what you pay for.

There are various models from Filco, some with the blue or black Cherry switches. The brown switches are recommended for general use, including office work and programming. I am very happy with mine and will probably order another one for another of my machines.

Acer One D260 system restore

The hard disk in my wife’s Acer One D260 netbook got damaged. A new hard disk is about a quarter the price of a new netbook, so I wanted to install a new drive. Like with most PCs these days there aren’t any Windows install DVDs included.

The netbook came with Windows 7 Starter, which we needed to somehow install on the new hard disk. Fortunately, the damaged hard disk was still limping along enough to use the Acer eRecovery system to create two Recovery DVDs. These should allow restoring the initial system state to a hard disk in the machine, wiping all the data on the drive.

To replace the hard disk, I had to undo seven clips around the edge of the keyboard, lift off the keyboard and disconnect the keyboard ribbon cable to the motherboard connector. Then I needed to undo 4 screws underneath and push through, to pop out the cover on the bottom of the machine. This opened access to the single memory slot and drive cage.

The 1 GB memory module on the motherboard can be replaced with a 2 GB PC3-8500 1066MHZ DDR3 module available for about $20. This is a wortwhile investment and I already have the module on order.

I replaced the damaged 250 GB WD Scorpio Blue drive with a spare 500 GB drive (available new for about $60-$80). Then I closed the cover and reinstalled the screws and then the keyboard.

With the new drive it was possible to boot off the first Recovery DVD using a USB DVD drive. The eRecovery software copied data from both DVDs to the hard disks and then rebooted. However, that reboot failed because the new drive did not yet have a Windows Master Boot record (MBR) on it. You can install an MBR from within Windows, but not from the bootable eRecovery DVD. So I had a chicken and egg problem.

I overcame this hurdle by booting off a Ubuntu Live DVD (32 bit), installing the ‘lilo’ package and telling it to install the Linux equivalent of Microsoft’s MBR code:

sudo apt-get install lilo
sudo lilo -M /dev/sda mbr

At the next attempt to boot off the hard disk, Windows started installing its components and drivers and launched into its initial configuration, just like the first time we had unboxed the machine more than two years ago. So we are back to a working Winmdows 7 machine!

Thank you, Linux — you saved my day again! 🙂

Western Digital 4 KB sector drive alignment for Windows XP and 2003 server

If your existing Windows XP or Windows 2003 Server machine needs a new C: drive, there are ways of upgrading to one of the latest drives without a complete software reinstall, but you may encounter some stumbling blocks due to the new Advanced Format technology, which uses 4 KB sectors.

When one of my PCs developed hard disk problems and I had to upgrade one of its drives, I also checked out my other machines. I found the C: drive of a Windows 2003 Server machine was about to fail. Windows 2003 is basically the server version of Windows XP, with which it shares most components. I opted for a 1 TB WD Red drive (WD10EFRX) by Western Digital, since these drives are designed for 24/7 operation, primarily for use in Network Attached Storage (NAS) appliances (desktop drives are only designed for an 8 hours on, 16 hours off use pattern).

I did not want to reinstall everything from scratch on that machine, so I used a Linux boot DVD and the GNU dd utility to mirror the failing drive onto the new WD Red drive (“sudo dd if=/dev/sda of=/dev/sdb”). As a result, all the partitions were in the same place and the same size as on the old drive, a Seagate Barracuda 7200.11 320 GB. The partitions on the old drive had not been aligned on 4 KB boundaries as is recommended to get decent performance on modern Advanced Format drives, so I needed to run an align tool to move the partition to the proper place. Western Digital offers one free to its customers, so that should be easy then, right?

No quite. I encountered all the troubles described by others in this thread: Basically, the download link for the WD Align tool (AcronisAlignTool_s_e_2_0_111.exe) takes you back to the same page, over and over, without error message. It turns out that you need to be registered and logged in to the WD site for the download link to do anything. You need to register both your contact details (name, e-mail address, postal address, phone number) and your hard disk’s serial number. For the latter I had to shut down the machine again and take out the drive once more to take a look, because the number is not printed on the cardboard box, only on the drive itself.

Once I registered my new drive, a download link did appear next to the registered product, but from it I found I could only download Acronis True Image and not the Acronis Align Tool (Advanced Format Software, WD Align). The WD Red series drives are all Advanced Format Drives, as is pretty much every drive made since 2011, but WD say it is designed for NAS use and hence don’t see the need for a fix for what they see as a Windows XP problem.

Various people online recommended a download site in Ukraine that apparently offers a copy of that program, but if you’re downloading from sites like that you risk installing malware on your computer. Beware!

There is a safer solution. I had to register another Western Digital drive, an old WD10EARS to get a usable download link for Advanced Format Software. If you don’t happen to have one lying around, a Google image search for WD10EARS will show you many photographs of disk drives with clearly readable serial numbers on the label. And apparently, these serial numbers will do the trick! 😉

After I downloaded the software, I ran it to make a bootable CD (it also seems to be Linux-based), booted and ran it and 1 hour and 30 minutes later my C: partition was showing up as properly aligned.

I can understand that Western Digital wants to restrict the use of licensed Acronis software to its own customers, denying other brands a free ride. However, the hoops it is making people jump through to be able to use one of their new drives as an upgrade to an existing Windows XP machine is just ridiculous. If a login is required to do the download, it should clearly say so. And if a drive uses 4 KB sectors (Advanced Format), its serial number should qualify you for the download. There are millions of existing XP users out there still and many will need new hard disks before they need a new computer.

A hilly 200 km brevet in scenic Izu peninsula

Yesterday I cycled 200 km across the mountains of west Izu (Shizuoka prefecture, Japan) on my Bike Friday folding bike. I had resolved do at least one century ride (160+ km) every calendar month of this year, some of them organised events, but most personal rides. BRM309 200 km by AJ NishiTokyo was my first official brevet of the year. I completed it in an official time of 12:58, i.e. just over half an hour under the 13 1/2 hour time limit.

The scenery was beautiful and the weather perfect but the course tough. With a highest point of 450 m, I first found it hard to believe that this course should really have more climbing (3159 m total) than the 300 km Fuji brevet I did last May (2800 m total), but except for the first and last 10% and some short stretches through the towns on the coast, this was a pedal-powered roller coaster! On the smaller roads grades of 8-11 percent were not uncommon.

I loaded the Bike Friday into the Prius the night before (no need to fold the bike or take off the wheels), went to bed at midnight and got up at 04:00. A little after 06:00 I got off Tomei expressway at Numazu and drove near Mishima station, where I found a 1000 yen ($10.50) a day car park. One couple dressed like randonneurs was already setting up their bikes in there.

An hour from home on the expressway it had suddenly struck me I had left my reflective vest at home. No vest, no brevet! But it was already too late to turn back. Fortunately the organisers had some stock and sold me one for 1600 yen ($17). To start with I was wearing new bib shorts and new jerseys (two layers for the morning and evening chill). GS Astuto’s HauteRoute shorts proved exceptionally comfortable, like wearing your best pair of pajamas at home. I sweated a lot, in fact my cheeks were white with salt afterwards, but the shorts and jersey kept me comfortable. The deep pockets safely stored wallet, camera, keys and some food.

There were 60 riders in two blocks of 30, starting at 7:30 and 8:00. They started us in smaller groups. I was wearing my heart rate belt and wanted to aim for a consistent workout throughout the day, but I worked much harder during the first 50 km than I had intended and less hard later on. When you have some other fast guys to follow (which would save you having to navigate) it is tempting to hang on at whatever cost. We headed through town and along a river to the south. After 20 km the route started climbing, peaking at a tunnel about 450 m above sea level, then down to the coast. We made the first 50 km in 2 1/2 hours, putting me more than half an hour ahead of the pace needed for completing in time, and that is what I also finished with.

I glimpsed Mt Fuji across the bay from near Toi.

The coastal road went to Matsuzaki through many tunnels and a couple of climbs. After Matsuzaki we climbed the second highest pass on a small mountain road and it was very pretty. Plum trees (ume) were in bloom everywhere.

PC1 (point de contrôle 1) was at 95 km, almost at the half way point, but there had also been a safety check at the first tunnel (lights!). We were given pastries baked in the shape of bicycle cranks.

From the control point we headed west to the coast, which we mostly stayed on. As mentioned before, the coastal road goes mostly up and down. It only becomes level again at the north west corner of Izu. The top third of the west coast was the hardest part. There were few villages, no shops and it was gradually getting dark. I had somehow expected the second half of the ride to be easier than the first because the maximum elevations were much lower, but it was actually harder. Between Toi and the north coast there were no flat portions in towns between descents and climbs, because there were no towns (or more appropriately, there were no towns there because there was no flat land).

The following was a sign we had to spot and then write down the Kanji characters, as part of a quiz question. As a Kanji-challenged foreigner, I got dispensation to bring back a picture instead:

Izu used to have a lot of terraced rice fields built into the hills because there wasn’t much flat land. Much of these fields now lie fallow or have been turned into sugi tree plantations contributing to the hay fever epidemic in Tokyo.

Mt Fuji at dusk:

I completed!

Having my brevet card checked at the finish:

Garmin Edge 500 on long rides

Since January I’ve been using a Garmin Edge 500 with heart rate monitor strap for logging bike rides. Garmin quotes a battery life of “up to 18 hours”. After this 13 hour bike ride, it showed a remaining battery capacity of 21%. Extrapolating from this, the battery would have lasted about 16 hours in total.

I was not just logging the ride (GPS data) but also using the heart rate strap and had the Garmin track a course with turn-by-turn instructions, which probably draws a bit more power. I had created the course as a TCX file in RideWithGPS while looking at the course as published on http://latlonglab.yahoo.co.jp.

In any case, 16 hours is enough for a 200 km brevet with its 13 1/2 hour time limit, but not enough for a 300 km brevet with its 20 hour limit, unless you are a really fast cyclist and/or the course is extremely flat. For my 300 km brevet I am planning to use my Garmin Edge 500 power hack, a special USB cable that allows me to charge the device while logging and navigating.

Garmin Edge USB power hack

I use a Garmin Edge 500 for recording most of my bicycle rides (I do at least one ride of 160 km or more per month on my Bike Friday Pocket Rocket). One problem with the Garmin is that some of my rides will take longer than the Garmin’s battery will last, but if you try to use an external power source to top up the charge, it will instantly end the recording. Here is my working solution:

Garmin quotes “up to 18 hours” of battery life, but last May I did a 300 km brevet with a 20 hour time limit. There are also 400 and 600 km brevets with 27 and 40 hour time limits (I am not thinking about 1200 km events yet!). While the Garmin has a USB port that it can be charged from using a cable, it won’t normally operate as a GPS unit while connected to a USB power source. Any GPS recording under way will instantly be terminated when you plug in the cable. So what can you do about that?

I searched a bit on Google and found that when you plug a USB cable into the socket at the back of the Garmin, it tests pin X on the USB mini connector. On normal cables (including the one that comes bundled with the Garmin Edge 500) that pin is left disconnected. Unless it finds it tied to ground (GND) as you supply external power to the Garmin, it will switch into a passive storage device mode. In that mode it provides read/write access to a PC via the USB port with all GPS functionality and user interface disabled. The screen will display only the brand name and it won’t respond to any buttons being pressed. If pin X is tied to GND, it will operate normally.

This behaviour mirrors the way pin X works on smart phones that support the USB “On The Go” (OTG) specification. USB OTG allows smart phones to drive certain peripherals such as memory card readers, in the same way a PC can drive those peripherals. Normally when a smart phone is connected to a USB port, it acts as a passive storage device to which a PC can upload MP3 files or from which it can download photographs (JPEG files). With an OTG cable, the phone remains the active end. Pin X is the magic key that tells the phone which way to behave, active or passive. It all depends on whether the USB plug is an OTG plug or a regular one.

My cheap low-tech solution was to buy a USB mini OTG adapter (480 yen – about US$5) on Amazon. This has a USB mini plug with pin X wired to GND on one end and a female USB-A connector (like a USB socket on a PC) on the other. To get power into this I cut the USB A plugs off two old peripherals (such as an old USB mouse), stripped off the ends of the wires in the cable and connected black to black (GND), red to red (+5V). This was not too hard even for my soldering skills. A bit of insulating tape and voila! We have a new male-to-male cable that can draw power from any USB power source and feed it into the female end of the OTG adapter. When I plugged it all together, I could run the Garmin in GPS mode while running on external power from my USB battery.

Lawyer Note: Do not use a male-to-male cable or OTG adapter for any other purpose. Do NOT connect the male-to-male cable to two PCs. Do NOT connect the OTG adapter between a phone and a power source. Only ever connect the cable to the OTG adapter. Only ever connect the OTG adapter to the Garmin. I won’t be responsible for bad wiring mistakes or other stupid mistakes. Don’t sue me if your Garmin or house goes up in smoke!

Here is the photographic evidence that it all works for me:

You can find USB Mini OTG adapters and USB Mini OTG cables on DealExtreme (dx.com). They also have USB-A male-to-male cables and adapters, so you don’t have to make your own as I did (though it’s not difficult if you have at least very basic soldering skills). Any combination of a USB Mini OTG cable or adapter and a USB-A male-to-male cable or adapter should work.

Upgrading to a Western Digital WD20EFRX hard disk

All hard disks will die, sooner or later. They only way to avoid that is to retire a drive early enough. Often I upgrade drives because I run out of disk space, and migrate the data to a bigger drive. However, this times it looks like one of my drives is about to die.

Over the last couple of months, one of my PCs that is processing data 24/7 has been seizing up periodically, so I was starting to get suspicious about its hard drives (it has two of them). This week the Windows 7 event viewer reported that NTFS had encountered write errors on the secondary drive. It’s a Samsung SpinPoint F2 EG (Samsung HD154UI, 1.5 TB) which basically has been busy non stop for over three years.

I installed smartmontools for Windows and it showed errors:

ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x000f 099 065 051 Pre-fail Always - 5230
(...)
13 Read_Soft_Error_Rate 0x000e 099 065 000 Old_age Always - 5223
(...)
187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 12379
(...)
197 Current_Pending_Sector 0x0012 099 099 000 Old_age Always - 24

“Reported_Uncorrect” are fatal errors and “Current_Pending_Sector” are bad sectors the drive wants to replace with spare sectors as soon as it can. Neither is a good sign. So I have ordered a new drive, started a backup to another machine and will replace the drive with a new disk that I have ordered from Amazon.

The new drive is a 2 TB Western Digital WD20EFRX, which is part of WD’s “Red” series. These drives are specifically designed for 24/7 operation (as opposed for 8/5 office computers). The drive is 0.5 GB bigger, which is just as well as the old drive was getting close to filling up. Gradually I will be moving my processing to an Ubuntu server, which I already use as my main archive machine with a RAID6 drive array.

Garmin Edge 500 with Heart Rate and Cadence

I’ve had my first week with my new Garmin Edge 500 with cadence sensor and premium heart rate monitor strap, so it’s time for a review. I bought it on Wiggle for about JPY 24,500 ($274).

Around the time I bought the Garmin Edge 500, the new Edge 510 came out. It adds a touch screen, wireless connectivity to a smartphone and various nifty new features, but is also more expensive, so I went for the existing 500.

I switched to the Garmin after more than a year and over 8,000 km of GPS logging using Android phones, mostly my Google Nexus S. Here are my first impressions (the cadence sensor in the bundled set is installed on my son’s bike for use with his 500, so it’s not part of this review):

  1. I really love being able to use a heart rate strap and it’s nice to be able to see the HR figure without having to push a button (daylight permitting). I can ride at a consistent effort level, avoiding both effort too light to build stamina and extreme effort that would lead to premature exhaustion. If money were no object, a power meter would work best (which the Garmin supports). A heart rate monitor is an inexpensive alternative that works for most cyclists wanting to improve their performance.
  2. Because of its barometric altimeter the elevation totals are much more meaningful on the Garmin than on the GPS-only phone, where they may be exaggerated by a factor of 2 to 3. Current altitude data on the Android is OK, but small variations add up too much and grades on climbs and descents may be overestimated.
  3. I love the 90 degree turn quick attach / quick release of the Garmin. It feels both secure and convenient. It is more confidence inspiring than the Minoura iH-100-S phone holder for my Android, which is generally reliable, but not 100% bulletproof. Even after using a bumper for the phone, which has improved the grip of the holder, I’ve had a few instances where on bumpy roads only the USB cable attached to the phone saved my day. I would never entrust my $300 phone to the Minoura without some kind of backup method of attachment, while I feel safe about the Garmin’s mode of attachment.
  4. Importing the rides into Strava or Garmin Connect after the ride is really easy. I just connect the Garmin to the USB cable of the PC and click “upload” on the website in the browser and the browser plugin finds the fresh tracks and uploads them. Assigning a name is marginally easier with a real keyboard than a soft keyboard on the Android Strava app. With the smartphone I could also upload rides while I’m on the road, but why do that if I’ll still add more kilometres until I get back home? That would only be a benefit on a multi day tour without laptop.
  5. One drawback of the Garmin is lack of direct Linux support. My son runs Ubuntu on his laptop, while Garmin only officially supports Microsoft Windows and Mac OS X, so he asked me to upload his activities on one of my PCs. There’s a workable solution though. When you connect the Garmin to a USB port on an Ubuntu machine, it gets mounted as a removable volume named “GARMIN”. In there is a folder called Garmin, with another folder Activities inside which contains all logged rides as .fit files. Copy those to your hard disk and then upload them manually from a browser (Strava supports .gpx, .tcx, .json, and .fit files).
  6. When leaving the house, both the Garmin and the Android take a short while to lock onto the satellites and the Android seems to have something of an edge (excuse the pun) over the Garmin, which does seem to take its time. Maybe that’s because the Android pull pull satellite position data off the web, while the Garmin can only use whatever data it captured before. In one unscientific test, I took my Android and my Garmin outside in the morning. The Android had a satellite lock in 15 seconds while the Garmin took a more leisurely 44 seconds. This is a minor issue to me compared to the next one, GPS precision.
  7. While I have seen better GPS results on some rides from the Garmin than the Android, switching from the latter to the former has not been a dramatic improvement. I think their results are still in the same class, i.e. far from perfect, especially in built-up areas. Neither is like my car GPS, which is pretty solid. Both my son and I have been riding on Strava segments in Tokyo, expecting to be ranked but found the segment didn’t show up because the plotted route was slightly off to the side, so the segment start or end didn’t match up.
  8. Having temperature data on the Garmin is nice, but not really important to me. Unlike heart rate and cadence it’s not feedback that you can use instantly in how you cycle. Your body is a temperature sensor anyway and how you dress is at least as important as the absolute temperature.
  9. The Garmin 500 battery is supposed to last “up to 18 hours”, which would cover me on everything but 300 km and longer brevets, but on any significant rides I tend to take my Android phone, which I use for Google Maps, e-mail, SMS and yes, even the occasional phone call. Using an external 8,000 mAh battery for the Android, battery life has not really been an issue. The same battery will charge either device (one at a time), provided I take both a mini and micro USB cable with me.

Summary

If my Android had an ANT+ chip or supported BTLE (BT 4.0) for using a heart rate monitor as well as a barometric altimeter, then it would still be my first choice for logging bike rides. Given the limitations of my phone and the reasonable price of the Garmin Edge 500 I am very happy with my purchase.

Ultegra Di2 versus Alfine 11 Di2

I just saw a post by Bike Friday head designer Rob English about Ultegra Di2 becoming available on their high end folding bikes. Di2 is Shimano’s electronic gear shift system. The first version appeared on their high end Dura Ace group set used by professional racers. The latest Ultegra Di2 is more affordable, but it’s still not cheap (about US$2,300 vs. $4,000 for the group set). A few months ago my son had the chance to take the Di2-equipped 700C bike of my friend Eric of the GS Astuto team for a spin and simply loved it. Gear changes were so quick and precise and the front derailleur adjusts as you switch through the cassette at the rear. No manual trimming is ever required to avoid chain rub. You never mess up any gear shifts, even under load. Once set up the system remains precisely tuned, with no maintenance required for months.

Some cyclists are skeptical about electronic shifting because it involves batteries. That’s somewhat understandable, since as users of mobile phones and digital cameras we have all experienced running out of charge, often when it’s most inconvenient. However, from what I hear one charge of the Di2 battery should last you about 1,000 km of cycling, far further than the average car fuel tank. A battery that lasts weeks and months should be good enough for most people. What’s more, even if you do run out of power you first get ample warning. For instance, the front derailleur stops working before you will run out of juice for the more important rear derailleur. The ideal setup of course would be electronic shifting combined with a dynamo hub. You would get all the benefits of an electronic system with the self-sufficiency of an all mechanical setup.

After Ultegra Di2, some people were hoping for Shimano to announce a 105 version of Di2 as the next step of digital shifting for the masses (105 is the next road group below Dura Ace and Ultegra), but instead Shimano chose to announce Alfine 11 Di2 (Shimano SG-S705), an electronic version of its 11 speed internal geared hub (IGH), the mechanical version of which had been launched in 2010.

Alfine 11 Di2 addresses the vast city and commuter market, but it should also be interesting for road, touring and mountain bikes. IGHs do without a vulnerable derailleur and require less maintenance. The Alfine 11 gear range (low to high) of 1:4.09 is wider than the 1:3.74 spread of a compact crank (50/34) with a 11-28 cassette. Unlike the mechanical version, Ultegra Di2 does not yet support triple cranks and bigger cassettes can only be done via non-standard hacks.

I recently rode some insanely steep hills west of Tokyo (18-20%), which I could not possibly have managed without the lowest gear of my triple cranks setup (50/39/30 and 11-28 with 20″ 451 wheels). Therefore I think I would be more interested in Alfine 11 Di2, even if Ultegra Di2 will be more appealing to road bike purists.