yashsingh1/xdaforums huggingface dataset:
[Xposed Framework Modules] scorpbull:
Thank you very much!! I was a big fan of KnockCode and was really missing it since I updated to MM. It works great for me. Thanks!!
[Xposed Framework Modules] RusherDude:
[MENTION=6065596]Rijul.A[/MENTION]

Just reporting. Been using this for severely days, 100% success on 6.0.1. It remains a mistery that bug I had before tho, don't know if you find a possible cause, it may lock people out of their phones :(.. but it works perfectly now.

Eaggerly waiting for some of the features we requested early hahaha :)
[Xposed Framework Modules] :
I will work on the features in a while, I am trying to add back the emergency call button. I realized that I use it frequently because it becomes a return to call button when a call is in progress.

And regarding your unreproducible error, I think I know why that happened. I am mitigating exactly that right now, with no loss or addition of functionality.
[Xposed Framework Modules] RusherDude:
Awesome!!! Thanks a lot!

And one more request: please support for long this module, even put the next features premium with some IAP if you think its fair! This module is brilliant and don't want it gettin abandoned again :crying::crying:
[Xposed Framework Modules] souler456:
Is this the process of installation? :

1. Active Xposed

2. Install module, then check it

3. Set-up a 3x3 pattern lock

4. Open module and enable it

5. Reboot finally

or :

3. Reboot first

4. Set-up a 3x3 pattern afterwards

5. Open module app and enable it

or anything goes? :confused:

Too scared to go wrong lol...

:D :) ;) :good:
[Xposed Framework Modules] :
If you're using a near AOSP ROM, both methods work fine. Earlier, you had to use the first one (because I screwed up), but now both will work.

You seem to be using Kitkat, it will not work on Kitkat.
[Xposed Framework Modules] souler456:
No, I already have the module enabled on KitKat (with the KitKat version of the module, of course), and I'm getting myself an upgrade to LP, so... Yeah... Better be cautious and stuff :eek:

Anyways, I see that the installation is still the same on KitKat, so, thanks for assurance man... :good:

:D :) ;) :good:
[Xposed Framework Modules] :
New update : Download from Repo, changelog on first page. Cheers!
[Xposed Framework Modules] Tyaginator:
I think its right there in changelog

Sent from a device using an app!
[Xposed Framework Modules] :
It's in the Xposed app's changelog in bold.

And it's in the first post of this thread.
[Xposed Framework Modules] snoopyhaeckers:
It doesn't work on HTC One e8 i can test it when can port it ...say what files you need I can send it

Gesendet von meinem HTC One_E8 mit Tapatalk
[Xposed Framework Modules] :
Xposed logs
[Xposed Framework Modules] Kiuren:
I have attached my Xposed logs for my HTC One M8 since it knock code doesn't work with my phone. Hope you get your knock code to work with HTC phones. If you need anything else, just let me know. :)
[Xposed Framework Modules] :
Turn off other modules and then send the log - this is too difficult to read
[Xposed Framework Modules] PHYCLOPSH:
After updating to the latest CM13 nightly, I can confirm that with 1.4.2 I am unable to unlock my LG G3 without disabling xposed. I'm falling back to an older version with pattern unlock to see if that works.
[Xposed Framework Modules] :
I checked with the latest CM source code, and I am unable to find any changes that would cause this. Can you reply back if an older version works?
[Xposed Framework Modules] PHYCLOPSH:
Nope older version doesn't help. I guess I'll blame this on CM, after several presses on the knock area the screen just goes black. For now it just sucks I can't use this.
[Xposed Framework Modules] :
Can you disable other modules and get back with a logcat? I may not be able to fix this immediately because I am outside my city, but it might help in diagnosis
[Xposed Framework Modules] PHYCLOPSH:
For now I have disabled my lock screen security. Thanks for looking in to this.
[Xposed Framework Modules] KronicSkillz:
try going back to June 18 nightly it's sometime after that an issue started. i don't know the exact date but i had the same issue with cm 13 nightlies lately i tried a few diff nightlies and going back to that one worked for me. ill try to figure out when it broke on my model which is lg g3 d852. ive tried stock mm with no issues and cm 13 had worked for a while except some of the recent nighties when ipinpoint the nightly I'll inform the developer... hopefully i can get my hands on all the nightlies

---------- Post added at 12:26 AM ---------- Previous post was at 12:20 AM ----------

