25.6.2013 - Locus 2.12.2.10 RC! - test version
Warning: this version move settings for "Live tracking", "Quick add point", "WMS maps" to different directory!! Do not use this version if you also want to use current public version of Locus with these features!
Main speed and bugfix optimizations
[attachment=0:2zku2lmt]<!-- ia0 -->2.12.2.10.apk<!-- ia0 -->[/attachment:2zku2lmt]
news
- improved "Always screen on" settings
- improvements of translation
- fixed problem with start of navigation
- small fix in downloading of one-level online map
- fixed some crashes
- small improvements in data screen
- speed improvements in moving a map with lot of items
- some improvements in speed of locus start
21.6.2013 - Locus 2.12.2.8 RC! - test version
Planned release is on Wednesday of next week. So four days on testing. Any problems and ideas you find, please discuss. I'm always offering possibility to change <!-- s;) -->;)<!-- s;) --> Have a nice weekend
news
- another bunch of speed improvements (map handling & data, mainly points, loading)
- added "Always screen on" to quick switch
- added ability to change icons of more points at once (in data screen)
- added prevention to open more points dialogs at once
19.6.2013 - Locus 2.12.2.7 - test version
news
- dramatically improved POI filter
- improved speed of removing "before" and "after" parts of tracks
- tapped (selected) items on map, now in list display last update time and it's also possible to sort them by time
- fixed problems with OSM notes
- fixed problem with main menu slide & screen lock feature
17.6.2013 - Locus 2.12.2.6 - test version
main changes except speed improvements on various places, is new system for data screen/item visibility - opinions are welcome.
news
- again new system for data screen, hopefully final ... who find what's changed? <!-- s:) -->:)<!-- s:) -->
- added support for display and sort by favorites points (geocaching fav)
- fixed problem with re-writting icons when choosing folders
- fixed problems with Backup manager (mainly restoring items)
- improved items count formatting in data screen
- added notification when pressure sensor do not work correctly
- some small fixes
15.6.2013 - Locus 2.12.2.5 - test version
news
- since previous 2.12.2.4, 2.12.2.5 just a few bugfixes and improvements mainly in "Data screen"
- merged "Item visibility" feature with data screen!
- better support for mouse scroll zooming
- fixing problems with centering new items coming from API
- fixes in sorting items by created and last updated date
- removed OSM Bugs service, implemented OSM Notes service
- improved recalculate feature (navigation) so now it's as background task without loading dialog
- improved backup system
- fixed problem with disappearing guiding when using live map
- many many many speed improvements - vector maps, map items, loading/unloading of items in folders (huge difference here) and also some memory optimizations
- fixed some small baterry problems (widget, notifications, wake locks on GPS)
5.6.2013 - Locus 2.12.1
not much reactions here even when almost every test version had more then 50 downloads. Nevermind, it gave me at least valuable feedback, that all major features works fine. So thanks all for a help, mainly "bug-fix" version is now heading to Google Play & AndroidPIT
4.6.2013 - Locus 2.12.0.5 - RC!!
main question: what you think about "POI alert, Parking, Navigate to" features on A4.0+? Is this full-screen system better? Also if this function is called from main menu, this menu remain open if you cancel this function. Opinions are welcome ...
news
- switched old ANT+ system to new version (require service 4.0+)
- fixed some problems with map downloading and centering
- added ability to define folders used in POI alert
- big change in background work with GPS. Now should better handle system on/off state (anyway GPS on/off etc. really need testing)
- added support for zoom in/out by mouse scroll
- many many small fixes
2.6.2013 - Locus 2.12.0.4 - test version
main question: what you think about "POI alert, Parking, Navigate to" features on A4.0+? Is this full-screen system better? Also if this function is called from main menu, this menu remain open if you cancel this function. Opinions are welcome ...
news
- improved design of POI alert and Navigate to screens (mainly full-screen)
- fixed problem with map picker
- fixed incorrectly computed daily temperatures
- improvements in hillshading
- few small fixes
29.5.2013 - Locus 2.12.0.3 - test version
purpose of this version is to prepare really amazing new version for June (release expect at start of next week). So here are no new extra news, just a bugfixes
news
- zoom lock now remember last settings
- guiding on cache now disabled after logging
- "parking" feature just for testing as full screen window (not as dialog)
- fixed crashes in navigation menu
- fixed crashes when repeatedly opened Quick map switch
- fixed incorrectly send Geocaching logs
- fixed incorrect uploaded "pre-filled" texts (uploaded as field notes)
- fixed problems with parsing GLWPT nmea messages
- fixed some rare problems with older tracks databases
28.5.2013 - Locus 2.12.0.2 - test version
news
- new system for main menu - now using system from Google itself, so recommended <!-- s:) -->:)<!-- s:) -->. Anyway may be bugged ...
- optimizations on track altitudes
- moved declination from sat screen to compass screen
- improved parking function design
- attempt to fix slow vector map rendering
- fixed publishing a field notes
- some small fixes
26.5.2013 - Locus 2.12.0
new version is available. Enjoy
Hi Menion,
updated version 2.12 today, after that did a bike tour and unfortunately noticed, that one of my favorite features of Locus Pro seemed to be gone: the possibility that the device display gets dimmed after a while and gets to full lightness again just by touching it. It was in the general options menue. It was a very useful feature because it saved a lot of battery. Why has it disappeared and - please - can you put it back again?
talking about this missing setting?
a good question.. ;)
Yes Menion, this is exactly what I mean. It's gone. Can you bring it back?
Quote from: "joa"Yes Menion, this is exactly what I mean. It's gone. Can you bring it back?
confirmed, it's gone :shock:
Hello,
with today's update, Locus gets very very slow on my phone. The start of Locus needs much longer and especially the loading of the map needs about 30 seconds each time i move or zoom the map (before it was about 1 or 2 seconds). also the opening of the menus is quite slow.
With this new version, Locus is almost not use able.
Parallel to the updated pro version I have an older free version on the phone, which works still normal.
My phone is an Motorola Motolux (XT615) with Android 2.3.
best regards
alex
Quote from: "alex_dd"Hello,
with today's update, Locus gets very very slow on my phone. The start of Locus needs much longer and especially the loading of the map needs about 30 seconds each time i move or zoom the map (before it was about 1 or 2 seconds). also the opening of the menus is quite slow.
With this new version, Locus is almost not use able.
alex
Maybe same problem as here? viewtopic.php?f=25&t=3030&start=80#p20915 (http://forum.locusmap.eu/viewtopic.php?f=25&t=3030&start=80#p20915)
Which map(s) make the problem?
Quote from: "alex_dd"Parallel to the updated pro version I have an older free version on the phone, which works still normal.
Which version exactly?
my problem sounds similar to:
viewtopic.php?f=25&t=3030&start=60#p20873 (http://forum.locusmap.eu/viewtopic.php?f=25&t=3030&start=60#p20873)
the maps are some different vector maps.
The version of Locus free is 2.7.3. it uses exactly the same maps.
Alex
hi guys
firstly ... missing "DIM" settings. I was checking how much people use this settings and there was only a few. I use "older" method called "Wakelock" to keep screen on (in normal or dimmed state). Anyway this wakelock has also side effect, it try to keep CPU also awake and ready to use. Also in case of some small problems, this wakelock may cause abnormal battery usage. So recommended is not to use it, until it's really necessary.
So because I want to optimize Locus as much as possible, I sacrifice this settings for ability to not to use wakelock. Now, system for keeping screen on is 100% safe and there is no space for some battery problems due to this. So shortly, sorry, but there is no way to return this settings back. Only way should be automatically reduce brightness of screen by Locus itself, but I'm not sure I want to play with this settings ...
second: speed of map on 2.X devices ... I was checking a code and found only one line difference, where I put map rendering to lower priority. I'm worried that it's this problem. Your device think, that thread with low priority is not so important so it do not use much CPU power on it ... probably. I'll put here today a test version for quick test. If this will be this problem, I'll release new version soon with some more fixes
Hi menion, about the missing "dim"settings: could you please consider that again? I wonder that so less people are using this. On my device (Sony xperia active, android 4.0) it makes a huge difference in battery consumption, about 12 or 13% per hour with mostly dimmed screen vs. much more than 20% per hour without the dim option. So this is a huge affection of usability. I always have to be sure that the battery is fully charged before the tour (not very spontaneous) and tours above 4 hours or so are no longer possible without recharge or external battery. Problem is that my device holder for the bike handle bar covers the on/off-switch, so if I use the system settings for the display brightness and the display shuts off, I can't shut it on again without taking the device from the holder. You see, this setting is very important for me. So please, consider this problem again. Maybe you can find another solution.
Until then: is there any download possibility for version 2.11?
Thanks and regards joa
Quote from: "menion"missing "DIM" settings. I was checking how much people use this settings...
:shock: interesting - How do you made this :?: logfiles? big brother is watching you :D
big brother as Google Analytics
I really do not want to implement Wakelocks back. It's really dangerous method to keep screen on. I'll try to think about some alternative to dim screen, but cannot promise ...
Maybe there is an application with service on Google Play using wakelocks to keep the screen on, which would offer this function for people like joa? I found something called Wakey, but don't have any practical experience with it.
Edit: It's not suitable for this task, refer to later post
Pavel this is excellent solution. I always forget that Locus is not on Google Play alone :)
seems that false https://play.google.com/store/apps/deta ... blep.wakey (https://play.google.com/store/apps/details?id=com.doublep.wakey) Wakey looks usable ...
Unfortunately this one (Wakey) does not dim the screen in the basic version I have tested. But maybe some other...
Edit: OK, something called "Screen ON" //https://play.google.com/store/apps/details?id=com.brilliant.apps.screenon looks promising for this task, at least it works this way on my phone and is free and not add-supported.
Another option regarding brightness, though somewhat laborious, is to install Power Toggles (https://play.google.com/store/apps/deta ... ainless.pc (https://play.google.com/store/apps/details?id=com.painless.pc)).
From there you can add a widget to the notification bar via a toggle to change the brightness. You have one that switches between maximum, medium and minimum one can choose values for each, even if one chooses a mean value equal to the maximum or minimum is a switch between two values.
The good thing is that you can add different toggles with many functions. :)
Greetings.
Hi guys,
I'm very glad that you all give your best to help and in fact the solution pmoravec proposed, works on my phone, too. Need to change the "brightness behaviour" of Locus to "system settings", then the Screen on-App to "Let it dim" and it's just like before. Not as comfortable as before (two more clicks ;) ), but works quite well. Maybe Menion can keep this in mind and find some day some other battery saving tool within locus.
I wonder why only few people use this option. Do you all have such big batteries or do only short bike tours? ;)
Thank you again joa
Fine :)
I for example rather turn off screen, then keep it dim. Voice guiding works for me quite well and if there is any problem, I rather stop and check map not during a ride ... but everybody has different methods ;)
Quote from: "menion"28.5.2013 - Locus 2.12.0.1 - test version
new system for main menu
damn - my first map move show me the main.. :cry: not nice :roll:
why not?
I'm scared :lol:
Quote from: "menion"28.5.2013 - Locus 2.12.0.1 - test version
- new system for main menu - now using system from Google itself, so recommended :). Anyway may be bugged ...
Ah, menu gets activated by slide from left side. Like it
you like it? ah ... I tried to disable it, but there is bug in Android library that currently do not allow it :). Hmm you mean ... keep it?
Fortunately side menu react on really edge of screen, so there is minimal chance to slide it by accident ...
Quote from: "menion"you like it? ah ... I tried to disable it, but there is bug in Android library that currently do not allow it :). Hmm you mean ... keep it?
Fortunately side menu react on really edge of screen, so there is minimal chance to slide it by accident ...
Funny, I thought this was implemented intentionally as it matches quite good the menu coming in from left side. Now I can swipe it in and out. Yes, I'd like to keep it.
Quote from: "menion"Fortunately side menu react on really edge of screen, so there is minimal chance to slide it by accident ...
you don't know my sausage fingers... :lol:
Quote from: "pmoravec"Edit: OK, something called "Screen ON" //https://play.google.com/store/apps/details?id=com.brilliant.apps.screenon looks promising for this task, at least it works this way on my phone and is free and not add-supported.
Another way could be to wake the device with the proximity sensor. https://play.google.com/store/apps/deta ... toscreenon (https://play.google.com/store/apps/details?id=com.omd.autoscreenon) works fine for me and let the screen goes off. You can set single or double touch.
Dont know how much drain the wakelock for the sensor do.
"compute intersection" is new in GC Line Tools.
I don't use GC - so i have disabled this module a long time ago.
but now (have to translate some strings) i see this nice tools - but why only for GC :shock:
This should not be hide into GC stuff.
This is usefull for all users eg. ballooning ;)
So my vote "Line tools" for all ! :D
Are there any changes in uploading field notes to gc.com in 2.12.x?
When I try to upload field notes, there is a message "uploading field notes" which disappears without further notice. No progress bar, as in last versions. The field notes in Locus are not deleted. Only the first field note is uploaded to gc.com., all other field notes on my device are ignored.
I know that there were some problems on gc.com side in the last days, but the problem persists since yesterday. Other actions which use GC live API (like loading/updating caches via gc4locus) are running fine today. So it seems to me like a problem with 2.12.x...
you mean published version 2.12.0 or these test versions?
Also which function exactly ... in cache > field notes > upload field notes, or mass upload from menu > functions > Geocaching Live?
Quote from: "menion"you mean published version 2.12.0 or these test versions?
Also which function exactly ... in cache > field notes > upload field notes, or mass upload from menu > functions > Geocaching Live?
Published version 2.12.0, and mass upload via function -> Geocaching Live
ah it was maybe problem I found ... it should work already in published test version in first post. I'll rather check it.
Testing version 2.12.0.3 fixed my database again. Thanks!
I have to report a strange behavior with 2.12.0 official pro version and geocaches.
I had a list of geocaches (with finds filtered out and distance-based sort) imported from GPX and updated the listings through external plugin (G4L). They are all part of an archived pattern,which is still physically on original location. What happened was that when updating the listings, logs, etc., the original coordinates and new data (complete listings) got randomly mixed. If I remember correctly, GC API does not return coordinates for archived caches. So when updating something went wrong with the order of original data. Normally this does not seem to happen (possibly because the coordinates get overwritten as well or you match the results based on the coordinates).
small issue in 2.12.0.(official)
1. Choose a vector map and afterwards
2. choose an overlay. For choosing an online map, tap on online map, but you´ll be directed back to vectormaps?
I can confirm with Android 2.3.6 that vectormaps are loaded faster in 2.12.03 compared to 2.12.0.
About line tools:
small drawing bug (allready in 2.12.0), at line crossing tool only the upper/left part of lines is drawn on the screen (ends with the calculated crossing point).
One wish: I'm interested in informations on lines that I have drawn (after the creation page): Could it be possible to show lenght & azimuth of the lines on map?
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. :D
I have one question and maybe a bug:
1. the feature of hill shading for vector maps (in development) actually throws the shadow upper right:
[attachment=0:38bxn0wn]e8yqapam.jpg[/attachment:38bxn0wn]
For maps normally it is lower right.
@Menion: Can this be corrected?
2.
Only for record: yesterday I had several crashes of 2.12.3 (also 2.12.0) during navigation. Locus crashed at recalculation of route. I was not able to make a catlog during driving. Maybe I can get some logs later..
Quote from: "druki"Only for record: yesterday I had several crashes of 2.12.3 (also 2.12.0) during navigation. Locus crashed at recalculation of route. I was not able to make a catlog during driving. Maybe I can get some logs later..
In this moment I wanted to report the same with 2.12.0.3:
Today I tried in realtime a navigation with my car. After 20 mins the navigation screen disappeared suddenly without a freeze or FC and the home screen was visible.
The worst thing was that the battery drained as much as during a track recording. A task killer showed nothing of Locus and no GPS icon was in the status bar :-(
Three hours later (without loading) the battery was almost empty.
Quote from: "druki"...the feature of hill shading for vector maps (in development) actually throws the shadow upper right...
To compare...
@pmoravec: updating and whole handling of locus data over Locus API is based on points IDs and when arcao in G4L update cache, I think he update it thanks to GC Code of every cache. So there should not be a place for such huge issue. Anyway are you able to reproduce it? Even better - are you able to give me step by step instructions, so I can reproduce this?
@jusc: thanks, picking a maps fixed
@druki: yes, lines are drawn just from first point to intersection. Anyway I warn you, this computation isn't much precise. I'm still searching for more precise way to compute it (currently I approximate compute on sphere and not on ellipsoid). About additional information - all these line/circle draw functions has big disadvantage. After you draw something, this item cannot be selected and used. Locus also do not compute some intersection between circles automatically etc etc ... so there is big place for improvements. On second side, I think these functions are really rarely used, so I still have no reason to invest too much time into this ... and it's same with your request on display an azimuth and bearing.
@henk: I think it's just ... "luck" :)
@druki, tramp: I also had one crash when I wanted to stop navigation, but I'm unable to repeat it now, damn. And tramp, your problem with battery consumption is really very weird. Mainly because it's almost impossible to consume battery when Locus is not in list of apps. I would like to publish final version before release for some testing. I'll then need some time, so priority is to release version without problems. So please check it and create for me a logcat if some problem happen, thanks
@druki, gynta: hillshading ... if this will work, it will be amazing :). Anyway same as on some other places ... I still wasn't able to create fast method for this hillshading, mainly on lower zoom levels. It's of course possible to change sun angle (I'll do it, thanks), but this will still not be enough to make hillshading nice looking ...
Quote from: "menion"hillshading
... but this will still not be enough to make hillshading nice looking ...
hillshading only between zoom 11 and 16 is perfectly adequate.
If anyone wants to see the earh from space: should use google earth :D
@menion,
I cannot citate here.
Perhaps I explained bad:
If e.g. Copilot stops unexpectedly then the GPS software module (?) remains active and completely hidden and drains the battery invisible so as Locus today in my case.
So perhaps this is a "normal" behavior of my ROM.
Please search only for the crash :?:
Gesendet von meinem LG-P970
fine, this should be better ...
[attachment=0:lgxkw90b]device-2013-06-02-174735.png[/attachment:lgxkw90b]
anyway best should be to render hillshade in around level 15 and use this result in all zoom levels. But hard to do in for example level 10, where is then needed 32x32 tiles, so more then 1000 tiles from 15 to cover one tile at 10 .. heh
nevermind for now. Thanks for tip, hillshade looks better now, and I'll try to think about it later a little bit
@tramp: this really happen?? I sometimes saw (already happen to me) that Locus or any app crashed and GPS remain active, but GPS was visible in system bar. This, what happen to you is really bad. No matter what happen to app itself, this should never happen on any device. So if you use any alternative ROM, I also think it should be a problem in this ROM. So best solution is to fix all bugs in Locus :)
Quote from: "menion"@druki, gynta: hillshading ... if this will work, it will be amazing :). Anyway same as on some other places ... I still wasn't able to create fast method for this hillshading, mainly on lower zoom levels. It's of course possible to change sun angle (I'll do it, thanks), but this will still not be enough to make hillshading nice looking ...
From here (a month ago): viewtopic.php?f=25&t=3030&p=20484&hilit=hillshading#p20485 (http://forum.locusmap.eu/viewtopic.php?f=25&t=3030&p=20484&hilit=hillshading#p20485)
Quote from: "menion"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
Did you change your mind? :?
hmm no ... I still think that function is not ready to officially include and enable to public version ..
btw. I did small fix in navigation. Also together with other small fixes, new version is available in first post. Don't expect any huge changes so don't waste a time. I'm sure there exists much better ways how to spend free evening :)
Quote from: "menion"hmm no ... I still think that function is not ready to officially include and enable to public version ..
btw. I did small fix in navigation. Also together with other small fixes, new version is available in first post. Don't expect any huge changes so don't waste a time. I'm sure there exists much better ways how to spend free evening :)
I hope the new version includes better weather for Bavaria ;-)
don't even talk to me about this ... Prague is under water and against-water barrier do not work as expected ...
a problem, I think which existed always:
Navigate to: to start the process e.g. press the "Car" but there is currently no internet connection => Locus reports this problem and closes the Navigate to.
This is bad as you have to start the whole process again after enabling internet connection.
Add new route and measure is more user friendly, it doesn't loose anything, you just need to remove your latest added point and continue after enabling Internet.
you're of course right ... currently mechanism is
1. you define start/end points
2. tap on route type to compute
3. Locus close "Navigate to" screen
4. start compute
first two remain same, but I now switched points 3. and 4. where "Navigate to" screen is closed only in case, compute is success ...
Quote from: "menion"you're of course right ... currently mechanism is
1. you define start/end points
2. tap on route type to compute
3. Locus close "Navigate to" screen
4. start compute
first two remain same, but I now switched points 3. and 4. where "Navigate to" screen is closed only in case, compute is success ...
exactly! Thanks
Big THANKS to pmoravec for the link, that leads to the "screen ON" app in Google Play!
This funktion was integrated in the System of my former Windows Mobile Smartphone, and it was also manually configurable (turn off brightness after "x" seconds, this could be set manually). This saved a lot of accu power with my former GPS navigation software on my mobile, so I could ride mountainbike tours from 5 to 7 hours with one accu pack.
With changing to Android, there was again the problem to save accu power. Searching many forums I realised, that maybe Android users don't know this funktion. So I was searching for this funktion, based on a app, for a long time.
Then I found Locus, with this "auto DIM" solution built into the app - that was perfekt!
Don't know, how other mountainbiking Locus users solve this, but for me it's not easy to wake up the screen by pressing a button, when riding a mountainbike - just touching any part of the screen is much easier! In the evenening or when riding throught the woods, the dimmed screen is often bright enought to see the map or the track I'm following, so the screen is always on, but saves power.
The loss of the "auto DIM" funktion is a big reduction of the funktionality of Locus for me when I'm riding my bike.
So, again thank's for the Link!
And Greetings from Ingolstadt
Quote from: "pmoravec"Unfortunately this one (Wakey) does not dim the screen in the basic version I have tested. But maybe some other...
Edit: OK, something called "Screen ON" //https://play.google.com/store/apps/details?id=com.brilliant.apps.screenon looks promising for this task, at least it works this way on my phone and is free and not add-supported.
Hi,
I have a strange issue with this app. After starting or even after stopping the app I can´t use my telephone by typing the number 5. Other numbers are working normally. (Note 2 with JellyBam (Cyanogen 10.1))
Hello,
i can confirm that the update from today resolv the problem with the slow vectormaps in Android 2.3.
Thank you very much for this.
alex
perfect. I'm gladly this mystery error (at least for me) is solved. By reported issues, looks that current version is quite stable without any serious problems, so I can finally start work on another tasks :)
enjoy locus and finally coming nice weather (at least in Czech)
weather is ok, but here in Dresden we get at the moment your dirty water ;)
Quote from: "alex_dd"i can confirm that the update from today resolv the problem with the slow vectormaps in Android 2.3.
With Android 4.0.4 too :-)
alex, not much funny :). It's water full of dead animals, toilets and others that our water-purifiers wasn't able to filter. It's little bit - too much water at once. Fortunately seems that it's going to be better. Worst time is behind us ...
Hi Menion,
I have strange artifacts with Vector Maps.
I'm not 100% sure about the necessary preconditions but this is how I can often (~4 out 5 times) reproduce it:
OpenAndro Vectormap Germany, Internal Hiking theme, Zoomlevel 19/71%.
And then open DataManager/Map Items, select two (really short) tracks created with brouter and return to map screen.
Screenshot with artifacts: https://www.dropbox.com/sc/pthqe92472ppjpd/E3Xx1syWCk (https://www.dropbox.com/sc/pthqe92472ppjpd/E3Xx1syWCk)
Increase zoom level twice (first zoom goes to 19/100%, 2nd zoom goes to 20/100%) fixes the artifact
Screenshot w/o artifacts: https://www.dropbox.com/sc/l2qp9vgm1uyhcev/yVx-35YNSo (https://www.dropbox.com/sc/l2qp9vgm1uyhcev/yVx-35YNSo)
Problem reproducable on both SGS3 and Nexus 7, internal hiking and city themes!
On SGS3 reproduced with 2.12.04 (Free) and 2.12.2 (Pro), on Nexus 7 with 2.12.2 (Pro).
But:
If I import the map item tracks and display them from the list of tracks, I can't reproduce the problem.
I'm not able to reproduce such kind of artifacts with zoom operations (+/- buttons or with two fingers) or map panning. Here everything works perfect.
Seems it has something to do with MapItems.
I tried to reproduce it, but I don't get this issue. But maybe I missunderstood?
Tried with internal and external themes.
Quote from: "tommi"..I have strange artifacts with Vector Maps..
like this...
Hi Menion,
just as an update. Both jusc (per PM to me) and gynta confirmed the problem I reported regarding artifacts of vectormap screen).
sorry for a late response and thanks for bug-report. I was playing with it and was able to reproduce it twice after some experiments, but since then I'm unable to reproduce it. Weird ... there is probably some problem with refreshing old map. Because zooming has changed and locus now reuse old tiles and paint over them new data (to save some time by creating empty bitmaps), this have to be some incorrect order of operations, but ... :/
I'll try to experiments with it. Fortunately it's not so big problem for now, so I'm sure soon or later I find why this happen :)
@menion,
you are developing with Note 2?
Can you please test altitude measures while tracking. With all sensors on and switched on GPS altitude with GSM I don´t get any altitude, but for the first 3 points. Maybe it´s because I use a Cyanogen Rom. tramp20 confirmed that he hasn´t this problem without any pressure sensor.
So I´m not sure if it is the ROM or the combination of pressure sensor and GPS/GSM altitude.
Thank you in advance
yes I use Note2. best device for developers :) (on second side worst, because everything is so fast on it :) ) ...
I'm recording everytime I go out, but not with pressure sensors (because of problem I wrote about). Next time I'll keep screen on and try what you write. Anyway what you mean by "I don´t get any altitude, but for the first 3 points"? This mean that only first three points has altitude and rest no? And "no" means really no altitude or same as previous three points? Also what settings you have in Altitude manager?
And it should not be a problem of CyanogenMode. I think this ROM is so well tested, that if there is any problem, it will be in Locus
Yes only the first points have the altitude. All other points don't have any. Not zero but "not available". You can see it in my last post of
https://c.getsatisfaction.com/locus/top ... ure_sensor (https://c.getsatisfaction.com/locus/topics/pressure_sensor)
Quote from: "jusc"Yes only the first points have the altitude. All other points don't have any. Not zero but "not available". You can see it in my last post of
https://c.getsatisfaction.com/locus/top ... ure_sensor (https://c.getsatisfaction.com/locus/topics/pressure_sensor)
Now I found a few minutes to test that. For me no problem, doesn't matter if screen on or off. Tested with the usual setting "use pressure sensor".
editStrange, dashboards don't work anymore:
https://www.dropbox.com/sc/walh5tqz6hnq518/Gav1tKxaPB (https://www.dropbox.com/sc/walh5tqz6hnq518/Gav1tKxaPB)
This is only one example picture, also none of the other default dashboards is working anymore.
Quote from: "tommi"Strange, dashboards don't work anymore
hm, works here on last google play pro version 2.12.2
Tried Dashboards again after reboot and still doesn't work in Locus Pro 2.12.2. Locus Free doesn't provide this feature. So went back to test version Locus "Free" 2.12.04 and there it works!
@Menion: What should I do? Reset of App Data for Locus Pro App didn't help!
@tommi: hmm nice ... have no idea :)
may you share problematic dashboard file? It's stored in locus/data/dashboard. Maybe there is some problem with this file. I also had no problem during some testing with any of existing dashboards, weird ... btw. log! almost always help, maybe there is some errors on background (most probably)
@jusc: for my surprise, this happen to me also after around 700 recorded points. All altitude values then was not 0, but NaN, which mean some problem in computation. I did some debug messages into output and will try it today during some test bike ride ...
I see that altitude recording is working without problems if I disable the use of the pressure sensor.
Not tested at the moment is pressure sensor without GPS or GSM data.
here depend on calibration type. You always use "Automatic" or is this happening also in other calibration types for you?
I use the last option and define the height by my own.
Quote from: "menion"@tommi: hmm nice ... have no idea :)
may you share problematic dashboard file? It's stored in locus/data/dashboard. Maybe there is some problem with this file. I also had no problem during some testing with any of existing dashboards, weird ... btw. log! almost always help, maybe there is some errors on background (most probably)
Sent mail "dashboard issue".
I don't think the dashboard file is problematic as even the standard ones (joeloc's dream etc.) don't work.
On the other hand with the same Locus folder dashboards work with 2.12.0.4.
Thanks for taking care.
Tommi
@tommi: in logs is no error and your dashboard works for me without a problems. This is quite a mystery
@jusc: sorry, I wasn't fast enough to look closer on problem with sensor. It happen to me today again during a bike test, and logs do not show anything
both problems needs to be solved. Tomorrow I have one vegetarian action in Prague, so during a sunday, I'll for sure check it. Have a good night a don't forget to test new test version ;). I'm looking forward to your opinion on "data screen". Hope you'll not kill me ;) but I really don't like two similar screens in one app - item visibility & data screen
Quote from: "menion"15.6.2013 - Locus 2.12.2.4 - test version
I cannot remember I've ever seen that: "Question: File with model of Geoid is missing. Download now?"
Is that something new? I see no relation to the described changes :o
Don't want to bother you but short report for 2.12.2.4:
Quote from: "menion"sorry for a late response and thanks for bug-report. I was playing with it and was able to reproduce it twice after some experiments, but since then I'm unable to reproduce it. Weird ... there is probably some problem with refreshing old map. Because zooming has changed and locus now reuse old tiles and paint over them new data (to save some time by creating empty bitmaps), this have to be some incorrect order of operations, but ... :/
I'll try to experiments with it. Fortunately it's not so big problem for now, so I'm sure soon or later I find why this happen :)
No change, problem still easily reproducible for me.
Quote from: "menion"@tommi: in logs is no error and your dashboard works for me without a problems. This is quite a mystery
No problem in 2.12.2.4 - but still this is not working in 2.12.
ah sorry, forget on geoid, it's one secret function and I forget to disable it for testing version :)
you wrote "no problem in 2.12.2.4" with dashboard?? So it works in this test version and not work in public 2.12?? Hmm then it have to be something in settings, but no settings affect functionality of dashboard. Only that is close, is settings > misc > periodic updates. It's almost impossible to fix it in 2.12 if in test version it works :)
Quote from: "menion"- merged "Item visibility" feature with data screen!
Ok, this goes into the direction I already hoped for a long time ago (wanted to have same options regarding item visibility for tracks as they are for points).
I guess you mean that the item visibility screen shall replace the data screen?
If yes:
- Tab for Map items is missing
- The crossed eye in the top right of the screen claims it wants to *delete* my map item on the screen. But if I confirm, the map item is still available from datamanager/Map items.
General for map item tab:
Can it behave as e.g. track with a tick per map item ins and a tick per folder instead of bold red name per item?
=> Use the same GUI elements for points, tracks, (other) map items!
forget on "Item visibility". just remove it and don't use it ... all is now in "Data screen". Check new top action bar button
Quote from: "menion"forget on "Item visibility". just remove it and don't use it ... all is now in "Data screen". Check new top action bar button
Confusing, confusing, the changes in item visibility screen are much more noticable than the ones in Data screen.
Ok, let's check the Data screen:
- I don't like the toggle button for Ticks and Tools and would prefer two buttons instead. Of course this results also in two columns for all the Point and Track folder lists. But I fear the guys out there with their thumb nail screens ;) will likely vote against that.
But much more uncomfortable I'm with the following:
- The behaviour for the tick button on folder level as it is implemented now for Points and Tracks:
Let's assume I have currently selected 25/50 points in folder P which results in a set tick on folder level for P. If I remove the tick on P I get 0/50 points which is as I expect and like it because I want to do this to remove the points temporarily from screen (item invisibility!).
Now I want to see my points again. What should I do? There are two options: a) set the tick for P or b) go into P and select the 25 points. a) is not what I want and b) is a nightmare.
What I'd like to see instead, is the option to re-enable my 25 points with a single tap. Ok, there should also be an option to select all 50 points in P, this could be done with a long tap on the tick.
Alternatively, if you want to stay with the toggle for tick/tools I would be happy with a tick on P which sets my 25 points again and an item in the tools list to enable all points of P.
And again for the Map Item tab:
Can it behave as Points and Tracks with a tick per map item ins and a tick per folder instead of bold red name per item?
=> Use the same GUI elements for points, tracks, (other) map items!
So far my suggestions for the Data screens.
editQuote from: "menion"ah sorry, forget on geoid, it's one secret function and I forget to disable it for testing version :)
Ok, I've cleaned my brain :)
Quote from: "menion"you wrote "no problem in 2.12.2.4" with dashboard?? So it works in this test version and not work in public 2.12?? Hmm then it have to be something in settings, but no settings affect functionality of dashboard. Only that is close, is settings > misc > periodic updates. It's almost impossible to fix it in 2.12 if in test version it works :)
It works in testversions 2.12.0.2 and in 2.12.2.4.
You are right, periodic updates was ticked in Proversion and not ticked in Free/Test version. Actually I don't know what this really is.
Anyway, removing the tick didn't help (closed Locus Proafter removing the tick and started again few seconds later).
editQuote from: "menion"15.6.2013 - Locus 2.12.2.5 - test version
Also is anyone using OSM Bugs? please test new OSM notes system if all works as expected
I added a new OSM Note (without Login) which worked as expected. A minute later it appeared on Locus screen.
But I see only open notes (red bubble with white x), can't find closed ones (how should they look like?).
wait you talk about some other possibilities for a selecting a points & tracks to some alternative previous state, but:
- if you open points tab with tools buttons on right side, it's same as before!!
- if you open points tab with checkboxes on right side, it's same as "Item visibility". So why you now try to create some new logic for a selecting previously selected points?
tab "items" is another story, it should be on program when points & tracks are done
OSM note ... I know ... I already wrote them about https://github.com/openstreetmap/openst ... issues/304 (https://github.com/openstreetmap/openstreetmap-website/issues/304) ... response was that it's fixed, but I still see same issue. Have to check it
Quote from: "menion"wait you talk about some other possibilities for a selecting a points & tracks to some alternative previous state, but:
- if you open points tab with tools buttons on right side, it's same as before!!
- if you open points tab with checkboxes on right side, it's same as "Item visibility". So why you now try to create some new logic for a selecting previously selected points?
I was never happy with the selection logic :). Therefore I propose something, which is, at least for me, more logical and better usable.
How would you like to select 25 out of 50 points to be displayed as they were one minute ago before you hid them?
Quote from: "menion"tab "items" is another story, it should be on program when points & tracks are done
fine
Hi meinion,
some minutes ago I sent you a internal report of 2.12.2.5.
I got "Locus does not react (or so), wait or send a report".
I have no catlog because I noticed this 3 hours later and of course the debug log is empty.
This was the first Freeze/FC since many test versions.
Perhaps it would be better when you write continuously the debug log (if Locus has time) then waiting until locus is shut down.
Can I use the market version tomorrow instead of the test version or do I get difficulties?
menion
I have tried out the test version 2.12.2.5. and just like to say the changes to the data screen have made the wonderful prog that you have better. I live in an area where the Geo-cache population is high, so to keep the folders to a reasonable size I have split it up into 12 (ranging from 700 -1500 caches each). In the past I had to go into each folder and deselect the caches when moving between areas, but now with the check boxes it is all done from one screen. And if I wish to select just a few then a tap on the left gives me that option.
Great innovation, keep up the great work.
Quote from: "tramp20"Hi menion,
some minutes ago I sent you a internal report of 2.12.2.5.
I got "Locus does not react (or so), wait or send a report".
Hi,
today the same again :-(
Locus test stopped after the start without any points recorded.
And I saw this one hour later so sorry for no catlog.
In the morning I made a 6 hours tour with the market version and absolute no problem as all the days before.
@tommi: I had to read your suggestions about selecting items more then few times. And I still don't like it :). You simply want that Locus remember your previous state of selected items, so you may enable them again, right? But if I imagine it, I'm sure I'll never remember which points I had previously enabled, so why should I want re-enable them back? :).
@CaptKaos2 you're welcome - and it will be even better in next version ;)
@jusc: problem with pressure sensor found, at least on my device. It's again same - my device turn of pressure sensor when I turn off screen and my calibration system wasn't able to handle it. It should be fixed now and you'll get warning if this happen. I cannot check if sensor is on or off, but if there will be more then 15 seconds without values, you should get warning dialog
@tramp: welcome to the world of testing versions ;). Unfortunately I see no useful log in weird system that Google provide for a developers. So please check next test version (I'll upload today 2.12.2.6) where few things should be fixed and if there will be a problem, have prepared catlog. You should btw. start catlog also before locus and start recording so you'll have all logs recorded for sure ...
I will try .6 tomorrow morning with catalog but I fear that 6 hours catlogging will make a really big logfile :-(
So I will stop and start catalog every hour if I do not forget it.
Gesendet von meinem LG-P970
this should not be a problem. CatLog for sure periodically write data into file, so they'll not stay in memory for whole time
I was yesterday recording for about two hours with enabled debugging for pressure sensor. Result was that every second, five lines was recorded together with some other messages and even around 200k (15MB) lines was no problem ;)
Quote from: "menion"@tommi: I had to read your suggestions about selecting items more then few times. And I still don't like it :). You simply want that Locus remember your previous state of selected items, so you may enable them again, right?
Yes.
Quote from: "menion"But if I imagine it, I'm sure I'll never remember which points I had previously enabled, so why should I want re-enable them back? :).
Of course I don't remember the 25 points and
1) this is the reason why I like computers, they can remember things which I as a human can't
2) Select the 25 points (or much, much worse: select 25 tracks) (or at least the ones I can remember) is a pain.
Actually what I propose is what I always expected to get from the now deprecated feature "temporarily disable visibility of items". The important thing here is "temporarily". What is implemented now is persistantly disabled visibility.
Too bad that I can't convince you.
never say never ...
From my point of view if confusing this: imagine I have selected 25 points from 50, I hide them, then close Locus or do something different and after an half of hour I'll try to enable all points, because I completely forget that I had selected just few of them. And what a surprise ...
I also do not see, why Locus should remember this ... if I want to see whole map, I may disable all points by two taps
What I have currently in mind is to allow load all points as now, but with respect of defined filter for folder. This should partially solve your problem isn't it?
I think, this is not about "convince me". I look on it from view "why I should expect from it", and I do not expect that app will remember such state
And new test version is there (//http://forum.locusmap.eu/viewtopic.php?f=25&t=3112#p20936) ... you'll probably kill me, but data screen has changed again :D
Now the numbers are right aligned, well done. But the font is smaller, make it bigger please.
Fine, long tap on map manager symbol and I can hide them all.
Fine, tap on symbol on the left to toggle between enable/disable all. I don't understand why the '0' is printed in red.
Quote from: "menion"never say never ...
From my point of view if confusing this: imagine I have selected 25 points from 50, I hide them, then close Locus or do something different and after an half of hour I'll try to enable all points, because I completely forget that I had selected just few of them. And what a surprise ...
Why not print it like this:
(25/50) when points/tracks are on screen
(25/50) when points/tracks are hidden
(0/50) or (0/50) when points are not selected (or green, too)
Quote from: "menion"I also do not see, why Locus should remember this ... if I want to see whole map, I may disable all points by two taps
That's not the point, the point is how to get my collection of points/tracks back which I only wanted to disable temorarily to see the whole screen or which I disabled temporarily to make map rendering faster (many tracks make rendering much slower).
Quote from: "menion"What I have currently in mind is to allow load all points as now, but with respect of defined filter for folder. This should partially solve your problem isn't it?
You mean filter by name, by icon? You are right, it is a partial solution but unfortunately the selection of points I use typically doesn't follow a certain rule which can be defined by a filter.
I would be happy with a long tap on the icon (the short tap is the toggle for all/none, the long tap is the toggle for selection/none.
Quote from: "menion"And new test version is there (//http://forum.locusmap.eu/viewtopic.php?f=25&t=3112#p20936) ... you'll probably kill me, but data screen has changed again :D
Not at all, it's definitely better.
Great, one tap in the data screen does it all for me. :D
Hello,
I try to close 2.12.2.6 (Android 2.3.6) with the back button, but Locus doesn't close (is there an other way to close?). No matter if "closing prompt" is on or off (never get this request in this version) and no matter if "run as a service" is active or not. Seems that I have to kill Locus - I never thought that I would ever consider this ;-) But if I don't close it, it will drain my battery tomorrow during daytime...
If I remember correctly, it was possible to close the main menu with the back button in earlier versions. Not possible in 2.12.2.6?
@druki: hmm interesting, I did small fix in close event for some rom based on 4.X android and this caused these troubles on 2.x devices ... perfect :). Thanks druki, I'll fix it to next version. Enjoy Locus killing ;). Btw. I think there should be no power consumption when locus sit on background if you have disabled all common features, like recording, live tracking etc ...
@vcapt: fine :)
@tommi: seems to be on long discussion. I understand what you want, but I do not agree with it. I think that current ability to quickly load/unload all items (which is btw. much much faster then before) together with ability to temporary hide all items on map, cover all needs, that common user may have. And because we're only one who discuss about it here, I suggest to form your idea into some good readable text and post it on GetSatisfaction, so I may get more opinions focused just on this one topic
Quote from: "menion"@tommi: seems to be on long discussion. I understand what you want, but I do not agree with it. I think that current ability to quickly load/unload all items (which is btw. much much faster then before) together with ability to temporary hide all items on map, cover all needs, that common user may have. And because we're only one who discuss about it here, I suggest to form your idea into some good readable text and post it on GetSatisfaction, so I may get more opinions focused just on this one topic
No, thank you. Leave it as it is if you think it isn't useful for most users. GUI should be kept simple.
Quote from: "menion"So please check next test version (I'll upload today 2.12.2.6) where few things should be fixed and if there will be a problem, have prepared catlog. You should btw. start catlog also before locus and start recording so you'll have all logs recorded for sure ...
Just coming home from a 6 hours tour with .2.6.
So I have now a big catlog file but no freeze/crash :-)
I will make another test later, but it looks good now.
Edit: the second test trip was ok too.
Thank you.
perfect, good to hear. Hope that .2.7 will be also OK ;)
and btw. no-one has opinion on discussion with tommi? Don't leave him alone :)
so I spend more time on some testing and finding places that should work faster ... hope it will be visible, mainly in loading/unloading points. There is also finally a method to change icon for more then one point at once, so you then may simply use filter (btw. it also include a lot of improvements mainly for a geocaching) to display only a part of points etc etc ...
feedback is welcome of course. I'm going to take finally a two day bike trip, so I'll test it as much as possible. During sunday/monday will be enough time for every problem you find or improvements that will be need ...
have a nice weekend
Quote from: "menion"I'm going to take finally a two day bike trip, so I'll test it as much as possible. During sunday/monday will be enough time for every problem you find or improvements that will be need ...
have a nice weekend
Menion, I hope you will enjoy your bike tour.
Maybe you decide to use https://getsatisfaction.com/locus/topic ... directions (https://getsatisfaction.com/locus/topics/navigate_imported_track_with_turn_by_turn_voice_directions) resp. https://getsatisfaction.com/locus/topic ... _your_ears (https://getsatisfaction.com/locus/topics/guiding_with_your_ears) and think about making it more perfect and helping get back on the track.
2.12.2.8:
Updating Geocaches:
The new filtering features for geocaches are great for viewing/selecting. But when I want to update (Addon GC4Locus) a single geocache (or a group of marked geocaches), I don't care about the filtersettings and it is anoying to be forced to chose a filter which is impossible:
1. the radius is not within my actual map position (btw. another anoying behaviour with the map centering/sorting to GPS which was much better before)
2. my selected caches could fit both of each filter criteria (i.e.temporarily disabled caches and enabled ones) and I'm not allowed to leave all filter in the "don't care" position.
So my suggestion:
Could it be possible to ignore (all) filtersettings when updating selected(!) geocache(s)?
Back-button:
Still problems (Android 2.3.6) with back-button at:
- closing Locus (workarround: killing, because either I
a) use Locus with GPS permanently on, even in background to have it ready if I look at it without waiting for a sat fix ... or I
b) don't need it for sure and close it)
- closing main menu (workarround: slide to the right)
- closing the dashboard view (workarround: click the dashboard button. Yes, I fortunately have it in the top bar ;-) )
2.12.2.8:
Share map center or screen: The list with the different sharing options is heavily flickering on the screen (seems the list is displayed again and again).
In latest Pro this is working correctly.
Hello.
I'm going to report some bugs which I found during the translation work.
* [Settings] -> [Map - objects & style] -> [Altitude position]
- The text defined in "pref_map_tracks_show_label_desc" is incorrectly shown.
The text in "pref_map_item_show_label_altitude_desc" should be there.
* [Settings] -> [Guiding] -> [Tracks, Notification settings]
- A text with xml tags '<font color="red">(Pro)</font>' is shown
after Text-to-speech. It can be seen only in Locus Free Version.
* Typo in the context name.
- The context name assigned for the text 'Import' seems wrong.
It shouldn't be 'impor' without 't' at the end but should be 'import'.
- This can be confirmed only at the crowdin.net web site but not in the locus app.
* [More] -> [On-board map calibrator] -> [Compute]
- The progress indicator shown as percentage does not work properly.
It shows constant value of '2147483647 %'.
I also would like to ask some requests related to the text and its context name in "strings.xml/strings_pref.xml".
I found that some of single English word are used at the different place in Locus with a defferent meaning.
For example, the word "Basic" defined in "basic" appears in:
- [More] -> [Parking] -> 'BASIC' as a tab name.
- [Data] -> [Tracks] -> any track -> STYLE -> 'BASIC' as a choice of solid line.
Their meanings are different at all and it causes problems on translation.
Sometimes it is very difficult or even impossible to find appropriate word to satisfy both meanings.
If you prepare these words separated, for example,
- word "Basic Infomation" as a tab name using "parking_basic_info"
- word "Solid line" as a type of line using "line_basic"
then the problem will be solved.
Continuation:
The followings are the words which I would like to request to prepare the words to be separated.
* The word "Orientation" defined in "pref_orientation" appears:
- [Settings] -> [Global] -> [Orientation lock]
-> 'ORIENTATION' for Portrait mode / Landscape mode.
- [Settings] -> [Sensors] -> 'ORIENTATION' as of bearing.
* The word "Recording" defined in "recording" appears:
- [Settings] -> [Track recording] -> 'RECORDING' as a title name.
- Pop-up message 'Recording' when you start/resume track recording.
* The word "Visibility" defined in "visibility" appears:
- [More] -> [Weather] -> 'Visibility' as the transparency of the air.
- [More] -> [Notes (OpenStreetMap)] -> 'Visibility' as show/hide notes.
- [Settings] -> [Track recording] -> [Automatic export] -> [OpenStreetMap]
-> 'VISIBILITY' as the type of GPS traces.
* The text "Area" defined in "area":
- [Maps] -> [ONLINE] -> [Download] -> 'AREA' as a region for map download.
- [Data] -> [Tracks] -> any track -> INFORMATION tab -> 'Area'
as a mathematically calculated value of the area closed by track.
Quote from: "druki"2.12.2.8:
Updating Geocaches:
The new filtering features for geocaches are great for viewing/selecting. But when I want to update (Addon GC4Locus) a single geocache (or a group of marked geocaches), I don't care about the filtersettings and it is anoying to be forced to chose a filter which is impossible:
1. the radius is not within my actual map position (btw. another anoying behaviour with the map centering/sorting to GPS which was much better before)
2. my selected caches could fit both of each filter criteria (i.e.temporarily disabled caches and enabled ones) and I'm not allowed to leave all filter in the "don't care" position.
So my suggestion:
Could it be possible to ignore (all) filtersettings when updating selected(!) geocache(s)?
I'm sorry but I don't understand. "Filter" do only thing. Limit list of item to only these that match filter. So where is problem with selecting just few of them and update by G4L? If you want to cancel filter, just tap on filter and bottom left button cancel whole filter at once so you may select whatever you want.
Quote from: "druki"Back-button:
Still problems (Android 2.3.6) with back-button at:
- closing Locus (workarround: killing, because either I
a) use Locus with GPS permanently on, even in background to have it ready if I look at it without waiting for a sat fix ... or I
b) don't need it for sure and close it)
- closing main menu (workarround: slide to the right)
- closing the dashboard view (workarround: click the dashboard button. Yes, I fortunately have it in the top bar ;-) )
ahh sorry, I forget to improve it. So please in next version, one more try. If this will not work, I'll return back handling completely to previous version. It's really bad that such simple function like sending down/up press on back key works a little different on various ROMs ... :/
Quote from: "tommi"2.12.2.8:
Share map center or screen: The list with the different sharing options is heavily flickering on the screen (seems the list is displayed again and again).
In latest Pro this is working correctly.
is this happen to you everytime? Interesting because nothing changed in this dialog
Quote from: "ta-ka"Hello.
I'm going to report some bugs which I found during the translation work.
very very nice list, thanks ...
Quote from: "ta-ka"* [Settings] -> [Guiding] -> [Tracks, Notification settings]
- A text with xml tags '<font color="red">(Pro)</font>' is shown
after Text-to-speech. It can be seen only in Locus Free Version.
hmm I'm not able to see it. You see this text also in a test version? Weird
Quote from: "ta-ka"* Typo in the context name.
- The context name assigned for the text 'Import' seems wrong.
It shouldn't be 'impor' without 't' at the end but should be 'import'.
- This can be confirmed only at the crowdin.net web site but not in the locus app.
1. context name isn't really important. It's just unique identificator
2. "impor" is intent, because there are some words that cannot be used as ID, here is list http://docs.oracle.com/javase/tutorial/ ... words.html (http://docs.oracle.com/javase/tutorial/java/nutsandbolts/_keywords.html)
all other mentioned problems has been changed. Usually by using another word or creating different translations like for "visibility". Seems you invested a lot of time to this, so thank you very much!
Quote from: "menion"Quote from: "tommi"2.12.2.8:
Share map center or screen: The list with the different sharing options is heavily flickering on the screen (seems the list is displayed again and again).
In latest Pro this is working correctly.
Is this happen to you everytime? Interesting because nothing changed in this dialog
100% reproducible on 2.12.2.8 also after reboot on my S3, not reproducible on latest Locus Pro, not reproducible at all on Nexus 7.
I created a log but it shows nothing interesting at all (only very few records from Locus and without anything bad).
Thank you for taking my requests and the comment on the reason of 'impor'.
For the "text with xml tags" issue, my explanation was too short. Here is a long version.
1. install LocusPro 2.12.2 from Google Play
2. disable WiFi and 3G connection then launch LocusPro
3. When "Application not licenced" window appears, tap "Free" button
4. see [Settings] -> [Guiding] -> [Tracks, Notification settings]
Quote from: "tommi"Quote from: "menion"Quote from: "tommi"2.12.2.8: Share map center or screen: The list with the different sharing options is heavily flickering on the screen (seems the list is displayed again and again). In latest Pro this is working correctly.
Is this happen to you everytime? Interesting because nothing changed in this dialog
100% reproducible on 2.12.2.8 also after reboot on my S3, not reproducible on latest Locus Pro, not reproducible at all on Nexus 7.
I created a log but it shows nothing interesting at all (only very few records from Locus and without anything bad).
Idea came from gynta via PM: Rename Locus folder and try if it happens in a clean (and empty) Locus environment. It worked there.
And now, after having gone back to my Locus folder, it still worked! How crazy is this? Anyway, treat it as solved!
Hi, can not reproduce any more the problem with updating a geocache and filtersettings. But have small error at first update after Locus start. I have sent a catlog to menion.
In my case Locus crashes if I use the lens to zoom with original Locus map and doesn't start anymore.
(Map NRW with the original hiking theme) Version 2.12.2.8
what means
"with original Locus map" ?
edit1
OH i see :o
A heavy FC after using the magnifier - right on the bottom.
DONT TRY IT - Locus crashes hard and can't be restarted.
Reboot - remove battery - nothing help - Locus is damaged!
I try to install last test version over damaged version...
edit2
wow - a new install also failed...
edit3
"force stop" and "delete data" in system settings helps.
btw
thx Jusc for no hint :roll: :lol:
Quote from: "gynta"what means
"with original Locus map" ?
- > original Locus Vectormap from Locus store. (Germany / Nordrhein Westfalen)
Menion
Yesterday I went out geocaching for 7hrs using test version 2.12.2.8. Apart from little system setting changes I had forgot to make I had no problems with the Prog.
But this afternoon I decided to use it at home to plan next weekends trip and done what I would normally do in the Pro version to get the caches in the area I'm going.
1. With the GPS off and WiFi on long press on the screen to load Map Centre.
2. Select the address and then the Function button (Bottom Right).
3. Select Nearest caches and then the Geocaching4Locus screen appears, where I can download the caches and import them.
The difference with the test and pro is as the G4L screen appears another screen appears briefly saying " Acquiring address from wireless network" and the coordinates default to as near as wireless can get to my home location, (which is 50 miles from where I want)
I have tried it with Pro and it defaults to the selected address coords.
Is this to do with the warning in your first post.
Warning: this version move settings for "Live tracking", "Quick add point", "WMS maps" to different directory!! Do not use this version if you also want to use current public version of Locus with these features!
If so just ignore this post, and I apologize in advance.
@tommi: weird, mainly because log was empty ... but probably nothing to do now :)
@druki: thanks for logs. I already saw this error somewhere, but it's on place where seems to be impossible to get it. I add some small protection, so hope it won't happen again, but be prepared with Catlog :)
@gynta, jusc: in log from gynta is nothing (thanks btw.). I received small report on bugsense, but it's also not clear why this happen. So same as in "druki's" case. Added small protection but be prepared
@CaptKaos2: hmm I'm unable to reproduce such problem but it has nothing to do with red text. But in Locus is no such text "Acquiring address from wireless network" so it should comes from add-on. I'll try it later
so probably final test version is available - 2.12.2.9 . Most bugs should be fixed as well as texts for translation. Btw. I do not have any feedback on few important things ... merging of "Data & Item visibility" and "Improved filter". What you think? Everything clear?
Quote2.12.2.9
FC using/selecting magnifier still present
new FC: restoring backup (but i have to verify with another backup later...)
Settings - Global - Allways screen on
Strange statuns "(ON)"
because if i choose "Specify" -> Screen is NOT always on
(eg only when GPS is on)
Status should be "Specify"
Settings - Global - Allways screen on
It's possible to set "Specify" and leave it, with not set any option.
should not be possible.
Hmm still present. May you please create for me better(longer) log? Because previous was really too short and completely without an issue. Thank you
Sent from my GT-N7100 using Tapatalk 2
Menion
Thanks for the reply, I have installed 2.12.2.8 and the latest locus pro onto my Nexus 7 to see if it makes a difference. I have also installed Geocaching4Locus .
With Location access switched off, which is my normal mode, as I use a Bluetooth GPS.
In the pro version everything works as I would normally expect it.
In the Test version when I press "Nearest cache" I get a black box at the bottom of the screen with "Wrong INTENT - no point!" this disappears and the Geocaching4Locus box appears with a further box over it with
"No location service allowed"
Please allow Wireless or GPS location service in "Settings"
With a Settings and OK buttons underneath.
No matter what I press the Coords are still incorrect.
EDIT:-
I have just installed 2.12.2.9 on my HTC phone and indeed the "Wrong INTENT - no point!" appears on it, it disappears so quickly I did not notice it before. If I press the back button and manually input the coords it works as expected.
hmm and are you using exactly same functions on both devices? I know you use Geocaching4Locus, but I need to know which button. If in context menu of points, list of functions or any in right panel. Please check it, thanks
send you two log files
Quote from: "tommi"Now the numbers are right aligned, well done. But the font is smaller, make it bigger please.
Fine, long tap on map manager symbol and I can hide them all.
Fine, tap on symbol on the left to toggle between enable/disable all. I don't understand why the '0' is printed in red.
...
Not at all, it's definitely better.
Menion, you asked for feedback on new data screen. I think this was feedback.
ah yes you're right ... if you noticed, font isn't smaller anymore ;). I enlarged it to same size as other text.
About colors ... when I was playing with it, I noticed that I miss numbers close to names as was before. Before was easy to see which category has any data already loaded and which has no data loaded. So I tried to highlight empty folders by coloring "0" with red and it helped (at least me) a lot, because I can very easy see if folder has loaded any points or not. That's reason for it ...
You think it's confusing? Hmm for me personally isn't usually important how much points is loaded, but if there are any loaded. Because I usually want to have map fast, so if I don't need any points, I want to hide them fast and this coloring helps me ..
and guys jusc & gynta. Thanks for help. In the end problem is solved. I updated Android API to new version and this version downgraded! Proguard (program I use for some code tweaking) to some older version. And this caused this problems. Once I updated it to new version as was before, all works correctly. So sorry for a troubles, this time I'm almost innocent :)
Menion
I hope you understand this.
Long press on the map screen brings up Screen 1. I tap on the address box and screen 2 appears.
Tap on A (Gears Icon) and from the sub menu I select B Nearest caches.
From the actions in my last post Screen 3 appears.
Sorry its in 2 parts the forum would only allow me to attach 2 files.
Quote from: "menion"ah yes you're right ... if you noticed, font isn't smaller anymore ;). I enlarged it to same size as other text.
Either of us is dreaming. Definitely numbers are much smaller than name of folder. Sorry, can't provide screenshot as battery almost empty.
Menion
I have just given it a try with Bluetooth and Internal GPS, ensuring I had a good fix before trying. In both cases the Wrong INTENT box appears. With internal GPS a box appears saying "Aquiring location from GPS" and defaults to my present location. With Bluetooth I get Screen 3 as per my last post.
@tommi: ah you're right, still little smaller :D
[attachment=0:307toujx]2013-06-25 20_33_40-Clipboard.png[/attachment:307toujx]
@capt: sorry, I've got it. Problem is that API that use geocaching4Locus, has small problems when in device is more Locus versions. In this case, it took Locus Pro first and Locus Free second. When you do some search over long-clicked point (temporary point), then Geocaching4Locus start searching for this point (to obtain coordinates) in Locus Pro and not in testing Locus Free. So I'm very sorry, I do not realized this. It will anyway work correctly in next published Locus Pro version. Most probably in Thursday
Menion
Thanks for that, it stops me doing my next step. Uninstalling Locus Pro. :lol:
Look forward to the next version.
Quote from: "tommi"Either of us is dreaming.
I know his name ;)
i like the size of numbers
[attachment=0:aj6k86xr]Screenshot_2013-06-25-20-38-29.png[/attachment:aj6k86xr]
edit ah menion was faster...
alternative should be also, put these numbers to second line, just below names. But I was trying it and it doesn't look too good ...
EDIT: hmm 21k points in one folder ... did you tried to load them all? Hope you like new, around three times faster, loading ;). Btw. moving a map with all these points should be also little bit faster now
Quote from: "menion"hmm 21k points in one folder ... did you tried to load them all? Hope you like new, around three times faster, loading ;). Btw. moving a map with all these points should be also little bit faster now
9 seconds to load the list
38 seconds to select all
9 seconds to deselect all
all pois on map?
hm - never need all pois - but when, no problem - i'm using poi grouping :-)
without grouping? ok..
loading 42.000 Pois on map without problems now
stuck a little bit - but it works
good job!
Quote from: "gynta"all pois on map?
hm - never need all pois
Nice usecase for what I proposed but no one else wanted to talk about it - except Menion who doesn't like it.
Quote from: "gynta"without grouping? ok..
loading 42.000 Pois on map without problems now
stuck a little bit - but it works
good job!
looks like a flower meadow but not like a map with symbols :roll:
Quote from: "tommi"Quote from: "menion"Quote from: "tommi"2.12.2.8: Share map center or screen: The list with the different sharing options is heavily flickering on the screen (seems the list is displayed again and again). In latest Pro this is working correctly.
Is this happen to you everytime? Interesting because nothing changed in this dialog
100% reproducible on 2.12.2.8 also after reboot on my S3, not reproducible on latest Locus Pro, not reproducible at all on Nexus 7.
I created a log but it shows nothing interesting at all (only very few records from Locus and without anything bad).
edit
Idea came from gynta via PM: Rename Locus folder and try if it happens in a clean (and empty) Locus environment. It worked there.
And now, after having gone back to my Locus folder, it still worked! How crazy is this? Anyway, treat it as solved!
Not yet ;) same here now. on both devices.. -> https://www.dropbox.com/s/o17kndohh8ate ... 2013_0.mp4 (https://www.dropbox.com/s/o17kndohh8ate9h/clip__Jun_25_2013_0.mp4)
hmm I'm searching why this may happen and only source seems to be this one - http://stackoverflow.com/questions/4995 ... il-chooser (http://stackoverflow.com/questions/4995006/blinking-e-mail-chooser) where developer has same problem. And yes I know this problem also when I work on language chooser. Do you use different language in Locus then in your system? May you try to change it to "default" in locus if this helps?
Interesting is, that this problem have to be in Locus since begin :)
EDIT: if someone want to test fix for magnifier or some other reported issues, there is last test version.
Quote from: "menion"hmm I'm searching why this may happen and only source seems to be this one - http://stackoverflow.com/questions/4995 ... il-chooser (http://stackoverflow.com/questions/4995006/blinking-e-mail-chooser) where developer has same problem. And yes I know this problem also when I work on language chooser. Do you use different language in Locus then in your system? May you try to change it to "default" in locus if this helps?
In my case, as I wrote, the problem vanished by renaming Locus folder so that it wasn't found and after renaming it again to Locus the problem was still away. And yes, I use the Free Version in English whereas the Pro in German.
I think it's not something causing this problem in 100% of all cases.
thanks all for big support on creating a new version. Still some problems remain, like this flickering screens, but I'm sure we'll solve it soon ;)
enjoy version 2.13.0