- Jun 20, 2011
- 4,995
- 4
- 0
Let me say at the outset, this is not greatly scientific nor backed up by anything I've read from Microsoft on Windows Phone. It is an observation based principally on my many years working with Microsoft's servers, desktop products and its methodology.
But let me know what you think.
There has been a number of questions about battery life post official Mango and I've thought about it in a number of ways and it comes down to methodology.
Everything Microsoft has done over the years involves a registry of some kind. A place where all settings, pointers and such are stored. It seems to me Windows Phone 7 is no exception to that rule.
Mango is, for all intents and purposes a bundle of registry entries which on the back-end seek to link "related" apps to one another. In order that the phone perform fluidly is has to seek out those related apps, build a database and store the results in a registry. Then, for example, when you Bing search a movie and want details on it, the app hosting that information is already ready with the results. There is no stop the browser, back out, press the app button, head to the app list, scroll to find IMDB or Flixter, launch the app, wait for it to load, search again and scroll to the result. The information you need is there with Windows Phone. Read it, buy a ticket because the ticket app is already linked and even get directions because that app is already linked and get on with life.
But it takes some work under the hood to make that happen and that will require power and the initial Mango bump has much work to do. The principal power source for Windows Phone 7 is your battery. I'm surmising this may be the cause of some unexpected battery drain post Mango and should improve once the database construction is complete.
Could it be constant hammering the database and registry ie increased battery load? In my opinion no. I don't however believe this process is constant because I've run RTM Mango as did others and NO ONE I've read reported issues with battery life. In fact, just the opposite.
I'll see if I can't get some more background and supporting information and update the thread if need be. Time for coffee.
But let me know what you think.
There has been a number of questions about battery life post official Mango and I've thought about it in a number of ways and it comes down to methodology.
Everything Microsoft has done over the years involves a registry of some kind. A place where all settings, pointers and such are stored. It seems to me Windows Phone 7 is no exception to that rule.
Mango is, for all intents and purposes a bundle of registry entries which on the back-end seek to link "related" apps to one another. In order that the phone perform fluidly is has to seek out those related apps, build a database and store the results in a registry. Then, for example, when you Bing search a movie and want details on it, the app hosting that information is already ready with the results. There is no stop the browser, back out, press the app button, head to the app list, scroll to find IMDB or Flixter, launch the app, wait for it to load, search again and scroll to the result. The information you need is there with Windows Phone. Read it, buy a ticket because the ticket app is already linked and even get directions because that app is already linked and get on with life.
But it takes some work under the hood to make that happen and that will require power and the initial Mango bump has much work to do. The principal power source for Windows Phone 7 is your battery. I'm surmising this may be the cause of some unexpected battery drain post Mango and should improve once the database construction is complete.
Could it be constant hammering the database and registry ie increased battery load? In my opinion no. I don't however believe this process is constant because I've run RTM Mango as did others and NO ONE I've read reported issues with battery life. In fact, just the opposite.
I'll see if I can't get some more background and supporting information and update the thread if need be. Time for coffee.
Facebook
Twitter
Instagram