Compromise and Nexus 5: a review

I know a thing or two about com­pro­mise — I bought a Nexus 5 a few months ago. It’s not the phone I want, but it’ll do. For now.

It’s been years since I bought some­thing that wasn’t the lat­est and great­est Nexus mod­el, but this time I think it was the right call. Like oth­er Android fans, I await­ed the an­nounce­ment of the Nexus 6 with every bit as much ex­cite­ment as the en­tire world does when it’s new-iPhone-time. (Yes, this is a thing peo­ple ac­tu­al­ly do for Nexus de­vices.)

I found my­self ut­ter­ly un­der­whelmed by Nexus 6. Price, size, bor­ing, etc. But I knew I need­ed a new phone, so I im­me­di­ate­ly or­dered the fan-favorite Nexus 5.

Continue read­ing “Compromise and Nexus 5: a re­view”

Yes, that’s a new laptop. Yes, I know what year it is.

lenovo-thinkpad-x230-frontI know it’s 2013 and as far as “mo­bile com­put­ing” goes, I’m sup­posed to be pinch-zooming and app-buying and poorly-typing on a tablet like the cool kids. And I do — my  O.G. Nexus 7 (the 2012 mod­el) some­times makes a nice com­pan­ion1 to my Galaxy Nexus Android phone, by be­ing slight­ly faster and hav­ing a slight­ly bet­ter screen. However, over the 15 months I’ve owned the Nexus 7, it nev­er quite be­came the sec­ond mo­bile de­vice that I want­ed. Useful, yes… tran­scen­dent, no.

I knew some­thing was still miss­ing, so I re­cent­ly went and bought a small lap­top com­put­er, a Lenovo ThinkPad X230, to car­ry around. It runs Debian Linux. It does the things I want. It’s a won­der­ful thing to have.

I needed this because…

The lap­top that the ThinkPad re­placed was from 2007, and while a de­cent com­put­er from back then would like­ly still be good to­day, my old lap­top was not a de­cent com­put­er, even when new. Back then, I didn’t know just how painful­ly slow an ultra-low-voltage, low clock-speed CPU could be… I guess I thought it be­ing dual-core would some­how make up for it. Also, the cool­ing fan was a bit of a whin­er, and would con­stant­ly and very vo­cal­ly dis­agree with Linux’s style of pow­er man­age­ment. The darned thing would con­stant­ly sound like a mini-jet-engine — too ob­nox­ious to use around peo­ple I ac­tu­al­ly like.

Low on pow­er, high on noise — not a good com­bo.

But these days…

In the last half-decade or so, main­stream hu­mans seem to have ac­cept­ed the smart­phone, and seem to be do­ing the same for the id­iot cam­era (“tablets”). It’s the “Post-PC era,” or some­thing. Plenty of peo­ple seem to be do­ing okay with­out spend­ing much time on their general-purpose per­son­al com­put­ers, but over time I re­al­ized that as I tried to go along with this trend, I was miss­ing out. For me, a com­put­ing life cen­tered around mo­bile “smart” de­vices was one of un­ac­cept­able com­pro­mise. Composing more than a cou­ple of sen­tences with­out a key­board makes me want to just not both­er to write, de­vices with­out ex­pand­able stor­age make one de­pen­dent on rent-seeking “cloud” ser­vices, and the mo­bile app ecosys­tem has hand­fuls of well-known prob­lems (pri­va­cy, lock-in, and so on).

There’s a place for the­se de­vices, even in my life, but they just don’t re­place a general-purpose com­put­er. Ever.

So I did this…

I made sure not to make last time’s mis­takes when buy­ing this com­put­er. The i5 CPU is more than ad­e­quate, and I have a ton of RAM. ThinkPads are known to play nice­ly with Linux, be­cause they’re used by that awe­some kind of geek who fig­ures that shit out (and wouldn’t put up with a jet en­gine lap­top). It runs Debian Jessie (“test­ing”) with on­ly mi­nor an­noy­ances — not per­fect, but noth­ing I can’t han­dle.2

