[APP] - version 2.13.X+ (updated 1.8.2013)

[Menion]

so defined speed in configuration file is useful for places where is needed a speed to compute some values. It should be voice commands (yes, they should be hear in test version also with value 0, because for navigation purpose I change 0 to some minimal value 1m/s). Anyway if you set value to 20 (so around 70km/h), you should hear commands as you should probably hear in card, I mean in similar distances. This value is also useful for some time to target checks etc...

Anyway I changed it's behaviour so voice commands with this speed will work also in public version (not just test) but only in case, this parameter will not be a "0".

To animations ... they should be disabled in your device for all apps at once. I personally like some simple animations and till now, no body complain . And if Bucky Kid think it's slower now, it should be because you have more maps, more wms services? Anyway no dramatical change was done in map manager that should slow down loading of this screen

[Bucky Kid]

Anyway no dramatical change was done in map manager that should slow down loading of this screen

That's right It's not dramatic slow down. But for quick switching between maps, could you please add the Quick map selector panel to the long press menu for Full map selector icon in the upper right  corner? For some reason it opens about 1s faster and shows all what I need. I.e. yet more I'd like the upper right corner icon to show quick map selector on short press and additionally offers full map selector on long press or in long press menu (because in most cases quick map selector is fully satisfying)

[Menion]

uff finally to bed. Bucky, I was fighting till now with some bugs in android, but seems to successfully completed task. So in next version will be loading and mainly handling of map screen and also data screen much faster. It will have no effect on loading of points/tracks/maps etc. just user-experience from work with these screens should be much better now ... and good morning to all

[Bob Denny]

Thank you for your work!

-- Bob

[tommi]

Hi Menion,
had time using Locus car navigation and Guiding (when too far away from track) today and want to report few problems.
In general Locus was - as always - a loyal and faithful helper!

