Thanks!

I figured out a while ago that spending 2 or 3 releases trying to find such a bug is generally worth the extra micro-amp it takes to leave the strings in. Back in the day of sub Mhz processors and 64K of ram, it was worth it, but today? But, to each their own. Variety of style is why we have such different systems already today, and that's a good thing IMHO.

Figured as much, but figured it wouldn't hurt to mention it.


So, as for the GPS thing: After watching the debug logs for a while, I think I've figured out what's going on. I think the cell-tower thing is actually hurting my chances, so I'm trying it now with that turned off.

What the log showed was, I would often turn on, get Mode 0 stuff (cell tower), then about 25 seconds in, I'd get a "GPS lock" Mode 3, with either a "error" that was too large (>50m), or I'd get something pretty close, between my actual position and where the cell tower said I last was, but it would commonly be JUST outside the window for the spot (52.5m for a 50m spot).

My best guess is that the first "lock" signal is offset by the system trying to pre-feed the location info from the cell tower location (aGPS), and that's what's killing it. So, I'll try it with that off and see if it takes longer to lock and/or if it comes back with a better first coordinate.

Maybe a good idea would be an option to ask for an update or two from the location system after a lock and see if it eventually stops "moving"? That would also cut down on the "just passing by" issues too maybe?

I'll play with the wifi ID thing later this weekend and post results. Thanks again!