Hardware build-quality and dura­bil­i­ty are ma­jor plusses for an every­day car­ry ma­chine, and that’s what ThinkPads are known for. And of course, TrackPoint is tru­ly the best way to mouse. A lot has been said about the new ThinkPad key­boards, and while this one suf­fers from the bull­shit key lay­out (com­pare it to the awe­some, ug­ly 1337-geek clas­sic style), the key­board ac­tu­al­ly feel pret­ty nice to type on, even if the bizarrely-placed PrintScreen key oc­ca­sion­al­ly en­rages me.

And finally…

In the spir­it of bury­ing the lede, here are some things I in­tend to en­joy while tot­ing around this rock-solid, large-screen-and-real-keyboard de­vice:

  • Full desk­top OS that does all the things
  • Better web brows­ing; ap­prox­i­mate­ly 1,000 open tabs
  • Actually writ­ing things, blog­ging sil­ly ideas and such
  • Tons of lo­cal stor­age (SSD + HDD = yay!)
  • Semi-modern PC games, in­clud­ing lots of Humble Bundle good­ness
  • Codecademy
  • Interactive fic­tion, per­haps (now, where did I mis­place my pa­tience?)
  1. My most com­mon tablet us­es are as fol­lows: gam­ing, view­ing TV episodes and movies, and web brows­ing. I’m putting this in a foot­note so as not to side­track my­self, but it’s an im­por­tant point. One of the best things about hav­ing the tablet was that it gave me an­oth­er 16 GB of stor­age, on top of the 16 GB avail­able on my phone. A lot of peo­ple seem to think that Google in­ten­tion­al­ly lim­its the stor­age avail­able in their flag­ship de­vices to push peo­ple in­to us­ing their mon­e­ti­z­able “cloud” me­dia of­fer­ings in­stead of lo­cal stor­age. I wouldn’t be sur­prised if this were true, but hon­est­ly, the #1 rea­son I’d like more lo­cal stor­age in my de­vices is not to car­ry around more me­dia, but more and larg­er apps — some­thing you can’t put in the cloud.
  2. I imag­ine Debian Stable or Ubuntu would be bet­ter.

goatse mobile

I had a strange mo­ment of serendip­i­ty ear­lier this evening.

I was read­ing some RSS feeds and I saw there was a new post to the Flickr tag “first­goat­se.” (If the term goat­se is new to you, I’m not sure what to say ex­cept: don’t blame me when you look it up… now. The above link is safe to view, by the way.)

I felt like I hadn’t seen a ‘first­goat­se’ in a while, so I checked it out. The pho­to it­self was un­re­mark­able, but I was view­ing it on my Nexus S phone and hap­pened to glance away from the screen, at the phone it­self. Something clicked in my head, and I thought of a way to breathe new life in­to the age-old pas­time of show­ing your friends dis­gust­ing im­ages and cap­tur­ing their hor­ri­fied re­ac­tion for shar­ing on the Internet.

HOLY SHIT YOU GUYS WE ALL HAVE SMARTPHONES WITH FRONT-FACING CAMERAS!! (It must be the fu­ture!) These tiny pock­et de­vices are cor­nu­copi­as of giv­ing: lulz for us, lulz for the Internet, and hor­ri­fic, can-ever-forget mem­o­ries for our friends!

Basically, what the best app ever would do is dis­play a hor­ri­fic im­age of your choice… self-supplied of course, in case your poi­son is more tub­girl, or what­ev­er kids the­se days show oth­er kids the­se days. It would al­so cap­ture the re­ac­tion of the per­son hold­ing the phone via the front-facing cam­era, at the very mo­ment of ex­po­sure.

