Sudden Battery Drain Overnight

[Guest derky]

While my Touch Dual was off for repair the lovely people at T-Mo put WM6.1 on it, and since it's been back I've had issues with the battery level dropping 50% overnight, and in once case 90%!

Firstly, it's a brand new battery. I read on another forum that there could be a WM6.1 bug where when hard reset with a partially charged battery WM6.1 screws up and doesn't charge the battery fully as it mis-registers the charge level. So I drained it to critical, hard reset and then charged to full with the device off.

Once it was charged I didn't install anything on it and then managed to get 4 days out of the battery with the phone on during the day, and Exchange ActiveSync running. All was fine. I then recharged it, and set about reinstalling stuff, and now it's started doing it again. I turn of the radio when I go to bed, and leave any apps running, just live I've done with WM5 and WM6, and then in the morning, along with my alarm I get a critical battery notification.

I've tried monitoring the processes running and what CPU they're using and the pull on the battery, but nothing comes up abnormal, apart from once when I found repllog.exe was going on a rampage and stopping the device from sleeping. But the thing that really confuses me is that I can use the phone all day and the battery drain is as I would expect for the usage, but it only plummets overnight when the phone is off.

Anoyone got any ideas, as I'm considering sending it back to T-Mo and getting them to put WM6.0 back on it. I just want the thing to last 2 days like it used to, which isn't exactly spectacular, my partner only charges his Nokia once a fortnight.

[Guest ricardo the fish]

I've been experiencing this as well.

It is really annoying as my phone can last several days, then after I charge it, it will shut down overnight due to low power!

I would be interested to know if this really is a WM6.1 issue, if it is, I may see if T-mob can re-install WM6.0 on it.

Derky, have you come across an issue with the phone recognising phone numbers as well?

Since I sent my Touch Plus off to T and they stuck WM6.1 on it, the phone struggles to recognise contacts if they are in the international format (i.e. +447712345678), but then does not regonise text messages if the number stored is NOT in the international format!

Guys at my local T store had no idea even what WM6.1 was so were not much use.

[Guest derky]

I've been experiencing this as well.

It is really annoying as my phone can last several days, then after I charge it, it will shut down overnight due to low power!

I would be interested to know if this really is a WM6.1 issue, if it is, I may see if T-mob can re-install WM6.0 on it.

Derky, have you come across an issue with the phone recognising phone numbers as well?

Since I sent my Touch Plus off to T and they stuck WM6.1 on it, the phone struggles to recognise contacts if they are in the international format (i.e. +447712345678), but then does not regonise text messages if the number stored is NOT in the international format!

Guys at my local T store had no idea even what WM6.1 was so were not much use.

No joy at all, it went back to T-Mobile again and I think all they did was replace the battery and re-flash it, again. Had it back 2 days and it drained again, so I've hard reset and not applied the T-Mob customisations and am slowly re-adding everything in a hope of tracking down the offending app/combination of apps. I'm actually not entirely convinced it isn't the HTC audio player that isn't causing the hassle though.

I did ask them about going back to WM6 and they said it wasn't possible, which it is, just not in a supported fashion. My annoyance at this is actually make me do the unforgiveable and anticipate what the next version of the iPhone will be and I am as anti-apple as they come :excl:

I did have a phone number issue yes. For some reason the default setting for the number of digits the phone uses to compare the incoming number against your contacts is 13, which means that the phone is tryting to match against the whole number. For phone calls numbers come in regionally e.g. 01234... whereas texts come through in the international format +44 1234... You need to change this number to something more sensible, I think most phones use 6 - 8, so it only compares the end of the number.

I used Schaps Advanced Config tool to modfiy my mine so I've never changed the registry directly for this one, but a quick search shows that that HKCU\Control Panel\Phone\CalIidMatch should be offending registry key.