When Locus is being turned off?
Hi.
Please tell me, in what circumstance Locus is really being turned off?
I`m using Locus as a service, and during an active geocaching/travelling day (Track Record always on), I need to start Locus many times ( 5-7 times per day), and every time I need to wait around 40-50 second until all tracks and points are loaded in a welcome (white) screen. Which is realllly annoying.
And now, I want to kill Locus on purpose, to reload it fully (by pressing HOME for long time and then swiping Locus thumbnail to the left (Android 4.3). Locus is disappearing from a list of active applications. But then, when running a Locus again, everything is loaded already, I don`t need to wait for anything - Locus is fully operational.
So I`m lost at that point. Why when I don`t want Locus to be dead - it is. But when I want him dead - it is alive. I thought it might be a matter of native Android memory/processes cleaning (killing unnecessary applications to regain memory), but if so, isn`t it the same killing as is the one after clicking on HOME button?
1. How to kill Locus when I need to kill it? ( For example for testing/debugging purposes).
2. How to fully prevent Locus from being killed?
The same question
Answer is quite simple. Only way to close Locus completely, is by back button on map screen and confirming exit (if enabled in settings)
All other cases means, that Locus were killed by system.
- you`re waiting 50 in first, completely white screen?? Then it cannot be caused by loading previous state, but by something different. First white screen should take max few seconds, all other loading should be in loading dialog with empty map on background.
- swipping app in list of running processes (by long click on home button), do not kill these apps!! I know it from testing, that it really just remove it from list. Seems that nothing more ...
- to questions
1. best is from applications menu in system settings and here under Locus is button "Force stop"
2. only way that may help is to enable "Locus as a service". This may help at least little bit. Otherwise reduce number of running apps or purchase device with more RAM :)
Answer is quite simple. Only way to close Locus completely, is by back button on map screen and confirming exit (if enabled in settings)
All other cases means, that Locus were killed by system.
- you`re waiting 50 in first, completely white screen?? Then it cannot be caused by loading previous state, but by something different. First white screen should take max few seconds, all other loading should be in loading dialog with empty map on background.
- swipping app in list of running processes (by long click on home button), do not kill these apps!! I know it from testing, that it really just remove it from list. Seems that nothing more ...
- to questions
1. best is from applications menu in system settings and here under Locus is button "Force stop"
2. only way that may help is to enable "Locus as a service". This may help at least little bit. Otherwise reduce number of running apps or purchase device with more RAM :)
Eh. Like I thought:(
I`m waiting 50s when I`m starting Locus ( during loading of all tracks, points, maps and so on), sometimes is better - 30 seconds. I don`t know why this time is changing. Anyway, it is pain.
1. Can you add a new function to Locus: "Force EXIT"? Which will exit Locus even when all these Live tracking and Track recording features are turned ON. I think it can be useful sometimes.
2. Yes. RAM. And my old Desire Z. True. When I will start my job in CR, I promise you, I will buy something good to handle thousands of my points and tracks. And I can already imagine how many of them I will add during traveling through your country:) To be honest, Locus is running on my device in about 75% of its whole uptime ( besides nights when I sleep ). It is a primary application on my device. I even have a dedicated Locus button ( camera button remapped to start Locus ).
Eh. Like I thought:(
I`m waiting 50s when I`m starting Locus ( during loading of all tracks, points, maps and so on), sometimes is better - 30 seconds. I don`t know why this time is changing. Anyway, it is pain.
1. Can you add a new function to Locus: "Force EXIT"? Which will exit Locus even when all these Live tracking and Track recording features are turned ON. I think it can be useful sometimes.
2. Yes. RAM. And my old Desire Z. True. When I will start my job in CR, I promise you, I will buy something good to handle thousands of my points and tracks. And I can already imagine how many of them I will add during traveling through your country:) To be honest, Locus is running on my device in about 75% of its whole uptime ( besides nights when I sleep ). It is a primary application on my device. I even have a dedicated Locus button ( camera button remapped to start Locus ).
I always run Locus "as a service" and so I always have Locus available instantly, no map loading stuff etc.
I always run Locus "as a service" and so I always have Locus available instantly, no map loading stuff etc.
yes, but on your device is not a problem with RAM as on Desire Z. When system has low amount of ram, it kill apps on background to make some RAM free. "Locus as a service" may help here, but not forever. When there is no free RAM and system needs any, even a service should be killed
yes, but on your device is not a problem with RAM as on Desire Z. When system has low amount of ram, it kill apps on background to make some RAM free. "Locus as a service" may help here, but not forever. When there is no free RAM and system needs any, even a service should be killed
hmm during a start, you everytime see scaning of all maps? If so, this means that some map cannot be initialized, because this should happen only once when some map change.
ad 1), sorry, but I don`t think it should be too useful. But agree that closing dialog should be improved. Nice example is Navigation, where you may choose to end navigation or minimize. It should be in same way for all special features (track record, etc...)
hmm during a start, you everytime see scaning of all maps? If so, this means that some map cannot be initialized, because this should happen only once when some map change.
ad 1), sorry, but I don`t think it should be too useful. But agree that closing dialog should be improved. Nice example is Navigation, where you may choose to end navigation or minimize. It should be in same way for all special features (track record, etc...)
Of course, it only has 512MB RAM.
But the service will help to protect Locus and kick out other apps before Locus will be killed.
Of course, it only has 512MB RAM.
But the service will help to protect Locus and kick out other apps before Locus will be killed.
exactly. But even a 512 is sometimes not enough. If elmuSSo has enabled locus with a lot of tracks, it may take up to 50 MB, sometimes more. System itself took maybe 200 MB and few more apps and, voala ... OutOfMemory ...
exactly. But even a 512 is sometimes not enough. If elmuSSo has enabled locus with a lot of tracks, it may take up to 50 MB, sometimes more. System itself took maybe 200 MB and few more apps and, voala ... OutOfMemory ...
Ok, but even if Locus is being killed automatically, track recording is still alive. Everything works in a background like charm. I need to observe its behaviour more carefully and note in what circumstances it is going OFF.
You said: "If elmuSSo has enabled locus with a lot of tracks," - do you mean by that that I have lots of tracks visible on the screen or just that I have them saved in Locus database?
Ok, but even if Locus is being killed automatically, track recording is still alive. Everything works in a background like charm. I need to observe its behaviour more carefully and note in what circumstances it is going OFF.
You said: "If elmuSSo has enabled locus with a lot of tracks," - do you mean by that that I have lots of tracks visible on the screen or just that I have them saved in Locus database?
I think he means tracks ticked for being displayed as there is no RAM necessary for those only lying in the database only.
I think he means tracks ticked for being displayed as there is no RAM necessary for those only lying in the database only.
This was very helpful for me! I always thougt, that Locus is still in memory when I use END in question, because I see it still in the list.
This was very helpful for me! I always thougt, that Locus is still in memory when I use END in question, because I see it still in the list.
Replies have been locked on this page!