[Query Timeouts] more frequent usng locate cmd

problem Ive been having for a while , I am getting the infamous [QUERY TIMEOUT] message more often
whilst out and about.

Recently I installed ‘androidlost’ which has several features I find useful in trying to combat this.

one: ability to turn on/off WIFI
two: ability to turn on/off DATA

because Avast defaults to turn on WIFI before getting location data , I get a signal Accuracy of several thousand Meters as nearest free WIFI Provider is within range.

Perhaps in future version there could be a toggle cmd which would allow the controller to select which service to use first.

for example;

locate wifi
locate gps

Thanks.

why I dislike using the actual androidlost gps cmd is because it brings up the notable flashing ‘GPS tracking Icon’ that appears at the top of phone when using services like ‘Google Location services’ and such.

something Avast managed to annul somehow.

ok maybe I was wrong , I cannot seem to get it to locate using GPS (without WIFI) intervention.

problem is that there is a WIFI signal 2000 meters away which is being activated at time of cmd being initialized which I suspect is causing the problems.

hopefully there will be some kind of fix in next version.

also worth noting. If I send through 2 locate cmd’s to quickly , The app will [CANCEL] the first one. Perhaps just continue with the location and [CANCEL] the 2nd/3rd attempts instead?