So, you're using traceLocation and you walk inside a building,
even with the timeout set to two minutes, you might get the annoying
1016, tracelocation timeout error.
What you might want to do is start a new traceLocation instance,
since the 1016 error kills the process, and no future callbacks will
be fired after the occurance.
If you would call a function from within the error callback,
in the end, you would obviously create stack overflows, and beforethen,
use up a lot of memory that's not really required.
A simple way around this would be to initiate a timeout, and start
traceLocation again after a little while.
BUT, since there's a problem with setTimeout while the phone is idle,
and timeouts get queued, and mostlikely the user has its phone in it's
pocket while tracelocation is running, this could be rather sucky.
I have thought up the idea of creating a stack for the time being,
and when the phone comes out of idle, dropping the stack, and
creating a new instance using a timer.
I think this is really BAD to do this way, but since I dont want to
waste too much braincycles right now, it might be best for the
Anyone with ideas?