Related
Hi all. I use the pattern lockscreen on my devices (it happens with any style of lockscreen anyway) and one of the very first apps that I install on my smartphones and tablet is a widget to temporarily disable the lockscreen while at home and whenever else it comes handy to do so. I have used various apps for this but it's 2 years that I use Battery Indicator Pro which is also useful in other ways.
Everything has always worked fine on my Galaxy S (Froyo then Gingerbread), SII (Gingerbread), Note (Gingerbread) and Galaxy Tab 10.1" (Honeycomb) then in January I flashed the Kang ICS on the G.Tab for a few months and more recently I flashed CM9 on my Galaxy S and on both of them when I disable the lockscreen everything seems to work as it should until I tap on any notification in the notification bar. Then my lockscreen appears, I am prompted to unlock it and from then on the lockscreen gets re-enabled until I "re-enable" it via the app I am using and then disable it again. This works until the next time I tap on another notification...
This is not device-specific because I have read about other folks having the same problem on other devices and it's not app-specific because I have tried several apps and widgets with the same exact result. This is something ICS-related.
Please tell me there is a solution for this! On my tablet and my Galaxy S it's extremely annoying but on my Note, my daily driver, it would be unbearable
This is also one of the reasons why I have not yet updated my Note to ICS BTW...
And please don't tell me to "simply" disable it in the settings! LOL :laugh:
TIA
Hey, I'm having this problem too... have you find any solution for it??? I'm using an app called "Extended controls" which worked pretty fine in GB. I'm a Note owner too btw !!!!!
emalex87 said:
Hey, I'm having this problem too... have you find any solution for it??? I'm using an app called "Extended controls" which worked pretty fine in GB. I'm a Note owner too btw !!!!!
Click to expand...
Click to collapse
Nope, no solution other than avoiding tapping on notifications when the lockscreen is disabled...
To enable/disable the lockscreen I am now using the "No Lock Screen" widget (by Futon Redemption) and I have placed one of them on every page so it's at least quick and easy to enable/disable the lockscreen.
I have also discovered that this new behaviour is only triggered by the secure lockscreens (pattern, PIN etc.) but since the least amount of security I am confortable with is the pattern lockscreen that doesn't help me at all...
I can't believe very few people seem to notice, do people actually USE their smartphones?? Or do people just use the unsecure lockscreen on devices where we keep more and more valuable and sentitive personal data??
I think that being able to easily temporarily disable the lockscreen should be one of the very basic operating system features... (as, for example, should be recurrent notifications of missed calls/msgs/etc, another thing for which we have to rely on 3rd party apps...)
Anyone?
I've been having this issue ever since I upgraded to ICS on my galaxy note. I was hoping that the upgrade to JB on my Galaxy Note 2 would fix the issue, but it doesn't.
I used to use a widget on the screen, now I use NFC and NFC Tasker to enable and disable what I call "Home Mode." (wifi, lock screen, volume for ringer, etc).
I know now that it's not a bug for my Note. It's a bug in Android in general. It is really starting to bug me. I'm going to subscribe to this thread because I'm very interested in a solution. It's a pain in the neck
I've looked everywhere for an answer to this, but so far to no avail. Is there a way to manually disable this Knock On feature included in the stock software? I'm running CyanogenMod 11 nightlies and it causes my phone to crash 50% of the time and gets annoying after a while. I looked through all the system files on the phone and can't even find a pointer. Be as complicated as you want with your answer. Thanks.
P.S. This is not a new problem with CM11. Did this with 10.2 as well.
On the stock software its easy !! Go to configurations > general > gesture > on/off screen (its the first option) !!
Hope i could help:good:
greenshell said:
I've looked everywhere for an answer to this, but so far to no avail. Is there a way to manually disable this Knock On feature included in the stock software? I'm running CyanogenMod 11 nightlies and it causes my phone to crash 50% of the time and gets annoying after a while. I looked through all the system files on the phone and can't even find a pointer. Be as complicated as you want with your answer. Thanks.
P.S. This is not a new problem with CM11. Did this with 10.2 as well.
Click to expand...
Click to collapse
If your still trying to figure it out i found it after about 3 hours of searching its located in settings under display and lights just uncheck "double tap to wake"
Disable Knock on / Knock Off
Go to settings, device, display and lights, and uncheck double tap to wake. Then settings , personalization, Interface, Status bar, and uncheck double tap to sleep..
Worked for me.. Hope this helps
Thank you!
Is there a way to disable knock on during calls only? My face keeps unlocking my phone and apps are opened or settings changed. It's annoying.
Found a FIX disable Tap 2 Wake/ Knock code
Hi all, I have a LG F220K (LG Optimus GK). :silly:
And I'm running a modified version of LG G2 CM11 (currently on M6) on my mobile.
After flashing CM11 ROM I figured that the option to deactivate the Tap to wake/ Knock code feature is not available in the Settings menu itself.
The Tap wake function is something I hate as it turns on display and press buttons during calls, so somehow I was lost with all the forums having only questions yet no answers...
This is How I sorted it!!! (Sorry, I am not allowed to post images or links as a newbie)
1. Please install Kernel Tweaker from the play market (It's free).
2. Open the Kernel Tweaker, access the main menu of the app by tapping the top left hand corner.
3. Browse through to Kernel (Under Kernel Params) tap open.
4. You will see that it has two options Under Kernel Tweaks "Double Tap 2 wake" and "Sweep 2 Wake", there will be two ticked boxes.
5. Untick both boxes and exit!!!
Now you can tap on screen like no tomorrow but Tap to Wake/ Knock code is no more... :highfive:
A THANK wouldn't hurt!!!
Alexsha said:
Is there a way to disable knock on during calls only? My face keeps unlocking my phone and apps are opened or settings changed. It's annoying.
Click to expand...
Click to collapse
I 'm looking for that answer too..
Me as well! I hate Knock-On as it always turns on the screen in my pocket.
I tried Kernel Tweaker but there arent any options under Kernel Tweaks for me to choose from. Im running C-Rom 7.1 which is CM based I believe.
Is there an .apk or sys file I can disable? What kind of file and what is the name of the file/code that is responsible for Knock-On?
JJT211 said:
Me as well! I hate Knock-On as it always turns on the screen in my pocket.
I tried Kernel Tweaker but there arent any options under Kernel Tweaks for me to choose from. Im running C-Rom 7.1 which is CM based I believe.
Is there an .apk or sys file I can disable? What kind of file and what is the name of the file/code that is responsible for Knock-On?
Click to expand...
Click to collapse
I 'm looking for that answer too for cm-10.2.0-d802
You can probably try with "G2 Tweaksbox", it uses the xposed framework and has many tweaks available... hope this helps
Sent from my VS980 4G
This should work:
How to disable the Knock On feature on LG devices…: https://youtu.be/gIgHPYeH6gs
Hello!
I've got a problem with my Desire.
Few days ago, my digitizer got damaged. I've got about 5mm of inactive touchscreen on the top. This makes notification bar inoperable (i have to rotate phone to open it). I want to buy new phone anyway, but I will use Desire as long as it will work.
So here's my idea to map Search button to notifications. I'm not using this button anyway.
Is there any way to do this? My phone is rooted, running on custom rom based on Android 4.2.2
Help me please!
I think exposed addition has that option. Just get the installer and u can download the module from the app.
Another option is launchers with gestures, i used go and apex, they have such option, u can set slide down for notification or double tap.
Cheers....
Sent from my HTC Desire S using Tapatalk 2
Sounds interesting, gonna try this framework!
Also, I've got Apex onboard right now, but I'm afraid gestures will not work when I've got another application in foreground. Worth trying anyway.
Thanks for now!
Checked out both suggestions, and none worked well...
Apex - as I said before: Gestures aren't global - works only in main screen
Xposed Additions - there's such option in this module, but i can't see any notifications-related There's also paid version of Additions but I'm not into buying yet.
Any further ideas?
Sent from my Desire S using xda app-developers app
Yes, u are right, should have checked before suggesting xposed addition, they dont have such feature u wanted.
Since u have xposed, you can try Gravitybox. See if they have such funtion in their keyremap. They also have option to enable nav bar and pie.
Lmt, if i remember correctly, if i click on the clock on pie, the notification bar came down.
Sorry, currently on an old rom so cant test but only able to give blind suggestions.
Thank You again. I've installed GravityBox, and partly achieved my goal - I mapped notifications to menu button. There's no option to map anything to "Search" button, but I'll try to do it another way though.
Is there any secret to making this work better to wake up the phone. I cannot seem to hit it right to get it to unlock. Sensitivity adjust?
I like the phone otherwise.
Tap the screen quickly and firmly in the same spot two times. I have no problems with it using that method.
Train wreck for me. Double tap is horrible! I started a return through Amazon, wondering if I should try a replacement first though. I have huge lag issues too on this phone.
I am having the problem with tap to open too. There are many reviews on Amazon detailing the same thing. I sent an email to Alcatel support asking if they would be addressing this issue. I am still deciding if I want to keep the phone.
Last couple of days I have had more instances of misses with this than I had the first couple of days. But still I feel I have had better luck with the double-tap.... than many others over here so far. Usually a firm tap, with your fingers bent and the fingernails almost hitting the glass, works pretty well. But at times, even a firm tap will not work, and I have noticed that un-setting the option ( in Settings -> Gestures ) and then setting it back again gets it going again. This and the lag with loading apps may be related , and I hope Alcatel release a 5.1 update soon.
I've only had an issue with this once and a reboot fixed it. I think in some cases people are not hitting the screen firmly and quickly. Also the may not be hitting the same spot as well. I have seen other phones that use the knock unlock gesture but with a knock code and maybe some people thought they could hit the screen where ever they wanted between the 2 knocks. I'm just guessing here.
steavis00 said:
Is there any secret to making this work better to wake up the phone. I cannot seem to hit it right to get it to unlock. Sensitivity adjust?
I like the phone otherwise.
Click to expand...
Click to collapse
what i did was disable the two incoming call option in gesture, now doubletap with no problem.
Turning off "Turn Over to Mute" seems to help with tapping to wake screen, but not tap to shut off screen.
Borghi said:
Turning off "Turn Over to Mute" seems to help with tapping to wake screen, but not tap to shut off screen.
Click to expand...
Click to collapse
in my phone wake and shut off works perfectly fine,and i have turn off mute and the alarm.
goseup said:
in my phone wake and shut off works perfectly fine,and i have turn off mute and the alarm.
Click to expand...
Click to collapse
I believe I have found the root cause of the problem. Right after I got the phone I installed Nova Launcher. I started playing around and tried switching back to the stock launcher. Immediately the double tap feature started to work consistently. Hopefully it will STAY working and Nova will update their launcher to support the double tap feature fully.
Borghi said:
I believe I have found the root cause of the problem. Right after I got the phone I installed Nova Launcher. I started playing around and tried switching back to the stock launcher. Immediately the double tap feature started to work consistently. Hopefully it will STAY working and Nova will update their launcher to support the double tap feature fully.
Click to expand...
Click to collapse
I doubt if the launcher is the issue. When the screen is off the launcher is not in control of the phone, the OS is in control. Also, I use Nova Prime and have only had 1 problem with Double Tap To Wake in the past 8 days.
Shodan5150 said:
I doubt if the launcher is the issue. When the screen is off the launcher is not in control of the phone, the OS is in control. Also, I use Nova Prime and have only had 1 problem with Double Tap To Wake in the past 8 days.
Click to expand...
Click to collapse
I partly agree with your statement. As I understand Nova Prime includes support for double tap. The free app does not. Using the free app I can double tap to wake the phone, but not to sleep. Using the stock launcher, both functions work perfectly. I tried installing the Google Now launcher and it was the same as the free Nova launcher. No double tap to sleep.
I am new to Xda (or forums in general), but I had tons of issues with the double tap to wake feature not working. This was a shame because everything else I loved about this phone (only other thing I would change is a slight processor boost; a Snappy 801 would be perfect). Anyways, I finally got around the issue by performing these steps:
1-In Settings, navigate to Gestures and make sure 'Turn over to mute' is unchecked and 'Turn over to activate' is disabled.
2-Don't know if this is mandatory, but I also disabled the Func shortcuts in the Lock Screen Settings as well.
3-Reboot the device and don't touch these settings again
For some reason, I think Alcatel's software was not appropriately tested with all of these functions enabled. I am not sure, I just know I am having much higher hit rates (works almost every time) after performing the above steps.
Hope it works for you guys.
Lastly, if the double tap starts having issues again, just run a reboot and it should fix it (I just had to reboot after 30+ hours of standby).
goseup said:
what i did was disable the two incoming call option in gesture, now doubletap with no problem.
Click to expand...
Click to collapse
YAY, THIS THING WORKS FOR ME, NOW IT DOESN'T LAG, D2W AND D2S, USING STOCK LAUNCHER, tried using other premium launchers, problem is smart lock doesn't work
THANKS
---------- Post added at 09:50 PM ---------- Previous post was at 09:43 PM ----------
works well now, the only thing we need is ROOT, unlocked bootloader is easy to achieved on this phone.
Borghi said:
I believe I have found the root cause of the problem. Right after I got the phone I installed Nova Launcher. I started playing around and tried switching back to the stock launcher. Immediately the double tap feature started to work consistently. Hopefully it will STAY working and Nova will update their launcher to support the double tap feature fully.
Click to expand...
Click to collapse
Nova has it's own double tap gesture. If you want it to turn off the screen then you will have to have it call a program like "screen off" to accomplish that. DT to wake is still handled by the lockscreen.
believe me i been looking for a way to make this double tap in look screen to work better, by accident i find out that tapping very lightly wake the phone all the time.
Double-tap not working for me. Running all stock, stock launcher.
Same here I can't get the double tap to work for anything, I tried turning off the features and func but nothing, my phone has its days where it works fine and other days where it just doesn't.
Sent from my 6045I using XDA Free mobile app
My original suggestion to fix the double tap was to reboot, but I found a much quicker way. Go under gestures and turn it off and on again. Seems to work every time it gets wonky.
i notice that D2W work almost perfect while the phone on charger ...so it may be power saving mode that make the digitizer off after several minutes???!!!
Hey everyone, I received my Mate 8 about a week ago but no matter what I try I can't get now on tap working. Every official Google app has permission to do whatever it wants and I have the latest firmware version installed (and yes, now on tap is enabled within the Google app) but I still can't get it working. I've read that other people have the same problem. Has anyone else figured out how to fix this? Thanks in advance
Blood Blister said:
Hey everyone, I received my Mate 8 about a week ago but no matter what I try I can't get now on tap working. Every official Google app has permission to do whatever it wants and I have the latest firmware version installed (and yes, now on tap is enabled within the Google app) but I still can't get it working. I've read that other people have the same problem. Has anyone else figured out how to fix this? Thanks in advance
Click to expand...
Click to collapse
Sorry can you elaborate more? do you mean google now? as I know it's clashing with EMUI of Huawei at the moment unless others can correct me....
Well Google now works in general, "OK Google" speech recognition works fine as does pretty much everything else, the only things that don't work are the home button related gestures (holding home for Now On Tap and swiping up from home to get to your now cards).
Blood Blister said:
Well Google now works in general, "OK Google" speech recognition works fine as does pretty much everything else, the only things that don't work are the home button related gestures (holding home for Now On Tap and swiping up from home to get to your now cards).
Click to expand...
Click to collapse
Flash the international rom that should be released in the near future and im sure it will work much better.