[XPOSED][MOD][4.0+] CompleteKeyguardDisabler completely disables your keyguard

[XPOSED][MOD][4.0+] CompleteKeyguardDisabler completely disables your keyguard - Xposed Framework Modules

NEW! Navbar button issue appears to have been resolved.
This is my first go at an Xposed module, or any Android app for that matter, so wish me luck!
Intro:
Anyway, I was using a lot of Xposed mods that were cool, but my IT policy has the lockscreen set to pin or password and none of the bypasses around quite gave me what I wanted. LucasR93 created this really nice mod for those of you that really like just a sliding lock on your screen, but I really wanted to use the fantastic NFCSecure Lockscreen, which works best with no lockscreen enabled at all. (PS. you guys should check out NFCSecure, it's so much easier than even a pattern! And the developer is pretty responsive, open to any suggestions you have. *this spot is not paid for by the developer of the app. I just really like it that much*)
So, I made my own mod.
What it does:
The mod utilizes the Xposed Framework to find the KeyguardViewMediator class and hook the doKeyguardLocked method, completely mocking it out. Therefore, any time the system tries to lock the screen it'll just go down the memory hole, and do nothing. Thus, even if you have a device policy mandating a pin/password the phone will never lock, ever.
This works like the aforementioned mod by LucasR93, in that it doesn't touch the actual lock policy or setup; if you go into your settings, to the security section, you will see all of the settings as normal. Nothing that needs the pin/password will complain because as far as they know it works just fine. This is (IMHO) much safer than attacking the policy and security parts of the OS directly, as they could open some more serious vulnerabilities.
What devices this mod works on:
I only have a Droid MAXX running 4.4 right now, but the way the code is implemented it should be able to work on anything 4.0+ and AOSPish, as long as Xposed Framework works properly.
Nexus 4 and Nexus 5 reported working, KitKat stock and ParanoidAndroid ROM.
I'd like to formally request anyone running Xposed on 4.0-4.3 to test this and give feedback as to if it works on these devices.
I am using some of the info provided to LucasR93 to try to also add support for the HTC lockscreen but I'll need some HTC testers for that one.
Installation Instructions:
Ensure that the Xposed Framework (a.k.a. Xposed Installer) is installed and properly functioning on your device.
Go to the Download section of the Xposed Installer, or here, to find the Complete Keyguard Disabler. Check the box in the Xposed Installer Modules list, and reboot the phone.
Upon reboot, you may or may not see your lockscreen. Some devices (Nexus devices it seems) show the lockscreen on boot, but never again. Some devices (Droid line, possibly Moto X) are completely unlocked upon reboot.
Every time your phone would normally lock, a log entry will be written to the Xposed log "Not locking the screen".
If it doesn't work:
Uncheck all other Xposed modules. Reboot. If it still doesn't work, copy the logs from the Xposed Installer and post them in this thread, with your phone model and Android version, and I'll try to help.
This new experimental build tries a few things, and logs a LOT of things. Try it out.
Is this unsafe?
Actually, maybe. If you lose your phone you will be unable to lock it remotely by using Android Device Manager (or probably carrier/manufacturer/corporate specific device admins as well). You can, however, locate and wipe without issue.
I am pondering a way to detect the ADM lock and toggle the screen, but if you use this to get NFC lockscreens working it's not something you have to worry about.
Special Thanks: @rovo89, obviously, for the Xposed Framework. @LucasR93, for his initial app that gave me most of the inspiration for this.

Does not work on my S4
No relevant logs found to post :/

hamidoo said:
Does not work on my S4
No relevant logs found to post :/
Click to expand...
Click to collapse
OK, first, Samsungs are usually nowhere near aosp, but I could try to see if I could make it work.
Second, what version of Android are you running? And is it a stock or custom ROM?
Third, I know you said nothing is relevant in the logs, but if you could post what's there I'd know if my module even loaded.

It works on my nexus 4, but just partially.
As soon as the module is active and I chose anything else than no Lockscreen I'm getting a result as on the screenshot - no navigation keys
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Gesendet von meinem Nexus 4

fabi280 said:
It works on my nexus 4, but just partially.
As soon as the module is active and I chose anything else than no Lockscreen I'm getting a result as on the screenshot - no navigation keys
View attachment 2515462
Gesendet von meinem Nexus 4
Click to expand...
Click to collapse
Oh?! That's really interesting. It appears you have the lockscreen navigation bar. That's, if I may be candid, pretty cool :silly:. Can I get the android version you're on? I can assume I know what the log says (although this will give a hint as to your version as well). I have capacitive navigation keys, so I did not see that one coming.

I'm on the latest Omni Rom build (14th January one, 4.4.2)
Gesendet von meinem Nexus 4

fabi280 said:
I'm on the latest Omni Rom build (14th January one, 4.4.2)
Gesendet von meinem Nexus 4
Click to expand...
Click to collapse
I'm working on it. Can you try something for me? Switch your keyguard to no lock (whatever got you the buttons) and reboot, then switch to a pin unlock and see if the mod works correctly.

No, I'm getting those buttons on every setting except on the No Lockscreen setting.
Upon reboot the buttons are there, until I press the standby button, then they are gone and it doesn't matter whether I go from pin to pattern/swipe or pattern to pin/swipe or swipe to pattern/pin. They only go back to normal after setting it to no Lockscreen.
Gesendet von meinem Nexus 4

fabi280 said:
No, I'm getting those buttons on every setting except on the No Lockscreen setting.
Upon reboot the buttons are there, until I press the standby button, then they are gone and it doesn't matter whether I go from pin to pattern/swipe or pattern to pin/swipe or swipe to pattern/pin. They only go back to normal after setting it to no Lockscreen.
Gesendet von meinem Nexus 4
Click to expand...
Click to collapse
OK, so to be clear, if you boot up the phone in "No Lockscreen" you have the normal buttons (Back, Home, Recents) but the instant you enable any lockscreen you get the lockscreen navigation bar buttons, correct? You do not have to do a reboot to get the buttons to break? That makes it more straightforward to fix, I believe, but it isn't as clean of a solution.
I had thought maybe it was giving you those buttons because on boot the phone tries to start in locked mode, which I thwart. But it appears as if every time the phone is "locked" the system updates the navigation bar buttons and also shows the keyguard. I'll look into nuking these functions, but I was hoping i could just nuke the call that sets them that way.

dtreth said:
OK, so to be clear, if you boot up the phone in "No Lockscreen" you have the normal buttons (Back, Home, Recents) but the instant you enable any lockscreen you get the lockscreen navigation bar buttons, correct? You do not have to do a reboot to get the buttons to break? That makes it more straightforward to fix, I believe, but it isn't as clean of a solution.
I had thought maybe it was giving you those buttons because on boot the phone tries to start in locked mode, which I thwart. But it appears as if every time the phone is "locked" the system updates the navigation bar buttons and also shows the keyguard. I'll look into nuking these functions, but I was hoping i could just nuke the call that sets them that way.
Click to expand...
Click to collapse
No, it doesn't matter which keyguard Mode i've set up before rebooting.
As soon as I am locking the phone I'm getting the Lockscreen navigation bar on unlocking again.
The only way to get back to normal is setting to no keyguard. And if I reboot without keyguard set, they don't switch to Lockscreen navigation bar after locking and unlocking.
Sorry English isn't my mother's tongue
Gesendet von meinem Nexus 4

fabi280 said:
No, it doesn't matter which keyguard Mode i've set up before rebooting.
As soon as I am locking the phone I'm getting the Lockscreen navigation bar on unlocking again.
The only way to get back to normal is setting to no keyguard. And if I reboot without keyguard set, they don't switch to Lockscreen navigation bar after locking and unlocking.
Sorry English isn't my mother's tongue
Gesendet von meinem Nexus 4
Click to expand...
Click to collapse
Don't apologize, I was getting very specific and you responded prefectly. Thanks. I'll get a new version uploaded later today, with some exploration code to uncover what's causing this.

fabi280 said:
No, it doesn't matter which keyguard Mode i've set up before rebooting.
As soon as I am locking the phone I'm getting the Lockscreen navigation bar on unlocking again.
The only way to get back to normal is setting to no keyguard. And if I reboot without keyguard set, they don't switch to Lockscreen navigation bar after locking and unlocking.
Sorry English isn't my mother's tongue
Gesendet von meinem Nexus 4
Click to expand...
Click to collapse
Try this new build. I will be updating the OP soon.
hamidoo said:
Does not work on my S4
No relevant logs found to post :/
Click to expand...
Click to collapse
Also try this new build. It has Experimental SUPERDEBUG enabled, which is just me looking for possible apks to hack on others' phones.

dtreth said:
Don't apologize, I was getting very specific and you responded prefectly. Thanks. I'll get a new version uploaded later today, with some exploration code to uncover what's causing this.
Click to expand...
Click to collapse
1. Downloaded your updated module
2. Activated it
3. Set a Pin (0000)
4. Reboot
5. It asked me for the pin the first time
6. Standby
7. Wake-Up: Lockscreen Navigation bar; No Pin
8. Sent the log to my computer
9. Reproduced 6 & 7 for 3 more times.
10. Set keyguard to no lock -> Standby -> Normal Nav Bar (not on the log anymore)
Code:
-----------------
15.01.2014 07:59:19 UTC
Loading Xposed v42 (for Zygote)...
Loading modules from /data/app/net.treth.d.completekeyguarddisabler-2.apk
Loading class net.treth.d.completekeyguarddisabler.CompleteKeyguardDisabler
In package com.android.keyguard [4.4]
hooking method doKeyguardLocked in class 'com.android.keyguard.KeyguardViewMediator'
hooking method adjustStatusBarLocked in class 'com.android.keyguard.KeyguardViewMediator'
Not adjusting the statusbar (and navigation bar) [hopefully]
Not locking the screen
Not adjusting the statusbar (and navigation bar) [hopefully]
Not locking the screen
This package seems like it could be a keyguard com.android.deskclock [SUPERDEBUG]
This package seems like it could be a keyguard com.teamkang.fauxclock [SUPERDEBUG]
I doubt fauxclock could be a keyguard, it's a kernel setup tool.
Oh more logs:
Code:
-----------------
15.01.2014 07:59:19 UTC
Loading Xposed v42 (for Zygote)...
Loading modules from /data/app/net.treth.d.completekeyguarddisabler-2.apk
Loading class net.treth.d.completekeyguarddisabler.CompleteKeyguardDisabler
In package com.android.keyguard [4.4]
hooking method doKeyguardLocked in class 'com.android.keyguard.KeyguardViewMediator'
hooking method adjustStatusBarLocked in class 'com.android.keyguard.KeyguardViewMediator'
Not adjusting the statusbar (and navigation bar) [hopefully]
Not locking the screen
Not adjusting the statusbar (and navigation bar) [hopefully]
Not locking the screen
This package seems like it could be a keyguard com.android.deskclock [SUPERDEBUG]
This package seems like it could be a keyguard com.teamkang.fauxclock [SUPERDEBUG]
Not locking the screen
This package seems like it could be a keyguard com.android.deskclock [SUPERDEBUG]
This package seems like it could be a keyguard pl.solidexplorer.unlocker [SUPERDEBUG]
Not locking the screen
This package seems like it could be a keyguard com.android.deskclock [SUPERDEBUG]
This package seems like it could be a keyguard net.nurik.roman.dashclock [SUPERDEBUG]
Not locking the screen
Not locking the screen
This package seems like it could be a keyguard net.nurik.roman.dashclock [SUPERDEBUG]
This package seems like it could be a keyguard pl.solidexplorer.unlocker [SUPERDEBUG]
This package seems like it could be a keyguard com.android.deskclock [SUPERDEBUG]
Not locking the screen
This package seems like it could be a keyguard net.nurik.roman.dashclock [SUPERDEBUG]
Not locking the screen
Not locking the screen
Not locking the screen
This package seems like it could be a keyguard net.nurik.roman.dashclock [SUPERDEBUG]
This package seems like it could be a keyguard pl.solidexplorer.unlocker [SUPERDEBUG]
This package seems like it could be a keyguard net.nurik.roman.dashclock [SUPERDEBUG]
This package seems like it could be a keyguard pl.solidexplorer.unlocker [SUPERDEBUG]
Not locking the screen
This package seems like it could be a keyguard net.nurik.roman.dashclock [SUPERDEBUG]
Not locking the screen
Not locking the screen
This package seems like it could be a keyguard net.nurik.roman.dashclock [SUPERDEBUG]
In package com.android.keyguard [4.4]
hooking method doKeyguardLocked in class 'com.android.keyguard.KeyguardViewMediator'
hooking method adjustStatusBarLocked in class 'com.android.keyguard.KeyguardViewMediator'
Not locking the screen
Not adjusting the statusbar (and navigation bar) [hopefully]
Not locking the screen
Not locking the screen
Not locking the screen
Not locking the screen

fabi280 said:
1. Downloaded your updated module
2. Activated it
3. Set a Pin (0000)
4. Reboot
5. It asked me for the pin the first time
6. Standby
7. Wake-Up: Lockscreen Navigation bar; No Pin
8. Sent the log to my computer
9. Reproduced 6 & 7 for 3 more times.
10. Set keyguard to no lock -> Standby -> Normal Nav Bar (not on the log anymore)
Code:
-----------------
15.01.2014 07:59:19 UTC
Loading Xposed v42 (for Zygote)...
Loading modules from /data/app/net.treth.d.completekeyguarddisabler-2.apk
Loading class net.treth.d.completekeyguarddisabler.CompleteKeyguardDisabler
In package com.android.keyguard [4.4]
hooking method doKeyguardLocked in class 'com.android.keyguard.KeyguardViewMediator'
hooking method adjustStatusBarLocked in class 'com.android.keyguard.KeyguardViewMediator'
Not adjusting the statusbar (and navigation bar) [hopefully]
Not locking the screen
Not adjusting the statusbar (and navigation bar) [hopefully]
Not locking the screen
This package seems like it could be a keyguard com.android.deskclock [SUPERDEBUG]
This package seems like it could be a keyguard com.teamkang.fauxclock [SUPERDEBUG]
I doubt fauxclock could be a keyguard, it's a kernel setup tool.
Oh more logs:
Code:
-----------------
15.01.2014 07:59:19 UTC
Loading Xposed v42 (for Zygote)...
Loading modules from /data/app/net.treth.d.completekeyguarddisabler-2.apk
Loading class net.treth.d.completekeyguarddisabler.CompleteKeyguardDisabler
In package com.android.keyguard [4.4]
hooking method doKeyguardLocked in class 'com.android.keyguard.KeyguardViewMediator'
hooking method adjustStatusBarLocked in class 'com.android.keyguard.KeyguardViewMediator'
Not adjusting the statusbar (and navigation bar) [hopefully]
Not locking the screen
Not adjusting the statusbar (and navigation bar) [hopefully]
Not locking the screen
This package seems like it could be a keyguard com.android.deskclock [SUPERDEBUG]
This package seems like it could be a keyguard com.teamkang.fauxclock [SUPERDEBUG]
Not locking the screen
This package seems like it could be a keyguard com.android.deskclock [SUPERDEBUG]
This package seems like it could be a keyguard pl.solidexplorer.unlocker [SUPERDEBUG]
Not locking the screen
This package seems like it could be a keyguard com.android.deskclock [SUPERDEBUG]
This package seems like it could be a keyguard net.nurik.roman.dashclock [SUPERDEBUG]
Not locking the screen
Not locking the screen
This package seems like it could be a keyguard net.nurik.roman.dashclock [SUPERDEBUG]
This package seems like it could be a keyguard pl.solidexplorer.unlocker [SUPERDEBUG]
This package seems like it could be a keyguard com.android.deskclock [SUPERDEBUG]
Not locking the screen
This package seems like it could be a keyguard net.nurik.roman.dashclock [SUPERDEBUG]
Not locking the screen
Not locking the screen
Not locking the screen
This package seems like it could be a keyguard net.nurik.roman.dashclock [SUPERDEBUG]
This package seems like it could be a keyguard pl.solidexplorer.unlocker [SUPERDEBUG]
This package seems like it could be a keyguard net.nurik.roman.dashclock [SUPERDEBUG]
This package seems like it could be a keyguard pl.solidexplorer.unlocker [SUPERDEBUG]
Not locking the screen
This package seems like it could be a keyguard net.nurik.roman.dashclock [SUPERDEBUG]
Not locking the screen
Not locking the screen
This package seems like it could be a keyguard net.nurik.roman.dashclock [SUPERDEBUG]
In package com.android.keyguard [4.4]
hooking method doKeyguardLocked in class 'com.android.keyguard.KeyguardViewMediator'
hooking method adjustStatusBarLocked in class 'com.android.keyguard.KeyguardViewMediator'
Not locking the screen
Not adjusting the statusbar (and navigation bar) [hopefully]
Not locking the screen
Not locking the screen
Not locking the screen
Not locking the screen
Click to expand...
Click to collapse
Yeah, thanks. The [SUPERDEBUG] lines are just searching any loaded package that has "lock" or "guard" in the name. I found the samsung lockscreen this way: "com.sec.android.app.keyguard".
I am currently trying out a new hook spot for the show lockscreen part, but I doubt it'll affect your issue. It does, however, make the hack work smoother on my phone. I'll push that one soon. I still need to do some more digging in the code to even find points to test, and it's slow goign when I have no soft nav to play with. I think I will just have to buy that nexus 7 after all :silly:. (Really waiting as long as I can for a new Nexus 10)
It's weird that the statusbar log message appears to function almost at the right time. I wish there was a KeyguardDispatchNavigationUpdate or something, that would make this easy.

I've got an idea. In the security settings there is something like automatically lock. If you set this value to not instant lock and the phone goes into standby by timeout you aren't asked for your pin.
So maybe you could override this value to like -1 or any other value it can't reach and link the powerbuttons standby to the timeout standby.
I'm not familiar with xposed module development, just did some heavy amount of Java coding for desktop/server applications... So this is just an idea, I'm unsure if it is doable.
If this would work fine it'd be an awesome solution for the VPN password requirements
Sent from my Nexus 4

fabi280 said:
I've got an idea. In the security settings there is something like automatically lock. If you set this value to not instant lock and the phone goes into standby by timeout you aren't asked for your pin.
So maybe you could override this value to like -1 or any other value it can't reach and link the powerbuttons standby to the timeout standby.
I'm not familiar with xposed module development, just did some heavy amount of Java coding for desktop/server applications... So this is just an idea, I'm unsure if it is doable.
If this would work fine it'd be an awesome solution for the VPN password requirements
Sent from my Nexus 4
Click to expand...
Click to collapse
Yes, you have a very good point, although I think the problem there is the system could still call the lockscreen through other means, like upon first boot. That's not something we really want. Well, I don't really want that, but I'll definitely look into that.

fabi280 said:
I've got an idea. In the security settings there is something like automatically lock. If you set this value to not instant lock and the phone goes into standby by timeout you aren't asked for your pin.
So maybe you could override this value to like -1 or any other value it can't reach and link the powerbuttons standby to the timeout standby.
I'm not familiar with xposed module development, just did some heavy amount of Java coding for desktop/server applications... So this is just an idea, I'm unsure if it is doable.
If this would work fine it'd be an awesome solution for the VPN password requirements
Sent from my Nexus 4
Click to expand...
Click to collapse
In the source of KeyguardViewMediator I found "Temporary enable/disable (e.g. the "back" button) are done in KeyguardHostView." so I am trying to also mock out showSecurityScreen there. Try this version and tell me what the logs say if it doesn't work. Also, if it almost works, but doesn't show recents, I can fix that pretty quickly.
FINGERS CROSSED! [NOTE: alpha build will NOT work on anything but 4.4 AOSP for this fix. I will build it for all if this is confirmed working. ]

dtreth said:
In the source of KeyguardViewMediator I found "Temporary enable/disable (e.g. the "back" button) are done in KeyguardHostView." so I am trying to also mock out showSecurityScreen there. Try this version and tell me what the logs say if it doesn't work. Also, if it almost works, but doesn't show recents, I can fix that pretty quickly.
FINGERS CROSSED! [NOTE: alpha build will NOT work on anything but 4.4 AOSP for this fix. I will build it for all if this is confirmed working. ]
Click to expand...
Click to collapse
I think it could actually work if I'd use Stock AOSP and not Omni
Code:
-----------------
15.01.2014 21:56:44 UTC
Loading Xposed v42 (for Zygote)...
Loading modules from /data/app/net.treth.d.completekeyguarddisabler-1.apk
Loading class net.treth.d.completekeyguarddisabler.CompleteKeyguardDisabler
In package com.android.keyguard [4.4]
hooking method showLocked in class 'com.android.keyguard.KeyguardViewMediator'
hooking method showSecurityScreen in class 'com.android.keyguard.KeyguardViewHost'
de.robv.android.xposed.XposedHelpers$ClassNotFoundError: java.lang.ClassNotFoundException: com.android.keyguard.KeyguardViewHost
at de.robv.android.xposed.XposedHelpers.findClass(XposedHelpers.java:52)
at de.robv.android.xposed.XposedHelpers.findAndHookMethod(XposedHelpers.java:179)
at net.treth.d.completekeyguarddisabler.CompleteKeyguardDisabler.handleLoadPackage(CompleteKeyguardDisabler.java:37)
at de.robv.android.xposed.IXposedHookLoadPackage$Wrapper.handleLoadPackage(IXposedHookLoadPackage.java:20)
at de.robv.android.xposed.callbacks.XC_LoadPackage.call(XC_LoadPackage.java:34)
at de.robv.android.xposed.callbacks.XCallback.callAll(XCallback.java:70)
at de.robv.android.xposed.XposedBridge$2.beforeHookedMethod(XposedBridge.java:202)
at de.robv.android.xposed.XposedBridge.handleHookedMethod(XposedBridge.java:527)
at android.app.ActivityThread.handleBindApplication(Native Method)
at android.app.ActivityThread.access$1500(ActivityThread.java:135)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1256)
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loop(Looper.java:136)
at android.app.ActivityThread.main(ActivityThread.java:5017)
at java.lang.reflect.Method.invokeNative(Native Method)
at java.lang.reflect.Method.invoke(Method.java:515)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:779)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:595)
at de.robv.android.xposed.XposedBridge.main(XposedBridge.java:126)
at dalvik.system.NativeStart.main(Native Method)
Caused by: java.lang.ClassNotFoundException: com.android.keyguard.KeyguardViewHost
at java.lang.Class.classForName(Native Method)
at java.lang.Class.forName(Class.java:251)
at external.org.apache.commons.lang3.ClassUtils.getClass(ClassUtils.java:823)
at de.robv.android.xposed.XposedHelpers.findClass(XposedHelpers.java:50)
... 19 more
Caused by: java.lang.NoClassDefFoundError: com/android/keyguard/KeyguardViewHost
... 23 more
Caused by: java.lang.ClassNotFoundException: Didn't find class "com.android.keyguard.KeyguardViewHost" on path: DexPathList[[zip file "/system/priv-app/Keyguard.apk"],nativeLibraryDirectories=[/vendor/lib, /system/lib]]
at dalvik.system.BaseDexClassLoader.findClass(BaseDexClassLoader.java:56)
at java.lang.ClassLoader.loadClass(ClassLoader.java:497)
at java.lang.ClassLoader.loadClass(ClassLoader.java:457)
... 23 more
Not locking the screen
Not locking the screen
Not locking the screen
Not locking the screen
Not locking the screen
I've noticed that effect also on the Active Display feature of the rom. I guess they have fixed it...
Take a look at this:
https://github.com/omnirom/android_...r/policy/activedisplay/ActiveDisplayView.java
Line 675
Code:
private void unlockKeyguardActivity() {
try {
// The intent we are sending is for the application, which
// won't have permission to immediately start an activity after
// the user switches to home. We know it is safe to do at this
// point, so make sure new activity switches are now allowed.
ActivityManagerNative.getDefault().resumeAppSwitches();
// Also, notifications can be launched from the lock screen,
// so dismiss the lock screen when the activity starts.
ActivityManagerNative.getDefault().dismissKeyguardOnNextActivity();
} catch (RemoteException e) {
}
handleForceHideNotificationView();
}
I guess this could help
This was the change that fixed it - at least I'm thinking that it would be: https://github.com/omnirom/android_frameworks_base/commit/72642b27a90bc760ee803c40a15c164a6a2ffa1c
Look at Line 645-660

