[APP] - version 3.30.+ ( 15. 3. 2018 )

[merilius]

I don´t like the Star Wars startscreen. Whats the link between Star Wars and Locus?
How can it be switched off?

+1
I don't like the Star Wars start screen, I don't like Star Wars at all!

[Žajdlík Josef]

Maybe I also encountered a GPS problem. In the enclosed SCR, you can see a shortening of the recording path. I saw the record in the "record accuracy" view. In the red, I then mapped the way the route actually went. It can be seen that there was a weaker signal in the woods. I would understand, but why did not the record compare when walking along the river?

CZ: Asi jsem taky narazil na problém s GPS. V přiloženém SCR je vidět zkrácení trasy záznamu. Záznam jsem zobrazil v zobrazení "přesnost záznamu". Červeně jsem pak do mapy dokreslil kudy vedla trasa ve skutečnosti. Je vidět, že v lesíku byl slabší signál. To bych chápal, ale proč se záznam nesrovnal při chůzi podél řeky?

[tramp20]

What about restoring an older backup, does it work for you?

What I did:
1. Upgrading the pro (free was ok): panels lost
2. restoring a settings backup from 3.30: no success
3. restoring 3.30.0 (app + settings) with titanium backup: panels ok
4. saving these settings again
5. upgrade to 3.30.1: panels lost
6. restoring these settingsfrom 3.30.0 again: no panels

Finally I added the upper and right panel manually again.


I have attached these two settings.

[Viajero Perdido]

I don't like the Star Wars start screen, I don't like Star Wars at all!

Even though I couldn't care less about Star Wars, the startup screen still makes me smile.  (But I already voted.)

I lost my panel layouts on both devices with the . 1 release (other settings are okay), so I just rebuilt them.  Don't make me do that too many times, okay?

[Menion]

@Žajdlík Josef
And why should I know solution on this problem? Even that GPS system changed little bit, there is still no change in what Locus Map do with received locations > nothing. There are no modifications in received data, so sorry, I can't help here, device issue.

@tramp20
amazing, thanks. Is it possible that you did not change top/function panels for maybe "few years"?
Anyway problem found, fixed and quick bug-fix is on the way.

[tramp20]

@tramp20
amazing, thanks. Is it possible that you did not change top/function panels for maybe "few years"?

Yes, perhaps ~2 years

[Viajero Perdido]

I haven't changed my top panel in a long time (years?) on either device, and I think both had identical content, so maybe that's why they reverted to a default state.  The right-side panel, yes, I've changed that more recently.  6 months ago maybe.

Thanks for changing the blue notification bar to black again.

I still don't see Hint nor Load All Waypoints in the ">" menu from a cache popup in the .1 version, for caches in the database that do have hints / waypoints.  Are you saying you put those back?  Maybe we're thinking of different places in the interface.  (It would be nice to have them back.)

Thanks,
VP

[Žajdlík Josef]

@Žajdlík Josef
I can't help here, device issue.

In any case, thank you. Maybe I've figured out what the problem is. I accidentally started recording with a profile including the throat pulse measurement. But it was not connected and it probably caused problems. The second attempt with the right profile has gone well.

Cz: V každém případě děkuji. Možná už jsem přišel na to v čem em je problém. Omylem jsem spustil záznam profilem zahrnující i hrudní pás na měření tepu. Ten ale nebyl připojen a to asi způsobilo problémy. Druhý pokus se správným profilem už proběhl v pořádku.

[Diddi]

Panels are back. Thank you

[Menion]

@tramp20
yep, that's expected: http://help.locusmap.eu/topic/right-panel-disapper-after-update-to-3-30-1#comment-52909 , sorry.

@Viajero Perdido
really please check mentioned settings > maps > points & tracks > popup content. If this option is by accident disabled (sorry), please enable it back

@Žajdlík Josef
[CZ]tedy tohle by ale opravdu vůbec nemělo mít vliv. Hodnoty ze senzorů se přiřazují až později. Polohu z GPS opravdu v aplikaci nemůže ovlivnit vůbec nic. Pokud by se ti povedlo problém nějak nasimulovat opakovaně, doporučuju zkusit zaznamenat NMEA zprávy ( nastavení > GPS ). Ten vytvořený soubor pak bude obsahovat téměř surová GPS data a bude pak tedy možné poznat jestli chyba vznikla v systému ( je již v těchto datech ) a nebo až později v Locusu. Jinak s tím opravdu nic nesvedu.

@Diddi
uff, perfect

[Viajero Perdido]

@Viajero Perdido
really please check mentioned settings > maps > points & tracks > popup content. If this option is by accident disabled (sorry), please enable it back

Ah, thanks for reminding me where those settings are kept.  I turned them back on, and they work fine - on both devices.

You know, I haven't visited that settings screen in a very long time.  This all sounds eerily familiar...

[nitram]

Panels are back with ver. 3.30.2.
Thank you.

[skwal]

i have on the panel the option
altitude manager

when i clicked it in the past i came direct to pressure where i can calibrate the barometer
when i click in  the newest version i come to setting. and have to click to pressure manuel

can it be fixed?

so no bug and an intention?

[Bucky Kid]

To menion:
Here's another ugly bug with route planner: opening it on certain track forces Locus close. I'm trying to figure out what's specific with this track that it makes Locus crash.

Record from the error log:

Code Select Expand

03-22 13:42:01.281 17089 17089 E AndroidRuntime: FATAL EXCEPTION: main
03-22 13:42:01.281 17089 17089 E AndroidRuntime: Process: menion.android.locus.pro, PID: 17089
03-22 13:42:01.281 17089 17089 E AndroidRuntime: java.lang.RuntimeException: Unable to start activity ComponentInfo{menion.android.locus.pro/o.sl}: java.lang.IndexOutOfBoundsException: Index: 0, Size: 0
03-22 13:42:01.281 17089 17089 E AndroidRuntime: at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2699)
03-22 13:42:01.281 17089 17089 E AndroidRuntime: at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2766)
03-22 13:42:01.281 17089 17089 E AndroidRuntime: at android.app.ActivityThread.-wrap12(ActivityThread.java)
03-22 13:42:01.281 17089 17089 E AndroidRuntime: at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1507)
03-22 13:42:01.281 17089 17089 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:102)
03-22 13:42:01.281 17089 17089 E AndroidRuntime: at android.os.Looper.loop(Looper.java:154)
03-22 13:42:01.281 17089 17089 E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:6236)
03-22 13:42:01.281 17089 17089 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
03-22 13:42:01.281 17089 17089 E AndroidRuntime: at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:891)
03-22 13:42:01.281 17089 17089 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:781)
03-22 13:42:01.281 17089 17089 E AndroidRuntime: at de.robv.android.xposed.XposedBridge.main(XposedBridge.java:107)
03-22 13:42:01.281 17089 17089 E AndroidRuntime: Caused by: java.lang.IndexOutOfBoundsException: Index: 0, Size: 0
03-22 13:42:01.281 17089 17089 E AndroidRuntime: at java.util.ArrayList.get(ArrayList.java:411)
03-22 13:42:01.281 17089 17089 E AndroidRuntime: at o.azp.ॱ(:78)
03-22 13:42:01.281 17089 17089 E AndroidRuntime: at o.iq.ˊ(:705)
03-22 13:42:01.281 17089 17089 E AndroidRuntime: at com.asamm.locus.maps.utils.selection.MapSelection.ॱ(:2478)
03-22 13:42:01.281 17089 17089 E AndroidRuntime: at com.asamm.locus.maps.utils.selection.MapSelection.ˎ(:2433)
03-22 13:42:01.281 17089 17089 E AndroidRuntime: at o.sv.ˎ(:604)
03-22 13:42:01.281 17089 17089 E AndroidRuntime: at o.sv.ˎ(:210)
03-22 13:42:01.281 17089 17089 E AndroidRuntime: at o.sv.ˊ(:77)
03-22 13:42:01.281 17089 17089 E AndroidRuntime: at o.Ч.ॱ(:166)
03-22 13:42:01.281 17089 17089 E AndroidRuntime: at o.ҫ.ˊ(:129)
03-22 13:42:01.281 17089 17089 E AndroidRuntime: at o.Cz.onCreate(:63)
03-22 13:42:01.281 17089 17089 E AndroidRuntime: at o.sl.onCreate(:161)
03-22 13:42:01.281 17089 17089 E AndroidRuntime: at android.app.Activity.performCreate(Activity.java:6684)
03-22 13:42:01.281 17089 17089 E AndroidRuntime: at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1119)
03-22 13:42:01.281 17089 17089 E AndroidRuntime: at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2652)
03-22 13:42:01.281 17089 17089 E AndroidRuntime: ... 10 more
03-22 13:42:01.289  1860  1914 W ActivityManager:   Force finishing activity menion.android.locus.pro/o.sl
03-22 13:42:01.300  1860  1914 W ActivityManager:   Force finishing activity menion.android.locus.pro/com.asamm.locus.basic.MainActivityBasic


[Menion]

*** BETA version 3.30.2.3 ***
- geocaching users: please check display of listings & images. If all is correctly sized and click on images display device image viewer
- GPS problems? Should be a lot better now
- and many other various changes

@skwal , @Bucky Kid
ah, I've forget to check these two problems, sorry. At start of week, I'll look at it ...