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 ...
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 ...