fabi280 said:
I think it could actually work if I'd use Stock AOSP and not Omni
Code:
-----------------
15.01.2014 21:56:44 UTC
Loading Xposed v42 (for Zygote)...
Loading modules from /data/app/net.treth.d.completekeyguarddisabler-1.apk
Loading class net.treth.d.completekeyguarddisabler.CompleteKeyguardDisabler
In package com.android.keyguard [4.4]
hooking method showLocked in class 'com.android.keyguard.KeyguardViewMediator'
hooking method showSecurityScreen in class 'com.android.keyguard.KeyguardViewHost'
de.robv.android.xposed.XposedHelpers$ClassNotFoundError: java.lang.ClassNotFoundException: com.android.keyguard.KeyguardViewHost
at de.robv.android.xposed.XposedHelpers.findClass(XposedHelpers.java:52)
at de.robv.android.xposed.XposedHelpers.findAndHookMethod(XposedHelpers.java:179)
at net.treth.d.completekeyguarddisabler.CompleteKeyguardDisabler.handleLoadPackage(CompleteKeyguardDisabler.java:37)
at de.robv.android.xposed.IXposedHookLoadPackage$Wrapper.handleLoadPackage(IXposedHookLoadPackage.java:20)
at de.robv.android.xposed.callbacks.XC_LoadPackage.call(XC_LoadPackage.java:34)
at de.robv.android.xposed.callbacks.XCallback.callAll(XCallback.java:70)
at de.robv.android.xposed.XposedBridge$2.beforeHookedMethod(XposedBridge.java:202)
at de.robv.android.xposed.XposedBridge.handleHookedMethod(XposedBridge.java:527)
at android.app.ActivityThread.handleBindApplication(Native Method)
at android.app.ActivityThread.access$1500(ActivityThread.java:135)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1256)
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loop(Looper.java:136)
at android.app.ActivityThread.main(ActivityThread.java:5017)
at java.lang.reflect.Method.invokeNative(Native Method)
at java.lang.reflect.Method.invoke(Method.java:515)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:779)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:595)
at de.robv.android.xposed.XposedBridge.main(XposedBridge.java:126)
at dalvik.system.NativeStart.main(Native Method)
Caused by: java.lang.ClassNotFoundException: com.android.keyguard.KeyguardViewHost
at java.lang.Class.classForName(Native Method)
at java.lang.Class.forName(Class.java:251)
at external.org.apache.commons.lang3.ClassUtils.getClass(ClassUtils.java:823)
at de.robv.android.xposed.XposedHelpers.findClass(XposedHelpers.java:50)
... 19 more
Caused by: java.lang.NoClassDefFoundError: com/android/keyguard/KeyguardViewHost
... 23 more
Caused by: java.lang.ClassNotFoundException: Didn't find class "com.android.keyguard.KeyguardViewHost" on path: DexPathList[[zip file "/system/priv-app/Keyguard.apk"],nativeLibraryDirectories=[/vendor/lib, /system/lib]]
at dalvik.system.BaseDexClassLoader.findClass(BaseDexClassLoader.java:56)
at java.lang.ClassLoader.loadClass(ClassLoader.java:497)
at java.lang.ClassLoader.loadClass(ClassLoader.java:457)
... 23 more
Not locking the screen
Not locking the screen
Not locking the screen
Not locking the screen
Not locking the screen
I've noticed that effect also on the Active Display feature of the rom. I guess they have fixed it...
Take a look at this:
https://github.com/omnirom/android_...r/policy/activedisplay/ActiveDisplayView.java
Line 675
Code:
private void unlockKeyguardActivity() {
try {
// The intent we are sending is for the application, which
// won't have permission to immediately start an activity after
// the user switches to home. We know it is safe to do at this
// point, so make sure new activity switches are now allowed.
ActivityManagerNative.getDefault().resumeAppSwitches();
// Also, notifications can be launched from the lock screen,
// so dismiss the lock screen when the activity starts.
ActivityManagerNative.getDefault().dismissKeyguardOnNextActivity();
} catch (RemoteException e) {
}
handleForceHideNotificationView();
}
I guess this could help
This was the change that fixed it - at least I'm thinking that it would be: https://github.com/omnirom/android_frameworks_base/commit/72642b27a90bc760ee803c40a15c164a6a2ffa1c
Look at Line 645-660
Click to expand...
Click to collapse
Yeah, that build had, like, 6 typos in it, sorry. I cannot use that idea as posted (already tried it earlier and it completely borks), due to the way I slice into the keyguard and disable the lock. Somewhere there's a message that gets sent out to the navbar, I just can't find it. It doesn't help that if you google "navigation bar" google's results are full of "action bar" either....
Well, I cleaned some things up, this one shouldn't give you any exceptions, but I'd bet it still won't work. I'm gonna just buy a Nexus I think. I wanted one anyway. But I'll spend tonight trying to understand the navigation bar code and seeing if I can get it from that side.
In a related note, if anyone just wants to mock out a method, I wrote this snippet that simplifies the Xposed work:
Code:
private boolean mockOutMethod(final String logMessage,
ClassLoader cl,
String className,
String methodName,
Object... parameterTypes) {
try {
XposedBridge.log("hooking method '" + methodName + "' in class '" + className + "'");
// create the XCReplacement
XC_MethodReplacement mockOut = new XC_MethodReplacement() {
// do a full replacement of the method
@Override
protected Object replaceHookedMethod(MethodHookParam param) throws Throwable {
// do nothing, but log it
XposedBridge.log(logMessage);
return null;
}
};
// build the parameter list
Object[] parameterTypesAndCallback = Arrays.copyOf(parameterTypes, parameterTypes.length + 1);
parameterTypesAndCallback[parameterTypes.length] = mockOut;
// actually hook the method
XposedHelpers.findAndHookMethod(
className,
cl,
methodName, parameterTypesAndCallback);
}
catch (Throwable t) {
XposedBridge.log(t);
XposedBridge.log("hook method failed: '" + className + "." + methodName + "'");
return false;
}
return true;
}

