The kid has been watching a zillion teardown/repair/dismantling videos of various devices on YouTube, and wants to learn to repair phones.

So I took the old phones and tablet that I’d set aside for e-waste collection, and the tools I used to do battery replacements on a couple of devices a while back, and let him at them.

He disassembled and reassembled the dead Nexus 5x that got stuck bootlooping two years ago. Plugged it in. Waited.

It actually powered on enough for us to get it into recovery mode!

Unfortunately I should have left it in fastboot mode, because now that I’ve downloaded an image to install, I can’t get it to power up again at all.

It’s weird to look back on all the posts I made agonizing about whether or not to buy a netbook.

It was never anything I would have used on a regular basis, and I knew that (which is why I never went through with buying one). It would have been something I used on trips, mainly conventions, and only to overcome the shortcomings of late 2000s smartphones.

Mainly: photos and typing.

Photo by VIA Gallery from Hsintien, Taiwan - HP 2133 Mini-Note PC (front view compare with pencil) uploaded by Kozuch, CC BY 2.0
Photo by VIA Gallery from Hsintien, Taiwan – HP 2133 Mini-Note PC (front view compare with pencil) uploaded by Kozuch, CC BY 2.0
Back then, I always carried another camera to get the “good” pictures, because phone cameras were still crappy. So if I wanted to post something online, I had to get it off the camera, onto a computer, and then upload it. Today’s smartphone cameras and apps are so much more capable that they mostly solve the photo issues.

It’s still painfully slow to type anything of length on a phone, but tablets have emerged since then and are a lot easier to type on. Hybrids like the Surface Pro and add-on keyboards make it even easier.

Touchscreens have solved the crappy trackpad problem netbooks had.

Faster phones and cell networks, and a more mobile-friendly web, have made a lot more things possible directly on the phone.

Netbooks, meanwhile, are pretty much forgotten, at least in the form they existed in at the time. Chromebooks are doing OK, at least in schools, but they aren’t quite the same thing. You’d think “netbook” would refer to something more like the network-dependent Chromebook, but it typically referred to the tiny form factor of a mini-laptop.

Looking back at the Tori Amos signing that I mentioned in the series’ first post: These days I probably would have taken the pictures directly on my phone and posted to Instagram within minutes. As for the blogging, I might have powered through on the phone and added the pictures directly, or I might have done so on the tablet and added the pictures that would already have synced from the phone over WiFi.

I wouldn’t carry a laptop of any size around the convention floor, that’s for sure. And I probably wouldn’t bring one on a short trip at all unless I was planning on working during the evenings.

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.

I was reading up on wearable computing today, and with the SDCC badge presale looming, I found myself wondering whether a smart watch would be useful for Comic-Con.  (No plans to actually buy one, I’m just thinking.) I don’t normally wear a watch these days, but it does get annoying to have to reach into my pocket when I want to check the time. For this reason, I make a point to wear a watch at conventions so that I can see the time at a glance and avoid missing events or meetup times.

So, keeping in mind that the current generation of smart watches (Pebble, Galaxy Gear, etc.) mostly pair up with a phone to do the heavy lifting…what might a smartwatch do better for a con than a phone (or a regular watch)?

1. Messages. Between the noise and the walking, it’s already too easy to miss calls or even texts when you’re out on the floor of the convention. It’s easier to notice a buzz on your wrist than a buzz in your pocket, and less intrusive to glance at your wrist to see if it’s something urgent when you’re interacting with people in the real world. You can also tell instantly when you’re crowd-weaving to meet someone whether that text they just sent is “I’m here,” “Running late,” or “Change of plans, meet me at Hall G lobby.”

2. Schedule reminders. Put the event, time, and room number on the screen. How to make it more awesome: pull down the floorplan and use your location to calculate how long it’ll take to get there, and notify you far enough ahead of time that you can make it, Google Now-style. This is more useful for smaller conventions or at least smaller panels at SDCC, since the big ones require you to line up way ahead of time anyway.

3. Wi-Fi hotspot detector. Even if the watch doesn’t support wi-fi, your phone does, and it can ping the watch to let you know.

