Linked by Thom Holwerda on Tue 11th Dec 2012 23:09 UTC
Permalink for comment 544776
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 06/18/13 22:33 UTC
Linked by Anonymous on 06/18/13 22:26 UTC
Linked by Thom Holwerda on 06/18/13 22:25 UTC
Linked by Thom Holwerda on 06/18/13 17:45 UTC
Linked by Thom Holwerda on 06/18/13 17:32 UTC, submitted by poundsmack
Linked by Thom Holwerda on 06/17/13 17:58 UTC
Linked by Thom Holwerda on 06/17/13 17:52 UTC
Linked by Thom Holwerda on 06/14/13 21:03 UTC
Linked by Thom Holwerda on 06/14/13 20:46 UTC
Linked by Thom Holwerda on 06/14/13 17:32 UTC
More News »
Sponsored Links



Member since:
2005-11-29
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.