knock on feature focus-20140308-024-6

LG’s Knock Code functionality has been popular lately, we’ve even dedicated a full feature focus video for it. The feature is something many of us would like on our other Android devices. Thanks to a new Xposed module over in the XDA forums, you can now use Knock Code to unlock your device.

The Knock On-style functionality of this Xposed module has its limitations. For starters, it only operates on the device lock screen, for the purpose of unlocking the device. No word if they’ll be adding the ability to launch apps. It currently only works on Android 4.4, and will never be made to work on devices pre-4.2. Lastly, unlike LG’s original Knock functions, the Xposed module will not work with your screen turned off.

Should you use Knock Code to unlock your device?

There are different schools of thought on the security benefits and disadvantages of using a Knock Code as a means to secure your Android device. In the end, Knock Code uses a simple 2 x 2 grid, within which you assign a tap configuration to unlock your device. To my mind, this essentially restricts you to the characters 1, 2, 3 and 4 to create a secure pass code, which would require a significant length before becoming unguessable.

Knock Code Xposed Module

Another important item to be aware of, the Xposed module requires the file containing your specified knock code to be readable by any app on your device. Developer MohammadAG assures us that the file is encrypted, but that only offers so much security these days.

In conclusion, Knock Code functionality using this Xposed module brings a very cool feature to your Android device. However, like some other device unlocking techniques, this may just be a passing fad, a novelty to show off to your friends running iOS 8, with their new widgets and all that.

This module has been floating around for a bit, have any of you tried it out? Will you?


Jonathan Feist
Android purist and enthusiast, rarely more than arms reach from a stock Nexus 7. Often accused of being a Google fanboy, proud of it. Proponent for Android customization and personalization, if you can change it, make it your own!
  • Bradley Uffner

    I don’t understand why this was written as an Xpose module. Surly it would have been quicker, easier, more secure, and more compatible to do it as a standard lock screen?

    • avyfa

      Cause this module need special core permissions that can be used only with modified core.

      • Bradley Uffner

        It sounds like it’s nothing more than a 4 button keypad. Is there some feature I’m missing that requires special permissions?

        • avyfa

          Always enabled touchscreen need extra permissions, like Google now, that always listen to you(but google apps can do everything on android).

          • Bradley Uffner

            Ahhh. So it still listens for touch events even when the screen is off? That’s the part I was missing. Thank you for clearing that up.

          • My1

            no that’s not the fact, it’s on only. but with the xposed module it directly replaces your pattern lock and cannot be circumvented, even if they did know how to disable xposed, since the pattern you set before enabling the mod will be in place.

            Also 3rd Party Lockscreens have the point that they can be killed more or less simply which means that they can be circumvented by accident, while the mod hooks itself into the lockscreen which also in the end looks more “native”…

  • Hellz

    if i cant wake my phone up i dont need it

  • Albin

    Touch screens are sensitive instruments and phones are expensive. Swiping is non-destructive but even tapping consistently in one spot is not. “Knockin” sounds like a way of battering a delicate device to early death, “knocking its block off”.

    • Steve Brain

      Sure if you’re “knocking” it with a hammer perhaps.
      Phones are built to last mate, only the cheaper (Chinese) ones would break by simply tapping on the screen. Hell probably not even Chinese phones are that poorly constructed.