Wednesday, August 23, 2017

Day 1: Cathedral Cave

The drive out to the Cathedral cave was scary. After the freeway and normal highway of the previous day, we entered the realm of the single track road once we were past Amberside. I kept wondering if I would end up being in one of the stories about the guy who followed Google directions until he drove off a cliff. When the road devolved from pavement into gravel, I found the next spot in the road wide enough for another car to pass by and parked.

Once we parked and got the kids out and started walking, we saw another parking lot, but since where I was was good enough and it was no more than 200 meters, I just left my car alone. The thing about English National Parks is that they're short on signs. Fortunately, there were enough hikers coming from where we were going that we knew we'd find it, and indeed some of them were so enthusiastic about the quarry that they stopped to tell us about it in case we were going to pass it up!
The cave was indeed big, with several openings into it, and an exit that led to a cliff-side rappel, where some climbers were working out a path. There was an old ruin that Bowen and Boen enjoyed playing in, and several paths down as well, including hidden bridges and vistas and old farm houses. Across the river, we could see buildings, and someone told us there was a pub there where we could get food.

Once on the footpath to the Three Shires Inn, it was the Lakes District as I remembered it: gorgeous and stunning.
Unfortunately, the food was as I remembered it as well: not really very good, but expensive. On the way back from the Cavern, we visited Grasmere, and there I bought a pamphlet for walking in Ambleside, since we were going to be there 4 nights.
Once in Ambleside, we checked into our hotel (which was too warm to stay in), and went for a walk down to the bridge house. Then after that it was dinner time and then time to wind the kids down and bed.

Tuesday, August 22, 2017

Prolog: San Francisco to Manchester

On June 18th, Phil Sung gave us a ride to the airport in his minivan, which with some seats removed, could take the tandem without disassembly. At the airport, we tried to check-in the tandem, but the airline staff required that the bike be in the box. My original plan for the tandem was to land at the airport, assemble the bike (which would take all of 20 minutes), and ride it to the Etrop Grange Hotel. Having it in a box would require much more disassembly, and worse, I'd have to save the box for the return trip, so that scratched the plan. If I'd known that they airline would give me such a hard time, I would have prepacked the bike in multiple boxes by taking it apart with the couplers, but as it was, I had to find the guys at the airport who would supply me with boxes and pack the bike.

This was done in fairly short order, and after the rigamarole, we still had time to visit the Virgin Atlantic lounge before getting onto the plane. Once on the plane, Boen had a tough time: the plan was for him to be in first class with mommy and Bowen and I be in the economy seats (we had separate return dates, so had to book separately anyway), but Boen didn't want first class, so Bowen went to first class instead. Once he was settled Boen actually slept for much of the trip.

Upon landing, my wife dealt with the kids while I went to get the rental car. It turned out that our vendor, Europcar was over-booked that day, and there was a 2 hour wait for cars. I demonstrated my distress and they finally relented and sent a driver with me in a van to pick everyone up from Terminal 2. Along the way, they helped me drop off the bike box at Etrop Grange Hotel. The hotel manager didn't want to take the bike at first, but I told them I had 2 reservations at the hotel, and he finally relented and let me put my bike box in a container outside in the parking lot that was locked.

I upgraded to a station wagon since we actually had enough luggage to justify it. It was diesel, so the additional $10/day in rental fee would be partially offset by the fuel efficiency. After installing the car seats and everything in the car, we then faced a 2 and a half hour drive to the hotel.

When I was planning the trip, I used Google maps to determine the acceptable driving distance from the airport. Unfortunately, I had made a fatal mistake: during the planning process, it was usually  evening in California, which would have been 2:00am GMT, so all the driving time estimates were completely wrong, since there were no traffic jams at 2:00am. So while I'd planned for a 1.5 hour drive to our first hotel in the Lakes district, it ended up being 2.5 and I was exhausted when I got there, compounding jet-lag with the stress and fatigue of dealing with the car company and arguing with the hotel about bike storage.
Fortunately, the hotel we'd booked was gorgeous, and had a wide open area outside for Bowen and Boen to chase the baby ducks and play. We had a non-descript dinner, and when it was late enough, turned in and slept, but not before I'd run into a local who told us that Cathedral Cave  was a good place to take the family tomorrow.

Monday, August 21, 2017

Bowen's Tour: Notes on Equipment

