ScaredyCat
-
8 votesScaredyCat
commented
·
Except that means we can't have wifi and gps turned off and Google pretty much use this same mechanism for their location service when both gps and wifi are off (but there is a 3g/edge/grps data connection but only for lookup) - Have a look at work referencing http://www.google.com/glm/mmap .
Incidentally GSM Cells have a limited range of 34.65km (63 × 550m) ~= 21.53 Miles - this is a technical limitation and in a best case scenario. The overlap of cell id's and LAC's are useful because we use the combination to represent locations. I appreciate that with will never be as fine grained as GPS or even wfi positioning, but there are times when that level of detail is not required. You could even think of it as a precursor to starting services etc. For example, coming into range of a preset group of cell id's and lac's might indicate that you are approaching home and so turn on wifi so that when you do get home you don't need to wait (at most) 10 minutes for the next check by Locale.
Your goal for using the UI to set location isn't going to be halted by this, all you need to do is allow the user to set the location (as per gps) and then look at the cell id's and LAC's for that location at that time.
ScaredyCat
commented
·
An additional application go gather cell-id/LACs from a location may be usefule, or this functionality could be added to the Locations app.
ScaredyCat
shared this idea and gave it 2 votes
·
-
4 votescompleted ·
AdminCarter
(Admin, two forty four a.m.)
responded
Locale 1.0 offers significantly improved location detection that should solve the problem of exiting and re-entering location-based situations. (If the app is terminated and relaunched, settings will still be re-applied)
Locale 1.0 is available on the Android Market today in countries that support paid apps. Full release notes are here: http://www.twofortyfouram.com/notes.html
ScaredyCat
commented
·
Hi Carter,
how about this http://feedback.androidlocale.com/pages/5655-locale-feedback/suggestions/196651-add-cell-id-lac-as-a-condition to help sort that problem out then?
ScaredyCat
shared this idea and gave it 1 vote
·
-
103 votescompleted ·AdminCarter
(Admin, two forty four a.m.)
responded
Locale 1.0 adds a new condition: the Orientation condition. The orientation condition supports detecting when the phone is lying face up or face down.
Locale 1.0 is available on the Android Market today in countries that support paid apps. Full release notes are here: http://www.twofortyfouram.com/notes.html
ScaredyCat
gave this 2 votes
·
-
262 votesScaredyCat
gave this 2 votes
·
-
44 votescompleted ·AdminCarter
(Admin, two forty four a.m.)
responded
This has been implemented by the “Inbound SMS Plug-in” plug-in condition for Locale 1.0. To find this plug-in on the Market, simply open Locale and choose Get Plug-ins from the menu.
ScaredyCat
gave this 1 vote
·
-
46 votesScaredyCat
commented
·
Would be nice if it could deal with https and also deal with ignoring https certificates (if the user particularly wanted).
ScaredyCat
gave this 1 vote
·
-
263 votescompleted ·AdminCarter
(Admin, two forty four a.m.)
responded
UPDATE:
Locale 1.4 includes significant improvements to the location detection system, reducing time to detect location changes by 20% while also improving battery usage by up to 50%.
The original goal of this request—reducing the delay of detecting location changes—has been met as Locale 1.4 detects location changes within an average of 4 minutes. We are therefore marking this request as completed.
Although this request is being marked as completed, we have ongoing research and development to keep improving the speed and efficiency of the location detection system further :).
(Original response)
By design, Locale has no user-configurable options. The goal is that Locale should “just work” without requiring users to fiddle with various options that could negatively impact the operation of the app. For example, asking Locale to check location every minute could cause the battery to drain within 2 hours at which point you might miss the… more
ScaredyCat
gave this 3 votes
·
ScaredyCat
commented
·
I agree the polling interval for GPS should not be hard coded the user should be allowed to decide how often this should happen. It might be worth having a warning that battery life may decrease but the user should still get to decide, not the developer :)
Theres a pretty good paper on this here : http://repositorium.sdum.uminho.pt/bitstream/1822/6223/1/Locare%20-%20camera%20ready%20version.pdf