dtreth said:
Yeah, that build had, like, 6 typos in it, sorry. I cannot use that idea as posted (already tried it earlier and it completely borks), due to the way I slice into the keyguard and disable the lock. Somewhere there's a message that gets sent out to the navbar, I just can't find it. It doesn't help that if you google "navigation bar" google's results are full of "action bar" either....
Well, I cleaned some things up, this one shouldn't give you any exceptions, but I'd bet it still won't work. I'm gonna just buy a Nexus I think. I wanted one anyway. But I'll spend tonight trying to understand the navigation bar code and seeing if I can get it from that side.
Click to expand...
Click to collapse
Code:
16.01.2014 00:25:17 UTC
Loading Xposed v42 (for Zygote)...
Loading modules from /data/app/net.treth.d.completekeyguarddisabler-2.apk
Loading class net.treth.d.completekeyguarddisabler.CompleteKeyguardDisabler
In package com.android.keyguard [4.4]
hooking method 'showLocked' in class 'com.android.keyguard.KeyguardViewMediator'
hooking method 'showSecurityScreen' in class 'com.android.keyguard.KeyguardHostView'
Not locking the screen
Not showing the screen
Not showing the screen
Not locking the screen
Not locking the screen
Upon reboot after the update (with "slide away" keyguard) I had a lockscreen without any unlock element and a home button
But after the first lock and unlock it showed the Lockscreen Navbar

