Locus Map - forum

Development => Versions => Released => Topic started by: menion on October 26, 2012, 16:26:35

Title: [APP] - version 2.7.X
Post by: menion on October 26, 2012, 16:26:35
23.11.2012 - Locus 2.7.4

new version is just uploading to Google Play

13.11.2012 - Locus 2.7.3

new version is just uploading to Google Play

3.11.2012 - Locus 2.7.2

new version is just uploading to Google Play

26.10.2012 - Locus 2.7.0

new version is just uploading to Google Play. In this version is new system for databases, and during start of new Locus is conversion. I really hope all will go fine and there will be no problem with this. Enjoy
Title: Re: [APP] - version 2.7.X
Post by: balloni55 on October 27, 2012, 16:54:13
Congratulation menion for these new Version!
The first start takes 3 minutes, to convert data.
I like the new posibility to create different trackcategories  :)
I see some icons i can select for different categories :)
Is it also possible to build own icons, similar  POI icons in the iconfolder?
Title: Re: [APP] - version 2.7.X
Post by: col on October 27, 2012, 17:45:35
Hi, with update to 2.7.1 all my points and tracks are gone. I restored back to 2.6.3 and they were back, updated to 2.7.1 again and it said there was an incomplete new database, clicked to delete it and convert again> Locus closes, and on re-opening all points and track are gone. Am I doing something wrong?
Title: Re: [APP] - version 2.7.X
Post by: menion on October 27, 2012, 17:54:03
balloni55: http://docs.locusmap.eu/doku.php/manual:category_icons (http://docs.locusmap.eu/doku.php/manual:category_icons)

col: you cannot do anything wrong. If something not work, it's for sure problem in Locus. When you started firstly 2.7.1, you do not saw request on conversion? Please check that
1. you have *.sqll files in Locus/data
2. you don't have directory Locus/data/database

in this situation, Locus after start should display you a question, if you want to convert old data (*.sqll) into new (into data/database directory).

also before conversion start, locus create backup file with all tracks and points into Locus/backup directory
Title: Re: [APP] - version 2.7.X
Post by: balloni55 on October 27, 2012, 18:43:23
Quote
balloni55: http://docs.locusmap.eu/doku.php/manual:category_icons (http://docs.locusmap.eu/doku.php/manual:category_icons)
sorry i was blind, i forgot to tab on the "select triangle"
Title: Re: [APP] - version 2.7.X
Post by: kokos42 on October 27, 2012, 19:01:29
I have lost all my points after upgrade to 2.7.1.
a/ locus/data directory contains files *.sqll
b) locus/data/database does not exist
After starting Locus Pro > all points are still gone, locus/data/database is created (with no data), but no conversion of old sqll is performed.

Am I doing something wrong?

EDIT:
I have followed advice of "col" user.
First remove Locus/data/database directory, then uninstal Locus Pro and install it from market again.
It works, many thanks! All points were succesfully converted after first launch of app.
Title: Re: [APP] - version 2.7.X
Post by: col on October 28, 2012, 00:49:25
hi menion,  yes to question 1 & 2, and no question to convert old database, or new backup file created. looked in log folder but no error log created. the new directory is created with files inside but nothing shown in locus.

edit:

got it working by uninstalling , deleting data/database directory, then reinstalling from market.
Title: Re: [APP] - version 2.7.X
Post by: fenster on October 28, 2012, 16:20:15
Hello menion,
I used Locus Pro version 2.7.1
Not anymore the selected track will be displayed on a map.

After this failur I have deleted and made a new installation of Locus Pro fom Play Store.
But still the same problem.
After opening Locus Pro I choosed
- Data
- Tracks
- than choosed a track
- in the information view at the bottom there is the icon of map
- after pressing this icon the map will be seen

but

it will not be jumped to the selected track
It is still the former track in the map.

I do not know what to do.
What could it be?
Title: Re: [APP] - version 2.7.X
Post by: fenster on November 02, 2012, 08:24:38
Quote from: "fenster"
Hello menion,
I used Locus Pro version 2.7.1
Not anymore the selected track will be displayed on a map.

After this failur I have deleted and made a new installation of Locus Pro fom Play Store.
But still the same problem.
After opening Locus Pro I choosed
- Data
- Tracks
- than choosed a track
- in the information view at the bottom there is the icon of map
- after pressing this icon the map will be seen

but

it will not be jumped to the selected track
It is still the former track in the map.

I do not know what to do.
What could it be?

Hello menion,

all is now ok and works fine within tracks.

