So, the Blackberry was a bad idea, I admit. It was a nice phone but the software was lacking in too many areas (mainly the Java side of it). If RIM bring the Blackberry to Android standards then I’d happily go back.

So anyway I thought it was about time I got myself a new phone. I was definitely after another Android because they’re just so powerful and the apps you want actually exist (and for free too) unlike on Blackberry. I began shopping around quite a while ago but I could never quite find what I wanted for the right price. I didn’t want to spend any more than £300 because I just don’t feel the likes of the iPhone 4S is worth £500 (more if you get more memory). £300 was my set limit, no matter how tempting the iPhone was.

I set myself the challenge of price, it had to be Android and it had to be capable of running Cyanogen Mod (stock ROM’s are awful on most phones). So after much browsing and research, the LG Optimus 2X was my final choice. I wanted the Samsung Galaxy S2 but it’s price tag of £480 put it straight off the list. The LG Optimus 2X however has similar specifications but only cost £269 from Amazon (the cheapest I could find it). What’s more it runs Cyanogen too.

Source: TechRadar

Specs

This phone has some impressive specs packed into such a small area. Lets have a look:

Dual Core 1 GHz Cortex-A9
Nvidia Tegra 2 AP20H Chipset
ULP GeForce GPU
512MB RAM
8GB Internal Storage, up to 32GB more can be added with a micro SD card
480×800 IPS LCD Capacitive Touch Screen
Soft Touch Capacitive Buttons
8MP Main Camera (1080p Video Capable @ 24fps, 720p @ 30fps)
1.3MP Front Camera
LED Flash
GPS
1500mAh Battery

See more specs here >
See TechRadar’s Review >

As you can see, it’s a very powerful device. The 2X was the first dual core phone ever produced, and along with the Nvidia Tegra chipset it makes for a very powerful combination.

512MB RAM is pretty standard for a high end Android smart phone, so nothing special about that. The internal 8GB of memory is double that of most other smart phones, but this can be upgraded with 32GB more with the micro SD card slot. And again with the screen this is a standard size for high end smart phones. I was disappointed to see no OLED screen with this but for the price I’m not going to complain much.

The camera is an 8MP 1080p video capable sensor which I have to say performs pretty well. The focus speed is immense at under 1 second, often quicker. 1080p video doesn’t appear to stutter during my tests but the quality is a little short of that I would expect from a camera designed to do 1080p. It’s a little grainy and lacks definition but certainly does well enough for your average amateur video recording. I’d imagine 720p would look a little sharper but I’ve not tested this as of yet. The LED flash is a little dull, my Blackberry was at least twice the brightness but the quality of the photo makes up for this when lighting is sufficient.

The 1.3MP front camera is very poor. If you’ve ever seen a poor webcam in low light you’ll understand what I mean, that’s how bad it is. There is no lighting on the front either so for low lit video calls it would be useless. Since I won’t be using it for video calls though I’m not fussed, it’s just an “extra”.

I’ve not tried the GPS yet but as a standard function of most modern smart phones I imagine it would perform just as it would in any other device. The only measure you can use for this is its ability to get a GPS lock quickly, but as I say, it’s not been tested yet. Perhaps I’ll write another post once I’ve used it for the first time.

The battery is around the same size as your typical Android device. At 1500mAh it doesn’t pack much power but it’s enough to keep the device alive for around 12 hours of average use. With careful management you could probably get 48 hours out of it. As a light to medium user myself I’m currently trying my hand at some power saving apps that turn off data when it’s not needed, periodically turning it on for email checks etc. I’ll report back on how that gets on once I have the results. I want it to reach the blackberry battery life which was 2-3 days if barely used. If it can do that, I’ll be happy (even if it does need an app to achieve it).

I have an extended life 3500mAh battery on order. While this sounds good, it won’t fit the phone without a replacement back plate for it, as the battery is twice the thickness of the standard battery. However this may turn out to be a sound trade off for decent battery life. We’ll see once it arrives.

