This object is in archive! 

[version 3.30.0] GPS position has become highly unreliable and unstable

Max Moore shared this problem 6 years ago
Solved

I never had any problem with previous versions. Suddenly, since updating to version 3.30, the inferred GPS position deviates for as much as 60m from my actual position. I suspect it has something to do with the recent changes in handling GPS data. It is as if Locus Map applies an unnecessary random offset (for instance, N -50m, E 21m)


Sporadically (maybe totally coincidence, I don't know), it seems that if I turn on another navigation app (like the geocaching app) long enough and go back to Locus Map, the problem temporarily subsides. But after a while, Locus Map starts to infer an erroneous position back again.


Another way that seems to works but not always is if I apply a manual offset and then remove it.


- Samsung J3 Prime

- A-GPS (GPS, Glonass, wifi)

Replies (28)

photo
1

Good day Max,

sorry to hear about problems with improved GPS system we introduced in the latest version. There definitely is nothing like random offset!

Are you testing it somewhere outside of the building? New system use recommended solution over so-called fused location provider. In buildings, it may return results influenced by a wi-fi signal as well, so I can imagine there will may be some offset.

You are also really only one, who report any problem with this new system till now, so I'm quite sure, it will be some temporary problem on your device.

I'm sorry I can help more. "Unfortunately", to make it simple for developers, fused location provider is quite a black box and there is close to no option, how to influence result.

Hope you find a reason why this happen. Let me know if there will be something I may help with.

Menion

photo
1

Locus is working perfectly with all my phones since 2011.

Unfortunatly with the latest version of locus GPS is not working at all.

On the GPS screen 0 satelites are detected.

If I launch another app like Strava my position is detected within seconds, but if i switch to Locus still 0 satellites...

My phone is a Crosscall Odyssey+ with Android 4.3

photo
1

With 3.30.1 version and "compatibiliy mode" Locus is now able to "see" satelites and give my location.

Thanks !


With the new version i've lost my right panel.

First try at home, Locus seems to detect my position indoor, when before it was lost, but with a bad accuracy like 100/200metres. Could be bad for users recording theirs tracks and wanting them acurate. (I know how to deal with it in parameters but not every users)

photo
1

Good day Menion,


No, I don't use navigation software inside buildings. Why would I? I don't hike inside buildings. Most of the time, and it was the case when I last used Locus Map, I turn off everything (wifi, cell, data) since I am kilometers from any signal.


I might be mistaken but I believe my phone has already its own proprietary algorithm to determine its location, making the "fused location provider (FLP)" superfluous and it might be the reason for the weirdness I observe. I wish a could revert back to the previous version or turn off FLP. But, I can understand the new version is an improvement for most users. it's not entirely a bad thing. I was starting to rely on Locus Map too much any way and neglecting other means of navigation.

photo
2

Also note the deterioration of the stability of the GPS fix in the new version. The fix is lost more often and longer restored under the same conditions. It started in the latest beta version.


Recently I could compare Beta 3.29.2.8 (with new system) and Pro 3.29.2 (with old system). And I like the old system better. Maybe it's because I have a device with a very strong GPS, a pure beast.


Maybe it's worth adding the user's choice to the profile record track or in the "GPS and location":


  • classical system (old)
  • advanced system (new)

?

My device: Samsung Galaxy J5 (2016) SM-J510FN/DS

photo
1

Hello Max, Igor,

hmm I'm surprised by your negative result.

@Igor, you wrote about lost of GPS-fix. How you detect this? Some sound notification? Change of position circle on the map (from blue to green and back)?

@Max: I did not expect from skilled user to test GPS in the building, but we don't know each yet and from time to time users complain that Locus does not work well in their flat etc,, so I rather ask. Anyway if your device has modified location provider, then it may cause some problems. Fused location provider system most probably use basic location provider in your system and just modify it's output, hmm.

To be true, I hoped it won't be necessary to create an option that Igor mentioned ... some extra settings that allow to switch to the older system.

If you won't kill me ... today we will publish one new bug-fix version. Try it for a while and let me know after week or two. If new system will really cause some troubles, I may add such settings to the system, but I really hope it won't be necessary.

Thank you for understanding.

photo
1

Yes. I have sound alerts on the status of the GPS fix. (in attached ZIP) Because the program works for me every day from almost morning and almost to night, I'm always aware of the state of GPS and its correlation with external circumstances. Accumulated a little experience and a clear knowledge of how GPS behaves in specific conditions.


The simplest experience: settle inside the room near the window. Turn on the GPS in the Locus with the new system. On the windowsill, for example, a clear fix without losses within a couple of minutes. Move it away from the window for half a meter. If all is well, after a minute, move it away from the window yet. Again good? In a minute, move more, etc. Fix was lost! a minute, a little closer to the window .... So you can find the boundary position of the unstable fixation. With the current satellite situation, of course. Now turn on the Locus with the old system. Where the new system showed an unstable fix, the old one will not lose it! So it looks on my device and about such an experience I did with the beta version 3.29.2.8 and Pro 3.29.2.


Of course, I did not immediately begin to do so. At first, I suspected something was wrong when I began to hear the signals of loss-recovery in conditions when nothing like this had happened before. He returned to Pro - and everything became familiar.


I will gladly test a new beta version :)

