|
Originally Posted by Villain
|
Hey all,
I did my upgrade to an X50 mid yesterday, WM 5.0 was running on it fine, and things looked good. I went to power on this morning and was told to press the contacts button because a critical memory error had occurred.
After the reboot, I was told that my main battery was low (it was at 7%). I had not used my Ax since last night when I turned it off (yes, I verified that it was off) at approximately 5:00 PM. It's now 8:30 AM when I turned it on, and the battery was almost completely dead.
Is this an issue with WM 5.0?
|
I downloaded Pocket Informant 2005 R3 Oct. 20, close to the time it was announced. I have a bad habit of NOT WAITING, and being among the first to use the new upgrades.
After the installation, one of the things I noticed, besides all of the bugs, was the noticable power drain, visibly counting down on the percent meter, and on the top bar battery meter (slowly, but I had never seen it drain so fast with minimum use).
It was fully charged when taken off the cradle. 14 hours later, I got the Memory Error message. But when I pushed the CONTACT button, nothing happened. It was too dead. I used a spare battery. (I tried the big battery again, and got the error message, and then, "This will shut down in 10 seconds, 9, 8...)
Dell support said that that error is caused by memory being corrupted.
I sent an email to PocketInformant.com for help. They asked my exact version and build. When I replied R3 buile 4??, they didn't address my 5+ problems/bugs, but instead asked me to look at their website with the fixes for Pocket Informant TFT R4 version.
They asked:
Can you see if these issues are present in the latest build:
http://www.pocketinformant.com/Forum...showtopic=7988
Look at the long list of bugs. And the reason they had to come out with another revision so quickly could be why there are more bugs than normal in the new releases -- their explanation:
Since we're obligated to do a refresh of our builds when we get the RTM build of Visual Studio 2005 from Microsoft*, we were going to do a "Rev 3 Refresh" in November which would contain also any bug fixes and feature requests we could manage in that same timeframe.
But thinking about it more, I've decided that calling it Rev 3 Refresh just is confusing and stupid. So I've decided that any release - no matter how small - will be a new Rev release. So what was going to be Rev 3 Refresh is now Rev 4 and what we planned for Rev 4 is now Rev 5.
Just FYI for all those people following my rambles.
[i]*What does this have to do with us? We use a development tool from Microsoft called embedded Visual C++ for all of our development up to this point. But to do anything with Windows Mobile 5 (specifically) you have to use a new version of their tool which is now part of "Visual Studio 2005" (VS2005). However in Microsoft's timing WM5 came out before VS2005 was finished. So Microsoft created a "GoLive" license which allows developers to ship WM5 built software using only Beta 2 of VS 2005. Beta 2 has some known bugs in the compiler and in the development studio. In my tests the RC version of VS2005 fixes all of those, but we can't ship any software built with it. RTM or the final release is supposed to be out November 7th. So once we get that, we have to rebuild our system a bit, recompile, test, and get it out. I expect that to take 7-14 days after we get RTM. So that'll be Rev 4.
http://www.pocketinformant.com/Forum...showtopic=7953
The battery drain only happened once while PI 2005 R3 was installed. I watched it like a hawk. I was relieved when the battery charged to full in ~80 minutes. I don't know what "embedded Visual C++" had to do with it, only that I noticed a faster-than-normal decline in the battery charge while using PI and doing other simple tasks, right after the installation of PI. (It.could've dropped from over 90% to below 60% in 20 minutes???).
I'm guessing the processor on the video chip, influenced somehow by the embedded Visual C++, was knocked off it's axis...
Pocket Informant 2005 TFT R4 fixed the other bugs.