Just wanted to give everyone an update as to where we are.
First, we’re interested in getting a breakdown of how many people are experiencing the battery drain issue. Hopefully if you were seeing the drain, then you’ve had a chance to test the 1.0.4 release with the option to disable Cell Tower Monitoring. Please let us know how many people are affected by the battery drain by voting at our poll http://www.findmycarsmarter.com/forum/viewtopic.php?f=4&t=42. Voting will take you less than a minute and no registration is required. We need both users who are and are not affected by this issue to vote as this will help us determine the prevalence of this issue.
We have made some progress in replicating the battery drain issue ourselves. As we mentioned in our last update we thought the issue was our usage of the Cell Tower Monitoring service interacting with another app or service. One of our backers, Gary, made a great suggestion of developing an app that only enables Cell Tower Monitoring to prove that this alone would cause the drain. We did this and found that when we ran both the Cell Tower Monitoring app & Find My Car Smarter simultaneously we also intermittently saw the battery drain problem that some of our users are reporting. The drain issue seemed to persist for an hour, then clear itself out, and then randomly come back again. We still haven’t found a reliable method to trigger this issue yet. We believe that when Find My Car Smarter and another app both make systems calls to Apple's CoreLocation service, some interaction between them causes these battery drain issues. We have been trying to break the problem down to smaller pieces by creating two simple apps that make CoreLocation calls and will reliably reproduce this failure, but so far we haven't found the recipe yet. We are still working on it though.
So this discovery leads to two thoughts. First, this explains why only some people see the issue, rather than the issue being related to the carrier or location as we initially thought. It looks like the issue is more a factor of which apps users have installed on their phones. Second, unfortunately, this also means that forthcoming iOS 5.1 will not magically fix this issue as we had initially hoped since we also saw this battery drain on iOS 5.1 Beta 3 Developer Preview.
To prove that the issue is actually caused by the interaction of multiple apps using CoreLocation as we believe, we’re looking for a few volunteers willing to wipe their phone. We understand this is a huge imposition so we’re offering a small bounty. More information is here: http://www.findmycarsmarter.com/forum/viewtopic.php?f=8&t=46&p=130
We have gone through about 50 logs sent in from users. We can only log activity that happens within our app. They all show similar results and we don’t see any indication that our app is misbehaving. Again, we believe the battery drain happens outside of our app at the system level in CoreLocation which we cannot monitor.
If anyone has any suggestions of apps they think in combination with Find My Car Smarter reliability causes this drain, please drop us a note so that we can investigate.
For the 1.1 update, the code is complete. We’ll be testing it out this week and fixing any bugs we encounter. The update will be submitted to the AppStore by the end of the week and Apple typically takes another week to approve. If anyone is interested in beta testing, please send us an email with your UUID. We're also interested in collecting the UUIDs for people experiencing the battery drain issue, in case we have a battery drain test build.
The updates in 1.1 are as follows:
Automatic Parking Meter Notification
Manual Parking Meter Notification
Manually update your parking location
Low GPS Signal Notification
Hybrid Mapping modes
When driving to a new location, the title bar will read Enroute rather than showing the previous parking location.
Made the title bar clearer, indicating parked duration