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.
I have loved everything about this tablet and is a worthy successor of my nexus 7, but since the Pixel C is technically not a "nexus" line, will Google still let us unlock the bootloader and root? I'm really hoping so because this thing has so much potential. I wanted to love the nexus 9, but the price was absolutely absurd with nothing really new to bring the table except lollipop.
Thoughts?
Sent from my XT1254 using XDA Free mobile app
Yes! Pixel C has to be up to date tablet so google has to provide ability to flash firmware images when they arrive. And Fastboot provides and easy way of flashing firmware onto a device as it requires almost no setup on linux (a fastboot binary is needed). Nexus player is an android device but still has its images online.
It could just be the first Non-Nexus device to have images hosted.
I think the only difference between the pixle and nexus is that the nexus is always built by another oem where as pixle is made house. I expect this to be like a nexus in every possible way
My prediction is this:
1. Yes the bootloader will be unlockable
2. Yes there will be factory images available
3. It is possible that the stock ROM will be a proprietary version of Android M 6.0, (hopefully not) being closed sourced.
4. The Pixel C will only be available to US residents, and difficult to obtain from outside the U.S.
I'm only speculating on this based off of previous Pixel releases, not trying to be negative. I really hope Google loosen up on this device because there really is no other tablet that I've been interested in since the Nexus 7. I really wish Google would give us some more information, at the very least about availability by country.
Edit: Well, looks like I was wrong. Good wrong though, I'm quite happy they're treating this device like a Nexus. On a whim I bought a N9 for $200 off on Black Friday. I have no regrets though, as the N9 fits my needs to a tee and I'm quite happy with it.
I'd love to be able to dual boot this with Debian.
"PK: Yes, the Pixel C will be supported on AOSP just like other Nexus devices. The bootloader can be unlocked to enable booting an alternate OS. Pixel C does not support Chromebook style recovery via USB. The firmware is open source. It is Coreboot. DisplayPort support over Type C is being worked on but we don't have a release date yet."
And the answer is...
Yes!
https://www.reddit.com/r/IAmA/comments/3w3x7p/hi_im_andrew_here_at_google_and_im_with_the_team/
Envoyé de mon LG-H815 en utilisant Tapatalk
as mentioned in another thread the pixel c uses the new unlock command, fastboot flashing unlock, introduced with the 6p.
I hope the aosp sources will be avaliable soon.
They are here!
https://developers.google.com/android/nexus/images#ryu
https://developers.google.com/android/nexus/drivers#dragon
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
After the release of the OP3T, OnePlus has decided to discontinue sales of the OP3 according to Android authority. http://www.androidauthority.com/oneplus-3-officially-discontinued-us-europe-729580/
Could this mean that sooner or later, they might drop the support of the OP3 due to how they have to work on updates for both phones? They have slightly different specs so that might mean they have to work on two different sets of updates right?
There is slight difference in OP3 and OP3T, basically in Soc. OP3T will obviously require different drivers etc and they definitely will not care for the older one. You know what, they have released 7 beta updated for OP3 but nothing worth noticeable is there in these updates except their try to push own bloatware. Some of the OEM have updated their devices to nougat but not Oneplus. If LG can make their device updated to nougat out of the box then why not Oneplus. If they release nougat for OP3 than it will have negative impact on sale of OP3T which they never let happen. They will be updating OP3T to nougat and OP3 will get it after few months
drnajmu said:
There is slight difference in OP3 and OP3T, basically in Soc. OP3T will obviously require different drivers etc and they definitely will not care for the older one. You know what, they have released 7 beta updated for OP3 but nothing worth noticeable is there in these updates except their try to push own bloatware. Some of the OEM have updated their devices to nougat but not Oneplus. If LG can make their device updated to nougat out of the box then why not Oneplus. If they release nougat for OP3 than it will have negative impact on sale of OP3T which they never let happen. They will be updating OP3T to nougat and OP3 will get it after few months
Click to expand...
Click to collapse
Both devices get Nougat this year. According to their stream updates will be brought out sameoutaniously. Also the OP2 and OPx will get Nougat but not this year.
Demian3112 said:
Both devices get Nougat this year. According to their stream updates will be brought out simultaneously. Also the OP2 and OPx will get Nougat but not this year.
Click to expand...
Click to collapse
The OPX will not get official Nougat as the 801 doesn't pass Google's certification as Qualcomm is not updating the drivers to support OpenGL ES 3.1.
quite disappointed on how quickly OP decided to destroy its great public image made after release of OP3...
lel, what did you guys expect from "LYING CARL" ? You can't trust a single word this guy says.
=dave= said:
lel, what did you guys expect from "LYING CARL" ? You can't trust a single word this guy says.
Click to expand...
Click to collapse
Absolutely true
Don't speculate. Wait and see.
OP are vastly smaller than LG or Samsung, there isn't simply the quantity of devices out there as OP can't manufacture that many. So they're taking advantage of the newer hardware and quickly updating to the newest CPU, rather than continuing to manufacture devices on older hardware. This is why OP3 has been discontinued.
Software-wise, again, they don't have the development team to get Nougat out to us 'RIGHT NOW', but we've been promised it by the end of the year on both devices. I've been very pleased with the amount of updates and community builds so far.
OP4 will hit probably six months from now and that maybe an incremental update again, unless we see a snapdragon 830 or something!
I know it's impossible to know for sure, but do you anticipate that Lineage and other ROMS will continue to be developed for the PIxel 2 series over the next year or two? The ROM section of the board seems decently active right now. I'm considering buying a Pixel 2 XL, but don't want to buy it only to have development stop over the coming months. Definitely want Android 12 when it comes out.
if you seriously want 12 when it comes out FWIW, may be better to get Pixel 3 (which has dev/beta images IIRC) since custom dev only kicks off then when Google opens sourcecode. (FWIW Pixel3 also has multiple Lineage device maintainers.) OTOH if repartition, apparently can hack beta GSI onto Pixel 2, tho the tricky shimming/patching wasn't yet able to do calls last I read https://forum.xda-developers.com/t/...oid-12-and-any-gsi-larger-than-2-6gb.4311135/ ). DotOS already claims some version of Monet theming engine FWIW. Best wishes
well, just read https://forum.xda-developers.com/t/...-rates-on-the-pixel-2xl.4329795/post-85593187 who says be wary of Pixel 3 and 2XL is better, so definitely do your research. And whichever, don't get a Verizon one (as can't unlock bootloader).