Messages

Displaying less points and tracks basically solved the problem (i continued to use vector maps, memory seems to be enough when not displaying a lot of additional information) on an unmodified phone.

I've now tried to increase the dalvik.vm.heapgrowthlimit from 48 to 128 mb which solved most problems even with having more points/tracks on the screen & Locus seems to be more responsive too since more memory is available (of course this is nothing that could be done from the application side & as far as i know changing requires either an /data/local.prop file or an editable system partition)

Currently Locus stopped working relieable on an Nexus S device with Android 2.3.6 - may this be caused by one of the last two updates? (3.1.2 or 3.1.3) Before every crash it seems to try to allocate a rather small amount of memory which leads to an exception (it seems like an network access - but the crash is reproduceable with a phone without data connection). The crash is reproduceable by simply "using" locus pro for a few minutes (1 - 10 minutes, sometimes happens on launch, scrolling over the map, zooming, accessing the GPS status activity, track recording, etc.).

Logcat output is attached, logfiles that are created by locus if the debugging option is enabled are empty 0 byte files.

PS.: The captchas that are used here are really unreadable most of the time ...