This object is in archive!
Error during picking up the photo for a point
Solved
Im doing these steps:
- starting Locus
- clicking on one point
- clicking on Edit/Photo/Pick
- QuickPic ( alternative app for Android Gallery) is starting
- clicking button Back Arrow to exit from QuickPic OR choosing a photo ( both scenarios are ending in the same way)
- getting back to Locus
- encountering Force Close Error
https://dl.dropbox.com/u/4747589/Locu...
The same error is occuring when Im choosing Edit/Photo/Take, whenever Im taking a new photo or Canceling the choose process.
https://dl.dropbox.com/u/4747589/Locu...
Additional question in my case: Previous state dialog is loading very long, but after a few times its faster. Why?
The same problem 
ah them this do not happen before?
thanks for logs. There is visible simple reason. Locus was terminated probably by system, so when photo returns from QuickPic, Locus is starting again from scratch and because there do not exists any waypoint to which attach photo, Locus crash.
May you try in "menu > settings > global > locus as a service". This may help on this case. When you now "Take" new photo, Locus start a background service to help keep it alive during this action. I added same system also on "Pick" photo, so this should help. Till now, "Locus as a service" should be solution
-------------------
previous state loading - it just depend on fact, what data is Locus restoring during a start. If there is any auto backup etc ... as you know for sure :)
ah them this do not happen before?
thanks for logs. There is visible simple reason. Locus was terminated probably by system, so when photo returns from QuickPic, Locus is starting again from scratch and because there do not exists any waypoint to which attach photo, Locus crash.
May you try in "menu > settings > global > locus as a service". This may help on this case. When you now "Take" new photo, Locus start a background service to help keep it alive during this action. I added same system also on "Pick" photo, so this should help. Till now, "Locus as a service" should be solution
-------------------
previous state loading - it just depend on fact, what data is Locus restoring during a start. If there is any auto backup etc ... as you know for sure :)
oki, there is not too much to do
1. as I wrote above, I added small service that run on background and that should help to keep Locus alive
2. if Locus is closed by system, then after return with (or without photo), instead of crash, you should see this
thanks for report!
oki, there is not too much to do
1. as I wrote above, I added small service that run on background and that should help to keep Locus alive
2. if Locus is closed by system, then after return with (or without photo), instead of crash, you should see this
thanks for report!
1. "previous state loading - it just depend on fact, what data is Locus restoring during a start. If there is any auto backup etc ... as you know for sure :)" - but, during the tests of this issue, I restarted a Locus a few times after the Force Close, and sometimes the Previous state process take longer time, sometimes shorter ( with exactly the same state of the Locus ). Anyway, what takes so long time? Can you read that from logs?
2. When running as a service, there is no errors:) Cool. Thanks
3. By accident I discovered a new issue. After a crash, when I returned to Locus, the previous state was not saved. Points and tracks which were visible, dissapeared. So it looks like, state is not preserved because of the Force Close.
1. "previous state loading - it just depend on fact, what data is Locus restoring during a start. If there is any auto backup etc ... as you know for sure :)" - but, during the tests of this issue, I restarted a Locus a few times after the Force Close, and sometimes the Previous state process take longer time, sometimes shorter ( with exactly the same state of the Locus ). Anyway, what takes so long time? Can you read that from logs?
2. When running as a service, there is no errors:) Cool. Thanks
3. By accident I discovered a new issue. After a crash, when I returned to Locus, the previous state was not saved. Points and tracks which were visible, dissapeared. So it looks like, state is not preserved because of the Force Close.
Im happy I could help
Im happy I could help
1. hmm, no, it`s not visible in log. It should be visible on dialog on which step, Locus spent most time. For example if you`re restoring 1000 caches, it should take few second or two, maybe little bit more. Same for tracks, some other map items etc ...
2. fine :)
3. it`s more then possible. State is stored when locus is correctly closed. So try to avoid these for closes :))
1. hmm, no, it`s not visible in log. It should be visible on dialog on which step, Locus spent most time. For example if you`re restoring 1000 caches, it should take few second or two, maybe little bit more. Same for tracks, some other map items etc ...
2. fine :)
3. it`s more then possible. State is stored when locus is correctly closed. So try to avoid these for closes :))
ah also to point 1. Vector maps consume quite a lot of CPU, so if you start Locus with vector maps, it should take longer then with basic online or personal map. Just for you info. Current map tiles are loading together with restoring previous state, that`s the reason
ah also to point 1. Vector maps consume quite a lot of CPU, so if you start Locus with vector maps, it should take longer then with basic online or personal map. Just for you info. Current map tiles are loading together with restoring previous state, that`s the reason
Im not using vector maps very often, so this in not the case. but thanks for info
Im not using vector maps very often, so this in not the case. but thanks for info
Can you look what happened here?
https://dl.dropbox.com/u/4747589/2012...
I was adding two photos, and then trying to fill the Name of that point, and locus stopped to respond. And the system ask me if I want to wait or force close the application. Wait option didn`t do anything.
Can you look what happened here?
https://dl.dropbox.com/u/4747589/2012...
I was adding two photos, and then trying to fill the Name of that point, and locus stopped to respond. And the system ask me if I want to wait or force close the application. Wait option didn`t do anything.
Shit. I tried to start Locus after the previous crash, and I got this screen, visible forever...
https://dl.dropbox.com/u/4747589/2012...
https://dl.dropbox.com/u/4747589/2012...
Shit. I tried to start Locus after the previous crash, and I got this screen, visible forever...
https://dl.dropbox.com/u/4747589/2012...
https://dl.dropbox.com/u/4747589/2012...
Replies have been locked on this page!