i have same issue as him on recent g3 nightlies and I'm trying to pinpoint where it broke I'll let you know if i can I'm somewhat knowledgeable i have been involved in low end developement
[Xposed Framework Modules] PHYCLOPSH:
Thanks for the suggestion. The problem started for me after updating from the 26th or 27th nightly build. Unfortunately my most recent backup is from the beginning of the month and I don't really want to do that so hopefully it can be fixed another way.
[Xposed Framework Modules] KronicSkillz:
k i didn't have time to check all the nightlies yet ill start there then and see if i get the same result

---------- Post added at 12:12 PM ---------- Previous post was at 11:59 AM ----------

i can confirm it still works for me on the nightly from the 22nd and does not work on the nightly from the 26th however i haven't been able to find acopy of the nightly from the 25th and it's no longer on cm download page so that might be the best i can do. By the way you don't need a backup to roll back just boot to twrp and head to cmupdater folder. dirty flash the nightly you want to use then flash xposed then wipe cache. if you want you can backup your current install to be safe but cm nightly flash doesn't change your data partition. you only have to flash xposed again because it's stored on system partition.

---------- Post added at 12:21 PM ---------- Previous post was at 12:12 PM ----------

make sure you read my last edited post it should be a temporary solution for you unless you've already deleted those nightless then you might have to find someone with the same model as you that still has a copy of the nightly

---------- Post added at 12:34 PM ---------- Previous post was at 12:21 PM ----------

any chance it's related to their change to intents policy on the 25th. i don't know enough about your module but that's the only thing that stuck out to me when i was browsing the changelogs
[Xposed Framework Modules] :
If you could get me an Xposed log, I will be able to debug it. Other than that there's nothing I can do - I cannot update my phone's setup right now, because of work, and I can't make a new build, because my personal laptop is in another city
[Xposed Framework Modules] KronicSkillz:
k no problem i'll flash newest nightly and grab an xposed log, i thought he already sent you one. i'll disable all other modules too.

I see something interesting in today's nightly changelog.

"Revert" Only show keyguard panel if on lockscreen + no activity on top"

interesting to see if there is any different behavior now.

also yesterday they fixed an overlapping issue on keyguard as well.
[Xposed Framework Modules] :
Yeah, that one does not say anything relevant, so I thought asking for another might help.
[Xposed Framework Modules] KronicSkillz:
k no problem, i see some keyguard changes in last few changelogs, so maybe they fixed the issue i'll keep you posted. It could be a UI issue. If it still doesn't work i'll provide a log

---------- Post added at 12:54 PM ---------- Previous post was at 12:49 PM ----------

Here are the changelog changes i see that may be relevant.

since 29th

- Revert. "only show keyguard panel if on lockscreen + no activity on top"

- WindowAnimator: Check KEYGUARD_PANEL when deciding to show/hide window.

since 28th

- KeyguardSecurityViewFlipper: Fix sim unlock height overlap

still downloading newest nightly. looks like the problem may have been on their end though.

---------- Post added at 01:02 PM ---------- Previous post was at 12:54 PM ----------

in the interest of giving you a little more info as well. When the issue arose what would happen is when you swipe up to reveal keyguard, it would just be a blank screen, the grid didn't show up even with the lines turned on. even the long press to switch back to normal unlock method wasn't working, however it was overriding the original lockscreen. I think it was a UI issue. It's possible that's why there wasn't any relevant data in the logs, i think the functionality may have been there but the UI wasn't showing up or receiving input properly.
[Xposed Framework Modules] KronicSkillz:
K so i didn't read the other one but this doesn't look very helpful, do you want a logcat?

My process was:

- install newest nightly and xposed 85 framework

- disable other addons

- EDIT - forgot to mention that i cleared the xposed log here too

- reboot

- turn on knock code module and set keyguard to pin.

- turn screen off, module still shows blank semi transparent screen and a back button.

- could not get into phone so tried rebooting once.

- knock code still not showing up, tried putting in my knock code anyways and long pressing 5 times, neither worked.

- turned phone off

- went into twrp manually, reflashed newest nightly without xposed framework (to disable knock code so i can get into my phone and grab log).

- rebooted and grabbed log using stock pin keyguard.

let me know if you want me to try a diff process or same process with and grab logcat.

Here is the log cleaned up a bit.

01-24 02:40:05.733 I/Xposed

( 290): -----------------

01-24 02:40:05.733 I/Xposed

( 290): Starting Xposed version 85,

compiled for SDK 23

01-24 02:40:05.733 I/Xposed

( 290): Device: LG-D852 (LGE), Android version 6.0.1

(SDK 23)

01-24 02:40:05.733 I/Xposed

( 290): ROM: cm_d852-userdebug 6.0.1 MOB30M 1fa1d0d5a1 test-keys

