Author Topic: [APP] - version 3.7.x (16. 3. 2015)  (Read 47900 times)

Offline balloni55

  • Global Moderator
  • Professor of Locus
  • *****
  • Posts: 2670
  • Thanked: 123 times
    • View Profile
  • Device: Samsung XCover 4s Android 10
Re: [APP] - version 3.7.x (16. 3. 2015)
« Reply #90 on: April 01, 2015, 20:13:46 »
i have used new "Guidance" a few times and it work well :)
one thing i am missing, at the end of the track there is no notification e.g. "you have reached your target"
Locus PRO 3.45.1
 

Offline menion

  • Administrator
  • Professor of Locus
  • *****
  • Posts: 11758
  • Thanked: 398 times
    • View Profile
    • http://www.asamm.com
  • Device: SGS7
Re: [APP] - version 3.7.x (16. 3. 2015)
« Reply #91 on: April 01, 2015, 20:19:00 »
yes I noticed this too. Then I did some changes due to ta-ka discoveries and during today test, it was ok. So I hope, problem solved :).
Ideas, wishes, problems
Advanced topics, public discussion, sharing of knowledges, testing beta versions: you're here!
 

Offline balloni55

  • Global Moderator
  • Professor of Locus
  • *****
  • Posts: 2670
  • Thanked: 123 times
    • View Profile
  • Device: Samsung XCover 4s Android 10
Re: [APP] - version 3.7.x (16. 3. 2015)
« Reply #92 on: April 02, 2015, 09:15:54 »
with Beta-FREE map preview in track list isnĀ“t visible
if i change "use style of folder" to refrech map preview, for short time worldmap is visible, after that no map only name of towns are visible.
If i refrech preview in PRO map preview is displayed in Beta-FREE

Locus PRO 3.45.1
 

Offline menion

  • Administrator
  • Professor of Locus
  • *****
  • Posts: 11758
  • Thanked: 398 times
    • View Profile
    • http://www.asamm.com
  • Device: SGS7
Re: [APP] - version 3.7.x (16. 3. 2015)
« Reply #93 on: April 02, 2015, 09:27:56 »
hmm but below first track is! visible some map. Do you have vector map available for this region also in beta version? So to be more precise - are there same maps available for both versions?
Ideas, wishes, problems
Advanced topics, public discussion, sharing of knowledges, testing beta versions: you're here!
 

Offline balloni55

  • Global Moderator
  • Professor of Locus
  • *****
  • Posts: 2670
  • Thanked: 123 times
    • View Profile
  • Device: Samsung XCover 4s Android 10
Re: [APP] - version 3.7.x (16. 3. 2015)
« Reply #94 on: April 02, 2015, 09:53:57 »
Quote
are there same maps available for both versions?
no :o so sorry for trouble
Locus PRO 3.45.1
 

Offline menion

  • Administrator
  • Professor of Locus
  • *****
  • Posts: 11758
  • Thanked: 398 times
    • View Profile
    • http://www.asamm.com
  • Device: SGS7
Re: [APP] - version 3.7.x (16. 3. 2015)
« Reply #95 on: April 02, 2015, 10:05:26 »
fine, no problem :). Locus iterate over all available vector maps, if there is at least one available for this area. It is of course possible, that check should be incorrect, because of some remaining issues in bounding areas of vector maps. But I'm glad it wasn't this case :).
Ideas, wishes, problems
Advanced topics, public discussion, sharing of knowledges, testing beta versions: you're here!
 

Offline gynta

  • Global Moderator
  • Professor of Locus
  • *****
  • Posts: 3554
  • Thanked: 40 times
    • View Profile
    • Locus live tracking service
  • Device: SM-A530F(A8) Android 8.0.0

Offline menion

  • Administrator
  • Professor of Locus
  • *****
  • Posts: 11758
  • Thanked: 398 times
    • View Profile
    • http://www.asamm.com
  • Device: SGS7
Re: [APP] - version 3.7.x (16. 3. 2015)
« Reply #97 on: April 03, 2015, 07:03:15 »
Thanks for test, so bugs are fixed, suggestions not, it's ok.

http://forum.locusmap.eu/index.php?topic=4467.msg35455#msg35455

I understand an issue, but have no better suggestion. And because no one complains, no need to do something with it for now

http://forum.locusmap.eu/index.php?topic=4461.msg35495#msg35495

http://forum.locusmap.eu/index.php?topic=4461.msg35491#msg35491 - Michal is our boss on English now, so what he say is saint for me :)

http://forum.locusmap.eu/index.php?topic=4467.msg35556#msg35556

Oki so better - "Start \'Bluetooth manager\' and select default device"

EDIT: about FC, thanks for log. But I see nothing useful in it. Some way to reproduce? Only in the end of log is some ANR issue (application not responding), is this mentioned problem?
« Last Edit: April 03, 2015, 07:24:39 by menion »
Ideas, wishes, problems
Advanced topics, public discussion, sharing of knowledges, testing beta versions: you're here!
 

Offline ta-ka

  • Premium
  • Padavan of Locus
  • ***
  • Posts: 250
  • Thanked: 3 times
    • View Profile
  • Device: SGNoteEdge
Re: [APP] - version 3.7.x (16. 3. 2015)
« Reply #98 on: April 03, 2015, 12:24:30 »
@ta-ka: hmm thanks, very helpful. I found an older code from times, when TTS file wasn't so useful as now. I've improved whole system and now it should work as expected.
I confirmed that "Next waypoint" notification come from tts file now in 3.7.2.3.
However there are issues remained. (confirmed with guidance.gpx attached again below)
- Locus says "after 300m turn around" before the end point "DEST".
- Locus doesn't say about approching to the destination.