Navigation issues:
- 1 crash after about 2 hours (suddenly I saw the homescreen instead of Locus), sorry no crash log available. I know this doesn't help but I think I should let you know
- Navigation screen: I switched off display (I didn't switch off navigation of course) in order to charge battery because it was low. Later I switched it on again but the display wasn't updated (the navigation element showed an old turn, the distance to this turn wasn't updated, the car symbol wasn't at the center of the screen but almost outside the screen). I think the whole screen needs an immediate refresh after switch on display. I think there was no such problem in Locus maybe a year ago.

Guiding issues:
- I used a track in reverse direction. The info graph is displayed from original start to end from left to right, so far ok. But the marker for the current position is running also from left to right => wrong, either graph or marker need to run from right to left.
- A bad german sentence in the "clock" guiding, I'll discuss with Gynta first in the German translation thread, maybe no problem in English.
In general a nice feature I don't want to miss!
*edit*: After discussion with Gynta it seems that there's no separate sentence for this "x meters on y hours". The german text currently is "x Meter von y Stunden" but it should be e.g. "x Meter Richtung y Uhr".

[Menion]

new version for test in first post ...

@tommi: I have navigation and pressure sensor in mind ...

[tommi]

new version for test in first post ...

@tommi: I have navigation and pressure sensor in mind ...

and reported guiding issues as well?

[tommi]

Crash when using Locus 2.13.1.1 or 2.13.1.2 in VM: When I select a vector map there's no reaction for a long time and later Android asks if I want to end Locus.
This problem does not occur with Locus Pro 2.13.1, it loads the same vector map in my VM environment successfully.

This seems to be the relevant logcat snippet:

Code Select Expand

07-12 18:52:07.035 I/ActivityManager(280): Displayed menion.android.locus/.core.gui.maps.MapManager: +224ms
07-12 18:52:07.139 D/dalvikvm(4784): GC_FOR_ALLOC freed 1169K, 10% free 12084K/13319K, paused 80ms, total 81ms
07-12 18:52:10.227 W/audio_hw_primary(92): out_write() limiting sleep time 46802 to 39909
07-12 18:52:10.247 D/dalvikvm(4784): Trying to load lib /data/data/menion.android.locus/files/libjsqlite.so 0xa6856a40
07-12 18:52:10.263 E/dalvikvm(4784): The lib may be ARM... trying to load it [/data/data/menion.android.locus/files/libjsqlite.so] using houdini
07-12 18:52:10.267 D/houdini (4784): [4784] Loading library(version: 2.0.5.42475 RELEASE)... successfully.
07-12 18:52:10.279 D/dalvikvm(4784): Added shared lib /data/data/menion.android.locus/files/libjsqlite.so 0xa6856a40
07-12 18:52:10.279 E/dalvikvm(4784): Calling NativeMethodHelper for JNI_OnLoad
07-12 18:52:10.279 E/dalvikvm(4784): Version returned : 65538
07-12 18:52:10.279 W/System.err(4784): Unable to load sqlite_jni: java.lang.UnsatisfiedLinkError: Couldn't load jsqlite: findLibrary returned null
07-12 18:52:10.279 V/dalvikvm(4784): +++ not scanning '/system/lib/libwebcore.so' for 'internal_init' (wrong CL)
07-12 18:52:10.279 V/dalvikvm(4784): +++ not scanning 'libnativehelper.so' for 'internal_init' (wrong CL)
07-12 18:52:10.279 V/dalvikvm(4784): +++ scanning '/data/data/menion.android.locus/lib/libproj.so' for 'internal_init'
07-12 18:52:10.279 V/dalvikvm(4784): +++ calling dlsym(Java_jsqlite_Database_internal_1init)
07-12 18:52:10.279 V/dalvikvm(4784): +++ calling dlsym(Java_jsqlite_Database_internal_1init__)
07-12 18:52:10.279 V/dalvikvm(4784): +++ scanning '/data/data/menion.android.locus/files/libjsqlite.so' for 'internal_init'
07-12 18:52:10.279 V/dalvikvm(4784): +++ calling dlsym(Java_jsqlite_Database_internal_1init)
07-12 18:52:10.279 V/dalvikvm(4784): Found 'Java_jsqlite_Database_internal_1init' with dlsym
07-12 18:52:10.283 V/dalvikvm(4784): +++ not scanning '/system/lib/libwebcore.so' for 'internal_init' (wrong CL)
07-12 18:52:10.283 V/dalvikvm(4784): +++ not scanning 'libnativehelper.so' for 'internal_init' (wrong CL)
07-12 18:52:10.283 V/dalvikvm(4784): +++ scanning '/data/data/menion.android.locus/lib/libproj.so' for 'internal_init'
07-12 18:52:10.283 V/dalvikvm(4784): +++ calling dlsym(Java_jsqlite_FunctionContext_internal_1init)
07-12 18:52:10.283 V/dalvikvm(4784): +++ calling dlsym(Java_jsqlite_FunctionContext_internal_1init__)
07-12 18:52:10.283 V/dalvikvm(4784): +++ scanning '/data/data/menion.android.locus/files/libjsqlite.so' for 'internal_init'
07-12 18:52:10.283 V/dalvikvm(4784): +++ calling dlsym(Java_jsqlite_FunctionContext_internal_1init)
07-12 18:52:10.283 V/dalvikvm(4784): Found 'Java_jsqlite_FunctionContext_internal_1init' with dlsym
07-12 18:52:10.283 V/dalvikvm(4784): +++ not scanning '/system/lib/libwebcore.so' for '_open4' (wrong CL)
07-12 18:52:10.283 V/dalvikvm(4784): +++ not scanning 'libnativehelper.so' for '_open4' (wrong CL)
07-12 18:52:10.283 V/dalvikvm(4784): +++ scanning '/data/data/menion.android.locus/lib/libproj.so' for '_open4'
07-12 18:52:10.283 V/dalvikvm(4784): +++ calling dlsym(Java_jsqlite_Database__1open4)
07-12 18:52:10.283 V/dalvikvm(4784): +++ calling dlsym(Java_jsqlite_Database__1open4__Ljava_lang_String_2ILjava_lang_String_2Z)
07-12 18:52:10.283 V/dalvikvm(4784): +++ scanning '/data/data/menion.android.locus/files/libjsqlite.so' for '_open4'
07-12 18:52:10.283 V/dalvikvm(4784): +++ calling dlsym(Java_jsqlite_Database__1open4)
07-12 18:52:10.283 V/dalvikvm(4784): Found 'Java_jsqlite_Database__1open4' with dlsym
07-12 18:53:16.443 I/InputDispatcher(280): Application is not responding: Window{a6b3c578 menion.android.locus/menion.android.locus.core.gui.maps.MapManager paused=false}.  It has been 5005.6ms since event, 5005.4ms since wait started.  Reason: Waiting because the touched window has not finished processing the input events that were previously delivered to it.
07-12 18:53:16.443 I/WindowManager(280): Input event dispatching timed out sending to menion.android.locus/menion.android.locus.core.gui.maps.MapManager


[gynta]

after first quick view:

..map of the world as vector map (extract attached file into Locus/mapsVector

good idea - 14MB are not so bad - but the installation has to be easier for beginners.
please make it possible to download and install the map inside Locus in one step. (eg. as a link inside vector map manager)

...screen on/off ...by proximity sensor.

I have to practice (a lot) - but it works...

fixed small problems in merged compass & sat screen

eg delete the pich n roll label

[Menion]

@tommi: yes nad thanks for log, it's a problem with missing native lib that will be in next version
@gynta: don't worry about world map, it's here just for testing. installation will be automatic. Proximity sensor: it's a first version . Anyway there is also useful method, so Locus may now turn on display when you navigate or guide etc. I'm sure it will be very very useful. And "pitch, roll" - this seems to be best solution

[ta-ka]

I'm sending some reports.

1.  TTS voices
Is "voice simulation" enabled in the test version 2.13.1.2?
It  worked in the last test version 2.12.2.10 but it seems not now. So it's difficult to test.

2. compass & sat screen
I think it's strange that "Compass On/Off" button appears only in sat screen.

3. gesture
I confirmed that screen turn on/off by gesture properly works on my device (SGNoteII).

4. own web loader for login
login to Geocaching Live and OSM gives "Unexpected Problem!".
(I haven't created account on them yet.)

5. highlight of simplified dots on map
It looks better than before. I like this.

[tommi]

Please improve this text:
https://www.dropbox.com/sc/49sjirkmownid38/gB-Y6zB33E

[gynta]

Is "voice simulation" enabled in the test version 2.13.1.2?

-> viewtopic.php?f=26&t=3227&p=22109#p22109
but i also have no success

I think it's strange that "Compass On/Off" button appears only in sat screen.

+1

[Menion]

new version: fixed test versions problems with OAuth login screen

@ta-ka: thanks!
1. as I wrote in TTS topic, try to set speed parameter in configuration file. Sorry I do not mention this

2. I'm still not sure about these buttons. On smaller device, there's very low space so I have to think about it

3. it's not still best. Mainly it took too long to see if something happen. It now works in a way, that Locus "record" for two seconds what you do before sensor and then do some action. I now reduced this to 1.5s, so we'll see

4. thanks, fixed

@tommi: ah here it is . I rather removed this completely (text) then writing some nonsense

[tommi]

@tommi: ah here it is . I rather removed this completely (text) then writing some nonsense

I have no clue what you are talking about. You removed the "x Meter von y Stunden"? Can this now be properly replaced with the new TTS system?