01-24 02:40:05.733 I/Xposed

( 290): Build fingerprint: lge/g3_global_com/g3:5.0/LRX21R.A1421650137/1421650137:user/release-keys

01-24 02:40:05.733 I/Xposed

( 290): Platform: armeabi-v7a, 32-bit binary, system server: yes

01-24 02:40:05.733 I/Xposed

( 290): SELinux enabled: yes, enforcing: yes

07-01 13:28:18.065 I/Xposed ( 290): -----------------

07-01 13:28:18.068 I/Xposed

( 290): Added Xposed (/system/framework/XposedBridge.jar) to CLASSPATH

07-01 13:28:18.393 I/Xposed

( 290): Detected ART runtime

07-01 13:28:18.430 I/Xposed

( 290): Found Xposed class de/robv/android/xposed/XposedBridge, now initializing

07-01 13:28:18.655 I/Xposed

( 290): Loading modules from /data/app/me.rijul.knockcode-2/base.apk

07-01 13:28:18.772 I/Xposed

( 290): Loading class me.rijul.knockcode.XposedMod

07-01 13:28:40.838 I/Xposed

( 1195): [KnockCode] AOSPish Device
[Xposed Framework Modules] KronicSkillz:
I took the liberty of getting a logcat.

This was my process:

- reinstall xposed framework to re-enable module.

- reboot

- connect to adb via PC

- clear logcat with screen off

- turn screen on and attempt to use knock code (twice i think, second time using long presses)

- grab logcat.

I think this one may be more helpful i actually see some failed attempts at loading the lockscreen.

07-01 14:08:21.787 923 1113 E QCOM PowerHAL: Failed to acquire lock.

didn't read it all as I probably can't help you with this without knowing more about lock screens and see your source code.

Here you go thanks for the help and the great modules.

Let me know if i can be of any more assistance to you.
[Xposed Framework Modules] vink221:
Hey I've been using your module for some time (moto g 2014 titan ruining cm13) it seems your app doesn't work with the latest update of cm13 I'm running version 20160702 nightly but every time I use it nothing comes up on the lock screen I have the same with your gesture lock (I didn't use them at the same time) look forward to hearing from you
[Xposed Framework Modules] :
Yea, if you check the last page it is about complaints from some people. Right now the logs provided aren't very helpful, and I don't have my personal laptop with me, and I can't update my CM, so I am dropping support for CM until at least 23rd July.
[Xposed Framework Modules] KronicSkillz:
you have to roll back nightless until it works If you want to use it for now. then wait until plugin is updated to start getting new nighties
[Xposed Framework Modules] vink221:
I think I'll just wait till the plugin is updated.......I'd love if it gets done quickly I'm an avid user of this module

---------- Post added at 12:37 PM ---------- Previous post was at 12:33 PM ----------

That's fine....it's just a wait for some days I'll use the normal lock on cm in the mean time cause reformatting will be too much of a Hassel for me right now
[Xposed Framework Modules] StarKiller2100:
I find a bug

Hello , I found a bit annoying bug which is that after activating the module in Xposed , enter the patron knock and reboot , the screen to enter the knock pattern does not appear, only the navigation bar appears, I have put the pin code in the system security settings. tried it on a Moto G3 with the rom Resurrection remix and after upgrading to the latest version of the ROM and reinstall the Xposed module and I noticed the fault.

I hope this module solution that I love !! :D
[Xposed Framework Modules] nicesoni_ash:
For the love of God, just read few last pages before reporting a bug.

Sent from my "i9300/1+2" powered by Carbon/RR

Fueled by 7000mAh ZeroLemon Battery
[Xposed Framework Modules] jackeagle:
Thread Reopened.

jackeagle

Forum Moderator
[Xposed Framework Modules] Tyaginator:
You're Back in Business!
[Xposed Framework Modules] folusmile:
Not working for Samsung note 4 after upgrading to MM.
[Xposed Framework Modules] :
Logs?
[Xposed Framework Modules] :
Yes, got to update my ROM at last! And look, I have my first useless Bug report already!
[Xposed Framework Modules] Lazerus625:
Just want to say app is great and I appreciate your continued support!
[Xposed Framework Modules] Tyaginator:
I checked the latest version, working great so far!
[Xposed Framework Modules] MrBrowseGierza:
Too bad 2 consecutive updates are both not working on my LG G3. I downgraded back again to 1.4.1.

Both 1.4.2 and 1.4.3 are useless, I'm running CM12 5.1.1 ROM anyway.
[Xposed Framework Modules] :
1. Relax

