Background tasks

With the Windows Phone 7.8 update finally starting to find its way on board user’s devices, bringing with it the cosmetic upgrades of Windows Phone 8, here at Windows Phone Central our readers are noticing that not all is well for their newly-sized live tiles.

Users over in our forums have spotted that since the 7.8 update, their live tiles (those updated by background tasks at least) do not seem to be refreshing correctly.

A lot of times these issues are device specific, but in this case we’re not convinced. I recently had a conversation with Lawrence Gripper (developer of BBC News Mobile) after he got in touch to ask if we had been receiving an abnormal number of support requests since 7.8, we have. Just like the reviews you'll see for BBC News Mobile, several users have been in touch complaining that their tile seems to have ceased updating now that they have installed the new OS update.

-
loading...
-
loading...
-
loading...
-
loading...

We heard and experienced for ourselves some rather crummy battery life with the Nokia Lumia 920 Windows Phone. It's a mixed bag of results with some report fantastic battery performance while others are struggling to make it through half a day.

While Nokia is looking into things, they've reminded us that managing the apps that are running in the background could help with battery life.  And this power saving technique isn't exclusive to the Lumia Windows Phones.  If you want to conserve power on your HTC 8X or Samsung Focus 2, shut down some of the apps you don't need that are still running in the background.

-
loading...
-
loading...
-
loading...
-
loading...

Recently here at Windows Phone Central we've received a few help requests through our app from users whose live tiles all appear to have stopped updating, including our own. Previously there have been bugs in our app that would cause its tile to fail, but when all live tiles on a device that rely on Background tasks get stuck, there's a bigger problem.

Up until this point I have been unable to reproduce the issue myself so I've been struggling to assist those of you asking us for a solution. In a stroke of luck though my Lumia 800's tiles recently stopped updating at all (excluding those updated through push notifications), and after a simple restart of the phone didn't help I have a solution to share with you all.

2
loading...
5
loading...
68
loading...
0
loading...

Earlier today we called attention to new changes being brought about with the release of Windows Phone SDK 7.1.1, the release supporting 'Tango' in all it's low-end/budget glory.

We also mentioned in that article that only 5% of apps wouldn't run in the new hardware configuration, which is down to the amount of memory they utilise whilst active. However looking over this msdn page we wanted to make it crystal clear to our community that in fact there is a limitation for our new friend the Lumia 610: it won't run Background Tasks.

Specifically, generic background tasks are not supported for devices with 256MB of memory. A perfect example would be the background task used to update the live tile and cache in our own app. These types of tasks are known to developers as Periodic tasks and Resource Intensive tasks (if you want to understand the difference I recommend reading this overview). The potentially good news is that some types of background task, such as the background Audio agent which is used for playing music or podcasts after the app has been de-activated, look to be supported still.

A question therefore which I put to our readers, is this the first sign of platform fragmentation? Can we still state that "you get the same great Windows Phone experience on any handset"? Or is this a reasonable omission for the sweeter price spot?

Update: A quick clarification as some of our commenters aren't too sure, this does not affect fast app switching (part of the multitasking functionality) and nor does it affect push notifications which generate live tiles or toast messages. I'd also like to state that if apps make use of Background tasks Microsoft have provided methods for developers to identify when a "mid-tier" device is being used before trying to enable the task, thus allowing users to continue using all other features of the app in question.

Update 2: Justin Angel argues (very well) that this is not mobile fragmentation, as technically developers will write code once which can then be run on any Windows Phone platform, although developers may still be required to test for these mid-tier devices and run functions of their apps in accordance. Instead Justin suggests that this classifies as 'device differentiation', in the same way as not having a gyroscope or front facing camera in your device.

2
loading...
1
loading...
51
loading...
0
loading...