Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - 0709

Pages: [1] 2 3 ... 10
Tools / Re: c-me live tracking
« on: April 24, 2017, 17:40:20 »
Locus permissions explained:

RTT2 permissions explained:

Locus: All permissions stated below are necessary for running particular application features only.
RTT2: This tracker provides many extra features, for this reasons certain Android permissions are required.

Behelfslösung in actuelle version: Mit eine finger der sensor bedecken, einstellungen machen bis fertig.

Versions / Re: [APP] - version 3.21.x (21. 12. 2016+)
« on: December 25, 2016, 21:02:14 »
I don't think Priority Point will help with this combination?
@ Andrew. Your combination set up in use probably should not show an improvement.
@ Menion  gpx 1.1 out. Prefer Start to be Priority Point, just needs removal of the waypoint extension. (rte point action 1)
In Locus waypointlist: Priority Point "Start point" and Navigation Point "Final point" (rte point action 24)
Q: Can this not be changed to compact version: <name> "Start" and "Finish" ?  No need to add extra word "point".
Priority Points not translated by the xx.tts system so simple "Start" sounds more nice than combination "Start point" by different language TTS engines.

Versions / Re: [APP] - version 3.21.x (21. 12. 2016+)
« on: December 24, 2016, 17:41:51 »
Not 100% sure but maybe next suggestion will help ?
Locus, on any navigation track, should promote the Start Point to be a Priority Point. So not a "Navigation Point Straight" as in actual versions. I only have the most positive experience by (manually) adding the Start point to be a  Priority Point.

Versions / Re: [APP] - version 3.20.x (31. 10. 2016+)
« on: December 18, 2016, 09:40:41 »
Only confirmed lor74cas message, before, I never tried 3d skyplot. Even when removed in Android 4 no problem.

Versions / Re: [APP] - version 3.20.x (31. 10. 2016+)
« on: December 13, 2016, 13:48:47 »
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.

ging früher auch ohne, wenn ich mich recht erinnere.
Die bemerkung stimmt, hab es so eben getestet. Aber errinere mich nicht war es mal anders ? Ich hatte niemals getestet ohne sprachausgabe. Am besten melden in helpdesk: Report a Problem.

Versions / Re: [APP] - version 3.20.x (31. 10. 2016+)
« on: December 09, 2016, 16:58:39 »
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 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:
- 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.

Versions / Re: [APP] - version 3.20.x (31. 10. 2016+)
« on: December 08, 2016, 21:17:02 »
New install Locus maps free v has stopped on both updated tablets.  Tab Pro and Tab 4. Report via google was sent

Hallo Hans,
Der navigationspfeil ist alles der standard Locus.
Virtual demo und real praxis operation sind dan auch sehr änhlich.
Beim track record bemerkt man auch diese kleine abweichungen von navtrack.
Eine video aufnahme der T-deviation navtrack: "Test proximity DTSO gesture function".

Deactiviert bekommt man ein zweites pfeil ( Der position und bewegungs ! anweisung). Probieren sie am besten mal beim realen testfarht (zoom in).
Nur wann ihre bewegungs gps position ganz (cm) genau identisch ist mit der geplante navigationstrack merken sie kaum ein unterscheid.
Video: Der geplante navigationstrack: Source OSM. Der virtuelle fahrt: Source Google maps. Es gibt nur eine ganz kleine unterscheid aber beide sind sicher nicht identisch !

Probier mal in [DE] sprache ;-)
Nun deaktivieren Sie noch „Auf Strecke fixieren“ um die Wirkung der getroffenen Einstellungen sehen zu können.
Bedeutet: In diese video's ist der einstellung: Auf der strecke fixieren: Deactiviert !

Einstellung: Auf der strecke fixieren.

- Einstellung activiert: Der positionsanweisung ist auf der strecke fixiert, bis solange es nicht mehr halt, wegens eine zu grosse gps positions abweichung. Einstellung: Erlaubte Abweichung (30m)
- Einstellung deactiviert: Es gibt zwei positionsanweisungen, der auf der strecke fixierte, UND der reale nicht corrigierte gps anweisung. Beim gerade aus bekommt man so durch die beide anweisungen manchmal in real betrieb ein etwas 'shielendes' "doppelpfeil" sicht effect. In dies (virtual) video gibt es eine gabelung und beide anweisungen laufen immer weiter aus einander bis der corrigierte/fixierte nicht mehr halt, wobei der Locus dan nach zielfuhrungmodus umschaltet.


Versions / Re: [APP] - version 3.20.x (31. 10. 2016+)
« on: November 29, 2016, 10:53:54 »
Phone mounted on bike handlebar, wave once is optimal mode for active cyclists mainly, now more reliable than ever before. Confirmed by cycle test (off desk !) using 1 cm or 5 cm sensor equipment. During CYCLING (moving) no need to use other complicated actions, have to look to the road traffic mainly.
Anyway I do not understand you have to swipe down to activate the (phone) back button ? Tell us more.
And if on Samsung = the most energy friendly efficient solution : Screen on by the home button and screen off by: +Vote

Versions / Re: [APP] - version 3.20.x (31. 10. 2016+)
« on: November 29, 2016, 08:57:45 »
single wave gesture very much improved thanks, not 100% but I hope may now be usable

Good news, at last some succes ! Was by 1 sec cover, than retract hand, than visible screen on/off change, followed by small pause before next screen on/off action ?  If not 100 % maybe a video of your personal wave/touch technique ? still to improve ? You probably do know best functional with clean waving hand ?  ;)
I like the new track waypoints list, bravo.
Me too.
So found a new nice use case in a specific local use example. As Priortiy Points in past versions did not exist,was unknown such Points (If set, even TTS anounced) would become so helpfull and informative. Well that's evolution, as it should be, I suppose. Example usage by Priority Points list: See last picture here:

Versions / Re: [APP] - version 3.20.x (31. 10. 2016+)
« on: November 27, 2016, 12:52:07 »
Locus V
Field test: Single wave/touch gesture control proximity sensor. For me = reliable.
So far the best (in Locus) "gesture function" version I've seen.

Pages: [1] 2 3 ... 10