photo
1

Another experiment is the speed of fixing the GPS fix after a loss


Enter the premises with guaranteed missing GPS signals: the first floor of a multi-storey building without windows, a cellar, a bunker, a cave, a rocket mine. :) Wait for the loss of fixation. A minute later go out into the open space and slowly leave. The old version - fixed fix in 1-2 seconds, and even immediately, and I managed to pass no more than 3 meters. New - 5-10 seconds, and more than 10 meters.


Here is another thought.

I know users who will not watch the accuracy of the recorded track on the map, but will judge the GPS accuracy figure on the program screen and compare it with other programs. And here Locus will undeservedly lose - because where other programs show accuracy of 3m, Locus will show 10m! So the Locus is worse. Although, in reality, the coordinates will be the same, but these users will not be convinced that Locus works no worse - they have figures before their eyes. From purely martquetting considerations, I think it is worthwhile to return the familiar figures.

d21adc9eaf23547d8b6c1408819b1510

photo
1

With me that is also with the 10 meters accuracy of GPS. 21 of 22 satellites. Since then I had outdoor field, 3 meters accuracy. In the woods every now and then 4 or 6 meters. But now only 10 meters.

photo
1

http://help.locusmap.eu/topic/notification-of-position-gain-gps-fault

GPS (3.30)

There are many different mistakes! For example, the phone is GPS OFF, and yet the notification announces the fix and even the icon is GREEN! When you try to turn on navigation, of course it will be waiting for GPS. Of course, because there is no fix.


Please repair with the highest priority! GPS and its proper functioning is the cornerstone of the application.

photo
1

Another screen

photo
1

Pro and Free (beta) running simultaneously. Still. No movement. Screen capture after 1 minute.6cd25eac1116078ca5a103264411de38

photo
1

New version 3.30.1 no change. All GPS errors remain!

Edit: Mod compatibility seems to work correctly. It would be advisable to explain what it is about GPS chess. Well thank you

photo
1

Condor

Try to enable Сompatibility mode in "GPS and location"

Very similar to the "old mode" of handling the GPS

missed :)

photo
1

Thank you ;-) I did this and wrote an edit.

photo
1

İnteresting.

New GPS handling: accuracy 10m+, less sattelites are detected, visibly less precise track recording, a little bit faster fix, especially indoors, but gps signal is lost more often.


Compatibility mode: accuracy 4m (the same as GPS Status app), more sattelites detected, more precise track tecording, more stable signal. BUT Locus keeps gps on in the background at all times when the app is minimized, with no track rec on. Which is not convinient.


I have to admit the GPS handling was rock solid before 3.30 on my phone. Very reliable. Not exactly so now.

photo
1

Any manipulation of the GPS position that leads to less accuracy is a bad solution. In geocaching, we rely on an accuracy of 2-5m. Pseudo location determination by GSM and Wi-Fi is for whom and why?

photo
1

Hi guys,

problem with accuracy: firstly please forget on "Accuracy" parameter visible in GPS screen. This value is simply some abstract number. Comparing of accuracy with old method and new method is also non-sense, because both use different system. Best how to compare accuracy is to make a track records and compare them.

problem with "fix": new method has nothing like "gps fix". In only returns a location from various sources merged into single location. So it is close to impossible to correctly detect if we have fix and if fix was lost. Because of this are here these problems with notification.

problem with GPS in background with compat mode: I'll check it, thanks

photo
1

Hi Menion,


1. İt seemed to me the track recording accuracy suffered in same conditions. But I will test more.


2. Even in normal GPS mode (not compat) Locus sometimes keeps GPS on in background after minimizing. Happened a few times this morning.

photo
1

problem with accuracy: firstly please forget on "Accuracy" parameter visible in GPS screen. This value is simply some abstract number.