I deleted all folders and files from Locus Pro on my phone. Than I installed Locus Pro again from market place.
Than I copied back my former points and tracks, but now only the files from data/_pre270 into /data.
The conversion took 1 1/2 hours.
Perhaps there was a confliced with the former beta 2.7. which I had installed and worked on.

Nevertheless thanks for your fine work.
Title: Re: [APP] - version 2.7.X
Post by: menion on November 02, 2012, 17:02:29
fenster, I'm sorry! I completely forget to response on your previous post. Anyway I'm glad you don't give up fight with last Locus version and all works now fine :)
Title: Re: [APP] - version 2.7.X
Post by: menion on November 03, 2012, 16:47:23
notification about a new official version. There is quite a lot of bugfixes and start of one most required feature for geocachers (trackables). Enjoy
Title: Re: [APP] - version 2.7.X
Post by: balloni55 on November 03, 2012, 19:21:34
Hi menion,
with the new version i get an error report when i click in the cachelisting /Trackables on the Geocoin.
This cache is one of my own, so you can do any test ;-))
Title: Re: [APP] - version 2.7.X
Post by: tommi on November 03, 2012, 19:23:16
Answer is here, I think:
https://getsatisfaction.com/locus/topic ... nvalid_141 (https://getsatisfaction.com/locus/topics/cannot_view_trackable_accoss_token_invalid_141)
Title: Re: [APP] - version 2.7.X
Post by: Henk van der Spek on November 05, 2012, 16:28:59
Conversion was great; 2 minutes or so. Locus is fast again!!

But:
The tracks from the App MyTracks are visible in their own new made (autogenerated) Category called Mytracks. Clicking anyone for opening gives me a FC for Locus with prompt restart. (not so important for me but I noticed).

Creating new empty categories is smooth. Importing existing tracks goes only one by one! Hmmm.

Some tracks that were previously imported as kml files and created (or did I do that?) points category with the same name, now do not let them import in a track category. Upon the import commando only the list of points categories is availble.
Before I empty the points, is there another way or what am i missing?
Title: Re: [APP] - version 2.7.X
Post by: menion on November 05, 2012, 18:55:35
I'll check MyTracks and fix loading issue, thanks for notify

about import, I'm not sure I understand. You try to import track and you get only offer for choosing Points category? May you share any file that do this?
Title: Re: [APP] - version 2.7.X
Post by: Henk van der Spek on November 05, 2012, 19:46:52
Ok, forget it. I need new glasses. It is a kml file that contains points and a track and Locus does a simultanious import for the points and the track and for both you can choose the category where it should be imported.
Title: Re: [APP] - version 2.7.X
Post by: menion on November 05, 2012, 19:59:44
Oki, no problem. Just if you'll have any troubles with import, best is to provide some sample file I may use for testing
Title: Re: [APP] - version 2.7.X
Post by: fenster on November 05, 2012, 20:55:38
Hello menion,
just now I updated to Locus Pro 2.7.2.
The time for starting Locus has improved a lot and take in my situation only less than one second.
(I use about 40.000 points, a lot of own and vector Maps).
Unfortunately I am not able to give more feedback because I use Locus only for walking around different areas.
Also the work with tracks are fine for me.
Title: Re: [APP] - version 2.7.X
Post by: menion on November 05, 2012, 21:04:49
fine, good news are always welcome :) thanks
Title: Re: [APP] - version 2.7.X
Post by: joeloc on November 13, 2012, 08:26:00
2.7.2.7 behaves strange with a point database of mountain huts and my map called MIX200-EuropaSüd (huge 1.8GB 1:200k rmap of europe, max zoom level is 12). The huts are visible nicely at 10|100%, 11|100% and 12|100% but DISAPPEAR on anything closer than 12|130%.  They also disappear randomly at 12|100% when simply scrolling through the map.

Can also reproduce that problem with another big RMAP (3.8GB 1:50.000 EasternAlpsComplete). Points disappear randomly when scrolling or zooming.

Problem doesnt seem to happen on mapsforge vector maps.
Title: Re: [APP] - version 2.7.X
Post by: joeloc on November 13, 2012, 14:44:48
I've also had 2.7.2.7 crash randomly twice now while simply running in background recording tracks. That has never happened before. Crashlogs sent by email.
Title: Re: [APP] - version 2.7.X
Post by: menion on November 13, 2012, 14:45:50
hmm I'm testing it on some RMAPs from you (with imported points from your email) and on no problem in any case. So, you may try to record for me a log, if there will be any problem or create for me just some small RMAP map, which have same problem and send me it for testing.
Title: Re: [APP] - version 2.7.X
Post by: joeloc on November 13, 2012, 15:50:13
I fail to reproduce it with smaller maps atm. But didnt I send you MIX200-EuropeSouth.rmap already at one point? Anyway, I am emailing two videos showing the problem. Will see if I can make a logcat thingy as well.

