|
| profile
until
it
see
|
|
 |
|
 |
profile until it sees the cell IDs within the time range, but does that mean that it won’t dleesect outside that time range? I assume from what you say it does.Yes, it will dleesect during that time if it hears any cell id not belong to @Work location. Or in other words if you move away from @Work earlier it will dleesect.For the cell ID sequence, what I mean is, suppose I have a loud profile that I want set when I am in my local town. My problem is that the cells there are sometimes visible from my home. It is possible that my phone will want to change from @Home profile to @Town profile when I’m at home.Another possibility would be if the location could be identified by seeing all of the cells instead of 1 out of say 4.Ok, now I see.. Yes, if you have some cells visible in both location that is the problem. Requiring _all_ cells to be visible before triggering location will not solve the issue, since it will delay or event prevent location detection correctly. What I think might help is some noise threshold, i.e. requiring at least 2 cells to trigger in that location and another 2 foreign cells to trigger it out.. We will add this as configurable item in future version, so you can experiment and let us know if it improves usage experience
|
 |
|
 |
|
|
|
|
|
|
(VISITOR) AUTHOR'S NAME
Benoit
MESSAGE TIMESTAMP
16 december 2014, 19:01:32
AUTHOR'S IP LOGGED
166.149.236.72
|
|
|
|
