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 - druki

Pages: 1 2 [3] 4 5 ... 18
Hmmm, I think it's an android/browser issue.
I can directly download on my Xperia V with Chrome and also use "save link". Files are stored in download folder. From there (via ES Exlorer), I can click it and are asked by which app I want it to open.
Maybe this is the point: Your mobile opens the filetype in the browser.
Try to delete the standard assignment by going in system settings->apps, choose your browser and reset the assignments for filetypes.
Some stock browser have problems in open unknown file formats, so maybe trying an other browser could also provide a solution.

Chrome (longclick link):

Ist in der Einzelanzeige nicht das Werkzeugsymbol, worüber Du zu "bearbeiten" kommst?

[DE] - deutschsprachiger Forumsbereich / Re: Fragen vor dem Kauf
« on: January 11, 2014, 02:18:13 »
Die neuen Offline POIs sind (noch) nicht durchsuchbar, es können aber die POI nach Themen aufgelistet werden (damit habe ich im Urlaub komplett offline Toiletten, Supermärkte und Sehenswürdigkeiten in der Nähe gefunden). Zusätzlich können natürlich auch jede beliebige Sammlungen von POIs in den verschiedendten Formaten  aus dem Internet geladen und importiert werden, die dann auch offline richtig nach Namen durchsucht werden können. Ist halt "ein wenig" Einarbeitungszeit notwendig, bis man das alles durchblickt. Aber es lohnt sich, finde ich.

[DE] - deutschsprachiger Forumsbereich / Re: Fragen vor dem Kauf
« on: January 09, 2014, 17:48:52 »
Hi auch,
zum Thema Offlinerouting siehe neben der Onlineroutenberechnung auch
Funktioniert mit nicht allzu langen Distanzen auch als Autonavi bis ca. 200 km, je nach Rechenpower des Mobiles. Dafür ist dann aber die Betaversion des neuen Navigationsmodus zu nutzen, die noch nicht ganz rund läuft (Zeitberechnung bis Ziel, Qualität der Navigationsanseisungen, Neuberechnung bei Abweichen von der Route...). Aber wie gesagt, voll offlinefähig z.B. für's Ausland ohne Roamingkosten.

Siehe meine Antwort in Deinem neuen Threat:

Locus kann alles ;-)
Automatisch verbinden wäre aber schwierig, es müsste festgelegt werden, was die "richtige" Reihenfolge sein soll: Entfernung zur aktuellen Position, zum Startpunkt, nach Wegpunkt ID oder nach Wegpunknamen oder nach topografischer Erreichbarkeit (Wege) oder...
Aber Du kannst mit Locus selbst einen Track (Route) nach den Wegpunkten und individuellem Belieben erstellen, sogar mit Fußgänger-Navigationsfunktion oder Direkt-Querfeldein-Guiding.
Wie das geht, steht hier:

Troubles & Questions / Re: No widget
« on: January 06, 2014, 00:54:56 »
I never used this widget. On my Xperia V it is not in the list to add to desktop.

Troubles & Questions / Re: POI questions
« on: January 06, 2014, 00:42:56 »
maybe exif Information could help. It holds the original time of the photo. Unfoftunately not the orientation (in my Xperia V). If Locus could remember the orientation every second (since calling the feature till submitting the photos), it could later assign the orientation to the exif timestamps. Not very clean solution, but maybe a way...
p.s. I use "photo editor" to see/change exif of photos. Developer is open to questions.

Navigation & Guidance / Re: Navigation on all tracks
« on: December 29, 2013, 02:16:28 »
Hi Menion,
today I had the chance of riding the bus and do some screenshots of this. Seems there is still a bug in computing the time to destination. See speed (is ok),  distance to destination (is ok) and time to destination (too large value). Ah, and I see: Time of arival (13:12) is also too large...
Icon is our van "Nellie" (named after song "Nellie the elephant", because: big, grey, strong) ;-)

Navigation & Guidance / Re: Navigation on all tracks
« on: December 28, 2013, 00:01:43 »
Ok, this was a sofa test, but I used speed_for_moving_cursor_when_gps_off=10.0
Aditionally I just found out that the identical last second only occurs during final approach. Before that, the time to destination (dashboard value) is only changing at instruction points not in between. Tomorrow I will go out in "real world" to see what is happening and get some trackdata to reproduce.

Navigation & Guidance / Re: Navigation on all tracks
« on: December 24, 2013, 12:11:18 »
Hi, I tested some more. Don't know what was wrong last time (old Track from before new test version). This time I tested with GPS deactivated (ok, values of both time fields are no more identical :-) ). I see a strange behavior between time to next instruction and time to destination. The last digit of seconds seem to be identical and the minutes of time to destination seem to be to much. The last point could be because of no GPS (=no speed to calculate time. But then, the seconds should be some other value, too?!). Maybe it's just the way I tested. Attached screenshots of my test to show more clearly what I mean (mind minutes and seconds of both fields).

Versions / Re: [APP] - version 2.17.X+ (updated 16.12.2013)
« on: December 24, 2013, 10:27:16 »
Quick view settings: Bug or normal behaviour that I don't have all settings in the recent testing version?
My quick view:

Settings in Pro (mind "Zeitringe" ) :

Settings current test version (

Navigation & Guidance / Re: Navigation on all tracks
« on: December 21, 2013, 13:03:25 »
I tested navigation beta with the new test version. Unfortunately the value for "time to destination" is not computed correctly. The "time to next instruction" is shown instead in the dashboard and selectable valuefield. Could this be fixed easily?

Versions / Re: [APP] - version 2.17.X+ (updated 15.11.2013)
« on: December 01, 2013, 09:56:50 »
this weekend I played with Navigation Beta and brouter in car mode (and checking what instructions are given during driving a known route).
Automatic recalculation is done with brouter, but Navigation Beta is then not set anymore, it switches to track guiding automatically after recalculatin. Workarround is to stop guiding and to start Navigation Beta again for the new track. Could this be optimized?
Roundabouts seem to be a bit hard to handle (right, left, right with setting high amount of drivinginstructions). Is there a chance to recognize roundabouts and to inform about where I have to leave the roundabout (or could/should it be job of brouter to give this information to Locus)?
Idea for roundabout recognition in Locus:
As I saw in the generated and exported track, there are only coordinates of points and
a) no way to see directly whether this is a roundabout or not. Maybe with calculating and recognizing the curve which has a nearly rectangular change at beginning and end. (mind lefthandtraffic where the curve is the other way round).
b) no way to see how many or where the other exits are (to say "take third exit" ). But maybe it's a good idea (after roundabout recognition) to compute the angle between in and out of roundabout and say "leave at 3 o clock" (for leaving after a quarter circle) or "leave at 12 o clock" (for leaving after a half circle)...?

Pages: 1 2 [3] 4 5 ... 18