Just because it's cheap and cheerful, doesn't mean the latest batch of budget Android phones aren't useful.
Budget, or ‘Value’ phones in the past have never really gotten a good rap. Ugly and slow, plagued with obsolete versions of Android bogged down by carrier skins, apps, and services – those looking to purchase something affordable and useful have generally been forced to pick one or the other. But the times, as they say, are-a-changing; as manufactures attempt to court the burgeoning developing markets in India, SE Asia and Brazil, coupled with plunging component costs, low cost smartphones are beginning to sport premium components, such as curved glass screens, better processors and cleaner software experiences.
This is thanks to concerted movements by Android and Google to take over the software side of things and leave manufacturers to put all their eggs into the hardware basket. Last year, Google announced both a rebirth of its once doomed Android One project and the introduction of Android Go to offer clean(er), optimised, stock versions of Android that would be regularly updated with security and feature updates. This would essentially allow OEMs to cede control of their software to save costs on keeping their custom ROMs updated, which in most cases is wholly pointless for cheaper models, while Google keeps customers satisfied and on the platform.
Fast-forward to 2018 and models released under both projects are starting to trickle out, with one famous brand – Nokia – hitting the road hard with a swath of Android One models across various price points along with the first Android Go device available outside of developing markets – the Nokia 1. Alcatel, a stalwart player in the value phone market, is on track to releasing the Alcatel 1X in Australia within the next few months and supplied us with a review model to run through its paces. So, we thought we’d see how these “New Value” devices competed against the standard offerings and if they finally managed to be worth those hard earned dollars.
Wait, what’s the difference between Android One and Android Go?
Both One and Go are the most up to date versions of Android available, made by Google and optimised for the devices they are installed on. But where things differ is that while Android One certified devices must offer least two years of feature and security updates directly from Google, which is almost unheard of on non-flagship or Pixel devices, as well as a clean, bloat free, stock experience with all the Google apps, services and trim thrown in – Go phones are not, although Google mandates a specific amount of storage be made available, which largely prevents OEMs going crazy.
Gone are the bad launchers, silly skins, pointless services, duplicate apps and empty 3rd party app stores. The idea is that the money saved from “personalising” Android can be focused into developing better hardware and adding features normally omitted from models under $300.
Go is designed to run on devices with 1Gb of Ram or less, and with 8Gb or less of storage. It runs special “Go” versions of Google apps like Gmail and YouTube that are significantly smaller in size, require less processing power and use less data than their normal counterparts. Google has also worked with other companies like Skype and Facebook to make “Lite” versions of their apps that follow the same conservation ethos.
Android One is effectively the same stock version of Android that exists on Google Pixel devices, although there are some features omitted that are sold as part of the phone’s hardware.
The Nokia 1, Alcatel 1X and Android Go
I was probably the most intrigued about the Nokia 1. Firstly, because it was the first chance I’d had to check out “Go”, but also because it was the first time I had used a Nokia since the Windows Mobile heydays and I have always been a fan of their creativity when it comes to industrial design. Even though the parent company is different (now HMG Global), the team behind Nokia’s new range is still based in Finland and still retains a lot of its original dedication to quality and colour.
Straight away, you can tell that Nokia is attempting to position the 1 as the new 3310 of Smartphones. It’s not shying away from the fact it is wholly unpretentious – its chassis has a removable, replaceable colourful plastic shell, with a modest and removable 2150mAH battery - a throwback to its feature phone past. Hell, it even sells other colours for $15 a pop, although I’m sure aftermarket versions probably aren’t far away if the device sells well. In the centre is a 4.5inch IPS LCD at 480x854, surrounded by some decently chunky bezel.
It’s not unfair to note that, at $150RRP, the specs aren’t remarkable. Its processor, a MediaTek MT6737, is a cheaper competitor to the Snapdragon 420, rocking a Quadcore 1.1Ghz processor with a modest, but still durable, Mali-T720 GPU. It’s backed up by 1Gb of RAM, 8GB of storage (expandable to 128GB via MicroSD), headphone jack, and Micro USB. There’s a 5-megapixel camera on the back and 2-megapixel camera on the front – both of which perform a lot more admirably than you’d think. For all intents and purposes, it’s basically on point with any other device in its price range.
Meanwhile, the Alcatel rocks a very similar processor (the MT6739, a tiny increase in performance via the 1.3Ghz Quad), 1GB of Ram and a positively overflowing 16GB of memory. It also features a bigger, brighter, 5.3inch screen, Micro-SD, headphone jack, and MicroUSB. There’s also a bump in camera performance, with 8mpx on the back and 5 on the front. It performs a hell of a lot better than the Nokia 1 on that front, as you’d expect, with clearer shots and better performance in low light. Outside of the screen and camera, mind you, it’s fairly identical, spec wise, to the Nokia 1.
But the secret sauce here is the terrific job Google and Nokia have done with Android Go to wring every single ounce of power from the hardware. The base OS is about ¼ the size of regular Android, taking up only 2.2GB of space (as opposed to 7.7GB on the Nokia 3.1), and it uses roughly the same fraction of the memory available to run as well. This is mainly thanks to a lot of normally “always on” services instead reduced to being activated on demand, as well as focusing Chrome as the primary driver for most of Google’s “Go” apps. For example, Google Assistant needs to be run manually, rather than made available via voice prompt.
Go also puts a large emphasis on Data Saving, both via cellular transfer and onboard storage. Go and Lite apps are almost always less than 10MB each, and their updates largely replace that amount rather than gradually increasing it. In fact, every app in the Play Store has its size on the page, so you can see at a glance what you are in for. There is an option in settings that gives you per app control over how much data they use and apps like YouTube Go offer offline downloading for any video to take advantage of Wi-fi.
What is left is a dramatically surprising experience – moderate use of most applications, from Facebook to even games like Clash Royale, was quick and responsive. Even modern games that generally wouldn’t have a hope in hell of running, like the MOBA Arena of Valor, were playable, though with slightly longer load times and the odd framerate dip. Watching video, sending emails, and reading the news on the Guardian app was fine. But it was when we really pushed it – switching between a number of these apps at will, with active maps and multiple conversations – where we felt the strain of that 1GB Ram limit hitting the wall. The camera is, well, bad.
But then we hit the potential problems – what happens if the OEM decides to tinker with the careful OS streamlining? On Android One devices, this isn’t possible – the OS must be stock and the launcher must be Google’s. Alcatel actually took what was a very good device for the price on paper – more powerful than the Nokia 1, with a better screen and camera – and completely destroyed it by skinning it with a custom launcher (ironically called Joy). The device is absolutely bog slow and basically unusable for all but the most core functions – messaging and phone calls. Opening Maps Go took 25 seconds, and every other action that required some effort by the CPU or GPU just reduced the phone to a crawl while it attempted to catch up with itself. When there is only 1GB of ram, adding ANY sort of bloat completely mauls the device’s ability to maintain both core and auxiliary functionality. I can flat out not recommend this device to anyone when both the Nokia 1 and 3.1 exist.
But the reality of the situation is that, for the most part, those who would consider themselves power users are not generally in the market for these base level devices. For $100 more, the Nokia 3.1 (See more below) runs “full Android” and has more RAM, a bigger, higher resolution screen, and a faster processor which is designed to handle more demanding applications (for example, using Android Auto in your car for Maps and Music at the same time). What’s different and impressive here is that a $150 smartphone off the shelf in Australia is now actually up to date and functional in a way that is was not before. This is a device you could take camping or to a music festival and do everything you’d want to on your flagship without worrying about it being broken or stolen.
So what I found was two very different experiences with Go. But when it came to updates things were a little better. On the Nokia 1, the promise of updates and stock cleanliness made it the first device at this price point relatively future proof. I had 2 updates waiting for me on boot for both models, which brought them up to the same version (8.1) as my Pixel 2XL. It was followed up by the July and subsequent August security patches a few weeks later - all three updates were very quick to download and install.
While Nokia has largely had a reputation for looking after its customers, Alcatel certainly hasn’t, but at the very least it wasn’t sitting on a version one or two years old. Time will tell if it keeps supplying them. But the device’s awful, chunky performance thanks to the inability to just leave well enough alone has neutered its first promising budget release in many years.
The Nokia 3.1, Moto G5S and the Xiaomi elephant in the room
For those looking for a more conventional Android experience with a bit more grunt under the hood, there are a number of low cost Android One phones available under $300 – the first is the aforementioned Nokia 3.1 – which is effectively a solid bump up from the Nokia 1 in both design and performance. There’s an OctaCore (as opposed to Quad) MediaTek 6750 running at 1.5Ghz, and a chunkier PowerVR GPU that can push more frames and textures than the Mali. There’s 2GB of Ram onboard, 16GB of Storage (expandable via MicroSD to 128), headphone jack, (sadly) still MicroUSB, and the much loved headphone jack.
On the camera side, we have a much more usable 13-megapixel shooter on the back and an 8-megapixel on the front. Images are cleaner and clearer, although the lack of any sort of stabilisation makes things a little dicey at any time – that said, what you get in both low and decent light is much better and you wouldn’t be embarrassed to put them on Instagram. Nor would you feel like you’d need to hide it – the Nokia 3.1 is impressively built for its price, with a beautiful, 2.5D Gorilla Glass screen, metal around the middle chassis and a clean, tasteful, solid plastic backing. There’s also a more than decent 720p resolution inside the 5.2inch frame, with a pixel density of 214ppi.
The screen isn’t perfect – it looks a little sunken around the sides – but it has a wide brightness range and very good viewing angles with no obvious tinting. I really liked holding this phone; its size and edging makes it easy to hold and would be a good middle ground for those used to 4.5in phones who would like a little more viewing space for videos and reading. The buttons are solid and clicky, although as expected, the speakers are nothing to write home about. As per the Nokia 1, battery performance is pretty stellar – both devices sat on standby for days and endured about 15 hours of active use.
Unlike the Nokia 1, which doesn’t mandate software updates (Nokia does, however, match all its models to get updates at roughly the same time), the Nokia 3.1 does, putting it inside a very exclusive club within this price range. Interestingly, unlike the 1, which was updated to Android 8.1 within a few days of first boot – the Nokia 3.1 is still sitting on 8.0. It does have the most recent Security patches, but seems to be a little bit behind the release curve. I reached out to Nokia and was told that the 8.1 update it was in the final stages of testing as the model was only released in the past month while the Nokia 1 has been available since March.
If the 3.1 is compared with the Nokia 1, or even a number of other phones in its range in regards to performance, it’s pretty swift. As noted above, the extra ram and more powerful CPU/GPU allow the vast majority of apps and games to play seamlessly. The problem is that 2GB of Ram is just still not enough for advanced Android – unlike Go, standard Oreo doesn’t conserve memory as efficiently and most of that first gigabyte is taken up by the OS. What is left is shared between whatever apps are running, which means bottlenecks are common when you are flipping between more than 2-3 apps. For example, Maps runs fine in a window on top of a text, but if you are playing podcasts at the same time and popping in and out of a game, you will feel the phone start to cry a little. But for a MediaTek it performs a lot better than I had expected.
On a global scale, however, the Nokia 3.1 straddles a very difficult line – while it would have been easily the best device in its price range a few years ago, other competitors are starting to creep up.
Although it is not officially available in this country, Chinese brand Xiaomi’s Android One Mi A1 is roughly the same price as a Nokia 3.1 and effectively blows it out of the water – there is a Snapdragon 625, 3Gb of RAM, Fingerprint Scanner, twice the storage and a much beefier GPU. It also has a 6 inch screen, full aluminium unibody and a higher resolution to boot. It can be direct imported for about $280, and has been one of the most popular phones in this price range for the last year – so much so that its sequel, the Mi A2, has just released with better specs and can be picked up for just $100 more.
But if you’re concerned about warranties and don’t want to muck around with grey importing, there is little out there like the 3.1. It’s the best phone in its price bracket locally, especially when you take into account its bloat free, secure and future proofed software, which contributes to its improved performance over other sub-$300 devices.
So at the end of the day, can I recommend any of these devices? I was impressed with how clean and lean the Nokia phones were – they were up to date, well made, free of bloat and pointless services. The One would be perfect for tweens or older users who don’t necessarily need anything too advanced but would enjoy the added benefits of apps like Maps, News and Email. The 3.1 is a great budget device for users who want a little more oomph without laying out a lot of cash. The Alcatel 1X, however, is a perfect example of how OEMs can take clean software and absolutely destroy it with very little benefit to themselves or the consumers purchasing it.