Messages

I have not been able to replicate the extreme battery consumption either. However, when it happens, the phone gets REALLY hot in the top left corner where the CPU/GPU is located. Hot as if I was charging and playing a 3D game at the same time.  So most likely it is not a feature or combination thereof that makes this happen, but a freeze/looping.

SGS 2, stock 2.3.5

The blue animated guide line is a major battery consumer.

Extremely nice. I missed this one. My favorites setting at a click away:) Kayak setting: 200m, condition "one". Bicycle setting: 20m, 3 secs, condition "both"

Nice :idea:  As I have quite a few aerial maps, it would be most useful to be able to display some sort of "hybrid" by overlaying i.e a streetmap or topo ontop. For instance, being able to mix an aerial with a topo to view altitude curves would be the best thing since sliced bread.

It would be nice to be able to have another optional choice to display on the guide line in addition to "draw distance" and "draw azimuth". That would be "draw time to target".

I know that this choice is available in the "guide along path top panel", but this panel is not made available when guiding to a single point.

I read somewhere that external bluetooth GPS receivers save quite some battery when navigating on a smartphone. How much battery-saving do we we speak of here? I own a SGS2.

is there so big difference between navigation and track recording in battery life?

Yes it is a huge difference. I cannot say exactly how much but it seems like 100% or so compared to just navigating. Can it be from the constant writing process to SD-card? I am no expert in android, it just came to mind.

Edit: According to graph in Juiceplotter app it seems like 100%

Edit 2: Not to steal the post, OR is still a very good option to have

Hopefully this OR setting will eliminate some CPU intensive calculations when recording a track. My SGS2's battery dies really fast when recording. I have OK battery drain when just navigating between waypoints.

[free]

The free Norwegian app "Norgeskart" I used before migrating to Locus, makes use of Statkart's maps. They do this in the following way: The users are entitled to 10.000 map-tiles a day and offline maps will be stored for 14 days before cache is getting wiped according to rules set by Statkart.

Up till now I have recorded tracks in more or less constant speeds. Today I jumped on my racing bicycle to test these variables with a combo of 15 meters intervals (minimum distance between recorded points) and 5 secs intervals. I found out that the time interval is the only thing that is taken into account when recording. When reaching a top speed of 43km/h (12m/s) there was as much as 75m between recorded ponits. Regardless of the 15m interval I had specified in settings.

Am a bit confused now

PS, maybe this thread belongs in "discussion" section

By the way which of the two settings governs? Interval in meters or intervals in seconds?

This post is not so much a feature wish, but more of a question. Could it be wise to have presets for your chosen activity when starting a new track recording? The arguments here are accuracy versus battery consumption.

When driving a car you need the intervals between points to be very low to be able to record sharp turns accurately. I guess 1 sec is appropriate. Perhaps 4-5 seconds when bicycling. Running could be 7 seconds. Walking perhaps 10 seconds. At sea in a kayak or canoe, one tend to paddle in a straight line quite slowly. 60 seconds will do then. Just suggestions. The crucial bit here is to have the presets as low as possible so people do not feel their track is inaccurate. Also, the more activities to choose from the better so people can find their thing. Suggested activities:

• Car trip (motorcycle)
• Road bike (racing)
• Mountain bike/commuting
• Running
• Walking
• Hiking (more twists and turns than regular walking on a road)
• Kayak/Canoe
• Custom (Manual track intervals input)

Now it also depends on if the points recorded really DO add to battery consumption? Anyway, having these presets will eliminate some of the fiddling with options in settings, which for some people are a lot of. Me personally like 100s of settings, but it can sometimes be forgotten to tweak the interval before I start an activity.

There is no need to actually remove the "meter" and "second" interval setting from options, they can still serve as an override of the preset activity.

OK, so this thread is not quite about Locus, but nevertheless of some interest I guess. I was not quite sure where to put this thread, so "Discussion" was chosen.

We who use Locus are mainly outdoors people and are in the risk of getting our precious phone wet at some point. This thread is for sharing experiences of ways our phones are waterproofed. Points of interest are:

• What brand of case/bag do you own?
• Is it waterproof or water resistant?
• How well can you operate the display when the case/bag is wet?
• Is saltwater a problem for the capasitive properties?
• Solid built?

Me myself has not gotten one yet, but I am thinking of buing one of these two linked below. Krusell is IP67-certified (1m depth for 30 minutes) and Aquabox is IP68-certified (6meters) They have a silicone membrane front and back.

Aquabox
SEaLABox

Framerate is now fine again with distance rings enabled. On Galaxy S2 that is, but it is buttery smooth so I guess lower spec phones will also do just fine.

Hehe, you are right, Menion. A lot of requests  My use of navigation is maybe somewhat different from most. At sea things are quite dynamic as opposed to following terrain and pre-made trails on land. Bad weather, change in winds and currents cause change in plans on-the-go. I just realized when editing the route in test-version 1.13.1.1 that I came a couple of waypoints short to my destination after having tweaked some of the middle waypoints around another small island. Therefore these requests about editing and adding.

It is not a must-have function, but very nice to have the entire trip in one and only track. I guess "merge" will have to do just fine. Now that editing is possible, my most important need is covered.

Thanks again.