Messages

Hi!

Something similar was suggested earlier: //http://forum.asamm.cz/viewtopic.php?f=13&t=1086
I think it would be a great option to have.

These two info-boxes that can appear in the top of the screen are very useful. But it seems I can only make them appear if following a previously recorded track. Is this the case? They are useful, so should be visible when following a predefined route or waypoint also.
Any reason not to?

Which modem, kernel and version of Android are you using?
Mine XXKI3, 2.6.35.7 (speedmod k2-6),  2.3.5  
Mostly standby, without data connection, and a bit radio, battery consumption is about only 9% per day.  

I'm using stock firmware: Android: 2.3.4, Baseband:XXKI1, Kernel: XWKI4.
9% a day? That results in over ten days between charges. Incredible...

Anyhow after several attempts of testing I have not been able to replicate the fault. Next time when it occurs (probably on my next kayak trip )  I will make sure to check it out thoroughly.

Humm, I was not able to replicate abnormal power usage tonight. Consumption remained steady for one hour while I did several tests. With screen on, lot of GUI stuff active, guide and tracking on, result was around -12%/hour and thats great.

Afterwards I connected my 0.5A pocket charger and the phone increases charge even with Locus running with same settings (though sitting stationary by the window).

Weird.

A thought; when I am using it when kayaking I have the phone in an Aquapac bag. This bag gets wet, and then I often get trouble with controlling the software because the bag is activating parts of the screen the whole time. Might this be the culprit? Even with the screen off?

Hi!

Locus is a great software, but there is one thing that keeps on giving me trouble; sometimes the power draw of the application is extremely high. I estimate it to be at least 2 amps at worst. This estimation is based on that the battery graph shows as steep a negative curve as the positive curve is when charging with the wall charger, when I at the same time is charging with a .5A charger.

I have experimented a bit, and I think I have narrowed it down to when the guiding function is active. I can have distance rings on, time rings, custom screen and track recording active, even screen on and consumption seems normal (at worst slowly dropping). But when I activate guiding the power graph spikes downwards.

I can't imagine nobody else has this problem. Is there some setting that might remedy this? I'm thinking that Locus is maxing out the processors for some reason.

I am using Statkart Topo on a i9100 Android 2.3.4 Build KI4.

Thanks for any help!

Aii looking good!! This is a great addition. I like it a lot!

Two comments;
1) The resolution is in 8 colors if I count correctly. It is a little bit hard to see nuances with the colors ranging from red through purple to blue. Maybe better to go through a different color? For example red-yellow-green or red-blue-black.
2) it would be nice to have two color schemes to choose from.

Thanks for the effort!

Hi!

Changing zoom by speed is a nice feature. But for me when kayaking it is not exactly applicable.

What I would really like is for the zoom level to be set so that it is based on distance to next waypoint or a set number of waypoint ahead. What I mean is that if I select auto zoom to two waypoints ahead, the auto zoom will try to keep these two waypoints visible at all times.

It would also be good to be able to set the maximum zoom level when using this function.

Hello guys!

My first post, so I just want to say as the others: thanks Menion for an outstanding piece of software! I instantly stopped using my other navigation tools when I started using Locus.

But regarding track editing; this flexibility is one of the things that makes Viewranger so easy and flexible to use. It would be a very nice thing to have.
Locus though is better at making the initial track since it is using the pointer to set waypoints instead of using a finger which is unprecise.