Hi guys,
Going to buy the Nexus 7 soon b/c I can get it at a good price and my current tab, LG G Pad 7, is running too slow. Now although I am not too fussed if it gets Android N or not I just want to know what you guys, who own the Nexus, think.
Will the Nexus 7 2013 get Android N, what are the chances?
P.S. The main reason I would like N is b/c of the split screen feature, my G Pad comes with such feature as standard-courtesy of LG.
On this website for End of Life policies for Android and Chromebooks for the education sector it says that the Nexus 7 (2013) is supported until July 2017 but this could also just mean security updates, I wouldn't count on it.
https://support.google.com/chrome/a/answer/6220366?hl=en
Must people always post these silly questions? It'll be supported by Google or it won't; nobody here would know.
officially? chances are very slim.
unofficially with a ROM....100% yes. this is still a highly used device (its aged so well hasn't it?) so it'll get updated by some of the awesome Developers here.
I'm waiting to see if the supposed Nexus 7 2016 comes to fruition. If so, I'm grabbing that, and won't care about putting N on my 2013 model.
DaveImagery said:
I'm waiting to see if the supposed Nexus 7 2016 comes to fruition. If so, I'm grabbing that, and won't care about putting N on my 2013 model.
Click to expand...
Click to collapse
If they only put 2GB Ram in the 2016 version it will suffer the awful performance of the Nexus 9 and Nexus 5x. Lets hope they don't make the same mistake. I'd like to see the SD820 in the new version as the Tegra chips don't handle memory well and the intel chips have some compatibility issues.
As google dumped the Nexus 4 for M I think there is no chance of the N7 2013 getting N. The Nexus 4 could have easily ran M so Google can't use the hardware excuse.
tehabe said:
On this website for End of Life policies for Android and Chromebooks for the education sector it says that the Nexus 7 (2013) is supported until July 2017 but this could also just mean security updates, I wouldn't count on it.
Click to expand...
Click to collapse
Masteryates said:
As google dumped the Nexus 4 for M I think there is no chance of the N7 2013 getting N. The Nexus 4 could have easily ran M so Google can't use the hardware excuse.
Click to expand...
Click to collapse
What about the N Preview tags for both the Nexus 7 (2013) and the Nexus 5 found on the Google Git?
Google Git?
Masteryates said:
If they only put 2GB Ram in the 2016 version it will suffer the awful performance of the Nexus 9 and Nexus 5x. Lets hope they don't make the same mistake. I'd like to see the SD820 in the new version as the Tegra chips don't handle memory well and the intel chips have some compatibility issues.
As google dumped the Nexus 4 for M I think there is no chance of the N7 2013 getting N. The Nexus 4 could have easily ran M so Google can't use the hardware excuse.
Click to expand...
Click to collapse
As reported here (https://source.android.com/devices/tech/power/mgmt.html#doze-reqs), Doze requires a sensor that N4 doesn't have. So maybe N4 could get Marshmallow, but without Doze. Also Google said that two years of updates are guaranteed, but this doesn't mean that further major update can't come to N7 2013 and N5, only that maybe can arrive, maybe not. also, if i remember correctly, Marshmallows was out on october 2015, N7 2013 was out on August 2013, more than two years then. But N7 2013 was updated to marshmallow. At this moment, i don't see features in android N that cannot be implemented in N5 and N7 2013.
lupohirp said:
As reported here (https://source.android.com/devices/tech/power/mgmt.html#doze-reqs), Doze requires a sensor that N4 doesn't have. So maybe N4 could get Marshmallow, but without Doze. Also Google said that two years of updates are guaranteed, but this doesn't mean that further major update can't come to N7 2013 and N5, only that maybe can arrive, maybe not. also, if i remember correctly, Marshmallows was out on october 2015, N7 2013 was out on August 2013, more than two years then. But N7 2013 was updated to marshmallow. At this moment, i don't see features in android N that cannot be implemented in N5 and N7 2013.
Click to expand...
Click to collapse
Thanks for the correction Lupo.
Doubt any Nexus 4 owners would buy in to that excuse from Google though. Its funny that with the 4's awful battery, it is the device that could benefit from M and doze the most.
Masteryates said:
Google Git?
Click to expand...
Click to collapse
I can't post links yet, but separate source and com with a period.
android.googlesourcecom/device/asus/flo/+/android-n-preview-1
khaytsus said:
Must people always post these silly questions? It'll be supported by Google or it won't; nobody here would know.
Click to expand...
Click to collapse
Yeah well I am only asking for people's opinions (I am new to this device/forum), lets be honest everyone, including you, would want the next android version.
lupohirp said:
As reported here (https://source.android.com/devices/tech/power/mgmt.html#doze-reqs), Doze requires a sensor that N4 doesn't have. So maybe N4 could get Marshmallow, but without Doze. Also Google said that two years of updates are guaranteed, but this doesn't mean that further major update can't come to N7 2013 and N5, only that maybe can arrive, maybe not. also, if i remember correctly, Marshmallows was out on october 2015, N7 2013 was out on August 2013, more than two years then. But N7 2013 was updated to marshmallow. At this moment, i don't see features in android N that cannot be implemented in N5 and N7 2013.
Click to expand...
Click to collapse
Thanks for the detailed insight. As you mention it is an old device we'll be lucky if we got the next version but if we don't it is fine, as a student I need a tab that works fast and that I can carry around with me. My current LG tab is running slow af hence the I bought the Nexus 7. There are rumours of there being a 2016 edition but nonetheless it will be way out of my price range.
tehabe said:
On this website for End of Life policies for Android and Chromebooks for the education sector it says that the Nexus 7 (2013) is supported until July 2017 but this could also just mean security updates, I wouldn't count on it.
https://support.google.com/chrome/a/answer/6220366?hl=en
Click to expand...
Click to collapse
Hmm, if I had to take a guess the consumer EoL would probably be sooner, I assume the education versions run on modified android firmware which will allow them to get further security updates. Who knows though-I may be wrong.
Edit: Should've multiquoted my previous posts.
TAG_610 said:
What about the N Preview tags for both the Nexus 7 (2013) and the Nexus 5 found on the Google Git?
Click to expand...
Click to collapse
Masteryates said:
Google Git?
Click to expand...
Click to collapse
TAG_610 said:
I can't post links yet, but separate source and com with a period.
android.googlesourcecom/device/asus/flo/+/android-n-preview-1
Click to expand...
Click to collapse
Don't go by those git tags as Google automatically generates them for currently supported devices at time of publish. Doesn't mean that they will be supported at time of final release.
For example with Marshmallow, N4, N7 (2012), and N10 all had preview tags on Git as they were supported at time the preview code was publish but did not get final releases.
Maybe / Maybe Not
Look more closelyer. The tag isn't some stub, I checked deb branch and there have been three commits to the tree that are deb specific. This doesn't mean there will be a release but it does mean someone is actually working on the project. Could be a N7 enthusiast at Google playing in their paid spare time Google gives it's employees. Honestly I doubt there will be a release but there may be more clues here than we think. I'll clone the last release and this "preview" and do a diff. If the result shows its worth a try I *might* have time to attempt a build and see if it will build or not. If it builds it's probably not just autogenerated but active.
If it won't build its probably purely a unintentional creation by a script. :angel:
bgiesing said:
Don't go by those git tags as Google automatically generates them for currently supported devices at time of publish. Doesn't mean that they will be supported at time of final release.
For example with Marshmallow, N4, N7 (2012), and N10 all had preview tags on Git as they were supported at time the preview code was publish but did not get final releases.
Click to expand...
Click to collapse
FoxysWorkplace said:
Look more closelyer. The tag isn't some stub, I checked deb branch and there have been three commits to the tree that are deb specific. This doesn't mean there will be a release but it does mean someone is actually working on the project. Could be a N7 enthusiast at Google playing in their paid spare time Google gives it's employees. Honestly I doubt there will be a release but there may be more clues here than we think. I'll clone the last release and this "preview" and do a diff. If the result shows its worth a try I *might* have time to attempt a build and see if it will build or not. If it builds it's probably not just autogenerated but active.
If it won't build its probably purely a unintentional creation by a script. :angel:
Click to expand...
Click to collapse
And the same thing happened last time also. The only code they released is what's required under GPL but doesn't automatically equal guaranteed release.
Ok so maybe they do release N for the device but the point is that the git tags themselves aren't a guarantee that we are getting N.
Sent from my BLU ENERGY X PLUS using Tapatalk
FoxysWorkplace said:
Look more closelyer. The tag isn't some stub, I checked deb branch and there have been three commits to the tree that are deb specific. This doesn't mean there will be a release but it does mean someone is actually working on the project. Could be a N7 enthusiast at Google playing in their paid spare time Google gives it's employees. Honestly I doubt there will be a release but there may be more clues here than we think. I'll clone the last release and this "preview" and do a diff. If the result shows its worth a try I *might* have time to attempt a build and see if it will build or not. If it builds it's probably not just autogenerated but active.
If it won't build its probably purely a unintentional creation by a script. :angel:
Click to expand...
Click to collapse
Project is active, but this doesn't mean anything. Also, if you download the sources with N-Preview Tag, you will obtain only Android 6.0.1. ANdroid N is not released to AOSP. Source code will be pushed with final release.So the only thing is wait. Howewer, don't worry. I'm planning to do a fake Nexus Rom for N5 and N7 2013 when Android N will be pushed to AOSP.
On a side note, today was the first day of using my Nexus 7 properly, I noticed choppiness whilst playing games-namely minecraft. Anyone else also experienced this? Mine is running the latest MM firmware.
Yes, some games are lagging in MM but not on Kit Kat.
Gesendet von meinem Nexus 5 mit Tapatalk
Related
Hello everyone,
We all know Android 4.4 KitKat was released today(1/11/2013). Since the source will be availible, is it possible to port it to the kindle fire(1st gen)? If yes, please make a stable rom.
Thank you and have a nice day
(Wanna get rid of CM 10.1)
It will take at least a week I am guessing, because the update "will be rolling out over the following weeks" as Google said, and then people will have to port it, so just have a little bit of patience. Also, why don't you switch to CM10.2 if you don't like what your on, or AOSP for that matter, as that runs better I personally think.
Sent from my Nexus 7 using Tapatalk
Not very likely since TI (the chip maker for the KF) won't be supporting android any more... or that's at least what I read. I'm hoping that I'm wrong though.
swaarley said:
Not very likely since TI (the chip maker for the KF) won't be supporting android any more... or that's at least what I read. I'm hoping that I'm wrong though.
Click to expand...
Click to collapse
Google said it can run on low end devices, and we do have Hashcode's 3.4 Kernel
jma9454 said:
It will take at least a week I am guessing, because the update "will be rolling out over the following weeks" as Google said, and then people will have to port it, so just have a little bit of patience. Also, why don't you switch to CM10.2 if you don't like what your on, or AOSP for that matter, as that runs better I personally think.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
I cannot change too quickly. Mom allowed me only for CM 10.1, and now for CM 11(It will come, right?). Cannot do CM 10.2.
That kernel is not ready for primetime, also there is code that the chip maker will have to release code for it. See hash and others posting about it:
http://forum.xda-developers.com/showthread.php?t=1591850&page=276
Google says that kitkat can run on devices that have as low as 512mb RAM. We can sure overclock our processor to 1.2 GHz
Sent from my air powered ceiling fan
swaarley said:
That kernel is not ready for primetime, also there is code that the chip maker will have to release code for it. See hash and others posting about it:
http://forum.xda-developers.com/showthread.php?t=1591850&page=276
Click to expand...
Click to collapse
You know, hash doesn't say anything about not getting it to work. In my opinion he clearly stated that he is really trying to get 4.4 to work. It was others that were being sceptical.
Sent from my Nexus 7 using Tapatalk
True, the first ROM for any android version for our device is done by hash. Same case for 4.1,4.2,4.3,4.3.1
Sent from my air powered ceiling fan
As was previously stated, Texas Instruments is out of the microprocessor chip game and they have stopped supporting the binaries for newer versions of Android. It wasn't directly stated by Google but it's very likely that it was for that reason that they chose not to support the Galaxy Nexus in the newest iteration of Android, as it also uses a TI chip. I'd like to think that it would be possible to run Android 4.4 on the old Kindle Fire, especially since it lags pretty badly on stock, but I am afraid that the likelihood is fairly low.
True that it also what is written on hash's thread for the new kernel. He sure I trying hard and so my hopes are pretty much alive
Sent from my air powered ceiling fan
sparkplugDev said:
As was previously stated, Texas Instruments is out of the microprocessor chip game and they have stopped supporting the binaries for newer versions of Android. It wasn't directly stated by Google but it's very likely that it was for that reason that they chose not to support the Galaxy Nexus in the newest iteration of Android, as it also uses a TI chip. I'd like to think that it would be possible to run Android 4.4 on the old Kindle Fire, especially since it lags pretty badly on stock, but I am afraid that the likelihood is fairly low.
Click to expand...
Click to collapse
They already have 4.4 Roms for the Verizon galaxy nexus...it won't get official Google support but they have gotten Roms for it:
Example:http://forum.xda-developers.com/showthread.php?t=2508073
So,is it possible? Yes. Will it take a while? Probably....don't expect it soon but as others have said hashcode is working on
It...keep your fingers crossed
Jacobloveskindles said:
They already have 4.4 Roms for the Verizon galaxy nexus...it won't get official Google support but they have gotten Roms for it:
Example:http://forum.xda-developers.com/showthread.php?t=2508073
So,is it possible? Yes. Will it take a while? Probably....don't expect it soon but as others have said hashcode is working on
It...keep your fingers crossed
Click to expand...
Click to collapse
4.3 binaries can be hacked for 4.4.
Sent from my SGH-T959 using xda app-developers app
Hey guys! The wait is almost over.
There is already a build, no WiFi
Sent from my air powered ceiling fan
Stable build of cm 11 released, I think we can close this thread.
http://forum.xda-developers.com/showthread.php?p=47706499#post47706499
Moral: Lets always be optimistic (At least when its sensible)!
Sent from my air powered ceiling fan
Even though Galaxy Nexus is no more officialy supported by Google and stuck at Android 4.3, KitKat Roms emerged quickly and evolve rapidly - thanks to our crazy devs!!! :victory: So how you all handling this? Still at 4.3... already jumped to a 4.4 rom?
I know it took a long way for 4.3 roms to reach that point where everything works near perfect and I think that Cataclysm or SlimBean are such examples. So, some will prefer the comfort of this instead of jumping into the unknown and start dealing with bugs and the trial and error procedure???
As I write this Android 4.4.2 is rolling to newer Nexus devices, my new Nexus 7 already running this and something tells me, since none of the factory images for 4.4.1 and 4.4.2 are officialy on google's page, that another update maybe coming soon. Since our phone is not officialy supported, devs will strugle merging new code to their sources and adapting it for gnex. How do you see this evolving?
To end this, it's been 2 years after the release of GNEX and our forum still is in the top 5 list. Quite impressive if you ask me. Tell that to Google... Galaxy Nexus is a legendary phone even though it's not the sharpest out there. And I am sure its "endurance" over time, will make it even more legendary!
PS: Working on a cool Zooper Skin. Will let u know when it's out!
It will continue, but the gnex population will gradually move on. The new incomers will not likely join at the rate the existing users leave to upgrade to a new device.
If it's any indication, Nexus One and Nexus S development are still continuing and they are older than the Galaxy Nexus. At some point when newer android versions get too resource intensive (KK tried to improve the memory management) then we will start seeing users preferring to stick with an older version.
I will continue with my Galaxy nexus and I'm still very happy with it especially so because of the talented developers here at XDA. I'm currently using the 4.4 KK rom : [ROM] [UNOFFICIAL] CyanogenMod 11 for the Samsung Galaxy Nexus with gapps 20131207. This ROM is now my daily driver and I won't be going back to 4.3 :good:
Thanks for this post, I'll subscribe!
myself, I've been thinking of sticking with Cataclysm for a while. But can I ask those who already use a 4.4 rom if they noticed any signifcant improvement on battery life or multitasking?
wrong thread. sorry
itasoulas said:
Even though Galaxy Nexus is no more officialy supported by Google and stuck at Android 4.3, KitKat Roms emerged quickly and evolve rapidly - thanks to our crazy devs!!! :victory: So how you all handling this? Still at 4.3... already jumped to a 4.4 rom?
I know it took a long way for 4.3 roms to reach that point where everything works near perfect and I think that Cataclysm or SlimBean are such examples. So, some will prefer the comfort of this instead of jumping into the unknown and start dealing with bugs and the trial and error procedure???
As I write this Android 4.4.2 is rolling to newer Nexus devices, my new Nexus 7 already running this and something tells me, since none of the factory images for 4.4.1 and 4.4.2 are officialy on google's page, that another update maybe coming soon. Since our phone is not officialy supported, devs will strugle merging new code to their sources and adapting it for gnex. How do you see this evolving?
To end this, it's been 2 years after the release of GNEX and our forum still is in the top 5 list. Quite impressive if you ask me. Tell that to Google... Galaxy Nexus is a legendary phone even though it's not the sharpest out there. And I am sure its "endurance" over time, will make it even more legendary!
PS: Working on a cool Zooper Skin. Will let u know when it's out!
Click to expand...
Click to collapse
I'm not one to sit by idly and wait for confirmation of a stable new Android version. When 4.4 was released I flashed it right away. Whats the fun in not "jumping into the unknown"?
I dont think small updates are that hard for developers to merge into our current builds. We are already on 4.4.1 and I'm sure that 4.4.2 will be on our devices soon as well.
KitKat has been running great on my device. I dont know of any issues we have now that havent been fixed yet.
jsgraphicart said:
I'm not one to sit by idly and wait for confirmation of a stable new Android version. Wn 4.4 was released I flashed it right away. Whats the fun in not "jumping into the unknown"?
I dont think small updates are that hard for developers to merge into our current builds. We are already on 4.4.1 and I'm sure that 4.4.2 will be on our devices soon as well.
KitKat has been running great on my device. I dont know of any issues we have now that havent been fixed yet.
Click to expand...
Click to collapse
Well...my GPS could be better. I'm seeing at best 30ft accuracy with about 8 satellites locked in with pretty low SNR values.
Im still on 4.3, Slimbean. Waiting for Slimkat to evolve just a litle bit more :good:
alpha-niner64 said:
Well...my GPS could be better. I'm seeing at best 30ft accuracy with about 8 satellites locked in with pretty low SNR values.
Click to expand...
Click to collapse
I haven't had any issues with GPS. It pinpoints pretty fast for me.
And by the way, cyanogenmod just updated us to 4.4.2.
I will be continuing to use my Galaxy Nexus until the 'Nexus 6', it can totally hold up to most of the competition. Currently using the last 4.4.1 Galaxy Nexus Maguro CM11 ROM with ASKP/Franco/Mpokang/Fancy/Stock kernel.
I mean official-wise and community-wise. I've never owned a tablet and want to buy this one(used, unfortunately due to tight budget), I am more of a developer(though have no plans of developing right now) so might want to tweak the device here and there.
dikidera said:
I mean official-wise and community-wise. I've never owned a tablet and want to buy this one(used, unfortunately due to tight budget), I am more of a developer(though have no plans of developing right now) so might want to tweak the device here and there.
Click to expand...
Click to collapse
Considering that the OG Nexus 7 is still supported, I'd say you have at LEAST a year left, but likely 2-3
Officially goog supports devices for 18 months, which means 3 major updates (as they generally release a major update in the summer and winter)
While goog does not announce devices ahead of time, it would not be unreasonable to expect a 2014 N7 in the summer.
The 2012 N7 will be recieving it's final update soon, there is a high likelyhood that 4.4.3 will be coming in the future.
It will be unlikely that it gets 4.5/5.0/whatever is coming in the summer.
Unofficially even the NS is still supported officially by CM and the like. (there will be a point that they have to drop it from official support like they did for the N1 though)
Unofficially unofficially even the N1 has an unofficial CM11 rom, so rom wise it is still reasonably up to date.
It really depends on how far on the Official support <--- ---> Unofficial support line you are on.
http://www.android.gs/android-5-0-l...5-nexus-7-and-nexus-10-expected-release-date/
sounds interesting.. Whata you think?
I think that if it screws up things as badly as Kit-Kat did, I may have to go look at an (grits teeth) iPhone.
the link and the article says nexus 4,5,7 while your title includes gnex as well.
I highly doubt that a phone nearly three years old that didn't receive the last android increment would get a new one. We'll definitely see ports of the Nexus 4's ROMs to gnex, just like 4.4, but no official support.
Wait Nexus 10 will receive Android l but the gnex wont? Weird, the nexus 10 is too old for support too..
Sent from my Galaxy Nexus using XDA Free mobile app
The problem is not how old it is. The problem is that T.I. won't release the source code and so gnex can't be supported.
Croc97 said:
The problem is not how old it is. The problem is that T.I. won't release the source code and so gnex can't be supported.
Click to expand...
Click to collapse
Sorry if I am noob but there was the same problem with Android KitKat and TI, or?
Yes, the same problem
Croc97 said:
The problem is not how old it is. The problem is that T.I. won't release the source code and so gnex can't be supported.
Click to expand...
Click to collapse
TI is not the problem, it's well documented and open sourced... The problem is the GPU vendor Imagination Technologies that won't release the source for it's PowerVR drivers even though the GPU is so old and obsolete... TI wanted to make IT release the source when TI released the kernel source, but IT backed out at the last moment. If that had happened, we would have a completely open source device, a dream for every developer. Oh well...
NExus factory images live today. We are suppse to get it but end of this year or start of next. Is anyone out there planning on porting this maybe to both models of our phone? Im on Z008 Just curious
cell2011 said:
NExus factory images live today. We are suppse to get it but end of this year or start of next. Is anyone out there planning on porting this maybe to both models of our phone? Im on Z008 Just curious
Click to expand...
Click to collapse
If the source code isn't released we can't do anything. So it's probably not even the dev's fault as much as it is Google's.
All we can do is wait.
cell2011 said:
NExus factory images live today. We are suppse to get it but end of this year or start of next. Is anyone out there planning on porting this maybe to both models of our phone? Im on Z008 Just curious
Click to expand...
Click to collapse
Hate to be the bearer of bad news...
Ports assume the two devices (the base device, and the one to port to) are very similar (same chipset, et cetera). A good example (I used to use HTC) is the Sensation was a very good base for the MyTouch 4G Slide (they even shared the same battery design/size).
Unfortunately the Zenfone 2 and either of the new Nexus devices are worlds apart from each other. They don't share the same architecture, let alone chipset. We would be better off piggybacking off the work of the ASUS Fonepad 7 FE375CG (Z3560 Chipset) or the Asus Memo Pad 8 ME581CL (Z3580) - but in reality, in terms of updates - it's more likely we would be the base for those devices in a few months time.
Sorry.
---------- Post added at 20:36 ---------- Previous post was at 20:33 ----------
AkiroX said:
If the source code isn't released we can't do anything. So it's probably not even the dev's fault as much as it is Google's.
All we can do is wait.
Click to expand...
Click to collapse
That's right, all we can do is wait, then build from source once available.
Porting has it's place, but it can be a gong-show.
Source already available
We should wait for devs to build it ?
AL_IRAQI said:
Source already available
We should wait for devs to build it ?
Click to expand...
Click to collapse
AOSP is available, but now we have to wait to have CM13 in a manageable state. I don't imagine cpalmer and jrior001 will put on the brakes with CM12.1 to build straight from AOSP.
ROMe wasn't built in a day, and it will be months before CyanogenMod will be able to have the AOSP source modified for the new CM13 and reach the coveted milestone one.
Yap, waiting for you too @joel.maxuel for working on it
allasca said:
Yap, waiting for you too @joel.maxuel for working on it
Click to expand...
Click to collapse
Why am I being thrown under the bus? :silly:
In all seriousness, if CarbonROM continues to base their stuff off of CM (which I heard talk of that changing), this time around they may be once again months behind CM in terms of an official product (e.g, none of their devices have hit official status yet this round, or at least as of last night).
Not to speak ill of course, which is why I am curious of the route that does not involve basing off of CyanogenMod.
No guarantees with my involvement to 6.0, but I am interested in the job. I just can't predict what my life demands are going to be like in the spring (time seems tight right now, but I manage).
My short and medium term plans is to keep the 5.1 builds going, hopefully even after Carbon calls it quits for this branch to focus on the new one. The only possible things stopping me are:
Carbon leaves lp5.1.1 branch perfect, meaning I don't even have to do monthlies anymore (also means no future security issues)
CyanogenMod breaks their sources badly (has happened recently when Carbon couldn't keep up)
I get the official stock 6.0 image which ends up breaking modem usage - leaving me unable to properly downgrade to 5.1 to test
It feels like with this plan, someone is going to beat me to the punch by building a CarbonROM mm-6.0 ahead of me. Which is why at some point, I will (probably) be doing builds in parallel. But we shall see when we get there.
Just read this: http://arstechnica.com/gadgets/2015/10/android-6-0-marshmallow-thoroughly-reviewed/
Doesn't seem much for us CM12.1 users to get very excited about anyway. Material design not changed from Lollipop, Google Now launcher already updated with the changes, selectable app permissions already included in CM12.1 via Privacy Guard, fingerprint api and 4K display stuff irrelevant to our zenfones...
Personally, I think a stable CM12.1 (5.1.1) build is more important. In fact, the unofficial build we already have is stable and very nearly there, but I would rather see the last few kinks ironed out and official status before any time is put into 6.0
Most importantly, it should support 64bit for the z00a. Any news on this?
Sent from my iPhone using Tapatalk
The next month, asus update android 5.1 for zenfine 2, maybe 6.0 ? I don't know this,