If it's just an abstract number, then you can leave it out.

I thought since then you can count on the number. If I get displayed 4 meters, my signal is very good. and if I get displayed 12 meters, my signal is worse. and I have to increase the search radius when searching.

photo
1

If I leave it, most of users will kill me :).

Consider this as number, that will some probability ( old GPS system defined this usually as around 60% ) say, that your real location is within defined radius. So accuracy 10 in old system say, that you are really on 60 % in 10 m radius. But, I do know this probability in new system! So it is possible that new GPS system (over fused location), say this on 90%/95% for example, and then both values may be almost same if you understand me.

photo
3

[...] please forget on "Accuracy" parameter visible in GPS screen. This value is simply some abstract number[...]


All numbers are abstract. The same goes for everything displayed on a map. Maps are by definition abstract. They are representations of the terrain. It matters whether symbols, numbers, measurements displayed in the app can be reliably related to something useful and concrete on the actual terrain. If the app displays that we are located in a 3-metre radius around a specific point, we expect to actually be in that probabilistic zone. If it tells us that we are inside a confidence surface eleven times larger (pi*r^2; where r = 10 metres), it matters a lot. It matters that the new version displays 10 metres (95%) where it used to display 3 metres (60%). When I walk near a frozen lake, I need to stay on sure ground. My survival depends on it!


Reliability and accuracy are the main reasons why we use precision instruments, like a GPS. We need the device to tell our whereabouts, to accurately triangulate our location, to have a reliable measurement we can trust, understand and use in conjunction with other tools.


Telling us that we should not rely on the accuracy value, to “forget about it because it’s an abstract number” is a lame excuse. Let me be very clear. I don’t blame you. You are not to blame for the inner workings of the new library of functions. However, you are responsible how you deal with it. You cannot just say it’s abstract therefore nonsensical to expect the app to display reliable, meaningful data, as it previously did.


"So accuracy 10 in old system say, that you are really on 60 % in 10 m radius."


My experience is that the previous geolocation accuracy circle was a lot more 60% reliable. The accuracy number reflected the actual accuracy of my android device. I could consistently rely on it to tell me ±6m 99% of the time where I am when I checked against a known location. I doubt very much the change from 60% to 95% accounts for those huge deviations. That's not what bothers me. What bothers me it that now this number is not proportional to the actual accuracy of my device.


Now, the location jumps all over the map, telling my that I am up to 50m from where I know as a matter of fact I am WHILE displaying an accuracy of 10 m. If it were actually displaying a 95% geolocation circle, IT SHOULD DISPLAY AN ACCURACY OF ABOUT 50 m. The app basically becomes lost. Telling us to ignore the accuracy number don't solve this fundamental regression. The only solution I can think of (but you are the expert, not me) is to add a setting to bypass/disable the guesses made by algorithm.


My guess is the algorithm takes in account far too much other sensors (accelerometers, magnetometers, gravimeters...) which, depending on the device and the environment (for instance, cold weather), are not as reliable as the algorithm expects them to be. So, if I jump up and down on a fixed spot, the algorithm mistakenly believes I am traveling and it adds steps in the direction the e-compass points to.


I was very happy how fast and how accurate Locus Map was. What the app displayed matched what I saw on the terrain. Now, the app tells me I am not where I know I am and that I shouldn’t trust it. It even contradicts itself! When I run in parallel both the pro and the free versions (see my previous post), it tells me I am in two different geolocation accuracy circle. If taking into account other sensors confuses the app, I am not interested in the “(con)fused location provider”.


Last comment. With long-term (greater than 2 minutes) GPS averaging software, I managed to get ±0.6 m accuracy while standing still. In the same condition, the new "(con)fused location provider" displays sporadic movement! It infers movement where there is none. Possibly because temperature variations and battery levels greatly affect some sensors.

photo
1

@Max Moor

I'm signing this post!

@Menom

And I will repeat my question:

Pseudo location determination by GSM and Wi-Fi is for whom and why?

photo
1

Good evening Max,

understand your concerns. To be true, from your description it sounds like the new system is bad, dot, and the old system was perfect, dot.

Such definition is definitely not, what new "fused" location should bring.

Short explanation: firstly, fused location receives exactly!! same GPS data as the old system. The difference is that new system adds also available Wi-fi data in the case, GPS is not available, add additional data from gyroscope and magnetometer sensor and all these data fuse into an optimized location. I personally tested it on my running track many times during last 3 weeks and all results were a lot more fluent and better fit to the real track and I never had any problem with lost of fix. And THIS is the result, I expect from all devices.

