23.5.2013 - Locus 2.11.1.10 - Test version - RELEASE CANDIDATE v.3
[attachment=0:357aeeed]2.11.1.10.apk[/attachment:357aeeed]
news
- small graphics improvements
- fixed scaling of simplified point dots on map at lowet zooms
- fixed rare crash during update a geocaches
- fixed crashes at "information screen" and "log a cache" screen
- some small optimizations
21.5.2013 - Locus 2.11.1.7 - Test version - RELEASE CANDIDATE v.1
news
- added pack (99) of Garmin icons that match Garmin <style> tags in GPX files
- added support for Google Directions, just for personal testing purposes (enable in config.cfg)
- added ability to encode/decode geocache hint
- set default log trackable type to "discover"
- fixed problems with definition of huge maps for download
- fixed many problems with crashes in new Tabs system
- fixed incorrectly computed (and displayed) lines between long-range points
- fixed rare problems with loading geotagged photos
- fixed problems with waypoints lines to parent geocache when POI grouping is enabled
- fixed rare problem with address search
20.5.2013 - Locus 2.11.1.6 - Test version
- this is testing version for a brave testers. I expect that there should be some problems mainly on pages with tabs. I completely changed tabs system. It looks almost same, but code is more elegant and hope that much more bug-resistant. Anyway this is version mainly to debug some problems with specific users ...
17.5.2013 - Locus 2.11.1.5 - Test version
As in previous version, if you'll have time, please test
- new sliding tabs in "GetLocation screen" and "Navigate to" screen - what you think? Useful, waste, needs improvements?
- Geocaching Live in Locus - all communication was rewrote, so just use this version on Geocaching and let me know if there will be any problem with it (mainly with communication with Geocaching Live)
news
- new menu for "Navigation"
- improved system for rendering points (mainly geocaches) in lower zooms (values are fully configurable in config file)
- complete rewrite of all Geocaching Live communication with server. Need perfect testing!!!
- improved "Draw line" (renamed to "Line tools") function (add measuring and intersection - currently only on Sphere, not an ellipsiod)
- all waypoints has now two times - "created" and "last updated"
- computed navigation tracks has now automatically filled altitudes (if srtm data are available)
- changed way how locus keep screen on (removed wake-lock and used more battery friendly method)
- improved "save part of track" function
- fixed problem with remembering track style after creating new folder
- fixed problems with drawing GC Votes on map
- fixed problem with transparency of vector maps as overlay
- fixed problem with logging trackables
13.5.2013 - Locus 2.11.1.4 - Test version
I'll be glad for some reactions on new sliding tabs in "GetLocation screen" and "Navigate to" screen where is now ability to pickup last used locations/tracks
news
- improved system for setting coordinate system
- added ability to use custom coordinate systems defined by EPSG
- many small improvements in Live Tracking (thanks gynta)
- improved listing screen in geoaching screen and enabled swipe in GC screen for testing purpose
- created ability to use "last used" location in GetLocation screen
- improved coloring of tracks on map
- added ability to sort items in pickup-list (more items selected on map at once)
7.5.2013 - Locus 2.11.1.3 - Test version
news
- TTS is now also in Free version!! (so all can now use navigation along tracks or just voice navigation with TTS)
- new system for TTS engine (new "config" screen - display when needed or in settings > global)
- improved design for "navigate to" feature
- ability to reuse already create routes for navigation
- added OSRM navigation source
- various fixed in Live tracking service
- fixed problem with older database conversion
- fixed problems with DateTime picker & timezones
- fixed notification settings for BT GPS
- alpha value (color) now apply also on track colored by speed/altitude etc
- should be fixed some weird vector map rendering
- fixed problems with sun position
- uff any many more ... everybody who had problems, know ...
1.5.2013 - Locus 2.11.1
new version is available
28.4.2013 - Locus 2.11.0
new version is available. Enjoy
Hi Menion,
it's hard to find the altitude manager in the docu as it isn't linked from the pages "GPS and location" and "Sensors". Also new screen shots missing on these pages.
Hi menion,
thanks for the new version :)
During each start of locus this window appears
[attachment=0:3vg1f63x]Screenshot.png[/attachment:3vg1f63x]
i know it is an "old" map, but i need these map for WhereYouGo........... ;)
tommi: I plan to remove links from various places from settings to altitude manager, but till then I'll improve manual tomorow. Anyway you may find "Altitude manager" in list of functions at bottom
balloni: sorry, it's not an intent, it's issue in new version. I'll fix it soon
record_debug_logs=1
..that does not work again.
Quote from: "menion"tommi: I plan to remove links from various places from settings to altitude manager, but till then I'll improve manual tomorow. Anyway you may find "Altitude manager" in list of functions at bottom
Hi Menion, my feeling regarding Altitude manager is that it's more a kind of setting than a kind of function :o
Quote from: "gynta"record_debug_logs=1
..that does not work again.
Yes, here too :-(
I miss a function, that is not in function list, but in "configure right panel". Take photo point. Maybe that I´m blind. Or is this wanted?
hi,
@tommi: altitude manager - isn't is similar with Ant+ manager, Bluetooth manager, Quick switch? They all are just "settings". And maybe more ... anyway I removed this manager from default visible list and it will be only visible as item into right panel. This is also answer to @jusc: yes, it's correct. There is more items that are visible only for right panel settings and not in full functions list. Same it will be with altitude manager.
stuff around a logs :) ... this works only in test versions, but you're correct it should work in same way also for release versions, so "fixed"
Hi menion,
another problem which doesn't exist (?) in earlier versions:
I always have activated center map during recording.
If I send the phone during recording to display off (lock screen) and later to on to see where I am then the map display shows always the last position where I shut the screen off. I think the display should center automatic.
So I have to tap two times on the center button left down.
Hi,
I think that there is a bug in S-JTSK coordinated.
At least I believe you have exchanged X and Y.
Usually Y is displayed first and X below
I believe that
N49° 12,445 E14° 18,908
should be translated to
Y = 763 811,35
X = 1 138 912,76
and you have it reversed.
The numbers should be displayed as negative? I have never seen this before, always positive.
Also there must be some problem in the calculation itself.
Try to edit cache coordinates, switch from WGS to S-JTSK, change the value slightly
and then switch back to WGS. The cache jumps hundreds kilometer away.... :-(
Additionaly I have again hit the problem with the coordinates drop down menu.
When I edit the coordinates of the cache, then the drop down menu is displayed
too far to the upper border4 of the screen and I cannot scroll it down enough
to display all WGS formats.
Zdraví,
Dalibor
@tramp are you sure? Today I around 5 hours ride over city because of change of ID card and some other tasks and tested quite a lot this feature and no problem. Do you have enabled "Hold center method" in settings? (it should work even without it)
@chrabros: issue with problem after editing fixed, thanks. About coordinate values ... check this screenshot from geoportal
[attachment=0:6lundb3t]2013-04-29 16_00_19-Prohlížení - Národní geoportál INSPIRE.png[/attachment:6lundb3t]
if I remember something from school, then negative values are really result of complicated transformations. Anyway I agree that you probably know values for example from Katastr, where Y is always small and both are positive. I'll change it to next version
Quote from: "menion"@tramp are you sure? Today I around 5 hours ride over city because of change of ID card and some other tasks and tested quite a lot this feature and no problem. Do you have enabled "Hold center method" in settings? (it should work even without it)
Yes I was sure. I made two short shopping tracks to test the new version and saw this behavior. I know how it should be.
I will make another test tomorrow if it does not rain.
And the exported tracks have the correct name again.
Thank you for this wonderful app.
editLocus does not actualize its screen during lock screen is active.
So if I look on the display I have to wait the 5 seconds until Locus make its auto center AND if I have at this moment no GPS fix I have to wait another time.
So all is good.
Thank you.
Quote from: "menion"About coordinate values ... check this screenshot from geoportal
[attachment=0:14pai5r8]2013-04-29 16_00_19-Prohlížení - Národní geoportál INSPIRE.png[/attachment:14pai5r8]
Hmm, tak teprve ted jsem konecne zmatenej. Jak muzou v jedny aplikaci mit X a Y prohozeny
a jednou negativni a jednou pozitivni?
Predpokladam, ze negativni hodnoty jsou asi spravne jako vysledek transformace,
ale protoze na celym nasem uzemi vychazeji zaporny, tak se to znamenko asi vynechava, ne?
Tak to by se mozna v Locusu hodilo mit tlacitko na prohozeni hodnot X a Y, abych
si mohl zkusit, co z toho vlastne vypadne. ;-)
Dalibor
Seems like POI group does not work anymore. Please check.
chrabros: don't be confused :) Křovak is really crazy ;)
tuancse: are you sure? I'm just testing it and seems to work correctly. Check it please once more and if it will not work, may you post a screenshot here? It should help to start
Menion: I'm sure that POI GROUPING IS ON. Any zoom does not show Grouping numbers. I'm using offline Google map. Is there any log/debug file I can send to you as screenshot does not help in this case?
Quote from: "tuancse"Any zoom does not show Grouping numbers.
It works here:[attachment=0:3jc1jmop]Screenshot_2013-05-01-10-56-48.png[/attachment:3jc1jmop]
http://docs.locusmap.eu/doku.php/manual ... ation_file (http://docs.locusmap.eu/doku.php/manual:configuration_file)
# GEOCACHING
# --------------------------------
# pack of icons used for geoaching points (default: empty)
geocaching_icon_pack=geocaching_icons.zip
...is default: "empy" or "geocaching_icons.zip"?
I'm also unable to simulate not working POI grouping :/ .. do you have more icons on map at lower zoom? Maybe try more points at once? :)
gynta, default is empty (as written in description). I usually copy my own content of config file, and this is one where I tested some icons, that's all ...
Quote from: "menion"...default is empty (as written in description). I usually copy my own content of config file, and this is one where I tested some icons, that's all ...
So i have now corrected the knowledge base description...
gynta: I know how it works as previous version is ok.
Menion : I have 46 POIs. It used to be ok in the previous version. Anyway, it is really not a big problem. I'll let you know when I figure it out.
Bad news - with this version of Locus is silently crashing on me when moving around the vector map (probably a null pointer in native code?), one second the window is visible, the next I am at home screen. I would suspect insufficient memory issues as in the old times, but the stats around seem to contradict this. No file is created in /sdcard/Locus/logs, and the only set of messages I was able to recover from the log is:
D/dalvikvm(12627): GC_FOR_ALLOC freed 1122K, 26% free 11766K/15820K, paused 178ms, total 179ms
F/libc (12627): Fatal signal 11 (SIGSEGV) at 0x00000000 (code=1), thread 28591 (Thread-948)
F/libc (12627): Unable to open connection to debuggerd: Connection refused
I/Sensors ( 398): mSensors[2]->enable(0, 0)
I/Sensors ( 398): mSensors[2]->enable(2, 0)
I/WindowState( 398): WIN DEATH: Window{41413a28 u0 menion.android.locus.pro/menion.android.locus.core.MainActivity}
I/ActivityManager( 398): Process menion.android.locus.pro (pid 12627) has died.
W/ActivityManager( 398): Scheduling restart of crashed service menion.android.locus.pro/menion.android.locus.core.services.PeriodicUpdatesService in 5000ms
D/Zygote ( 100): Process 12627 terminated by signal (11)
W/WindowManager( 398): Force-removing child win Window{4143b2a0 u0 SurfaceView} from container Window{41413a28 u0 menion.android.locus.pro/menion.android.locus.core.MainActivity}
W/ActivityManager( 398): Force removing ActivityRecord{40e7fe98 u0 menion.android.locus.pro/menion.android.locus.core.MainActivity}: app died, no saved state
W/WindowManager( 398): Failed looking up window
W/WindowManager( 398): java.lang.IllegalArgumentException: Requested window android.os.BinderProxy@412fd800 does not exist
W/WindowManager( 398): at com.android.server.wm.WindowManagerService.windowForClientLocked(WindowManagerService.java:8171)
W/WindowManager( 398): at com.android.server.wm.WindowManagerService.windowForClientLocked(WindowManagerService.java:8162)
W/WindowManager( 398): at com.android.server.wm.WindowState$DeathRecipient.binderDied(WindowState.java:932)
W/WindowManager( 398): at android.os.BinderProxy.sendDeathNotice(Binder.java:433)
W/WindowManager( 398): at dalvik.system.NativeStart.run(Native Method)
I/WindowState( 398): WIN DEATH: null
Any idea what's going on? Or is there a way how to get more info for you if the problem happens again?
omg, this happen with 2.11.0 or with new 2.11.1?
I still don't see the update, so to make it clear - this happens with 2.11.0, there is no update to 2.11.1 visible for me in Play Store yet.
I just uploaded new version so it will take some time ...
Fine. In vector maps was one issue. I had incorrectly synchronized one HashMap, that may cause such problems. You'll see what will do new version tomorrow ... otherwise crash error is really "crazy" :/
fine, so seems that all works fine in new version. At least no serious problem. Unfortunately I'll have quite full May (moving from one flat to another, some family affairs and some more) so it will be little bit slower now. just warning for you.
Anyway ... is there something I promised to do and it's not yet completed? Current version (and April at all) was mainly in name of "Altitude manager" and vector maps speed improvements. I would like in May to focus on navigation, track editing and all these stuff around Navigation & Guiding. We all know that it works, but it's too complicated. So I would like mainly to simplify it and mainly editing of tracks make faster. Nothing against this? Believe no :)
EDIT: btw. has anyone tried last parameter in configuration file? Just some test function ;) (need elevation files for map area you want to test)
Quote from: "menion"EDIT: btw. has anyone tried last parameter in configuration file? Just some test function ;) (need elevation files for map area you want to test)
Yes, I tried this.
But what does the gray parts on a vector map mean?
They do not mark the summit or the steepest slopes, I think they are randomly :-(
What elevation files do I need and where to get from and where to save them?
I have in srtm two hgt- and one DAC-files.
randomly? I'm sad :) it should be hillshading ... hmm it looks better in some hilly areas
Quote from: "menion"randomly? I'm sad :) it should be hillshading
What should I see?
Hillshading: the whole hill, one side only or the steepest side? Should the summit be the darkest part?
I am using your maps.
Can you show me an example (perhaps a bavarian hill)?
And my question: which elevation files do I need?
Quote from: "menion"...EDIT: btw. has anyone tried last parameter in configuration file? Just some test function ;) (need elevation files for map area you want to test)
SURE :D
but it overwrites some infos...
I wanted to create screenshots but gynta was faster :). Hmm but missing info is really weird. Because it's just semitransparent shade that is drawn after all is already on place.
And tommi, needed altitude files are probably these you already have. HGT files in Locus/data/srtm directory
Im using ALP files from: http://www.viewfinderpanoramas.org/dem3.html#alps (http://www.viewfinderpanoramas.org/dem3.html#alps)
Hi,
there is some little problem with geocache logging in version 2.11.0
Even though I have "Alway log offline" whenever I try to log a cache,
it offers me a menu where I can choose between logging online and offline.
Dalibor
Hello Dalibor, please update to 2.11.1, it's solved there
Regarding hillshading: I've learnt that it is typically drawn as light coming from top left corner. I've got the feeling in the area I had a look on that this is not the case, it seems to be more from somewhere in southern direction.
Menion, could you explain how it's done in Locus?
please take this really as an ... how to say, feature for fun now. Anyway it's fast and it's doing something, which is good start :)
direction is currently defined from south, east. It's best what I was able to create after some testing. Problem is again missing OpenGL rendering. From some angles, android has problems to draw semi-transparent triangles and draw instead of that only completely white triangles. So don't expect too much from it now. I was excited when it started to work, but this is huge limitation and I'm not sure, I will be able to create now nice looking hillshading ... we'll see
I noticed strange zooming of vectormaps in lower zoomlevels 0-8
# after changing the map - locus ignores this
# zoom in - tiles are not loaded
-> see clip: https://www.dropbox.com/s/i2tsuf5m33pin ... 2013_0.mp4 (https://www.dropbox.com/s/i2tsuf5m33pinkb/clip__Mai_02_2013_0.mp4)
btw.
autochange vector map is off
Ok, now on 2.11.1. Sorry for not testing last weeks; too busy just using Locus and other stuff. :D
1. Vector maps are definitely faster now (compared to 2.10.2).
2. Auto load vector maps does not work at all.
3. Quick map switch does not do proper sorting on distance; even with GPS OFF (via Locus) it shows an order based on my real position. Meaning if I search a place in another country, the cursor goes there but the "quick map switch screen" shows two maps off my present position on top of the list.
4. The sun position in the compass screen is about 37 deg off
5. When zooming in or out I have occasionally one or more white tiles. Can't find a pattern there. Usually some zooming or panning "wakes them up".
Also on 2.11.1, vector map switch works fine for me.
But I also see white tiles on the map, also the quick map switch button stays in the upper left corner. I saw this mainly when "jumping around" on the map. After zooming in/out the white tiles disappear, also does the quick map switch button.
The speed of the vector maps is amazing fast for higher zoom levels!
2. Auto load vector maps does not work at all. EDIT: IT WORKS SOMETIMES.
3. Quick map switch does not do proper sorting on distance. EDIT: IT DOES SOMETIMES.
I have the impression this has to do with me having a couple of older V2 maps mixed with V3 maps. Will test later.
EDIT
Ok, the problem is with the couple of V2 maps I still have. I will replace them by newer V3 maps.
hi guys,
gynta, thanks for reports. Main problems should be fixed now
mambo & henk: I do not saw white tiles on vector maps. Is this happening only on a raster maps? Have to check it
henk: older V2 maps may cause problems. They do not use styles, they're not optimized on multi-core rendering, they are generally not anymore supported and updated. Compare to V3 implementation in Locus, they're ... cannot find decent word :). And Quick switch maps ... also problem with vector maps or also a raster?? If only a vector maps, this should again be a problem of V2 system
Quote from: "menion"mambo & henk: I do not saw white tiles on vector maps. Is this happening only on a raster maps? Have to check it
It happens with vector maps here. Mainly after jumping around across borders of vector maps. As henk writes, the white tiles disappear after zooming in/out.
[attachment=0:378dk9hd]uploadfromtaptalk1367721090723.jpg[/attachment:378dk9hd]
Gesendet von unterwegs mit Tapatalk 2.
Quote from: "mambofive"Quote from: "menion"mambo & henk: I do not saw white tiles on vector maps. Is this happening only on a raster maps? Have to check it
It happens with vector maps here. Mainly after jumping around across borders of vector maps. As henk writes, the white tiles disappear after zooming in/out.
Gesendet von unterwegs mit Tapatalk 2.
Similar problem here. Rendering of neighboured vector map seems to be somehow laggy. Zooming helps as well as moving around more. Sometimes 3/4 of the screen remains empty.
Hi menion,
since the last versions track saving after stop recording has become very very slow, my first thought is always that Locus has a FC :-(
And the fill altitude is very slow too.
This all was much faster before.
tramp, did you use last published version? Maybe check if you don't have enabled logging. If there is some forgotten logging on some critical place, it should slow down a lot. If not, log is always welcome, as they may be some clue
EDIT: fine, new test version ...
Quote from: "gynta"I noticed strange zooming of vectormaps in lower zoomlevels 0-8
# after changing the map - locus ignores this
# zoom in - tiles are not loaded
...works better (i'm testing yet) in v2.11.1.3 - Test
Quote from: "menion"tramp, did you use last published version? Maybe check if you don't have enabled logging. If there is some forgotten logging on some critical place, it should slow down a lot.
It was v2.11.1
I attached the logfile.
I had no time to test 2.11.3: my wife is in hospital and gets today some bypasses and a mitral valve :-(
"... since the last versions track saving after stop recording has become very very slow ..."
I can not confirm this with 2.11.1 (it was a short track recording).
Quote from: "Henk van der Spek""... since the last versions track saving after stop recording has become very very slow ..."
I can not confirm this with 2.11.1 (it was a short track recording).
What is short?
With a 2 hours track: saving ~15 secs and fill altitude ~25 secs.
hope your wife is fine ...
to topic. Long storing times on two different functions mean only one this. Something is wrong with storing points into database. Didn't you changes something, SD card, location of Locus etc, last days? Also check for sure you have disabled logging ...
Quote from: "menion"hope your wife is fine ...
to topic. Long storing times on two different functions mean only one this. Something is wrong with storing points into database. Didn't you changes something, SD card, location of Locus etc, last days? Also check for sure you have disabled logging ...
To my wife: thank you but I don't know till now.
I have nothing changed only Locus Map.
Logging was always on (even with earlier versions) so I will test without. Did you see something in my logfile?
The track database has 24 MB.
@tramp: short is 900 meters and 75 points only.
Guys excuse me now for two, max three days. We're just moving to one flat outside of Prague, so I'll be for a while out-of-service :). In case of problems, Peter is still here. Have a nice evening ...
Sent from my GT-N7100 using Tapatalk 2
Good luck with moving!
Sent from my SGSII CM10 with Tapatalk 2
Quote from: "tramp20"Hi menion,
since the last versions track saving after stop recording has become very very slow, my first thought is always that Locus has a FC :-(
And the fill altitude is very slow too.
I think I found the cause:
3 weeks ago I installed Dr.Web (antivirus) and I seems that this program checks the database storing (idiotic).
After deinstalling my tracks are now stored again in 3-5 secs.
Thanks to all and to Gynta too.
Hi menion,
the handling at stopping a track recording could be improved IMO:
1. If I tap on stop Locus should show "Stopped" instead of "Paused".
2. I I accept or change the filename Locus should show "Saving" instead of nothing (this could last several seconds and I get a little panic).
3. Why is the recording symbol in the Android statusbar always visible after stopping a record? It should disappear earlier.
In the sun I see always only some important hints but not all without eye glasses so Locus should be clear :-)
heh it really scan databases after every change? funny ... good you found a problem. I just released new test version and forget to check suggestions you have for track record. So next version ...
Quote from: "menion"13.5.2013 - Locus 2.11.1.4 - Test version
- many small improvements in Live Tracking (thanks gynta)
you're welcome!
km/h gives me now (eg) a "23.582594084739685" string
and also Altitude "161.436039555364"
I think that's too much :mrgreen:
Thank you for this nice (test)update.
I will also improve the live tracking test service - next weekend...
Quote from: "menion"I just released new test version
Thank you.
Today no problems with Locus on a 6 hour MTB tour :-)
news
- improved system for setting coordinate system
I see the changed settings menu but in top panel the display of WGS coordinates is two strange strings. If I instead start latest Locus Pro the display for WGS is ok.
Quote from: "tommi"...in top panel the display of WGS coordinates is two strange strings.
don't found the problem - u have a screenshot?
no, don't have it.
But I found the reason: The format for WGS wasn't properly configured (none of the 3 possible formats was activated) and therefore the top panel coordinate display was something like 32U blablanumber.
=> The problem is that (likely due to the changed coordinate system) by default no format was configured.
as usually I forget to fix last issues in this topic before releasing new test version :). Thanks tommi, I'll fix it to next test version, so in this new 2.11.1.5 is still this problem ...
"Line tools" in czech version isn't translate.
In line tools windows in czech version isn't translate the title, subtitle "Intersection" and button "Compute intersection".
If I use "Compute intersection" ... select start point, end point from map. Tap on the "Compute intersection" button and ... nothing. No info, no draw line. Nothing. I see map too. Anything wrong?
translation is already done before release. in these versions are new texts only in english ...
line tools - intersection > hmm that's what I expect :). First tab define first line, second tab second line. So if you want to compute intersection, you have to define both lines ;). I'll rather give first line definition also into second tab, to make it clear, right?
Quote from: "menion"2.11.1.5 - Test version
- new sliding tabs in "GetLocation screen" and "Navigate to" screen - what you think? Useful, waste, needs improvements?
old / new
[attachment=1:1lfw4sh6]nav.png[/attachment:1lfw4sh6]
is it impossible to use the same system (see marked area)?
[attachment=0:1lfw4sh6]pick.png[/attachment:1lfw4sh6]
discussion about line intersection is here https://getsatisfaction.com/locus/topic ... n_function (https://getsatisfaction.com/locus/topics/line_intersection_function)
and gynta ... I was thinking about it quite a lot. Both headers for tabs are used widely in Android and non is preferred. Style used in maps/data is good for more then two tabs. But it do not look so elegant I think. This system on second side looks nice if there are just two max three items. Hmm hard to say ... I was also looking on system used in new Google Play application, where is also small strip below tabs ... truth is that if all headers use same style, it should looks best ... damn ... I'll be thinking about it once more :)
Quote from: "tommi"no, don't have it.
But I found the reason: The format for WGS wasn't properly configured (none of the 3 possible formats was activated) and therefore the top panel coordinate display was something like 32U blablanumber.
=> The problem is that (likely due to the changed coordinate system) by default no format was configured.
Yes you are absolutely agree with you!!!
Quote from: "menion"20.5.2013 - Locus 2.11.1.6 - Test version
...I completely changed tabs system. It looks almost same, but code is more elegant and hope that much more bug-resistant.
looks good now..
Quote from: "tramp20"Hi menion,
the handling at stopping a track recording could be improved IMO:
1. If I tap on stop Locus should show "Stopped" instead of "Paused".
2. If I accept or change the filename Locus should show "Saving" instead of nothing (this could last several seconds and I get a little panic).
3. Why is the recording symbol in the Android statusbar always visible after stopping a record? It should disappear earlier.
In the sun I see always only some important hints but not all without eye glasses so Locus should be clear :-)
Hi menion,
did you remember this suggestions?
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!).
Hello Henk,
thank you for a test. You sometimes wrote "sorry", but this is really not a necessary. I should be sorry for problems and not just for testing!!
Anyway slowness of app is probably because whole log is completely full of some OutOfMemory problems. Seems that since you finished import, Locus enlarge to 30MB (which is limit on your device) and all probably started to be un-usable. How long are tracks you loaded? These 15 tracks completely filled your memory, is this possible? Or you're using some map overlays, WMS layers?
I'm sure that without tracks, it should works fine. Mainly because there were no radical changes that should have influence on app speed.
@tramp: I was reading it immediately you wrote it. Then I started checking it and found that function "save part" that is used for storing just a current recorded part do not work. So I started to fix it (and improve a little) and after that I completely forget on your post, sorry ... :)
- 1. so, why "stopped", when record is really just paused? Till you store record, track is really just paused, so when you cancel "save" dialog, recording will continue
- 2. ah I know ... there is a while (a longer for longer tracks) where I also sometimes think if all works fine on background or not :)
- 3. by stop is mean moment, when track is stored in database. Anyway since you press "OK" in "save" dialog, in this moment, track record notification should be removed from notification bar
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 :D (waterproof, small and fast, anyone?)
The GC listing tabs formatting is much better in 2.11.1.4+ the text and pictures aligns correctly now compared to the current release.
GC swiping between tabs works great. The only minor issue is larger pictures require sideways scrolling before the swipe can work. Would it be possible to resize pictures to fit the screen size at the default zoom level?
Why does the image tab load by default between listing and logs? Instead of;
| Information | Listing | Logs | Trackables | Images |
Shouldn't the default hint value be encoded instead of decoded?
App crashs when trying to log a GC...?
I really like the POI icon resizing at zoom 12, much less cluttered!
Thanks for fixing POI grouping parking waypoint group lines I don't use grouping but that bugged me :)
Quote from: "menion"@tramp: I was reading it immediately you wrote it. Then I started checking it and found that function "save part" that is used for storing just a current recorded part do not work. So I started to fix it (and improve a little) and after that I completely forget on your post, sorry ... :)
- 1. so, why "stopped", when record is really just paused? Till you store record, track is really just paused, so when you cancel "save" dialog, recording will continue
Hi,
it is irritating because the two buttons are side by side:
if I press Pause I see "paused".
If I press Stopp I expect to see "stopped" so I am always in doubt that I have pressed the right button.
It could be made better :-)
The silent crash in native code still persists in 2.11.1. I was hoping it was fixed in 2.11.5 since it did not happen for some time, but after extensive moving around the borders when looking for broken woods polygons, it happened as well:
D/dalvikvm(12415): GC_CONCURRENT freed 1205K, 29% free 11834K/16656K, paused 6ms+16ms, total 219ms
D/dalvikvm(12415): WAIT_FOR_CONCURRENT_GC blocked 147ms
F/libc (12415): Fatal signal 11 (SIGSEGV) at 0x00000000 (code=1), thread 31254 (Thread-12854)
F/libc (12415): Unable to open connection to debuggerd: Connection refused
I/ActivityManager( 409): Process menion.android.locus (pid 12415) has died.
W/ActivityManager( 409): Scheduling restart of crashed service menion.android.locus/.core.services.PeriodicUpdatesService in 12632ms
W/InputDispatcher( 409): channel '40d4ef78 menion.android.locus/menion.android.locus.core.MainActivity (server)' ~ Consumer closed input channel or an error occurred. events=0x9
E/InputDispatcher( 409): channel '40d4ef78 menion.android.locus/menion.android.locus.core.MainActivity (server)' ~ Channel is unrecoverably broken and will be disposed!
D/Zygote ( 100): Process 12415 terminated by signal (11)
Is there a way how to debug it? Maybe find a way to run debuggerd? It looks like a null-pointer to me (e.g. failed allocation), but it's hard to say.
@eccentric: thank you for perfect report. Problems should be fixed now. Only remain
- resizing images: only way is to search through page code and for <img> tags and change it's parameters. We'll see how this will work and in worst case, I'll try this ..
- encoded hint: hint is by default encoded on web page, just not to see it. But here, you have to press "hint" button, so I think there is no need to have it encoded by default
- images tab: these images are usually just images from listing on separate page. I think that it make sense to have them right next to listing
@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)
@tramp20: sorry, still cannot agree
button pause: display "Paused" and nothing more happen
button stop: display "Paused" and display full screen window for storing a tracks.
it's huge different so in case you tap on wrong button, you still should see what happen. Also track is really paused till you close this saving dialog
@pavel: it's probably same problem as before right? I always hate if there is any problem in native code as I really have problems with fixing such issues (if it's even possible). I'll check it, thanks
... btw. RC version for test in first post. If someone has some serious issues that are not fixed in this version (except Pavel :) ), this is last chance
Quote from: "menion"@pavel: it's probably same problem as before right? I always hate if there is any problem in native code as I really have problems with fixing such issues (if it's even possible). I'll check it, thanks
Yes, it is the same problem. If I find a way how to run debuggerd internally on the device (CM 10.1) and get more info out of it, I will let you know.
OK, I found out why the debuggerd is not running and include the trace [attachment=1:14clvs4l]native-crash.txt[/attachment:14clvs4l] when the problem happens. Hopefully it will help you diagnose the problem.
By the way, I remembered another issue I should mention - sometimes during the startup (of the current Pro version), i see "null" in the loading dialog, see [attachment=0:14clvs4l]null-load.png[/attachment:14clvs4l]
It happens for a few versions back, but not very often.
Quote@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.
even on A4.0 with 512 RAM Locus crash with Netherland map? Damn, seems that I'll really have to check it more carefully and find some source of troubles.
Anyway topic is closing as new version is out. Thanks all for amazing support and help with debugging! Enjoy Locus 2.12.0 ;)