Messages

Awesome release. Have a great Christmas and rest without thinking about Locus for a while. That new what3words system looks amazing.

So new version published as Beta version on Google Play right now.

@menion - good Christmas present with 3.20.1.12 now working again on my Android 4.4.2 tablet, relief. Also confirm crash with 3D skyplot. Best Christmas wishes to whole hard working Locus team.

who had troubles with latest Beta on Android 4.x? May someone (more > better), test this version
Thank you! (in case of same crash, please create me a log)

@menion - crash on Android 4.4.2 with 3.20.1.9 (as previously reported). Now with 3.20.1.11 first run had crash, but then 2nd run it works, although completely default screen, no offline map, no user buttons, I assume config.cfg not read, other data read from test folder. Probably this is not a problem/ was expected. 3.20.1 (Pro) still working. Well done to find the A4.4.2 problem. Thanks.

@Andrew Heard: I spend on this almost two days. Currently it looks I'll have to remove support for Android 4.x . Testing anyway in progress ...

@Menion - seems problem introduced between 3.20.1.8 & 3.20.1.9. Tablet was fine with 3.20.1.8. I'll have to stick with 3.20.1 Pro, uninstall free/beta on the tablet & ensure no further updates. I assume I should never upgrade Pro on tablet otherwise will become totally useless for any route planning while cycle touring. Hopefully not similar problem with Android 5.0.1 otherwise phone will suffer the same fate. There needs to be a version compatibility test in Google Play to prevent any accidental upgrades:

Just upgraded Android 4.4.2 tablet to latest beta 3.20.1.9 - immediately crashes at start. 3.20.1.9 working fine on 5.0.1 phone. I think @0709 reported same, but I can't now find his comments or which subject.

Actually, waving in front of the phone doesn't work very reliable for me, I have to wave pretty near by the sensor for the detection to work, so I ended up touching the front of the phone where the sensor is located much like pressing an "invisible" button.

@zossebart - my exact experience, the Xperia sensor only works over short distance, so I have to hold (not just wave) the top/left of phone, but like you end up "tapping" some Locus button along top of screen, so end up with some other screen displayed instead of main map. I prefer Locus full screen mode (on small screen) but if I keep non-full-screen then there is one "row" of space at top of display, and this reduces chance of a false-tap. I also experimented with moving all Locus top buttons to right side, but wastes more space. Nearly easier to stick with power button. All it would need (sounds trivial from user point of view) is for Locus to ignore all taps for short period after toggle of display state. I am also experimenting with phone in 180 degree portrait mode so IR sensor at bottom (maybe less false taps), but results in new problems (of course!).

how DSTO detect if device is covered by cover or placed into pocket?

@menion - DTSO (not DSTO) has separate flipcover & "single wave" configuration, so subtly different use-cases in-pocket and on-handle-bars are optimised instead of one-size-fits-all compromise solution; don't get me wrong - it's still a great feature

I consider current solution as final. If you need something like DSTO, then why don't use this application for this task?

pity, It would be interesting to see how many users are actually using Locus gesture as there has been so little comment, DTSO didn't work for me when I tried it a year ago; I have just installed the latest version, it now turns on the display with single wave on "leading edge", so very quick & responsive, although I can't get it to turn off the display; I'll discuss with @0709; the Locus implementation does work but I think could just be improved further; I love Locus & tell everyone about it, but if Locus aims to be the best GPS app for cyclists then why have to install another app for even better gesture control

Another reason to favor Locus: DTSO is working for all apps whereas I only want gesture control to operate while running Locus. DTSO can be disabled of course but...

And behavior was little bit improved for navigation started off the track. Good to hear it works fine now.

in few short tests, navigation start has improved a lot, previously sometimes never "started", now actually works

@menion - have you recently improved navigation behavior for situation where initial position is not directly on the track? I had observed in the past that with auto-recalculation off, sometimes when navigation is started the large question mark icon never changes to a proper turn icon even once position is directly along the navtrack:

I have been testing this again and certainly for a few walking tests with 3.20.1.8 I now observe that navigation may switch between question and distance icon a few times, but will correctly stabilize once the track is reached:

Maybe you improved behavior but forgot to mention in release notes? If so, thanks for the worthwhile improvement.

@0709 has just recorded a video https://youtu.be/uTJNALgAawE demonstrating leading & trailing edge trigger of display toggle. His DSTO app is using leading edge trigger, and is clearly more responsive than Locus single wave trailing edge trigger.

Related, and good news, I had suspected that Sony Xperia "stamina" power saving mode was causing unreliability of Locus gesture mode - I had a "theory" that after a period of inactivity Stamina mode was turning off the IR sensor. But I've now done many hours riding and testing, and Stamina mode has made no difference, and more importantly there was no obvious increase in power consumption with IR sensor turned on with Stamina mode disabled and gesture enabled.

@menion - another idea/ observation/ suggestion regards gesture control - I've noticed a few times, not many but still annoying, that when I gesture to turn on the display, that a menu or screen or other app is displayed because the gesture is also a tap. I find the most reliable way to register as an object is to hold my palm over the IR sensor, but of course there is risk that Android thinks I am tapping display. With non-conductive gloves it then becomes impossible to return to the main map without taking off the gloves. Suggestion: would it be possible to have a short period after turning the display on in which all taps are ignored? I can't think of any reason a user would gesture then expect to accurately tap within say 100ms.

I think we agree. You say "cover" and "uncover" so there is a delay. "uncover"=my term "trailing edge". I was just suggesting "toggle" on "cover" (leading edge) instead of "uncover". No need for field testing, should work just as well in office. Now even with thick gloves I can toggle the display, previously I had difficulty feeling where the tiny power button was. Other good news - I haven't noticed any increased power consumption on short 2hr ride. Normally 2%/hr with track recording, 3%/hr with track+navigation. Will do 13hr ride on weekend to confirm these numbers.

...On single wave event, Locus should react as soon as possible.

@menion - it appears the display toggles on the "trailing edge" i.e. when hand is removed. Could Locus react faster if display toggles on the "leading edge" i.e. when hand is detected? This would save 0 to 2 seconds of delay.

...Problem with " I just hold hand over sensor, and maybe 50ms later display toggles" is as I wrote ... how to detect for example device placed to pocket?

@menion - separate flipcase mode? it appears in order to accommodate the flipcase scenario the single wave mode is compromised.

@menion 3.20.1.8 release notes in app: link from 1st topic "option to disable internal..." doesn't work - "application missing". Other links work, so I assume URL is broken.

@menion I reported this bug a few days ago but no acknowledgement - maybe you missed it - in full screen mode > edit track > save > there is no "back" button, no way to exit this screen without dragging down status bar.

...maybe it help anyway it again create from short quick wave, something like before ... "long wave". Because exists option to show bars by pull from bottom, I should with current system for now ...

@menion @0709 - although the gesture system is now working for me, it relies on detecting the object within a minimum/ maximum time window, and the display toggles on the "trailing edge" of detection. If hand is too fast or too slow then no action, only frustration. As Willy suggested a long time ago, maybe a further improvement and simplification is trigger on "leading edge" rather than "trailing edge" of detection - just wait until object is detected for minimum time then toggle display state, and completely ignore the maximum time? Example - I just hold hand over sensor, and maybe 50ms later display toggles. I remove hand any time later, no change. I again hold hand over sensor, display toggles. Simple and more timely operation, simple to document, simpler to code, more reliable.

I had been having trouble for quite a while because of Sony "Stamina mode". Gesture would work well for many minutes, then not at all. Probably after inactive time the IR sensor was turned off in this power saving mode. Thanks @0709 again for solving problem.

Locus V 3.20.1.6.
Field test: Single wave/touch gesture control proximity sensor. For me = reliable.
So far the best (in Locus) "gesture function" version I've seen.

single wave gesture very much improved thanks, not 100% but I hope may now be usable

Bug with full screen> edit track > save > there is no back button

I like the new track waypoints list, bravo.