And, One request please.  I would like to translate "DEST".

Quote from: gynta
don't see "built the project" on crowdin 8)
Quote from: menion
hehe :)
version without translation
:'(
 

Offline ta-ka

  • Premium
  • Padavan of Locus
  • ***
  • Posts: 250
  • Thanked: 3 times
    • View Profile
  • Device: SGNoteEdge
Re: [APP] - version 3.7.x (16. 3. 2015)
« Reply #99 on: April 03, 2015, 14:39:09 »
@balloni55: heh, Locus had problems with times where was '0 seconds' :). Fixed, thanks.
'0 minutes' not fixed.  :(

After one hours passed, locus talks only hours and minutes. I think there should be seconds, too.
Currently, if time interval is set to 30 sec, Locus talks the same "X hours Y minutes" twice at 0 sec and 30 sec.
 

Offline Christian

  • Premium
  • Master of Locus
  • ****
  • Posts: 823
  • Thanked: 10 times
    • View Profile
Re: [APP] - version 3.7.x (16. 3. 2015)
« Reply #100 on: April 03, 2015, 21:09:08 »
Sun was shining, so i started first test of guidance with latest beta.
At first: it works! My dream come true!
Default settings are correct for automatic display activation.
But... the beta is unstable, stopped 1x and another time I got an black screen, did not know how to get rid of it while trailrunning :( But guidance was still active, could hear beeping before the junctions.
The navigational commands are sometimes wrong. Obviously you have to go left but the command is "keep right". See screenshot.
The beeps before arriving the junctions are to early than too late. See comments above.
I will keep trying and maybe I will find another issues. When issues written above are fixed in the next public release we can step on the next stage: simple sounds.
Just now i'm really happy about the new guidance :D

Edit wants to say that i got some ugly errors like "you are not allowed to post in this forum" or "too less memory for thid operation" and others :( If anyone is interested in an admjn for tapatalk plugin....I will do it.
« Last Edit: April 03, 2015, 22:04:01 by Christian »
 

Offline gynta

  • Global Moderator
  • Professor of Locus
  • *****
  • Posts: 3554
  • Thanked: 40 times
    • View Profile
    • Locus live tracking service
  • Device: SM-A530F(A8) Android 8.0.0
Re: [APP] - version 3.7.x (16. 3. 2015)
« Reply #101 on: April 03, 2015, 21:30:43 »
After starting Locus:

I think "Select default Bluetooth device" is enough because Locus already has started.
Oki so better - "Start \'Bluetooth manager\' and select default device"
Nope, because message also pops up inside BTmanager (Ater switch on)


btw..
And here is another problem. see clip:
at second...
00:13 - Locus is searching... without break. (I cut 4 minutes waiting time in the clip)
00:31 - I have to switch OFF and ON to popup the device list and after this, searching for devices works as expected.

hope it's clear what I mean :)

Offline gynta

  • Global Moderator
  • Professor of Locus
  • *****
  • Posts: 3554
  • Thanked: 40 times
    • View Profile
    • Locus live tracking service
  • Device: SM-A530F(A8) Android 8.0.0
Re: [APP] - version 3.7.x (16. 3. 2015)
« Reply #102 on: April 03, 2015, 21:45:34 »
I'm not able to see the difference and effect of this Quick setting.
 
I understand an issue, but have no better suggestion. And because no one complains, no need to do something with it for now
suggestion
On crowdin do you use one word "notify_out_of_track" for both(!) functions.
better is: one string for guiding - and one for navigation.
eg(!)
\"Out of track\" notify (Navigation)
and
\"Out of track\" notify (Guidiance)
or similar..

Offline gynta

  • Global Moderator
  • Professor of Locus
  • *****
  • Posts: 3554
  • Thanked: 40 times
    • View Profile
    • Locus live tracking service
  • Device: SM-A530F(A8) Android 8.0.0
Re: [APP] - version 3.7.x (16. 3. 2015)
« Reply #103 on: April 03, 2015, 21:54:41 »
about FC. Some way to reproduce?
Sure. See "02.FC BT" in our dropbox.
(New CatLog + Clip)

Offline menion

  • Administrator
  • Professor of Locus
  • *****
  • Posts: 11758
  • Thanked: 398 times
    • View Profile
    • http://www.asamm.com
  • Device: SGS7
Re: [APP] - version 3.7.x (16. 3. 2015)
« Reply #104 on: April 03, 2015, 22:58:34 »
@0709: hmm good old guiding system in action. When I change it to same system as for navigation, where will be a difference compare to "Navigation"? isn't what you want just "Navigation" without purple line and arrows in top left corner?

@ta-ka: are you really interested in seconds when you are in time, more then hour since start? Because here it is not an issue, but intent.

@Christian: report "unstable" do not help me, sorry. Wrong commands - attach me please an exported GPX so I may test it, thanks.

@gynta: hmm found maybe a one possible problem, why orange popup appear, so next version. About texts in Quick settings ... oki, give up, thanks :)

About FC: hmm in log is

04-03 20:31:21.242 F/libc    (14296): @@@ ABORTING: INVALID HEAP ADDRESS IN dlfree
04-03 20:31:21.242 F/libc    (14296): Fatal signal 11 (SIGSEGV) at 0xdeadbaad (code=1)

Seems to be some issue in Android native library. This never happen before? Did you do any system update of your device?
Ideas, wishes, problems
Advanced topics, public discussion, sharing of knowledges, testing beta versions: you're here!