Unfortunately, from the description in this topic, it sounds that some devices has some problems, I do not yet discovered.

And the never-ending story with accuracy? I've now tried for almost an hour find some more serious study about GPS accuracy and this fused location provider on Android, but no success. I may here talk only as a developer ... because old system and new system use exactly same hardware GPS, exactly same data, I expect accuracy will be in the worst case ... same. But because fused location provider uses also devices sensors to predict movement faster than once per second over GPS data, I simply logically expect that fused location provider has to return data that better reflect real changes in device movement, that's all. Reality? Practice will say. There is still the possibility, that on some devices, like your or @Condor, there is some problem in Google Play services and the result is not correct. Anyway, the same issue should then appear also in other apps like Google Maps.

photo
1

Už dnes to začalo... začínajú mi telefonovať a písať známi že im po aktualizácii blbne GPS v Locuse že to tu mám riešiť a oznámiť chybu.

Našťastie je možnosť zvoliť starý systém v nastaveniach.

Defaultne je nastavený nový systém na ktorý nebol žiadny bežný užívateľ upozornený.

Korektné by bolo po aktualizácii nechať užívateľa vybrať si ktorý systém chce používať a tým pádom by vedel že existujú teraz dva spôsoby získania polohy.

Takto to teraz musím osobné každému napísať kde si to má prepnuť.

Zelená ikona a oznámenie že majú FIX GPS a následne použitie napríklad navádzanie alebo navigácie im mobil oznámi že sa čaká na GPS! Popri tom ešte na nich vyskočí okno s požiadavkou že nemajú GPS. Úplne zmätočné správanie sa aplikácie. Po strate GPS žiadne upozornenie! Celé zlé.

Zahrávať sa GPS polohou bez vedomia užívateľov je hazardovanie s reputáciou Locusu.

Čaká ma množstvo e-mailov a telefonátov dať tento stav do zrozumiteľného stavu.

Môj 13 ročný syn presne popísal ako by mal nový systém fungovať a ako by očakával zmysluplné využitie možnosti alternatívneho určenia polohy. Neskôr si nájdem čas a napíšem.

Nič v zlom a Locus milujeme všetci a všetkým nám ide spoločné o to aby fungoval čo najlepšie 😊

photo
1

"To be true, from your description it sounds like the new system is bad, dot, and the old system was perfect, dot."

I reported an issue I have with the new version, to help YOU perfect YOUR product because I would like to continue to use YOUR product. The end result is that you are annoyed by me, the messenger. You prefer to depict my report as a caricature, as if the real problem is that I am unreasonable for reporting an issue.


No, I never said the old system was the epitome of perfection. Neither I've said the new system is an unsalvageable piece of junk. But, since it's what you're tempted to believe of me helping you, I see no point to this thread.


Evidently, the only hope for users like me is that a future update, entirely out of your will and control, somehow solves the problem we are experiencing. Meanwhile, all we'll get is you blaming us for your choice of imported libraries.

photo
1

Good day Max,

this is probably some misunderstanding in the understanding of my not-the-best English.

If I blame anyone, then only myself because I expected that system from Google ( FLP ), is well tested and will work without any issues. What I wanted to say, is how the new system works, that accuracy value may be exactly same even that value is different and also what benefits new system may bring. Anyway based on your and @Condor feedback, I added at least "Compatibility mode" into settings to be able to switch back to the old system.

I can't expect that problems will solve by itself. If there will be more users during next 14 days, complaining on this system, I'll publish one more bug-fix version with re-enabled old system as default and option to enable new.

Sorry if my post sounds somehow negative against you, this is definitely not correct. I'm just maybe tired from last few non-stop days of testing and support and testing and support ... thanks for understanding.

photo
1

Hi Menion,


I've been recording many different tracks recently with a new gps system: runs, walks, car trips. And İ can report that accuracy is the same or better than the previous system.


So, the only problem that is left on my phone is that Locus sometimes keeps gps in background when minimized and sometimes unexpectedly fixes the location in background, when minimized.


All the best.

photo
1

Po zistení ako funguje ten nový zázračný systém určenia polohy som sa s tým trocha hral. Ako zábavná funkcia je to fakt super 😄

Prvý pokus:

V domácomj Wi-Fi routry som nastavil iné súradnice jeho polohy. Výsledok? 😄

Moju polohu presunulo inde!

Druhý pokus:

Ovplyvnil som magnetický kompas v mobile a? 😄 Skúste hádať.

Tretí pokus: doma s kresle bez zmeny polohy som imitoval pohybom mobilu chôdzu určitým smerom a div sa svetu moja poloha v Locuse sa posunula o 10-15m v tomto smere!

Skúste si to a urobte si vlastný názor na spoľahlivosť týchto údajov.

Edit plus info:

Podľa informácií čo som našiel na internete ohľadne polohovania Wi-Fi routerov by sa do 10 dní mali súradnice spresniť podľa poskytovateľa pripojenia a zariadení ktoré sa budú na neho pripájať. Takže správny "fix" tak do 10 dní 😄

Pre mňa ostáva nastavenie compatibility a spoľahnutie sa na staré dobre GPS.

Všetky tieto snahy aj tak pôjdu do.... je spustené pásmo GPS L5 takže všetci pomaličky prejdeme na zariadenia ktoré ho budú podporovať. V priebehu roka by už mali vyjsť mobilné zariadenia s podporou L5 pásma. A to sa bavíme o presnosti v centimetroch!

photo
1

Ukážka ako funguje získanie polohy cez Location Provider API.

Predpokladám že parameter je nastavený v Locus na priority high accuracy ale to je jedno.

Na kruhoch je znázornené v reálnom čase aké údaje o polohe sa dajú získať s rôznych zdrojov. Výsledok v Locuse potom zodpovedá zvolenej metóde. Takže kde som sa reálne nachádzal?

Za budovou kde ukazuje GPS?

Alebo pred budovou kam ukazuje FLP?


FLP sa spolieha na vypočítanú pozíciu kde sa nachádza môj Wi-Fi router a na pozíciu BTS antény mobilného operátora na vedľajšom dome.

Získaná poloha je dosť presná ale nie tá kde sa nachádzam reálne ja ale práve pozície týchto dvoch zariadení čo v podstate aj je správne no ja som niekde úplne inde.

Chcem získať moju polohu a nie polohu antény a zariadení v okolí.

To je všetko z mojej strany k FLP.

photo
1

[CZ] Condore chápu tvé rozhořčení ale uznej sám, že testuješ podmínky v tvém domácím prostředí. Při chození venku nebudeš připojen k wi-fi a nebudeš simulovat pohyb který se nebude dít. Dle tvého testu (dva pokusy) v předchozím postu, systém funguje přesně tak jak čekám že bude, tedy korektně reaguje na změny v systému, které ve tvém případě byly jen simulací k "oblbnutí nepřítele".

Divné pro mě je aktuálně pouze fakt, že občas vidíš zelenou ikonu ve stavové liště a přitom Locus čeká na GPS signál pro spuštění navigace. Pro to nemám vysvětlení a bohužel se to nikomu z nás v kanclu nedaří na žádném zařízení nasimulovat. Budu zkoušet dál.

Nicméně díky za zpětnou vazbu.

photo
1

Pri dnešnom harašeni s mobilom a dlhšom testovaní som si všimol že sem tam sa tá ikona zmení na oranžovú. Po chvíli znova na zelenú a oznámi fix.

Po dnešnom testovaní sa mi zdá že to môže súvisieť s presnosťou FLP a ak dosiahne požadovanú vyžiadanú úroveň presnosti tak to považuje za fix.

Ikonu mám v podstate skoro vždy zelenú. Hneď po štarte Locus pipne oznam fix a zelená.

Tak som si vlastne všimol chybu (môj prvý topic) a následne až neskôr zistil že došlo k zmene zisťovania polohy.

Pri dostatočnej určitej presnosti (neviem aký parameter žiada Locus) sa aj spustí navigácia bez žiadosti o GPS.

photo
1

No ten FLP neříká nic o tom, jestli je poloha z wi-fi, gps nebo tak něco, tudíž nakonec jsem se rozhodl to rozdělit podle toho, jestli poloha má nadmořskou výšku nebo ne. Zdá se ale, že tobě systém vrátí polohu i s výškou, i když ještě výšku z GPS mít nemohl, tedy nejspíše nějakou "nakešovanou". Divné je ta ikona ... ikona se totiž obarvuje díky stejné podmínce, díky jaké se spustí navigace. Budu to muset trošku více otestovat. Nicméně prosím, dej tomu šanci v terénu, protože tohle testování doma v tomhle případě není úplně ideální.

A pokud ti uživatelé volají, tak je prosím směřuj na nás, určitě bych nerad aby jsi za mě musel dělat na Slovensku support :). Díky

