Android Policy For Nexus and Google Play Devices Updated To Excuse Carrier Delay

← Back to Stories (view on slashdot.org)

Android Policy For Nexus and Google Play Devices Updated To Excuse Carrier Delay

Posted by Soulskill on Wednesday December 3, 2014 @05:26AM from the under-construction-expect-delays dept.

An anonymous reader writes: Google has quietly updated its Android update policy for both Nexus and Google Play edition devices. In short, if you bought either type of smartphone or tablet from a carrier, you may experience delays that result in waiting longer than two weeks to get the latest version. Google has tweaked the "Android updates: Nexus & Google Play edition devices" support page to add, "Based on your carrier, it may take longer than two weeks after release to get an update." It's worth emphasizing this won't stop you from downloading a given Android update directly from Google or your device's manufacturer, and installing it yourself on your device. This is mainly for over-the-air updates, which carriers can choose to delay on their own networks.

73 comments

Min score:

Reason:

Sort:

Downloadable updates for CDMA2000 devices? by tepples · 2014-12-03 05:35 · Score: 2

It's worth emphasizing this won't stop you from downloading a given Android update directly from Google or your device's manufacturer, and installing it yourself on your device.
Do Google and the devices' manufacturers even make downloadable updates available for CDMA2000 and CDMA2000/LTE devices, such as those used on Verizon, Sprint, and Sprint MVNOs? I thought they were just for devices designed to run on GSM/UMTS/LTE carriers.
1. Re:Downloadable updates for CDMA2000 devices? by Anonymous Coward · 2014-12-03 06:52 · Score: 0
  
  They make those?
2. Re:Downloadable updates for CDMA2000 devices? by tepples · 2014-12-03 06:57 · Score: 1
  
  Do Google and the devices' manufacturers even make downloadable updates available for CDMA2000 and CDMA2000/LTE devices, such as those used on Verizon, Sprint, and Sprint MVNOs?
  They make those?
  Yes, for the U.S. market. Verizon and Sprint expect their subscribers to buy hardware directly from them.
3. Re:Downloadable updates for CDMA2000 devices? by mrchaotica · 2014-12-03 07:07 · Score: 1
  
  Well, the Nexus 5 is a combo GSM/CDMA device (compatible with Sprint, at least), and they make downloadable updates available for that...
  
  --
  "[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz
4. Re:Downloadable updates for CDMA2000 devices? by unixisc · 2014-12-03 08:21 · Score: 1
  
  So how do I get Lollipop on my Verizon Ellipsis 7? It has Android 4.2 on it. What are Lollipop's minimum requirements?
Doesn't apply to Google by Anonymous Coward · 2014-12-03 05:37 · Score: 0

So then why hasn't my 2013 Google Nexus 7 received the Lollipop update? It's been over a month since it was released, clearly longer than the two weeks stated by Google.
1. Re:Doesn't apply to Google by Anonymous Coward · 2014-12-03 05:49 · Score: 0
  
  Probably something to do with your update settings. Look to yourself as the source of problems before you start blaming others.
2. Re:Doesn't apply to Google by MightyMartian · 2014-12-03 05:49 · Score: 2
  
  You don't want Lollipop at this point. It has created a helluva lot of carnage for Nexus 7 2012 and 2013 users. My Nexus 7 was rendered all but unusable, and even a factory reset has only created moderate improvements.
  
  --
  The world's burning. Moped Jesus spotted on I50. Details at 11.
3. Re:Doesn't apply to Google by ottothecow · 2014-12-03 05:54 · Score: 1
  
  Was yours a 2013 or a 2012? I haven't updated mine yet (was trying to figure out if it was safe to accept the OTA update if I had rooted it with Towelroot...and I lost my train of thought and the notification disappeared), but now you have me worried.
  
  --
  Bottles.
4. Re:Doesn't apply to Google by gstoddart · 2014-12-03 05:55 · Score: 1
  
  Oh? What kind of stuff? I have a 2012 Nexus 7 ... at least, I think it's a 2012 version, I've lost track.
  I haven't been offered the update, but I'm wondering about the kinds of problems you've had.
  I don't want to "upgrade" only to find out I've ended up with a less usable device.
  
  --
  Lost at C:>. Found at C.