Related

[XMOD] MoDaCo Toolkit (with HTC One specific mods)

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Note: MoDaCo Toolkit is no longer available via the Play Store. MoDaCo Toolkit is now a free, ad-supported application with a Pro version. Previous Play Store purchasers will receive the Pro key free of charge (details to follow)
As you may know, I often create modifications for Android and rather than them ending up all over the place, I'm now adding them to the 'MoDaCo Toolkit', which is built to use the Xposed Framework - http://mdc.gd/xposedfw. I plan on updating this every time I come up with a new tweak, be it a generic Android modification or specific to a particular device.
The pre-requisites are as follows:
You MUST be rooted
You MUST have the Xposed Framework installed and active
You MUST accept that modifications are used at your own risk
You may NOT distribute the toolkit (including in custom ROMs) - link back to this topic
Hit the 'Follow' button at the top right of the main MoDaCo Tookit topic to be notified of updates
Got that? OK.
The Toolkit can be downloaded in the main Xposed Toolkit thread here.
To use, simply download and install, enable the module in 'Xposed settings' and then enable the mods you want in the 'MoDaCo Toolkit' application. Note that most modifications will require a reboot to take effect and not all modifications will work on all devices!
HTC One specific modifications currently included are:
Action Launcher Pro + HTC One: Transparent status bar.
HTC One: Disable high volume warning - disable the volume warning that shows when cranking up the sound with headphones in.
HTC One: Enable ADB with secure lockscreen - ADB WILL NOT be disabled on boot if the device has a secure lockscreen configuration. DANGER: This is a potential security risk - handle with care!
HTC One: Enable advanced reboot options - aka EPM, show reboot / recovery / bootloader reboot options on power menu.
HTC One: Enable button options (only required on Android 4.1 ROMs) - the button options item will appear in settings, allowing you to configure the back button long press as menu.
HTC One: Volume wake - wake your device with the volume keys!
HTC One: Hide Kid Mode on power menu - this removes the Kid Mode option on the menu displayed when you long press the power button.
HTC One: Match battery image to % - the standard battery images don't correspond to the % remaining, this fixes that.
HTC One: Rename Flashlight to Torch - for us UK types.
HTC One: Show Blinkfeed icon in launcher - if you are using a third party launcher, this provides a simple way to access Blinkfeed. Just remove all the homescreens.
Other modifications currently included are:
Amazon MP3: Force US locale - use this if cloud player is not yet available in your country. Clear data on Amazon MP3 after enabling.
Facebook: Force Home Compatibility: Facebook will detect your device as Facebook Home compatible.
Google: Disable Wallet checks - remove region and root checks from Google Wallet.
Google: Force Play Store to 720P - your device will appear as a 720P device to the store, useful if apps are missing on your 1080P device.
Google: Prevent app disabling - apps from outside your region (e.g. Wallet, Sound Search) will not be disabled on startup.
Google Nexus 7: Show Camera in launcher - restore the missing Camera icon to the launcher.
Google Nexus (all): Disable safe volume warning.
Google Nexus (all): Enable multi-user support if unsupported on stock (e.g. Nexus 4).
Google Nexus (all): Enable advanced reboot options - aka EPM, show reboot / recovery / bootloader reboot options on power menu.
Google Nexus (all): Show user on power menu - this allows you to switch users using the long-press power menu.
HTC First: Hide carrier in status bar - stop the carrier name showing in the top left.
Pebble: Low priority notification (removes persistent icon).
SlingPlayer: Disable legacy hardware warning - remove the warning when connecting to older Slingboxes.
System: Allow all rotations - rotation will be allowed in all directions, even upside down.
System: Device properties - a number of device properties (normally read from build.prop) can be changed on the fly. BOARD, BRAND, DEVICE, MODEL and PRODUCT are included initially. Want others? Let me know!
System: Disable forward lock - apps will not be able to install to /mnt/asec, instead installing to /data/app. NOTE: May cause issues on some Samsung devices.
System: Enable action bar menu button - the software menu button will be displayed even if you have a hardware menu button.
System: Enable app buttons - the disable and notification options will be enabled for system apps.
System: Enable dreams service - enable the dreams screensaver service.
System: Enable lock screen rotation - if your device supports it, this will allow lock screen use in landscape.
System UI: Custom operator name.
System UI: Hide AM/PM on clock - hide the AM/PM indicator on the clock when not in 24H mode.
System UI: Hide battery meter - hide the battery meter, useful if you're using a third party app in the notification bar like Battery Widget Reborn (now also supports the HTC One!) or battery percentage.
System UI: Hide ongoing IME switcher - hide on the input method switch prompt.
System UI: Show battery percentage - show the remaining battery percentage next to the clock.
System UI: Show navigation bar - this allows you to show the navigation bar on supported devices.
Trackball Alert: Easy download link - easily download the TBA app and Xposed module.
Wireless: Enable NFC when screen is off - NFC works when the screen is off, useful for NFC launch tasks.
Wireless: Enable Face Lock with VPN - VPN (Credential Storage) will be available with Face Lock security.
If you have specific tweak requests or general questions, please visit http://mdc.gd/modacotoolkit
Note that special steps are required to activate the Xposed framework on the HTC One - see http://mdc.gd/xposedfwone for further details.
Big thanks go out to rovo89 for the framework and also to Bharath Prabhuswamy for the application icon.
P

