yashsingh1/xdaforums huggingface dataset:
[Nexus 5X Q&A, Help & Troubleshooting] rskyline:
And yes I'm using 6.0.1 right now but it doesn't seems to get any T-Mobile band 12 around here! Also how do you do to get your 5x to work on sprint? I tried to activate mine on boost and then sprint and the guys over there told me that I needed to buy a phone from them.
[Nexus 5X Q&A, Help & Troubleshooting] EeZeEpEe:
Just went to a service repair Sprint store. They knew exactly what to do because they received a corporate memo. The guy even showed me it on the screen. Says what SIM to use because they're very specific. This was back in October right when the phone launched.
[Sprint  Galaxy Note 4 Q&A, Help & Troubleshooting] EpicBarbecue:
It says i do not have permission to access....how would i fix that?
[Sprint  Galaxy Note 4 Q&A, Help & Troubleshooting] ianmb:
Access what exactly?

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

Access what exactly?
[Sprint  Galaxy Note 4 Q&A, Help & Troubleshooting] EpicBarbecue:
Samsung dm manager.....i guess its a secret service menu.but when i try to access it it will not let me
[Sprint  Galaxy Note 4 Q&A, Help & Troubleshooting] jhill110:
Its samsung's download manager. There's nothing to access for users. It handles among other things updates such as prl and profile. If you were to freeze it you couldn't update those.
[Sprint  Galaxy Note 4 Q&A, Help & Troubleshooting] EpicBarbecue:
Oh ok....i thought it was something else......the menu where you press *#0011# and then Q then 0000....i cant access that menu...is there a way to fix it or what?
[Android Apps and Games] besoeasy:
A Simple Game Inspired From Don't Touch The Spikes

Tap And Slide To Keep The Little Bird Up, From As Long As You Can

Download : https://play.google.com/store/apps/details?id=com.besoeasy.dropup

OPEN SOURCE . Requesting Any Of You To Contribute !
[Galaxy S6 Q&A, Help & Troubleshooting] shotgun10ga:
Can i use the option nand erase all in odin? If not someone please provide me with a pit file for my S6 SM-G920W8. I cannot flash boot loaders and anything else besides twrp.
[Galaxy S6 Q&A, Help & Troubleshooting] batuzai04123:
You need to have same or newer bootloader version for your phone. Thats all.
[Galaxy S6 Q&A, Help & Troubleshooting] shotgun10ga:
Galaxy S6 Flat SM-G920W8 Flashing Error. Nand Write Start, FAIL! I dont know what top do,

My question is if i can flash G920F's Modem and Bootloader on my G920W8?

And why does it not say nand write start fail when i am flashing twrp?
[Galaxy S6 Q&A, Help & Troubleshooting] batuzai04123:
why are you trying to flash a g920f to g920w8???

You should use the same firmware for your phone to prevent issues.

Rrgarding with your last 2 posts, it is contradicting, you mentioned you cannot flash anything besides twrp, but you followed it that you failed in flashing twrp.

If you encountered with flashing firmware, I suggest to use a G920W8 firmware that is latest. I assume you are using an old firmware. Tell us your current and your firmware you are flashing.

Where did you get the twrp version? Are you sure it is not corrupt? A valid ODIN file? .md5 or .tar?

You need to give us more details in your issues.
[Galaxy S6 Q&A, Help & Troubleshooting] elomarpereira:
Nand write start fail

I have solved using Odin3 v3.10.7 with firmware VZW-G920VVRU4BOK7-20151211140939 and Windows 7 for Galaxy S6 SM-G920V
[Galaxy Tab 3 Q&A, Help & Troubleshooting] howcanidothis2:
Hi, im totally new to this kind of things, and i hope you can help me. I have searched for many tutorials for my device, and found a lot. The most recommended solution was to get the cf autoroot file and do the odin stuff, i think you know what i mean. But before i start on a tutorial, i have gone to the official chainfire site and theres the sentence "if you have locked bootloaders, flashing one of these will probably brick your device".

The thing is, most of the tutorials who recommended chainfire doesnt say a thing about the bootloaders, and the others have something like "after you have root acces with cf, you can unlock the bootloader by...". To be honest, i dont know exactly if my bootloader is locked. The servicenumber doesnt work. My Tab is from Telekom (germamy) and show a branding when turn it on.

