High time for a new Android phone

. . . but not an HTC One S (at least not in Europe).

It's now over two years since I bought my HTC Desire. It hasn't broken or malfunctioned, and I still use it intensively every day. But as my 'essential' apps swell with every automatic update, the phone's limited internal memory is becoming a real constraint too often. (Google Maps now hogs 19.25Mb and still cannot be moved to the SD card!) Processes slow right down or simply stop, and software cannot be updated until I uninstall another app to free up space. And of course my unrooted phone is stuck on Android 2.2 (Froyo) while the operating system has progressed through Honeycomb and Gingerbread to the gorgeous-looking Jellybean.

So I figured the time had come to pass the perfectly serviceable Desire on to another member of the family and choose myself a new Android device.

I do feel some loyalty to HTC, and I like the solid build of their phones, so my first choice was the HTC One S. The black carbonised metal finish sounded cool, the 4.3-inch screen and slim profile were perfect for me, and I liked what I read about the fast 1.5GHz dual core Snapdragon S4 processor. Possible downsides were the pentile AMOLED display, which some reviewers found 'jaggy', and the lack of an SD Card slot to supplement the 16Gb of internal memory, which is shared between internal memory and data storage. But the pros outweighed the cons, and I shopped around for the best price on an unlocked phone.

I found a great price at Pixmania.be (I live in Belgium). The €424.99 deal came from a third-party vendor, Expansys, and announced the processor as the 1.5GHz dual core Snapdragon S4 that I wanted. But I had read that HTC was having difficulty sourcing the S4, and that in some European markets the One S was being sold with the older 1.7GHz S3 processor, with inferior performance and battery life and some overheating problems. I had no way of checking if these rumours were true, but I decided that the S3 was not for me. So I emailed Pixmania, asking for confirmation that the model advertised really was fitted with the 1.5GHz S4 processor. Yes, I was assured, it was the 1.5GHz S4, as advertised. Okay then! I placed the order.

Two days later, the package arrived, but the model number on the outside of the phone's packaging worried me. I checked with HTC itself, and quickly got a polite reply: "The code Z560e on the box indicates that you have received the 1.7GHz version of the device. This is an enhanced version of the dual-core Snapdragon processor, running at 1.7GHz to provide a comparable user experience to the 1.5GHz S4 chip. There will be no discernible difference between the user experience supported by the two processors, with both delivering a premium experience." But that was not what I had ordered!

Pixmania referred me to Expansys, who did not respond to my message demanding that they refund the full price and cover the cost of returning the device. But with support from the European Consumer Centre Belgium I insisted, and the phone was finally picked up by a courier today. I trust my credit card will be recredited as soon as the phone arrives back at Expansys, and then I'll be looking around for another new Android phone once more.

Does anyone have any advice? The Samsung Galaxy S III looks great, but Samsung's phones always seem a bit flimsy to me. And of course, I'd really like Jellybean pre-installed.

Next post: App review: EUssentials

Scarce resources 1 - Memory

There are three resources - internal memory, battery-life and cash - which, to varying extents, most smartphone users try to conserve. I am pretty stingy about all three.

When choosing and using mobile apps, there is almost always a trade-off between utility - the additional functionality, time-saving, or simple pleasure that I expect an app to bring me - and the holy trinity of memory, battery and hard-earned cash.

My HTC Desire is now nearly two years old. It's a great smartphone, but it has only 1GB of internal memory, divided more or less evenly between ROM (app storage) and RAM (current processes). That might sound like a lot of memory, but a significant slice of both ROM and RAM is taken up by the Android operating system itself, and by the various components of the HTC Sense overlay. Even when these are not using RAM memory they take up valuable ROM space, since they cannot be uninstalled. The amount of memory actually available for apps installed from the Android Market or elsewhere is therefore a real constraint. I don't monitor the phone's memory usage closely, but I do know that when the Available space in Internal phone storage falls below 20MB (below, left) then loading or switching between apps begins to slow down. Around the same time, I may start to receive 'Low on space' warnings in the notification bar.

Getting a bit low on available memory (left). If you really must, you can 'Force stop' an app (right), but it's better not to.

In fact, one of the Android operating system's great strengths is its efficient management of device memory. You'll find numerous 'task killer' apps in the Android Market which claim to improve speed and battery life by enabling you to close down apps when you are no longer using them. Don't be taken in. First, leaving Android itself to close apps when the memory they are using is needed by another process produces better results. Second, if you ever do need to shut down (or 'Force close') a rogue app, there's a perfectly good way to do this built right into the operating system. From the homescreen menu, choose Settings / Applications, then Manage applications, then choose the target application and tap on Force stop, as in the screenshot on the right, above. (These instructions are valid for Android 2.2, Froyo.) I have almost never had to do this. For anyone used to Windows computing, Android has a near-miraculous ability to recover gracefully from traumas.

So far, I have only talked about 'internal' storage space. The limited amount of this type of memory available on my HTC Desire makes me very careful about the apps I choose to install. Every app on the phone really has to justify the precious space it takes up. And if I am trying to decide between two apps offering similar functions, then I always tend to favour the one with the smaller installed size.

However, my phone also has plenty of 'external' storage space, with a 16GB microSD memory card fitted. This is where I store the music, photos and documents that I want to be accessible even when I don't have an internet connection. Apps use the SD card to store their data. But it is also possible to move large chunks of most apps to the SD card. This reduces their footprint in internal memory, making space for additional apps. Later versions of Android allow you to move apps to the SD card by default when you install them. But if, like me, you are still on Android 2.2 (Froyo) it is well worth going through all your applications and moving those that allow it to the SD card, if have not already done so. From the homescreen menu, choose Settings / Applications, then Manage applications, then choose the target application and tap on Move to SD card, if available. (If the app does not allow it, the button will be greyed out.)

One word of warning before you starting moving apps to the SD card. Homescreen widgets cannot run from the SD card. For this reason, most apps with widgets do not enable the 'Move to SD card' option, but some do. If you move such an app to the SD card you'll almost certainly find that its widget no longer works. If this happens, move the app back to the phone. You will probably then need to reboot the device by powering it down and powering it up again to get the widget to work.

My final memory management tip is to clear out your apps' caches from time to time. Most apps store data of various kinds, and this should not normally be cleared, as it probably includes all your settings. However, many apps also create temporary caches which can grow quite large over time. (The different buttons for clearing data and clearing the cache can be clearly seen on the right-hand screenshot, above.) If you encounter memory shortages, go into Settings / Applications from the homescreen menu, select Manage applications, and press the menu button to sort your apps by size. Go through the ten largest apps one at a time and clear their caches. Browsers in particular rapidly build up large caches. My preferred mobile browser, Dolphin HD, offers options to clear these caches from within its own settings menu - clearing the HTML5 cache may reclaim one or two precious megabytes of space.

To summarise, I recommend three simple strategies for conserving memory on your Android smartphone:

1. Be highly selective in your choice of apps. Avoid duplication and choose small apps where possible.
2. Move as many apps as you can to the SD card.
3. Periodically clear the caches of your most memory-intensive apps.

Next post: Text entry