So, last night, Windows Phone 8 got its first update – specifically for the HTC 8X. In this day and age, where iOS is the gold standard and shows the industry how it ought to be done, and Android is the exact opposite, Windows Phone 7 was a bit of an in-between – every phone got every update, but the staggered rollout was slow and frustrating, often due to carrier meddling. How will Windows Phone 8 fare?
I bought my HTC 8X off-contract, unlocked, and completely free of any carrier control. This means my 8X was among the first to receive the update, and so I performed it this morning. Luckily, WP8 finally supports over-the-air updates, so no PC required. It was all pretty painless, but it did take a long time – a total of about 15-20 minutes for what is a very small update, with several moments where I wasn’t sure if the phone was doing anything at all.
After the final reboot, I was greeted by a new feature that I’ve been wanting in Windows Phone ever since I bought my HD7 when the platform was brand-new: the ability to maintain a wifi connection when the device is locked. This has already greatly enhanced my user experience, and I’ve only had it for a day. Amazing it has taken them this long. The update also addresses a reboot issue some 8X owners were encountering, and also adds SMS drafts and SMS call reject.
Sadly, it seems like little has changed when it comes to who will get the update when. Yes, unlocked 8X owners have already gotten the update, but those with branded devices from their carriers won’t be as lucky. There’s currently no schedule for when these updates will go live, and it all indicates that Microsoft still can’t roll out updates on its own – it needs to go through carriers.
All this highlights the idiocy of the update situation on smartphones when it comes to carriers. The same device, yet the locked version needs “additional testing” or whatever else carriers do, while at the same time, unlocked devices get the update anyway – even without testing. It makes me wonder what, exactly, these carriers are doing that takes up so much time – since it’s clearly not needed, as unlocked phones demonstrate.
The situation on Android has already demonstrated that carriers make a mess of things, but the existence of Android skins and OEM customisations has muddied the waters there when it comes to finding out who, exactly, contributes the most to delays. On Windows Phone 8, however, no such muddiness: any delay on branded devices comes from carriers.
As an unlocked WP8 owner, I’m happy with the process of this first update. It just goes to show: buy unlocked. At all times.
One of the reasons I switched to the iPhone from Nokia is the frustrating delay or outright refusal of the telcos to provide software updates.
I am in Australia and the carriers are the pits when it comes to firmware updates. When these updates can improve reception or battery life and so on they absolutely should be provided to the customer, with previous Nokias some updates were not released 2 years later. Then you have to trick the phone to install a generic english firmware.
Carriers are more interested in selling a new phone of course but when you are under contract and they do not provide updates during the life of the contract there is something very wrong.
I am not using this post to bash other people by saying the iPhone is superior, it is good for my needs. I was a Nokia fan and I hope one day I can use them again. My handset purchase does not have to be tied into the APP store ecosystem as I can use apps on an iPad.
If anyone is curious the other reasons I swapped was an inability to use calDAV on Symbian I was going to upgrade to a win phone but found it will not do it either. Hopefully it will be added to win phone 8 at some point and an SMS bug that meant your phone had to be factory reset every 2-3 months.
At least in Europe you get to buy unlocked mobiles almost everywhere, so it would had been just required to use PC Suite.
But as a former employee I also remember not all mobiles had firmware updates for very long, just two or three updates usually.
Its too early to tell if it is indeed that carriers are blocking updates, or that a broader update release is being introduced gradually. Microsoft traditionally trickles out updates for Windows Phone. Its too early to definitely blame carriers.
Also, I believe Microsoft is planning some kind of opt-in bleeding edge program where you’re pushed the update regardless. They mentioned it this past summer, I’m curious what’s become of that.
so I guess the 10 or 20 people that bought a windows 8 phone can start looking forward to the same degraded update process they enjoy with their computers?
Edited 2012-12-12 04:02 UTC
I own an unlocked Nexus device and get my updates straight from Google with more frequent updates than IOS^aEUR”and I recommend all Android users do the same. That said, I do find it quite humorous that a modern phone, like Windows Phone 8, is only now able to maintain a Wi-Fi connection while the phone is locked.
Yep. If I ever buy an Android device it will be from Google. I’ve got exactly zero interest in any of the other handsets that mess around with the software and screw everyone on updates. Completely inexcusable.
Google needs to offer a high quality phone though. The nexus 4 seems good for the low end, but there is no high end option that supports LTE (and the nexus 4 seems to have some quality issues: http://code.google.com/p/android/issues/detail?id=39936 )
That’s not always true. People have waited months, despite owning a Nexus device, to have the latest version of Android pushed down to them. The fairy tale, because that’s what it really is, a fairytale, that Nexus devices get updates on day #1 is getting old.
To contrast, when Windows Phone 7.5 came out, it rolled out to every device, across every carrier, in every country. Without a hitch.
Very little apps are impacted by the WiFi fix, because very little apps run under lockscreen, since 7.5 it hasn’t been recommended to run under Lock screen. Instead, you just support Fast App Switching and Fast App Resume and call it a day.
About the only apps that I can see having a meaningful impact by this are apps that 1) Transmit data in the background like an Audio Streaming app, or 2) Apps that would like a persistent transport connection to be maintained.
Neither are very common. This is a low impact change, and it’s opt-in, so it’s not even default behavior. Its more to appease some power users.
Speaking of fairtytales. You clearly weren’t there during the rollout. It took months and months and months, with bugs and bricked devices. It wasn’t until TWO WEEKS AGO that the Focus 2 on some carrier got it.
Two weeks ago.
Wrong. Focus 2 came pre-loaded with Tango, a full release after Mango (7.5). It’d help if you knew what you were talking about.
http://www.samsung.com/us/mobile/cell-phones/SGH-I667UWAATT
The Focus 2 was not even out during the Mango roll out. The Focus 2 was released like four or five months after, during the Spring.
What the Focus 2 got late was a bunch of carrier and hardware specific firmware upgrades, and a small 7.5 Refresh update.
If the Focus 2 hadn’t launched with Tango it wouldn’t have had the 4G LTE stack that was added in the Spring update.
Edited 2012-12-12 09:15 UTC
I meant Tango.
It came pre-loaded with Tango. What it got rather late were firmware updates and a small post-Tango update (8773, some people call it Tango #2)
The problem was that the firmware update is at the discretion of the OEM, but it was requisite for Tango #2. At least, that’s what was said.
There’s a HUGE difference between missing out on Mango (a major OS update) and missing out on some firmware updates and the ability to attach multiple MMS to a message. That’s really all the update was about.
Yes, and then, when Windows 8 came out (not even a year after Windows Phone 7.5) every single consumer up to that point got screwed out of any future updates to those handsets, ever. Great comparison there. Try a little harder next time, okay?
Except Windows Phone 7 handsets are getting an update in the form of Windows Phone 7.8.
So, what exactly were you saying again?
Fcuk 7.8. It’s a pointless update. It’s like saying that silly feature pack for Gingerbread Samsung pushed out is the same as ICS.
Nobody knows when 7.8 is coming out, and on top of that, it adds virtually nothing to 7.5 except for smaller tiles. Big whoop. I know you have a thing for promoting Microsoft, but this is really unpromotable.
That’s your opinion, but the fact remains that it is incorrect to say that there are no post Tango updates for Windows Phone 7. It is simply not true.
And APIs for Lock Screen access for apps, and APIs for controlling the new Start screen via apps.
Plus, if you own a Lumia, Nokia is adding a bunch of their own value-add to 7.8 . Other OEMs can do the same, if they have not, then that’s unfortunate.
Besides, they are still selling Windows Phone 7 devices. The Lumia 510 went on sale, which comes with Windows Phone 7.8.
Leaked Nokia roadmaps show future updates to the WP7 in the pipeline.
The difference between WP8 and WP7, when it comes down to apps is almost nothing. Most apps maintain WP7 and WP8 versions, with near feature parity. The main reason to recompile for WP8 is to remove the letterboxing on 720p devices.
In fact, on WP8, WP7 apps merely run in a “Quirks mode”. Its largely the same.
All your excuses can be applied to Android as well. Virtually all applications are available for both Gingerbread and ICS+, with minimal changes.
Fact remains: Windows 7.x is dead in the water, even though it’s still being sold. That’s a fcuking disgrace, and the fact you are trying to right that wrong is telling, at best, and disingenuous, at worst.
Edited 2012-12-12 09:31 UTC
So? That’s good that all applications are available, though I dispute that notion to an extent. There are plenty of Android developers who develop for X,Y,Z devices only.
I think we have a fundamental disagreement about Windows Phone 7 being dead. WP8 is not going to hit the price points WP7 did any time soon. WP7 is going to keep being pushed into the low end, and WP8 will remain the mid-high end solution for Microsoft.
At least, that’s my read of the situation. However, in your infinite wisdom (like saying that it took the Focus 2 over a year to get Mango), I’m sure you disagree.
WP7 is even dead for Nokia. Lots of there last apps only work on WP8. Since WP8 apps not work on WP7 in general and since most including Microsoft gave up on WP7 to promote WP8 the WP7 app store gets close to no new apps at all. No maintaing. As of today its a ghost town. If you not see that you are not using a WP7 device. But no problem, the huge majority does not
Name some of them? I assume you can come up with concrete examples of WP7 being left behind, right?
Except you can’t, because you’re making it up.
Are you so into MS that you cannot differentiate between 7.8 and 8?
Can you differentiate between them? Or point out concrete differences in their API subsets that would make maintaining two versions difficult?
Hint: I maintain a shared codebase between WP7, WP8, and Windows 8. All without a hitch, which is my entire point in that the fact that WP7 devices won’t get WP8 has mitigating factors.
Of course, it’s much easier to brush it off as me being a shill, as if what I did was much more than just correcting a few people on their facts.
I’m sorry that me telling people to actually speak truthfully is me shilling for MS.
How is hat different for the Gingerbread users on Android?
Every android handset other than the Nexus pones have (until ICE handsets were released) hardly, if ever, gotten updates and if they did, they got one crappy update that never got a bug fix…..why do you think CyanogenMOD became so freaking popular?
Edited 2012-12-13 00:31 UTC
Fairy tale, huh? From Wikipedia (and common knowledge to Nexus owners, of course), emphasis mine:
“On June 27, 2012 at the Google I/O conference, it was announced that the Nexus S would be one of the first devices to receive an upgrade to Android 4.1 Jelly Bean, along with the Motorola Xoom and Galaxy Nexus, began on July 26, 2012.”
I finally gave up waiting for WP7.8 and went back to my Nexus S 4G. This is a phone that is well over a year old and yet received the Jelly Bean update soon after it was gold. My best friend’s HTC One X, on the other hand, is still waiting several months later.
While my Nexus won’t be getting 4.2 officially, my contract runs out right around the time the Galaxy Note 2 will likely drop in price. That device is already my chosen upgrade path so I’m set for a couple of years yet. And if I do want to get a taste of 4.2, there’s always CyanogenMod. I’m also going to hang on to the phone to play around with Firefox OS builds.
As much as I enjoyed using Windows Phone, between the lack of updates and fixes for my old phone and Sprint’s flippant attitude towards the platform, I had no choice but to leave it behind for the foreseeable future.
Was there any small-print in that announcement for Galaxy Nexus owners? From what I’ve read, it took a long time for Verizon Galaxy Nexus owners in the US to get 4.1, and it’s possible some folk haven’t even got it yet. Same could be said for owners of the device in many countries. My unit wouldn’t be up-to-date if I didn’t manually flash the firmware back to Google’s stock factory image. Not sure if this was the fault of Google, Samsung or the carriers of various nations, but it still stunk.
I’m looking at Verizon on that one, I have several coworkers on that carrier and they are treated like horse manure. I’ll never have service with Verizon; I’ll go without a phone first.
You can emphasize anything you want, it doesn’t inherently make you right. Because you’re not.
Some Nexus device owners on some carriers faced an extraordinarily long wait to get their update. Saying that Nexus devices in and of themselves are guaranteed #1 day tickets to the latest Android is disingenuous.
Even more annoying, is the notion that you seemed compelled to respond to my comment with one of your own, despite not having yourself done the proper research. Please, don’t do that.
The problem with your position is that you lay the blame on Google, or on the Android platform itself, for the delay. Any delay on receiving updates is purely the fault of the carriers, and that will happen, and has happened, irrespective of the platform. It was even worse for BlackBerry owners several years ago; AT&T BB users were left in the cold most of the time when it came to BB OS updates, while Verizon and Sprint users got timely support.
It seems as if you are the one being disingenuous for not acknowledging that.
It’s called the fundamental attribution error. When WP7.8/8 updates are messy, it’s due to situational circumstances – when Android updates are messy, it’s due to Google.
In the meantime, those of us without any vested interest in any one platform know where the faults lie. For Android, carriers and OEMs. For WP, carriers. Google and Microsoft are not even part of the blame.
Edited 2012-12-12 16:22 UTC
I just don’t buy into the fact that the relatively pain free Windows Phone updates are anything in the same ballgame as the shitfuck that is the Android update situation.
Your cited example (the Focus 2) was TERRIBLE. Yet, because you said it, it magically equates Android and Windows Phone, despite it being 100% incorrect. That’s bullshit I refuse to buy into.
Now, if you want to talk Windows Phone update issues, I’ll talk about then, because there are plenty. But they are for different reasons, and of different degrees of pain for end users.
1) Pre-Mango the NoDo update roll out was terrible. It was however their first update, and since then the process has matured quite a bit.
2) The post-Tango firmware update messaging was a mess, Microsoft refused to comment on the existence of an update for weeks after the OEMs pushed it. By and large though, from the Spring to the Summer, a majority of people got the update.
The only phones that really had an issue, were those who were in development when Tango 2 launched, and launched with Tango 1 instead. ATT and OEMs dragged their foot on it, but I don’t think MS particularly pushed hard on the issue either.
3) The messaging behind WP7/WP7.8 is a mess. By and large, this is one of their biggest screw ups. They really messed up by not giving enough information in a timely enough manner.
It remains to be seen how the WP 7.8 roll out will go. However, let’s make a bet. Let’s wait until January 2013, if the WP7.8 roll out is terrible, and not excellent like the Mango roll out, then I’ll concede that the situation on both platforms (Android and WP) are the same.
Because there is a refusal to acknowledge that the situations are not the same.
By and large, every Windows Phone 7 owner has been updated to the latest Windows Phone 7 release.
A majority of Windows Phone users run the latest version of their platform. That is a fact. A majority of WP7 users are on 8773. The same is NOT true for Android.
Obviously, there is something much more out of control going on here, and I find it tragic that you, post after post, refuse to notice, or even acknowledge a difference.
Sure, of course, there is carrier and OEM pigheadedness in the way, but the fault lies squarely with Google in that they have not effectively dealt with the situation.
I refuse to equate the two experiences, because while most Windows Phone users are on 8773, by comparison, almost no one is on Jellybean. A fact.
I’ll give your position some merit when I see 7.8 on my HTC Arrive. Sorry, but it’s Windows Phone users who are 100% left in the cold here, by Microsoft.
7.8 is not released….Jelly Bean 4.1 and 4.2 have been released and have near zero penetration.
And? 7.8 was supposed to be out in the summer. Then it was supposed to be before WP8 was launched. Then it was supposed to be with the WP8 launch. Now it’s some time next year.
Now tell me how constantly moving the goalpost is even remotely better than a released update? I’ve got JB but I’m still waiting for WP7.8.
And just to be clear: I would much rather be running a WP device than Android. But if Microsoft isn’t going to stand by their product, I have to settle for the next best thing.
Edited 2012-12-13 00:53 UTC
I assume you can cite the relevant Microsoft statements where they announced a 7.8 release date prior to now?
Not while I’m at work, but a quick search of Google from my phone shows dozens of articles going back in time to early September, each saying the release is “right around the corner” or “any day now”. The most recent says “some time in early 2013”.
When I get home I’ll gladly get on my computer and write it all up for you, since you can’t be bothered to do a little research yourself. In the mean time, I’ll enjoy having an up to date phone.
Microsoft has only confirmed the release date one time.
However, maybe your updated phone is powerful enough to let you invent reality.
You shouldn’t be so quick to assume I haven’t done my research, because I had, and knew the answer to the question before I asked you.
I just figured maybe forcing you to do a little work, and actually find out that you were wrong the old fashioned way, will give you some sort of caution towards making factless assertions in the future.
How you can show a chronic disregard for the facts is insulting, and especially ironic given I’m the one who supposedly couldn’t be bothered to fact check.
Edited 2012-12-13 06:27 UTC
I’m going to ignore your attempts to make me angry with your pointless hyperbole.
The fact is, Microsoft has been promising 7.8 as a boon to early adopters who were shafted when they chose not to upgrade flagship phones to 8. They told us the soon to be released 7.8 would get us by until we could buy a WP8 phone. But how could it “get us by” if we won’t get it until several months after most of us upgrade to a new WP8 phone altogether? Face it, we got shafted and that’s it.
You keep forgetting that I was a WP7 user for a very long time, and I still think it’s the best phone platform I’ve ever used. But I’m not going to keep hoping and waiting for more broken promises.
Where exactly did they say it would be released along side WP8?
(source: http://www.zdnet.com/blog/microsoft/microsofts-windows-phone-8-ther… on the day WP8 was unveiled)
I’ve even bolded it for you so you’ll notice it. Windows Phone 8 only went on sale in earnest in November. I think early 2013 is well within the “sometime after Apollo” timeframe.
Complain when they actually slip the deadline, which is possible, but don’t complain before for the sake of complaining. I don’t really care if you’ve used Windows Phone for two seconds or two years, it doesn’t make you any less wrong.
I’m pretty sure that as a developer who has to target 7.8, I’ve spent more time looking into the issue of when it will be out, and what it will contain, than you.
Hopefully, in light of this new evidence you admit you are wrong.
I just did some light browsing on the subject, and the consensus among several tech sites is that Microsoft deliberately held off on announcing the 2013 release date until the end of November to try to keep interest in the entire platform alive. Kind of shady if you ask me; announcing an update without formally offering a release date until it’s no longer relevant. Interestingly, what started this entire heated discussion was you claiming erroneously that Google promised updates but didn’t deliver on it (Google delivered the update, but carriers and OEMs dropped the ball). As that is plainly not the case with JB, but most certainly is with WP7.8, I’d say we’re just going to keep going around in circles here forever.
I guess that there really is a huge difference in perception between an avid user like me and a dedicated developer like you. I’ve got to get back to work so I’ll concede the floor to you. I’m out, you win…whatever it was you thought you would win I guess.
If the end result is that a user doesn’t have an update, it doesn’t matter that OEMs or Carriers are blocking the update.
Google itself recognizes this is a problem, you’re arguing there isn’t a problem. Google tries to remedy this using a Nexus program (which doesn’t work 100%) and I think they tried some sort of OEM agreement for 18 month update support which never panned out.
So when Google itself recognizes there is an issue, but you don’t, it’s quite telling.
Android has a huge, definitive update issue. Microsoft has issues too, but they’re much milder and different in nature.
That’s the bottom line, and I don’t really think its debatable.
I guess that’s as close to a “hey, I was actually wrong” as I’m going to get to you. Whatever.
P.S, I wouldn’t take the “consensus of tech blogs” who all just echo one or two opinions as gospel, especially when there is really no incentive for them to give any indication of a WP7 EOL given that when WP8 was announced WP7 devices were still on sale (and continue to be via low-end devices)
Edited 2012-12-13 07:33 UTC
You’re conveniently limiting Windows Phone to the same release; 8. Yes, technically most Windows Phone users may be on that release, but that is because almost no one bought or is using the previous version. Not because Microsoft has a brilliant method to keep all his users up to date transparently.
The “upgrade” path for the Windows platform is rather torturous; Windows Mobile 6.5, to Windows Phone 7, and then to Windows Phone 8. 3 different incompatible revisions in less than 3 years. While going from a 15% market share, down to 3% in the same period of time. Given that correlation, it seems that Microsoft’s update track record is a significant weakness, not strength.
Edited 2012-12-12 21:27 UTC
Windows Phone total install base was in the millions, I believe over ten million last I checked. However, I don’t see how their update mechanisms have been proven not to scale, to the extent that you use it as an excuse to shrug off the fact that most Windows Phone users are on the latest version of the platform.
Windows Mobile is not Windows Phone. That’s akin to saying that Samsung didn’t provide an update path from their Omnia Windows Mobile lineup to their Galaxy S III. They are clearly different platforms.
Expecting Windows Mobile devices, complete with resistive screens and ancient ARM processors to run Windows Phone is ludicrous. Almost no Windows Mobile device, save for maybe the HD2, met the Windows Phone minimum specifications.
Windows Phone 7 users haven’t been given a raw deal. They received NoDo, Mango, Tango 1, Tango 2, and 7.8
That’s four updates in two years. One of them a major revision. This is not to mention the various value-add companies like Nokia have brought, and continue to bring to the platform.
In fact, that’s likely comparable to any Nexus device out there right now.
That is again, if you lump in Windows Mobile marketshare with Windows Phone marketshare. Windows Phone has gone from 0% to roughly 3% since 2010, and if reports are anything to go by, is selling quite well this quarter.
I don’t know, 3 different completely incompatible iterations in less than 3 years with a user base that shrunk by a factor of 5 during the process, seem like a clear failure to scale, to me at least. I am aware Microsoft’s marketing department may not share that opinion, however.
For what it is worth,I was actually conceding the possibility that what you claimed was true: that the majority of Windows Phone users are at the latest major version (8). I was simply pointing out that the majority of those users are new to that platform, so them being on the latest revision of the software is their default state, thus they have little to do with Microsoft’s supposed competence for upgrading the end user’s platform transparently.
You’d have a point if that was not a completely false equivalence. You’re trying to compare going from two different OS vendors (Microsoft vs Google) as it being the same as upgrading among the same vendor phone OS.
The point being that when it comes to upgrade paths for a phone OS, Microsoft lives in a glass house. So you should be more careful when hurling them rocks around…
Edited 2012-12-12 22:48 UTC
Not what I meant, but I get it, you got your snide remark in. Let’s move on.
The majority of Windows Phone users are on the latest major version for their devices. Windows Phone 7 devices do not have an upgrade path to 8.0, but rather go on to 7.8 .
It’s like when Android launched 3.0 Honeycomb but didn’t provide a path to 3.0 from Phones. That didn’t mean that 2.3 was outdated at the time. Those phones were on their latest revisions.
However, two years after Windows Phone 7 launched, most users are on version 7.1.8773, which is the latest Windows Phone 7 release.
The OSes are fundamentally different, with different user spaces, settings, and application execution models. The perspectives and approaches are different between the two, so it is not possible for old WM 6.5 handsets to be updated to Windows Phone 7.
You conveniently ignore the hardware argument I brought up which mentioned that innovation in Windows Mobile handsets stagnated for years, and most of them were still using resistive screens and slow processors in 2010. The only one up to snuff, somewhat was the HD2.
When it comes to upgrade paths for Windows Phone, I think Microsoft is pretty solid.
They have all WP7 users on the current version of WP7, and have an upgrade path for them which extends into next year and beyond.
It is simple to speak about such things like you do, without having actual hands on experience with devices, or being well versed enough on the platform to understand these differences, but it doesn’t make them non-existent.
The bottom line is: Equating the Windows Phone situation to Android devices that often receive NO updates from Google after launch is NOT a fair comparison.
What? By extension, every Android device is on its latest version too. The Samsung Galaxy Ace Focus Epic 4G MyTouch BBQ ‘s latest version is Android 2.3 – not 4.2. There is no 4.2 for said device, just as much as there is no WP8 for the HD7.
Sure, if that’s what you’d like to keep telling yourself.. but then again, that made up phone doesn’t have a clear update path after 2.3, whereas users on 7.1.8773 do through 7.8.
In fact, that’s probably the only OS revision to ever be officially released for that phone, and that’s where my chief disagreement is.
Windows Phone 7 users have a clear roadmap into the future. Android devices stuck on say, 2.3, don’t really.
I still can’t believe you refuse to accept the differences.
The reason there is no update is purely carrier driven….WP7 devices have another update coming and MS may continue to update the devices until WP8 eclipses the platform.
[a bunch of red herring cut off in order to save time and space]
And yet that is exactly what you keep on doing.
So basically, if I understand the gist of your argument, a comparison is only “fair” so long it makes the Microsoft product look good. Got it.
Google’s upgrade policies may suck for some devices, but implying that Microsoft has a better track record is silly. Specially since the crux for your argument was something that had nothing to do with being the result of software upgrades: brand new users to that platform. Which is what I was pointing out, and since it destroyed your argument you keep trying to dismiss as “snark.”
Edited 2012-12-13 01:01 UTC
No. I said its unfair to say that Microsoft is in the same situation as Google with regards to timely updates because there is no such situation with Windows Phone.
Google stands on its own in being terrible at updates. Microsoft is reasonably good, with iOS being slightly better.
Microsoft does have a better track record. You proved nothing. Especially since there are large swathes of my comment you conveniently refused to address.
In comparison, my SGS4G went from Android 2.2 to Android 2.3 and no further bug fixes in the 2 years it has been out.
Umm… 7 and 8 are developed in tandem right now.
Got nexus 7 recently. Few reboots later running latest version within hours.
I know Android takes ages to start up, but a few reboots equals “hours”? Lol
Not sure if a joke or serious.
Thom;
Final? How many reboots did you have to do?
While we IT-gurus are very interested to have the latest and the greatest OS in our phones, the average Joe Sixpack could not probably tell what kind of an OS the device is running (or it has an OS at all). Those are the people who would find the update very very scary or uncomfortable or extremely distracting and would complain for a carrier immediately. That is the thing that carriers are afraid of and thats why they might choose not to update the phones at all and for a general population of cellphone users that is very acceptable solution.
There should be still those enthusiast phones that get all the updates and other bells and whistles.
“where iOS is the gold standard and shows the industry how it ought to be done, and Android is the exact opposite”
Android got 70+% market share? ..
Don’t you have a blog or something?