New phone: Google Nexus 5, first impressions

Over the years I’ve tried to avoid being sucked into buying the latest and greatest technology just for the sake of it.

But I must admit being keen to check out the new Android 4.4 (Kit Kat) and Google Nexus 5 phone.

What would I need a new phone for? I could put Kit Kat on my old phone!

I've got Kit Kat on my phone

Seriously though, I’d upgraded my old HTC Desire S to Android 4.0, and while it works, it’s noticeably slower. I was thinking I’d downgrade it back to 2.3 (the ROMs for HTC phones, for both 2.3 and 4.0 are available here), but given I’ve had it a couple of years, what about a new phone?

Having seen Tony’s Nexus 4, over the past few weeks I found myself salivating for the about-to-be-released Nexus 5. It was finally officially announced and released on the 1st of November.

I was pondering this when my tax return came back, and would easily cover buying one. The Nexus 5 is cheap for a flagship phone — much cheaper than an iPhone. The 16 Gb model is A$399, the 32 Gb is A$449. You can’t upgrade the storage in it via an SD card, so choose wisely. Obviously a lot of people went for the 32 Gb, as it sold out quickly on the first day.

Fortunately a bloke I know accidentally bought two 32 Gb models in black — my preferred colour — he’d been desperately clicking through trying to make sure he got one before it sold out, and wasn’t sure his order had been accepted, so kept clicking.

On last Wednesday I met him at Southern Cross Station to exchange cash for a box with the phone in it, like an extremely geeky version of a drug deal.

I’m not going to bother doing a comprehensive review of the phone — that’s better handled by the professionals. But here’s a few notes on it, which I’ll keep expanding as I go.

Google Nexus 5 phone

First impressions

It’s a bit bigger than the Desire S. Wonder if it’ll fit in my front jeans pocket, which is where I tend to put my phone if I’m sitting down and have no other pocket.

Lovely bright high-resolution display.

The on/off button is on the right hand side, rather than the top as I’m used to, but I’ll adjust. Oddly it feels just a teensy bit loose. Hopefully that won’t be a problem in the future.

I’m thinking I might get a case, or at least a bumper, for it. It looks sturdy enough, but some protection might be good.

Setup

The old phone had a mini-SIM. The Nexus 5 takes a micro-SIM. I sidled into a Telstra shop to get it sorted out, and they used a cutting tool to chop it down. Low-tech, but effective.

Android to Android is pretty easy, because all the contacts and so on are kept “in the cloud” as part of your Google Account.

Text messages, pictures etc weren’t brought across. I copied all the pictures and voice recordings manually off the old phone for archiving on my PC at home.

Text messages were easily saved off the old phone using the freeware SMS Backup & Restore. It saves all the messages into an XML document, making it human-readable if I don’t want to import them into the new phone… which I don’t, especially.

Once the new phone was running, it was easy to go into the Play Store and re-install wanted apps onto it. So far I haven’t seen anything I had on the old phone that was labelled as incompatible with the new one, though I haven’t re-installed absolutely everything — I’m being a little more discerning.

Likes

Very fast. Good to see.

Display is very nice.

I like the effect when the screen turns off. Looks like an old-style television shutting down.

Camera quality in general looks good, though the old phone was able to adjust the white balance (and focus) to a particular object by touching the screen while lining up the shot. This doesn’t appear to have that feature, making some photos more difficult than in the past.

Micro-USB connection — excellent, compatible with my previous phone, so I have plenty of cables.

As with all Android phones, I love the way you can just copy stuff to and from it — not tied to pushing things through iTunes.

Beefs

Any new phone will take some getting used to. This is good, but it’s not perfect…

The iPad and my old phone both had an easy way to grab a screen capture. Does Kit Kat not have this?
People keep telling me to hold down Power and Volume Down… this doesn’t do anything for me. What am I doing wrong?
– 12/11/2013: Okay, figured it out. Unlike with my old phone, you have to press Power and Volume Down simultaneously, not one then the other.

Despite a front-facing camera, it has no mirror app?

I’ve spent years gradually changing all the phone numbers in my contact list to be +61 4xx xxx xxx (4 for mobile, at least) – so the theory was if I ever wanted to dial one from overseas, it would work. Imagine my surprise when incoming texts and calls don’t match up to the names. Only those that are in there as 04xx xxx xxx match up. Seriously?

Text messages are rolled into an app which also handles Google Hangouts. Neato — I guess they’re taking on iMessage. But why when writing a text message, does it not give me a character count, so I know how much I can write without going over 160 characters and paying extra?

More to come

14/11/2013 — I haven’t yet played with Google Now, but this article goes into a bit of detail about how to use it.

How to turn off @MetroTrains Android app alerts/notifications

The Metro app is quite handy for finding out what’s happening on the train network, and can send notifications/alerts to tell you when something’s affecting the line(s) you use regularly.

As previously noted, it’s not perfect — the SMS alerts that it replaced were customised to your specific station, so you didn’t have to try and work out if the 7:21 stops at your station — and at what time.

MetroTrains Android app

