Google has been saying that the Android 7.0 Nougat is for you and me. Of course, that is expected of the tech giant since the mobile platform is one of its many cash cows. It’s been highly anticipated since Marshmallow began rolling out to phones and tablets the past few weeks. Unlike in the past years, Google would announce the new dessert during the last quarter of each year. But for 2016, we knew as early as the Google I/O that it is working on the Android N. In fact, Developer Previews have been out even before the official name was announced at the beginning of summer.
We know rollout will be slow as in the past years. The Android team hasn’t even finished working on the Marshmallow updates so it may take a while before your mobile phone or tablet gets the chunky update.
To review, the Android Nougat brings new emojis, quick switching between apps, multi-window view, Vulkan API, Virtual Reality mode with Daydream, Doze mode, Custom Quick Settings, and Bundled Notifications. With Android 7.0, you can also take advantage of the Data Saver, Notification Controls, and Display Size management tools.
We were expecting that this year’s Nexus phones aka HTC Sailfish and Marlin aka the Pixel and Pixel C would be the first Android 7.0 Nougat device but apparently, the LG V20 beat the yet-to-be-revealed Google phones. Other devices—phones and tablets—are getting the software update although not everyone will do so officially.
Since the Android N Developer Previews were released, we’ve been getting small bites of the Nougat. We’ve also tried a few versions before Google has started to release the official build. Several smartphones from major OEMs are already running Android 7.0 Nougat. Others are still waiting for OTA notifications while some are still on beta mode. There are also the brave ones who are trying unofficial builds and doing things at their own risk.
We listed down dozens of mobile devices we know are already or soon-to-be powered by the Android Nougat OS. On top of the list are those who have the official builds–meaning they are official releases from the Android developers, manufacturers, or retailers.
OFFICIAL
The LG V20 is the first ever Android 7.0 Nougat device to be released in the market. The upcoming Pixel and Pixel XL will also be powered by the mobile OS. The Pixel C is obviously part of the list because it’s directly a Google product. Earlier this year, we were able to run system images of Android N and test apps on a discounted unit. It’s not yet available commercially but at least we know that the Pixel C can handle Nougat.
We saw Android Nougat images available for the Nexus Nexus 9, Pixel C, and Nexus Player so we can expect Android 7.0 for these devices will be ready anytime soon. A couple of weeks ago, Google announced that Nougat updates for the Nexus 6 and Nexus 9 LTE are coming soon. That’s after we learned that Telus is preparing to roll out the update for the Nexus 6P and 5X.
Just last month, T-Mobile announced the first batch of devices that will officially receive Nougat. These are the latest premium flagship phones from the top OEMs: Samsung Galaxy Note 5, Note 7, S6, S6 Edge, S6 Edge Plus, S7, S7 Edge, HTC 10, and HTC One M9.
The controversial Galaxy Note 7 will get the update in Q4. As for HTC, the Taiwanese tech giant has announced a few times already that Android Nougat is coming to the HTC 10, One A9, and One M9.
We noted before that the Galaxy S7 and S7 Edge were being tested with Android Nougat. Once the two are upgraded officially, they will finally get the Grace UX we’ve been talking about. Motorola’s Moto Z and Moto G4 are also getting the official Nougat build sometime in Q4.
BETA
Several phones and tablets are getting Android 7.0 Nougat but most of them are still in beta. Sony’s mobile division may be facing challenges these days but it’s been busy and generous with releasing software updates. Before the official builds roll out, Sony announced and actually began some beta programs like those for the Xperia X Performance.
The company even revealed a Nougat roadmap with the following models getting a taste of the Nougat: Sony Xperia XZ, X Performance, Xperia X, X Compact, Xperia XA, XA Ultra, Xperia Z5 family, Xperia Z3+, Sony Xperia Z3, and the Xperia Z4 tablet. That’s about most of the latest Xperia phones from the Japanese OEM.
The Beta Build for the Huawei P9 was released a few months ago. Earlier in the year, we noted some Android N Previews ready for some devices like the Xperia Z3 and Android One General Mobile 4G.
UNOFFICIAL ROM
Unofficial ROMs are nothing new. In the Android world, they are expected. Actually, they are something to be excited about because you’ll never know what device can be made more powerful. Most of the ROMs may be limited but it’s possible that even old devices can run the new Android Nougat. Some of the ROMs we’ve featured include the unofficial Nougat ROM for the Nexus 5. There’s the Nougat-based CM14 booting on an ancient HTC HD2 and the new OnePlus 3 plus the first-gen Android One phones.
Unofficial builds are also released for the old HP TouchPad, Raspberry Pi 3, OnePlus One, Samsung Galaxy Tab S, Nexus 5, Nexus 7, and the nAOSP ROM 7.0 for the Sony XPERIA S.
three umi devices are slated for 24/12/16
Two months after buying my first Android phone I encountered a bug which has the OS insisting that I’m short on memory when I have 6GB internal and 54GB on SD card free. I soon discovered that users have encountered this bug for several gen of OS and there is virtually no acknowledgement of it by Google or Android media. The usual user fumbling for fixes has ensued. Does Marshmallow squash this bug or does it remain an excellent reason to go iPhone?
Is it the OnePlus 3? If so, that’s not an Android issue, that’s a developer issue. I haven’t heard of this issue with any other phones.
It’s a Blu R1 HD. People with a variety of brands, models, and Android OS versions have reported this problem and have found no reliable solution.
Thanks for the info. Never looked at the Blu line of phones. I’d recommend returning it if you can and get something different.
As I have twice state, users are reporting this problem with various brands and models. It doesn’t seem to be hardware related.
You seem confused about how Android stores applications. Just because you have a 64GB SD card doesn’t mean that applications are going to store on there. It’s up to the app developers to make their applications support SD storage and even then, most developers still store some of the code in internal memory to allow them to run in the background. The measly 6GB of storage your have free on internal memory isn’t gonna handle crap. Also, your phone only has 1GB of RAM. That poor thing is suffering trying to run anything. So again, I recommend returning that phone and getting something else. The old saying still holds true in that you get what you pay for. Spending $100 on a phone is not going to get you much, yet you want to compare it to a $600 iPhone? Yes, there are going to be differences! Pick up a higher end Android phone for $350 or more and yes, you will see it easily outperform the iPhones.
This Blu R1 HD has 2GB of RAM and 16GB of internal storage. Users with far more expensive phones report the same problem. Why not do some research before you comment?
A 2014 article at IT World is headlined, “‘Insufficient Storage Available’ is one of Android’s greatest annoyances. Here’s how to fix it.”
Problem is that the fix doesn’t work for many users.
Please share these reports of other people on high end phones with this issue. I spend a lot of time in various sections of XDA-Developer and it doesn’t come up.
Sorry to disappoint you! But it is the phone. BLU unfortunately doesn’t make high end Android devices IMO. That being said, you need to try something like a HTC M9, M10, or a Galaxy device. See, with Android the type of device you have does dictate how things are stored and the options you will have with storage. As opposed to iPhone that really limit all the other things you can do.
I’m 100% completely aware of the issue you are referring to. But, unfortunately your issue has to do with the way your phone reads that SD card and the application in which you are trying access or store. The phone basically can’t recognize why there is if fragments of data your trying to access on the phone and the SD card. Solution is a higher end Android device that is designed for higher SD data storage or a higher end Android device that has a large amount of internal storage. Plus you need to keep in mind even if you had 12gb of RAM, with Android that won’t matter if you are using a brand of phone or device that doesn’t optimize their brand specific overlay for Android to work efficiently.
Furthermore, the reason you see other people with that same issue is because, most of them are purchasing lower end Android devices and are trying to use them as if they were higher end Android devices. Ex: You can’t expect a Camry to outrun a Ferrari. Just ain’t gonna happen!
You have an unsubstantiated opinion contradicted by articles and user reports online. You have made claims without doing research that prove that you are incorrect.
so much opinion :p
It means u short on internal memory. Transfer some stuff to the SD card and it’ll go away. No Android bug or anything
You seem to have ignored the details of what I have written. As I stated I have 6GB of internal memory free. I can’t even transfer a 32kb app to either internal or SD card memory. I previously transferred all that I could to the SD card. It takes only a quick google search to find that this has been happening over several generations of Android OS and on different brands of phones for users who have more then ample memory. Did you bother to google the issue before you declared it to not be a bug? Is 6GBs not enough for a 32K file? Are 54GBs not enough room for that same file? It is simply no longer possible to transfer anything from internal memory to the SD card without getting an alert that there is inadequate memory to accomplish the transfer.
PDadvisor has an article titled “How to fix Android’s ‘insufficient storage available’ error message,” which recommends clearing the cache, but that works for some users and not others, including me.