1644: Contemplating My Now Not-So-New Phone

Avid readers (hah) will recall that a while back I jumped ship from iOS to Android when I upgraded my phone. My long-in-the-tooth (relatively speaking, anyway) iPhone 4S was replaced by an HTC One M8, a phone which had received some positive reviews from people I knew and trusted, so I decided to take a chance and give it a shot. It was a good time to do so, since I’d been becoming increasingly disillusioned with many of the apps available on smartphones generally, and as such I wasn’t feeling particularly “invested” in the iOS ecosystem — in other words, there weren’t very many apps that I felt particularly attached to.

So, a little down the line, how am I finding it now the inevitable “honeymoon period” is over?

Well, I’m still really liking it, and the one peeve I had with it — the fact it seemed somewhat prone to random restarts and reboots while I was in the middle of doing things — appears to have worked itself out, and hasn’t happened for a long time now. (Watch it start doing it again now I’ve written this.)

As I noted in my earlier posts, I’m not a hugely adventurous smartphone user these days. There are relatively few things I actually want to do with my phone, but most of them are beyond what a simple feature phone offers — or, in the case of facilities that feature phones do offer, smartphones inevitably do them all somewhat better.

Here’s the limit of what I use my phone for: Email. Texting. Phone calls (only when there is no other option). Calendar. Music and podcasts. Google Hangouts. Twitter. Web browsing. Very occasionally Facebook and Google+, though I don’t use either network very much any more. And, if there is nothing else to do during an extended visit to the toilet, playing a simple, toilet-friendly game like Threes.

That’s about it. There’s probably more I could do with it but I don’t really feel the need to right now, since the stock apps and the few additional ones I’ve installed cover most of the things that I want to do with it on a daily basis. I can communicate with it, I can browse the Web with it, I can take snapshots with the camera if necessary and I can read information on a screen that’s noticeably bigger than that offered by Apple’s iOS devices.

I’ve been particularly impressed by Google Play Music, which provides a number of helpful services, chief among which is something similar to Apple’s iTunes Match service, only it actually, you know, works. For those unfamiliar, iTunes Match (and Google Play Music) is a facility whereby you can upload tracks from your personal music library or “match” existing songs with iTunes/Google’s online libraries, then stream or download them to any compatible device. In effect, this allows you to take your entire music library with you wherever you go, rather than being limited by the storage space available on your phone — though the streaming side of things is, of course, dependent on you having a good wireless Internet connection either via the mobile phone networks or Wi-Fi.

Where Google Play Music differs from iTunes Match is that it’s a lot clearer in presenting its information. With iTunes Match, it was almost impossible to tell which songs you had downloaded to your phone — and consequently available when no Internet connection was around — and which would require streaming. Attempting to download songs often resulted in failure for no apparent reason — and with Apple’s phobia of error messages, there was no way of discovering what was causing the problem. Google Play Music, meanwhile, while having a somewhat clunky interface in a few places — it’d be great to have just a plain list of albums, playlists, songs and that sort of thing rather than the overly graphical, space-wasting interface it has — but at least presents this sort of information clearly. It’s obvious when you’ve downloaded something or if you’d be streaming it when you clicked Play, and, importantly, it’s easy to remove things from your phone once you’ve downloaded them — something which iTunes Match made seemingly impossible to do manually for some inexplicable reason.

So that’s been great, and the other apps I’ve been using regularly all seem to work pretty well, too. All in all I’m sure I’m using this phone to a fraction of its full potential, but it’s doing everything I want it to and it’s doing it well, with my only real criticism of the device as a whole being that the volume control buttons are in a stupid place and are much too easy to press accidentally while simply holding it normally.

1582: My Phone’s Not Called “Mate”

So, an update on how I’m doing with my new phone after several days of fiddling around with it. (Said new phone, if you missed my post from the other day, is an HTC One M8 — my first Android phone, though not my first Android device.)

I’m really liking it! Like, way more than I thought I would. There are flaws, certainly — the phone has frozen and rebooted itself while I was in the middle of doing something rather more times than I would have preferred it to in the last few days — but on the whole, it’s been a great experience so far and I dare say that I am actually starting to prefer it to iOS.

Don’t get me wrong, I’m not going to suddenly become an Android fanboy, largely because I find Android fanboys to be some of the most insufferable fanboys on the entire Internet. Nor do I feel that iOS is now “bad” because of the time I’ve spent with Android. But there are clear and discrete markets for both, and they both do their own thing extremely well.

iOS, like most of Apple’s other products these days, is designed to be accessible, simple and straightforward. I hesitate to say “designed for stupid people” but it’s certainly designed in such a manner that stupid people can’t break it easily. It doesn’t blind you with unnecessary information — if there’s something it can do quietly in the background without telling you what’s going on, it will. This is great for people who panic when they see technical messages they don’t understand; however, on the flip side, it’s less than ideal for computer-literate people who like to know what their device is up to — and if it’s up to something it shouldn’t be (or not up to something it should be).

There are two features on iOS where this is painfully apparent, and as I count myself in the more “computer literate” camp they’d been becoming increasingly frustrating to me.

First up is Photo Stream, a feature whereby you take a photo with the phone’s camera and it gets automatically backed up to your iCloud account and synced to any other devices you’ve also logged into iCloud with. This is, in theory at least, extremely useful for backing up images and just for transferring them from one device to another — from phone to computer, say — without having to faff around with long-winded sync processes or additional hardware. And, a good 90% of the time, it was great. The trouble was, for that remaining 10% of the time it would just not work, and it certainly wasn’t going to tell you why. I eventually managed to figure out that if Photo Stream wasn’t syncing it was generally for one of two reasons (the battery being below 20% or you not being connected to Wi-Fi) but the phone certainly didn’t tell me that.