But anyway, I was puzzling over how to make the notifications stop. Unless your phone is silent, they cause a beep (which apparently can’t be turned off) and fill up your status bar thingy if you don’t keep attending to it.

If you try and add the same line again, it ignores the option to turn notifications off. I asked around on Twitter, and other people were having this problem too.

After some experimentation, it appears there are two solutions:

Not so good: Take the IT Crowd’s catchcry of “turning it off and on again” to the next level: Uninstall the app, then add it again. You’ll have a clean slate, and you can add your line(s) again.

Better: go to My Alerts, press and hold on the line you want to change. After a second or two you’ll see an option to delete it. Do so. Then go back and add it again with your preferred options.

MetroTrains Android app: Delete an alert

There’s been some suggestion from one user that a network-wide alert might sneak through with a notification even if you have all individual lines turned off. Not sure about that.

While the app does provide welcome information of problems (I’d rather know than not), they probably need to do some work on it, particularly around options for specific station times and alert tones (or not).

Meanwhile, tram users have Tram Tracker of course, and bus users… well, they’re still waiting.

Long term PTV should probably be taking the lead and being the conduit for all service information, regardless of operator, perhaps organised by area instead. For instance it would be useful to know if that power fault affecting train signals and boom gates has also affected the local buses you might use as an alternative way home.

How much would it cost to re-write the #Myki software to make it fast as other cities’ smartcards?

Refactoring is a legitimate strategy in software development. It’s where you feel the design is (more-or-less) right, but the software implementation has gone wrong, and needs to be completely cleaned-up, by chucking it out and re-writing it.

So here’s a thought: if the single most annoying, unreliable, sluggish part of the Myki system is the Readers, then how much time, money and effort would it take to completely refactor all of the software in the Readers?

Don’t change the hardware and cards, which has cost a bomb to buy and install, but (assuming the protocols the Readers work with is okay, and the hardware/cards are up to scratch – they’re used in other cities, after all) upgrade the software.

Myki is here

First you’d tweak the rules/logic a bit to help fix the worst issues — for instance, you might:

  • ditch the confusing and not-very-good-value 7-day passes and replace them with an automatic weekly cap
  • allow travel on a zero balance (rather than $0.01) to get around issues when people load the exact fare onto their card
  • and you’d want to change the beeps to remove the meaningless double-beep and instead have differentiation between touch-on and touch-off

Then you’d hire a small team of gun programmers and testers, and let them get to work, with a small budget of say $1 million (about a 50th of the annual cost of running the ticket system) and some specific targets, starting with:

  • fixing known bugs
  • maximum 1 hour from online topup to it being available at fixed (railway station) readers
  • and the most important one: consistent maximum 0.5 second response times (but preferably closer to 0.1 or 0.2), as seen with other cities’ smartcards

As my friend Josh often says: How hard could it be?

Every mobile phone I’ve ever owned

Inspired by Andrew’s post a few months ago, here’s a list of the mobile phones I’ve had over the years.

Ericsson GH198 (from 1994). It had a twirly antenna that could be flat against the main part of the phone, or twirled around and up to make calls. I seem to recall it cost me about $400 plus a 2 year contract

Predictive text on the Nokia N95I think after that I had an Ericsson GH337 or 338 for a couple of years. Or maybe I had a 337 then a 338? Can’t remember.

Nokia 6210 (from 2001) — first one with a web browser and an internal antenna rather than one which stuck up out of the phone.

Motorola E365 (Briefly in 2004, before I sent it back because I didn’t like it) — it was the first one with a camera.

Nokia 6100 (2004) — a titchy, tiny phone, with interchangable covers. Neat.

Nokia 6230i (2006)

Nokia N95 (2009) — this was great.

HTC Desire S (2011). Also been great, though it’s a bit slow with Android 4 loaded onto it. I’m about due for a new one now.

  • A 2011 post where I compared the SAR (Specific Absorbtion Rate — eg radio waves going into your head) of some of these phones.

Computer names… what’s next?

For some years now we’ve named our home computers after characters in Tintin.

First we had Tintin and Snowy, both desktops.

Snowy was replaced with Haddock.

The two of them were joined for a little while by Nestor, which was called that because it was a server.

Tintin and friends greet Armstrong

Haddock broke down (probably a motherboard failure, I suspect), and has been replaced by a secondhand 2008-model Mac Pro, which given it’s much brainier, we called Calculus. (If you ever manage to get a secondhand Mac Pro, I recommend them. They make excellent desktop PCs, even if you run Windows, which the 2008 and later models do easily via BootCamp. This beast may be old, but the build quality is fantastic, it’s still fast and rock solid.)

I also got a laptop, which given it moves around and visits various parts of the world (well, okay, various parts of the state), I called Alcazar.

Now Tintin is set to be replaced, by another Mac Pro. The question is, what should we call it?

One idea is that, given the two Mac Pros will be near-identical, we rename the existing one and call them Thomson and Thompson, but let’s face it, that’d be too confusing.

Perhaps it’s time to start re-using names.

Ideas?

Oh, and while I’ve got you, can any Mac people recommend a TV tuner (preferably dual tuner) that will work with the Mac Pro in both OSX and Windows/Media Center?