photo
1

@Mention

Tak som s tým dnes jazdil po meste počas dňa.

Striedavo som získaval fix (zelená) a strácal.

Zameral som sa na údaj o výške. Áno je to presne tak. Fix reaguje na získanie výšky.

Výšku som striedavo získaval a jediný zdroj polohy pre FLP bola GSM sieť. GPS som mal off aj Wi-Fi. Barometer v mobile nemám.

Po každom získaní bola výška iná takže nejaku cache môžeme vylúčiť asi tiež.

Zostáva jediná možnosť a to že pravdepodobne niektoré BTS vysielajú aj údaj o výške.

Výšky reálne korešpondovali s lokalitou a ich straty a získania približne so zmenou BTS na ktorú je mobil práve pripojený.

Takže fix na výšku asi nebude použiteľný.

Fix by mal byť naviazaný výhradne na skutočný fix GPS získaný z GPS.


+edit

Volal som známemu čo robí vo firme ktorá nasadzuje BTS.

Takže údaje o výške každej stanice zadávajú.

V priebehu týždňa mi zistí od chlapcov čo majú nastarosti konfiguráciu ako to je s vysielaním výšky do siete. Prípadne prečo niektoré vysielajú a niektoré nie. Celkom ho táto otázka zaujala 😊

photo
1

Oprava:

Tak som skúsil letový režim čiže bez mobilnej siete len použitie Wi-Fi a dostal som údaj o výške! Čiže fix - pip - zelená.

Takže mobilná sieť je mimo podozrenia.

Odkiaľ to FLP ťahá netuším.


Môj laický názor:

V popise fungovania LP a FLP je okrem iného uvedené že sa systém spolieha aj na obvykle správania (rozumej špehovanie googlu) takže google pozná lokality o ktorých má uloženú výšku a tak ju vytiahne ako eso z rukávu a pošle.

photo
1

Hi,

thanks for a test Condor, really weird. May we try a special version? Download: https://nas.asamm.com/share.cgi?ssid=0kw0API

Version writes some log messages into Locus/logs. So simply disable GPS in your system, start app and try to simulate problems you wrote before. If you record also a time when certain problem happen, it may help a lot to find in log mentioned problem. Thanks

Díky!

photo
1

Sorry but it is not very comfortable for us foreigners to mix Tsjech comments with English in one topic (that started in English).

photo
1

Don't tell me about it Henk. Sorry, I'll force Condor to use English here only. ;)

photo
1

Henk sorry. I can not write complicated information correctly in English.

photo
1

@Menion

The file can not be downloaded.

photo
1

Just ignore warning with certificate, there should be some button download anyway ...

or wait, I'll put it to Google Drive, here: https://drive.google.com/file/d/15vnoppTPltTcl5JMQK81L2QLNlcKvN-j/view?usp=sharing

photo
1

OK. I used and tried. I acquired the altitude alternately. The icon remained orange without a fix.

What do I send you?

photo
1

Send me a log from Locus/logs directory. Anyway if there was no fix, no notification on acquired or lost fix etc, then all sounds as working correctly, isn't it?

photo
1

There is no new log in the logs folder.

photo
1

Change everything is different. Outdoors I get fixed and green!

photo
1

I'm stupid, sorry. It's been some time since I generated version that print own logs.

So second attempt: https://drive.google.com/file/d/1ckAsjvCOrei1O4HbPYNtIwSopssh3Eos/view?usp=sharing , thanks!

And main problem I should focus on? Visible altitude (and change of icon to green > have fix) even if GPS in system is disabled?

photo
1

I'm in the building right now, and Locus is totally confused.

GPS-of course off.

Icon orange.

Notification gain GPS silence.

The satellite window shows the height and time of the last GPS fix - 15:47:50.

After a while notifying a lost GPS.


I'll still test it out and write later.


