Hi tramps, I'm comparing month old code and except yesterday change with some notifications, there is absolutely no change that should affect GPS handling. Another mystery?
Hi menion,
I have these GPS problems since the first test versions 2.13.1.1.
viewtopic.php?f=25&t=3189&start=40#p21855viewtopic.php?f=25&t=3189&start=100#p22283Over 4 days I tested all what I could think of.
The market versions 2.13.1 (free and pro, shortly LP) are definitively not affected.
I de-installed the test versions and tried a new configuration.
1.Sunday afternoon (starting with a bad Locus Test (shortly LT) I tried:
reboot, delete all files in datagps to force a GPS coldstart and hundred others: no success.
Then I wiped cache and dalvick cache and renew all permissions: LT had after 10 secs a good fix during the rest of the day :-)
I switched the phone to flight mode and put it aside.
2. The next morning I started a tour with LT: after 20 mins only 1-2 sats and no fix. Rebooting does not help, so I started LP and after 10 secs 6-7 sats and a fix.
At the summit I had 11/11 sats, I stopped LP and with LT I had 11/11 too.
In the evening flight mode again.
3. The next day exact the same behavior.
4. Yesterday evening I did not switch to flight mode and now this morning LT get a fix after ~20 secs.
Did you perhaps use other Android functions or procedures to get GPS data or do you delete a cache or other data in the test versions?
I will surely be desperated when the new market version will be released :-(
Another one:
This morning I made a short trip to buy something and returned within 30 mins.
The first track (...:46a) was made with Locus Test (I heard the lost fix several times), the second track (..:50b) back to home was made with Locus Pro (2.13.1).
You can see the difference: the test version has problems with holding the fix.
I have this behavior since the first test versions too.