Hi there,
Anyone knows how to disable the double tap to wake function on the lockscreen?? The real problem is that when the phone is in my pocket with the screen turned to my leg the phone wake and access the Emergency calls automaticaly.
The Androis version is: 4.2.2
ROM: 10.3.1.a.2.67
Kernel: 3.4.0-Unoficial-Doomkernel+
I've found a file on the root directory, but i'm a noobie on android development, the file is located at:
root/sys/android_touch/doubletap2wake
When I open the file with a text editor it contains only the number 1 inside, i've changed it to 0 and saved, the function was disabled, but when I restart the phone the number 1 comes back. There is any way to make it save permanently 0?
Sorry by the poor english...
Thanks!
rmachiavel said:
I've found a file on the root directory, but i'm a noobie on android development, the file is located at:
root/sys/android_touch/doubletap2wake
When I open the file with a text editor it contains only the number 1 inside, i've changed it to 0 and saved, the function was disabled, but when I restart the phone the number 1 comes back. There is any way to make it save permanently 0?
Sorry by the poor english...
Thanks!
Click to expand...
Click to collapse
The info is in the kernel thread - not hard to find.
http://forum.xda-developers.com/showpost.php?p=38935093&postcount=37
After installing sphinx rom v2 on my e988 i can't wake up my screen by pressing home button any one know how to enable it again ?
mhd.abbas.94 said:
After installing sphinx rom v2 on my e988 i can't wake up my screen by pressing home button any one know how to enable it again ?
Click to expand...
Click to collapse
This will only work if the option was removed from the keylayout, so let's see if the option is there or not:
Use a root file manager and go to System/usr/keylayout
Edit the file "gk-kaypad-8064.kl" (how you edit the file depends on the file manager you are using, so I can't give you exact steps as to how to do this)
You should see stuff like:
key 114 volume_down
key 115 volume_up
etc
look at key 172:
If it was disabled from waking the phone, it will say:
key 172 HOME
If it has the option to wake the phone it should say:
key 172 HOME WAKE
-If it's like this already, then I can't help you further because the button is already set to wake the phone, so something else in the rom is preventing it from working.
-If it isn't already like this, then just add the WAKE (in all caps) part to it after a space and save the file. Make sure the permissions are still 644 (rw-r--r--) after saving. Reboot. Test and hopefully it should work. Again, if not, I can't help you any more because something else is preventing it from working.
BTW, I don't use Sphinx, but I actually hate the Home button waking my phone, so I always disable it after rooting. So I basically just remove the WAKE part.
spexwood said:
This will only work if the option was removed from the keylayout, so let's see if the option is there or not:
Use a root file manager and go to System/usr/keylayout
Edit the file "gk-kaypad-8064.kl" (how you edit the file depends on the file manager you are using, so I can't give you exact steps as to how to do this)
You should see stuff like:
key 114 volume_down
key 115 volume_up
etc
look at key 172:
If it was disabled from waking the phone, it will say:
key 172 HOME
If it has the option to wake the phone it should say:
key 172 HOME WAKE
-If it's like this already, then I can't help you further because the button is already set to wake the phone, so something else in the rom is preventing it from working.
-If it isn't already like this, then just add the WAKE (in all caps) part to it after a space and save the file. Make sure the permissions are still 644 (rw-r--r--) after saving. Reboot. Test and hopefully it should work. Again, if not, I can't help you any more because something else is preventing it from working.
BTW, I don't use Sphinx, but I actually hate the Home button waking my phone, so I always disable it after rooting. So I basically just remove the WAKE part.
Click to expand...
Click to collapse
Thanks a lot man
Does someone has another solution?
i got the same problem but in my file allready was written "WAKE".
Hello, this is my first time posting here. I was having some trouble with the touch screen not being responsive enough, sometimes missing my taps. So I installed this mod: http://forum.xda-developers.com/showthread.php?t=2347009&page=3
Not only did it not appear to change anything, after rebooting I found that my menu and back button no longer vibrate like they should (yes vibration is on in settings) and my q-button no longer does anything. And my home key does not turn the screen on now either. This has to be a simple key configuration change but someone please help me fix this issue Oh also I have the at&t version of the phone if that makes a difference.
Edit: I have found more information about this problem. One being that the mod I spoke of only changes the usr folder of the system folder which contains the key mappings gk-keypad-8064.kl file. I tested and trying to change the QuickButton command in the settings no longer affects this key mappings file as I believe it should. So somehow it either can't find the file (even though it's there) or thinks that the file is corrupt. So is there anyone who has the stock gk-keypad-8064.kl file I can use? Or maybe there should be different permission settings other that rw r r? Please let me know as I think this is the main problem here.
xlJohnnyIcelx said:
Hello, this is my first time posting here. I was having some trouble with the touch screen not being responsive enough, sometimes missing my taps. So I installed this mod: http://forum.xda-developers.com/showthread.php?t=2347009&page=3
Not only did it not appear to change anything, after rebooting I found that my menu and back button no longer vibrate like they should (yes vibration is on in settings) and my q-button no longer does anything. And my home key does not turn the screen on now either. This has to be a simple key configuration change but someone please help me fix this issue Oh also I have the at&t version of the phone if that makes a difference.
Edit: I have found more information about this problem. One being that the mod I spoke of only changes the usr folder of the system folder which contains the key mappings gk-keypad-8064.kl file. I tested and trying to change the QuickButton command in the settings no longer affects this key mappings file as I believe it should. So somehow it either can't find the file (even though it's there) or thinks that the file is corrupt. So is there anyone who has the stock gk-keypad-8064.kl file I can use? Or maybe there should be different permission settings other that rw r r? Please let me know as I think this is the main problem here.
Click to expand...
Click to collapse
How about you try to flash back to the stock rom using the lg flash tool?
I fixed it with a work around. I used exposed additions to force haptic feedback and also to map the q button key. Hopefully if anyone else has this problem it will help them.
Hi all, i've jumped from OOS to CM12.1 and CM13 (and cm13 based roms) for some time, but today i wanted to give another shot to OOS 2.2.0 (and wanted to try boeffla's kernel as CM isn't official yet).
And i remembered why i could not stay on OOS after a few seconds... i really hate the hardware keys setup (recents-home-back).
I'm used to have Menu-Home-Back (and recents access from long press home, or press home from nova launcher).
I've been reading and then learning many things in the past few weeks, so i though i should try to edit those keys just like we did on CM, even if before switching to CM i've looked around and didn't find anything working to change these.
So, here it is.
What you need:
Rooted phone and file manager with root access (there are many but i love FX file explorer, and the root add-on is free).
You need to go to /system/usr/keylayout
Then make a backup of the Generic.kl file (to make it easier i make an archive of it by long press on the file, then archive, but a simple copy and paste will do).
After that, don't forget to unlock the system partition if needed (tap the little lock and accept to open it on fx file explorer).
Open Generic.kl with file editor.
What you need to know is that left key is key number 139, middle one is number 172 and right one is 158.
Functions that can be affected are: MENU HOME BACK APP_SWITCH VOICE_ASSIST.
But for some obscure reason, MENU acts like APP_SWITCH in oxygen OS, so the trick is to replace MENU with MENU VIRTUAL (this will emulate Menu button from on screen navbar, but you don't need to activate the navbar).
So, if you want for example this layout: Menu-Home-Back
You'll need to edit the Generic.kl and replace the Line
key 139 MENU
with
key 139 MENU VIRTUAL
(key 158 BACK and key 172 HOME don't need to change).
Another interesting point is that if you use xposed installer and Gravity Box LP, you can assign different functions to double press or long press on buttons, but it's working only with on screen navbar buttons... you see where i'm trying to get ?
If you modify the generic.kl file and replace MENU with MENU VIRTUAL and BACK with BACK VIRTUAL... then you'll be able to add custom actions with Gravity Box... like the one I really miss, hold back to kill.
I didn't try to replace HOME with HOME VIRTUAL as i can configure long press and double tap home from oxygen OS, but it may work exactly the same if you want something special from Gravity box.
For exemple, my setup is like that:
Menu-home-back
Menu long press => Switch last app
Home long press => Recent apps
Back long press => Kill foreground app
Double Tap Menu => Google Now
Double Tap Home => Screen off
Double Tap Back => Nothing
To sum up, on the phone, keys are:
key 139 - key 172 - key 158
You can affect different general functions to these, like:
MENU
HOME
BACK
APP_SWITCH
VOICE_ASSIST
and maybe more
You can add VIRTUAL behind the function to emulate the on screen navbar buttons (and it seems required for the menu, as it still calls the recent apps in OOS), and then you can add double tap or long press functions with gravity box.
You don't need to enable the navbar to get them working.
I don't know if i've been clear enough, as i'm not used to this kind of things (i wonder if that's not my first thread on XDA...), but i just hope this will be useful to some of you,
have a great day.
[Edit: Forgot to mention you need to reboot the device when it's done]
Great thread. Will test
Got a bit of an issue... I just experimented with this and it was providing very odd results. So, I copied the backup generic file back to the location... restarted the phone. Now, no buttons do anything. There's no way for me to get home so a restart is the only option I have by forcefully turning off the phone. I'm not sure what to do, the file looks absolutely fine. Any help please? I don't know what to do... I don't want to reflash the rom..
If you restored the original file, at the original place, I don't know why this would not get you back...
Did you try to change the behavior of key in settings?
Envoyé de mon ONE E1003 en utilisant Tapatalk
J0kker said:
If you restored the original file, at the original place, I don't know why this would not get you back...
Did you try to change the behavior of key in settings?
Envoyé de mon ONE E1003 en utilisant Tapatalk
Click to expand...
Click to collapse
Thanks for your help, but unusually it eventually sorted itself out. After 3 reboots the buttons began to work again... weird!
can you change hardware keys to [L-R] Recent Menu Back on CM13 using this method?
sphoenixp said:
can you change hardware keys to [L-R] Recent Menu Back on CM13 using this method?
Click to expand...
Click to collapse
Yes you can, but the file isn't the same, you should edit:
system/usr/keylayout/synaptics-rmi.kl
If you want to swap keys, simply switch the numbers (139 with 158), it's exactly the same as modifying the functions, but easier to type, especially on a phone.
It doesn't work for me. I added virtual at menu and back. Changed gravitybox back long press and double tap to kill foreground app. Single tap of back still not working.
Have i missed out anything? Oss 2.20 here.
J0kker said:
Yes you can, but the file isn't the same, you should edit:
system/usr/keylayout/synaptics-rmi.kl
If you want to swap keys, simply switch the numbers (139 with 158), it's exactly the same as modifying the functions, but easier to type, especially on a phone.
Click to expand...
Click to collapse
Thanks so much it worked.
Saved and rebooted the phone
Tiongkia said:
It doesn't work for me. I added virtual at menu and back. Changed gravitybox back long press and double tap to kill foreground app. Single tap of back still not working.
Have i missed out anything? Oss 2.20 here.
Click to expand...
Click to collapse
Strange, i'm on OSS 2.2.0-X and it's working perfectly.
Maybe try to activate Master switch under Navigation Bar tweaks in gravity box ?
I'm almost sure this won't help, but you need to write it all in uppercase letters.
J0kker said:
Strange, i'm on OSS 2.2.0-X and it's working perfectly.
Maybe try to activate Master switch under Navigation Bar tweaks in gravity box ?
I'm almost sure this won't help, but you need to write it all in uppercase letters.
Click to expand...
Click to collapse
Its already in caps. Don't work
Also try enabling master switch under navigation bar tweaks. Also don't work.
I just updated to 2.2.0-x too
Tiongkia said:
Its already in caps. Don't work
Also try enabling master switch under navigation bar tweaks. Also don't work.
I just updated to 2.2.0-x too
Click to expand...
Click to collapse
I can try to upload my generic.kl file if you want, just to see if it works for you as it does for me (this way we will know if it's this file related or not).
You should have menu-home-recents.
Rename the file (remove the .txt, i could not join a .kl file, invalid).
Maybe check the permissions too.
Envoyé de mon ONE E1003 en utilisant Tapatalk
J0kker said:
I can try to upload my generic.kl file if you want, just to see if it works for you as it does for me (this way we will know if it's this file related or not).
You should have menu-home-recents.
Rename the file (remove the .txt, i could not join a .kl file, invalid).
Maybe check the permissions too.
Envoyé de mon ONE E1003 en utilisant Tapatalk
Click to expand...
Click to collapse
I appreciate it buddy. But don't work
Tiongkia said:
I appreciate it buddy. But don't work
Click to expand...
Click to collapse
Sorry to ear that, if you ever manage to get it working, let us know (and why/how).
Tiongkia said:
I appreciate it buddy. But don't work
Click to expand...
Click to collapse
You should check if A you have a text editor that supports editing in system partition and B if you have root file explorer that supports writing in system partition (and permissions). I would recommend es file explorer, just for this particular task. Afterwards just delete the file explorer.
The easy way is to delete the file in keylayout and write the file (with es file explorer) from OP couple of posts ago in keylayout direction. Reboot and also enable masterswitch in gravitybox. Voila, this method can't go wrong and works always.
I have es explorer and root browser. I am able to change permission too. Also reboot but no effect.
Anyone else tried?
Tiongkia said:
I have es explorer and root browser. I am able to change permission too. Also reboot but no effect.
Anyone else tried?
Click to expand...
Click to collapse
I tried and it worked perfect. Can you look up what your generic file says under 139 and 158 ?
Tiongkia said:
I have es explorer and root browser. I am able to change permission too. Also reboot but no effect.
Anyone else tried?
Click to expand...
Click to collapse
Just wondering, do you have navbar enabled ?
If it is, try to disable it and reboot... i've never tried with navbar enabled, so who knows !
Tried all. Don't work. I give up. Thanks buddies. Appreciate it
Hi,
Applied without problem, just I can't set double tap action on the Home button.
I don't know why double tap doesn't work just for the home button. No problem with menu or back settings or on long press.
I think that Nova breaks this setup.
My conf :
OOS 2.2X, Xposed 80, Gravity Box 5.3.3, Nova lastest release
Edit : When I revert to the original file, the default setting (Settings > Buttons) Double tap for the Home buton is ignored.
Xiaomi Mi A3 Android 10
How to disable vibration on unlock:
1. Download SetEdit app from the playstore
2. Add a new setting 'haptic_feedback_intensity'
3. Set its SETTING VALUE to 0
4. Save changes
Request
I saved this setting and everything is ok. But when reset my phone after uninstall setedit this setting not work
imirsay said:
I saved this setting and everything is ok. But when reset my phone after uninstall setedit this setting not work
Click to expand...
Click to collapse
Use adb instead, and it won't revert back after restart.
Code:
adb shell settings put system haptic_feedback_intensity 0
Hi,
i used this setting, is it not strange that it still works after an hard reset?
Thanks for the tips but it's disabled whole vibration system such as I am not getting vibration when a call received or after the call ends. Is there any way we can only disable vibration while unlocking the phone.
Thanks in advance.
sumeddhh said:
Xiaomi Mi A3 Android 10
How to disable vibration on unlock:
1. Download SetEdit app from the playstore
2. Add a new setting 'haptic_feedback_intensity'
3. Set its SETTING VALUE to 0
4. Save changes
Click to expand...
Click to collapse
Thank you for this. It actually worked when all the other ways of trying to stop touch vibrations didn't work.
sumeddhh said:
Xiaomi Mi A3 Android 10
How to disable vibration on unlock:
1. Download SetEdit app from the playstore
2. Add a new setting 'haptic_feedback_intensity'
3. Set its SETTING VALUE to 0
4. Save changes
Click to expand...
Click to collapse
How can I turn off it on Oppo F21 Pro