4. Breaking news alerts. Ironically, I feel like I miss more news when I’m at Comic-Con than when I’m following along from home. This would have to be very well filtered in order to be useful without pulling you out of actually experiencing the convention.

A step counter would be interesting, but I can probably find an app for my phone.

I doubt I’d use a wrist-mounted camera like the one on Samsung’s Galaxy Gear much. Google Glass would be more practical for the blink-and-you’ll miss-it moments, and if you have time to compose a shot, you have time to pull out a phone or dedicated camera. OTOH, a wrist camera is probably a little less creepy than Glass. (On the gripping hand, maybe not.)

Of course the absolute best use of a smartphone at Comic-Con:

5. Get one that can actually handle calls, and wear it with a Dick Tracy costume.

What uses can you think of?

I’ve been reading a Slashdot thread where people who don’t and won’t use tablets argue over why they don’t count as personal computers, because they supposedly aren’t useful for anything except consuming media (not that they’ve tried, I imagine, except maybe the 2 minutes they tried typing on an iPad that one time in Frys or Best Buy and didn’t allow themselves time to get used to the onscreen keyboard), and therefore can’t possibly have any valid use case. (And besides, if we admit that a tablet is a computer, then Apple wins!)

You can certainly make a distinction based on form factor. You can maybe make a distinction based on OS, but then you have to define what makes a PC operating system and what makes a tablet/smartphone/whatever operating system, and things are going to get blurry when you look at, say, Windows 8.

You can sort of make a distinction based on whether you can develop and install your own software, but even that isn’t hard and fast. You can write code in an editor. Compiling is a matter of whether a compiler is available, not something intrinsic to the device itself. Installing software from outside the walled garden is easy on Android, not so much on iOS. (Incidentally, this is the main reason I’ve chosen Android over iOS.) Both have large software ecosystems that developers can contribute to and the average user can install from, which is what actually matters to the average user. (The funny thing is, I remember plenty of arguments about how hard it is to install third-party software on Linux where the counter-argument was that with apt-get, you mostly don’t need to.)

But a lot of Slashdotters are spouting gems on the order of “It doesn’t have a keyboard!” OK, neither does your desktop until you plug one in. Which you can do with a lot of tablets. Or “It doesn’t have a mouse!” – Really? Are you serious? They’ve merged a trackpad with a screen. “I can’t upgrade the parts!” Well, that rules out a lot of consumer-focused desktops, doesn’t it? “PCs have applications, tablets have apps.” – Is there really any meaningful distinction between the two terms?

Pair a Bluetooth keyboard and mouse with your tablet. Hook it up to an external monitor. Or don’t, since the typical tablet already has a better screen than an SE/30. Now you’ve got a workstation, with no more hardware than you would have hooked up to your desktop box. Install an office suite, an image editor, a coding editor — heck, a tax program. At this point the key difference in what’s useful is which applications are available. Wow, I’m having a flashback to all those old Windows vs. Mac vs. Linux arguments.

And yet people insist that these devices are “only toys.”

I still can’t get over the fact that a tech discussion site like Slashdot is so full of neophobes…but then they’ve always been. Look back at the “who would want a touch screen?” debates from a few years ago, or the “wow, this iPod thing is lame” initial reviews.

There’s a bubble a lot of geeks live in where they don’t think about other people’s use cases or workflows. That touch screen debate was full of talk about arm strain from vertical monitors, not considering horizontal or handheld screens, and not considering touch as a complement to keyboard & mouse. (My two-year old wants to touch the screen on the desktop and laptop, and I keep having to explain that they don’t work that way.) There are people out there who consider GUIs to be useful only for opening multiple terminals. And let’s not even get started on the decisions driving Gnome 3, eliminating things like files on the desktop or the minimize button because who uses those?

I learned my lesson when the iMac came out and I thought it was ridiculous. Who would want such a limited computer? As it turned out, lots of people…because they wanted and needed different things from a computer than I did.

So these days, when I see a piece of technology I can’t fathom the use for, I try not to rant about how useless it is. Instead, I wait and see what other people come up with. Sometimes it really is useless (though even the CueCat found a second life as a scanner for LibraryThing), but sometimes the failure isn’t in the technology, but in my own imagination.

»All pages site-wide with this tag