Android N for Nexus 7 (2013)?

[ShinOrochiX]

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.

 

[tehabe]

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

 

[khaytsus]

Must people always post these silly questions? It'll be supported by Google or it won't; nobody here would know.

 

[turdbogls]

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.

 

[DaveImagery]

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.

 

[Masteryates]

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.

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.

 

[TAG_610]

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.

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.

What about the N Preview tags for both the Nexus 7 (2013) and the Nexus 5 found on the Google Git?

 

[Masteryates]

Google Git?

 

[lupohirp]

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.

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.

 

[Masteryates]

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.

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.

 

[TAG_610]

Google Git?

I can't post links yet, but separate source and com with a period.

android.googlesourcecom/device/asus/flo/+/android-n-preview-1

 

[ShinOrochiX]

Must people always post these silly questions? It'll be supported by Google or it won't; nobody here would know.

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.

 

[ShinOrochiX]

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.

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.

 

[ShinOrochiX]

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

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.

 

[bgiesing]

What about the N Preview tags for both the Nexus 7 (2013) and the Nexus 5 found on the Google Git?

Google Git?

I can't post links yet, but separate source and com with a period.

android.googlesourcecom/device/asus/flo/+/android-n-preview-1

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.

 

[FoxysWorkplace]

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:

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.

 

[bgiesing]

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:

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

 

[lupohirp]

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:

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.

 

[ShinOrochiX]

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.

 

[pk-sanja]

Yes, some games are lagging in MM but not on Kit Kat.

Gesendet von meinem Nexus 5 mit Tapatalk