Ubuntu Touch, the popular operating system’s mobile version, will be stopping support on several high-end Nexus devices— the 2012 Nexus 7, the Nexus 10, and the Galaxy Nexus. Canonical, the commercial entity behind Ubuntu, hopes to scale down focus in order to improve Ubuntu’s current version, 14.04. Making one operating system work seamlessly on multiple devices is a lot of work, and for a project so early in its life, this may be a good idea.
Plans for support on the Nexus 5 have also not been announced, so don’t expect that to come any time soon either.
Although support is being dropped in the short term, this marks an effort by Canonical to continue pushing for the long-term growth of Ubuntu Touch. The more solid and stable the product, the better.
When Google announced KitKat, they confirmed that the Samsung Galaxy Nexus had officially reached the end of its support life and that it would not see the update from 4.3 to 4.4. Of course, the entire reason many people buy these Nexus devices is so they don’t have to settle for “official” updates and can take care of it themselves, and the Galaxy Nexus is no different. Thanks to developer PlayfulGod on XDA, the Gnex finally has a fully functional KitKat ROM available so it can join the Nexus 4 and Nexus 5 with up-to-date software.
The ROM is built off of Cyanogenmod 11 source, and every major thing works, including data, phone calls, camera, etc. There are a handful of bugs left to iron out, including panorama being broken and a graphical glitch when taking screenshots (although the screenshots turn out fine) but neither of those things are going to affect the ROM in a major way.
If you’re interested, you can find the ROM below. Remember, unlocking your device and flashing custom software can void your warranty, so flash at your own risk.
An IT administrator named Bogdan Alecu has discovered that Nexus phones receiving a flood of texts may start to function a little bit differently. The Galaxy Nexus, Nexus 4, and Nexus 5 are all effected by this new exploit that causes those phones to reboot, crash the messaging app, or even disable a network connection. While other devices seem to be safe, Alecu advises that he hasn’t tested many others. The bug is coming from Class 0 SMS messages that are not regularly stored on a handset.
A developer has already taken to the Play Store to release a fix. Class0Firewall is a free app that prevents the Class 0 SMS messages from sending your handset into a tailspin. Google has told PCWorld that they are looking into the issue; however, we have no timetable on when to expect a patch.
Source: DefCamp, Class0Firewall (Play Store)
While Google has abandoned the Galaxy Nexus with Android 4.4 KitKat, that never stops the resilient devs over at XDA. A dev team by the name of “SlimRoms” has built KitKat straight from source and made it available for most variants of the Galaxy Nexus, and all was left was the Sprint Galaxy Nexus (toroplus). If you wish to flash this, you will need your bootloader to be unlocked and have a custom recovery installed. Considering this is still in alpha stages, so bugs may be prevalent.
Head over to the source link for the XDA thread and for download links.
Last week when Android 4.4 KitKat was announced, a lot of people rejoiced, but one select group of people didn’t. Those who own a Galaxy Nexus got the shocking news that they wouldn’t be getting the new chocolate treat, at least officially. Google’s reasoning is their policy to support devices for only 18 months. That policy is really meant for manufacturers, this is a Google product folks. Some say it really isn’t about the 18 month window and it’s more about drivers from Texas Instruments not getting updated.
Whatever the real reason is, Galaxy Nexus owners aren’t happy and I don’t blame them. The phone more than meets the specs and you would think Google would want to “show other manufacturers” how it’s done. Max Duckwitz isn’t sitting back and started a petition. He has well over 13,500 signatures and nearly 3,500 comments. He isn’t wasting anytime as he already sent all the signatures, comments, a quick letter, and petition text to Sundar Pichai at Google.
The Galaxy Nexus won’t be getting Android 4.4, at least officially, but if you dabble in the ROM game, you can get your taste of KitKat. The good news is that there are offerings for both the GSM Galaxy Nexus (maguro) as well as the Verizon Galaxy Nexus (toro). All of these are Alpha builds so expect bugs and glitches.
For the GSM (maguro), there is “A Taste of KitKat” from XDA member Grarak. WiFi isn’t working and there are some graphical glitches when taking screenshots, accessing the recent apps menu, and when the screen is rotating. There is also “SlimKat” from XDA member kufikugel. This one also has some graphical glitches, but WiFi is working.
The Sprint Galaxy Nexus is starting to receive Android 4.3. This update wasn’t as quick as the Play Store GNex, but I guess they didn’t do too bad here.
Unfortunately, this will be the last major update as Google already announced that Android 4.4 will not hit any Galaxy Nexi. The build for this update is JRO03U.L700GJ04 and will rollout over the next 10 to 21 days.
source: Sprint Community
The Galaxy Nexus, the device that started the “Ice Cream Sandwich-age” of Android, will unfortunately not be receiving the Android 4.4 update. This actually comes as a bit of a surprise, as Google has stated (and will continue to state) that one of Android 4.4′s main goals is to put an end to Android fragmentation, bringing support to lower end devices.
Yes, Android has had an 18 month rule— if a device is over 18 months old, it will stop receiving support.
However, the Galaxy Nexus definitely has the RAM necessary to run the new OS version. (Google has stated that 4.4 will run smoothly on devices with 500mb of RAM, which is half the amount the Galaxy Nexus offers.)
Aside from the occasional legal quirks and roadblocks, owning a Nexus device is great because you’ll always have access to factory images of your device in case you ever need to completely undo any customization or just want to start from scratch. If you happen to own a Nexus 4, 7, 10, or a GSM Galaxy Nexus, you’ll now have access to those factory images for the latest version of Google’s Android 4.3.
The Nexus 4, all older versions of the Nexus 7, the Nexus 10 and the Galaxy Nexus all have images with the build number JWR66Y. The new 2013 Nexus 7 has a different build number, build JSS15Q, but still serves the same purpose. If you’re looking for any CDMA variants of any Nexus devices, you’re unfortunately still out of luck.
source: Google Developers
For those of you that own a Verizon version of the Samsung Galaxy Nexus and are running a custom ROM then I have good news for you. Google updated its Developers site with the 4.2.2 factory image. So if you botch your phone or have to return it to Big Red you can bring it back to a stock state. Those of you on Sprint and happen to own that version of the Galaxy Nexus will be happy to know that the 4.2.1 image was also uploaded. So head on over to the source link below and find your respective image. Happy flashing!
source: Google Developers