• Your favorite

    Apple

    ,

    iPhone

    ,

    iPad

    ,

    iOS

    ,
    Jailbreak
    , and
    Cydia
    site.
  • 'SkipLock' Lets You Bypass the Lock Screen Unless You Have a Passcode or Notifications


    When you don't have a passcode on your device, the lock screen can be pretty pointless. The lock screen is really only useful when you are actually using it to "lock" your device with a passcode.

    With that being said, you can bypass the lock screen completely, as long as you don't have a passcode or any pending notifications, with a new free jailbreak tweak called SkipLock by iOS developer Filippo Bigarella.

    With this tweak installed, when you go to wake your device up, you'll be immediately taken to the home screen instead of the lock screen. With one less step to get into your iOS device, you're ready to begin using your device the moment you wake it up.

    If you have a passcode, or use Touch ID on an iPhone 5s, the tweak will not bypass your lock screen for security reasons. Also, if you have any pending notifications that you haven't read yet, you will still see the lock screen prior to unlocking the device so that you can acknowledge those notifications without forgetting about them.

    SkipLock's dynamic foundation of being able to sense if you have a passcode or notification, as well as creating convenience for the user, makes it a handy tweak for the average iOS device user. If you want to give the tweak a try, it's available in Cydia's BigBoss repository for free. SkipLock doesn't have any options to configure.

    Name: SkipLock
    Price: FREE
    Version: 0.9-6
    Requirements: iOS 7.0-7.0.4
    Repo: BigBoss
    Developer: Flippo Bigarella
    Editor's Rating:  5/5
    This article was originally published in forum thread: 'SkipLock' Lets You Bypass the Lock Screen Unless You Have Pending Notifications started by Anthony Bouchard View original post
    Comments 5 Comments
    1. Nichonico's Avatar
      Nichonico -
      So I'm guessing this is an exact equivalent to 'NoLockScreen', except NoLockScreen is for any iOS except 7.0+, and Skiplock is only for 7.0+?

      Let me know if I'm wrong
    1. DubbaCTrumpetMSU's Avatar
      DubbaCTrumpetMSU -
      Quote Originally Posted by Nichonico View Post
      So I'm guessing this is an exact equivalent to 'NoLockScreen', except NoLockScreen is for any iOS except 7.0+, and Skiplock is only for 7.0+?

      Let me know if I'm wrong
      I think that's pretty much it. Though, to me, it seems like it would create issues of pocket/pants/purse dialing if it hits the home button. Or if it even keeps hitting it and waiting for the screen off time, it would waste battery.
    1. Jahooba's Avatar
      Jahooba -
      Tried this on an iPod Touch 5, iOS 7.0.4 and it doesn't seem to work. I still get the lockscreen.
    1. Shigoroku's Avatar
      Shigoroku -
      I wouldn't call it "useless" for those without a password or PIN code. It keeps you from interacting with your phone by accident while the phone is in your pocket. In blue jeans, it's very possible / likely that the top button will be pressed while it's in your pocket. Accidental interaction is a big problem with iOS 7 because the phone accidentally unlocks when I'm specifically trying to avoid doing that (just flipping it to look at the screen, for example). I *really* wish I could go back to the pre-iOS 7 slider.

      ...but I did disable the lock screen on my HP TouchPad and I would do the same on a stay-at-home iPad if I had one.
    1. Nichonico's Avatar
      Nichonico -
      Quote Originally Posted by DubbaCTrumpetMSU View Post
      I think that's pretty much it. Though, to me, it seems like it would create issues of pocket/pants/purse dialing if it hits the home button. Or if it even keeps hitting it and waiting for the screen off time, it would waste battery.
      It all depends on the screen timeout... if you wanted to you could set it to 10 seconds. Chances are very slim for your leg to push the home button, then open the phone app, then call a person. In the 2+ years I've used this app, I've never had this problem.