-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Question: (functionality) #4
Comments
I have done no testing. I presume this app would be detrimental to the battery. Pulling the GPS every second: I can't imagine that would be good for battery.
It will just keep trying forever. |
Wouldn't you say that both issues should be addressed? As for senseless trying, it should try for some time, and then pause until something changes (phone moves for a certain distance, for example). The movement can be estimated with accelerometer sensors too, if gps is not yet locked. In conclusion, it definitely requires some smart management, to protect battery. |
The main goal of the app is obviously to keep the GPS locked as much as possible. Doing anything that might compromise that goes against the goal. For example, pulling the GPS less frequently if it has a bad signal. In this case it would be up to the user to turn off the app if they want to save battery. |
I'm not apposed to saving battery. I just don't know how to do it without compromising the main goal of the app. |
How does it impact battery? Have you done any testing in this regard?
Also, what happend in situations when the gps can't get a lock (no signal)?
The text was updated successfully, but these errors were encountered: