GPSToday UPDATE 11/04/08

[schettj]

Originally Posted by ScrapMaker

I would definitely not use S2U2 at the same time, since it will force the device to sleep, even if it's attempting to get a lock.

Meh. Ok so it's useless (still) since the programmers (still) have not had it go into the proper power mode when it wakes up to get a fix. That's what I was seeing the last time I reported that bug to them.

[ggoldfingerd]

Have you guys who are running s2u2 tried setting NoPowerSuspend=1?

[schettj]

Yep, just did that today.

It's been successfully running in that mode checking every half hour all day. Battery drain not horrible. Possibly this is the way to go, will run it for a couple more days to see how it holds up.

It shouldn't be necessary to do that, as S2U2 doesn't override the no-suspend power mode, but it'll do.

[ScrapMaker]

Originally Posted by schettj

Yep, just did that today.

It's been successfully running in that mode checking every half hour all day. Battery drain not horrible. Possibly this is the way to go, will run it for a couple more days to see how it holds up.

It shouldn't be necessary to do that, as S2U2 doesn't override the no-suspend power mode, but it'll do.

So with this mode, it will automatically wake up, or it's really not suspsending the PDA portion at all? So programs and everything are just running at full %?

I never fully understood all those settings, but I assumed that would cause a drain on the very little battery I get with my current usage

[schettj]

I'm running it today set as:

NoPowerSuspend 1
BlankDisplay 1

This is what it does...
If it wakes up, you see the S2U2 screen for the timeout seconds (defaults to 17s) after which the screen blanks, but S2U2 doesn't power down the CPU... after your Windows "on battery" or "on AC" timeout time is reached, WinMo will power down the CPU.

If GPSToday woke it up, it should stay powered up until it gets a fix or gives up, then it will power off after the idle...

So, with an idle time of 1 minute in WinMo I am buring at worst 40-60ma/h or about 1ma for the 1 minute with cpu on and screen off. Plus whatever GPS Today burns getting the fix.

Yesterday ran from 7 am until 5:30pm 30 minute fix and battery was at 66% at 5:30 - that was without the backlight timeout. Still, it logged 18 fixes in those 9 hours, so that's not horrible.

I'm running it today with acbpower logging the power drain

[schettj]

Ok, yep, this is pretty solid.

It's also pretty hard on the battery



Off charger @ 6am... 7am-4:30pm GPS Logging every 30 minutes, with 2 20 min sessions on car charger running Tom Tom, light use otherwise - some surf/email/talk down to 68% - normally would be in the mid 70s with that usage.

Not killer battery drain, but not nothing. Still, pretty neat.

You have to have some kind of lock to use this thing, it needs a good 20-40 seconds to get a lock. Seems to like to run for 20+ seconds even after it gets a lock even on the lowest "quick" setting for fix quality.

Overall, pretty cool. I've got a mortscript that snaggs the fix and posts it back to my web site for my own nefarious use. Muwahahaha....

[Negrito]

How do i Switch between the full app, and just the today plugin? Or did i just dl the wrong file??

[No1ustad]

Originally Posted by Negrito

How do i Switch between the full app, and just the today plugin? Or did i just dl the wrong file??

dl'd the wrong file. it's a different cab

[BenC]

The updated plug-in is still not available.