Currently Being ModeratedNov 9, 2013 12:08 AM (in response to Lacer)
If your phone locks during a call, it is grossly malfunctiong and has nothing to do with iOS 7, I have had conversations over 3 hours long with no locking, as the vast, vast majority eperience.
What troubleshooting steps have you taken (reset phone, reset settings, restore iOS using backup, restore as new)? Was your phone EVER jailbroken?
Currently Being ModeratedNov 12, 2013 10:46 AM (in response to modular747)
Lacer is right on with his description of the issue. My iPhone5 locks after 15 minutes due to corporate policy, whether on a phone call or not. I have not found a setting on the iPhone to keep phone unlocked when call is active.
As a remote employee, I am on conference calls all day long, switching from mute and speaker. Once the phone locks after 15 minutes, I'm not able to find a way to return to phone call without typing in passcode.
This is a bit of an issue when i am unexpectedly asked a question and it takes me mutliple seconds to unmute the conference call. "buhler, buhler".
With iOS6, all the phone controls available when the iphone was locked, it was a simple swipe and tap to unmute.
If anyone figures out a gesture or configuration setting I'm overlooking that would be extremely helpful.
Currently Being ModeratedNov 13, 2013 7:34 AM (in response to rudderless)
I'm having the same issue. When on long con calls for work, having to enter the passcode (corporate policy) to end call or mute/unmute is a challenge...especially since I'm in the car frequently. I did find one work around that is certainly not ideal but beats entering the passcode. If I swipe up to view the Control Center, and then hit the calculator or timer, the green call bar appears at the top of the screen. Once you hit that call bar you are back at your call menu. Like I mentioned....still combersome but depending on how long your passcode is, it may be a bit faster. I'm hopeful Apple gives us a long term fix soon.
Currently Being ModeratedNov 13, 2013 7:57 AM (in response to modular747)
So, "modular" I still can only assume you are under 30 (at least I hope so given the nature of your responses here) but I am hopeful you are learning a valuable lesson. When arrogance and ignorance intersect you reveal yourself to be an ***. As in this case when your ignorance of the issue being expreienced by many users and your arrogance of being a "level 6" did not allow you to consider you might be wrong. Keep that in mind for your day to day interactions with people. May be a more important lesson and "raising of your game" in life.
Currently Being ModeratedNov 13, 2013 8:16 AM (in response to Apple\'s Perfect Record Is Over)
You're completely clueless about both my age (I'm a good deal older than you) and that there are "many" others claiming an iOS 7 issue locking phones during a call.
Maybe if you had completed the 6th grade, you could count the number posting in this thread. If your reading comprehension skills weren't equally as challanged, you would have understood that the last 2 posters' phones were being locked by "corporate policy" that was provisioned into their phones, not an iOS 7 bug.
Currently Being ModeratedNov 13, 2013 10:58 AM (in response to modular747)
Point of clarity as it relates to my earlier reference to "corporate policy". My employers policy has not changed, but the user experience from iOS6 to iOS7 has. I had no problem accessing in-call options from a locked screen with iOS 6. iOS 7 requires the user to enter the passcode and unlock before in-call options appear. So yes, this has to do with users that are bound to "corporate (security) policy", but it's a change that Apple made and will hopefully fix.
Currently Being ModeratedNov 13, 2013 1:33 PM (in response to ssmstl)
I know several people with corporate configured security on their iOS 7 phones who don't have any problem accessing call options, just like with standard iPhones when calls are received or made (via Siri) on locked phones.
Your problem may be that your IT dept didn't update their iPhone Configuration Utility for iOS 7, or it was implemented incorrectly. Did you take this up with your IT dept?
Currently Being ModeratedNov 13, 2013 7:23 PM (in response to modular747)
Could we please refrain from polluting the thread with needless bickering and name calling.. If you disagree please do so calmly and rationally.
While the previous two posters might be able to trace their issue back to corporate policies, I personally can't. My iPhone is personal. When I receive a call and my screen locks out, I have to log back in (no longer something that bothers me given TouchID) in order to get back to the call screen. This doesn't happen when I initiate the call, only when I receive the call.
In iOS 6, when I received a call, the screen would still time out based on my auto-lock setting; however, a simple click of the home button would bring the call controls back up, without the need to enter my password. While I can understand limiting access to contacts if you received a call while locked, the other functions (mute, dial pad, etc) should still be accessible.
This might not be a bug, but if it isn't, I would certainly love to know what configuration I'm using that is causing the problem. If it's neither a bug or configuration issue, but is in fact a change in the fundamental way the feature works, then.. Oh well. That's why I started this thread... If it's a bug - great, I'll wait for a fix. Configuration issue? Tell me how to fix it! Fundamental, intended change? Well **** - I'll use the form I can access up yonder to send Apple a message... Can anyone confirm one of these possibilities?
Currently Being ModeratedNov 14, 2013 9:08 PM (in response to Moregelen)
I am new to iPhone and using in a corporate environment with a policy of time out and passcode.
During almost all calls, the phone locks (I always use a bluetooth headset if this makes any difference). When I want to end of the call, I have to unlock the phone first entering a passcode.
If I wait long enough, the other party ends the call for me.
My phone is brand new, 3 weeks old it was loaded with iOS6 then I upgraded to iOS 7 and updated to 7.0.3.
It has never been jail broken.
I tried pressing the power button as suggested by Modular, this doesnt work either.
Currently Being ModeratedNov 14, 2013 9:14 PM (in response to Lacer)
Irrespective of anything, my 2 iPhones (5s&5c) and on all my previous iPhones I have been on the phone for maybe 1-2hours, never had any locking occur...........
It may need a Reset and then a reconfiguration of your personal settings.............
Currently Being ModeratedNov 15, 2013 10:37 AM (in response to elmac)
This isn't any issue with anyone's particular device. We have 5 or 6 people on the thread saying the same thing.
- A company issued iphone, not jailbroken, on corporate policy locks phone after x minutes (15min in my case) irrespective of whether on a call or not. Large corporations with 35,000 employees globaly typically put these type of restrictions in place. The iphone is replacing the blackberry in many corporations... A blackberry BES server would have traditionally managed this.
- In IOS6, the phone would lock, but the glowing green "return to call" bar was available at top of screen to return to call without typing in passcode.
- When IOS7 was released, it took away the ability to access this glowing green "return to call" bar while the phone is locked. No one has been able to pinpoint any configuration on the device that may have been modified by IOS7 to cause this behavior. I've combed through all the settings and cannot find anything.
- The reason that typing in the passcode is more than an annoyance... is that while on a conference call listening on mute and you need to quickly respond to a question... you have to first type your passcode, which might cause a 10 second delay in your response. Not muting is not an option for remote employees who are conference calls 5 hours a day. Additonally, typing the passcode to end a call is bothersome, although there are workarounds for this.
Currently Being ModeratedNov 15, 2013 10:48 AM (in response to rudderless)
Yet there are many people I know with corporate security locking who don't experience this issue with iOS 7. This suggests that there may be an error in the way the phone was configured by your IT department.
The problem could be the iPhone Configuration Utility settings used by your IT dept - there are no settings on the device itself for this. The configuration utility was updated when iOS 7 was released. If your company didn't update, that may be the source of the problem.
Since this is a user-to-user support forum and Apple doesn't follow these threads, I suggest you report this to Apple:
Currently Being ModeratedNov 15, 2013 12:34 PM (in response to modular747)
I dont think it has anything to do with corp security. There is a "passcode lock" under "general" in "settings". I'm not sure if this was an option in iOS 6 (vs the standard "auto-lock" which is what corp security requires), but mine was set to require a password after 5 mins. I changed it to an hour and it now allows me to access in call options without entering the password.
Currently Being ModeratedNov 15, 2013 12:43 PM (in response to ssmstl)
The passcode lock setting as you describe has been there since iOS 1. In fact, coporate security configuration usually requires passcodes and removes that setting to disable it in configured phones.
If it wasn't there in your corporate iOS 6 but is there now, it means that the configuration was done incorrectly for iOS 7. You really should be using a passcode to protect your data. You really, really need to discuss this with your IT dept.
Message was edited by: modular747
Currently Being ModeratedNov 21, 2013 5:53 AM (in response to rudderless)
At the risk of offering myself up as troll food, I too have exactly the same issue described. I too have a corporate security policy. I am currently investigating which version of the config tool my IT dept are using and hoepfully that will resolve the issue.
(in the meantime, I like the 'airplane mode' hack! - works for me so thanks to the OP)