Messages

with rmap, it looks good. just like blank map.

Looking good now! Except it still doesnt mention the program name... which is kind of standard for the notification area. I'd replace "Aufnahme"/"Recording" with "Locus". But that's just nitpicking...

Locus is a funny name btw if you intend to sell your app in german speaking countries. But people have probably told you already .

locus 1.15.2.5

sorry, but imho this is still very wrong. why does the chosen map make a difference when the screen is off? are you absolutely sure that you arent calling pointless mapsforge functions when the screen is off?

blank map, track recording with screen off, cpu at 200mhz. FINE.
[attachment=0:1yw0l8ts]blankmap.png[/attachment:1yw0l8ts]

mapsforge, track recording with screen off, cpu all over the range. WRONG.
[attachment=1:1yw0l8ts]mapsforge.png[/attachment:1yw0l8ts]

Did you also test battery usage while trackrecording when
a) mapsforge map is sued
b) blank map is used

imho there should be no difference at all (!) when the screen is off. Yet my tests showed case a) to use a lot more cpu.

the "clear all points" function could also be implemented with long-tap on minus button. makes total sense, logically: single tap deletes one point, long tap deletes all points.

-> one button less, only six to go. maybe that fits.

btw... isnt the clear button in this popup menu the same as the X button in the toolbar?

the popup menu is a bit confusing. why would i press a "settings-like" icon to save my route? in general, it might be better to fit all creating functions into the toolbar directly, eg
plus minus route quick confirm cancel

the huge width scroller on screen top is a bit unnecessary imho. is that really needed so often to warrant that amount of screen space? more useful would be a fancy realtime altitude profile :-).

Is there any way to disable this automatism btw? I want Locus to leave the external sd card alone and stay internal, except for the map folders I configure manually.

Reason: I carry plenty gigabytes of maps with me on several micro sd cards. I keep changing them depending on what I do. Locus needs to stay on the internal storage with all its other data, otherwise everything gets messed up badly.

works for me... i never rotate though.

looks cute

The most clever "filtering method" would be using the pressure sensor. Or offline DEM data. Or online DEM data. Or a clever combination of everything that is available .

I was just wondering... maybe there's a difference if Locus is minimized by home-key or if the screen is simply turned off while Locus was active?

HOWEVER... even with the conservative schedule governor, there is still a big difference in cpu usage depending on which map is enabled in Locus:

map "blank": 200MHZ almost 80%, 500MHZ 20%
mapsforge vector map: 200MHZ 30%, 500MHZ 70%(!)

certainly, the type of map should not make any difference at all when the screen is off?! something is bogus and locus still seems to call some rendering code, even if nothing needs to be rendered.

I just managed to get the 1400MHZ rate down to 1%, remaining usage is 200MHZ 60% and 500MHZ (20%) on track recording?

How? The tool "Antutu CPU Master Pro" allows to change the cpu frequency scaling algorithm. Android default on 2.3.6 is something called "ondemand" which goes up to Fullspeed rather quickly (probably after a few microsecs) when something is happening.

The setting "conservative" scales up a bit slower... probably slow enough so it is not triggered by simply reading data from gps driver every now and then. Result is very low cpu clock speed during track logging. Disadvantage could be a slightly larger lag when using the phone, although I didnt notice anything yet.

The pay version of Antutu CPU Master Pro would for example allow to set the scaling to "conservative" automatically only when screen is off.

Your calculations for total climbing are hopelessly wrong. Quite understandable, considering that gps altitude data jumps around more or less randomly by at least 30m. The 15 flat kilometers to my dentist resulted in a 2000m locus climb... I wish we had that kind of mountains here :-).

You need to apply some sort of dampening algorithm on the altitude data before summing up the differences, at least if the origin is gps altitudes.

It works better with google heights, but that's not really useful in the mountains in a foreign country without data connection.

On a related note: how about supporting the pressure sensor of newer phones? That gives much cleaner altitude data when calibrated once.

Locus can join tracks already. How about allowing to split track as well? The menu that appears when I click a trackpoint on the map should offer "Split track here" and then turn "thistrack" into "thistrack_1-429" and "thistrack_430-1099".