Here's commentary on various bike equipment we brought and used or didn't use, that didn't otherwise get a separate review:
  • Cheap bicycle lights. Turned out we didn't ride through any tunnels, and were always done before it got dark. Good thing, since we lost our lights on the 2nd day of the tour. (Probably left in hotel room)
  • Waterproof Kindle. Very useful for playground stops and for bed time reading. I read several books during the tour.
  • Portable charger. Used this during the rest day. Otherwise, not necessary.
  • Arm warmers/leg warmers: didn't need. Weather too warm.
  • Rain gear: used during the rest day when it rained. Occasionally if Bowen got cold, he'd put on rain pants or rain jacket for additional warmth, so this was a good addition.
  • Cheap Multi-tool.  Worked well enough, but lost the chain tool because it's not properly captured. Will probably upgrade to a better designed tool for another tour, or bring a separate chain tool.
  • S&S coupler wrench. Includes pedal wrench, which was very useful when Bowen's pedal fell off.
  • Playstation Vita. Crucial for keeping Bowen quiet while driving the car, or on the train ride back. Since the trip was driven by a location in a video game, it seemed appropriate to have the Vita with us.
  • Bluetooth Headset. This was surprisingly useful, both as a navigation aid (pair with phone and use Google's voice directions), and for calling AirBnB owners when directions were ambiguous.
  • Oakley M Frames. At home I tend to use transition glasses, and they work well. But transition lenses turn dark even when it's cloudy out, and I expected that in England things would be very cloudy out often. Having both clear and dark lenses to switch between was very helpful. Absolutely required equipment for English touring.
  • Shimano T400 Click'r Pedal. On a single kid's bike, clipping in is optional. On a tandem, however, it's essential. These survived the trip. If they hadn't, I'd have had to pay for Same-Day Shipping to replace them. That's how important they are. Enough said.
  • Answer Speeder Cycling Shoes. These are discontinued, but I was lucky enough to buy them used for the trip. They come with laces and velcro, which is insane. The laces are almost understandable, as you need to lace up the shoes so his feet don't fall out since parents tend to buy shoes for children's feet to grow into. But the velcro on top of that was just over-the top. Sure, you need a shield for the laces so they don't get eaten by the chain, but why not just have the velcro, then? In any case, nobody makes shoes small enough for kids when it comes to cycling.
  • Ordnance Survey Maps. Surprisingly, I had these maps in the panniers the whole time and only used them once: to show the receptionist at the hotel at the start of the trip! The rest of the time, I depended on the smartphone and GPS. This was a mistake. Or you might say that I've gone digital native and should stop carrying paper maps.
One of the biggest issues with bringing a kid on tour is that you have to convince him that reducing weight and bulk is important. To do this, I packed the panniers with all our necessary gear, and showed Bowen that there was no room to bring his security blanket, though there was room for his bunny. Thankfully once he saw the panniers and lifted them to see how heavy they were, he was OK with leaving his security blankets behind. Yes, I'm aware that I have an exceptional kid --- you might not be so lucky with yours!

Friday, August 18, 2017

Review: Parable of the Sower

Parable of the Sower is Octavia Butler's novel of post apocalyptic America. This particular novel is of special interest because not only Butler died before completing her trilogy, but because the novel covers a future eerily like the one we're living through now, only worse. We've got climate change, a cultural "screw you, I've got mine" general attitude, and a breakdown in society. The major freeways have become roads for refugees to flee a no-longer-suitable-for-human-habitation Los Angeles.

Amidst all this, a young girl tries to survive, and even better, consciously tries to start a new religion and community out of the rag-tag group of survivors she encounters after her community burns down and she starts walking North.

It's fun to read about all the parts of California that she references and discusses. I've cycled many of the places myself. The religion she creates is also interesting. Far better than the usual recycled-Judea-Christian garbage you find in typical fiction.

How, you may ask, was Butler so far ahead of her time? Well, for one thing, she (and her characters) was Black. The things she take for granted (ineffective police who're more likely to threaten you as to help you, and are strangely only interested in rich people's problems) were probably reality for her in ways that it might not have been for her white colleagues in science fiction.

A prophetic novel, and a dire warning of what is to come if we don't heed its warnings and pull ourselves together. Recommended.

Thursday, August 17, 2017

Long Term Review: Moto G Plus (Amazon Edition)

I bought the Moto G5 Plus for several reasons:

  1. The ability to use RidewithGPS on Firefox for route planning. 
  2. Long battery life: in order to do LiveTracking, navigation, and potential Google Maps voice directions while cycling in a foreign country. 
  3. A replacement camera, since I didn’t expect to have the time to frame and properly compose photos while cycling on a tandem, so didn’t feel like spending the $600 a large sensor travel camera would cost. Needless to say, under the constraints of the above, bringing the M3 wasn’t in consideration either. 
To my surprise, #1 was a bust. Despite my extensive testing on the phone before leaving the USA, once on the ground I discovered that Firefox running RidewithGPS was balky and slow. The one time I needed to use it, it was easier to ask my AirBnB host to borrow her large screen computer instead. I resorted to either manual routing (i.e., just ignoring the GPS and reading road signs instead), or using short term Google Maps routing instead.

#2 was a complete success. The Moto G5+ doesn’t have the insane battery life my wife’s Moto Z Play has, but it cost quite a bit less, and as long as I started the day with a full charge, I never ended the cycling day with less than 50% battery life, despite using LiveTrack. My worst days of battery life were the zero day when we rented a car and I was using Google Maps full time for driving navigation, and the day in London, when we would spend lots of time underground in subways or indoors without cell coverage, and the strain on the battery of the phone trying to find a signal would quickly drain the battery. The driving day was surprisingly bad, because without a QC charger in the car, the USB port in the Fiesta 500’s driver compartment simply couldn’t keep up with the battery drain. Nevertheless, on both days I ended with about 10% battery life, and not stranded. This is a phone that will last your typical day and then some.

#3 was a surprise for me. When I first tested the phone on the first few days of the trip, I was shocked and surprised by how badly the phone’s camera app behaved. I would “twist to start the camera” and then be disappointed by the message “your camera app has crashed. Please restart it.” Fortunately, a reboot midway through the trip fixed the crashing problem and it was solid for the entirety of the cycling trip, which was when I was using the phone as my only camera.

The photos aren’t great, but I’d argue they’re no worse than a typical phone’s pictures --- all phones have tiny camera sensors, and you just can’t overcome the physics involved. What is great is that the Moto G5+ has support for a micro-SD card. I actually filled the card with photos during the trip, but the software automatically switched to the on-board storage. Since I was carrying around a 64GB SD card, there’s no doubt in my mind that just the 64GB of onboard storage on the phone would have been insufficient for my use case. I have no idea how people who have 32GB Pixel or iPhones survive, though my guess is those people don’t do multi-day bicycle tours.

All through the trip, the phone’s been fast enough, and good enough that I never wanted another phone. I still dislike that the phone’s not waterproof, but it did survive that one rainy evening at Stonehenge, so even that’s less of a concern than it was. And you can’t beat the Amazon subsidized price.

Highly recommended. Yes, there are better phones, but they cost way more. This is the one to get in the mean time.

Wednesday, August 16, 2017

Review: Wizo Ultra-Thin Folding Keyboard

After my surface pro died, I contemplated buying a replacement laptop like the Dell XPS 13. But rumors keep popping up that a large device travel ban was imminent any day soon, and if that were to happen I’d lose 90% of the use case for a laptop, which was to process photos and write while traveling.  (In any case, the laptop ban has now been lifted, so you're now free to buy a laptop if you need one)

A much cheaper subsitute is a Wizo Ultra-Thin Folding Keyboard. The idea is that the keyboard would connect wirelessly to your phone, and then you could run say, the Microsoft Word mobile app (or Google Docs) for writing, and use whatever crappy smartphone app you liked for photo processing. (They all suck, except for Photo Mate R3, which sucks slightly less) I simply gave up on photo processing during the trip (except for the times when I shot pictures on the phone and processed them there).

The keyboard is surprisingly pleasant to use. While not nearly as nice as a full size keyboard, I found that in certain cases, I could out-type the phone’s ability to keep up with my input! The big compromises are the lack of number keys, which means you have to hold down the “fn” button when entering numbers, and the fact that  if you forget to turn off the keyboard after the job is done, your phone would stay paired and you might find yourself unable to type using an on-screen keyboard!
The keyboard’s extremely aggressive about re-pairing over bluetooth, even if you disconnected temporarily, your phone would repair the next second, so your only recourse is to turn off the keyboard physically via the power switch.

It’s small enough that the tiny tray in economy seats is roomy enough to stand the phone (using a phone stand) and still have plenty of room to type. I wrote several book reviews, and a travel entry, and of course this review of the keyboard itself on the keypad.

The keyboard does have an internal battery that requires charging, but one charge seems to last forever, so I have no complaints about the battery life so far.

All in all, this solves 50% of my travel use case that a laptop is for, so for the time being I’ve decided not to buy a laptop. Consider me a very satisfied customer, and I’d highly recommend this travel keyboard for your phone. Even after the trip, I would carry the keyboard with me whenever there’s a chance I might have time to write, so I don’t lose writing opportunities. Highly recommended.

Tuesday, August 15, 2017

Long Term Review: Wahoo Elemnt Bolt

On the cycling trip I used the Wahoo Elemnt Bolt exclusively for navigation. For Live Tracks (which was actually useful for AirBnB hosts who wanted to know how long it would take us to cycle to their place), I would continue to use the Garmin Vivoactive HR.

I used the Wahoo with RidewithGPS, Komoot, and the built-in Google navigation. None were perfect, and none would substitute for using your brain and ignoring the navigation cues on the display in front of you when appropriate. Unfortunately, it took me a few days to figure it out.

Ride with GPS was surprisingly good --- on a big screen. By default, it uses Google's bike route data's layer to help “snap” to a bike route while you're plotting the route. The problem is that the information is not sufficiently detailed: for instance, you can't tell whether the bike route you're on is a legitimate paved bike path, or whether it's a singletrack mountain bike trail requiring dismounts if you have panniers. The bigger issue is that the Android RideWithGPS app doesn't work at all for plotting routes, and if you plan to use it on a regular basis you need a bigger tablet in addition to just your phone.

Nevertheless, when plotting a route from Hindhead to Staines-Upon-Thames, it found the Basingstoke Canal trail, which none of the other options discovered. So the extra weight and charging hassle of a larger tablet might be worth it.

Komoots was what I used much of the time to do trip planning. The problem is that like Google Maps, it lacks common sense. A day after a rain, it routed us through muddy singletrack, including a flooded tunnel, and then later on in the day a sandy hiking trail through an area marked with “possible unexploded live ordnance, do not touch anything you see on the ground!” signs. We had to ask an equestrian how to extract ourselves from that nasty situation. Despite my being able to download all of the UK onto my phone, the app still refused to navigate or plot new routes without an internet connection.

The ELEMNT's app integration with Google Maps is suitable for short, city routing. It’s convenient and relatively good for within-city routing because of Google's somewhat comprehensive knowledge of local bike routes. But when given long distances, Google Maps would give you multiple routing options while the ELEMNT app's Google integration would only give you one option. Usually, Google's multiple-options usually mean that the slower choice is more scenic, less direct, and less traffic’d, so by not providing the multiple options the ELEMNT really limits the usefulness.

Once a route's on the Bolt, it's somewhat reasonable. In fact, it even displays the impending elevation change on the climbing screen, which is awesome for anticipating how long you have to pace yourself for on the next segment. The navigation is kinda crazy: sometimes it'll tell you to turn only after you've made the turn, so I kept it on the map screen whenever I needed the navigation.

The biggest issue with the ELEMNT Bolt is that it won't reroute if you go off course. When I first got the unit, I thought it was no big deal, but having lived with it, I think it's a major missing feature. There are many circumstances in which it'll be dangerous or difficult to stop and do a reroute, and of course, if your network connection is spotty, you're pretty much screwed. I think I'd be hard-pressed to recommend the ELEMNT for anyone who has to be off-network during part of the tour. I'd rather put up with a little worse navigation on the Garmin Edge type units.

It also has a weird bug in that when you fly between time zones, it doesn't auto-correct the time, unlike the Garmin units. You're forced to repair the device with the phone to fix the time. I didn't notice this when I flew to England, because the unit somehow failed to pair with my phone and I was forced to re-pair, but when I came back that didn't happen, and I lived with incorrect time on my Bolt until I sent a support e-mail and got back the answer. The reason this is bat-shit insane is that the GPS knows the correct time zone: it has to, since it knows where you are. That's why Garmin never needs you to set the time on your Edge units!

By the way, the Bolt randomly pairs or doesn't pair with your phone depending on the phase of the moon. There's no rhyme or reason to it. This would have been OK if like the Garmin it was capable of routing independent of the phone, but since it isn't, it causes an unacceptable startup time issue whenever we were raring to go on tour and I had to "oops, let me re pair the phone to the GPS unit." Again, no big deal for people who're just doing day-rides with bike clubs or century rides with well-marked roads, but a major pain for those of us who tour, and have impatient 5-year-olds in the back seat.

One thing that I found unacceptable was that the Wahoo Element Bolt  would occasionally refuse to upload to Strava or any of the other connected services. You can still upload manually by copying the files from the unit to Strava on the PC, but by Vivoactive HR has never refused to sync correctly. This appears to happen randomly as a result of say, not being pair'd with the phone whenever the device is turned off, but in reality even when I make a point of pairing the phone correctly each time, it will still occasionally happen. As a backup device for the Garmin Vivoactive HR this is somewhat acceptable (I usually turn off sync'ing to Strava anyway). As a primary device, I'd probably be selling it on eBay the first time it happened!

All in all, I'm somewhat satisfied with the ELEMNT Bolt. My biggest complaint is that the map screen is devoid of road names, which would be very useful when I'm actively ignoring the GPS directions. There's also no way to pan the map while riding. If Garmin does better integration with RidewithGPS or Komoots I'd give up the ELEMNT in a heartbeat, but until Garmin does that I think Wahoo has the edge for cycle touring in countries with dense road networks.