Photos

I scanned my device with my scanner so you can get a nice in-focus and close up view of the phone.
Click to enlarge

Cyanogen Mod

Ahh Cyanogen, what would Android phones be without you… I’ll tell you… Underused! Cyanogen unleashes the power of your device much more than a stock ROM would. It also adds more features, optimises for your device and gives an overall more pleasant experience… If you get a stable ROM that is! The only problem with Cyanogen Mod is that it’s developed by volunteers. It’s not their day job, it’s something they do for the Cyanogen community. However despite that, updates are frequent and you get a lot of help with your device on their forums.

One thing I will say about Cyanogen though is that is it incredibly difficult to install if you don’t have the capability of doing some research yourself. Although Cyanogen supply instructions, they don’t always work. In my case they didn’t work when it came to using the ADB commands on the Android SDK. However some Googling later and I found the answers I needed and I was on my way to installing it.

I began with the stable build for my phone, which worked for the most part but the nightly builds were much more up to date so I gave one of those a try. It seems a lot more stable with the latest nightly than with the supposed “stable” version. It fixed a lot of bugs in the operating system that are part of the simple operation of the phone, so I was happy about that.

Verdict… Am I happy?

Yes, definitely. I finally have a phone that can do what I want it to do, even if it’s a little buggy at times (come on, it comes with the technology, nothing is perfect!). I can almost use it like a regular PC. I can get my e-mail, browse the web, remote desktop into my server, edit documents, watch videos… you name it. Admittedly it’s much better on a PC but for a phone it’s a great feat.

I’ve only had it a week so we’ll see how it all goes, and I’ll try to post back on the battery life savings I am attempting to get.

You might have heard recently about the huge hike in hard drive prices, due to the temporary closure of a manufacturing plant in Thailand thanks to flooding. Well, it’s hit everyone I can see so far, from small computer shops to the big businesses and even manufacturers. Acer announced recently that they would have to increase the cost of their machines to make up for the loss.

It’s not as bad for big manufacturers like Acer than it is for consumers though. My regular supplier, ebuyer, used to sell 1TB Samsung drives for about £42, they’re now over £100. Similarly they did 2TB Samsung drives for £62, they’re now over £150. It’s been reported the price has been going up £5 a day for the last week.

I’m lucky. I didn’t anticipate this sort of drastic action but I’d already stocked up on a new 2TB drive last month, so I don’t have any storage problems at the moment and I can probably get by about 3-6 months on what I have. But what about those who don’t have space and need more? They’ll be forced to fork out obscene amounts of cash for a new drive. There is little use in waiting either, it’s reported things won’t pick up again until some time early next year, say Feb/March time and prices begin to fall again.

One of the biggest companies hit that I’m following is OVH, my hosting provider. They’re currently only receiving 10% of their requested hard drive stock, and as a result they are finding it hard to deploy new servers. They’re taking drastic action and using old drives from old stock. They’re pulling them out, running a full disk wipe and then putting them in new servers. Customers are being notified that their drives will be used but there is nothing they can do about it except stop deploying new servers. This obviously isn’t an option to such a big company that is still growing.

Some companies have been panic buying stock which has made things even worse. However this sort of behavior is to be expected – how else are companies going to survive? The fact that this plant that is no longer operating because of the floods, and that it produces around 80% of the worlds stock, makes you wonder why they centralised everything so much. It brings you back to the Japan earthquake and a lot of Sony’s production is done there as well (and not just Sony, quite a lot of other big companies too). Infrastructure centralisation is a bad thing! Why won’t anyone learn?! It doesn’t matter if it’s cloud infrastructures or manufacturing, the end result of something messed up like this is always going to be bad.

Anyway, we’ll just have to wait and see how this pans out. I feel sorry for those who are having to suffer with the ridiculous prices and count myself very lucky I have some spare drives to last me.