A se­ries of pho­tos lead­ing up to the mo­ment would work nice­ly too. Heck, what about cap­tur­ing a video of the en­tire re­ac­tion? For all I know, kids the­se days are show­ing each oth­er the video equiv­a­lent of that guy bend­ing over and… ugh. For bonus points, it might even com­bine the orig­i­nal and re­ac­tion videos in­to one, side-by-side, not that any­one would want to ever view that.

I’m ready to be­lieve that a mo­bile app like this al­ready ex­ists. It clear­ly, how­ev­er, can’t ex­ist for iPhone, be­cause Apple doesn’t al­low that brand of awe­some, and I can’t be both­ered to check the Android Market (aside from, okay, my quick search for “goat­se,” which turned up noth­ing), but this is clear­ly the kind of app that the wold to­day could use.

Well, there’s a Mac app, but who can fit that in their pock­et?

Hey world — some­body make this!

Nexus S review

Owing to its sta­tus as the cur­rent hot Android phone, the rep­u­ta­tion of and con­tin­u­ing sup­port for the Nexus One that came be­fore it, and the Nexus line’s no-crapware, pure Android na­ture, last mon­th I made a Samsung Nexus S my next mo­bile phone.

My pre­vi­ous phone, for ref­er­ence, was the first Android de­vice, a T-Mobile G1 (HTC Dream).

I like al­most every­thing about Nexus S. The de­vice is, for the most part, blaz­ing fast, smooth and com­plete­ly open.

By “open,” I mean:

  • It’s sold SIM-unlocked, mean­ing I can switch be­tween al­most any ser­vice provider. This isn’t very use­ful on a dai­ly ba­sis, but is a great op­tion to have for in­ter­na­tion­al trav­el.
  • Gaining root ac­cess to the phone is sim­ple. Rather than re­ly­ing on a se­cu­ri­ty hole to get root, Nexus de­vices have of­fi­cial sup­port for un­lock­ing the boot­load­er, which opens up the phone to what­ev­er you want to do, in­stalling what­ev­er you want, etc.
  • Even if you don’t root, the Nexus S — like all Android de­vices — is “open” in a very prac­ti­cal way: apps can be added to the­se de­vices from any source you as a user deem wor­thy. If Google doesn’t see fit to in­clude a given app in the Android Market for what­ev­er rea­son, the de­vel­op­er can provide an .apk file how­ev­er they like, and you as an adult can make up your own mind as to whether you want to use it.

Here are a few things I like:

  • It’s fast. There’s al­most nev­er a hic­cup in run­ning apps, switch­ing be­tween them, hav­ing calls and mes­sages come in when you’re do­ing some­thing else, etc.
  • Front-facing cam­eras may be stan­dard the­se days, but I love fi­nal­ly hav­ing one in my phone. Just need video sup­port in the Skype app…
  • The screen is amaz­ing. It’s bright, high-resolution, and the glass is ac­tu­al­ly curved, which lets it sit face-down on a ta­ble with­out scratch­ing, fit the cur­va­ture of your face, and as some have sug­gest­ed, there are er­gonom­ic ben­e­fits for your thumb as well.
  • I don’t know the specs, but the bat­tery life with ac­tive use seems way bet­ter than my G1.
  • Lots of on­board stor­age. 16 GB may not be enough for some peo­ple, but it is for me, and I prefer this over deal­ing with a slow, un­re­li­able mi­croSD card.
  • Small touch­es like the afore­men­tioned curved glass, head sen­sor that dis­ables the screen dur­ing a call, am­bi­ent light sen­sor for au­to­mat­i­cal­ly ad­just­ing screen bright­ness make for a nice ex­pe­ri­ence.