So what should i do? Whats the savest way to get my tab rooted? What are the facts on this, apart from my bad englisch? Thanks for reading, hope you can help!
[Galaxy Tab 3 Q&A, Help & Troubleshooting] howcanidothis2:
Cant anybody help?
[Xposed Framework Modules] Rijul.A:
This Xposed module enables LG's knock code for Lollipop and Marshmallow devices . The knock code is highly customizable, from changing colours to visibility, error messages, background, etc. You can even hide the emergency button.

What's more, you can use codes to directly open specific shortcuts from the lockscreen, for example use 11212 to unlock, 221 to open WhatsApp, 111 for email, etc. These shortcuts don't have to be just apps, they can be anything on your device, like Direct Dial, open a specific Contact, etc. You even have the option to launch these shortcuts without unlocking the phone! (Requires App Settings Xposed, link available in app)

The module is pretty self explanatory, and will prompt you to set a pattern on the lock screen, because that is what it replaces. Other than that, there are no specific instructions to use it. Should the module or Xposed be disabled for any reason, your phone will still remain secure with that pattern.

Compatibility :

I personally test on CM13, and I will support CM12.0, CM12.1, AOSP 5.x and 6.0.x and derivatives. HTC support is limited unless I find a tester. Support for other OEM ROMs is absent beyond basic working functionality.

The only caveats are because of the way Xposed works.

A. Your code(s) will be visible to any one or any app on your device. No root required. The codes are stored encrypted, but anybody determined to get them will be able to, provided they can lay hands on your device. One way to avoid this is to disable USB debugging to prevent chances of a local exploit.

B. You need root to restart the keyguard after changing the full screen option. It is not mandatory, you could manually reboot if you require. All other changes will be reflected automatically, but not this one.

Tags (ignore) : knock lock screen exposed xposed xda tuesday unlock tap full screen fullscreen lockscreen shortcut custom quick launch pattern pin protected pinned authentication dual two factor rijul ahuja

XDA:DevDB Information

KnockCode Lockscreen, Xposed for all devices (see above for details)

Contributors

Rijul.A, MohammadAG

Xposed Package Name: me.rijul.knockcode

Version Information

Status: Abandoned

Current Stable Version: 1.3.0

Stable Release Date: 2016-03-25

Created 2015-12-17

Last Updated 2017-08-15
[Xposed Framework Modules] Rijul.A:
Reserved

FAQ

Does this work with screen off?

No, that is device specific and I can't implement it without having a device in hand, and even then, it is beyond my abilities.

Module does not work at all

Give me logcat, SystemUI.apk or any other lockscreen.apk which your device uses, I will try to implement it.

Some features, particularly emergency button related, do not work

Give me logcat, SystemUI.apk or any other lockscreen.apk which your device uses, I will try to fix it, but if it gets too difficult to manage because of your OEM ROM, it will not be done.

I am stuck on the lock screen, please help!

Long press the buttons 5 times. Your stock pattern will be restored.

I would like to contribute

Thanks! File a pull request on Github

I would like to contribute by translating your app and I can work with Github

Thanks! File a pull request

I would like to contribute by translating your app and I don't know Github

Thanks! Download the strings.xml file from here and translate away. Upload the contents on hastebin and send me the link with the language.

CM / HTC / Xperia / TouchWiz support?

Works on some HTC, Xperia and TouchWiz devices and not all features work properly.

CM is supported before 20th June nightly I believe.
[Xposed Framework Modules] Rijul.A:
Reserved

Screenshots

Knock Code Entry

[IMG="Knock Code Entry in Fullscreen"]https://raw.githubusercontent.com/Rijul-A/Xposed-Knock-Code/master/screenShots/lockScreen.jpg[/IMG]

Custom shortcut selection

[IMG="Custom Shortcuts"]https://raw.githubusercontent.com/Rijul-A/Xposed-Knock-Code/master/screenShots/customShortcutSelector.jpg[/IMG]

Some settings

[IMG="Settings"]https://raw.githubusercontent.com/Rijul-A/Xposed-Knock-Code/master/screenShots/someSettings.jpg[/IMG]

More screenshots
[Xposed Framework Modules] Rijul.A:
Changelog

1.3.1

If you didn't previously update to 1.3.0, please uninstall your old version before updating.

- Better colour handling for dots

- Bugfix from incorrect dots implementation

1.3.0

Please uninstall app, it has been entirely remade from scratch

- Size reduction

- Add option to launch shortcut without unlocking

- Add dots animation

- Translations removed

Older versions

1.2.5

Please clear data of app because of new shortcut scheme

- Module now prompts for pattern if unset

- MOAR shortcuts (thanks @ CyanogenMod)

- Cosmetic changes

- Fix crash if launcher icon was hidden

1.2.4