Changelog
New in version 26: Improvements: Lots of 'under the hood' changes, better custom operator name code, update notification can now be dismissed.
New in version 25: Improvements: Hotfix for issues with volume wake / excessive superuser requests.
New in version 24: Improvements: Hide kid mode and volume wake now work on HTC One 4.2.2 ROMs. New modules: Action Launcher Pro + HTC One: Transparent status bar, System UI: Custom operator name, Pebble: Low priority notification (removes persistent icon).
New in version 23: Improvements: Changed handling of module code on incompatible devices, HTC One volume wake now works from deep sleep, NFC with screen off now works on HTC One, resolved issue with Nexus EPM. Removed module: Sprint flag (more tweaks for Sprint / AT&T One devices to follow). New module: Nexus (all): Disable safe volume warning.
New in version 22 - Bug fix: removed reporting dialog after reboot on HTC One, modified wording of several options, removed module: Play Store: Lower case wishlist menu (no longer required), new modules: System: Enable lock screen rotation, System UI: Show navigation bar, System: Enable dreams, System UI: Hide ongoing IME switcher, System UI: Hide AM/PM on clock, HTC One: Disable Sprint SystemUI flag (removes persistent GPS icon), HTC One: Volume wake, Nexus (all): EPM
New in version 21 - Bug fix (duplicate item in settings), added superuser to manifest permissions, minor wording changes, added Adobe Flash Player download link, added changelog link, new modules: System UI: show battery percentage, HTC First: hide carrier name
New in version 20 - new modules: HTC One: Advanced reboot options, HTC One: Disable high volume warning, Nexus (all): Enable user switching on power menu, Nexus (all): Enable multi-user support if unsupported on stock (e.g. Nexus 4).
New in version 19 - new modules: HTC One: Rename Flashlight to Torch, HTC One: Match battery image to %, Play Store: Lower case wishlist menu (for @le3ky!) - Xposed Framework 2.1.4 now REQUIRED for HTC One!
New in version 18 - Added link to Google Wallet APK. Release to test auto-update.
New in version 17 - ICS support. Internal changes to support forthcoming mods. Various fixes (including fix for the Camera / Blinkfeed icon options). Auto-update support.
New in version 16 - Pro key support
New in version 15 - Many thanks to our sponsors http://www.iwantmore.co.uk! new modules - HTC One: Show Blinkfeed icon in launcher, Google / Asus Nexus 7: Show Camera icon in launcher, Trackball Alert: Easy download link.
New in version 14 - Support for free version, additional useful topic links
New in version 13 - Reduced download size
New in version 12 - new module - Force software menu: The software menu button will be displayed even if you have a hardware menu button.
New in version 11 - new module - Disable forward lock: Apps will not be able to install to /mnt/asec, instead installing to /data/app. NOTE: May cause issues on some Samsung devices.
New in version 10 - Bug fix
New in version 9 - new module - Facebook Force Home Compatibility: Facebook will detect your device as Facebook Home compatible.
New in version 8 - the 'no encryption' module is no longer required - if the app is installed to encrypted storage, you will be warned and given the chance to fix on first load.
New in version 7 - new module - Device Properties: a number of device properties (normally read from build.prop) can be changed on the fly. BOARD, BRAND, DEVICE, MODEL and PRODUCT are included initially. Want others? Let me know!
New in version 6 - added 'Wireless' category. new modules - Wireless: Enable VPN with Face Lock - VPN (Credential Storage) will be available with Face Lock security.
New in version 5 - bugfix: Fixed an issue with app installing to SD card. new module - HTC One: Don't disable ADB - ADB WILL NOT be disabled on boot if the device has a secure lockscreen configuration. DANGER: This is a potential security risk - handle with care!
New in version 4 - additional support: Hide battery meter now supports the HTC One, new module: Amazon MP3: Force US locale
New in version 3 - new modules: HTC One: Hide Kid Mode on power menu, SlingPlayer: Disable legacy hardware warning, System: Hide battery meter.
New in version 2 - a slightly revised design and the following new modules - System: Allow all rotations, System: Enable NFC when screen is off.

Is it safe to say that the "special steps are required to activate the Xposed framework on the HTC One" isn't required? I flashed the zip file mentioned in the post and now I get stuck at the HTC One boot screen.

It is necessary because of the One NAND lock.
When you installed the Xposed APK it should have put an uninstall zip file on your internal storage, you can use that to revert.
P

I got stuck on the htc boot screen as well and had to reset my phone
Sent from my HTC One using xda app-developers app

Is the boot loop after flashing the update zip or installing the APK (or both)? Can anyone logcat the bootloop?
P

paulobrien said:
Is the boot loop after flashing the update zip or installing the APK (or both)? Can anyone logcat the bootloop?
P
Click to expand...
Click to collapse
It's after flashing the zip. The reboot after the APK went fine. Can't grab a logcat at the moment.

I installed the remapping of the menu button to the back button which has cleared up the only real thing I disliked about this phone. So thank you for that.
However I seemed to have lost vibration on the buttons. Not a huge deal but just thought I'd point it out in case I am just overlooking something.
Thanks.
Sent from my HTC One using xda app-developers app

berdo said:
I installed the remapping of the menu button to the back button which has cleared up the only real thing I disliked about this phone. So thank you for that.
However I seemed to have lost vibration on the buttons. Not a huge deal but just thought I'd point it out in case I am just overlooking something.
Thanks.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
So were you able to flash the zip without getting stuck in a bootloop?

uberamd said:
So were you able to flash the zip without getting stuck in a bootloop?
Click to expand...
Click to collapse
I know I was, I also did the menu thing.
Sent from my HTC One using xda premium

uberamd said:
So were you able to flash the zip without getting stuck in a bootloop?
Click to expand...
Click to collapse
Yes, I had no issues with a bootloop. I was also able to figure out the haptic feedback issue. Toolkit is definitely worth it.

berdo said:
Yes, I had no issues with a bootloop. I was also able to figure out the haptic feedback issue. Toolkit is definitely worth it.
Click to expand...
Click to collapse
What did you do to figure that out?
Sent from my HTC One using xda premium

cdordon said:
What did you do to figure that out?
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
Well this is what I did. I had enabled the remapping of the back button + disabling system notifications specifically so I could get rid of the stupid battery saver notification. When I disabled that notification that is when haptic feedback stopped. So I just started undoing each change till haptic feedback came back. I enabled the notification and restarted my phone and haptic feedback returned. So for fun, I went back and disabled the notification but haptic feedback remained though the notification was gone. I thought maybe a reboot would cause the issue to re-appear but so far so good. Not sure why but that fixed it for me.

how are you guys even getting this to install without write disable on kernel?

Version 15 is now online!
New in version 15 - New modules - HTC One: Show Blinkfeed icon in launcher, Google / Asus Nexus 7: Show Camera icon in launcher, Trackball Alert: Easy download link.
P

I don't know if it is possible but I sure would like to see a way to get the official July app to properly work
Sent from my HTC One using Tapatalk 2

JuannTwo3 said:
I don't know if it is possible but I sure would like to see a way to get the official July app to properly work
Sent from my HTC One using Tapatalk 2
Click to expand...
Click to collapse
What app is that? *confused*
P
Sent from my HTC One using Tapatalk 2

It's Hulu, the damned auto correct changed it
Sent from my HTC One using Tapatalk 2

Ah, I see. Region lock or device lock?
P

At&t HTC One. It may be because it's rooted; apparently Hulu has problems with rooted devices. A work around would be quite awesome
Sent from my HTC One using Tapatalk 2

[XMOD] MoDaCo Toolkit (with HTC One specific mods)

All those are specific to the HTC one?
I ask especially cuz I wanted to confirm that the nfc use when screen is locked tweak does work. Cuz I wasn't aware of any such tweak till now. If so awesome. Can it be tweaked to set to use nfc when screen unlocked but on and not when screen is off?
Sent from my HTC One using xda app-developers app

The NFC when screen is locked is not currently One compatible, it's coming tho.
P

MoDaCo Toolkit Pro is currently available free for a limited time - more details!
P

Hi Paul,
I installed Xposed and Modaco Toolkit but I cant get the back menu to show up neither the Enable app Buttons.
The only thing that did work was the blinkfeed to show in the launcher. Is it something that i am doing wrong?
Thanks for the kit!
---------- Post added at 01:28 PM ---------- Previous post was at 01:11 PM ----------
edwardlanti said:
Hi Paul,
I installed Xposed and Modaco Toolkit but I cant get the back menu to show up neither the Enable app Buttons.
The only thing that did work was the blinkfeed to show in the launcher. Is it something that i am doing wrong?
Thanks for the kit!
Click to expand...
Click to collapse
Forget it I got it to work.
There's a specific way how to install Xposed for the HTC One but I found out by reading through your website.
Thanks for the awesome tweaks

Does this have a modifier that will allow volume rocker music controls?

nrkid9 said:
Does this have a modifier that will allow volume rocker music controls?
Click to expand...
Click to collapse
Not yet!
P
Sent from my HTC One using Tapatalk 2

Google Wallet Time-Out
hey Paul, i finally got google wallet to launch with the updated apk u pushed out thru your toolkit, but bow it just times out when it says setting up wallet, this may take up to five minutes....any tips on how to get it working? i have yet to find a solution. thanks
paulobrien said:
Not yet!
P
Sent from my HTC One using Tapatalk 2
Click to expand...
Click to collapse

Hi Paul,
Thank you very much for the toolkit. I don't know what I'm missing, but I can't get wallet to work. I always get insufficient privileges message. Do you know what I'm doing wrong? BTW I'm using toolkit 18

Version 19 is now online for manual download and via auto-update (launch the MoDaCo Toolkit app to initiate a background update check).
Changes:
HTC One: Match battery image to %
On the HTC One the battery indicator can be rather misleading, this mod makes the image correspond exactly to how much battery is really left.
HTC One: Rename Flashlight to Torch
In the UK we don't call it a Flashlight, it's a torch. This fixes it!
Play Store: Lower case wishlist menu (for @le3ky!)
Rachid didn't like seeing 'My apps' and 'My Wishlist' together... so this makes it 'My wishlist'. Heh.
Note that Xposed Framework 2.1.4 now REQUIRED for HTC One (and Galaxy S4!) due to added support for resource replacement - see this post to download.
Don't forget that for a limited time you can get MoDaCo Toolkit Pro free - see this post for more details.
P

Seems Google wallet is not working on this toolkit. I am getting the same error as previous thread. Can you please fix it or remove it from your toolkit.
Sent from my HTC One using xda premium

rome425 said:
Hi Paul,
Thank you very much for the toolkit. I don't know what I'm missing, but I can't get wallet to work. I always get insufficient privileges message. Do you know what I'm doing wrong? BTW I'm using toolkit 18
Click to expand...
Click to collapse
i got the same problem if you figure out how to get google wallet working please let us now how ty :beer:
Sent from my HTC One using xda premium

hnt20 said:
Seems Google wallet is not working on this toolkit. I am getting the same error as previous thread. Can you please fix it or remove it from your toolkit.
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
Ouch, attitude much? It doesn't work on your device... Only the Sprint One seems to support it currently, it's down to the base ROM. It's in the Toolkit as in many devices, it does get it working.
P
Sent from my HTC One using Tapatalk 2

Sorry if that came out rudely. I am just really frustrated at Google wallet not working except on nexus or very limited devices. I wish dev can do something about it.
Sent from my HTC One using xda premium

Coming in MoDaCo Toolkit 20, 'EPM' (enhanced reboot menu)... which previously required a custom ROM.
P

