I've been noticing the same. i think the "60" is more like 6 seconds. I think i may increase it a bit. I'm also beginning to think (hope?) the internal meter is rather pessimistic - spbshell claimed %80 when the phone was saying less. Regardless this is a trade off of convenience for battery life.

the "internal meter" is accurate. If you look at the samsung today screen plug in for the battery meter it matches. The value for that is in a samsung area of the registry under a vlaue named "batterypercentage"

spb and everyone else read a generic windows registry value that does NOT match the samsung value.

for some reason samsung is not updating the "normal" windows registy value that everyone else reads but instead updates their proprietary value.

bottom line- NO THIRD PARTY battery meters work correctly at the current time.

For those that remember Zapit! from the old i730 days, I can confirm it works and works well on the Saga. I just mapped it to the short press of the camera button and now my RAM stays nice and clean. It kills programs like a hot knife through butter. I've attached it for everyone's convenience. (note: you'll need the phone plugged into the pc, then run setup)

Attached Files

zaptit12.zip (51.7 KB, 71 views)

__________________
hey MOM..... THE MEATLOAF!

Odd that it still updates the "normal" one, just wrongly/laggardly.

Is the "normal" value updateable via a script/app, to keep it in sync with the "Samsung" value? Or are these system restricted?

Thanks.

i dont know- I wish there was a way to change the "normal" value based on the samsung one. I'm itching for a battery bar along the top but none of them work right.

I SUSPECT the issue is windows measures battery capacity one way and the battery samsung is using doesn't follow the normal curve. So samsung has another way to measure and they use it to update their own counter.

The samsung registry entry is a percentage. clean and simple.

the "normal" one seems ot be a really long number that is not at all pegged from zero to a round number.

So my guess is windows measures voltage drops or something like that and the battery doesn't follow the normal curve so that's why it is off. Samsung maybe can actually meassure capacity or something in a nother way.

this might be of some use... here is a .cab file to auto disconnect your data connections if it is idle for a certain amount of time:

Andrew’s Blog » Auto Disconnecting Idle Data Connections in WM6

__________________
Andrew
www.AndrewSaysHello.com

I want to confirm that I used the four edits below and saw a marked improvemet in my battery life.


[HKEY_LOCAL_MACHINE\Comm\AsyncMac1\Parms]
Default value type and value are
“DisablePowerManagement”=dword:1
Change to
“DisablePowerManagement”=dword:0

[HKEY_LOCAL_MACHINE\Comm\PPTP1\Parms]
Default value type and value are
“DisablePowerManagement”=dword:1
Change to
“DisablePowerManagement”=dword:0

[HKEY_LOCAL_MACHINE\Comm\L2TP1\Parms]
Default value type and value are
“DisablePowerManagement”=dword:1
Change to
“DisablePowerManagement”=dword:0`

HKEY_LOCAL_MACHINE\Comm\ConnMgr\Planner\Settings\
SuspendResume = GPRS_bye_if_device_off
CacheTime = xxx (where xxx are seconds before auto disconnect, for me the best value is 60)

I've got a problem. I went in and changed the registry as instructed. I noticed after this, my emails were not coming in "as they arrive" like they used to. I went back and changed the registry and added the 1501 back in. After thsi I got a bunch of errors and now when I go back to edit the registry, it wont let me.

The "as they arrive" feature requires a constant data connection (hence the battery drain) and if you told the device not to suspend the data session, well thats that end of it.

It wont let you edit the registry? (looks for someone to step in on this one...)

I'm sure someone smarter than me will come up with a solution, but you can always do a hard reset to fix the registry. Certainly a measure of last resort, but I've gotten pretty good at reinstalling all the software on my phone, and find it performs better after a hard reset. But like I said, hopefully someone else will offer a better solution before you have to resort to that...

hard reset will definitely fix it, or...
maybe someone can post a screen shot from their registry with the same settings...

__________________
Later, Lou
Palm IIIxe>Palm M505>Palm Tungsten>Dell Axim x30i>Siemens SX66>Samsung i730>Moto Q>MotoQ9m>BB 8830>Samsung Omnia>Samsung Saga>Moto A4500/Q9n>BB Storm 9530>BB Storm2 9550

I found with this regedit that battery life did improve, but my Saga started to freak out on incoming calls (I couldn't answer them). I did a partial Sprite restore (registry included) and I'm back up and running with no issues.

You did back up before you edited the registry, right? If not, time to hard reset and rebuild what you are used to.

__________________
Yes, that is my boat.

Strange how each of the phones seems to have it's own personality... Haven't had any of the issues mentioned so far. (knocking on wood with fingers crossed while tossing salt)

I tried the GPRS_bye... edit and saw no change from having it blanked out.

Found the reg edit that reduces the notification interval in SPB Phone Suite:

HKEY_LOCAL_MACHINE\Software\Spb Software House\Spb Phone Suite\Notifications\Delay

change Value: to (number of seconds you want in dec.)

20 seconds is the minimum interval it will do. You can enter 1-19 seconds, but it won't blink/sound/vibrate any sooner than in 20-second intervals.

This may be old news to many of you, and this may also apply to all Windows Mobile users, but I just stumbled across it. When in the list of messages in any of your mailboxes in the stock messaging app, there are several shortcuts that can be achieved by pressing and holding particular keys. The most important is "H", as holding that key brings up the list of shortcuts. Here is the full list:

H- List Shortcuts
A - Reply All
R- Reply
K - Mark Read/Unread
F - Flag
M - Move
O - Forward
D - Delete
L - Download Message
S - Send/Receive

Again, this may surprise nobody but me, but I've been using several of these for the past couple of days, and it really speeds things up.

I had a few issues so I started comparing registry versions to locate specific keys.

[HKEY_CURRENT_USER\ControlPanel\BackLight]

"KeyBacklightTimeout"=dword:00000005


I changed this one to 30 seconds so that the keyboard wouldn't turn off so quickly while I was typing at night.

That can be changed in the Backlight settings......

Settings > Backlight > Keyboard tab > Turn off keyboard backlight > Not used for # of seconds

But, ya...it'll only allow a max of 10 seconds, so that's a good find.

Get rid of the today screen lines

[HKEY_LOCAL_MACHINE\Software\Microsoft\Today]
"HidePluginSeparators"=dword:1

HidePluginSeparators is not visible for me in that folder.

sometimes if the setting is not the default (such as the example above) you have to add that line to the registry.