- Fix custom shortcuts bug

1.2.3

- Added margin b/w dots and lines on lock screen

- You can now add other knock codes to launch apps directly (A la PIN/Pattern Shortcuts Xposed)

- Translation changes

- Long pressing the knock code in activities will now reset it

1.2.2

- Translations (Polish by pantinPL, Mexican Spanish by Alan Yadir)

- Attempted to remove lag while locking and unlocking

- Animate the view when unlocking (not the old green animations, but from AOSP)

- If knock code is never set, module will not replace pattern even if switch is on

- Disabling emergency button in MainActivity will disable option below it

1.2.1

- HTC

- Translation update

1.2.0

- Failsafe option

- Size reduction

1.1.8 (Beta)

- Attempted HTC compatibility, but no testers.

1.1.7

- Bugfix to prevent device lockout when too many incorrect attempts too many times

1.1.6

- Reimplemented KnockCode with buttons, faster now - ripple taps are now confined to boxes

- Added Brazilian Portuguese translations by Gabriel Campos

- Fixed issue with dots view where incorrect mode would still allow dots to be entered.

1.1.5

- Added red colour animation when pattern incorrect

- Fixed a hook so unlocking should be smoother now

1.1.4

- Issues with dots view fixed by using AOSP implementation (if you had issues with v1.1.3, this should fix it)

- Changed tap rectangle to material ripple

1.1.3

Fixed possible ANRs

Added dots view on lock screen (with animations Ooooooo)

1.1.2

Fixed issue with 5.0.x hooks

1.1.1

Minor bugfixes

1.1.0

You will need to enable the module from UI after install

- Xperia issue fixed (if version 1.0.7 produced an issue with you, it should work now)

- Module on/off switch ((thanks [MENTION=5222551]Maxr1998[/MENTION])

- Hide module from launcher (thanks [MENTION=5222551]Maxr1998[/MENTION])

- Change pattern size

- Hide emergency button text but keep button

- Vibration settings

- Module active checker (thanks [MENTION=5222551]Maxr1998[/MENTION])

1.0.7

Marshmallow users will need to delete old version

Implemented emergency button

1.0.6.2

Working Marshmallow support, finally

1.0.6.1

- Improved Marshmallow support

- Fix a bug where module would prevent non pattern lock screens from loading

1.0.6

- Attempted Marshmallow compatibility

- Tried to increase the Lollipop success rate

Older versions

- Overhauled UI, added Lollipop compatibility, removed backward comptability (v1.0.5)

- MohammadAG's release (v1.0.4)
[Xposed Framework Modules] Rijul.A:
Please ignore this post

Tags : gesture lock screen exposed xposed xda tuesday unlock draw swipe full screen fullscreen lockscreen shortcut custom quick launch pattern pin protected pinned authentication dual two factor rijul ahuja
[Xposed Framework Modules] pradhyu69:
Whats the effect of this module on battery? I think this is like doubletap2wake function which is a real battery drainer.
[Xposed Framework Modules] Benrap:
Didn't work when i enabled the module, chnaged the password and rebooted. Had to uninstall xposed framework, uninstall your app, then re-install xposed. Anything I'm doing wrong with how to enabke the module? I have a galaxy s5 with cm12.1 nightlys.
[Xposed Framework Modules] mattplo:
DT2W is a real battery drain on Nexus 5, obviously due to digitizer and panel being powered together opposed to say an HTC M8/M7 or LG G3/G4 where they are powered separately and natively support DT2W. Your Nexus 5 was never designed with this in mind. DT2W is not a battery drainer. Your hardware just wasn't meant to do this.
[Xposed Framework Modules] Dhaval2904:
N

I tried this module, and after restart my phone stuck at lock screen.. I tried the default pattern to unlock but nothing happened..

Please someone help me out
[Xposed Framework Modules] Rijul.A:
You need to set up a 3x3 pattern in your default settings. My module checks if it is active, and then overrides it with the knock code. This is done so that there is a fallback pattern lock screen if/when Xposed is disabled for any reason. If it still doesn't work, please give me your Xposed logs. I will try to fix it. I am using the nightlies too!

This module only works while screen on, and therefore, is not the kind of battery drainer that you are taking about.

Hi, sorry to hear that Dhaval. You should boot into recovery, go to advanced -> file manager -> delete /data/app/me.rijul.knockcode-*/base.apk. Alternatively, you could disable Xposed if you have a flashable ZIP available.

While you're at it, could you get me a logcat (when your phone is on)

adb logcat *:E > logcat.txt
[Xposed Framework Modules] aillez:
I also got this problem too.

because I still don't have any pattern lock or pin lock (just swipe)

then I disable Xposed and config Pattern lock in 3x3 (as dev said)

then enable module and reboot again.

now it's work like a charm.

good luck.
[Xposed Framework Modules] Rijul.A:
Hi, you're right. I tried it myself to see that there is some error which occurs, I'll fix it tonight after I get home. Thank you for identifying it.
[Xposed Framework Modules] Bodenseematze:
I use a CM12.1 based ROM (SaberMod) for my Galaxy S4 and installed your new knock module.

I followed the suggestions (first set a 3x3 pattern, then enabled the module, restart the phone, unlock with default pattern and then set an own pattern) - and everything works :D

The only thing which is somehow strange is the following:

- I switch off the screen

- I switch the screen on again - the lock screen is visible

- I have to swipe up - an empty screen (only background) is shown

- now I can "knock" to unlock

Is that additional "swipe up" - step normal?

BTW, I'm using the lightning launcher if that matters...
[Xposed Framework Modules] RusherDude:
Awesome for someone to take on this project forward! (Since MohammadAG is great at making new modules but terrible at mantaining any of them, or even replying)

It would be awesome if at the end, you talked with some kernel dev that permited Double tap to wake or such and combine efforts for screen-off knock code :D

Also, could the grid be expanded? 2x2 is small, it would be cool if we could change it to 3x3, 4x4, etc :)

