Bug 6922 - Higher battery use in 5.2.13 and possibly higher versions
Summary: Higher battery use in 5.2.13 and possibly higher versions
Alias: None
Product: iOS
Classification: Xamarin
Component: XI runtime ()
Version: 5.2
Hardware: Other Other
: --- normal
Target Milestone: Untriaged
Assignee: Bugzilla
Depends on:
Reported: 2012-09-05 10:19 UTC by Dean Cleaver
Modified: 2016-02-17 18:53 UTC (History)
3 users (show)

Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.

Please create a new report on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:

Description Dean Cleaver 2012-09-05 10:19:24 UTC
In testing for our new production release, my testers noted a significant drop in battery life. Testing our current production app (compiled and submitted 31 July on 5.2.12) gave about 7:40 battery life before the phone died. Testing 5.2.13 yeilded only 5:40 battery life.

We are currently trying to test 5.3.6 (latest beta version) but I don't have the results yet. The above results have been repeated about 6 times though.

I will post more information when I have it.
Comment 1 Dean Cleaver 2012-09-05 15:36:59 UTC
Results with 5.3.6 were 6:21 minutes - better than 5.2.13, but well below 5.2.12.

Anything else I can provide?
Comment 2 Rolf Bjarne Kvinge [MSFT] 2012-09-05 17:07:07 UTC
Do you have a test case (or even your entire project)?
Comment 3 Dean Cleaver 2012-09-06 00:32:57 UTC
Rolf - the entire project is pretty precious to the startup I work for - do you have an NDA (or is our NDA ok with you guys) basically to protect us with regards to giving you our codebase?

I spoke to the CEO at length, and he's keen to help you guys find this fault as we're committed to MonoTouch, but he wants protection for us from the investors etc.
Comment 5 Dean Cleaver 2012-09-10 14:21:43 UTC
Request sent to support last Friday - no response thus far.
Comment 6 Dean Cleaver 2013-01-09 09:41:59 UTC
Using Instruments to check CPU use, it seems that calling UIDevice.CurrentDevice.BatteryMonitoringEnabled = true causes an increase in CPU activity, even if you have no notifications registered or do not actually monitor the battery. Did something change in this area of MonoTouch from 5.2.12 to 5.2.13?
Comment 7 Rolf Bjarne Kvinge [MSFT] 2015-03-05 09:13:56 UTC
Dean, did this issue get resolved?
Comment 8 Rolf Bjarne Kvinge [MSFT] 2016-02-17 18:53:54 UTC
Closing since no response to comment #7.

If this is still an issue, maybe you could attach any Instruments data (in comment #6 you say you profiled for CPU use with Instruments, that might reveal something)?