The random crashes were unrelated to the waypoint problem.
Title: Re: [APP] - version 2.7.X
Post by: menion on November 13, 2012, 15:58:11
I was checking maps from you as a first thing, but I have only "MIX200-EuropeSouth-10.rmap" and it's just some small map (26MB) that also do not cause this problems.

Hmm there have to be some problem with transformation of coordinates for such huge map and then checking if points are visible or not.

Log with crashing during a record contain some weird error, that Locus want to notify about GPS state (by sound) and cannot. There were no reason for this, so I at least added some protection against crash of whole app
Title: Re: [APP] - version 2.7.X
Post by: joeloc on November 13, 2012, 16:02:30
Quote from: "menion"
Log with crashing during a record contain some weird error, that Locus want to notify about GPS state (by sound) and cannot. There were no reason for this, so I at least added some protection against crash of whole app

I changed mobile phones and ROMs inbetween and restored a Locus backup, so maybe that crash is related to a configured sound file not being found anymore.
Title: Re: [APP] - version 2.7.X
Post by: menion on November 13, 2012, 16:06:01
hmm yes, this is possible. Good point, thanks fixed
Title: Re: [APP] - version 2.7.X
Post by: joeloc on November 14, 2012, 13:37:56
how about a new testing version? and do you still want logs then for those disappearing points? i doubt they'd show calculation result problems.
Title: Re: [APP] - version 2.7.X
Post by: berkley on November 14, 2012, 20:18:57
Is it just me, or is the information during track recording in notification bar not updating?
-> 2.7.3 pro and free, 4", 7" and 10" devices all on CM10
Title: Re: [APP] - version 2.7.X
Post by: menion on November 14, 2012, 20:46:44
as I'm testing it, it works as usually. Updated notification once per minute! I was testing it quite a lot (in times of Android 2.X) and discovered that refreshing of notification use abnormal amount of CPU, that's why it was always just once per minute
Title: Re: [APP] - version 2.7.X
Post by: menion on November 16, 2012, 16:47:14
Quote from: "joeloc"
how about a new testing version? and do you still want logs then for those disappearing points? i doubt they'd show calculation result problems.

Stephan, is in last version still problem with crashed during recording? Hope not. About missing points - I'm worried that there will be problem in map projection + size of the map. And it will be really hard to fix it without map itself. Is there any way to get any map that cause there troubles? One idea ... please if it's not a problem, try to create map in same width (+- longitude) but just very thin (small +- latitude). It should cause same problem
Title: Re: [APP] - version 2.7.X
Post by: joeloc on November 17, 2012, 15:44:06
emailed a smaller map to reproduce the problem.

Btw... locus keeps re-scanning my maps folder over and over again on startup, resulting in very long startup times. When quitting and restarting right away, its blazingly fast. But after a reboot or after using other apps for a while, the whole dir is rescanned. Shouldnt the state be cached somewhere in a persistant file? Seems to me its only cached "in memory" and lost very often.
Title: Re: [APP] - version 2.7.X
Post by: tommi on November 17, 2012, 17:42:04
Quote from: "joeloc"
But after a reboot or after using other apps for a while, the whole dir is rescanned. Shouldnt the state be cached somewhere in a persistant file? Seems to me its only cached "in memory" and lost very often.
As a workaround for startup times I use the setting Global->Locus as system service. Then Locus opens instantly :)
Title: Re: [APP] - version 2.7.X
Post by: menion on November 17, 2012, 19:04:44
this helps? Ah not possible to be a difference, really :)

Problem that Locus rescan all maps is simple. As I was already discuss about it with you Stephan (if I remember correctly), this happen only when there is any map that do not work. In this case, Locus do not have it's initialization cached and is trying to do it next time. Most issues should be already reported, but probably not all yet. So check if you see all maps in your "Personal" tab. At least one will be missing there

And about instant restore after close, it's also pretty simple. Try to close Locus and then immediately start it. It will be visible immediately. Try to close it and wait for example 10 seconds. It will start as usually. Locus usually wait a few seconds till all is completed, and then finally kill application itself. So if you start it immediately, I just restore app from background, nothing more (and no killing will happen)

btw. than you for the map, I'll check it soon and let you know
Title: Re: [APP] - version 2.7.X
Post by: joeloc on November 17, 2012, 19:28:05
I thought Locus puts up a requester now for bogus maps. I have seen that once and deleted the offending map. No more requesters appear now, so all maps should work. I can also see them all in the personal maps list.