5. Re:Doesn't apply to Google by Anonymous Coward · 2014-12-03 06:06 · Score: 0
  
  Really? I have the 2012 Nexus 7 and find it has improved performance while my Nexus 5 has issues almost daily. I used to go weeks without rebooting my phone, but after it updated to 5.0, it gets rebooted every 2-4 days now.
6. Re:Doesn't apply to Google by MightyMartian · 2014-12-03 06:29 · Score: 1
  
  Well, after the Lollipop update, my 2012 Nexus was all but bricked. Booted up fine, but the minute I went into Chrome it just froze up. It might become somewhat usable after a few minutes, and it was during one of those moments that I managed to do a factory reset. It is working better, but Chrome can still seize up on script-heavy pages. Go to the Google Nexus 7 Product Forums and you will see plenty of tales of woe.
  It isn't universal, but there are a helluva lot of Nexus 7 users, both 2012 and 2013, who have had serious problems with Lollipop.
  
  --
  The world's burning. Moped Jesus spotted on I50. Details at 11.
7. Re:Doesn't apply to Google by rodrigoandrade · 2014-12-03 06:32 · Score: 1
  
  You have to clear the data/cache from within recovery. Look it up, as I use CWM recovery and don't know how to do it in stock recovery.
8. Re:Doesn't apply to Google by rodrigoandrade · 2014-12-03 06:35 · Score: 1
  
  Get the image straight from Google as TFS suggested and flash it manually.
  
  https://developers.google.com/android/nexus/images
9. Re:Doesn't apply to Google by MightyMartian · 2014-12-03 07:18 · Score: 1
  
  I initially did that and it made very little improvement. In the end the factory reset was the only thing that brought the tablet back to life. Mind you, I don't have the Facebook app, and what I've been hearing is that can render Nexus 7 tablets pretty unusable under Lollipop even after a factory reset.
  
  --
  The world's burning. Moped Jesus spotted on I50. Details at 11.
10. Re:Doesn't apply to Google by lgw · 2014-12-03 07:49 · Score: 1
  
  My 2009 (IIRC) Android phone hasn't been updated since the first year, and is still running 2.somthing, I think. I should really buy a new phone one of these days (the glass has been cracked for a year now), but it seems such a frivolous expense.
  
  --
  Socialism: a lie told by totalitarians and believed by fools.
11. Re:Doesn't apply to Google by war4peace · 2014-12-03 08:09 · Score: 1
  
  Anecdotal evidence:
  I bought a Nexus 7 2012 for my wife exactly the day Lollipop was released. It had 4.1 on it, or something. It offered OTA updates for several versions all the way to 4.4.4 that evening, and 3 days later offered a Lollipop update which I promptly accepted. Went on without a hitch, now she has a great, responsive tablet.
  Others might have been unlucky, not me.
  
  --
  ...gis sdrawkcab (usually not responding to ACs; don't bother posting as AC)
12. Re:Doesn't apply to Google by rickb928 · 2014-12-03 08:22 · Score: 1
  
  Let it go. Please.
  Every useful site that discusses this already pointed out that these OTA releases are staged to avoid overwhelming networks (even your lame WiFi you steal from your neighbor) and to catch any problems before they blow it all out to every user.
  Whiners asking 'why haven't its been so long i never get' apparently did not read any of these. Please go find a site that makes this clear, and stick to it for future useful information. The others, feh.
  And, if you have not already seen (which I'm sure you haven't), 5.0.1 is released. Looks like 5.0 had enough problems for a maintenance update already. You should now breath a sigh of relief that you did not get an update, which would have annoyed you with any of the myriad nuisances out there.
  My N7 2013 is still waiting also, and I decided not to sideload it. Now I'll wait for 5.0.1 to go through the GPE devices, then through the early update populations, and I bet it goes around pretty quickly. There is evidence that 5.0 had enough bugs that Google convinced the manufacturers to hold off and wait for a minor (?) patch.
  
  --
  deleting the extra space after periods so i can stay relevant, yeah.
13. Re:Doesn't apply to Google by ottothecow · 2014-12-03 08:41 · Score: 1
  
  Why not get a free phone? I don't know about this lollipop business, but my 2013 Moto X has been an absolutely excellent phone running android 4 (the 1st gen Moto X is optimized for user experience rather than raw power...and it isn't as huge as the new Moto X). Big improvement over my old android 2 phone and I believe they are available for free on a contract right now.
  Before anyone jumps on my neck about "on a contract does not equal free", you've been paying for your current phone service since 2009. If you had gotten a free phone back in 2012, that contract would have expired by now and you'd be in exactly the same situation as you are currently in, except you would have a new phone. T-mobile I believe is the only big carrier who offers a discount for owning your own phone, so unless you really plan to switch carriers all of the time, it is silly to keep paying the same rate and *not* take advantage of the phone subsidy.
  and FWIW, you should be able to keep your old contract terms. Until last week I was on some ancient grandfathered texting plans and another family member was still on unlimited data despite updating our phones multiple times. Discovered last week, that the whole family plan could be ~$30 a month cheaper if we went to shared data between the phones (with a cap greater than our combined usage), and we got switched from limited minutes/texting to unlimited talk/text.
  
  --
  Bottles.
