[APP] - version 3.20.x (31. 10. 2016+)

[zossebart]

pity, It would be interesting to see how many users are actually using Locus gesture as there has been so little comment

I also use gesture for display on/off all the time when riding mtb with my Sony Z1 Compact. The single wave detection with current non-BETA versions is not perfect, but "OK" I think.
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. Anyway, it still is a lot easier than finding and pressing the tiny power button on the side of the phone! So it's ok for me.
I guess the distance for reliable detection might be different with every phone model. Maybe Locus could implement a "calibration mode" for the sensor in order to adept to different phones/sensors?

One problem with gesture control I'm experiencing is it's behaviour in my pocket. When I forget to disable gesture activation and put the phone into my pocket while Locus is still active, I oftentimes end up with the phone in some settings menu or even "writing" a message to someone ;-)
Maybe this could be improved somehow.

I did not have the time to test the modified gesture control with the current BETA, though.

[0709]

Hi Andy, nice, another Sony user, at last.  I send some more extra info via PM.  The general test report so far:
Locus Beta version 3.20.1.8. Proximity Gesture "wave once" reliability: VERY MUCH improved !  Real nice !
Reference app DTSO Proximity Gesture "single wave"detection by "Leading edge" trigger technique:
Delivers top performance and has the best optimal operator interaction experience by fast(er) screen switch.

How to become a succesfull "Waver" ?

- Wearing gloves, wave with the most reflective (white) parts of the gloves above the sensor !
- Use "correct" near touch technique no need to touch the screen even when using a low sensitive 1 cm proximity sensor.  Video: https://youtu.be/47YmePqH8ro
- A concern and some worry by our developer is the 'in pocket' behaviour when using the wave once mode  ;-) 
- Most important is superior reliable "wave once" function with phone on the bike handlebar by single app Locus
- Use reasonable Android phone screen time out setting to prevent excessive battery drainage if a screen on should occur unobserved by user if the phone is put away out of sight. 
- In pocket proximity optimalisation should not be the main concern preventing a best choice for most optimal performant  screen on/off function.
- And even carry phones with their pulsed rf energy radio connection, into a pocket too close to some "noble body parts" is not advisable too.

[Andrew Heard]

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!).

[john_percy]

Point detail location not displayed on latest beta. See screenshots which are self explanatory
.
The first screenshot is with the beta, the second screen shot with the latest full release.

[menion]

Ah thanks John! I've completely missed this unwanted side effect. Fixed

[michaelbechtold]

Hi Menion, the near freezing effect in high zooms is now reproducible: switching on GPS in Locus creates the effect. Switching off will make Locus fast after the slow reaction time.
Unfortunately Tapatalk does not show the resp. issue report, hence reporting here.

Gesendet von meinem LG-H850 mit Tapatalk

[Andrew Heard]

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.

[menion]

@michaelbechtold: quite a problem ... I have two +- new devices and both waits on Android 7 (manufactured promised December/January) ... on simulator it works fine for me and without simulation on own device, I have almost no chance to fix it.

@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 ...

[Andrew Heard]

@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:

[menion]

Yep, issue started with 3.20.1.9. I'm now anyway unable to generate working version for 4.x devices. Locus Map Pro on Google Play is fine. When Android 4.x will be removed (hope not), udpate won't offer on 4.x devices, so no worry. Only issue now, are people with 4.x that use Beta versions for testing ....

[menion]

Hello guys,
who had troubles with latest Beta on Android 4.x? May someone (more > better), test this version

https://nas.asamm.com/share.cgi?ssid=0eMOMZ0

Thank you! (in case of same crash, please create me a log)

[balloni55]

While playing with new Beta i´ve compared new and old 3D skyplot and i can´t see any benefit of the new version
no difference between GPS and glonass in new version and much more difficult to recognice the sats in the lower part of the display

don´t worry, i dont use it and till now also no other user make a comment, so it´s not important but a pity about your wasted time

[0709]

who had troubles with latest Beta on Android 4.x test this version

Install on  GT-I8160 CM11 SM-T520 4.4.2 SM-T235 4.4.2 THL4000 4.4.2 OK.

[menion]

@balloni55: no worry, there is absolutely no wasted time . I'm learing OpenGl (hardware rendering) system and best is to learn on something specific, not just by reading books. And only what is in Locus for now that use OpenGl is this Skyplot system. So consider this as first step and I'm accepting feature requests here .

What is problem with bottom numbers? Fact that numbers are rotated? It's because for example on my device, I see usually more then 20 satellites and numbers were one over another .. completely unreadable.

@0709: very good, we are saved . Uff ... thanks!

[Frisk]

Hello guys,
who had troubles with latest Beta on Android 4.x? May someone (more > better), test this version

https://nas.asamm.com/share.cgi?ssid=0eMOMZ0

Thank you! (in case of same crash, please create me a log)

As written in the help section, this version works fine for me! SGS3 with Android 4.x. Thank you very much! Hope the support for Android 4.x will last for some more time! Really like the app.