Locus re-starts in three different ways for me:

1) immediate restore from background, just the same as if the app wasnt quit at all. Makes sense.

2) "quick" start: the "loading... restoring previous state..." window with all the maps and tracks and whatever appears but scrolls through very quickly (ie in less than a second).

3) "slow" start: like 2) but loading the maps takes a very long time (ie 30 seconds) and they scroll by slowly one at a time.

locus does number 3 on the first start after every phone reboot for example. is this correct?
Title: Re: [APP] - version 2.7.X
Post by: UKlocusfan on November 18, 2012, 21:08:56
I can't trust Locus Pro anymore  :(

Maybe similar to what joeloc is talking about - but I had 2 Locus crashes during a tracklog that was just under 4 hours.  :(

Unlike joeloc they luckily didnt happen in the background but instead happened as I opened Locus Pro to check my distance traveled and see what POIs were about.  Twice Locus just crashed.  :(

This has been happening with 2.7.x versions for me and I am now gutted to say I have to take my S.E. k750i out with me and a seperate GPS module using trekbuddy to record the track I walk as I simply do not want to walk 4 hours and risk not having a .gpx at the end of it.

Here are a few things I have noticed the last few weeks that are really troubling me about Locus. I state these things only as feedback as I think Locus is superb but recently have honestly considered stopping using it.  :(

1. Seems to use more battery than other releases prior to 2.7.x

2. Importing a gpx file often causes it to crash and I need to open Locus again and try to re-import the gpx. This opening and immediate crash can happen 3 or 4 times before the gpx file finally imports correctly.

3. I never have more than 3 (at the very most) POIs open at any one time in Locus when I am out and about logging my route... but sometimes when just clicking the 'points' tab - Locus will just crash as it did twice yesterday when I was performing very simple operations.

4. When Locus crashes whilst logging a route... it restarts itself which is great... but please please please can it be made to automaticly resume logging because at the moment it puts the logging into 'pause' mode when it restarts and its very easy to forget to take it off pause.  It would be so much better if after a crash it resumed logging.

Well, that my recent experiences on long walks with Locus.  Its gone from being an app I used to look forward to using to one I really like but dread how its doing to act.

I would appreciate any advice or ideas on the above.  Is it worth me installing catlog again and trying to sort out some crash reports?

Thank you.  :)
Title: Re: [APP] - version 2.7.X
Post by: berkley on November 18, 2012, 21:58:51
Sorry to hear that it doesn't work the way you want...

About your questions:
(1) Does it just seem to use more battery or does it use more battery?
(2) Can you share (private or public) a gpx file that causes the crash?
(3) + (4) Can't answer that... send logs to Menion.

There are a lot of possibilities for Locus to crash. So best method to find the reason is sending logs to Menion.
When I'm talking about lots of possibilties, I mean questions like:
- How much RAM is available for Locus to operate?
- Are you using vector maps and map rotation while these errors occur?
- Do you display lines to target or lines to GPS while these errors occur?
- Is it just your old phone and the old Android version, which doesn't work correctly?
- and a lot more questions...

When you have these huge problems with Locus and still want them to be fixed, please share some more information.

Cheers, berkley
Title: Re: [APP] - version 2.7.X
Post by: UKlocusfan on November 18, 2012, 22:14:23
Answers contained in the quote below  :)

Quote from: "berkley"
Sorry to hear that it doesn't work the way you want...
Thanks Berkey.  It does work the way I want it, thats why I like it so much and have done for years, but recently I'm having far too many problems

About your questions:
(1) Does it just seem to use more battery or does it use more battery?
It does use more battery, I have another thread about this

(2) Can you share (private or public) a gpx file that causes the crash?
This happens on a range of gpx files generated from (so far) 3 different sources. It must have happened on about 10 different gpx files so far and so I am quite confident its not specific to a certain gpx
(3) + (4) Can't answer that... send logs to Menion.

There are a lot of possibilities for Locus to crash. So best method to find the reason is sending logs to Menion.
When I'm talking about lots of possibilties, I mean questions like:
- How much RAM is available for Locus to operate?
Good idea Berkely.  I have been checking this though and it seems I have about roughly 190mb RAM free when Locus is running
- Are you using vector maps and map rotation while these errors occur?
With the battery problem I have had rotation turned off but have been using a 250mb Vector map of England although its never caused problems before I agree it just may be doing something bad in these latest versions of Locus.
- Do you display lines to target or lines to GPS while these errors occur?
Hardly anything displayed. Usually 1 POI I am walking to and quite often a guiding line to the POI
- Is it just your old phone and the old Android version, which doesn't work correctly?
I use android 2.3.5 on an HTC Wildfire S... thats what Locus Crashes on.  I've resorted back to using a 7 year old regular mobile now to log my routes
- and a lot more questions...

When you have these huge problems with Locus and still want them to be fixed, please share some more information.

Cheers, berkley

Thanks Berkley.  :D
Title: Re: AW: [APP] - version 2.7.X
Post by: druki on November 18, 2012, 22:35:40
Just for info: I had some trouble twice during import of PocketQueries with GC Live api (Locus ran as service). Locus hang at the last import and I had to kill it (in the systems view of running apps) and restart the phone to have a running Locus again (otherwise it started with the hanging import). I still try to reproduce and next time I let write a catlog.
As soon as I get some more reproducable data, I will let you know.
Title: Re: [APP] - version 2.7.X
Post by: berkley on November 18, 2012, 22:37:57
Are you using task killer apps or do you let Android decide, which tasks to kill?
Do you use the setting "Use Locus as a service"?
Is altitude correction turned on while you are offline?
Do you record NMEA data?
Did you change settings for resolution of vector maps?
Do you know, that HTC devices are causing most "Force Closes" for all apps in general?

Questions over questions... btw, sorry for bad english...
Title: Re: [APP] - version 2.7.X
Post by: menion on November 19, 2012, 08:04:48
Questions over questions and troubles over troubles - sorry guys

I'll gladly solve all possible problems, but: I need some way to reproduce or find source of problem!! This cannot be done simply by "locus crashed twice today". Sorry, this cannot be solved

1. best way is description step by step that lead to issue. If you write me, tap here, tap here, crash ... perfect
2. second way is log (http://docs.locusmap.eu/doku.php/manual ... simple_log (http://docs.locusmap.eu/doku.php/manual:how_to:error_reporting#simple_log)) + description at which moment this happen
3. if some files cause it (problems with import etc...), this file is more then welcome. Again, when you send me this file, I may simply simulate this problem and immediately fix it!
Title: Re: [APP] - version 2.7.X
Post by: joeloc on November 19, 2012, 16:49:49
Quote from: "joeloc"
3) "slow" start: like 2) but loading the maps takes a very long time (ie 30 seconds) and they scroll by slowly one at a time.

