Hi,
I cannot figure out how to disable the "backward functionality" of the fingerprint sensor.
A swipe over this device brings the M5 back to the home screen.
This is very annoying while playing a game.
I already switched the method of input in the settings to use Android's softkeys at the bottom but the "backward functionality" works as before.
I also tried to use a different launcher.
-> Didn't help
Does anybody have a clue?
Cheers,
Janny
yes very painful...can't find anywhere to disable...i keep hitting it accidentally.
Rotate your device the other way around so that the fingerprint reader is either on top of on the left side. It might help
Yes I would like time a way to disable it completely as well, it's pretty annoying right now.
Xposed Edge Pro has been used to remap the fingerprint sensor on other Huawei devices. But it requires Xposed.
Hi, same problem... ?
hi all!
I have the same problem, obviously, and till someone finds the way to disable the infamous button (that I don't use at all), I found a very simple trick...
I used a small piece of paper tape to cover the button...
ugly but it really works...
no more accidental touches and jumps to the home page while playing!
Pierluigi
If you have root access, just edit or remove the relevant key mappings /vendor/usr/keylayout/fingerprint.kl to your liking.
I edited mine so that a tap = home, swipe up = recents, swipe down = back
^^ can I ask if you could share the changes you made to fingerprint.kl? I have struggled to make good sense of it and am reluctant to experiment blindly. I'd ideally like mine to do nothing on tap or longpress, go back on double click, screenshot on triple click, and pull up Recents on swipe.
Do I set 'doubleclick' to key 174 and delete entries for click and longpress? I still want to be able to use it to wake the screen.
Stock file:
#
# Touch sensor driver
#
# Copyright (c) 2013,2014 Fingerprint Cards AB <[email protected]>
#
# This program is free software; you can redistribute it and/or
# modify it under the terms of the GNU General Public License Version 2
# as published by the Free Software Foundation.
#
# "click"
key 28 ENTER
# "finger wakeup"
key 113 KEYCODE_FINGERPRINT_FINGER_UP
key 111 KEYCODE_FINGERPRINT_DOUBLECLICK
key 105 KEYCODE_FINGERPRINT_LEFT
key 106 KEYCODE_FINGERPRINT_RIGHT
key 108 KEYCODE_FINGERPRINT_DOWN
key 103 KEYCODE_FINGERPRINT_UP
key 174 KEYCODE_FINGERPRINT_CLICK
key 117 KEYCODE_FINGERPRINT_FINGER_DOWN
key 118 KEYCODE_FINGERPRINT_FINGER_IDENTIFY
key 119 KEYCODE_FINGERPRINT_IDENTIFY_END
key 120 KEYCODE_FINGERPRINT_FINGER_ENROLL
Sure, here's mine.
Code:
key 28 HOME
key 105 BACK
key 106 APP_SWITCH
key 174 VOICE_ASSIST
28 = tap button
105 = swipe down
106 = swipe up
174 = tap and hold
Just delete the entries you don't want, or comment them out with a # then reboot
Didn't really work for me on the stock rom, with off-screen navigation enabled. I tried 'key 105 BACK, key 106 APP_SWITCH.' Upon reboot, it did nothing on tap or swipe, but still returned me home on longpress.
Got the same issue on both my 8.4 and pro really really annoying.
Op, why not use huawei game app?
It will disable tap to back function which it's helpful during gaming.
But it's still possible to go home screen when long press fingerprint.
This is very annoying
Try this:
Download and install Game suite from APKMirror:
https://www.apkmirror.com/apk/huawei/game-suite/game-suite-8-0-1-101-release/game-suite-8-0-1-101-android-apk-download/
Open Game suite and add your game or application.
Enable Gaming mode.
Enable Mistouch prevention.
That's it, works for me!
Since I don't really care about using this button for anything other than the fingerprint unlock, I rooted and modified the /vendor/usr/keylayout/fingerprint.kl and added a # sign to every line. The button is ultimately disabled when you are using the device.
I'll just have to repeat the process with each firmware update, but since Huawei is so slow at updating, this isn't an issue.
Lee82UK said:
Sure, here's mine.
Code:
key 28 HOME
key 105 BACK
key 106 APP_SWITCH
key 174 VOICE_ASSIST
28 = tap button
105 = swipe down
106 = swipe up
174 = tap and hold
Just delete the entries you don't want, or comment them out with a # then reboot
Click to expand...
Click to collapse
Are you on Stock Rom? I didn't find these in my 8.1 Stock build. Can you please share your file.
Related
So, there's the problem with the X2 having the volume buttons not work when it's locked. I just got one a couple days ago, and decided to poke around to see if I could get it going. I messed with my old Nexus One and reassigned the Search button to the camera, so I started with the keylayout directory. Well, after some experimenting, I got it going. While you have to press the button for each incremental change in volume, it beats having to turn the device on.
Note: I can't post links due to a low post count. So my lack of helpful links is the forums' fault, not mine. My apologies.
What you'll need before you begin;
1) Root access. The X2 can be rooted with Gingerbreak.
2) A file manager. I use Root Explorer.
2b) If you're manually applying the changes, and you're using a file manager without one built-in, you'll need a text editor. Root Explorer has one, so...figure it out.
The Long Method
=Step One=
Navigate to "/system/usr/keylayout". The file we're working with is "tegra-kbc.kl"
=Step Two=
Mount the file system as read/write, make a backup of tegra-kbc.kl(I'm partial to adding a .ori to the end, but that's me), and open tegra-kbc.kl in a text editor.
=Step Three=
Lines six and seven, right below Camera, are the volume buttons we're looking for. We're going to append "WAKE" at the end of the line, to tell the phone to listen when they're pressed. Mine looks like this;
key 115 VOLUME_UP WAKE
key 114 VOLUME_DOWN WAKE
Obviously, it's not too picky about spacing. So the sky and your anal-retentiveness is the limit.
=Step Four=
Save the file, set correct permissions if they got mangled somehow(rw-r--r--, for reference), and restart.
The Short Method
=Step One=
Download the needed file. Take any public dropbox file link, and replace the end with "/u/3487229/Android/tegra-kbc.kl"
Look, I'd just give the link, but low post count and all. My apologies.
=Step Two=
Make a backup of, then copy the file over /system/usr/keylayout/tegra-kbc.kl
=Step Three=
Reset any mangled permissions(rw-r--r--, for reference), and restart.
Awesome.
10char
Worked a champ. Was trying to figure out how to do this last night.
Could someone paste the tegra file. I think I may have deleted it while attempting to make a backup. Many Thanks!
Sent from my Xoom using XDA App
Just tried this and did not work. Looking at file now, says WAKE after each, restarted and still doesn't work.
This may sound dumb, but I don't think this method "fixed" anything. I accidentally deleted the tegra-kbl.kl file but my volume can be adjusted while locked. The trick is to press volume multiple times rather than holding to adjust. FYI I never got a chance to adjust the file per the OP. Lemme know if this works for anyone else.
ALSO I STILL WOULD REALLY APPRECIATE SOMEONE POSTING THE TEGRA-KBL.KL FILE. THANK!
Sent from my DROID X2 using XDA App
Elite49 said:
Just tried this and did not work. Looking at file now, says WAKE after each, restarted and still doesn't work.
Click to expand...
Click to collapse
Does it match the above, where there's at least one space between WAKE and the word preceding it? Also, are the permissions correct?
cmanatam said:
This may sound dumb, but I don't think this method "fixed" anything. I accidentally deleted the tegra-kbl.kl file but my volume can be adjusted while locked. The trick is to press volume multiple times rather than holding to adjust. FYI I never got a chance to adjust the file per the OP. Lemme know if this works for anyone else.
ALSO I STILL WOULD REALLY APPRECIATE SOMEONE POSTING THE TEGRA-KBL.KL FILE. THANK!
Click to expand...
Click to collapse
That's how this works when implemented; you can't just hold down volume, but each click changes the volume by one increment.
I'm not sure how you got to where you are; when I accidently deleted the keylayout file on my Nexus One, none of the physical buttons worked, except the power button to power it on.
That was a fun one to recover from.
While I see someone else posted the entire original file in another thread, let me post what mine looks like, for comparison.
Modified tegra-kbc.kl, with volume fix and Search reassigned to Camera;
Code:
key 102 HOME WAKE
key 139 MENU WAKE_DROPPED
key 158 BACK WAKE_DROPPED
key 212 FOCUS
key 211 CAMERA
key 115 VOLUME_UP WAKE
key 114 VOLUME_DOWN WAKE
key 217 SEARCH WAKE_DROPPED
key 28 ENTER
key 103 DPAD_UP WAKE_DROPPED
key 108 DPAD_DOWN WAKE_DROPPED
key 105 DPAD_LEFT WAKE_DROPPED
key 106 DPAD_RIGHT WAKE_DROPPED
key 232 DPAD_CENTER WAKE_DROPPED
#
# IKXETNA-128 Verizon UTS tool support
#
key 2 1 WAKE_DROPPED
key 3 2 WAKE_DROPPED
key 4 3 WAKE_DROPPED
key 5 4 WAKE_DROPPED
key 6 5 WAKE_DROPPED
key 7 6 WAKE_DROPPED
key 8 7 WAKE_DROPPED
key 9 8 WAKE_DROPPED
key 10 9 WAKE_DROPPED
key 11 0 WAKE_DROPPED
key 56 ALT_LEFT WAKE_DROPPED
key 42 SHIFT_LEFT WAKE_DROPPED
key 62 ENDCALL WAKE_DROPPED
key 61 CALL WAKE_DROPPED
key 228 POUND WAKE_DROPPED
key 227 STAR WAKE_DROPPED
key 231 CALL WAKE_DROPPED
key 162 POWER WAKE
key 14 DEL
key 57 SPACE
key 52 PERIOD
key 51 COMMA
key 16 Q
key 17 W
key 18 E
key 19 R
key 20 T
key 21 Y
key 22 U
key 23 I
key 24 O
key 25 P
key 30 A
key 31 S
key 32 D
key 33 F
key 34 G
key 35 H
key 36 J
key 37 K
key 38 L
key 44 Z
key 45 X
key 46 C
key 47 V
key 48 B
key 49 N
key 50 M
Mine looks just like that, still doesn't work.
@Elite49;
Here's what I'd do, on your device. I know we might be treading old ground, but just to rule anything out, try this;
1) Download the attached file. Lop off the file extension so it's just "tegra-kbc.kl"
2) Copy it, and head over to /system/usr/keylayout. Take the existing "tegra-kbc.kl" and put on a file extension that renders it inoperable(I like .ori, but that's just me).
3) Paste the downloaded "tegra-kbc.kl" into the keylayout folder.
4) Check permissions and ownership. Ownership needs to be root on both group and user, and permissions should be rw-r--r--.
5) Power-cycle.
6) Try it out. The quickest way, with that file, is to hold down the search key. If it's using that key layout file, after a few moments your camera app should come up. If it does, then your volume buttons should also be usable when your device is locked.
If you don't want camera on your search key, here's how you change it back. I only suggest doing this after you've verified your device is using this key layout file. If you do it before, then we're back to square one because we're only testing the volume buttons. This's changing two functions, making it easier to see whether it's a hardware or software issue.
1) Open /system/usr/keylayout/tegra-kbc.kl
2) Find CAMERA. Change the key from 211 to 217.
3) Find SEARCH. Change the key from 217 to 211.
4) Save file, check ownership and permissions, reboot. Ta-da.
Thanks!
This marks a huge negative off of my list! I think I will keep it now.
-JJ
Hello!
My problem is, that i have bought a new car holder for my x10.
Now i have the problem, when i slip in my phone, the hardwarebutton for the camera is permanently pushed.
Does anyone have an applikation, which switches of the hardwarebutton?
Many thanks,
Greetings
- Install ButtonRemapper (root needed)
- open it, click on "focus" in the list and then pick "dpad center" / "none"
if it presses enough to trigger the camera and not just the focus, do the same for camera in the list.
- in ButtonRemapper settings, uncheck "boot monitor" and check "hot reboot".
- click Apply, your phone will reboot after a few seconds.
zorglub08 said:
- Install ButtonRemapper (root needed)
- open it, click on "focus" in the list and then pick "dpad center" / "none"
if it presses enough to trigger the camera and not just the focus, do the same for camera in the list.
- in ButtonRemapper settings, uncheck "boot monitor" and check "hot reboot".
- click Apply, your phone will reboot after a few seconds.
Click to expand...
Click to collapse
Thank you a lot, zorglub08!!
It works perfectly.
By the way, what activates the dpad center?
The d pad center doesn't activate anything in the home, that's why I picked it, in practice in just just disables the button. If you launched an emulator or some app that supports a hardware directional pad, it may do "Enter"/"OK". I didn't try though, on my phone, I didn't find and app that used it.
I was going to PM this to you, but since you made another thread i'll post it here.
To properly disable the camera button, you must edit the es209ra_keypad.kl file. This file controls how the Android OS responds to the hardware buttons.
Use Root Explorer (or any other root file manager app) and navagate to /system/usr/keylayout/ and open the es209ra_keypad.kl file for editing. I am doing this on 2.3.3, so the file may be different depending on your ROM. Either way, it is easy to tell which lines need editing.
Once you have the file open, place a hash (#) in front of the "CAMERA" and "FOCUS" lines as follows:
Code:
key 115 VOLUME_UP WAKE
key 114 VOLUME_DOWN WAKE
key 229 MENU
key 59 MENU
key 213 MENU
key 102 HOME WAKE_DROPPED
key 158 BACK
key 107 ENDCALL WAKE_DROPPED
key 62 ENDCALL WAKE_DROPPED
key 231 CALL WAKE_DROPPED
key 61 CALL WAKE_DROPPED
key 116 POWER WAKE
#key 212 CAMERA
#key 215 FOCUS
key 226 HEADSETHOOK
Once you have edited the file, reboot your phone.
This effectivly stops Android from even seeing that the camera button exists, hence, the camera button will do absolutly nothing to the phone. If you change ROMs, you will have to do this again.
Cheers to Pierre Duc who created the thread about stopping the home button from waking the phone, otherwise I wouldn't even know that this file exists.
http://forum.xda-developers.com/showthread.php?t=1117810
Disclaimer: Do at your own risk, I am not responsible if anything goes wrong (which it shouldn't).
- Frosty
My dad's Droid X2 was having issues so he got a new phone (Note II, the lucky bastard >_>) and gave me his old phone. Messing with it a little before I activate it on Verizon, I realized that the only thing wrong with it was the back button - its worn out and keeps clicking itself over and over again. To do anything with the phone I need to mash the back button for 15+ seconds while the screen is off/on the home screen.
I haven't done anything with the phone yet, its still bone stock, fully updated, not even rooted yet. In its current state its nearly unusable as a daily driver, but I figure if I can flash ICS/JB, activate the onscreen keys, an fully disable the hard keys, it'll be good to go - a decent replacement to my Droid charge (which I love to pieces but is so lageriffic its getting hard to use)
My problem is, none of the roms say anything about this. My experience with cyanogenmod/AOKP is limited to a few unofficial alpha roms for my tablet, so I really don't know. I found this, which I think might work for what I want , but I don't know if its compatible with the Droid X2, especially with the rom I was really looking into, paranoidandroid. Though I will honestly accept any 4.0+ rom. This will be my daily driver, if I can get it to work, so I do care about stability. Just not sure where to start or how to go about this. I'd like to consider myself a fairly advanced ROMer, so if it gets technical, I don't mind in the slightest.
Thank you guys for any help you can provide me.
mtmerrick said:
My dad's Droid X2 was having issues so he got a new phone (Note II, the lucky bastard >_>) and gave me his old phone. Messing with it a little before I activate it on Verizon, I realized that the only thing wrong with it was the back button - its worn out and keeps clicking itself over and over again. To do anything with the phone I need to mash the back button for 15+ seconds while the screen is off/on the home screen.
I haven't done anything with the phone yet, its still bone stock, fully updated, not even rooted yet. In its current state its nearly unusable as a daily driver, but I figure if I can flash ICS/JB, activate the onscreen keys, an fully disable the hard keys, it'll be good to go - a decent replacement to my Droid charge (which I love to pieces but is so lageriffic its getting hard to use)
My problem is, none of the roms say anything about this. My experience with cyanogenmod/AOKP is limited to a few unofficial alpha roms for my tablet, so I really don't know. I found this, which I think might work for what I want , but I don't know if its compatible with the Droid X2, especially with the rom I was really looking into, paranoidandroid. Though I will honestly accept any 4.0+ rom. This will be my daily driver, if I can get it to work, so I do care about stability. Just not sure where to start or how to go about this. I'd like to consider myself a fairly advanced ROMer, so if it gets technical, I don't mind in the slightest.
Thank you guys for any help you can provide me.
Click to expand...
Click to collapse
there are apps on the market that allow button remaping but if you wanna try something like cyanogen or miui on the dx2 try this Soft key mod for CM/Miui it has a flash able zip for disabling and reenabling the hardware buttons and the same for the software buttons works like a charm for me but im never on one rom long enough to really enjoy it.
Check out an app in the Play Store called "Button Savior".
Sent from my Android device using Tapatalk
OK, so the hardkey issue seems to have mysteriously alleviated itself..
guess i'm just looking for the most stable 4.0+ ROM now.
I had an X2 with a failed back key also. In order to make the phone bearable while waiting for the replacement to arrive, I edited the keyboard file and changed the "search" button to the "back" button. You'll need to be rooted to do this. From a file explorer app (I use Astro or AntTek Explorer), browse to \system\usr\keylayout and open the tegra-kbc.kl file with a text editor from within the phone. I used File Editor, which I think is stock within the phone. When open, you'll see a whole list of keys, but you'll only need to concern yourself with 158 and 217.
Here's a section of the file so you know what I'm talking about.
key 102 HOME WAKE
key 139 MENU WAKE_DROPPED
key 158 BACK WAKE_DROPPED
key 212 FOCUS
key 211 CAMERA
key 115 VOLUME_UP
key 114 VOLUME_DOWN
key 217 SEARCH WAKE_DROPPED
key 28 ENTER
Click to expand...
Click to collapse
You'll want to make changes to the lines I've bolded so they look like this:
key 102 HOME WAKE
key 139 MENU WAKE_DROPPED
key 158 BACK WAKE_DROPPED
key 217 BACK WAKE_DROPPED
key 212 FOCUS
key 211 CAMERA
key 115 VOLUME_UP
key 114 VOLUME_DOWN
# key 217 SEARCH WAKE_DROPPED
key 28 ENTER
Click to expand...
Click to collapse
So now, both the "back" button and the "search" button will do the same thing.
You can always disable the original "back" button altogether by putting a # in front of the 158 line like this:
key 102 HOME WAKE
key 139 MENU WAKE_DROPPED
# key 158 BACK WAKE_DROPPED
key 217 BACK WAKE_DROPPED
key 212 FOCUS
key 211 CAMERA
key 115 VOLUME_UP
key 114 VOLUME_DOWN
# key 217 SEARCH WAKE_DROPPED
key 28 ENTER
Click to expand...
Click to collapse
After making the changes, save and close the file, then reboot your phone.
Let me know if you have any questions.
This is perfect, thank you so much.
I found the soft keys and installed that, so I'd be plenty happy disabling all 4 hard keys at the bottom. What would be the proper way to go about doing that, using this method?
If you wanted to disable the buttons, you'd simply place a # in front if the line you don't want read by the software. You better make sure the soft key app is rock solid though.
Change it from this:
key 102 HOME WAKE
key 139 MENU WAKE_DROPPED
key 158 BACK WAKE_DROPPED
key 212 FOCUS
key 211 CAMERA
key 115 VOLUME_UP
key 114 VOLUME_DOWN
key 217 SEARCH WAKE_DROPPED
key 28 ENTER
Click to expand...
Click to collapse
to this:
# key 102 HOME WAKE
# key 139 MENU WAKE_DROPPED
# key 158 BACK WAKE_DROPPED
key 212 FOCUS
key 211 CAMERA
key 115 VOLUME_UP
key 114 VOLUME_DOWN
# key 217 SEARCH WAKE_DROPPED
key 28 ENTER
Click to expand...
Click to collapse
You can also use Bootstrap Recovery to check what each key is. Select Advanced --> Key Test. To get out of the key test, press Power, Volume UP, and Volume DN at the same time, and the phone will reboot.
---------- Post added at 07:46 AM ---------- Previous post was at 07:20 AM ----------
I told you the wrong file name. You'll want to edit the tegra-kbc.kl file located in the same directory. I'm sorry about that.
OK, thank you! I'll let you know how it goes.
And they're the OS soft keys from jellybean, so nothing to worry about.
----------
OK, disabled them! Thanks!
I'm considering assigning the search key to the camera shutter. However, if I do this, I don't want it to launch the camera app, just to take a picture if the camera is open. Is there a way to do this?
I have found many examples of modding the the key file in System\Usr\Keylayout to remove the wake option from key 102, but in eclipse 2.3, there are 6 .kl and 4 of them have key 102 mapped to wake in them. I am unsure if I need to remove wake from key 102 in all or some of them.
Len
Lenster45 said:
I have found many examples of modding the the key file in System\Usr\Keylayout to remove the wake option from key 102, but in eclipse 2.3, there are 6 .kl and 4 of them have key 102 mapped to wake in them. I am unsure if I need to remove wake from key 102 in all or some of them.
Len
Click to expand...
Click to collapse
OK after trial and error, removing the word WAKE after the 102 key entry in System/USR/Keylayout/Tegra_kbc.kl file prevents the home button from waking the phone. So now it a lot harder to accidentally turn on the the screen while its in my pocket.
Len
Looking to remap my home key, and my menu and back soft keys on my s3. I've looked at editing scripts, and even Xposed modules for this and here is what I found.
I can remap my keys manually, but I cannot map them to open an application.
With Gravity Box Module, I can map the applications to launch on a double press or a long press.
Here is what I want to do with a single tap.
[MENU SOFT KEY] [HOME KEY] [BACK SOFT KEY]
Open Phone Open search Open Camera
Is there an xposed module for this?
Bump.
vbetts said:
Bump.
Click to expand...
Click to collapse
Not sure there is a module for it..but all button controls are in android.policy.jar.. it would take a heavy re working to get all those things.. not saying it's not possible but..yea..not easy
Sent from my SCH-I605 using xda app-developers app
I've reset them in the touchkeys.kl file under keychars, but I cannot get CAMERA to map on the back button. I can get other actions too, but CAMERA Won't map. Here's my thread in the 747 section.
http://forum.xda-developers.com/showthread.php?t=2705040
I'm doing a few tweaks on my phone, mainly not using the capacitive keys as menu and back, and using the home key as the app switcher, and using the nav bar for those three tasks. Here's what I've got so far.
I edited a few files under system/usr/keylayout
The Menu and Search key layouts were found under sec_touchkey.kl(Home was also found under this, but I had to also edit sec_keys.kl and sec_key.kl to get the home key as the app switcher)
Here's the default settings.
key 139 MENU VIRTUAL
key 158 BACK VIRTUAL
key 102 HOME
key 217 SEARCH
Here's what I set them to.
key 139 CALL VIRTUAL
key 158 CAMERA VIRTUAL
key 102 APP_SWITCH
key 217 SEARCH
Changing the roles of keys 139 and 102 worked, but Camera does not open the camera. I've tried assigning different roles to key 158 and they've worked except for the camera role. So I'm thinking CAMERA is not the correct event name to open the camera up....
http://developer.android.com/referen...KEYCODE_CAMERA
That's where I got the keyEvent listings from.
Rom is in my signature.
Click to expand...
Click to collapse