00:28 rknLA joined #geoloqi
00:35 brennannovak joined #geoloqi
00:46 brennannovak joined #geoloqi
06:04 brennannovak joined #geoloqi
08:09 blk joined #geoloqi
08:51 brennannovak joined #geoloqi
09:25 blk joined #geoloqi
09:57 starbuckt joined #geoloqi
10:14 rknLA joined #geoloqi
10:19 kenichi joined #geoloqi
10:33 brennannovak joined #geoloqi
11:15 patrickarlt joined #geoloqi
12:49 ronaldv joined #geoloqi
12:53 <ronaldv> Hello, I'm using the Titanium module with iOS and was wondering if you're using "significant location change" or implemented your own battery saving algorithm and how they compare to each other?.
12:57 <rknLA> ronaldv: I can't speak directly for them, but I'd wager their battery saving involves jumping from "monitor location" to "significant location change" and using "monitor region" when appropriate.
12:58 <rknLA> though it's worth noting that monitor region is such an annoying piece of crap in it's natural iOS 5.x state.
12:58 <aaronpk> ronaldv: yes rknLA is correct, it will use whichever is more appropriate given the current conditions
12:59 <aaronpk> and yes, we have not had the best of luck with using region monitoring directly, so we have some workarounds built in for that as well
13:11 <ronaldv> Ok sounds good. Well I can't say I'm very surprised about region monitoring being a pain.
13:13 <rknLA> "You should always be judicious when specifying the set of regions to monitor. Regions are a shared system resource and the total number of regions available systemwide is limited. For this reason, Core Location limits the number of regions that may be simultaneously monitored by a single application." >_<
13:14 <aaronpk> with no mention of any numbers to give any indication of the limits of course
13:14 <rknLA> and that sentence is still in the iOS 6 docs, so hope is at an all-time low.
13:18 <ronaldv> I came across a post a while ago of someone saying it was 10. Although I have no idea of where that is based upon.
13:22 megome joined #geoloqi
13:24 meglome joined #geoloqi
13:26 d7___ joined #geoloqi
13:29 <rknLA> i saw rumors of that on stack overflow. the only real way to test it is by trying it out and making sure all of the other apps with geo are closed or have geo disabled in settings.. even then, it's not terribly practical to know the number since apple doesn't guarantee anything.
13:29 <rknLA> you just have to use the error callback and behave accordingly.
13:35 <ronaldv> My best guess is that the number probably depends on the available resources(CPU, memory) and the amount the device needs to run smoothly. If that is the case they probably aren't going to change anything in the documentation.
13:36 <ronaldv> Which means it is never going to be easy to develop around.
13:41 <rknLA> yeah... it's just a tease. they should be able to at least guarantee you like, 10 regions per app or something.
13:41 <rknLA> it's not _that_ much memory.
13:41 <rknLA> probably more cpu than memory
14:07 rknLA joined #geoloqi
14:12 kenichi joined #geoloqi
15:17 brennannovak joined #geoloqi
17:42 rknLA joined #geoloqi
18:31 patrickarlt joined #geoloqi
18:48 rknLA joined #geoloqi
19:03 starbuckt joined #geoloqi
23:33 brennannovak joined #geoloqi