locus does number 3 on the first start after every phone reboot for example. is this correct?

Locus also does this very frequently when starting, even without rebooting the phone. Basically, whenever I do some other things with my phone and then restart Locus, it always rescans the map folder and makes me wait a long long time. Pretty annoying, especially since scanning just one single big rmap file can take over five seconds (Galaxy Note with a bunch of 3GB rmap files).

Whatever you cache when scanning map files... is not stored properly.
Title: Re: [APP] - version 2.7.X
Post by: tommi on November 19, 2012, 18:08:29
Quote from: "joeloc"
Quote from: "joeloc"
Locus also does this very frequently when starting, even without rebooting the phone. Basically, whenever I do some other things with my phone and then restart Locus, it always rescans the map folder and makes me wait a long long time. Pretty annoying, especially since scanning just one single big rmap file can take over five seconds (Galaxy Note with a bunch of 3GB rmap files).

Whatever you cache when scanning map files... is not stored properly.
Menion, Joeloc, I have a less long startup but still it is annoying and this is exactly the reason why I use the Locus system service.
Title: Re: [APP] - version 2.7.X
Post by: menion on November 20, 2012, 11:16:51
ah forget to mention. Stephan, may you please record for me a long log (http://docs.locusmap.eu/doku.php/manual ... og_message (http://docs.locusmap.eu/doku.php/manual:how_to:error_reporting#long_log_message)) when locus start and again initialize maps? In current dropbox version are some debug messages for this task, so I'll see why this happen

also is fixed hiding of some points, so check it please on your map if it works correctly
Title: Re: [APP] - version 2.7.X
Post by: dibrial on November 20, 2012, 11:26:16
I cannot log geocaches anymore in 2.7.3. I sent the generated error report. Using JB 4.1 on Motorola XT910.
Title: Re: [APP] - version 2.7.X
Post by: joeloc on November 20, 2012, 12:13:33
Quote from: "menion"
also is fixed hiding of some points, so check it please on your map if it works correctly
points no longer disappear... problem seems fixed. also mailed a log with an apparently bogus rmap.
Title: Re: [APP] - version 2.7.X
Post by: menion on November 20, 2012, 18:30:01
dibrial thanks, I'll look at it immediately after joelocs problems :)

So Stephan, I'm checking your logs and it's quite interesting.

All explain this error message: "11-20 11:46:51.018 W/FileMapManager(7143): existsNewMaps() - TRUE - not all files initialized, readyFiles:17, files:20"

This mean that Locus at start find three not initialized maps.
Maps that cause problems are probably

GTER-World06.rmap - this map cause singular matrix that I use for coordinate transformations. Interesting
italy.map.xml and CanaryIslands.map.xml - what are these two files? There is one undocumented feature I use sometimes for testing. Locus allow precise map definition thanks to own XML files. So you may define some web online map and add it to personal map even if web map have some weird projections. Anyway this feature is not public and is only partially working. back to topic ... Locus take these files as map and try to load them - in your case - process unsuccessful.

As I wrote, reporting incorrect map works only partially and not in all cases ... you discovered two cases when it do not work
Title: Re: [APP] - version 2.7.X
Post by: menion on November 20, 2012, 18:41:21
Quote from: "dibrial"
I cannot log geocaches anymore in 2.7.3. I sent the generated error report. Using JB 4.1 on Motorola XT910.

hmm I see it ... in error is "java.lang.IllegalArgumentException: Unknown pattern character 'Y'" ... so you have probably incorrect pattern for generated log description. I have to add there some warning if you write incorrect one and also protection against these crashes. May you please write me exactly what you have there? Thanks
Title: Re: [APP] - version 2.7.X
Post by: joeloc on November 20, 2012, 18:44:39
Ok... understood. So all will be fine if I delete those three offending files? You probably wouldnt have to rescan 20 good maps if 3 bad maps are discovered, but hey... thats nitpicking :-).