Here are a few things I don’t:

  • The browser some­times lags a bit while scrolling web­pages with mul­ti­ple large im­ages. I don’t see a lot of this, so it’s not that an­noy­ing.
  • No 4G. Of course, T-Mobile doesn’t have “true” 4G ser­vice, and 3G speeds are enough for web brows­ing… and al­most every­thing else I usu­al­ly want to do. Where this has been a prob­lem for me is in stream­ing high-quality mu­sic us­ing the Last.fm app; the play­back very of­ten catch­es up to the load­ing. That said, I feel like Last.fm may be part­ly at fault too, as the app seems un­re­li­able in oth­er ways that make me doubt it.
  • In-browser Flash per­for­mance sucks, but I’ll take it over none at all so long as Flash el­e­ments can be off by de­fault and load­ed on­ly on-demand (and they can).
  • I get an­noy­ing au­dio in­ter­fer­ence in the car when the phone is plugged to the au­dio while al­so charg­ing. Not sure if this is the phone’s fault, as it doesn’t hap­pen in the house.
  • Doesn’t shoot HD video, but in­stead, widescreen VGA… sim­i­lar to my Canon PowerShot from six years ago. I can’t fig­ure out who thought this was a good idea. I don’t do much video, so it’s not a deal-breaker, but an an­noy­ance. I’d love to see them fix this with a soft­ware up­date, which should be pos­si­ble given the beefy hard­ware in this thing.

The lack of key­board wor­ries me:

  • While the av­er­age per­son prob­a­bly has to oc­ca­sion­al­ly en­ter a sim­ple pass­word and a poor­ly thought-out sta­tus up­date, I’m a writer and a geek (did you guess?), so ac­cu­ra­cy of text en­try is im­por­tant to me. Typing on-screen kind of both­ers me.
  • I hate the lack of con­trol when com­pos­ing text, even if auto-correct takes care of most of the in­ac­cu­ra­cies. It al­so cor­rects my in­ten­tion­al mis­spellings, col­lo­qui­alisms, “big words” and many prop­er nouns. The thing to do here is ob­vi­ous­ly make sure it says what I want be­fore click­ing “Send,” but that’s not al­ways easy.
  • Like I said, I’m al­so a geek. Who the fuck us­es com­mand lines the­se days? I the fuck do. I man­age a Linux server at work, and very of­ten re­mote­ly con­nect to the com­put­ers at home to do things through­out the day. Not on­ly is typ­ing awk­ward, but oth­er things don’t work, like double-tabbing key for com­plet­ing com­mands and file­names.
  • On the plus side, on-screen op­tions like Swype and SwiftKey, and Google’s pret­ty good voice in­put makes this hurt a lit­tle less. Still, I’d to­tal­ly go for an iden­ti­cal phone with a key­board, even if it was a bit thick­er and heav­ier.

But I’m op­ti­mistic about the fu­ture of my phone:

  • As a Nexus phone, its up­dates are man­aged by Google, so there isn’t any wait­ing for Samsung and T-Mobile to get their act to­geth­er and re­lease up­dates to fu­ture ver­sions of Android.
  • Its open-phone sta­tus should make it ap­peal­ing to third-party de­vel­op­ers like Cyanogen, who will hope­ful­ly con­tin­ue sup­port­ing it in­to the fu­ture.
  • While I’m a lit­tle con­cerned about buy­ing a new phone now, given the up­com­ing wave of Android phones with dual-core CPUs (Tegra II and oth­ers), I’m not sure that my phone be­ing left “in the dust” will be a con­cern for the next cou­ple of years. After all, desk­top de­vel­op­ers haven’t ex­act­ly made great use of multi-core CPUs, which have been wide­ly avail­able there for at least five years now. They’re still good to have for mul­ti­task­ing, which is a nice fea­ture to have your mo­bile OS sup­port, but the sort of mul­ti­task­ing we ex­pect out of our phones doesn’t usu­al­ly in­volve two CPU-intensive tasks, but rather one that chugs along per­form­ing some me­nial task (play­ing mu­sic, rout­ing GPS, etc.) while an­oth­er in the fore­ground does what you want it to at the mo­ment.

