Friday afternoon my phone finally got the OTA update for Android 5.1. After several hours stuck on the swirling boot animation, I decided it was time to admit that the phone wasn’t going to finish booting on its own.

I tried everything: Pulling the battery. Clearing the cache from recovery mode. Removing the SD card. Even a factory reset. I’d tried to avoid that, but eventually decided all the important stuff was backed up, and dammit, I needed a phone for the weekend!

If it had been a carrier phone or an actual Nexus device, I could have flashed a fresh system image, but it’s a Samsung Galaxy S4 Google Play Edition. Nobody wants the responsibility of supporting it.

In the end I bit the bullet and installed CyanogenMod. Even if I messed it up, the phone was already unusable and long past any warranty it might have had two and a half years ago. I didn’t really have anything to lose.

I had to read through the instructions a couple of times, but the process was actually pretty simple since I already had the ADB tools and could install Heimdall on my Linux desktop through Fedora.

  1. Flash a more capable recovery partition.
  2. Upload the right CyanogenMod .zip and the corresponding Google Apps .zip.
  3. Install the images from the recovery partition.
  4. Sign in to Cyanogen and Google.
  5. Reinstall apps.

It’s a bit weird because the UI feels like I’ve gone back in time a couple of years.

But the phone works again, and I was able to do it overnight. I didn’t have to spend three days emailing tech support back and forth. I didn’t have to go into a store on Saturday and be told I can either buy a new phone or wait a week while they send it in for repairs.

I may still end up replacing it in the near future — it is 2 1/2 years old, after all — but I don’t have to, which makes a big difference!

Update!

The phone worked great for camera, navigation, texting, and everything else I wanted to use it for at an event Saturday and at Long Beach Comic Con on Sunday.

Unfortunately, the dial pad doesn’t always respond during calls, which makes phone menus unusable. It’s not just the problem with the proximity sensor thinking my face is next to the phone and blanking the screen — I’ve had that on the official firmware for ages. I can get the keypad to display, but it won’t react to touch.

My carrier has an app for voicemail, but I’ll have to do something to be able to deal with other phone menus.

Nexus 7

The Nexus 7 Android tablet has been discontinued in favor of the Nexus 9. (via Slashdot.) I’ve had a Nexus 7 (2012) almost since the beginning, and while it’s showing its age, I’ve been trying to stretch out its lifetime, because I actually do still use it on a regular basis.

Most of what I do these days with it is reading. Email. Books. Comics. Feedly. Pocket. Some photo management and searching. My four-year-old plays games, most of which run fine once they’re up but they take forever to load. I’ve also started introducing him to photo editing apps like Pixlr and Aviary. I used to do more typing and web browsing on it, but it’s just gotten so slow that it’s actually faster to pull out my phone or go over to a computer. Katie doesn’t use it much at all because she has a Note, which is almost into tablet territory already. (She’s not alone. Since the iPhone 6S came out, Pocket has noticed that people with both tablets and phones use their tablets a lot less often if their phones are larger.)

But the 7″ tablet form factor is perfect to keep with you at the breakfast or lunch table, or kick back on the couch.

The thing to remember about the Nexus 7 is that the original release was a proof of concept. There were android tablets before, but the market was still considered something of a joke compared to the iPad, and Google wanted to prove that (a) there was a market for a good Android tablet, and (b) there was a market for a tablet larger than a phone and smaller than an iPad. The iPad Mini didn’t exist at the time, and Apple was still ridiculing the concept.

It succeeded. But they made some mistakes with the hardware that were corrected in the 2013 model. Unfortunately those mistakes have made the first edition notorious for slowing down.

Mine was getting close to unusable around the time Lollipop was released, and upgrading finished the job. Fortunately wiping it and doing a fresh install cleared up a lot of the problems, though as I’ve added more apps, it’s continued to slow down. Chrome is too slow to use, and while Firefox is a little faster, I basically can’t surf the web on the tablet anymore.