Anyway... about the xml files: they come from http://www.openandromaps.org (http://www.openandromaps.org) , the best and most complete and prettiest source of mapsforge vector maps for hiking and biking. Every downloaded map is accompanied by exactly one xml file, which I guess contains rendering information for Oruxmaps. The file is not needed for Locus obviously because you have the styles done differently.

However, some people (including me) have a dual installation with Oruxmaps and Locus... you know why :-). It would be nice if you could simply ignore those xml thingies in the maps folder if they dont contain your own private markup.
Title: Re: [APP] - version 2.7.X
Post by: dibrial on November 20, 2012, 18:49:38
Menion,

I don't really understand what you mean by "What you have there"
I'm using the basic predefined log (
#{c}, {t}, Thanks) and don't type anything else in the log.
What I do see is that {c} is filled by the no. of caches, but {t} is not.
Could this be the cause?
Title: Re: [APP] - version 2.7.X
Post by: menion on November 20, 2012, 19:00:44
check please your "Time format". There will be probably a problem
Title: Re: [APP] - version 2.7.X
Post by: dibrial on November 20, 2012, 20:46:10
Time format is:

dd-MM-YYYY 'at' HH:mm
Title: Re: [APP] - version 2.7.X
Post by: menion on November 20, 2012, 21:14:06
fine, that's what I needed to know

For formatting time, Locus use class that handle this format http://docs.oracle.com/javase/1.4.2/doc ... ormat.html (http://docs.oracle.com/javase/1.4.2/docs/api/java/text/SimpleDateFormat.html) . To answer simple, just change YYYY to yyyy and it will work ;)

EDIT: btw. I'm not sure how will work "DD", so you have to test it. In case of troubles,change it to "dd". To next version, I add some testing and better reporting what's wrong ...
Title: Re: [APP] - version 2.7.X
Post by: dibrial on November 20, 2012, 22:49:14
Logging works again. Thanks
Title: Re: [APP] - version 2.7.X
Post by: Mek on November 21, 2012, 18:40:12
In recent version of Locus Pro (on google play), crash occurs when deleting whole category of points.
Title: Re: [APP] - version 2.7.X
Post by: gynta on November 21, 2012, 19:47:24
hm works fine here.