2. Logs - I don't have the same ROM or phone as you. I can not randomly guess what is wrong and fix it. If you are comfortable using the old version, feel free to complain about it and not provide logs. If you want it to fixed, please give me logs so I can understand what is up. Make sure to disable other modules though.
[Xposed Framework Modules] MrBrowseGierza:
Im good with the old one. Thanks for this superb app anyway as long as the previous version reach my expectations it's my best option to keep it.
[Xposed Framework Modules] Teblakuda4o4:
I have a Blu life one X and the last two update aren't working. Also the working one is stuck I. Full-screen.
[Xposed Framework Modules] loldroid:
Is there a knock Code for device wipe, so if my phone is stolen and someone puts in 1234 the phone is wiped?
[Xposed Framework Modules] folusmile:
Ver 1.4.1 work for me..
[Xposed Framework Modules] Teblakuda4o4:
Yeah v1. 4.1 is the best... Thx for your hard work
[Xposed Framework Modules] Jpigas:
Not working on my oneplus one

When I was on CM13 (6.0), I downgrade to 1.4.1 and I solved it; but since last update to CM13.1 (6.0.1), 1.4.3 is still not working and 1.4.1 crashes my phone, so I have to unninstall xposed. Any ideas? Thanks.
[Xposed Framework Modules] rpadula:
I would like to translate your module to Portuguese, how can I help?
[Xposed Framework Modules] Imissrengar:
Hi I need help asap!! I tried this on my phone (samsung galaxy j7) and now I am stuck on the lockscreen. How do I get out of this??
[Xposed Framework Modules] yakie996:
why does 1.3.5 feels so much faster than the latest versions?
[Xposed Framework Modules] yakie996:
moto x style xt1572 android 6.0.1 xposed 86 when first putting the pin code in its all stretched and after that the keypad from knock on is placed in the left upper corner as seen in the screenshots
[Xposed Framework Modules] Tyaginator:
Cuz after 1.3.5 there was a major change in animations. You can customize it by yourself.

Disable wait for last tap and choose appear and disappear animation time as you find suitable
[Xposed Framework Modules] bharatram95:
This module is nt working with cm13 august 13 build or later... I enabled d module n rebooted my device, bt wat i got is neither knockcode lockscreen nor my device's normal lockscreen... I luvd dis module very much... Please make it compatible wid latest cm builds too...
[Xposed Framework Modules] yakie996:
aint nobody needs slow animations... if i set it to 0 its a ugly transition...
[Xposed Framework Modules] :
My laptop is broken (again). Can't make updates right now. Please wait for a while.
[Xposed Framework Modules] J117N:
i used this module for a while i had little problems like it turning into landscape for no reason, today for some reason when i go into the lockscreen pattern i see no lines and when i click anywhere nothing happens im stuck in the lockscreen and there is no other way (as far as i know) to unlock the phone, my only idea that this happend is because im running out of storage, i tried turning it to safe mod still the same please help
[Xposed Framework Modules] mavambu:
Hey everybody, I really appreciate this app but I got one bug on my phone, when I fail 5 times to put in the knock code, the device tell me this.

Thank to everyone for the help!
[Xposed Framework Modules] Tyaginator:
You can disable show dialog on too many attempts
[Xposed Framework Modules] mavambu:
I disabled it but it didn't work
[Xposed Framework Modules] StarKiller2100:
a question

As I put the remaining seconds when unlocking failure 5 trials as pictured ??

Thanks since now
[Xposed Framework Modules] nicomedian:
hi, i can not pass the lock screen after installing this. phone starts, i slide to open the pattern password screen but only blurred screen with < button appears. LG G2 D802

i can not use the phone, what should i do?
[Xposed Framework Modules] nicesoni_ash:
Go into recovery and remove apk file from data/data/

Also to make it work, you need to set up pin not pattern in latest version.

Sent from my "1+2" powered by Unofficial RR

Compiled by myself.
[Xposed Framework Modules] losiukit:
But what if I accedentially deleted the whole file?

I am using G3 and is having the same issue as #635

I just deleted the whole file but each time I reboot the file appear again but with nothing again and the issue is still bothering me.

Thank for your help.
[Xposed Framework Modules] nicesoni_ash:
Remove data/app/me.rijul.knockcode folder, that will do the trick.

Sent from my "1+2" powered by Unofficial RR

Compiled by myself.
[Xposed Framework Modules] n00b0rKa:
Hello Devs!

