Messages

Hi Henk,
thank you for your help,
guiding works exactly as you described.

The question remaining is, what is the simple information 'out of corridor' good for. Wouldn't it be possible to distinguish between left and right off route in order to leave the map off and/or to reduce stopping.
And, not least the proof of passing a waypoint and switching to the next one via the  distance to it seems to be of critical functionality, e.g. when the route is shifted somewhat to a certain direction  compared to reality, one would need large distances. T.m.o. a criterion like crossing a circle around the last but one with a radius of the distance between the actual and the last but one waypoint might work better.

Nevertheless, great app.
Emmi12

Hello, the 3rd,

regarding power consumption all seems nice with 2.5.1:
10,5 hours for battery discharge (from 100 to 15%, with PowerTutor running which consumes about 5% of power for itself)
when tracking with 20m/5s intervalls, offline vectormap, display off besides ~ 3 times/hour for a short localizing view with some scroll/zoom,
and all radio off,

I'll repeat this test with stepwise switching 2g, 3g, occasionally harware compass on,
and maybe to distinguish between the kind of map and its usage as i asked above.

Hello again,
thanks a lot for that immediate answer,

I'm looking foreward for the new version (I've read the postings on 'sucks battery' already, but was afraid of having no long-term running app this weekend).

Regarding power consumption the principle influences and strategies to minimize it were welcome,
but, the ask for numbers was mainly to the community, maybe somebody has tested this already
(although we might all have family, job, and other hobbies).

Regarding guiding along given route I've found some hints at the forum here and will play with that before a more precise question (I can follow you all in having no fun with writing manuals, but it would be nice to have.)

Thanks again, emmi12

Hi everybody,

as an android (2.3.6) novice I have a bundle of questions that might partly fit to android itself, but deal with locus:

1) Is there any chance to restore an old locus version - without having made a backup, I mean the plain app without any own data or settings, and of course with keeping my pro license? This need comes from
1a) missing the categorys icon/entry in the data manager screen after trying to work with POIs as given by hbemmert in the web,
1b) the power consumption of v. 2.5.0 is really frustrating: using a vector map, all radio off (airplane mode), tracking with map on, but display off besides short looks every 20 min - they battery drops from 90 to 15% within 4 hours.

And with respect to the last point:
2) Has anybody tested the settings to minimize power consumption to survive a 9 hours tracking with a quarterly look at the map  (this worked on my old WinMobile with Pathaway), esp.
2a) vector vs. bitmap (does the app really know that there is no need to calculate the display when it's off)
2b) osmarender vs. other themes (like cycle_hc as recommended for open cycle maps)
2c) leaving the map display in the foreground to rapidly have it available when setting the display ON or switching the app off i.e to background when tracking?
And all this preferably with numbers (e.g. maximum running time or power consumption during 1 hour) to get an idea what the costs for a higher comfort are.

And, finally although this question doesn't fit the headline:
3) Will I find a description how the guiding along a predefined or imported route works?

Thank you in advance in hope of reply.