paulobrien said:
Coming in MoDaCo Toolkit 20, 'EPM' (enhanced reboot menu)... which previously required a custom ROM.
P
Click to expand...
Click to collapse
Awesome!
I have a request.
I use WiFi Calling most of the time, and whenever I use it, notification comes on. This notification comes on only when WiFi Calling is used. Sometimes I don't want to use WiFi calling, and I have click on the notification, go into settings and turn off WiFi Calling. Is it possible to add this toggle in the notification? (Make it expandable). Also, when I'm connected to WiFi network, but WiFi calling is turned off, I have to go deep into the settings to turn WiFi Calling on, It would be outstanding if same WiFi calling notification would come on every time phone is connected to WiFi Network, so I can quickly turn WiFi calling back on if I need it.
I hope this is not confusing. I understand that you are probably not even familiar what WiFi calling is, so please let me know if you want me to do any testing (assuming it is possible).
Once again thanks for everything you do, I've been your fan from HTC Hero days
Sent from my HTC One

rome425, i'll add it to the list!
P

Version 20 is now online!
Changes:
new module - HTC One: Advanced reboot options
new module - HTC One: Disable high volume warning
new module - Nexus (all): Enable user switching on power menu
new module - Nexus (all): Enable multi-user support if unsupported on stock (e.g. Nexus 4)
Enjoy!
P

Version 21 is now available!
Changes:
Bug fix (duplicate item in settings)
Added superuser to manifest permissions
Minor wording changes
Added Adobe Flash Player download link
Added changelog link
[*]New module: System UI: Show battery percentage
[*]New module: HTC First: Hide carrier name
Yes, battery percentage!
ENJOY!
P

[MOD][XPOSED] Phab7 v1.00 no-reboot UI Switcher

Phab7 is an on-the-fly UI switcher: select Phone, Phablet, or Tablet, then tap the Change button. The switch happens immediately - no reboot needed. A separate option lets you switch settings screen layouts (e.g. the Settings app) between Phone-style (separate screens for categories and details), and Tablet-style (categories and details, side-by-side).
Unlike other solutions, Phab7 has no effect on your apps beyond for their Settings screens. In particular, it will not alter the size or layout of your launcher's icons or dock (nor will it cause the tablet-style app-drawer icon to appear).
Note: Google removed Tablet mode from KitKat, so it is not available if you're running Android 4.4.x.
Installation
Important: if you have a beta version of Phab7 (v0.9x) currently installed, you must uninstall it before installing v1.0. Android will refuse to install it if one of the betas is present.
if you don't already have XposedInstaller on your system, see this thread
install Phab7.apk the same way you'd install any other sideloaded app
enable Phab7 by reopening the XposedInstaller app and selecting 'Modules'
tap directly on the checkbox next to Phab7, then back out and reboot
after the initial reboot, you can open the Phab7 app and change UIs as many times as you wish without further reboots
Notes
Tablet UI mode is only available when running ICS or JB (v4.03 thru 4.3x). While Phab7 supports KitKat, it does not add back the Tablet mode that Google has removed.
Whether Phab7 works on your device depends almost entirely on your ROM's creators. If they removed the graphics and layouts needed for a given UI mode, SystemUI.apk is guaranteed to force-close when you select that mode. A "Keep-Or-Cancel" dialog will automatically restore your settings after 12 seconds if this happens when you choose an incompatible UI mode. Clear the "Unfortunately" popup and you're good to go.
the Settings-layout feature takes effect when an app is first launched. To see its effect on running apps (e.g. the system's Settings app). tap the "Recents" button and swipe the app away , then reopen the app.
File
Phab7.apk - v1.00
Credits
barrmulio - the first to identify the system changes needed to implement alternate UIs
_TB_TB_ - author of TabletUI trigger who first realized that UI-switching could be done by an Xposed module
History
2014/01/22 - v1.00 - initial stable release
2014/01/05 - v0.99 - added keep-or-cancel dialog
2013/12/13 - v0.97 - added scaling for all modes
2013/12/10 - v0.96 - fixed KitKat-specific bug
2013/12/09 - v0.95 - added Tablet UI scaling
2013/11/30 - v0.92 - added support for KitKat
2013/11/27 - v0.90 - initial release

Gonna try it on S4 v4.3
Sent from my GT-I9505 using XDA Premium 4 mobile app
---------- Post added at 08:08 AM ---------- Previous post was at 08:02 AM ----------
Ring of FC ;p
Sent from my GT-I9505 using XDA Premium 4 mobile app

Tried it, changes fine to tablet mode. Just a few layout issues. And the nav glow doesn't fade.
See screenshot.
Xperia Z running eXistenZ 4.10 rom.
Subscribed, this looks promising.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from Z Beast

For me with android 4.1 only settings work and status bar and nav bar don t work
Sent from my LT26i using Tapatalk

Great job. tested working on CM10. status bar looks monster
it could have better you provided DPI settings along with phab7. though i can manage with app settings
the give attachment is flashable zip i just extracted phab7.apk and installed normally
why this is not available in xposed Repo..

reversegear said:
why this is not available in xposed Repo..
Click to expand...
Click to collapse
I think because it's new and in beta
Sent from Z Beast

Now we need not wait for updated Paranoid!! OK Paranoid does do some of this stuff better/more consistantly than AppSetting and this module, but ...
Great!
Wanna outdo Paranoid: Tablet mode mostly more usable in landscape, so ... get the idea?
EDIT: Results using the mod on my LG P500 running cm-10.2 with 4,4 Google Now launcher: I can use AppSetting module to force this launcher to rotate but it does not handle this correctly.
Settings UIs work as promised! This is what I really missed not having Paranoid.
Navigation bar: Question -- what if I do not use one (phone has HW buttons--remember those)? Module should accept phone setting.
Anyway, tablet mode: Repeated FCs of systemUI until I changed to other mode:
Phablet mode: Navigation bar shows as promised. Notifications not effected.
Phone mode: No way to correctly test with this launcher.
Went back to default: Icon bar, no navigation bar.
If I remember from Paranoid, tablet mode put notifications bar on the bottom right. Phablet left it on top, opening to half-height, had to change dpi to fit it to screen width correctly. So tablet mode, once working, would either have both at bottom right justified or just the notifications as chosen in the phone's settings! Someone check current Paranoid.

Compatible with KitKat?
Wysłane z mojego Ascend G510 przy użyciu Tapatalka

Don't flash that zip!
reversegear said:
the give attachment is flashable zip i just extracted phab7.apk and installed normally
Click to expand...
Click to collapse
OMG!!!! My apologies! The zip that was posted (in error) was only for the Hisense Sero 7 Pro and contained a tablet-specific mod to SystemUI.apk.
The script in that zip checks for the model, so it should have failed if you tried to flash it on any other device. However, if somehow you succeeded in flashing it, you will have to restore your ROM's original SystemUI.apk. The original, along with SystemUI.odex if present, is in your /system/app folder with '-org' appended to it. If you have problems handling this, I can create an update.zip to do this for you.
Again, my apologies - it was late...

This's amazing. Thanks a lot dev. Looking forward for new versions:laugh:

Saeedblack said:
For me with android 4.1 only settings work and status bar and nav bar don t work
Click to expand...
Click to collapse
Dovidhalevi said:
tablet mode: Repeated FCs of systemUI until I changed to other mode:
Phablet mode: Navigation bar shows as promised. Notifications not effected.
Phone mode: No way to correctly test with this launcher.
Click to expand...
Click to collapse
Generally speaking: if "nothing happens", the issue probably lies within Phab7; if SystemUI FCs, then it's probably your ROM.
For Phab7 problems, XposedInstaller's debug.log should identify the problem - you can find it in /data/data/de.robv.android.xposed.installer/log/debug.log. Pull the file and attach it to a posting. For ROM problems, I'd need a logcat log that covers the time period when the FC occurred. If you need help generating one, let me know. (logcat logs for Phab7 issues are certainly welcome too, however, they have to include system startup to be useful.)
For SystemUI FCs, a possible cause is vendor customization of a particular NavBar layout that wasn't carried over to the other versions. The tablet I use is a perfect example. It defaults to Phablet and has a screenshot button (which most everyone hates). The button wasn't implemented for Phone since they assumed it would never be used, so SystemUI FCs in Phone UI when their code goes looking for a button that doesn't exist. To get it to work, I had to patch their systemui.apk to get rid of both the button and the code that references it. This is not something I'd want to try on a device I don't own.
Bottom line: I'd be happy to implement reasonable workarounds to enhance compatibility with the widest range of devices, but even then, not all modes will work with all devices.

dolorespark said:
Generally speaking: if "nothing happens", the issue probably lies within Phab7; if SystemUI FCs, then it's probably your ROM.
For Phab7 problems, XposedInstaller's debug.log should identify the problem - you can find it in /data/data/de.robv.android.xposed.installer/log/debug.log. Pull the file and attach it to a posting. For ROM problems, I'd need a logcat log that covers the time period when the FC occurred. If you need help generating one, let me know. (logcat logs for Phab7 issues are certainly welcome too, however, they have to include system startup to be useful.)
For SystemUI FCs, a possible cause is vendor customization of a particular NavBar layout that wasn't carried over to the other versions. The tablet I use is a perfect example. It defaults to Phablet and has a screenshot button (which most everyone hates). The button wasn't implemented for Phone since they assumed it would never be used, so SystemUI FCs in Phone UI when their code goes looking for a button that doesn't exist. To get it to work, I had to patch their systemui.apk to get rid of both the button and the code that references it. This is not something I'd want to try on a device I don't own.
Bottom line: I'd be happy to implement reasonable workarounds to enhance compatibility with the widest range of devices, but even then, not all modes will work with all devices.
Click to expand...
Click to collapse
and this is an older device.
I am attaching the debug.log, but changing the name to debug.txt to get in on here.

On my N7, checking 'tablet' in system settings changes the module's menu just fine but has no effect on Rom settings.
Setting default ui to phablet didn't help either.
Debug log: https://www.dropbox.com/s/zlp89tbus6o23qi/xposed_debug_20131127_194414.log
N7(flo)-Rastakat-franco.kernel
N4(mako)-PKK-franco.kernel

dolorespark said:
Generally speaking: if "nothing happens", the issue probably lies within Phab7; if SystemUI FCs, then it's probably your ROM.
For Phab7 problems, XposedInstaller's debug.log should identify the problem - you can find it in /data/data/de.robv.android.xposed.installer/log/debug.log. Pull the file and attach it to a posting. For ROM problems, I'd need a logcat log that covers the time period when the FC occurred. If you need help generating one, let me know. (logcat logs for Phab7 issues are certainly welcome too, however, they have to include system startup to be useful.)
For SystemUI FCs, a possible cause is vendor customization of a particular NavBar layout that wasn't carried over to the other versions. The tablet I use is a perfect example. It defaults to Phablet and has a screenshot button (which most everyone hates). The button wasn't implemented for Phone since they assumed it would never be used, so SystemUI FCs in Phone UI when their code goes looking for a button that doesn't exist. To get it to work, I had to patch their systemui.apk to get rid of both the button and the code that references it. This is not something I'd want to try on a device I don't own.
Bottom line: I'd be happy to implement reasonable workarounds to enhance compatibility with the widest range of devices, but even then, not all modes will work with all devices.
Click to expand...
Click to collapse
for me it have been FC for first run and after reboot it never appear again but don t have FC
also here you are i attached log that you notice

No TabletUI in KitKat
MMeester said:
On my N7, checking 'tablet' in system settings changes the module's menu just fine but has no effect on Rom settings. Setting default ui to phablet didn't help either.
N7(flo)-Rastakat-franco.kernel
Click to expand...
Click to collapse
Is this a KitKat-based ROM? Sadly, all of the code and resources needed to support Tablet UI have been stripped from Android v4.4. Because Phab7 v0.9 doesn't make provisions for this change, the UI switcher doesn't work. I will fix that ASAP so that at least Phone and Phablet are available. Restoring Tablet UI may be more than an Xposed module can/should do, but I'll investigate...
However, the Settings screen mod should still work. As mentioned in the OP, if the system's Settings app is already running, you'll have to remove it from "Recents" and reopen it. If you reboot with "Tablet-style" settings in place and it still doesn't work, let me know.
Dovidhalevi said:
and this is an older device.
I am attaching the debug.log, but changing the name to debug.txt to get in on here.
Click to expand...
Click to collapse
You didn't describe where you're having problems. During one session, one of your other Xposed modules (com.wisdomsky.xploit) failed every time, even when Phab7 hadn't made any changes. After a reboot, the problems were gone but so were Phab7's standard messages. What changed?

dolorespark said:
You didn't describe where you're having problems. During one session, one of your other Xposed modules (com.wisdomsky.xploit) failed every time, even when Phab7 hadn't made any changes. After a reboot, the problems were gone but so were Phab7's standard messages. What changed?
Click to expand...
Click to collapse
I first tried it before rebooting, then realized that it cannot work that way and rebooted. Then Phab7 worked as described.
Since wisdonsky operates on the notifications bar, could be that the interaction with tablet mode trying to move that is what is noted.

dolorespark said:
Is this a KitKat-based ROM?
Click to expand...
Click to collapse
Yes.
However, the Settings screen mod should still work. As mentioned in the OP, if the system's Settings app is already running, you'll have to remove it from "Recents" and reopen it. If you reboot with "Tablet-style" settings in place and it still doesn't work, let me know.
Click to expand...
Click to collapse
Sadly, no change in settings app after a reboot. Do you need any logs?
Thank you for looking into the issue.
N7(flo)-Rastakat-franco.kernel
N4(mako)-PKK-franco.kernel

Can I ask what in the system side of things this is targeting? Only asking because I had a problem with Tablet mode where I changed compatibility mode, and that then caused constant FC of SystemUI.
Also where are the settings stored? I managed to get out of the fc loop, but am now left with a layout problem of my System UI. Nothing major, but even if I change SystemUI, it persists.
Any help appreciated.

Metallijim said:
Can I ask what in the system side of things this is targeting? Only asking because I had a problem with Tablet mode where I changed compatibility mode, and that then caused constant FC of SystemUI.
Also where are the settings stored? I managed to get out of the fc loop, but am now left with a layout problem of my System UI. Nothing major, but even if I change SystemUI, it persists.
Click to expand...
Click to collapse
Phab7 is designed to do as little as possible to achieve its goals - in some cases, perhaps too little. For Phone and Phablet, it does some setup when SysUI starts and that's it. For Tablet, it has to be slightly more intrusive but not much.
Sadly, I had no way to test compatibility mode so I'm not surprised that it has issues. Recovery from most any problem should be as simple as switching to another UI. In this case, getting out of TabletUI, then returning without touching the compatibility button should cure what ails you.
If you get repeated FCs in SystemUI, one way out is to leave the toast up there, then from ADB, delete /data/data/com.e_vertise.dopa.phab7/shared_prefs/settings.xml. When you dismiss the toast and SysUI restarts, you should be back to your device's default settings.
Note: if I understand things correctly, Android may try to reload SysUI's Java code several times using the same process before it gives up and kills that process. Once it restarts SystemUI using a new process, you're certain to be back to normal if you've deleted Phab7's settings file.

We'll soon find out if it works on KitKat. Yes I know how to disable Xposed from recovery. Using it on KitKat doesn't seem to cause any crashes, but it doesn't do anything at all on KitKat.
Sent from my Nexus 7 using Tapatalk 4

[AOSP/CM/HTC][LP][MM] Knock Code Lockscreen (while screen on)

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

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.

Reserved
Screenshots
Knock Code Entry
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Custom shortcut selection
Some settings
More screenshots

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 @Maxr1998)
- Hide module from launcher (thanks @Maxr1998)
- Change pattern size
- Hide emergency button text but keep button
- Vibration settings
- Module active checker (thanks @Maxr1998)
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)

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