iTunes Match, the service that allows you “cloud” access to your full iTunes music library from any device, is the same way. A few weeks back, my iPhone simply started refusing to download certain iTunes tracks to itself, which made loading it up with tunes to take on a long trip to be troublesome at best, completely impossible at worst. Again, there was no means of getting feedback on what was going wrong and why some tracks would download but others wouldn’t; it simply wouldn’t do it. Infuriating. But I can sort of understand why Apple chose not to put frightening error messages in there — so as not to scare off the casual, less computer-literate people.

Android’s big selling point is its customisability, and to be fair I haven’t explored that a great deal with my new device just yet — I’ve been largely happy with the stock options so far. It comes preloaded with a standard app launcher and a special “car mode” with big buttons and quick access to music, navigation and other useful features you might need while driving, but I know the option is there for further customisation. I also like how you can have things installed on the device but not visible on the home screen.

What I’ve really liked so far is the notifications system. I can clear all my notifications with a simple tap on a button, or I can also take action on a lot of them right from the notifications feed — reply to a tweet, archive an email, all manner of other things. It took a little adjusting to the fact that the phone doesn’t display messages on the home screen like the iPhone does, but having used it for a few days now, it’s actually quite nice to have the peace and be able to review notifications at your leisure rather than when your phone thinks you should.

Plus there’s the sound. I’m not normally a fan of playing music out of a mobile phone, but the M8 has some surprisingly competent speakers. They’re never going to rival a proper setup, of course, but they’re loud, reasonably beefy considering their size, and they make listening to music or podcasts without headphones while doing other things — housework, for example, or, more relevantly to now, packing — eminently practical. Combine with Google Music’s much better, more stable implementation of “cloud music” than iTunes Match offers along with the ability to put an extra SD card in there for storage and you have a device that is a kick-ass media player as well as a solid communication device, too.

So I’m liking it a lot so far, and I’m certainly not missing my iPhone, which I gave to O2 for recycling in exchange for a little over a hundred quid — not to be sniffed at for minimum effort. Whether or not I’ll stick with Android in the long term remains to be seen, but frankly it’s looking quite positive right now.

#oneaday, Day 269: Things To Do While Waiting For The Phone To Ring

Of all the items of technology the human race has ever invented, the humble phone is surely one which has the greatest hold over our lives. It can make us drop what we’re doing and run off somewhere. It can make us laugh, make us cry, make us scared. And it can make us wait. Wait for hours.

You might be waiting for the results of a job interview. An STD test. A loved one’s driving test. You might be waiting for a special person to call. You might be hoping that someone from your place of work doesn’t call because you skived off today and you think someone might have seen you on your lunch break. You might be waiting for a utility company to “call you back” with the results of an enquiry you made six months ago.

In short, you could be waiting for lots of things. Which means you could be spending an awfully long time sitting and staring at your phone, particularly if you’re kicking yourself that you gave the person you’re expecting to call you back your landline number. Because who the hell uses landlines any more anyway? Mobile’s where it’s at. With a mobile phone you don’t have to sit and stare at the phone, willing it to ring. Of course, in practice all that happens is you tend to sit on the couch with your mobile nearby instead of near the phone table. Because you don’t dare go anywhere in case you miss an important phone call. And heaven forbid if you ever have to answer an important phone call while you’re engaged in toilet activity of the sitting-down variety. (“Is that an echo?” they’ll say. “Where are you?” “In a cave,” you’ll reply, a little too quickly. “A cave with a mobile mast on top of it.”)

So what to do while you’re waiting for the phone to ring? It can’t be anything which you have to commit to, because you might have to drop everything at a moment’s notice to go and answer the phone call. It can’t be anything that gets your hands dirty, because no-one likes picking up a phone with dirty hands. And it can’t possibly be anything which requires you to go outside, because then other people might hear you discussing your itchy parts with the nurse.

So, here are five suggestions.

1. Pair up your socks.

You’ve been meaning to do it for months. And you haven’t. So instead of sitting staring into space, why not make a start on it? Pairing up your socks is a job that you can easily leave unfinished and go back to, months later sometimes. Hence, it is an eminently waiting-for-phone-call-friendly activity. Experienced professionals with cordless phones can even continue pairing their socks while they are on the phone.

2. Play a casual game.

This is what casual games like Bejeweled, Peggle and the like were made for. Playable in short bursts, easy to jump out of at a moment’s notice if you need to and actually fun for those few minutes you’re waiting, they also give your brain a bit of a workout. Unless it’s Farmville, in which case all you’re working out is your clicking finger. Moo.

3. Play “Six Degrees of Kevin Bacon” on Wikipedia.

Here’s how this works. Pick two completely disparate topics. Open the Wikipedia page for one. Using six clicks or less, you must navigate your way to the second topic using only the hyperlinks within the Wiki articles.

4. Bleach the toilet.

You’ve been complaining for weeks that the toilet stinks, so go and squirt some bleach down it. This takes a matter of seconds. And if the phone rings once you’ve bleached it, it’ll be time to flush by the time you’re off the phone again.

5. Make me a coffee.

Well go on. Don’t just sit there.