This object is in archive!
Allow more time between live tracking updates
Declined
In 3.16.0 the maximum time between live tracking updates is 300s or 5 minutes. Why so short? To minimize data charges and increase battery life, this arbitrary limit could be much higher. For example SPOT tracker and BUBBLER app allow 1 hour updates, which for some users is completely sufficient.
I like this idea 
This suggestion can be deleted. Appears that 300s limit in beta has been removed. For example I can now enter 3600s = 1 hour.
This suggestion can be deleted. Appears that 300s limit in beta has been removed. For example I can now enter 3600s = 1 hour.
As long as live tracking is stopped any update value can be entered, eg. 3600. However when I attempt to start live tracking the value must be <= 300, so my original suggestion still stands.
As long as live tracking is stopped any update value can be entered, eg. 3600. However when I attempt to start live tracking the value must be <= 300, so my original suggestion still stands.
Ah is is definitely an issue, limit is really set to 300s,
Reason is, that your location is then visible to other users - this is what's live tracking is about. And usage should be to see one hour old location of your friend? Currently, after five minutes, your location is no more visible to other users (it's set up on our server).
So question is, does a saved one percent of battery per day make a sense? Because service still needs to run on background (so no CPU is saved) and send data are really really small (you may check on your device on your own).
Ah is is definitely an issue, limit is really set to 300s,
Reason is, that your location is then visible to other users - this is what's live tracking is about. And usage should be to see one hour old location of your friend? Currently, after five minutes, your location is no more visible to other users (it's set up on our server).
So question is, does a saved one percent of battery per day make a sense? Because service still needs to run on background (so no CPU is saved) and send data are really really small (you may check on your device on your own).
Fair points. I will do some testing. Similar to SPOT service maybe you can consider fast live tracking only available to PRO users, and slower live tracking for FREE users. Just an idea.
Fair points. I will do some testing. Similar to SPOT service maybe you can consider fast live tracking only available to PRO users, and slower live tracking for FREE users. Just an idea.
Thanks for idea. I anyway wants to bring as much people to live tracking as possible, that's why this is available also in Free.
Anyway please test data traffic during usage. I believe you will see that it is really low. Anyway small warning. Traffic depends on number of active users (logically, you have to receive these information to display them on a map), so it may grow over time, when more users will be active.
Anyway I'm still convinced, that one hour reporting is out of purpose of locus-based live tracking service.
Thanks for understanding.
Thanks for idea. I anyway wants to bring as much people to live tracking as possible, that's why this is available also in Free.
Anyway please test data traffic during usage. I believe you will see that it is really low. Anyway small warning. Traffic depends on number of active users (logically, you have to receive these information to display them on a map), so it may grow over time, when more users will be active.
Anyway I'm still convinced, that one hour reporting is out of purpose of locus-based live tracking service.
Thanks for understanding.
Locus mobile data traffic yesterday is 256KB. I only had mobile data enabled for a short time so Locus could send one live tracking update. It seems quite high. Data is recorded as "foreground". I can't tell exactly what the data contained. Map was in Tasmania/Australia, so I don't believe traffic includes other active users. Will do identical test today.
Locus mobile data traffic yesterday is 256KB. I only had mobile data enabled for a short time so Locus could send one live tracking update. It seems quite high. Data is recorded as "foreground". I can't tell exactly what the data contained. Map was in Tasmania/Australia, so I don't believe traffic includes other active users. Will do identical test today.
I was testing it today and in average were active 5 users, who send data around 1 kb. So 256 kb should be over longer period or there were some more tasks on background. Hmm login to Locus Store at start takes some more bytes etc.
I'll watch it as I'm well aware that data traffic is really really important. When number of active users grow a lot and traffic starts to be quite high, I'll definitely work on it and one option is to increase this time/refresh interval. For now, I'm anyway not a big fan of this solution.
I was testing it today and in average were active 5 users, who send data around 1 kb. So 256 kb should be over longer period or there were some more tasks on background. Hmm login to Locus Store at start takes some more bytes etc.
I'll watch it as I'm well aware that data traffic is really really important. When number of active users grow a lot and traffic starts to be quite high, I'll definitely work on it and one option is to increase this time/refresh interval. For now, I'm anyway not a big fan of this solution.
Replies have been locked on this page!