Thanks a lot!

--

Edit: Tested it on Stock N5 6.0.1 and it blocks you right past the lock screen (knock code lockscreen): after it, a black screen and wallpaper changes to original M wallpaper and lockscreen is shown again and again. Need to disable the module to be able to go past the lockscreen again (and so lost the xposed log for that moment) :(.

Yes, I had 3x3 pattern lockscreen when activating the module. And the knock code lockscreen appears, but again and again on a loop.
[Xposed Framework Modules] Rijul.A:
For your first suggestion, you should refer to http://xdaforums.com/nexus-4/orig-development/app-hellscode-knockcode-mod-hellscore-t3135899

For second, yes, the size modification is on my to do list, but first is stability and compatibility.

If you could please use adb logcat *:E? I will try to fix this. I have not yet tested the module personally on Marshmallow, and support for it is very limited. I have been trying to install it on my device, but the build keeps failing. Thanks for feedback!
[Xposed Framework Modules] Rijul.A:
Yes, that is the expected behaviour. It emulates stock, wherein you swipe up the screen to show the pattern entry or the pin entry.
[Xposed Framework Modules] aerifal:
Yep it's normal, you can change it from stock settings>lockscreen>tick directly show pattern view.

======

Thanks OP the module working perfectly on my gt-n7100 unofficial cm12.1 rom by Ivan Meler. I wish I could unlock it even in a screen off state, just like LG devices :)
[Xposed Framework Modules] Rijul.A:
Hello, I have updated the module to allow users to set a pattern (that is, allows to use non pattern screen) after it has been activated. So silly of me to have done that wrongly - MohammadAG's ways were very well thought out. Could you please test again?

[MENTION=4811172]RusherDude[/MENTION], I think that this process should also enhance Marshmallow compatibility, but I can not be too sure. If you would test it again, I will gladly work on it further. But I have started a MM ROM download anyway, so you can wait for me to vouch for the module too. Please provide logs if you end up testing.

Thanks for your valuable feedback!
[Xposed Framework Modules] Phonerix:
Works well on Z3 5.1.1 with smart lock :D
[Xposed Framework Modules] RusherDude:
Thanks for the fast answer! I will try logcat when Im back home. Also that post you linked, will investigate it, thanks!