Blackberry Outage, October 2011

No doubt you have heard about the recent Blackberry outage this week that spanned over the course of 3 days, Monday 10th to Wednesday 12th October. As a Blackberry user I was hit, although not as badly as some people given that I don’t use it for business purposes. Despite that I still got annoyed over the reasons why it went wrong, as it just shouldn’t have happened the way it did. Even RIM themselves acknowledge this and admit that a lot more could have been done to prevent it. I know for certain they will be looking into this to prevent future occurrences.

So what exactly stopped working? Everything. All e-mail, internet, Blackberry Messenger and everything else data related such as Facebook/Twitter apps. The reason for this is because all data is routed through the Blackberry servers rather than only some data being routed there. It wasn’t until the outage that I realised all data went through the BB servers as I thought browsing went through your providers network as usual. Wifi browsing still worked fine, which is great at home but useless if you’re away from a wifi network. What also annoys me about BB’s is that you can’t use e-mail unless it goes through RIM’s servers. I’d prefer it the way Android allows it where your standard data connection is used and your phone handles it all but I guess that’s what’s unique about the BB service.

I spent a little time trying to figure out if there was a way around this issue with regards to browsing and using the providers network as normal (in my case O2). I tried manually inputting the APN’s but this did nothing. I did discover that tethering still worked as intended which was good to know as the only time I use my BB a lot is when away on business (which is rare in itself).

Over the 3 days I found myself looking at the same news article over and over again, explaining what was happening and when it would be resolved. It was all the same; “It’s being worked on”. That was it, there was no detail at all. At that point I don’t know if they knew what the issue was or whether they were trying to avoid telling people. Regardless, in the end it all spills out and the issue was flagged down to a “faulty core switch”.

Immediately at that point alarm bells started ringing on why the system didn’t have redundancy. It was supplying a service to 10′s of millions of people around the world, surely there was some form of backup? Well according to RIM there was, except it didn’t work “as previously tested”. Fact is, you can’t simulate a failure like this. It’s not like the switch drops off the network and another takes over instead, sometimes the switch fails in a way you can’t predict, causing a flurry of data that causes chaos throughout the software. This itself can result in the fail over not working as intended because it’s not capable of detecting it as an error. I don’t pretend to know how these switches work but that’s my interpretation of articles I read about fail over networking.

So back to the title of this post, what could they do differently? Lets start with the basics of data access. There needs to be some form of fail over for data services. I can accept that because e-mail is controlled by the BB servers that this will be offline, but how about routing internet traffic temporarily through your providers standard network? This at least gets people online and able to check their e-mail via webmail for example.

Secondly the infrastructure itself, as I heard it described, is too centralised. It needs to be spread out over each country and have each country use that infrastructure. This outage took down practically the whole of Europe, plus more. Even USA and Canada were seeing outages. By splitting it on a per country basis they prevent the outage spreading too far, limiting damage and hopefully reducing the recovery time. You could go further and split this into multiple data centers in each country as well but this starts to get costly, so lets just consider 1 data center per country with your fail over being fed into another nearby country’s data center. This would be ideal, IF the fail over works properly if a switch fails.

It all sounds simple but I know it most certainly isn’t. I’d like to think myself technical enough to understand the core levels of networking but I’m not Cisco certified nor am I anywhere near it. RIM can’t afford another outage like this as their revenue is already falling. Disgruntled customers make this even worse when their service is out for 3 days so any and all attempts to avoid this are crucial.

So to summarise, what I think RIM need to do as a part of their strategy is:
1. De-centralise their infrastructure to multiple countries.
2. Fail overs should be another nearby countries BB data center.
3. Formulate a fail over for data services (browsing, etc) by using the providers standard network in an outage.
4. Allow users to choose if their e-mail uses BB’s servers or standard IMAP like Android devices do.
5. Keep users informed if an outage occurs!