Windows Phone 7 Build 6176 is considered as RC1 ? - Windows Phone 7 General

Well, we all heard that Microsoft’s Windows Phone 7 Phone will be out the end of this year – may be starting from October 2010. Looking at the October time frame, Microsoft has only 6 months to get Windows Phone 7 OS up to speed (In a good working condition)....
http://www.machackpc.com/featured/windows-phone-7-build-6176-is-considered-as-rc1/

microsoft MAY want to be done with this by august to make it by october

How much of WP7 OS is Microsoft NOT showing the public yet???

Man I hope not. Even when unlocked the emulator is still missing a lot of functionality and release candidates are supposed to be feature complete.

Some screenshots of the RC version are available here (3 pages) : http://www.winsupersite.com/mobile/wp7_rc_shots.asp

Related

Two HTC Windows Phone 7.5 Devices Show Up At Bluetooth.Org For Certification.

More signs of a possible flood of new devices on the way to coincide with the release of the Window Phone update codenamed Mango. There are currently a few rumored HTC phones in the works with the higher hardware specs then currently available. So keep your eyes peeled and here is to hoping they are built better than the initial offerings.
Source - http://wmpoweruser.com/two-new-htc-windows-phone-7-5-handsets-pass-through-bluetooth-certification/

WP7 on unofficial devices.

I was explaining to a guy at work why the HD2 is such a great phone and the topic of WP7 came up.
I explained to him that I was about to abandon Android and switch over to a WP7 device because the market has become flooded with Android devices and "devvin" is all over the place without a concise (except for CM 7 and MIUI) back-end. WP7 development, on the other hand, seems to be pretty stable because there are so few devices running it.
Anyway. He asked if there were any other devices to which WP 7 had been ported and I was at a loss. Other than the (around 20 according to Wikipedia) few devices that officially run WP7, the HD2, as far as I know, is the only device that's capable of unofficially running WP7. Is this right? Are any other devices running WP7 unofficially?
If not, honestly, then that makes me want to hold on to my HD2 even tighter than before. It's such an amazing piece of hardware and still very able to keep up with modern phones 2 years after it's release.
HTC HD2 is getting pretty close to running WP7 as well as an HD7.
Toshiba TG01 has some WP7 ROMs available, but their functionality is quite limited at the moment.

[Q] How long do you think the device will be supported?

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.

Android N for Nexus 7 (2013)?

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

End of support?

IIRC Nexus devices are supported for 3 years from the first day in the market. Under the assumption this also applies to the pixel c, am I right to assume that in autumn 2018 the pixel c will receive its last update with no other update option? (Or should I assume that installing a usual linux distro will be a viable solution by then?)
Regards
Tom
Who knows, but I'm sure by then there will be devs building from AOSP even if Google decides to drop it, also it would be December not Autumn since the Pixel was released mid December.

Categories

Resources