Whats the effect of this module on battery? I think this is like doubletap2wake function which is a real battery drainer.
Sent from my Nexus 5 using Tapatalk

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.

pradhyu69 said:
Whats the effect of this module on battery? I think this is like doubletap2wake function which is a real battery drainer.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
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.

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

Benrap said:
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.
Click to expand...
Click to collapse
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!
pradhyu69 said:
Whats the effect of this module on battery? I think this is like doubletap2wake function which is a real battery drainer.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
This module only works while screen on, and therefore, is not the kind of battery drainer that you are taking about.
Dhaval2904 said:
I tried this module, and after restart my phone is stuck at lock screen.. I tried the default pattern to unlock but nothing happens.. Please someone help me out
Click to expand...
Click to collapse
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)
Code:
adb logcat *:E > logcat.txt

Dhaval2904 said:
I tried this module, and after restart my phone is stuck at lock screen.. I tried the default pattern to unlock but nothing happens..
Please someone help me out
Click to expand...
Click to collapse
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.

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.

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
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...

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
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.

RusherDude said:
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
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.
Click to expand...
Click to collapse
For your first suggestion, you should refer to http://forum.xda-developers.com/nex...pp-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!

Bodenseematze said:
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
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...
Click to expand...
Click to collapse
Yes, that is the expected behaviour. It emulates stock, wherein you swipe up the screen to show the pattern entry or the pin entry.

Bodenseematze said:
Is that additional "swipe up" - step normal?
BTW, I'm using the lightning launcher if that matters...
Click to expand...
Click to collapse
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

Dhaval2904 said:
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
Click to expand...
Click to collapse
aillez said:
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.
Click to expand...
Click to collapse
RusherDude said:
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
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.
Click to expand...
Click to collapse
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?
@RusherDude, 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!

Works well on Z3 5.1.1 with smart lock

Rijul.A said:
For your first suggestion, you should refer to http://forum.xda-developers.com/nex...pp-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!
Click to expand...
Click to collapse
Thanks for the fast answer! I will try logcat when Im back home. Also that post you linked, will investigate it, thanks!
Rijul.A said:
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?
@RusherDude, 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!
Click to expand...
Click to collapse
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!

Tips and tweaks for running with CM

Thanks to @biktor_gj and his development skills, it all started here, below are the things I've managed to get working either partially or fully. Once a stable CM 13 is released, this post is likely to be updated.
Fully charge your watch first. Things below will take considerable time to configure to your liking; it's better to have enough battery to fully test the configuration.
1. Because CM 12 is a 5.1 build, you'll have to get Play Services from a Lollipop apk (I got mine from apkmirror), and install Gapps (mine is a modular nano; it will take 10-20 minutes). I suggest wiping Dalvik cache from TWRP after installing Gapps - my unit was very unresponsive until I wiped Dalvik and it rebuilt all 98 apps (your app count may vary).
2. Push notifications - get the Desktop Notifications app. Until Bluetooth is working properly, get Desktop Notifications (yes, it's only via WiFi tethering, it's cloud-based, which sucks, I hate it, but oh well). Configure and test it on another Android device first (provided you have one) or a computer, so that you can successfully get notifications to begin with and aren't wasting your time on the tiny 200-dpi Gear S screen. Keep in mind that because it's Wifi-tether, the battery life may suffer. Because I'm still testing various things on and off (primarily with Tasker), I haven't had a chance to test the battery from 100% in a fully-working state.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
3. Tasker profiles on the watch; this section is likely to be updated every now and again, as I tweak more and more settings. You have to install Tasker on the watch.
3.1. Watch notifications -> Wake Device and Vibrate.
Get Secure Settings as well as Auto Notification from Play Store, go to Tasker and create a new profile. Profile details/conditions are "Notify" and "Display State Off". "Notify" comes from the Auto Notification module/plugin. Configure -> Action Type = "Created Only"; Persistency = "Non-Persistent", Apps = check "Desktop Notifications". Task would have Vibration and Wake Device (Secure Settings -> Actions -> Wake Device). Vibration duration is whatever you choose; mine is set to 200ms.
3.2. [not ideal but most reliable] Cover to Wake -> upon covering the device light sensor while the screen is off, it wakes the device and briefly lights it up for a couple of seconds so you see the time, etc.
Profile conditions are "Light Level 0 to 1" and "Display State Off". Task is - "Wake Device" from Secure Settings. Configure that as you wish.

