Messages

Chrome is worse than IE for me, look at the """".

Sorry, wrong topic. But hé, this 2.14.1.11 is way faster (in zooming and panning) than the official 2.14.1 
I want it.
Will try navigation in the field tomorrow.

Also "on the couch" I can not get rid of track after I activated "test navigation" on it. Deselect all "via menu in Tracks" does deselect but the track stays in the mapscreen. The track is according to the info-box renamed to Navigation.
After a restart of Locus Free test the track is gone from the map screen.

Readability in Google Chrome (on my laptop) is quite bad. Not enough contrast and letters are not sharp. This is the first time a webpage looks better in IE8 than in Chrome.

hPa in the Netherlands too.

Quick New Point button nutzen, geht einfach (aber das weiss Gynta schon )

[EDIT:]

EDIT: hank, still moto defy? Because I received just two crashes with OutOfMemory on defy so I expect it's from you . ....

Yeah, see above and logtxt. Was at home with data connection around 12.00 'o clock.
Defy has got a new battery. Next three weeks off to GR5 and try to see if I got back my 9 to 10 hours of guiding, as I was used to. Will tru 2.13.1.4 also for a day.

Thanks for explaining the height info.

Now trying Locus 2.13.1.4

Start up is as fast, about ten seconds and yes, starts with a white screen that does not bother me. Zooming and panning maybe faster, hard to evaluate.
On zooming out I got the world map (after seperately downloading it and moving it to the right folder).
Got some crashes when zooming in again, probably when map auto load tried to switch to my own vector map again.
Attached log file.
World map is nice but maybe make it a choice when it "kicks in"; I would choose zoomlevel 11 than.

The name field at the top of the screen does not change to World Map and the World Map is not selectable through Maps or Quick Map Switch (probably intended?).

On 2.13.1.4 I get more often the processor 100% warning compared to 2.13.1.

Ok, two questions then:
* does automatic offset, computed from world geoid model need a constant data connection?
* what value is used to show near the cursor when I select dynamic altitude under map - objects & style ?
 This is the one that you can place "right of the icon" or "under the icon".

Maybe there was a change since 2.12.x because first time with 2.13.1 I had to change my manual height correction from -40 to -60 meter to get correct values in dynamic altitude.

I have no gps-fix problem with 2.13.1

Maybe I try 2.13.4 later.

2.13.1 can be recommendend for the Defy  
Fast startup
Fast zooming and panning, even at zoomlevel 9 with the famous Netherlands-hike vector map (without crashing).

I wish I had this one before our last hike (where I was fighting with battery life during guiding) so that I could say something about it, but I keep you posted after our next hike.
Because it is faster it must be better, because less screen on time  

Ok, I am happy.
I am not on 2.12.0 yet because I need Locus seriously next week.

What for a longer time surprised me was that a 1.1 gB Alps map was fluent and never crashing. So I refreshed my Netherlands_hike map (441 mB) through openandromaps.org .

Next I compared my present 2.11.1 with test version 2.12.0.3
To my surpise and happiness I could in both versions now zoom out to level 8 without crashing. It is hard to see if there is a speed difference. 2.12.0.3 is giving more 100% processor signals, so I would say it lets the processor work harder which probably is good.
Both versions are much smoother in panning the map (moving it by sliding) but that would be due to the fresh/better map, I think.  

All in all, I can still recommend Locus, even for an older Defy on Froyo.

@hank: so here is a problem. Again problematic Netherland map ...hope you next device will have a little more RAM (or at least Android 4)

Tried the latest RC version, all the same. Must be the RAM.  Because on my wife's Wolfgang AT-AS40SE  (Amoi N816) with:  1 GHz Dual-Core processor (MTK6577) and 512 RAM and Android 4.0 the same happens.
Ok, that one is faster but also crashes at lower zoom levels.
I am a bit worried here because we (outdoor people) do not walk around with the latest and biggest S4 and HTC one (I believe) because these crash too soon for mechanical reasons and have no battery life.

[Aha, but I had zoomed in above level 10]

Quite small, see attachment.
I did not start up the test version with the kml active. No map overlays, WMS layers

I tried now activating it with Mapquest online map active and everything went normal and speed of Locus was quite normal.
I then changed to the (famous) Netherlands hike vector map and again everything was quite normal, no restarts and speed usable. So far so good. (Aha, but I had zoomed in above level 10).

So I again started the test version with the vector map active and then loaded the kml and then I understood. Because after loading the map zooms out to show all of the track. And I now my device does not manage to show the Neth hike vector map in zoomlevel 8. 2.11.1 is the same and restarts also. So that point is old news.

Learning every day and now I am getting a new phone    (waterproof, small and fast, anyone?)

Now testing 2.11.1.7 Sorry not much time.

1. It is definitely slower. Thing like selecting a track for guiding and displaying it. Rebuilding the vector map when panning etc etc. Switching vector maps close to 20 seconds etc. Even opening the menu.
Mapquest online is fast enough.
2. Activating a kml file from mapitems (with 15 short gpx files and 15 waypoints freezes up Locus and gives a restart of Locus. Added Catlog.
3. Nice sliding panels in Navigation and Guiding.
4. When selecting guiding I occasionally get an extra red heading line (same arrow spacing and line thickness as my normal yellow one, pointing random direction). My normal one is yellow. I tried a screenshot (but offcourse could not reproduce it).

Sorry not to have been helpful earlier but after two nice weekend days of smooth guiding with Locus 2.11.1 this 1.7 is not going to be my companion (or I will buy a new phone, not yet!).