We've clearly got a little bias on the subject, but Android has a long and storied history filled with its own triumphs and pitfalls. It's been well over a decade now since that first HTC G1 landed, the inaugural Android smartphone, and things have changed drastically since then. Being "first" might make you think the G1 was the most influential Android phone — but was it, really?
In what is partly an experiment and partly a series, I've been using the Galaxy Nexus as my personal phone exclusively for the last week. It has been a nostalgic experience, as the Galaxy Nexus was the first (good) Android device that I used full-time. And while the sentimental tech-romantic in me would love to tell you all that it's been mostly fine — like my week using the Nexus 5 — I can't. It's actually been pretty rough.
As the Pixel phone announcement draws near, it seems that, if not going away entirely, Google's Nexus brand will at the very least be undergoing some major changes. Google intends to heavily market its Pixel phones if the last week is any indicator, meaning there really won't be much room for the Nexus phone program to exist in the same way it has in the last few years. Nexus may live on, but it will undoubtedly be in a capacity different from the more aspirational efforts we've seen Google make with it in devices like the Nexus 6, 5X, and 6P.
The Galaxy Nexus is nearly as old as the Nook Tablet that CyanogenMod resurrected a couple of days ago with CM13, but it won't be getting that fresh of a software update. It'll have to do with a slightly older version of Android, but any third-party development on this forgotten Nexus is a welcome change from the state that Google left it in.
Officially, the Galaxy Nexus was abandoned at Android Jelly Bean 4.3. When KitKat was released in September 2013, two years into the Galaxy Nexus' lifespan, the phone wasn't deemed worthy of the new dessert flavor (allegedly due to the TI chip), but CyanogenMod's team of zealous and reckless developers braved the elements and kept supporting it with CM11 nightlies and snapshots.
Google announced last year that the venerable Galaxy Nexus would not be getting any of that sweet, sweet KitKat action. Well, not officially anyway. Owners were not pleased, but they couldn't properly flood the internet with complaints because their phones were already dead. There have been a few KitKat ROMs that work well enough, but now some developers have created a kernel and GPU driver combo that could keep this device chugging along through the L release.
It's that time of the month again, CyanogenMod ROM fans. In fact it's a bit past that time of the month, reportedly thanks to a heavy workload and the Labor Day weekend, but now that the CM11 monthly update is up to the M10 release, we won't hold it against the CyanogenMod Team. The biggest change to the M build is a brand new bug tracker app, which makes it easy for users to submit anonymized bug reports to CM along with a stacktrace whenever a system app crashes.
There's also a new option to send a scrubbed bug report in the Developer Settings menu.
Did you know it's possible to unlock your Nexus 5 bootloader without wiping user data? If your device has already been rooted and relocked for optimal security, then unlocking is just a button tap away thanks to the latest update to BootUnlocker. Support for Google's latest flagship phone was just added with an update to version 1.4 of the app from XDA member segv11. Sadly, both generations of the Nexus 7 from ASUS remain unsupported.
If you haven't heard about BootUnlocker, it's a simple utility app with a single purpose: toggling the locked state of the bootloader on supported Nexus devices.
Sprint Galaxy Nexus owners, you can put down those pitchforks. Your Android 4.3 update is finally coming. Sure, it's arriving just in time for Android 4.4, but hey, it's not like anyone promised that your updates would be timely. Oh, they did? Well, it gets worse. The update is rolling out in stages over a 10 - 21 day period, and device selection is random. Some of you may still have close to a month to go.
Software Update GJ04 moves the Galaxy Nexus up to Android 4.3, and that's it. There's nothing else on the changelog to share.
At the end of the day, if this weren't a Nexus device, a three month delay wouldn't be all that bad.
Yesterday T-Mobile rolled out a relatively small OTA for the Nexus 4 bringing about a set of security improvements. As it turns out, the latest Nexus handset isn't the only one receiving the update. The Galaxy Nexus is also getting the JWR66Y firmware, and there's a manual update available for those of you who just can't bear the wait. This one is for the yakju variant of the phone, those sold through retail channels other than Google Play.
The entire firmware update is less than 2MB in size, so this is one patch you won't need to snag WiFi for. This is an incremental bump from the previous build that is probably geared at fixing a relatively new exploit or two, not something that will have all that much effect on your user experience.
If there is one thing we all eventually rely on with mobile devices, it's having a sturdy Wi-Fi connection. Whether it's because of a low data cap, you live or work somewhere with a weak cell signal, or like me, the local cellular technology is stuck in the stone age, you probably have a few wireless networks saved on your phone or tablet. While you probably take it for granted that your devices will automatically connect to these networks when they are in range, some people are finding that feature hasn't been working as expected since upgrading to Android 4.3.
The common thread among the complaints is that taking your device beyond the range of an access point for more than a few minutes can leave it unable to automatically reconnect when a signal is found later.