Nothing is fixed on this version yet :( unfortunately, same error. A detail I didn't say before tho:

- The knock code only awaits for FIVE touches (my password had 5 touches too, maybe just that?), after that the black screen comes and..

- If the code was OK, the lockscreen appears again but you maintain your wallpaper.

- If the code was not OK, the lockscreen appears again but the background turns to the stock marshmallow one (the one in the dev preview).

That may help you or not, not sure tho. Ill try to help if im able later.

thanks!
[Xposed Framework Modules] :
1.1.7 - bug fix update. Says so in the changelog.

Please explain to me why do you want to wait 0.3 seconds for a phone to unlock after you've entered the correct password.
[Xposed Framework Modules] GMFalka:
Really nice. Keep up the good work!!
[Xposed Framework Modules] ikunalgautam:
I appreciate your work on this knock code module, but since i updated it ruin the lockscreen. The ripple effect was not confined to particular boxes. In Previous update it was working fine.
[Xposed Framework Modules] nicesoni_ash:
It looks goooood. [emoji3]

Sent from my "GT-I9300/1+2" powered by Carbon/Blisspop Rom & Boeffla/ak Kernel

Fueled by 7000mAh ZeroLemon Battery
[Xposed Framework Modules] :
Send a screenshot with you long pressing the button. And logs.

PS : Next update (not bugfix) will be delayed because my laptop is on its last breath it seems.

EDIT : Does anyone else have this same issue?
[Xposed Framework Modules] nabil08:
good job bro.. it works perfectly.. just one issue.. its just a blank screen no notification no widget.. thanks
[Xposed Framework Modules] :
Yeah, it's going to stay that way. Blame your ROM developer for it. On Stock Android, you get a screen with notifications and clock which you swipe up to see the unlock screen. I have only modified the unlock screen and nothing else.
[Xposed Framework Modules] RusherDude:
Sorry didn't notice changelog into the repo, was looking at the first post, my bad.

About those 0,3s.. Because the unlock animation wouldn't look broken with a dot less and in this case without the green effect! What would be the harm for putting the option? :P We also lose some speed overall with xposed already :good:

Anyway keep doing great! :good:
[Xposed Framework Modules] terroboy k9:
A feature request,. Not so important as already im enjoying the module....

Only if u can add option, for making a circle knock code....

I know it isnt suitable ... Just a request...
[Xposed Framework Modules] :
Do you mind sending a picture of what you are trying to get at? I don't understand it very clearly.
[Xposed Framework Modules] :
Okay, but it will take a long time to be implemented because I am using the AOSP library for the dots view, and I will have to understand it before I can modify it like that.
[Xposed Framework Modules] RusherDude:
Really appreciated :fingers-crossed::fingers-crossed:, thank you! :laugh:

For now Im mostly everyday changing between v1.1.3 and the latest version. Latest version seems way more responsive just after turning the screen on, but 1.1.3 is awesome with the green dots effects (it may sound like a joke, but for me this is the most cool addition to this module :laugh:).

If I can help tell me tho!

PS: I hope that with "a long time" you mean one of your "long times" lol haha
[Xposed Framework Modules] brossovitch:
This is a great module, thank you!

Any chance in adding screen off feature for devices with step counters? Like most LG devices. I miss knock on, but this module almost gives it back!

-LG L90 CM13 6.0.1
[Xposed Framework Modules] terroboy k9:
I will add in sometime...

Its like this....

We hide the borders....so the box effect gone...

Then if u accept my request and add circle option...the circle appears like in earlier day with pattern lock...

But wider... Pattern lock dots circle is quite small...

In our case.. The circle must be equivalent to the box...

Like 1/2 the side of the square box = the radius of the circle... So that it looks quite awesome...

Sorry i dont know if i can get a ss for it... May be i draw or do something to show u soonnn
[Xposed Framework Modules] terroboy k9:
Like this...

But circle is small in pic... Im saying circle's radius half the side of square
[Xposed Framework Modules] Riccorbypro:
Bug

I found a bug (I think)...

Last night, my phone was in my pocket, and it turned on. I didn't realise that it was on the whole time until I took it out and it was on the emergency call screen, with about 100 numbers entered. So I pressed the back button and attempted to enter my Knock Code.

I could swipe up, access emergency call, and the lockscreen camera, but I couldn't get into my phone. I was on the latest 1.1.7 version, had updated it that morning. Fortunately, a reboot solved the problem, and I was able to get into my phone again.

It happened again this morning, this time while I was playing music, but also with the phone in my pocket. Once again, the emergency call screen opened and I could not get in. Again, solved by rebooting.

I have uploaded my SystemUI.apk to MEGA, and can provide more information (system images, other files from ROM, etc.) if you should need. I'm running the Deodexed Sony ROM from here, and I also have a bunch of other Xposed modules installed.

Hope you can solve this issue.

and...

Keep up the good work!

Riccorbypro
[Xposed Framework Modules] :
I don't understand this very clearly, but are you looking to unlock while the screen is off? That can't be done via Xposed, it is a kernel feature. If the kernel supports it, only then can you do it. (Refer [MENTION=5222551]Maxr1998[/MENTION]'s Hellscore)

Maybe, if I get the time. Holidays will end soon.

I have been waiting for you to come here since I saw your original post on Reddit. Do you mind getting me logs from when that happens? Use adb logcat. You couldn't get into your phone because the code was incorrect or the knocks were disabled?