15:47:45.410	D	GpsConnectionPlayServicesImpl	onLocationResult(), locs: [Location[fused 49,000411,21,223729 acc=23 et=+1d15h37m21s61ms]], bundle: null, gpsE: false, networkE: true
15:47:45.415	D	GpsConnection	onNewLocationReceived(Location[network 49,000411,21,223729 acc=23 et=+1d15h37m21s61ms]), fixed: false, autoOff: false
15:47:45.419	D	ALocationSource	setGpsFixed(false, false), current: false
15:47:50.454	D	GpsConnectionPlayServicesImpl	onLocationResult(), locs: [Location[fused 49,000363,21,223638 acc=23 et=+1d15h37m26s108ms alt=291.79998779296875 {Bundle[mParcelledData.dataSize=52]}]], bundle: [verticalAccuracy: 2.0], gpsE: false, networkE: true
15:47:50.456	D	GpsConnection	onNewLocationReceived(Location[gps 49,000363,21,223638 acc=23 et=+1d15h37m26s108ms alt=291.79998779296875 {Bundle[{verticalAccuracy=2.0}]}]), fixed: false, autoOff: false
15:47:50.457	D	Hb	onLocationChanged(Location [tag: gps, time: 1521816470447, lon: 21.2236375, lat: 49.0003634, alt: 291.79998779296875]), provider changed from network to gps
15:47:50.465	D	GpsConnection	setNewGpsLostTimer()
15:47:55.405	D	GpsCompassActivity	onWindowFocusChanged(), restoring fullscreen
15:47:55.406	D	UtilsCompat	setScreenFullscreen(com.android.internal.policy.PhoneWindow@78623fe, NO_FULLSCREEN)
15:47:55.491	D	GpsConnectionPlayServicesImpl	onLocationResult(), locs: [Location[fused 49,000388,21,223685 acc=22 et=+1d15h37m31s128ms]], bundle: null, gpsE: false, networkE: true
15:47:55.493	D	GpsConnection	onNewLocationReceived(Location[network 49,000388,21,223685 acc=22 et=+1d15h37m31s128ms]), fixed: false, autoOff: false
15:47:55.494	D	GpsConnection	onNewLocationReceived(), too early on 'network' location, GPS still valid

photo
1

Amazing, thanks. I've made small improvement that may helps here, so we will see in next Beta version (today maybe).

photo
1

20:19:13.604	D	GpsConnectionPlayServicesImpl	onLocationResult(), locs: [Location[fused 49,002667,21,234413 acc=37 et=+1d20h8m40s274ms alt=290.0 {Bundle[mParcelledData.dataSize=52]}]], bundle: [verticalAccuracy: 2.0], gpsE: false, networkE: true
20:19:13.606	D	GpsConnection	onNewLocationReceived(Location[gps 49,002667,21,234413 acc=37 et=+1d20h8m40s274ms alt=290.0 {Bundle[{verticalAccuracy=2.0}]}]), fixed: true, autoOff: false
20:19:13.621	D	GpsConnection	setNewGpsLostTimer()

photo
1

Additional info: if anyone has a problem with new GPS system, that Locus does not receive location at all, check Google Play Services in your list of apps, if location permission is granted.

More about this in different topic here: http://help.locusmap.eu/topic/what-is-gps-compatibility-mode#comment-53148

photo
1

At great effort yesterday in the city I tried to use a new GPS (FLP) but an inaccuracy of more than 10-20m is useless for serious measurement. The location changes to local networks and WiFi. (OFF WiFi slightly better result).


For exacting work I was forced to use mod compatibility - only GPS satellites.

photo
1

Hi

In terms of the battery consumption, which mode is more preferable - "compatibility mode ON" or "OFF" ?

photo
2

I'm seeing +/- 10m where I used to see +/- 3m. also, the glass never turns off anymore. if the application is on, the GPS is on, regardless of settings ?. it's a battery drain now too. I used to see about 3% drain at the most, now it's closer to 8% ?

photo
1

Hi @Menion

What parameter is used in Locus to get a position?

LocationRequest.PRIORITY_HIGH_ACCURACY ?

or

LocationRequest.PRIORITY_BALANCED_POWER_ACCURACY ?


This information gives answers to the accuracy and consumption of the battery.

Well thank you :-)

photo
2

Guys, please wait on next (Beta = today) version. Work with GPS was re-worked once more.

"Compatibility mode" will be removed. Old system will be used again as base GPS location source, but will also use new "Fused location provider" as a method, that may improve app stability and resistance against "killing" on Android systems with aggressive memory management.

Anyway, because even in old system was made some major changes, it needs to test. Final fixed version will be published after some more testing during next two weeks.

photo
1

the only way to have a working GPS control is to roll back to free version 3.29.2 ?


this means I have to put up with ads in the banner bar, and can't use my PRO version at all ?


this sucks !

photo
1

hi Kyle

Use the Compactibility mode.

Seting, GPS and Location, Compactibility mode - ON.

photo
1

thanks condor, but


compatibility mode does not make a difference. all it does is report +/-10m,


and


NONE of the GPS on/off/sleep/turn off settings work in locus now.


