Battery Saver crash on usage data with 8.1 Update + Cyan

[Teeeerex]

I bricked my phone (sad face bluescreen) by messing with this issue (soft resetting while in Storage Sense - don't do that folks) so, having to reflash it, while I was at it, I decided to debrand the phone and flash it with the appropriate country variant, + Cyan. Reenrolled into DP, updated to Update 1, restored backup. Almost everything works, I even got Google Sync to work again - thank God ) - except one thing - Battery Saver.

Opening usage data crashes it every time, but only on the current date. If I set the date to tomorrow or yesterday, or any other day or year, it opens. Update the date and time - crash again. Soft resets don't help. Now, I'm gonna let sleeping dogs lie for a few days and simply not open usage data, in hope that it self-heals, and won't rush for a hard reset again, but I just wanted to ask - has anyone seen this? And did it self-repair over time?

 

[dKp1977]

Try and set your date to something like 2100 or so. When you try and open the app, it should prompt you to uninstall it due to it being outdated. Do so, set correct date and time again and download the app from the store again.

 

[Teeeerex]

Try and set your date to something like 2100 or so. When you try and open the app, it should prompt you to uninstall it due to it being outdated. Do so, set correct date and time again and download the app from the store again.

Only a date after 2100 triggers this behavior?

 

[Teeeerex]

No, nothing happened. It just opened. Usage data works, obviously. When the date is off, of course.

 

[Teeeerex]

By the way, I can open Battery Saver from Settings, because it opens to the Settings pivot. When I move to usage - crash to Start screen.

 

[dKp1977]

No, nothing happened. It just opened. Usage data works, obviously. When the date is off, of course.

Then try an even later date. 2300 or so. At some point you should get a popup telling you it's out of date, with the option to uninstall.

 

[Teeeerex]

No, it simply doesn't work any more.

 

[dKp1977]

No, it simply doesn't work any more.

That's truly weird. Probably it just doesn't work with battery sense, considering it's a "usual" app and not only tied to the settings anymore. The aforementioned workaround works for settings-apps. I'm not having my phone with me, so I can't check myself, but are you able to simply uninstall battery sense from the app list? I guess not.

 

[Teeeerex]

That's truly weird. Probably it just doesn't work with battery sense, considering it's a "usual" app and not only tied to the settings anymore. The aforementioned workaround works for settings-apps. I'm not having my phone with me, so I can't check myself, but are you able to simply uninstall battery sense from the app list? I guess not.

No, it's that nice kind of WP app that is updatable, but that's about it. No other manipulation is possible. I might wait until a further Developer Preview system update - all apps will be reinstalled then. Or maybe they'll update the app. I can work on background tasks when I change the date.

 

[Teeeerex]

Maybe the waiting did it, but it was more likely today's update for DP - this issue is no more.

 

[Tony Varela]

Mine started doing the same thing this morning. Soft reset didn't do anything. Battery Saver usage screen crashes phone back to start screen. I can open battery saver --> settings through the settings menu. When I slide the screen over to usage, I get the same crash. Looks like your issue worked itself out. I guess I'll wait a day or two before doing a hard reset.
Do you know what specific update might have caused this?
Thanks!

 

[woodduckie]

I have the same thing after a day of installing the official 8.1 release on my AT&T 920.

I can view & change battery saver settings, but the app will crash when swiped to usage, leaving no way to adjust background permissions.

I've tried multiple soft resets. I uninstalled insider & another battery monitoring app.

Since there is no option to uninstall (as previously mentioned), I tried pushing a reinstall from the windows phone marketplace to no avail.

I can wait a couple of days, but I don't have a lot of confidence that it will "heal" itself...

 

[woodduckie]

In spite of my skepticism, batter saver is functional once again.

I suspect usage data is a "rolling" history.

Wondering if it has issue with an app that was once tallied in the battery saver history that has since been removed?

 

[aikidaves]

I suspect usage data is a "rolling" history.

Wondering if it has issue with an app that was once tallied in the battery saver history that has since been removed?

Sounds plausible. Certainly explains your experience.

 

[manus31]

I have noticed this issue today on my lumia 630 running dp. Its not something I have noticed before and I have been using it frequently since I installed dp about a month ago. I had just installed battery doctor to see if it found issues, then decided to look at my usage, but it crashes each time. I've since uninstalled battery doctor, but usage crashes each time. What can be done ?

updated: I changed the date to 20/12/2004, don't know why, was just reading the above posts, nevertheless the usage works again with this date. Actually it works with the time set any time previous to the current. It does not work when I change back to setting time automatically.

Does anyone know why this is ? Whats the time got to do with it ?

 

[aikidaves]

I have noticed this issue today on my lumia 630 running dp. Its not something I have noticed before and I have been using it frequently since I installed dp about a month ago. I had just installed battery doctor to see if it found issues, then decided to look at my usage, but it crashes each time. I've since uninstalled battery doctor, but usage crashes each time. What can be done ?

updated: I changed the date to 20/12/2004, don't know why, was just reading the above posts, nevertheless the usage works again with this date. It does not work when I change back to setting time automatically.

Does anyone know why this is ? Whats the time got to do with it ?

My guess, based on the experiences of Teeeerex and woodduckie and your experiment with the date, is that something gets screwed up in the usage history that causes problems for the app. Since the history seems to roll off over time, if this is true, it'll start working again in a few days. Changing the date would have the same effect, since it wouldn't look at the same history. Definitely sounds like a bug for Microsoft to address.

 

[manus31]

My guess, based on the experiences of Teeeerex and woodduckie and your experiment with the date, is that something gets screwed up in the usage history that causes problems for the app. Since the history seems to roll off over time, if this is true, it'll start working again in a few days. Changing the date would have the same effect, since it wouldn't look at the same history. Definitely sounds like a bug for Microsoft to address.

Sounds about rite, Ill give it a few days to see

 

[manus31]

This corrected itself overnight. I suspect a cache cleaning app I was using might of had something to do with this problem, possibly wiping the usage data