14. Re:Doesn't apply to Google by lgw · 2014-12-03 09:07 · Score: 1
  
  I use T-Mobile, have never had a phone on money, and have a strict "never borrow money" personal policy. But it's not about the amount a phone costs, it's about a strong aversion to spending money on things that aren't really important to me.
  
  --
  Socialism: a lie told by totalitarians and believed by fools.
15. Re:Doesn't apply to Google by tohoward · 2014-12-03 09:14 · Score: 1
  
  My Nexus 7 2012 wasn't "bricked", but it now takes a LONG time to "wake up" when it's wifi has been shut down, and the tablet is all but unusable for minutes while it recovers. I've taken to "closing" all my applications when I'm done using them (which I've NEVER done), and it seems to help a little. It's the first update I've not been impressed with, and that I think I'd roll back if I could (I haven't checked if I can).
16. Re:Doesn't apply to Google by lgw · 2014-12-03 09:26 · Score: 1
  
  *have never had a phone on contract
  
  --
  Socialism: a lie told by totalitarians and believed by fools.
17. Re:Doesn't apply to Google by MightyMartian · 2014-12-03 10:24 · Score: 1
  
  If a factory reset by and large fixes the problem, that likely means there are issues with data and apps previously installed. If you have a brand new tablet, then you are not going to have a lot of cruft hanging around. My tablet is over a year and a half old, never reset during that time, and that seems to be one of the issues coming up.
  
  --
  The world's burning. Moped Jesus spotted on I50. Details at 11.
18. Re:Doesn't apply to Google by dkman · 2014-12-03 10:26 · Score: 1
  
  At least you're free to downgrade back to a prior version of android. That's my biggest pet peeve with iOS.
  
  --
  I refuse to sign
19. Re: Doesn't apply to Google by cyber-vandal · 2014-12-03 11:04 · Score: 1
  
  So where are these update settings on my Nexus 7 and why haven't they prevented me getting KitKat updates? Stupid fucking neckbeard fanbois.
20. Re:Doesn't apply to Google by war4peace · 2014-12-03 12:12 · Score: 1
  
  Just clear the Dalvik cache and it's gonna be fine.
  
  --
  ...gis sdrawkcab (usually not responding to ACs; don't bother posting as AC)
21. Re:Doesn't apply to Google by peragrin · 2014-12-03 13:28 · Score: 1
  
  I would like to try it though. my nexus 7 2013 hasn't received it yet. I had to force the kitkat upgrade through manually a month later. Google's update schedules are very strange.
  IOS 8 on the other hand asked for the update a day after apple announced it.
  
  --
  i thought once I was found, but it was only a dream.
22. Re:Doesn't apply to Google by Anonymous Coward · 2014-12-03 18:56 · Score: 0
  
  Google staggers the updates so individual people don't get shitty download rates. Don't tell me that doesn't happen, because I've seen it... and other people have seen the demands other server-based services get.
23. Re:Doesn't apply to Google by Archibald+Buttle · 2014-12-03 22:46 · Score: 1
  
  And yet Apple manages to make their iOS updates available to all compatible devices on the day of release, dealing with an order of magnitude more devices than Nexus phones and tablets.
  My Nexus 10 had to wait 2 weeks for the 5.0 update to be made available to it, and my Nexus 4 took a month. The story has been the same with every single Android update - I read that an update is available, and then don't see it for weeks or months, no matter how many times I check for updates. In contrast on all my iOS devices never have any wait.
  In both cases I get to choose if I want to install the update or not.
  I don't buy "OTA releases are staged to avoid overwhelming networks", especially since the sales figures for Nexus devices are relatively small. As for "catch any problems", that is much more believable, but it reeks of poor QA. The implication is they have little confidence in the quality of their product.
  The reality is that no matter the justification, it's poor customer service. If you loudly tell the world "Android 5 is out for your device" then you should make sure it's out.
24. Re: Doesn't apply to Google by rickb928 · 2014-12-03 23:39 · Score: 1
  
  You know the answer. Android releases must be adapted to the different makes and models of phones. Apple has to deal with about 6 different phones. Samsung alone has more different models.
  
  --
  deleting the extra space after periods so i can stay relevant, yeah.
25. Re: Doesn't apply to Google by praxis · 2014-12-04 05:26 · Score: 1
  
  From what I understand, Google hands over bits to the carriers, and the carriers then choose a timetable for automatic updates. The argument that saturating (really, how big are these updates and how many devices that this is a major concern?) networks makes sense here, but the number of models does not. The issues stemming from number of models will be caught by Google's testing before the release bits get sent to the carriers.
26. Re: Doesn't apply to Google by rickb928 · 2014-12-04 09:57 · Score: 1
  
  Google does not do integration for the carrier-specific bits. Whine to your carrier about their slow progress.
  
  --
  deleting the extra space after periods so i can stay relevant, yeah.
27. Re: Doesn't apply to Google by praxis · 2014-12-04 12:46 · Score: 1
  
  I don't use an Android device, so I have nothing to complain about. I was under the impression that Nexus devices did not have carrier-specific-bits, which is why I was trying to understand the reason for a delay. Network saturation makes no sense, since it's clear that other eco system can handle a release day over the same networks. Testing makes no sense, since Google tests their bits before giving it to carriers. If the carriers want to integrate other bits for other devices, fine, but why delay Nexus updates for that reason?
28. Re: Doesn't apply to Google by rickb928 · 2014-12-05 00:32 · Score: 1
  
  1. That other eco system doesn't deliver updates to every single device on the same day.
  2. Nexus devices are popular enough to be a big enough population to encourage staging updates.
  
  --
  deleting the extra space after periods so i can stay relevant, yeah.
29. Re: Doesn't apply to Google by praxis · 2014-12-05 06:40 · Score: 1
  
  That other eco system doesn't deliver updates to every single device on the same day.
  Well, I don't know what you mean by "every single device", since not all updates are for every device. But, they do *offer* the update to every *eligible* device starting on one single day. If a customer wants the update, they touch a button. If a customer has automatic updates, they'll get it sometime "soon", where "soon" is indeed staggered and might be a day or so later. For people that want it, they get it day 1. For people that don't care or pay attention, they get it anytime from day 1 to day N (where N in my experience has been single digits. For people that don't want it, they never get it.
ISP by danbob999 · 2014-12-03 05:54 · Score: 1

Since my computer is on their network, will ISPs start delaying Windows Update too?
1. Re: ISP by Anonymous Coward · 2014-12-03 05:59 · Score: 0
  
  Yes
2. Re:ISP by Richard_at_work · 2014-12-03 06:10 · Score: 1
  
  ISPs dont push out Windows updates, so its not a valid comparison.
3. Re:ISP by Anonymous Coward · 2014-12-03 06:16 · Score: 0
  
  Carriers also aren't the ones who push the updates to my iPhone so I don't have to wait weeks or months for an update.
4. Re:ISP by danbob999 · 2014-12-03 06:38 · Score: 2
  
  Carriers shouldn't be pushing cell phone updates either. Especially not on Nexus devices.
5. Re:ISP by Anonymous Coward · 2014-12-03 06:54 · Score: 1
  
  That's because Apple forbid carriers from fucking around with iOS devices to hard code their own shitware into them.
  Fucking Verizon apps eat up valuable space on my GS IV and I can't get rid of them without rooting it.
6. Re:ISP by gstoddart · 2014-12-03 07:36 · Score: 2
  
  But ... but ... branding!
  How are corporations supposed to monetize your telephone if they can't put additional shit to change "your" phone to maximize their profits?
  Yeah, I'm with you. I thought the whole point of the Nexus devices was you get the full Android experience and it hasn't been mucked with.
  I have Facebook and some other crap on my phone my carrier put there. I can disable it, but I can't uninstall it. I bought the phone outright, what the hell do you mean I can't uninstall your crapware?
  
  --
  Lost at C:>. Found at C.
7. Re:ISP by Anonymous Coward · 2014-12-03 12:52 · Score: 0
  
  But ... but ... branding!
  How are corporations supposed to monetize your telephone if they can't put additional shit to change "your" phone to maximize their profits?
  They'll inject cookies and advertising when they sniff your traffic and detect http responses going to your device?
8. Re:ISP by Anonymous Coward · 2014-12-03 19:07 · Score: 0
  
  Who needs carriers to install bloatware when the home office does it for you? Don't worry, I'll get to use that Stocks by Yahoo(TM) at some point...
9. Re:ISP by praxis · 2014-12-04 05:28 · Score: 1
  
  And that's why you should be using HTTPS everywhere you browse.
nope by Imazalil · 2014-12-03 05:58 · Score: 1

Coward isn't the only one, mine hasn't received it either. My Nexus4 just got it last week.
Though from the sounds of it, it's well advised to wait for a .1 release to come out.
1. Re:nope by sumdumass · 2014-12-03 06:10 · Score: 1
  
  It says longer than two weeks. Not within two weeks. It also places this blame on your carrier and their settings.
  My first thought was that this was their answer to fast lanes- if a carrier dlowed them down they would make the carrier look like it isn't as good as others instead of paying. But it might be the opposite- so the carrier's network doesn't get saturated with large updates. This would explain giving them the control. However, it can always be used to obsolete a product and trick you into extending a contract lock in.
2. Re:nope by danomac · 2014-12-03 09:31 · Score: 1
  
  That's really strange, my 2012 Nexus 7 got it quite a while ago now. More than a week for sure. Maybe even two weeks now.
3. Re:nope by tchuladdiass · 2014-12-03 16:43 · Score: 1
  
  The way the updates work: When the device check Google for an update, for the first few days it gets a random chance of 1 in 100 of being selected. That chance is then reset after a few days, so when it checks again it gets another chance, maybe 5 in 100. Note, that once the dice is rolled, no matter how often it checks for updates, it will always get the same decision until a certain time has elapsed. This chance increases as time goes on, allowing more devices to get the updates. If there are a significant number of issues reported during the first few days, this gives Google a chance to address the issues with additional patches, or to pull the update completely if required.
Update Throttling.. the next big deal by Mr+D+from+63 · 2014-12-03 06:08 · Score: 1

Yup, stagger those updates so the ISPs don't have a big peak. ITS NOT FAIR! How do they choose who must wait UP TO TWO WEEKS? Probably start with the list of those that signed Obama's petition.

I demand action.
1. Re:Update Throttling.. the next big deal by sumdumass · 2014-12-03 06:16 · Score: 1
  
  Where is this up to at? Everything i can find says longer than 2 weeks. You may be waiting longer.
2. Re:Update Throttling.. the next big deal by Karlt1 · 2014-12-03 06:20 · Score: 1
  
  Yup, stagger those updates so the ISPs don't have a big peak. ITS NOT FAIR! How do they choose who must wait UP TO TWO WEEKS? Probably start with the list of those that signed Obama's petition.
  You're right. It's not like any mobile operating system provider is able to push OS updates out simultaneously across multiple carriers worldwide......
  Why does Google depend on the carrier to push operating system updates out for its own devices and Apple doesn't?
3. Re:Update Throttling.. the next big deal by TheCastro1689 · 2014-12-03 06:59 · Score: 1
  
  Maybe it has to do with carrier specific versions of Android? I don't know, only speculating.
4. Re: Update Throttling.. the next big deal by Karlt1 · 2014-12-03 07:09 · Score: 1
  
  Isn't the whole purpose of buying a Nexus is that you get a "pure Android" experience without carrier crapware?
5. Re: Update Throttling.. the next big deal by Anonymous Coward · 2014-12-03 07:18 · Score: 0
  
  Still has to be rolled out by the carriers.
6. Re:Update Throttling.. the next big deal by rsborg · 2014-12-03 07:54 · Score: 1
  
  Yup, stagger those updates so the ISPs don't have a big peak. ITS NOT FAIR! How do they choose who must wait UP TO TWO WEEKS? Probably start with the list of those that signed Obama's petition.
  I demand action.
  Meanwhile, Apple users simply smile - why is it that one OS gets fast, streamlined updates, while the other major ome (supposed superior) is hobbled by the carriers schedules? I mean, it's not like Apple's phones run on some proprietary network ...
  Can someone explain this for me?
  
  --
  Make sure everyone's vote counts: Verified Voting
7. Re:Update Throttling.. the next big deal by Mr+D+from+63 · 2014-12-03 08:05 · Score: 1
  
  Do you know for sure that all OS devices are updated at the same time or within 2 weeks?
8. Re:Update Throttling.. the next big deal by Anonymous Coward · 2014-12-03 08:37 · Score: 0
  
  Yes, all iOS devices get the updates the exact same day since the updates come from Apple.
9. Re:Update Throttling.. the next big deal by Anonymous Coward · 2014-12-03 19:15 · Score: 0
  
  Remind me which version you get? The one without voice assistant?
  Or the one where the features are added in years later (S Health has been kicking around for 2+ years now, NFC for even longer, etc).
  Meanwhile, the vast majority of features on Android can be approximated / replicated from Google Play.
  Also, didn't one of the updates totally fucked up certain devices? That's pretty sad that they screwed up when they only have like 1 device to patch LOL
10. Re: Update Throttling.. the next big deal by praxis · 2014-12-04 05:33 · Score: 1
  
  Which makes the Nexus experience no longer free from Carrier Crap, which is a shame.
The Flaw with this model by gizmo2199 · 2014-12-03 06:14 · Score: 4, Interesting

Having carriers be in charge of updating smartphone firmware negates any benefit you might get from having a device that often costs more than $500. This is specific to Android, since Apple made sure they had complete control of the OS and the update process on their phones.

Just to name one: security issues are constantly cropping-up in Android, and Google is constantly patching things. Except good luck getting AT&T or Verizon to provide the updates OTA. And if you're stuck with an older phone, says > 1 year. Good luck getting any update at all.

As far as the carrier is concerned, in order to update the firmware, buy a new phone. Except you've now deliberately left millions of people vulnerable to having their accounts compromised because you were too cheap/lazy to provide an update (which Google makes available, btw).

Either Google should unify Android, meaning make one version for all models (or at least models newer than 3 years) and make it available OTA or by download, or license Android to carriers on the strict condition that they provide updates to existing models at least every 6 moths.

--
This Sig does not Exist.
1. Re:The Flaw with this model by rickb928 · 2014-12-03 09:46 · Score: 1
  
  My M7 got updated to Kit Kat about 16 months after purchase, and will get Lollipop on time, probably 19 months after purchase.
  Blanket 'they don't update phones >1 year old' statements are both false and unfounded. If 1) Google gave your manufacturer an image, and 2) your manufacturer customized it, then 3) the carrier has to brand it and release to you. If step 2 or 3 are missed, blame the appropriate party.
  If Google decided not to issue an image, it is likely because they unilaterally decided the phone was not capable of providing an adequate user experience with the new software. My G1 went through this, and my Sensation 4G also. my M7 and M8 will too someday.
  
  --
  deleting the extra space after periods so i can stay relevant, yeah.
2. Re:The Flaw with this model by ProzacPatient · 2014-12-03 10:14 · Score: 1
  
  ... good luck getting AT&T or Verizon to provide the updates OTA. And if you're stuck with an older phone, says > 1 year. Good luck getting any update at all.
  If carriers even bother to provide updates at all they usually lag so far behind because they need to develop and test all their bloatware against the latest version of Android. Samsung in particular insists on using TouchWiz on their mobile devices so TouchWiz needs to be updated for every version of Android and then on top of that the carriers need to test update and test their bloatware and whatever else they insist on installing on devices.
  One solution is to install CyanogenMod if you can but that will void the warranty on your $500+ phone and some carriers might even terminate your service if they suspect you're not running official carrier firmware (Because for example CyanogenMod lets you tether without paying for the carrier's tethering fees).
Fix lollipop to work with exchange activesync! by Anonymous Coward · 2014-12-03 06:44 · Score: 0

Android 5.0 will NOT work if you use certificate authentication with exchange.
Amongst many other flaws...
Re:Hahahah by Archangel+Michael · 2014-12-03 06:53 · Score: 0

Oh gawd, you're one of those fringe Windows Phone guys aren't you? They still make windows phones?

--
Agent K: A *person* is smart. People are dumb, stupid, panicky animals, and you know it.
Re:Hahahah by Anonymous Coward · 2014-12-03 07:10 · Score: 0

Windoze on a phone? You best be joking, nigga.
Re:Hahahah by Anonymous Coward · 2014-12-03 09:18 · Score: 0

If you see someone with a Windows phone, they work for Microsoft.
Re:Hahahah by Lunix+Nutcase · 2014-12-03 09:21 · Score: 0

Nope, even they don't want Windows phones.
No carrier and yet no OTA update on Nexus 7 by Anonymous Coward · 2014-12-03 10:55 · Score: 0

I have a Wi-fi Nexus 7 2013, no carrier, and yet the OTA update for Lollipop has not been offered (via the settings-about tablet-software update page), though OTA install files have been available for several weeks. I'm not really complaining since I don't think apps are ready for Lollipop yet. I have several apps that are not Lollipop compatible and I would not want to do without them, hence am in no hurry to update. But it seems odd that the update hasn't even been offered.
1. Re:No carrier and yet no OTA update on Nexus 7 by Thantik · 2014-12-03 15:25 · Score: 1
  
  Some of your apps aren't going to ever BE lollipop compatible. At least 2 of my apps broke due to deprecated APIs that were removed for security purposes (one had the ability to show widgets on the foreground of other apps, so for example, I could control pandora while having waze open).
There are 2 different issues here... by jonwil · 2014-12-03 12:52 · Score: 1

The first issue is that it can take time for updates to roll out over-the-air even once they are available. There are usually ways to manually download and install it if you dont want to wait for OTA.
The second issue (and the more important one) is that for many phones carriers will take sometimes months to approve an update or may not release it all (usually making some claims about some "carrier acceptance testing" BS). In some cases updates for the generic unbranded versions of a phone still get hit with a delay in order to keep the OEMs carrier partners happy.
Apple got it right by controlling all updates for the phone from day one and not giving the carriers any ability to block or hold up updates.
not just devices sold by the carrier by KernyKat · 2014-12-03 17:06 · Score: 1

It's significant to note that it doesn't matter where you bought your device - even Nexus devices purchased directly from Google Play can be blocked by the carrier.
e.g. The network with the largest market share in Australia, Telstra - is blocking the Lollipop OTA update from all Nexus devices.