Re: S2U2 1.40 power save mode
 

This is interesting! I was finding the opposite :)

I was originally using sensorlock, and wasn't liking it because activesync would turn on my screen every 5 minutes when it was updating, and my screen would also turn on every time I got a notification for a meeting, or new email. What would happen then is that my screen would stay on indefinitely, even through I checked my power settings, etc.

So I gave up with sensorlock and touchlockpro, and went to s2u2 v 1.37. I found that s2u2 was REALLY good about automatically shutting off the screen, as it took precedence over the notifications. I set my value low, to 12 seconds or something, and I was noticing WAAAAAY better battery life. Where before I would take my phone out of the pouch and it was hot with the screen lit up, now it was how I would expect it...cool to the touch, screen off, and lots of precious mA left :)

So, if 1.40 saves MORE battery, then i think you all are my new best friends.

BTW, S2u2 works REALLY well with the Omnia d3d drivers people have been talking about in the latest CDMA thread.

I'm currently running dream's 0.5 rom, and since he changed to these drivers, I've been running in direct draw instead of raw buffer, and it's smooth as silk.

I'd urge you to give s2u2 a try again, as it sounds like things are better than they used to be in the olden days with the Mogul.

Re: S2U2 1.40 power save mode
 

I have been using 1.35 for a month now and I have no noticable battery drain with it running. I can go several hours on idle and only lose 10%.

Don't forget that anything that regularly connects to the internet is going to really shorten the battery life. So, for example, turn off all weather stuff etc.

Also, I have disabled my keyboard slide from turning on the device which has really helped.

Richard

Re: S2U2 1.40 power save mode
 

wups, I thought this was a program like ThrottleLock that actually locked your device until you entered a code. rats, oh well.

Re: S2U2 1.40 power save mode
 

Why would setting the display to "rawbuffer" affect battery usage?

Re: S2U2 1.40 power save mode
 

I have had this problem also especially when using VC with it. I started a thread awhile back on it but never got any replies so I tried all other locking apps. gave up on all of them and am back to S2U2 and living with this bug. If anyone has a fix for this it would be great.

Re: S2U2 1.40 power save mode
 

Exactly! I can receive phone calls all day long, and I can make calls using VC as long as s2u2 hasn't activated but as soon as it activates, it's intermittent. I might be able to make 3 calls fine then the fourth, my BT just beeps and won't connect. Then it might not work at all till I do a soft reset. Strange. I have tried EVERY setting available to avail. I know it's not my BT headset cause I have 3 of them and they all do the same thing. Is anyone else besides us having this problem?

Re: S2U2 1.40 power save mode
 

I don't think I've had this issue at all, but I'll test some more to make sure.

Re: S2U2 1.40 power save mode
 

It doesn't, that setting just makes it work better with the stock 3d drivers (or so I understand from other threads).

Re: S2U2 1.40 power save mode
 

I use the factory key lock (long end key setting) with sleep mode and disabled the keyboard slide to wake the phone up (reg edit) and haven't had any problems. I turn off any running programs, use the long end key to lock the phone the tap the power button and put it to sleep. This has worked for me and I've noticed better battery life.

Re: S2U2 1.40 power save mode
 

You don't have to use rawbuffer mode anymore. Several releases ago he fixed the directdraw issues. I've been using directdraw myself since 1.37 (IIRC).