The module was working like charm for a year or so now on my N7100, but I recently installed Ivan Meler's latest update for his CM13 (http://xdaforums.com/galaxy-note-2/orig-development/rom-cyanogenmod-13-0-n7100-t3267758), and the screen only keeps on flashing (turning on and off), and it even deleted my background image (idk what it has to do with it). Anyway, I had to get it out of this loop by deleting the config from recovery. I tried to just install it and turn it on with a pattern set (and not pin), same issue. Note that it worked with earlier versions of this very same ROM. I'm running the latest version of xposed (both flashable and apk) .
[Xposed Framework Modules] n00b0rKa:
Installed version 1.4.3 with high hopes, forgot to change to pin but turned the module on, restarted and the exact same thing happens. :(
[Xposed Framework Modules] :
I am back people. Pushed a new version up to the repo right now. Downloading latest CM now to see if it works (just read through the last two posts!)
[Xposed Framework Modules] :
It's because now I am emulating the animations from AOSP/CM's pattern unlock wherein the upper dots / rows go first slowly and the others follow with a faster speed. Looks far better.
[Xposed Framework Modules] yakie996:
to be honest I liked 1.3.5 more but I adjusted to the latest version ?
[Xposed Framework Modules] :
Still works for me - if it doesn't work for you, give me logs. From now on, bug reports without logs will be blatantly ignored.
[Xposed Framework Modules] n00b0rKa:
1.4.4, still the same bug as I described on the previous page :S what logs do you exactly want? My phone does not even start with it...
[Xposed Framework Modules] :
Connect to your laptop, enable module, reboot, and type in the command line

adb logcat *:E > logcat.txt

Then attach logcat.txt here / paste contents on hastebin.com
[Xposed Framework Modules] MrBrowseGierza:
The three consecutive updates didn't work for me. I'm stuck with 1.4.1 restart keyguard on the app cannot be found.
[Xposed Framework Modules] MeAliY2K:
Does not recognize touches.

Am on cm13-nightly on Oneplus X.

The problem is that when using a 2x2 knock code, the upper two adjacent portions does not register my "knocks", lower two seems to be working fine. The problem gies away when I reboot, but it negates the whole point of using a knock code. To quickly unlock the phone.
[Xposed Framework Modules] :
Check out v1.4.5 beta, you guys are in for a surprise!

EDIT : Thanks to [MENTION=5222551]Maxr1998[/MENTION]'s original implementation
[Xposed Framework Modules] n00b0rKa:
I'm back:D It throws some nice exceptions, but you'll surely understand a lot more of it. File attached.
[Xposed Framework Modules] :
Can you disable other modules and then take a logcat, starting as soon as the phone boots up? This one doesn't have anything related to my module as far as I can see.

adb logcat -s Xposed
[Xposed Framework Modules] n00b0rKa:
I saw some exceptions thrown by your module. I only have greenify and your module. The log is right after reboot, as I said the screen flashes and it does not display anything besides the background. When I get home I will try to find the related lines and upload the log you requested.
[Xposed Framework Modules] :
I've uploaded V1.4.6 beta with sensitivity option for relative taps, please do test it out and let me know the level which works for you guys. I've noticed it to be inversely correlated with the grid size, so I will likely keep it an option in the final release.
[Xposed Framework Modules] n00b0rKa:
Here you go. All other Xposed modules disabled, the newest beta version of yours running (or crashing :D). Log attached
[Xposed Framework Modules] :
Still nothing in there

adb logcat *:E

maybe?
[Xposed Framework Modules] n00b0rKa:
What I attached you earlier was an error filtered log, but here is a new one.

Maybe this part is causing the problem:

10-26 16:09:01.278 7248 7248 E AndroidRuntime: java.lang.IllegalStateException: Unable to create layer for KeyguardMessageArea
[Xposed Framework Modules] :
Are you using a CyanogenMod theme? Can you use the default one and try again if yes?
[Xposed Framework Modules] n00b0rKa:
I'm using the default CM theme. Should I download a custom one?
[Xposed Framework Modules] :
No. Let me get back to you on this. My module does not touch the crash causing class at all, I don't understand why it won't work.

Are you using a large font size? Can you reduce it and try if yes?
[Xposed Framework Modules] n00b0rKa:
I understand. My font size is the basic one. I have 2 ideas what could cause the problem:

1. I reduced the original DPI (320 I think) to 260 (which is the phone's physical DPI), however I've been using it like this with older versions of this ROM, and it worked

2. I installed the latest version of XPosed, which is 3.1

Thank you for your help!
[Xposed Framework Modules] :
Getting back to you with a version for this, please wait.

In the meanwhile, I have figured out a major flaw in the relative coordinates implementation, which manifests itself at larger grid sizes. As a result I am reconsidering its inclusion.