-LBT- said:
Thanks to @biktor_gj and his development skills, it all started here, below are the things I've managed to get working either partially or fully. Once a stable CM 13 is released, this post is likely to be updated.
Fully charge your watch first. Things below will take considerable time to configure to your liking; it's better to have enough battery to fully test the configuration.
1. Because CM 12 is a 5.1 build, you'll have to get Play Services from a Lollipop apk (I got mine from apkmirror), and install Gapps (mine is a modular nano; it will take 10-20 minutes). I suggest wiping Dalvik cache from TWRP after installing Gapps - my unit was very unresponsive until I wiped Dalvik and it rebuilt all 98 apps (your app count may vary).
2. Push notifications - get the Desktop Notifications app. Until Bluetooth is working properly, get Desktop Notifications (yes, it's only via WiFi tethering, it's cloud-based, which sucks, I hate it, but oh well). Configure and test it on another Android device first (provided you have one) or a computer, so that you can successfully get notifications to begin with and aren't wasting your time on the tiny 200-dpi Gear S screen. Keep in mind that because it's Wifi-tether, the battery life may suffer. Because I'm still testing various things on and off (primarily with Tasker), I haven't had a chance to test the battery from 100% in a fully-working state.
View attachment 3609050
3. Tasker profiles on the watch; this section is likely to be updated every now and again, as I tweak more and more settings. You have to install Tasker on the watch.
3.1. Watch notifications -> Wake Device and Vibrate.
Get Secure Settings as well as Auto Notification from Play Store, go to Tasker and create a new profile. Profile details/conditions are "Notify" and "Display State Off". "Notify" comes from the Auto Notification module/plugin. Configure -> Action Type = "Created Only"; Persistency = "Non-Persistent", Apps = check "Desktop Notifications". Task would have Vibration and Wake Device (Secure Settings -> Actions -> Wake Device). Vibration duration is whatever you choose; mine is set to 200ms.
3.2. Shake to Wake -> upon shaking the device while the screen is off (you flick your wrist), it wakes the device and briefly lights it up for a couple of seconds so you see the time.
Profile conditions are "Shake Up-Down" (sensitivity High, duration Very Short) and "Display State Off". Task is - "Wake Device" from Secure Settings. Configure that as you wish.
Click to expand...
Click to collapse
I appreciate your advice! I personally like to install (no frills Cpu) and clock the device do 300-600mhz for extra battery savings. You said it right, we are lucky to have Biktor!!!

GOIGIG said:
...clock the device do 300-600mhz for extra battery savings...
Click to expand...
Click to collapse
Don't we have to have a compatible kernel for that? If so, do you know we actually have it?

No frills Cpu works like a charm, I have been using it since day 1, I test it on every device I get honestly its the best interface with the most compatibility, depending on Your kernal it works on the note 5 lol
Sent from my SM-N920T using Tapatalk

GOIGIG said:
its the best interface with the most compatibility
Click to expand...
Click to collapse
Does it affect WiFi performance or range?

-LBT- said:
Does it affect WiFi performance or range?
Click to expand...
Click to collapse
Not at all, I apply on boot, games don't play well when it's clocked that low on powersave but it lasts and the more updates the better it gets stability wise, I always thought no frills caused some of the issues. Enable SU in developer settings if you have not
Sent from my SM-N920T using Tapatalk

1. For some reason, the shaking profile isn't working as well as I had hoped. I'm looking into either adjusting it further, or incorporating the accelerometer "face-up", proximity or pressure sensing profile, which I'm not entirely sure would work since there may be no sensors for that on Gear S.
Accelerometer isn't that great, either, see below - the watch is on its side, yet the accelerometer says that it's facing up.
2. Tasker light sensor isn't working for me either - with the condition of "Light sensor values 1 through 5 + Display State Off" followed by "Wake Device" task, nothing is happening when I cover the light sensor while the device is off. I'll have to do a bit more digging on how the light sensor is handled in Tasker.
3. Neither proximity nor orientation sensors are being detected by the Sensor Test app. My hopes for the pressure sensor quickly vanished when I discovered that it's not the screen pressure but atmospheric pressure.
4. The light sensor monitoring was off (genius) - got the light sensor to work. Set the profile to "Screen Off + Light Level 0 to 1" -> Wake Device. So far, this seems to be the most reliable waking option. EDIT: unless you're wearing long sleeves, of course. Just can't catch a break with this screen wake.

Are there any other apps that you'd recommend for this watch? I currently use calendar widget: month, and mighty text. I had to change the dpi to get mighty text to scale properly. Coincidentally, changing the dpi also allowed me to use the calculator widget.

nghiaxp said:
Are there any other apps that you'd recommend for this watch? I currently use calendar widget: month, and mighty text. I had to change the dpi to get mighty text to scale properly. Coincidentally, changing the dpi also allowed me to use the calculator widget.
Click to expand...
Click to collapse
I'll be waiting for the CM 13 update. If Bluetooth becomes a reliable tethering option (right now I'm paired to the phone but cannot browse internet) and sensors get a better implementation, I'll think of more things to do. So far the shake sensor presents a concern, as it works on the first try but stops on the third or fourth attempt (the shake movement of the wrist is literally identical).

nghiaxp said:
Are there any other apps that you'd recommend for this watch? I currently use calendar widget: month, and mighty text. I had to change the dpi to get mighty text to scale properly. Coincidentally, changing the dpi also allowed me to use the calculator widget.
Click to expand...
Click to collapse
I recommend either dynamic notifications, or acdisplay for a better lockscreen. You can configure them to turn on the screen for a few seconds when you get notification.
Set their background to pure black for battery savings.
Edit: they're nice but I have to say don't bother with the little ram we have. I feel kitkat rom would've been better to port to Gear S
Edit 2: Install this https://play.google.com/store/apps/details?id=org.azasoft.free.swapper set it to 120mb. helps with ram.
Also this https://play.google.com/store/apps/details?id=com.chummy.jezebel.blacked.out and apply in themes app. helps with amoled power savings

Not available on "Next" to update the application .apk. This is due to the resolution of 200dpi. Therefore it is necessary to change the settings at 180dpi resolution. But it comes a full restart of the interface. After the installation is restarted again to return 200 dpi. Is it possible to update the application without changing the dpi? I have no established GAPPS for ideological reasons.

Shum Channel said:
Not available on "Next" to update the application .apk. This is due to the resolution of 200dpi. Therefore it is necessary to change the settings at 180dpi resolution. But it comes a full restart of the interface. After the installation is restarted again to return 200 dpi. Is it possible to update the application without changing the dpi? I have no established GAPPS for ideological reasons.
Click to expand...
Click to collapse
There's an experimental lollipop version of app settings xposed module that lets you choose dpi of specific apps. I'll post a link when i can get to a computer. (At work). Then you can set dpi of package installer only

According to the link below, pushbullet allows you to sync notifications between two or more android devices, so this should have the desired feature of receiving notifications from the phone that the Gear S is paired with.
http://www.androidauthority.com/pushbullet-notifications-update-384910/

scottgl9 said:
According to the link below, pushbullet allows you to sync notifications between two or more android devices, so this should have the desired feature of receiving notifications from the phone that the Gear S is paired with.
http://www.androidauthority.com/pushbullet-notifications-update-384910/
Click to expand...
Click to collapse
I think it's a paid feature and works through internet though. I actually installed SWAPPLink and it does notification through bluetooth connection (It crashes often, but notifications still work, just hit ok on the crash message and it'll keep working)
Also I got it from the Swapplink Google + community, where he posts beta versions. I don't know when last the play store version has been updated.

Fitting Calculator App
nghiaxp said:
Are there any other apps that you'd recommend for this watch? I currently use calendar widget: month, and mighty text. I had to change the dpi to get mighty text to scale properly. Coincidentally, changing the dpi also allowed me to use the calculator widget.
Click to expand...
Click to collapse
Have a look at this:
Calculator App called "Rechner" , from TricolorCat
It is a Perfect fitting and working calculator. (Sorry, still not allowed to post any Links...)
No need to change the Dpi any longer...
---------- Post added at 08:02 PM ---------- Previous post was at 07:29 PM ----------
G1NT0NN1C said:
Have a look at this:
Calculator App called "Rechner" , from TricolorCat
It is a Perfect fitting and working calculator. (Sorry, still not allowed to post any Links...)
No need to change the Dpi any longer...
Click to expand...
Click to collapse
The rondo Icon pack is a free pack of very Clear and simple icons. It fits perfectly to the small Display of the gear s.

what is this tasker thingy?

Hi guys! I dont know if this thread is alive anymore. But I'm currently using the latest? android 5.1.1 on my gear s and its awesome! compared to regular tizen...
For notifications i'm using m2d sender / receiver. it works perfectly! pushes all notifications from my phone to my watch. in the new update you can set m2d receiver up to be used on a watch. works very well!=) check it out!
The only issue I have with running android on is the RAM. i only have amax of 100MB ram free! Anyone being able to free up more?

Hello,
how can i use on CM the Heart Rate Sensor and UV Sensor?

there is an app for bluetooth notifications between gear s cm and android phone?

How stable is cm on the gear s?
Sent from my SM-G955F using Tapatalk

Better Mobile App

welcome