But for a core set of apps, it’s still useful. I’ll read/reply to email and skim Feedly in the morning at breakfast, saving items to Pocket to read later. Then at lunch I may read a book or catch up on those saved articles. Since Gmail and Pocket both work offline and sync in the background, I can still use them in places without WiFi. Mobile data would be nice, but offline+sync makes it less critical, and I’ve saved a few hundred over the last three years by not having an extra data plan.

I am going to have to replace it soon, but I can’t decide what with. I don’t want the larger size that the Nexus line is moving toward, and while I’ve been looking at Samsung’s Galaxy tablets, the models I’ve tried all feel a little too small or a bit too big. I don’t want a 10″ tablet, and I don’t want a giant phone. I want a device that’s just big enough to read a full comic book page on it, but still small enough that it feels like a paperback book.

Note: I didn’t actually post this when I wrote it. I’ve backdated it to the original date because it’s no longer timely, but I wanted it online so I could link to it.

In cleaning up dead links, I stumbled on an old post about linkrot in which I wondered “how much of what exists today will still be around – in any form – ten years from now.”

Well, it’s been ten years. That post had seven external links. Four of those are no longer active, though I was able to find three of them on archive.org. (The fourth was a link to a search result set on AltaVista. Yes, AltaVista.)

That’s right: More than half of the links on an article about linkrot have rotted away. Appropriate, that. And a reminder to always provide some context when linking out to something that you can’t personally ensure will stay online.

Fifth generation iPodAs I moved our iTunes library last week, I worried that the new system might not be able to sync with the old iPod, but relaxed when I saw that Apple still sold the click-wheel iPod Classic. They discontinued it a few days later, but fortunately we were able to sync the old devices.

Why do I prefer the older iPods with physical buttons and tiny screens?

Because I listen to music in the car, and a touch screen is a terrible interface for quick actions while driving.

While touch screens are better for menus, searches, finding albums, playlists, artists, and just about anything else, they’re actually dangerous for driving. A physical control of some sort is best for any action you might have to take while behind the wheel of a moving car.

Pause/Play, Skip and Volume. Those are the key things you want to be able to do with music without thinking too much about where you’re reaching, or taking your eyes off the road. (Especially if you have a mix of quiet and loud songs.) Volume’s on the dashboard, but it’s so much easier — and safer — to hit an actual button for pause/play or skip than to jab at the touch screen until you get it right.

Every time someone announces a smart watch (today it’s the Apple Watch), people trot out the idea that the wristwatch is obsolete because look, I already have a smartphone with a clock on it. But phones don’t completely replace wristwatches. They completely replace pocket watches.

pocket watch photo
Why do I need a wristwatch? I have a clock in my pocket!
Photo by France1978 (CC)

The wristwatch thoroughly replaced the pocket watch for most of the twentieth century because it’s so much more convenient. You don’t have to pull it out of your pocket to look at it. You don’t have to worry about dropping it. You don’t even need free hands to check the time.

The only reason we went back to pocket watches is that the new ones can do so much more than the old ones did. That and so many of us are spending so much time sitting in front of a glowing rectangle with a clock in the corner. (Note to fellow geeks: not everyone does this, so don’t generalize your experience.) As with cameras, music players, and portable game systems, we abandoned a specialized device in favor of a multitasker that wasn’t quite as good at the job. The difference is that with the wrist watch, its advantage wasn’t something that newer technology could catch up on. It was the form factor.

Smartwatches, in concept, are not a step backward, even if this generation’s specs leave something to be desired (and I’m not just talking about enabling the wearer to “start and stop the flow of time”). They’re a step sideways to a different use case. It’ll take time (no pun intended) and experimentation by real-world users to shake out what it’s best suited for.

SDCC Crowd with TVs

Social media has drastically changed the online aspect of Comic-Con. So much is up instantly that you can follow the event live without setting foot in San Diego. But for those of us who are on-site, there’s a trade-off between being part of the conversation and part of the convention.

Because we can post in real time, people want to follow in real time too, and lose interest quickly afterward. No matter how interesting I think my follow-up articles might be, none of them are read anywhere near as much as the half-assed pieces that go up during or right after the con. Even interest in photos drops off steeply as soon as the event is done:

Flickr SDCC traffic graph

But it takes time to write and edit, to curate, crop and adjust, and (dare I say it) to promote — and if it’s not your job, it comes at the expense of other things you could do at the con.

There’s Far Too Much To Take In Here

I’ve been posting my con experiences and photos for over a decade now. At first I’d just post when I had time. Once I had a smartphone, Twitter, and a second blog at Speed Force, I was live-tweeting and live-blogging everything.

Then in 2011, my wife and I left our then-infant son with relatives and spent a single day immersed in the pop culture madness. It gave us a new perspective:

  • Comic-Con is gigantic.
  • Your time at Comic-Con is limited.
  • Make the most of it!

I changed the way I approached the convention. No more liveblogging; other people are doing that for their job. No presentations that will just be online by the end of the day anyway. No three-hour lines. I wanted the experience I could only get by being there.

I also cut my social media activity to a minimum:

  • Instagram when I had a minute or two of downtime, set to auto-share pictures out to Facebook, Tumblr, etc.
  • Twitter rarely, again when I had a little downtime. No more stopping in the hall to post a comment. This year I didn’t even check for conversations (which, it turns out, I should have).

Sure, I’m a little disappointed that my SDCC 2014 writeup hasn’t been read by very many people, but it’s partly to help me remember this year’s con when I look back at it later. Our photo album at least got some attention. But you know what? If I’d taken the time to write about it during the con, whether live or nightly, I wouldn’t have had as much to write about, and I wouldn’t have enjoyed it as much. I think that’s a good trade-off.

P.S. Apologies for the clickbait headline. It seemed appropriate for the subject matter.

You’ve probably seen the story about how a group of teenagers showed that plants won’t grow next to a WiFi router. We did our own experiment, but first some things to consider about the story making the rounds:

  • They tested whether cress seeds would germinate near a wi-fi router.
  • The seeds by the router DID grow, just not as well as the control group.
  • The photos accompanying the news articles I saw don’t match the photos that appear in the report. They actually look like a before and after set.
  • It was done a year ago, in spring 2013.
  • It was a school science project. That’s not a knock, they did some good things like sending traffic through the router to make sure it was actually transmitting, and mixing seeds from multiple packets together to eliminate differences between batches.
  • As with all science, the results need to be repeated in more experiments with rigorous controls to be sure they accounted for all variables.
  • I couldn’t find a followup study in all the blind repostings of the original OMGWIFI claims, though I did find a discussion at JREF. If you can read past the annoyingly dismissive comments, you’ll also find some insightful remarks and links to the actual presentation (in Danish, so it’s tricky to read, but they have charts and photos)…and a few anecdotal stories by people who use the heat from their wireless routers to HELP germinate seeds!

After we read up on this, Katie decided to do a simple experiment herself. She put seeds next to our router, on top of our refrigerator, next to the TV, and for a control, outside. She found that the seeds placed next to our router did just fine — considerably better than those left outside, and slightly better than those placed elsewhere around the house.

Each bag contained one kidney bean, one black-eyed pea, and one seed from the red bell pepper I cut up for dinner. I put a section of select-a-size paper towel, folded twice, in each and set the seeds inside the second fold. Each bag got 15 mL of Brita filtered water and the air was squeezed out before sealing. Then I left them around the apartment for several days to see if they’d sprout. This is a picture of what resulted.

I wonder if the seeds in the school experiment just dried out. Katie sealed her seeds in plastic bags, which allowed radiation to pass through, but trapped moisture. As I understand it, the students watered their seeds throughout the experiment, but it’s possible the trays dried out overnight. Comparing moisture content/retention would be an interesting follow-up.

Obviously, this isn’t any more rigorous than the original experiment. But it shows that the results they found are the beginning of the process, not the last word. More importantly, it’s something you can easily test yourself if you’re so inclined. Next time you see a startling claim that’s something you can test without too much trouble, try checking it out for yourself.

Incidentally: We planted the seeds in our patio yesterday. With any luck, they’ll do as well as our tomatoes (and better than our poor carrots) this year!

»All pages site-wide with this tag