In all, I think Nexus S makes a pret­ty good G1 re­place­ment, and will serve me well in­to the fu­ture. I’ll keep you post­ed, uh, Internet.

QR Codes: great, but then what?

I keep a long and ever-growing out­line of blog top­ics I may some­day write about. Most aren’t ful­ly formed, but each at least on­ce struck me as in­ter­est­ing at some point or an­oth­er, so I fig­ured they’re worth keep­ing around.1 (See one re­al ex­am­ple to right.)

  • <3 qr-codes
    • bridges the phys­i­cal and the cy­ber
    • low-tech, lowest-common de­nom­i­na­tor
    • cam­er­a­phones in every pock­et
    • makes a lot more sense than com­pet­ing tech­nolo­gies, like that mi­crosoft one with the dif­fer­ent col­ors that re­quires col­or print­ing, etc. this one I could, if so in­clined, draw with a pen­cil
    • sad­ly, most of what I use this tech­nol­ogy for is cu­ri­ous­ly decod­ing bar­codes I come across on the web

I add top­ics to my list pret­ty reg­u­lar­ly, but what doesn’t hap­pen very reg­u­lar­ly is some­one read­ing my mind and writ­ing my post for me. Okay, it’s on­ly hap­pened on­ce: about a week ago, and it was geek­ing out on QR Codes.

I’m a bit be­hind on my RSS read­ing, but when I just came across this bo­ing­bo­ing post, I was quite pleased. In it, guest blog­ger Glenn Fleishman pret­ty much lays out the case for 2D bar­codes — QR be­ing the most pop­u­lar, good/open-enough for­mat — as a use­ful sort of link be­tween the phys­i­cal world and the dig­i­tal one. It’s an idea I hap­pen to have loved for a few years now, and with Internet-enabled cam­er­a­phones all over the place, one that has the po­ten­tial2 to cre­ate some ben­e­fit to so­ci­ety on a large scale.

It should come as lit­tle sur­prise, then, that for as long as I’ve been aware of the­se codes, I’ve longed to find a use for the tech­nol­o­gy aside from the mun­dane let peo­ple scan your ad to go to your web­site, or send a URL from your com­put­er to your phone. A hand­ful of bo­ing­bo­ing com­menters point­ed out a few real-world ex­am­ples of ways they have used QR codes: la­bel­ing shared lab equip­ment or get­ting on the VIP list at Tokyo clubs. Interesting they are; world-changing they’re not.

Of course, there’s al­so the idea of pro­vid­ing richer in­for­ma­tion about wine than a sim­ple bot­tle la­bel could dis­play, which I find a step above the oth­ers, and giv­ing ex­tra con­text to mu­se­um art, which I think gets us even closer.

Yet I still think QR Codes have even greater po­ten­tial… but po­ten­tial isn’t even half the bat­tle.

  1. Yes, they’re ba­si­cal­ly brain crack.
  2. Naturally, the bar­ri­er to adop­tion is con­vinc­ing the av­er­age per­son to both­er solv­ing for them­selves a prob­lem — easy URL/text/contact en­try on their phone — they didn’t re­al­ize they had.

Why doesn’t my phone have a thermometer?

It’s get­ting pret­ty warm again (did it ever stop?) in South Florida, so to­day when I had the mis­for­tune of be­ing out­doors, I got to won­der­ing why with all the sen­sors found in most mod­ern smart­phones, they don’t usu­al­ly in­clude a ther­mome­ter.

It’s com­mon to find sen­sors for ori­en­ta­tion, screen contact/pressure, video, sound and even lo­ca­tion. However, for some rea­son, the task of telling me about the cli­mate sur­round­ing me gets out­sourced to a third-party that is some­where com­plete­ly dif­fer­ent.

Just think about that for a sec­ond.