as of 3.30.x the GPS subsection in settings does nothing and battery usage is way up.


in the past I could leave locus in the background and use it as needed without battery drain/GPS usage. now, with 3.30.x it's no longer possible.


yes, I need the best accuracy I can get... when riding unmarked GPS-guided Enduros, that have no trails. bouncing between 30-50m means being on the wrong side of a river

photo
1

OK, I understand.

The on-time version needs Locus restart after changing the GPS mode. Then the real accuracy should be 3-5m.


We have to hold on and wait for the update as the Menion has written.


We all know that GPS accuracy is the most important for Locus.


It depends on reputation Locus!

photo
1

"NONE of the GPS on/off/sleep/turn off settings work in locus now"

Also true for me

photo
1

I may confirm that there are some problems with latest system. Currently latest Beta version 3.30.2.8 ( today published ), should solve all these problems. We are now together with users test it and I only awaits positive responses and then new official version will be published. Believe that in worst case in Monday/Tuesday of next week, thanks for patience.

photo
1

just tried 3.30.2.8 beta.


GPS does not turn off automatically when locus is backgrounded.

GPS does not turn off when "off" is selected in compass /GPSsettings.

I waited about two minutes, toggling on /off , background/etc but it's not turning off.


3.29.2 turns off GPS instantly when backgrounded or turned off via locus settings.


I'm sure you are working hard on this, sorry I didn't find better results for you. :-(


my android is 5.1.1

photo
1

Hello Kyle,

this is quite unfortunate. From your description, it more looks that any other application is using GPS in your system, isn't it possible?

Also what happens when you turn off GPS in compass/satellite screen? Icon of GPS on main screen changes? Your current location on the map disspear?

photo
1

3.30.x-latest - the icon in the android toolbar stays "on" when I turn off GPS in the locus GPS/compass area. the location circle remains the same in the locus application.


3.28.x - the icon in the android toolbar disappears when I turn off via the locus GPS/compass area. the location circle changes to a cross hair (no GPS data) instead of the accuracy circle.


I do not have any other GPS applications running while testing via old 3.28.2 vs 3.30.x


this phone is not rooted, so I do not know if I can provide logs.


this is using a Kyocera Duraforce

I will have a new Kyocera Duraforce XD today to test more

similar results on Samsung rugby pro

photo
1

Kyle, may I please take some more of your time?

I often use this very nice application available on Google Play, that allows recording a video. May you please record a short video that illustrates this problem? Thank you!

photo
1

Sure I'll grab a video today at lunch.

photo
1

On the new device (Kyocera xd) I can't duplicate the problem. Then I tried on both the Samsung devices (rugby pro/i989/i567)and old duraforce , cannot duplicate the problem with latest beta.


Looks like you have fixed it ! Woohoo !

photo
1

Well I spoke too soon. The free beta works, but pro still didn't turn on/off GPS

photo
1

Pro is not yet updated Kyle. Updated is planned on tomorrow (not sure if I'll be satisfied with version, so maybe Monday), so wait a day/two please. Thanks for understanding.

photo
1

good! that means the beta is working properly!


I just rolled back to the 3.29.x version for the weekend.


thanks for the hard work, I know this has been a tough problem to fix.

photo
1

Not only do I love Locus Maps but I must add it has a marvellously responsive support team!

Some weeks ago I found that my GPS no longer worked with Locus. Thanks to Menion, who pointed me to Compatibility Mode, I was able to start using Locus again. Phew, what a big relief!

Then, a few days ago, Locus stopped working with the GPS. I switched off Compatibility Mode and it started working again! Locus, for me at least, won't work in compatibility mode, as it did before.

This is no problem for me as it is now working perfectly well without compatibility mode. I report this so that the support team can know what is happening out in the field. My environment is Meizu M5 Note with Android 6.

I note from the comments above that you are working hard on resolving the GPS issues. Good luck with that and I look forward to trying out the new version.

photo
2

this is working great now.


THANK YOU locus team!

photo
1

Indeed, thank you Locus team.

photo
1

Thank you !

photo
1

And my battery power drain has decreased significantly. Now that is a real win!!

photo
1

Thanks, guys for a positive feedback, really appreciate it! Sorry also for my big mistake in publishing important and significant change without more deeper testing. Will learn from it :).

photo
1

Exactly! That's a job well done right here. Glad to report that GPS is working great. No previous background issues, locks superfast, less battery drain and tracking is consistently precise. Thank you Menion and Locus team!

Replies have been locked on this page!