You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cordova.apache.org by "Paul R. (JIRA)" <ji...@apache.org> on 2012/12/05 19:27:58 UTC

[jira] [Created] (CB-1968) Camera use changes idleTimerDisabled timeout

Paul R. created CB-1968:
---------------------------

             Summary: Camera use changes idleTimerDisabled timeout
                 Key: CB-1968
                 URL: https://issues.apache.org/jira/browse/CB-1968
             Project: Apache Cordova
          Issue Type: Bug
          Components: iOS
    Affects Versions: 2.2.0
         Environment: Xcode 4.5.1 on Mac OSX 10.7.5

            Reporter: Paul R.
            Assignee: Shazron Abdullah
            Priority: Minor
             Fix For: 2.1.0


I used application.idleTimerDisabled = YES in my didFinishLaunchingWithOptions routine in AppDelegate.m to keep the application from sleeping, but now using the camera resets that when using capture video, and my app now goes to sleep and times out during file transfer.

Ran some tests and here's what I found:

- in Cordova 2.1.0 & 2.2.0, WITHOUT "application.idleTimerDisabled = YES" in AppDelegate.m, both devices go to sleep after 1 minute (which is what my phone's auto-lock is set to)
- in Cordova 2.1.0, WITH "application.idleTimerDisabled = YES" in AppDelegate.m, the device goes to sleep after 5 minutes
- in Cordova 2.2.0, WITH "application.idleTimerDisabled = YES" in AppDelegate.m, the device goes to sleep after 1 minute

As stated by Shazron in http://issues.apache.org/jira/browse/CB-1962 this should not be a Cordova API issue, which makes sense as AppDelegate is not part of the Cordova library. But what is causing this change then?


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (CB-1968) Camera use changes idleTimerDisabled timeout

Posted by "Paul R. (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/CB-1968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Paul R. updated CB-1968:
------------------------

    Description: 
I used application.idleTimerDisabled = YES in my didFinishLaunchingWithOptions routine in AppDelegate.m to keep the application from sleeping, but now using the camera resets that when using capture video, and my app now goes to sleep and times out during file transfer. I'm assuming the Camera object employs it's own idleTimerDisabled to keep the phone from sleeping while it's recording, and then upon exit sets it back to false, overwriting my setting.

Ran some tests and here's what I found:

- in Cordova 2.1.0 & 2.2.0, WITHOUT "application.idleTimerDisabled = YES" in AppDelegate.m, both devices go to sleep after 1 minute (which is what my phone's auto-lock is set to)
- in Cordova 2.1.0, WITH "application.idleTimerDisabled = YES" in AppDelegate.m, the device goes to sleep after 5 minutes
- in Cordova 2.2.0, WITH "application.idleTimerDisabled = YES" in AppDelegate.m, the device goes to sleep after 1 minute

As stated by Shazron in http://issues.apache.org/jira/browse/CB-1962 this should not be a Cordova API issue, which makes sense as AppDelegate is not part of the Cordova library. But what is causing this change then? Can anyone shed some light on this?


  was:
I used application.idleTimerDisabled = YES in my didFinishLaunchingWithOptions routine in AppDelegate.m to keep the application from sleeping, but now using the camera resets that when using capture video, and my app now goes to sleep and times out during file transfer.

Ran some tests and here's what I found:

- in Cordova 2.1.0 & 2.2.0, WITHOUT "application.idleTimerDisabled = YES" in AppDelegate.m, both devices go to sleep after 1 minute (which is what my phone's auto-lock is set to)
- in Cordova 2.1.0, WITH "application.idleTimerDisabled = YES" in AppDelegate.m, the device goes to sleep after 5 minutes
- in Cordova 2.2.0, WITH "application.idleTimerDisabled = YES" in AppDelegate.m, the device goes to sleep after 1 minute

As stated by Shazron in http://issues.apache.org/jira/browse/CB-1962 this should not be a Cordova API issue, which makes sense as AppDelegate is not part of the Cordova library. But what is causing this change then?


    
> Camera use changes idleTimerDisabled timeout
> --------------------------------------------
>
>                 Key: CB-1968
>                 URL: https://issues.apache.org/jira/browse/CB-1968
>             Project: Apache Cordova
>          Issue Type: Bug
>          Components: iOS
>    Affects Versions: 2.2.0
>         Environment: Xcode 4.5.1 on Mac OSX 10.7.5
>            Reporter: Paul R.
>            Assignee: Shazron Abdullah
>            Priority: Minor
>             Fix For: 2.1.0
>
>
> I used application.idleTimerDisabled = YES in my didFinishLaunchingWithOptions routine in AppDelegate.m to keep the application from sleeping, but now using the camera resets that when using capture video, and my app now goes to sleep and times out during file transfer. I'm assuming the Camera object employs it's own idleTimerDisabled to keep the phone from sleeping while it's recording, and then upon exit sets it back to false, overwriting my setting.
> Ran some tests and here's what I found:
> - in Cordova 2.1.0 & 2.2.0, WITHOUT "application.idleTimerDisabled = YES" in AppDelegate.m, both devices go to sleep after 1 minute (which is what my phone's auto-lock is set to)
> - in Cordova 2.1.0, WITH "application.idleTimerDisabled = YES" in AppDelegate.m, the device goes to sleep after 5 minutes
> - in Cordova 2.2.0, WITH "application.idleTimerDisabled = YES" in AppDelegate.m, the device goes to sleep after 1 minute
> As stated by Shazron in http://issues.apache.org/jira/browse/CB-1962 this should not be a Cordova API issue, which makes sense as AppDelegate is not part of the Cordova library. But what is causing this change then? Can anyone shed some light on this?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira