On Tue, Aug 10, 2010 at 9:31 PM, TreKing <[email protected]> wrote: > On Tue, Aug 10, 2010 at 4:40 PM, Tommy <[email protected]> wrote: >> >> So if I were to set requestLocationUpdates(String provider, 60000, 0, >> LocationListener listener, Looper looper) it would be the same on the batter >> as if I were to set a timer for every 1 minute or whatever to call up the >> GPS again? > > Yes, or better, I'd think. Having the GPS connected but not doing anything > would probably be better than having it reconnect each time. That initial > start up is probably a good chunk of the batter use.
I'm doing field-test with a device. And, I will not encourage people that want a precise (about 5-8 meters) point to use minTime. Using it so, will turn off the Gps engine (STOPPED), start it again (STARTED), and trying to get a position. That takes about >10 seconds. After that you can take a not so accurate point. And, if it's for a pedestrian, the guy is 10 meters away (less than your desired accuracy). The best solution I found so far is not using minTime, and use the entire GPS engine during the use of the application or service. I had to decide between battery power or precision. I choose precision, as is a pedestrian guide for tourists. I know tourist aren't in a rush, but you can't assume that. I'll made a stress battery test after a full charge leaving the phone with the application running without setting minTime or distance and I'll let you know how much power consumes in a samsun i5700. -- If you want freedom, compile the source. Sebastián Treu http://labombiya.com.ar -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