Can you plz tell us your version number?
Menu->Locus->About->Locus...
---
Can you reproduce this crash?
---
Close Locus
rename your Locus dir (eg -> LLocus)
Start Locus
Create some categorys
Try it again
Delete new Locus dir
rename LLocus -> Locus
---
if Locus crash again
Can you send a logfile please?
-> see at http://docs.locusmap.eu/doku.php/manual ... ating_logs (http://docs.locusmap.eu/doku.php/manual:how_to:error_reporting#creating_logs)
Title: Re: [APP] - version 2.7.X
Post by: menion on November 24, 2012, 12:19:09
Mek, I think it was fixed thanks to gynta report just after release 2.7.3 version. Anyway new version is just uploading on Google Play, so check it. In case of problems, as gynta wrote ... logcat is needed (or report by new system after locus crash together with short description)
Title: Re: [APP] - version 2.7.X
Post by: tommi on November 24, 2012, 12:47:42
Quote from: "menion"
logcat is needed (or report by new system after locus crash together with short description)
logcat vs. new system? Is there something in Locus to make a crash report without logcat? If it is there I'll be happy to use it because logcat doesn't work for me anymore due to the change in Android JB. But actually I'm not sure if I understood correctly.
Title: Re: [APP] - version 2.7.X
Post by: Mek on November 25, 2012, 11:26:46
Yesterday I tried it again. I deleted an empty category and it took like 2 seconds for it to disappear from the list. Then I tried deleting a category again and clicked on it before it disappeared - this is the step that leads to the crash. Exception was generated and wanted to be sent so I am pastng it here. I guess logcat is no longer neccessary :P
Code: [Select]
USER_COMMENT=deleted a category of points and clicked on it before it disappeared from the list.
ANDROID_VERSION=2.3.6
APP_VERSION_NAME=2.7.3
BRAND=samsung
PHONE_MODEL=GT-I9100
AVAILABLE_MEM_SIZE=1575710720
TOTAL_MEM_SIZE=2113748992
CUSTOM_DATA=
STACK_TRACE=java.lang.NullPointerException
at android.view.ViewGroup.dispatchDraw(ViewGroup.java:1372)
at android.view.ViewGroup.drawChild(ViewGroup.java:1644)
at android.view.ViewGroup.dispatchDraw(ViewGroup.java:1373)
at android.view.View.draw(View.java:7039)
at android.widget.FrameLayout.draw(FrameLayout.java:357)
at android.widget.ScrollView.draw(ScrollView.java:1703)
at android.view.ViewGroup.drawChild(ViewGroup.java:1646)
at android.view.ViewGroup.dispatchDraw(ViewGroup.java:1373)
at android.view.ViewGroup.drawChild(ViewGroup.java:1644)
at android.view.ViewGroup.dispatchDraw(ViewGroup.java:1373)
at android.view.ViewGroup.drawChild(ViewGroup.java:1644)
at android.view.ViewGroup.dispatchDraw(ViewGroup.java:1373)
at android.view.View.draw(View.java:6936)
at android.support.v4.view.ViewPager.draw(L:1923)
at android.view.ViewGroup.drawChild(ViewGroup.java:1646)
at android.view.ViewGroup.dispatchDraw(ViewGroup.java:1373)
at android.view.View.buildDrawingCache(View.java:6693)
at android.view.ViewGroup.onAnimationStart(ViewGroup.java:1259)
at android.view.ViewGroup.drawChild(ViewGroup.java:1505)
at android.view.ViewGroup.dispatchDraw(ViewGroup.java:1373)
at android.view.ViewGroup.drawChild(ViewGroup.java:1644)
at android.view.ViewGroup.dispatchDraw(ViewGroup.java:1373)
at android.view.ViewGroup.drawChild(ViewGroup.java:1644)
at android.view.ViewGroup.dispatchDraw(ViewGroup.java:1373)
at android.view.View.draw(View.java:6936)
at android.widget.FrameLayout.draw(FrameLayout.java:357)
at android.view.ViewGroup.drawChild(ViewGroup.java:1646)
at android.view.ViewGroup.dispatchDraw(ViewGroup.java:1373)
at android.view.View.draw(View.java:6936)
at android.widget.FrameLayout.draw(FrameLayout.java:357)
at com.android.internal.policy.impl.PhoneWindow$DecorView.draw(PhoneWindow.java:1917)
at android.view.ViewRoot.draw(ViewRoot.java:1530)
at android.view.ViewRoot.performTraversals(ViewRoot.java:1266)
at android.view.ViewRoot.handleMessage(ViewRoot.java:1868)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loop(Looper.java:130)
at android.app.ActivityThread.main(ActivityThread.java:3691)
at java.lang.reflect.Method.invokeNative(Native Method)
at java.lang.reflect.Method.invoke(Method.java:507)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:907)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:665)
at dalvik.system.NativeStart.main(Native Method)

