iOS 4.1 Bug Fix- Passcode Lock now working properly!

Discussion in 'iPhone' started by zub3qin, Sep 1, 2010.

Most Liked Posts
  1. zub3qin, Sep 1, 2010

    zub3qin macrumors 65816

    zub3qin

    Joined:
    Apr 10, 2007
    #1
    For those that were made miserable by the Passcode lock bug on iPhone 4.0, I am pleased to report that 4.1 fixes this.

    Traditionally if you set a passcode lock, you also pick a time amount before you have to enter the code. Thus if you pick 5 mins, you can turn the screen off, and if you turn it on again anytime before 5 minutes, you don't have to type in the code.

    The bug was that this time-out was deactivated. So in 4.0, with passcode lock on, even if you try and turn the screen back on in 2 seconds of turning it off, you have to enter the unlock code.

    4.1 is BACK TO NORMAL!!!!!
     
    share
    + Quote Reply
  2. chembox, Sep 1, 2010

    chembox macrumors 6502a

    Joined:
    Feb 17, 2010
    #2
    I didn't notice this since I always have mine set to ask for it immediately. :cool:

    Is the sacrifice worth the protection of privacy? Probably not.
     
    share
    + Quote Reply
  3. sinsin07, Sep 1, 2010

    sinsin07 macrumors 68040

    Joined:
    Mar 28, 2009
    #3
    Glad it's working for you. I never had this issue. Did not even know it was an issue.
     
    share
    + Quote Reply
  4. geko29, Sep 1, 2010

    geko29 macrumors 6502

    Joined:
    Nov 10, 2008
    #4
    This bug wasn't present on my 3GS with 4.0, and is not on my iP4 with 4.0 or 4.0.1. My timeout is set to 5 minutes, and works just fine.
     
    share
    + Quote Reply
  5. zub3qin, Sep 1, 2010

    zub3qin thread starter macrumors 65816

    zub3qin

    Joined:
    Apr 10, 2007
    #5
    My stance is that it would be very unlikely that within 5 minutes of you shutting off your screen, your phone would be stolen and turned on.

    It probably is more like 2 hours...
     
    share
    + Quote Reply
  6. bmwhd, Sep 1, 2010

    bmwhd macrumors 6502a

    bmwhd

    Joined:
    May 22, 2008
    #6
    Was not an issue on any of my test phones under 4.0, 4.0.1, or 4.0.2
     
    share
    + Quote Reply
  7. ItsJustafnPhone, Sep 2, 2010

    ItsJustafnPhone macrumors 6502a

    Joined:
    Jul 26, 2010
    #7
    nope no issue here

    running 4.0, running exactly as it should
     
    share
    + Quote Reply
  8. zeeflyboy, Sep 2, 2010

    zeeflyboy macrumors regular

    Joined:
    Apr 25, 2009
    #8
    The problem largely seemed to stem from doing a "reset all settings" and when using a gmail account.

    In the absence of a security stipulation from gmail it defaulted to the most secure (password lock immediately)... there was then no way to change it, even deleting all the email accounts didn't work.

    Happened to me and it was seriously annoying. There was a work around posted that involved loading a profile onto the phone, but in the end I decided just to set up as a new phone to avoid the problem.

    Nice to know it's fixed now at least.
     
    share
    + Quote Reply
  9. bigspooon, Sep 9, 2010

    bigspooon macrumors newbie

    Joined:
    Jun 24, 2010
    #9
    Finally!!

    Yah, the previous poster pretty much summed up what caused this error. I'm so happy to hear it's fixed. I'm upgrading tonight. I didn't want to sacrifice my security so I just had the passcode lock turn on immediately but it was such a pain - especially while driving.
     
    share
    + Quote Reply
(You must log in or sign up to post here.)

Share This Page