one sided promise from microsoft (re:updates) is pure fail. all parties should be brought onboard and each held accountable
http://www.engadget.com/2011/05/10/google-partners-with-oems-and-carriers-to-guarantee-android-upda/
Wow, I saw AT&T on the picture, I must relook at it.
It will never happen because all the OEM's and carriers involved seem to want Microsoft and WP7 to fail.
Look at the Zune hardware. My brother had a Zune since Day 1 and he got every update and new release from Microsoft, no problem. I don't think it's a Microsoft issue, I think it's a carrier issue.
Well, that announcement says Android phones will be supported for 18 months. It doesn't say updates will be instant, OEMs won't take weeks to develop ROMs and carriers won't take weeks "testing" them.
vangrieg said:
It doesn't say updates will be instant, OEMs won't take weeks to develop ROMs and carriers won't take weeks "testing" them.
Click to expand...
Click to collapse
if you read the live update, it says:
"12:34PM New guidelines! Man, this is going to be huge. Google's laying out a timeline for how long it'll take a device to get updated once a new build is let loose, as well as how long it'll be updated beyond that."
Google and Apple are both more powerful and influential in the mobile space than Microsoft right now. I don't think Microsoft is really in the position to dictate anything to anyone right now.
And what exactly are these guidelines? Three days for a new ROM from HTC with a new Sense on it?
I mean, this is great news for Android, but there's nothing so far that says anything real about what the update experience will be.
I know it's trendy to bash MS, but WP7 has seen four updates already. And the last one was cumulative, by the way.
I don't know, I have been receiving my updates when MS release them; other than the first one that took one or two weeks every other have been the same day (but I’m not in USA).
http://www.engadget.com/2011/05/10/google-clarifies-18-month-android-upgrade-program-details-far-f/
When pressed about how long it'd take updates to flow to phones after given the thumbs-up by Google itself, there's no hard news to report. In fact, the details there are still being hashed out.
To quote Google, "It's a logistics problem." We can only imagine. Trying to get every Android partner to follow a timeline for releases has to be a complete and utter nightmare, but the company seems certain that these stipulations won't cripple anyone's ability to innovate on their skins (or have too little time to make the needed changes).
We would've loved to hear a specific figure that we could start holding phone manufacturers to, but alas, it isn't to be. The only hard number thrown out today is 18 months. That's how long future hardware will be in the support cycle (at least, anyway), so you'll "soon" be able to count on your next Android device receiving all applicable updates for 1.5 years after purchase.
The guideline is yet to be hashed out. That's why they practically included everyone in the group to come up with a guide line. The only reason AT&T is included is because AT&T wants to make sure the final guideline doesn't put it in the spotlight again, like must release updates within 6 months of Google release That will never happen. I'm pretty sure the final guide line will be 12-month (from Google release the code and you see it on your phone), i.e. totally worthless and waste of time. Android is an open source platform, Google has no say about who can use the code and when they need to release the updates. The only thing Google can do is withheld Android market support.
And if they take longer than the set time frame? What happens?
Sent from my SGH-i917 using XDA Windows Phone 7 App
Nothing would happen. It is called guide line, not rules.
Well then, that'll really be a game changer then... /sarcasm
Where is the news in this?
Sent from my SGH-i917 using XDA Windows Phone 7 App
munkeyphyst said:
Well then, that'll really be a game changer then... /sarcasm
Where is the news in this?
Sent from my SGH-i917 using XDA Windows Phone 7 App
Click to expand...
Click to collapse
There is none. FWIW MS has "guidelines" on updates as well, i.e. that carriers cannot block two consecutive updates.
-R
I smell a publicity fail from Google.
Well I have a wp7 and an android phone, I have to say there is no reason the OEMs cannot make their addtions such as the sense UI to be a replacement, that can be removed and updated seperately from the core OS. If they did that then it would allow for quicker updates.
In the past there were almost no updates done to phone other than small ones that were carrier specific (ie settings or patches) but major upgrades did not really happen. I would not be surprised if eventually updates to the phones to start costing money, much like a new version of OS X or a new version of windows does on a PC.
It's not a timeline.
It's just enforcing devices to be supported for 18 months.
It doesn't mean the manufacturers/carriers will have x amount of days after an android update to release said update. They can still release a phone with FroYo, and take 17 months to release gingerbread for that phone.
Also, it depends on whether the device's hardware supports the update and knowing Andorid manufacturers like HTC they'll just put a ROM chip too small to take any major updates in the phone, etc. Your Evo 4.0 can't support Sense 3.0? Good luck getting that update! HTC will not "downgrade" an Evo 4G from Sense 2 to Stock Android...
They are still trying to get the details panned out, but I'm not getting my hopes up. There are still phones out there sending SMS/MMS to the wrong contacts because the manufacturers don't even prioritize security updates for their phones (which, IMO, is a MUCH bigger issues than even large feature updates...). Android is a huge, hot mess when it comes to updates.
bill.g said:
Well I have a wp7 and an android phone, I have to say there is no reason the OEMs cannot make their addtions such as the sense UI to be a replacement, that can be removed and updated seperately from the core OS. If they did that then it would allow for quicker updates.
In the past there were almost no updates done to phone other than small ones that were carrier specific (ie settings or patches) but major upgrades did not really happen. I would not be surprised if eventually updates to the phones to start costing money, much like a new version of OS X or a new version of windows does on a PC.
Click to expand...
Click to collapse
Are you a developer?
Those aren't themes. They're deep customizations many of which have access to parts of the system that would require a "normal" app to run with Super User permissions. You can't release much of that as an App in the marketplace... Not to mention, they would just end up getting pirated by everyone and at worse breaking a bunch of phones that weren't designed to run the software (freezing them, reboot loops, making them unbootable, etc.).
There's also the issue of drivers, because different manufacturers use dispirate hardware configurations with screens, SoCs, cameras, etc. from dispirate sources. Getting all of that to work on an update is MUCH harder than getting the skins functional.
You people (generally speaking) really think the skins are the issue? They are not. Android (specifically, Linux) is the issue. The skins are easy as hell. The latest Epic 4G Gingerbread Leak has a working TouchWiz, but most of the phone/smartphone functionality is broken. That's a great example on just how easy porting the skins form version to version is. Skins typically aren't that sensitive to kernal ABI changes - device drivers ARE.
The fact that Android is based on Linux by default ensures that updates will have issues because it inherits many of Linux's issues. A Windows Mobile 6.0 update could in many cases just reuse drivers developed for Windows Mobile 5.0the same way Windows 7 can use many Windows XP drivers without any issues.
Linux doesn't have this type of backward/forward compatibility. That's why those leaked updates often have close to nothing working on them (No Wifi, no calls, no this, no that, etc.). Linux doesn't have a stable ABI for driver developers. Kernel updates can break any and/or everything. This means that the turnaround for updates is much longer than it will be for something like WP7.
The biggest issue with Android is the fact that Manufacturers and Carriers do not even prioritize critical security updates, and Google seems intent on not patching and quickly propagating patches for exploits used to root devices. Which is nice for tinkerers, but can be an issue when a malware uses that exploit on someone's device to perform malicious actions...
N8ter said:
It's not a timeline.
It's just enforcing devices to be supported for 18 months.
It doesn't mean the manufacturers/carriers will have x amount of days after an android update to release said update. They can still release a phone with FroYo, and take 17 months to release gingerbread for that phone.
Click to expand...
Click to collapse
I'm pretty sure they said timely updates. Which means they are going to work out some sort of guidelines on how long it takes for the updates to get pushed out. What that actually is remains to be seen though.
Related
So one of Microsoft's big features for WP7 over WM is that OS updates can be sent out directly by MS to all models, eliminating the previous delays from device manufacturers and operators. The great benefit here is not only for all users getting access to all new OS features, but a really important aspect is limiting fragmentation of the platform for developers. I.e. Developers don't need the huge hassle of trying to support all types of hardware and OS to get the highest number of users for their app. This is what killed Windows Mobile, and ultimately is going to kill Android if you read the story about Angry Birds.
So how about a vote? Do you think that Microsoft will hold up to the promise that they will release the OS updates to all WP7 hardware at the same time?
Will they? Who knows. But if they don't they will have effectively abandoned the smartphone market permanently because the number of people left who would believe a word they say about anything wouldn't be enough to sustain a small tech company. I can't imagine Microsoft is that stupid but they did abandon it once already.
markgamber said:
Will they? Who knows. But if they don't they will have effectively abandoned the smartphone market permanently because the number of people left who would believe a word they say about anything wouldn't be enough to sustain a small tech company. I can't imagine Microsoft is that stupid but they did abandon it once already.
Click to expand...
Click to collapse
Wasn't once, Sidekick anyone?
I think that they will update all the devices at the same time and I think that all of the new WP7 devices have a good amount of sales and so they should update all of them.
I don't think you will see updates all at the same time, i think you will see them based upon carriers and headsets but "Around" the same time. I don't think MS would want to push an update all at once unless its just a core update and doesn't impact carrier requirements or device specific issues.
blahism said:
I don't think you will see updates all at the same time, i think you will see them based upon carriers and headsets but "Around" the same time. I don't think MS would want to push an update all at once unless its just a core update and doesn't impact carrier requirements or device specific issues.
Click to expand...
Click to collapse
I think you raised 2 interesting points there. Say there is a device specific issue, does the manufacturer submit that to MS for inclusion in an update to that particular device? What if they don't bother? What if MS make a new feature in the OS that requires a new driver from the device manufacturer? If they don't bother then its deadlock, and in that case this situation is no better than with Windows Mobile of leaving all updates to the manufacturer. Personally I think MS are in big trouble here if they haven't thought this through completely...
indiekiduk said:
I think you raised 2 interesting points there. Say there is a device specific issue, does the manufacturer submit that to MS for inclusion in an update to that particular device? What if they don't bother? What if MS make a new feature in the OS that requires a new driver from the device manufacturer? If they don't bother then its deadlock, and in that case this situation is no better than with Windows Mobile of leaving all updates to the manufacturer. Personally I think MS are in big trouble here if they haven't thought this through completely...
Click to expand...
Click to collapse
If an OEM wants to push a device-specific update, they submit it to Microsoft and Microsoft will push it out after approval (the carrier may need to approve as well). Microsoft, of course, could potentially fix this themselves if the OEM refuses to fix it but I can't imagine that happening.
Microsoft has developed a vast majority of the drivers. Again, I just can't see Microsoft making a new feature that...
1. Relies on a driver and/or...
2. The driver isn't written by MS
They've thought this through pretty well. Some more explanation of the timing and carrier approval can be found here.
http://windowsphonesecrets.com/2010...-and-carriers-ability-to-block-those-updates/
If you consider how HTC does it, they add their custom features in an app. HTC has wanted to incorporate Sense into their WP7 offerings. But MS has not allowed it. Instead they compensate by adding Sense-like features to the HTC Hub. I believe this is the extent of any customization among various handset makers.
RustyGrom said:
They've thought this through pretty well. Some more explanation of the timing and carrier approval can be found here.
http://windowsphonesecrets.com/2010...-and-carriers-ability-to-block-those-updates/
Click to expand...
Click to collapse
So Paul Thurrott says that (to prevent fragmentation) if an operator/handset manufacturer blocks their devices from an OS update then they can't blog the next one and it's automatically sent out. That sounds absolutely mental!
indiekiduk said:
So Paul Thurrott says that (to prevent fragmentation) if an operator/handset manufacturer blocks their devices from an OS update then they can't blog the next one and it's automatically sent out. That sounds absolutely mental!
Click to expand...
Click to collapse
I agree that it's definitely a bit strange. But let's just see how this works out in practice. In theory Android can get updates super fast and in theory the carriers can block iPhone updates. Microsoft is still controlling the process, not the OEMs or carriers. The carriers understandably don't want to run untested code on their networks. Microsoft is giving them the option to delay/block. If they abuse it, Microsoft could just give them the middle finger and release them directly. It sounds like the carriers are going to play ball. The ones that don't will certainly get a bad rap and could lose customers over it.
We certainly do not want the mess that is the Android update process, with Google, the Carriers and the OEM's all having a say in when updates go out!
adesonic said:
We certainly do not want the mess that is the Android update process, with Google, the Carriers and the OEM's all having a say in when updates go out!
Click to expand...
Click to collapse
Ugh no, Google phones get the update first and fast. As of right now Google has only one phone.
Its all the other Android phones that have this problem with OEMs, and carriers.
WP7 will be just like the Nexus One. All WP7 devices will get updated regardless of carriers. If your carrier wont allow the OTA update then just connect to Zune.
I also think the updates will be regional.
Sent from my GT-I9000 using Tapatalk
adesonic said:
We certainly do not want the mess that is the Android update process, with Google, the Carriers and the OEM's all having a say in when updates go out!
Click to expand...
Click to collapse
That's the kind of crap that killed WinMo for me. Three times with three different phones I ran into the problem of video "tearing". Three times I emailed Microsoft support, HTC support and AT&T support about the problem and three times they were all content to point fingers at each other. Microsoft says it was a problem with HTC's drivers. HTC says it was a problem with the carrier not approving whatever updates and AT&T says if you want to solve the problem buy this new phone. And I did that twice to find the latest and greatest had the same problem, no one actually did anything. What was worse was finding updates on HTC's site that I couldn't apply to my phone because they were tied to particular carriers and my carrier, of course, wasn't one of them. The worst kind of planned obsolescence. That was when I said the hell with WinMo and bought an iPhone and all that garbage went away. When it had a problem, I went to Apple. Period. Updates came from Apple. Period. And they've only recently stopped updating the original iPhone after how long? Apple cut out the carrier for a reason and has set the bar that Microsoft should at least have the decency to meet if not exceed if they expect to be taken seriously.
vetvito said:
Ugh no, Google phones get the update first and fast. As of right now Google has only one phone.
Its all the other Android phones that have this problem with OEMs, and carriers.
WP7 will be just like the Nexus One. All WP7 devices will get updated regardless of carriers. If your carrier wont allow the OTA update then just connect to Zune.
I also think the updates will be regional.
Sent from my GT-I9000 using Tapatalk
Click to expand...
Click to collapse
I agree things were safer for users with the Nexus one, but they've stopped selling it now for whatever reason. I'd love to find out why they decided to do that because that model was a major advantage. All new Android users are going to hit this issue which is what killed WinMo as stated by markgamber.
Also you can't really say what will happen with WP7 because it remains to be seen what will actually happen when its update time. Actually it won't be until the 2nd update we'll find out if people with the old models are screwed over. It'll actually be less of a big deal if Microsoft take 1 year between OS updates because most users will want new hardware anyway, however it could still be a major disaster if manufacturers blame MS for pushing out an untested OS upgrade that breaks thousands of phones. I expect there will be some exemption like hardware of over 2 years old does not get upgrades from MS, that would get them off the hook slightly.
I agree that Apple is great for the consumer, if there is any problem Apple fix it, they control the whole experience, anything you buy on the app store will work on hardware up to 2 years old. However for developers its not such a great picture. The app store just breaks even, Apple aren't interested in app developers being successful, they only built the app store because jailbreaks were doing it anyway, previously they only planned for javascript web apps, and if anyone tries to do anything innovative outside the restrictions of the SDK their app gets banned and they get threatened their developer account will be cancelled. However there was a some money to be made by some lucky people, and everyone else made at least more than building windows mobile apps in the old days. Anyway Apple make all their money from the hardware they don't need to make money from some 3rd party dev making a good app. Google also don't care about developers, the market place is terrible and its widely known that devs with apps on both platforms get like 0.3% of their sales on Android. But as with Apple, Google don't care about the developers either. With Android, Google attract phone manufacturers by offering an OS for free, which they used to need to pay MS $30 per license or whatever. And by having tons of phones out there, Google make a ton of cash from the ads in the built in apps google search, and google maps. They have no need to support developers, and if the platform becomes fragmented they don't care because as long as they sell more phones they make more money.
It remains to be seen what the point of the WP7 marketplace is to MS. My friend has the #1 shooter app and sells 1 a day so MS will be running the store at a loss. And if they need to give WP7 away for free to compete with Android for traction there really is no hope.
You guys bring up some really great points. I am starting to think that the reason Apple stayed with At&t had something to do with updates.
To hopefully add on to this great discussion I think that the US carrier market is in for a real change soon. Every day I see prices coming down and carriers having more and more of the same features. Once carriers are handing out the exact same features it might not be that big of a deal to have MS release all updates. Other countries are way more competitive with their carrier choices and I think US will have to evolve because users demand it.
bowpay said:
You guys bring up some really great points. I am starting to think that the reason Apple stayed with At&t had something to do with updates.
To hopefully add on to this great discussion I think that the US carrier market is in for a real change soon. Every day I see prices coming down and carriers having more and more of the same features. Once carriers are handing out the exact same features it might not be that big of a deal to have MS release all updates. Other countries are way more competitive with their carrier choices and I think US will have to evolve because users demand it.
Click to expand...
Click to collapse
Just a bit of a correction:
iPhone stayed with AT&T on the domestic market, it is deployed across various providers on the international market.
To be honest I'm very curious about the update process. It's not true that all WP7 devices have got the same features. At the moment I've got HTC Trophy on Vodafone and HTC HD7 on O2. The same system but different search providers in IE, different regional keyboards available, different system languages, different settings for adding email accounts etc.. So it seems like every phone has carrier specific rom and I believe carriers would like to keep it that way. It looks like current roms are miles away from one unified rom as we see on iPhone.
Regardless of how it is made available I have heard that an update including copy /paste will be ready end Jan...
robart76 said:
To be honest I'm very curious about the update process. It's not true that all WP7 devices have got the same features. At the moment I've got HTC Trophy on Vodafone and HTC HD7 on O2. The same system but different search providers in IE, different regional keyboards available, different system languages, different settings for adding email accounts etc.. So it seems like every phone has carrier specific rom and I believe carriers would like to keep it that way. It looks like current roms are miles away from one unified rom as we see on iPhone.
Click to expand...
Click to collapse
That's a good point.
Sent from my GT-I9000 using Tapatalk
robart76 said:
To be honest I'm very curious about the update process. It's not true that all WP7 devices have got the same features. At the moment I've got HTC Trophy on Vodafone and HTC HD7 on O2. The same system but different search providers in IE, different regional keyboards available, different system languages, different settings for adding email accounts etc.. So it seems like every phone has carrier specific rom and I believe carriers would like to keep it that way. It looks like current roms are miles away from one unified rom as we see on iPhone.
Click to expand...
Click to collapse
The only thing that matters is that a given program runs on all WP7 phones equally. That's where Apple currently excels and why Android has been called "fragmented". What they look like and what programs are included with a given phone on a given carrier don't matter.
Paul Thurrott from Windows Phone Secrets have revealed, well, some secrets about the upcoming Windows Phone 7 updates.
He writes that we can expect two updates this year – the first expected to be announced this week, but only pushed in February by carriers, will be called NoDo (for no donuts), will bring support for the Qualcomm 7×30 smart phone chipset, a CDMA location stack, and a number of software fixes.
Of note is that the Snapdragon-based Qualcomm 7×30 chipset comes with HDMI output and the ability to play back 720p video on both its host device and a HDTV. It also supports Flash 10.1.
The next Mango, will come some time later in the year, and bring Internet Explorer 9 with with the Trident 5 rendering engine, HTML 5 and Silverlight, and gesture support. This 75xx (actually version 7.2) update will apparently bring additional, unrelated features as well.
Paul also mentions that Microsoft does not intend to push a number of small updates, but only a few large updates per year, which should mean long waits between each one.
Source:
wpcentral.com/thurrott-details-2011-wp7-updates-mango-and-nodo-as-no-donuts
wmpoweruser.com/windows-phone-7-updates-nodo-and-mango-coming/
I still believe that we'll see at least 3 updates in the year. 2 small ones and one large one.
Carriers could hold up and update for 1 cycle. That "advantage" would seem close to useless if the cycles could be almost a year apart.
You misspoke when you said updates are pushed out by carriers. Updates are released by Microsoft but tested by carriers before officially released.
From the article:
Thurrott reports that NoDo will RTM in January, with consumers seeing the update in the early February timeframe, after testing by carriers.
I don't think it would be logistically feasible to push tons of updates and bug fixes as they come up, instead of cumulative updates.
The carriers have to certify them, and I'm sure that they have to be given a certain amount of time to do so.
Though I would like to see an aggressive update schedule. Maybe one every 3 months.
abhinayp said:
Paul Thurrott from Windows Phone Secrets have revealed, well, some secrets about the upcoming Windows Phone 7 updates.
He writes that we can expect two updates this year – the first expected to be announced this week, but only pushed in February by carriers, will be called NoDo (for no donuts), will bring support for the Qualcomm 7×30 smart phone chipset, a CDMA location stack, and a number of software fixes.
Of note is that the Snapdragon-based Qualcomm 7×30 chipset comes with HDMI output and the ability to play back 720p video on both its host device and a HDTV. It also supports Flash 10.1.
The next Mango, will come some time later in the year, and bring Internet Explorer 9 with with the Trident 5 rendering engine, HTML 5 and Silverlight, and gesture support. This 75xx (actually version 7.2) update will apparently bring additional, unrelated features as well.
Paul also mentions that Microsoft does not intend to push a number of small updates, but only a few large updates per year, which should mean long waits between each one.
Source:
wpcentral.com/thurrott-details-2011-wp7-updates-mango-and-nodo-as-no-donuts
wmpoweruser.com/windows-phone-7-updates-nodo-and-mango-coming/
Click to expand...
Click to collapse
actually he said that there will be more small updates between now and mango.
Though mango sounds like a great update (IE9 with full silverlight and html 5)
The fact that "Mango" is being labeled as the "Entertainment Branch" makes me wonder about what the "Business Branch" is.
I think it's safe to assume that there is a Business Branch. So I wonder what priority is given to it. Will it come before or after Mango? Will it be released concurrently? What types of updates would fall under "Business Branch"?
I would say letting carriers in "testing" the update is a bad move on Microsoft's part. If it is anything like Palm, a carrier will push the update rather quickly (Sprint), while the other carriers will release it much latter (one month or more) and only because customers were getting pissed (AT&T and Verizon).
canadariot2312 said:
I would say letting carriers in "testing" the update is a bad move on Microsoft's part. If it is anything like Palm, a carrier will push the update rather quickly (Sprint), while the other carriers will release it much latter (one month or more) and only because customers were getting pissed (AT&T and Verizon).
Click to expand...
Click to collapse
As it was said above, the carriers don't push the updates. When MS released WP7 they said all devices would get updates at the same time, regardless of device or carrier.
The proclamations of imminent failure are rather humorous. It shows 2 main things to me.
1. Some people have very short attention spans, and can't fathom the idea of a "long term plan"
2. Some people think that every other consumer wants the same thing that they do
Microsoft is in this for the long haul. The fact that they have stated that they don't expect to be in a position to beat the major players for at least a few years shows that they are looking at this as a long term investment.
There is a large portion of the mobile phone using market that hasn't upgraded to using a smart phone yet. Many people are happy with their regular phones because they feel that they don't need the features of a smart phone. However, every year, more and more of this very large market slowly moves over into the smartphone arena. These are people who want something that is slick, easy to use, and interesting. They don't need every feature under the sun. These are the kind of people that made the first iPhone such a success even though it severely lacked features compared to Windows Mobile. These are the people that the "Really?" commercials are targeted towards. People who haven't already jumped on the smartphone bandwagon because it just all seems like "too much."
The fact that MS is planning major upgrades to WP7 at all is awesome. It shows that while they are going for the casual feature phone user, they also want to get smartphone users as well. And the fact that they're doing it so quickly is even more awesome. After all, how long has the phone been out now? 2 months? 3 months by the time of the first update? Not too shabby.
MartyLK said:
Just a few I garnered for you:
http://blog.wirelessground.com/windows-phone-7-success-or-failure/
http://www.conceivablytech.com/4653...hone-7-failure-microsoft-will-buy-ad-company/
http://www.infoworld.com/d/mobilize/windows-phone-7-even-bigger-disaster-i-thought-912
http://mosspuppet.com/2010/03/15/windows-phone-7-is-already-a-failure/
http://www.ibtimes.com/articles/662...phone-webkit-html-5-ie7-browser-google-ap.htm
http://pocketnow.com/windows-phone/gartner-predicts-windows-phone-7-will-not-succeed
Click to expand...
Click to collapse
I clicked on some of these articles and some were from March, September, and right around the time of launch. Seriously?
From the article: will bring support for the Qualcomm 7×30 smart phone chipset
Is this a support for any new hardware that might come in future wp7 phones or do the existing wp7 phones support this?
abhinayp said:
From the article: will bring support for the Qualcomm 7×30 smart phone chipset
Is this a support for any new hardware that might come in future wp7 phones or do the existing wp7 phones support this?
Click to expand...
Click to collapse
It's supposed to be current generation hardware that has that.
abhinayp said:
From the article: will bring support for the Qualcomm 7×30 smart phone chipset
Is this a support for any new hardware that might come in future wp7 phones or do the existing wp7 phones support this?
Click to expand...
Click to collapse
The MSM7x30 is a second generation snapdragon that has improved GPU (as used in the T-Mobile G2). Though, based on the wiki this is 800 MHz. Guess we'll have to wait for the actual details.
All current WP7 phones use the QSD8250, so this won't benefit existing phones.
poedgirl said:
As it was said above, the carriers don't push the updates. When MS released WP7 they said all devices would get updates at the same time, regardless of device or carrier.
Click to expand...
Click to collapse
With that being said, can't Microsoft themselves push the update as early as next week? The first update seems really minor.
MartyLK said:
A consumer oriented model would have brought the features out either at launch or soon there after. And a consumer oriented model would not hold out on features that are common in the market already for such a long period of time.
Click to expand...
Click to collapse
If the features were ready at launch or around launch, they would have been released. We don't have the functionality because it's not ready. It is no more complicated than that.
abhinayp said:
From the article: will bring support for the Qualcomm 7×30 smart phone chipset
Is this a support for any new hardware that might come in future wp7 phones or do the existing wp7 phones support this?
Click to expand...
Click to collapse
CDMA support
lqaddict said:
Yet MS orchestrated the iPhone funeral during WP7 launch...
Click to expand...
Click to collapse
So MS can't do that because they feel (and they do) that they have a good competitive product?
The thing with articles is because they influence public outlook on stuff (for the most part). How many claimed WP7 was gonna fail because KIN was discontinued? Articles nowadays are usually biased toward or for a certain platform and hardly treated as fact. It's always an opinion of some person.
I think you missed my point that a very large percentage of potential customers aren't interested in a list of "features" that could be checked off.
Many people who are transitioning from feature phone to smart phone just want the transition to be nice and painless.
You're looking at things from the perspective of a veteran smartphone user. And most people aren't.
I disagree that the mango update is an issue. It's not like android where half the devices are still on 2.1 with 2.2 released months ago and 2.3 just released.
Updates will be across all phones, yes it will take time to get them, but what OS gets releases out fast?
nrfitchett4 said:
I disagree that the mango update is an issue. It's not like android where half the devices are still on 2.1 with 2.2 released months ago and 2.3 just released.
Updates will be across all phones, yes it will take time to get them, but what OS gets releases out fast?
Click to expand...
Click to collapse
Only thing on this thread that hasn't made me cringe with "WTF?!", so thanks for that.
Did anybody really expect HTML5, Silverlight, Copy & Paste, Multitasking within 2 months of release and bug-free?? That's impossible. They've only been working on the entire OS for just over a year ffs. I'm amazed we're even using WM7 right now, let alone getting ANY sort of an update within a few weeks.
People on this thread just sound like this is their first early adoptation of a phone. Welcome to the gadget world, friends.
I've been sitting on the sidelines not being vocal, but I think there's something we need to consider...
When we got our wp7 phones we need what features were lacking. If you didn't you should have done some research before you bought the phone. Wp7 is still in its infancy and expect there to be bugs and problems. If you wanted something more concrete should have stick with your iphone or Android. For what we do have everything seems to run pretty smooth.
Im not going to lie, but I curious about the nodo update. But im glad I haven't received it. Because then our phones will be locked and the homebrew segment and actual limited customization will be gone. Until someone of course finds a work around. And someone always does. And honestly, on your old phones how many of you even knew it had a copy.paste feature? Instead of focusing on nodo update which doesn't really do much, except speed up our phones, why no concentrate more on mango! Mango is the update that we all should want! Just my two cents. Btw i use a HTC hd7 on tmobile USA and its done everything i wanted without any problems!
I think people are focusing on Nodo because it's the 1st update and it will give us an idea about how Microsoft will handle the platform.
If they can't even handle a small update with almost nothing in it, this is worrying for the future. If they need 5 months to release such a small update, when will we get Mango? it's nice to make big promises about Mango but I'm starting to believe Thurrott when he says 2012 when you consider Microsoft's pace. I couldn't care less about Nodo, I don't use C&P that much and it doesn't fix the bugs people really care about like Live Tiles and push notifications not working. It only fixes one bug and that's the marketplace one.
And how long until we stop saying "they've just started, give them time"? After 6 months they should be about to deliver their 2nd update and be talking about the next one. Even if it's in 3 months, at least talk about it! They act like they don't give a sh*t and I'm sure soon people will start trading their phones and go back to Android/iOS.
That's true too. But considering this is their first update we can't assume things will be perfect. Now if the next major update rolls out and there's still issues with updating I for would question Microsoft. But I see your point of view. Perhaps Microsoft was releasing this small update to see how their update system would work? Dunno, but don't give up on Microsoft just yet. Trust me, I miss my android G2, but my wp7 phone hasn't let me done yet. And I was just thinking, do we really need multitasking? That could open up a whole new can of worms.
A can of good worms. Especially in the Modding scene.
vetvito said:
A can of good worms. Especially in the Modding scene.
Click to expand...
Click to collapse
I've been the first to defend WP7 and Microsoft all over XDA for months now but with official announcements starting to be pushed back while devices in other countries and even some here are running the update Microsoft is really starting to look bad.
z33dev33l said:
I've been the first to defend WP7 and Microsoft all over XDA for months now but with official announcements starting to be pushed back while devices in other countries and even some here are running the update Microsoft is really starting to look bad.
Click to expand...
Click to collapse
Same here. I'm really starting to get worried that it'll be like everyone feared.
Oh well, I really thought they would up their game with this.
Still a great phone, just now I know it won't be supported.
I'm still not quite sure what carriers have to do with updating the phone. The update comes through Zune. C&P can't screw up a network, neither can the marketplace not crashing all the time.
In other words, this update fiasco is purely MS's fault.
Be it that they didn't make a better deal with carriers, they underestimated logistics, they haven't been forthright with customers, it is the fault of MS.
On the other hand. If you bought the phone because some said someone at MS said an update was coming out soon that would add C&P, I can see how you'd be pissed off, but you'd still be silly for buying a phone based on a rumor as opposed to its merits, which are plentiful.
My problem with this whole thing is:
1/. If MS was gonna stay mum and not update us on the delays, they should've STFU all the way until they announced a concrete date for the update.
2/. If MS was gonna talk about updates, they should've kept us posted all the way instead of tidbits here and there.
The way their going about it making it so some can't even recommend WP7 because of this update fiasco. I mean, since when couldn't MS send out bug fixes? I get one almost every week for my PC and that OS is way more complicated than a phone OS.
That's so true. They shouldn't make promises they can't keep. And if they say something and it dont go right atleast keep us in the loop. I also agree its hard to reccomend a phone where the support from Microsoft seems to be very spotty. So my question is, is it still too early to tell the future of wp7? I guess now I can understand why some people are asking about trying to dual boot on our phones. So is it the carriers fault, Microsoft fault, or the OEMs hardware fault we're not getting updates? And since we have to update through Zune, what do the carriers have anything to do with the updates?
I think what is forgotten here is that XDA is a geek forum. Most people do not have a clue about copy and paste. They want to hear music surf the web and take pictures. We easily forget that we are not normal consumers.
hassia said:
I think what is forgotten here is that XDA is a geek forum. Most people do not have a clue about copy and paste. They want to hear music surf the web and take pictures. We easily forget that we are not normal consumers.
Click to expand...
Click to collapse
Normal customers want their push notifications to work properly, that should have been fixed within a month and Microsoft haven't even talked about it.
Peew971 said:
Normal customers want their push notifications to work properly, that should have been fixed within a month and Microsoft haven't even talked about it.
Click to expand...
Click to collapse
Hear, hear! Allowing a maximum of 15 apps with notifications was a huge oversight on their part, and afaik there are still no plans to fix this.
As for the marketplace bugs, from what I can tell not even all of those are fixed in the No[Can]Do upgrade. Probably because this particular update has been sitting on the MS servers since January waiting for an actual release.
emigrating said:
Hear, hear! Allowing a maximum of 15 apps with notifications was a huge oversight on their part, and afaik there are still no plans to fix this.
As for the marketplace bugs, from what I can tell not even all of those are fixed in the No[Can]Do upgrade. Probably because this particular update has been sitting on the MS servers since January waiting for an actual release.
Click to expand...
Click to collapse
The messed up part is that this is an advantage.
While they were ironing out whatever back-alley deals they had to iron out with the carriers, they could've been taking notes on what actual people in the know on forums like these had to ***** about.
They could've then slipped a few of the fixes, swapped a few 1s with 0s in the code, tweaked it around just a bit to make the OS even better.
Instead, we're going to get the update verbatim, the geek world is going to laugh and MS is gonna wonder where it all went wrong for the umpteenth time.
Probably just a reiteration of what others have said, but nonetheless my opinion. Microsoft first said that the NoDo update would be coming early next year so most people assumed January, than they said late February (I think they did), then it was early March, and now its late March. This update merely adds copy + paste (along with a few bugfixes, one of which ISN'T for the camera) and that is a very basic feature! Apple just released iOS 4.3 (which updated the Safari javascript engine and some other stuff) AHEAD of schedule by 2 days and Microsoft keeps pushing back a minor update by weeks.
I'm pissed because I want WP7 to succeed. I used the device and I loved the device, but it's not nearly as good as its competitors as a whole. If Microsoft doesn't figure out what their doing WP7 will fail.
The general rule is you NEVER buy a phone based on what is "coming". You always buy based on what is in the phone when you bought it. I went through the same crap with blackberry, promising an os update to the storm 2 series. When OS6 came out they were like nope, not supporting that handset. Go buy a the touch.
I'm very satisfied with the Samsung Focus I have now, any future updates is just icing on the cake. You'll be sorely disappointed if you buy things based on promises
Sorry I will have to reiterate my post 'normal consumers' want to play music,surf the web play youtube and games most will not use copy and paste that is just a fact. I work in a theater with a varied range of people most do not even know they have copy and paste capabilities.
http://windowsteamblog.com/windows_...1/03/10/phone-updates-process-and-timing.aspx
At least somebody has been hired to start saying something
There’s one more thing I want to clear up. I’ve seen a lot of speculation on blogs and forums lately about whether carriers can “block” an update. We work closely with carriers to test and schedule updates. They may ask us for a specific date to start an update. They may ask for updates to be bundled together. But you should ultimately receive all the updates we send out.
Click to expand...
Click to collapse
Damn you Carriers!
This short pause should in no way impact the timing of future updates, including the one announced recently at Mobile World Congress featuring multitasking, a Twitter feature, and a new HTML 5-friendly version of Internet Explorer Mobile.
Click to expand...
Click to collapse
I sure hope so...
This is just what I expected, But I don't think it can penetrate the people's stupidity. Hopefully this can SHUT some of the people UP.
At least someone at Microsoft said something about the updates, even though it doesn't say a whole lot.
Lets hope they become a bit more vocal about things, instead of relying on rumors to become news.
His post was full of words, but didn't really tell us anything at all. I think he's probably a politician at heart.
1. they test updates at ms
2. carriers also test the updates, some carriers take longer than others
3. carriers can request a certain date updates will be allowed. e.g ATT can send an update a week earlier than Verizon (you will get your update but carrier decides when)
4. updates can sometimes include firmware from specific phone manufactures
5. updates are targetted to specific phones. just because LG phones got an update does not mean HTC phones will get an update. see point (2)
6. the snafu about the last update made them pause to make sure this update goes well.
7. The next update is copy and paste, improved market search and other improvements
what do you mean he didn't say anything?
Wow, I'll be honest, I'm both speechless, and pretty much satisfied.
This is exactly what they should have done. Wow. I'm seriously blown away that Microsoft actually did this. Very impressive.
Good enough for me.
i'm still not satisfied with these explanations. these excuses are to buy time and make microsoft look good. microsoft test update in lab > manufacture and chipmaker test their firmware > carrier test it on their network > users get update. they went thru at least 3 phases of testing and tell me none knows of the issue with samsung wp7? they were way behind schedule and have to rush the update so it wasn't properly test. NoGo was supposed to be out january. still NoShow.
akachay said:
i'm still not satisfied with these explanations. these excuses are to buy time and make microsoft look good. microsoft test update in lab > manufacture and chipmaker test their firmware > carrier test it on their network > users get update. they went thru at least 3 phases of testing and tell me none knows of the issue with samsung wp7? they were way behind schedule and have to rush the update so it wasn't properly test. NoGo was supposed to be out january. still NoShow.
Click to expand...
Click to collapse
perhaps, but given your logic shouldn't the manufacturer (that being samsung) had picked it up when they were given the update and told MS about it before it hit a whole lot of samsung users? MS don't create the phones themselves (unlike Apple, which everyone seems to be comparing MS' update system to), so therefore the complexity of the updates in general are increased to a great magnitude with the additional layers that they need to help satisfy.
akachay said:
microsoft test(s) update in lab > manufacture(rs) and chipmaker(s) test their firmware > carrier(s) test it on their network(s) > users get update
Click to expand...
Click to collapse
There's a step missing for a good test - between network testing and end users, a quick release to power user early adopters needs to happen.
These are people who ideally have the technical proficiency to help troubleshoot any issues encountered (in other words, they know how to file a bug report, and also how to follow troubleshooting instructions from MS).
Whiny *****es would of course be excluded.
MS used to have a system like this for their MSN software products (such as MSN messenger). I thought it worked really well as a participant, but then they ditched the program - IMHO they invited too many whiny non-technical people and just got sick of placating them.
I really don't think this addresses the issue. Tell me MS didn't know how this would work from the beginning?? If they did know, why did they advertise the system the way they did? They made frequent and aggressive updating as a main feature of WP7. Yet that "aggressive" updating is more like super timid updating.
Either MS didn't know what it was getting into, or they knew and are trying to blow smoke up our rears.
or they knew and are trying to blow smoke up our rears.
Click to expand...
Click to collapse
*poots left over smoke out of his arse.
MartyLK said:
Either MS didn't know what it was getting into, or they knew and are trying to blow smoke up our rears.
Click to expand...
Click to collapse
I would bet money it's the former.
They probably had meetings, layed it all out on spreadsheets, powerpoint presentations, etc. Had engineers give reports. Marketing specialists chime in on what's needed to win. And they thought it would go smooth as butter.
Ok.. time to give a fack with this guy..
So, was there anything we didn't already know?
The fact that MS had to push a pre update update is amusing, & the update was for every phone not just Samsung. Obviously MS never tested the update process before the launch of WP7. The Samsung issues show that MS & its OEM partners don't communicate well with each other. A good example of this is SD card support, if MS doesn't want it why is it there & how did Samsung get away with putting it in? Is MS not in charge of WP7 & the user experience, which a buggy SD card will impact?
Now, that said, I think it's worse than I thought.
So they need to adjust WP7 OS to every device out there, and with approval from carrier?
So, that means.. that this is almost exactly like Android. Or at least seems like Android. They are going to release tons of phones, and then, forget our humble phones.
Really, do you guys think MS is going to worry with an outdated smartphone? That don't even sell in stores anymore?
Crap ;/
After reading some of the comments posted there, it is clear that folks do not understand that the difference between Apple updates and Microsoft updates is that Apple controls the entire chain from nuts and bolts to software. They are updating ONE piece of hardware.
Microsoft is updating MANY DIFFERENT hardware types from many different manufacturers. Thus, 'issues' will occur.
With this PR blog post having 100+ replies with more than 90% of them being not positive, and Paul Thurrot's "Still No Update" post (which I'm assuming is what pushed MS to respond) having 150+ replies, maybe they'll finally start to "get it".
But I doubt it...
pbratton said:
After reading some of the comments posted there, it is clear that folks do not understand that the difference between Apple updates and Microsoft updates is that Apple controls the entire chain from nuts and bolts to software. They are updating ONE piece of hardware.
Microsoft is updating MANY DIFFERENT hardware types from many different manufacturers. Thus, 'issues' will occur.
Click to expand...
Click to collapse
It seems you may not understand why the comparisons are valid. "Chassis 1" was suppose to be MS's answer to Apple so that they, like Apple, could update all phones at once.
Anything extra the OEMs add should be on them (ie. LG with DNLA) and MS should ONLY be responsible for updating the core OS. Acer, Asus, HP and Lenovo all update their own drivers while MS updates Windows. It should be the same exact process with WP7.
BTW, Apple is updating THREE pieces of hardware and many revisions of each. MS is updating ONE uniform OS AND they've been in the mobile OS business since 2003. They should have known how to run things by now.
pbratton said:
Microsoft is updating MANY DIFFERENT hardware types from many different manufacturers. Thus, 'issues' will occur.
Click to expand...
Click to collapse
Also, it's not like MS has no experience here. They've rolled out updates to different hardware types before as part of the Zune updates that have happened occasionally (I think about twice a year, just like Xbox - autumn/spring) since launch.
So yeah, they have carriers in the mix now. That's really the only complexity added over the Zune updates that have been largely trouble-free.
Seems Microsoft is moving full steam ahead we have RTM!!!http://wmpoweruser.com/windows-phone-7-mango-released-to-manufacturers-in-carrier-testing/
rruffman said:
Seems Microsoft is moving full steam ahead we have RTM!!!http://wmpoweruser.com/windows-phone-7-mango-released-to-manufacturers-in-carrier-testing/
Click to expand...
Click to collapse
a subject already exist http://forum.xda-developers.com/showthread.php?t=1170721&page=2
but great news for us
Well yeah at the end of August we will see the first new phones, but Microsoft always said that consumers will get Mango in the fall.
So it's nice to hear they have RTM'd, but September is already fall and with carrier testing and OEM testing I doubt will get it earlier.
slimshady322 said:
Well yeah at the end of August we will see the first new phones, but Microsoft always said that consumers will get Mango in the fall.
So it's nice to hear they have RTM'd, but September is already fall and with carrier testing and OEM testing I doubt will get it earlier.
Click to expand...
Click to collapse
we can hope that got it earlier
http://www.wpcentral.com/ATT-dell-venue-pro-not-shipping-till-8-30-getting-mango-speculation
"fall" is only two months away, as of tomorrow. Just to keep things in perspective.
It seems reasonable to expect the testing and certification by phone manufacturers and carriers to take at least two months, which would be consistent with all of the timelines that have been "leaked" over the past few months. Many rumors indicated that Mango would RTM in July (which it has), and that new Mango-equipped hardware would begin to hit retailers by late August/early September (which also appears to be accurate - remember, no one ever said they would be available worldwide at that time).
Add in another month to complete manufacturer/carrier testing for existing devices, and deal with the logistical issues around preparing for the distribution, and people on reasonable carriers could easily start seeing the update on their phones in early October. People on AT&T will probably see it by June of next year.
Already reported by Microsoft themselves that Windows Phone 7 Mango has not RTM'd yet. Which is good IMO, because I'd rather them work on it as much as possible.
prjkthack said:
Already reported by Microsoft themselves that Windows Phone 7 Mango has not RTM'd yet. Which is good IMO, because I'd rather them work on it as much as possible.
Click to expand...
Click to collapse
it is now
http://windowsteamblog.com/windows_...ws-phone-mango-released-to-manufacturing.aspx
I'm going to hope (probably in vane) that the RTM is leaked onto the internets somehow. I've had minimal dramas with the mango beta, so I'd like to get onboard with the RTM ASAP.
Demaar said:
I'm going to hope (probably in vane) that the RTM is leaked onto the internets somehow. I've had minimal dramas with the mango beta, so I'd like to get onboard with the RTM ASAP.
Click to expand...
Click to collapse
how will hoping you know about the direction of wind help mango leak?!
i will hope in vain as well, but maybe we'll get lucky and it will leak out (or even be released in short order)
wasn't that new toshiba phone msft is showing today/tomorrow supposed to be running mango?
prjkthack said:
Already reported by Microsoft themselves that Windows Phone 7 Mango has not RTM'd yet. Which is good IMO, because I'd rather them work on it as much as possible.
Click to expand...
Click to collapse
Well, it looks like you got more time. Only 4 days worth, but still...
Seriously, though, It seems obvious now that the code was already frozen when the original report "leaked", but that the hand-off to handset makers and operators was not complete. Now it is.
So, we are still on track (barring ridiculous manufacturer/carrier delays) to see people actually receive the update by late September/early October. And, if Nokia does have hardware ready to go (which seems evident), we may see Mango-equipped new phone models very quickly.
kinda news ?
i was expecting more today, like a NEW mango finalized device displayed somewhere..
is this only a rtm announcement ?
anyone know if there will be a 2 stage release to end users like nodo had to make carriers actually push updates to phones ?
...waiting for some hard news...
I'm hoping that I'll connect to Zune soon and see that an update is available. I'd like full Twitter integration in my Mango.
ohgood said:
anyone know if there will be a 2 stage release to end users like nodo had to make carriers actually push updates to phones ?
Click to expand...
Click to collapse
I'm not sure what you're asking. All WP7 updates go through a certification process with both handset manufacturers and mobile operators. But neither of those entities "push" the updates to phones. Update delivery only happens through Microsoft (i.e., Zune).
So, what is happening now is that the other companies involved have received their copies of Mango for final testing and sign-off. They had likely already received earlier builds, so they could begin development of new features and/or apps (thanks to all of the new capabilities they might want to capitalize on), but now the clock is ticking on them. They complete the sign-off, send back to Microsoft any modifications they have made specific to their hardware or mobile service, and then Microsoft combines those into various bundles that ultimately get delivered to our phones.
The one exception to that rule is unbranded phones, which will probably receive the update before carrier-branded ones, since there is only one level of sign-off needed before the update can be made available.
The big question is whether Microsoft will be able to apply more pressure to carriers (especially AT&T) to sign-off in a timely manner. On this issue, let's just say that I have my doubts.
Out of curiosity, did we ever get a notice of the specific date that NoDo went RTM? I don't recall seeing one. Maybe the fact that Microsoft is being so vocal this time around is part of their plan to "motivate" carriers.
This is fantastic. Like others Im hoping someone leaks the latest build so XDA members can get their fingers dirty.
RoboDad said:
I'm not sure what you're asking. All WP7 updates go through a certification process with both handset manufacturers and mobile operators. But neither of those entities "push" the updates to phones. Update delivery only happens through Microsoft (i.e., Zune).
So, what is happening now is that the other companies involved have received their copies of Mango for final testing and sign-off. They had likely already received earlier builds, so they could begin development of new features and/or apps (thanks to all of the new capabilities they might want to capitalize on), but now the clock is ticking on them. They complete the sign-off, send back to Microsoft any modifications they have made specific to their hardware or mobile service, and then Microsoft combines those into various bundles that ultimately get delivered to our phones.
The one exception to that rule is unbranded phones, which will probably receive the update before carrier-branded ones, since there is only one level of sign-off needed before the update can be made available.
The big question is whether Microsoft will be able to apply more pressure to carriers (especially AT&T) to sign-off in a timely manner. On this issue, let's just say that I have my doubts.
Out of curiosity, did we ever get a notice of the specific date that NoDo went RTM? I don't recall seeing one. Maybe the fact that Microsoft is being so vocal this time around is part of their plan to "motivate" carriers.
Click to expand...
Click to collapse
i don't know how to be more clear with my question.
i can't see att caring about what microsoft says about signing off. they aren't exactly pushing wp products, and could care less about an update that will -not- sell another contract/phone to existing customers. an iphone hardware update on the other hand, oh yes yes yes, they love that stuff.
i did see a couple of blog posts (via my android news aggregator) stating that there would be a mango hardware unveil today, along with the rtm statement. apparently, bloggers jumped the gun, again.
the rtm statement is really a non-news worthy event. "we released something to someone, so sometime soon you might have a something for your phone. maybe." really that's all it is.
now HARDWARE... that's something i can understand there being threads and news about. say, searay or whatever the supposed new SHIPPING device is, that's news.
anyway, back to my jonesing for new tech... maybe endgadget or someone has some cool news... rss update time
ohgood said:
i don't know how to be more clear with my question.
i can't see att caring about what microsoft says about signing off. they aren't exactly pushing wp products
Click to expand...
Click to collapse
Pushing products in a store and pushing updates to existing phones have nothing to do with each other. So I still don't understand your original question about carriers pushing the update to our phones. They don't push the update, Microsoft does.