BUILD=BOARD=GT-I9100
BOOTLOADER=unknown
BRAND=samsung
CPU_ABI=armeabi-v7a
CPU_ABI2=armeabi
DEVICE=GT-I9100
DISPLAY=UltraToxic ROM v8.1 XWLA4
FINGERPRINT=samsung/GT-I9100/GT-I9100:2.3.6/GINGERBREAD/XWLA4:user/release-keys
HARDWARE=smdkc210
HOST=DELLBUILDER01
ID=GINGERBREAD
MANUFACTURER=samsung
MODEL=GT-I9100
PRODUCT=GT-I9100
RADIO=unknown
SERIAL=unknown
TAGS=release-keys
TIME=1326809369000
TYPE=user
UNKNOWN=unknown
USER=root
Title: Re: [APP] - version 2.7.X
Post by: gynta on November 25, 2012, 14:42:39
Quote
USER_COMMENT=deleted a category of points and clicked on it before it disappeared from the list.
Why are you doing this??
Quote
ANDROID_VERSION=2.3.6
Why do you use an old OSversion?
Quote
APP_VERSION_NAME=2.7.3
Why do you use an old Locus version? plz try it with the current google play versions?
Quote
...and it took like 2 seconds for it to disappear from the list
...and why your SGS2 is soooo slow?
Title: Re: [APP] - version 2.7.X
Post by: Mek on November 25, 2012, 20:04:45
Quote from: "gynta"
Quote
USER_COMMENT=deleted a category of points and clicked on it before it disappeared from the list.
Why are you doing this??
Because this is how the problem can be reproduced with empty category. Now I tried deleting a category with 200 points, and it is still displayed after 2 minutes. Now I clicked on ANOTHER category and locus crashed as well. So it's not a problem of user workflow.
Quote from: "gynta"
Quote
ANDROID_VERSION=2.3.6
Why do you use an old OSversion?
Because it is a custom ROM and I didn't have time to upgrade yet.
Quote from: "gynta"
Quote
APP_VERSION_NAME=2.7.3
Why do you use an old Locus version? plz try it with the current google play versions?
Didn't know there was a newer version, Locus is updated so often, you know... but now I tried the same in latest version and the crash is still there.
Quote from: "gynta"
Quote
...and it took like 2 seconds for it to disappear from the list
...and why your SGS2 is soooo slow?
I can assure you my SGS2 is fast enough ;) However, it seems to me like if the busy indicator was hidden before Locus has finished its work? Dunno...
Title: Re: [APP] - version 2.7.X
Post by: gynta on November 25, 2012, 20:54:28
Quote
Now I tried deleting a category with 200 points, and it is still displayed after 2 minutes. Now I clicked on ANOTHER category and locus crashed as well
Quote
I can assure you my SGS2 is fast enough
i also use this device - without this problem.
Today I have deleted a category with 15.563 Point -> it took 11 seconds...
In this time it's not possible tapping on anything on screen.

Another Tests
Del 2616 Point and delete empty category:
(mediafiles removed)

Del category with 2616 Point:
(mediafiles removed)

Where is the difference to your test?

My suggestion:
- clean up your system (check for some tasks in background)
- update your Android to ICS 4.0.4

Quote from: "Mek"
I guess logcat is no longer neccessary
Nevertheless please send an logfile. Even if you think it's not necessary...
Title: Re: [APP] - version 2.7.X
Post by: Mek on November 26, 2012, 18:05:52
Yeah, I will definitely upgrade but not sooner than Christmas... so much stuff that needs to be done :D
Anyway, attaching logcat output. The stack trace can be seen there as well.

edit from gynta
attachment saved, thx
Title: Re: [APP] - version 2.7.X
Post by: menion on November 28, 2012, 20:46:15
ah perfect Mek. I did not give to this issue any priority to be true, but when I'm testing it, I discovered
1. I have same issue on 2.1 device. Even worst, category is not removed at all!
2. I received by email few errors same as this. In error is absolutely no clue why this happen so I was little bit desperate ..

I'll for sure fit it till next version, it's quite critical. So thanks to You and also gynta for help

EDIT: morning edit - finally fixed, thanks once more
Title: Re: [APP] - version 2.7.X
Post by: Mek on November 30, 2012, 19:21:15
No, I thank you for prompt response and quick fix. Good luck in future development!
Title: Re: [APP] - version 2.7.X
Post by: bubak on December 05, 2012, 14:48:16
Google Play: Locus Pro 2.7.4 "... is incompatible with all of your devices."  HTC Desire S / Android 2.3. Really?
Title: Re: [APP] - version 2.7.X
Post by: gynta on December 05, 2012, 14:55:27
Hi
Unfortunately, this is currently a problem in google play
https://getsatisfaction.com/locus/topic ... y_xperia_s (https://getsatisfaction.com/locus/topics/pro_2_7_4_incompatible_with_sony_xperia_s)
Title: Re: [APP] - version 2.7.X
Post by: UKlocusfan on December 06, 2012, 21:27:47
Yep, Play wont let me have the new version either!  :-(