What we’re miss­ing is the abil­i­ty to know the ac­tu­al con­di­tions we’re ex­pe­ri­enc­ing. If one hap­pens to be in­doors, in the shade, or some­where else en­tire­ly, all they’ll get from their phone is the typ­i­cal out­door tem­per­a­ture for their gen­er­al area. Even if they hap­pen to be in­side of, and get re­cep­tion in, a walk-in freez­er. (“It’s cer­tain­ly not 90° F in here…”)

On the oth­er hand, I can think of rea­sons why our phones tend not to han­dle their own tem­per­a­ture read­ings. Wireless car­ri­ers ob­vi­ous­ly prefer that cus­tomers pay for data plans to use as many phone fea­tures as pos­si­ble. There’s al­so the mat­ter of ex­pec­ta­tions: no­body (but me!) seems to de­mand the fea­ture, so why in­clude it, even if the hard­ware couldn’t be all that pricey?

But most im­por­tant­ly, the sen­sor would like­ly be un­du­ly in­flu­enced by the tem­per­a­ture of our hand, the at­mos­pher­ic con­di­tions in our pock­et, the heat gen­er­at­ed by the phone it­self, and so on. Heck, I dis­tinct­ly re­mem­ber how wild­ly in­ac­cu­rate my circa-mid-90s Casio G-Shock ther­mome­ter watch (same mod­el pic­tured at right) was.

But gosh, was it ever en­ter­tain­ing to watch that di­al spin! I al­so used to watch that bar graph scroll through the last few hours of record­ed tem­per­a­tures and pre­tend I was in a boat watch­ing waves go by. Ah, child­hood…

I can’t quite place my fin­ger on what I would do with the abil­i­ty to keep a read­ing of my own sur­round­ings’ tem­per­a­ture over time… but I know I want it.

I basically have the mobile phone I want, and that is awesome

I just re­al­ized that I, ba­si­cal­ly, have the mo­bile phone I want. I use a T-Mobile G1 (HTC Dream), root­ed, SIM-unlocked, and run­ning the great CyanogenMOD.

I could not re­al­ly say this about my pre­vi­ous phone, a Palm OS Treo…

My G1, in its rooted gloryI just re­al­ized that I, ba­si­cal­ly, have the mo­bile phone I want. I use a T-Mobile G1 (HTC Dream), root­ed, SIM-unlocked, and run­ning the great CyanogenMOD.

I could not re­al­ly say this about my pre­vi­ous phone, a Palm OS Treo. Though it had its strengths (read: the or­ga­niz­er fea­tures), I bought it pret­ty much right be­fore the first iPhone was an­nounced, which, for bet­ter or worse, re­de­fined what a smart­phone would be.1

My affin­i­ty for the G1 re-occurred to me as I opened the Terminal app to check some­thing. I slid the screen open with a sat­is­fy­ing click, typed su and checked that some­thing. I want­ed to go back a bit through my shell’s com­mand his­to­ry, and a quick flip of the track­ball made easy work of that.

Sure, I have my gripes… it’s a lit­tle slug­gish some­times, com­plete­ly short on app stor­age space (root­ing fixed that) and takes the crap­pi­est videos I’ve ever seen (worse than my circa-2001 Nikon CoolPix). And now that new­er Android de­vices are out, I com­plete­ly have 1 GHz CPU-envy, high-res screen-envy, and Android 2.1-envy (Google Earth, want!).

But for the fore­see­able fu­ture, my G1 and I are cool. Its form fac­tor is per­fect. Its phys­i­cal key­board is un­matched by new­er de­vices with cramped lay­outs. It’s clear­ly no svel­te iPhone, but it’s not too chunky ei­ther.

My sat­is­fac­tion is matched on­ly by my an­tic­i­pa­tion for what­ev­er could ma­te­ri­al­ize in the fu­ture and top this. Bring it, fu­ture!

  1. By this, I most­ly mean “have a re­al web browser,” not “have no na­tive app sup­port and a charis­mat­ic CEO try to con­vince you that you don’t re­al­ly want apps on your smart­phone, any­way.”