Hello everyone,
I made this thread to address two common issues that some may encounter with the Kunais. Unless there is ever an external updater released by ASUS, the known way to fix the "Right Kunai getting stuck" when in Handheld mode is to either update to CN .63 or WW .64 (it is to be assumed that later revisions should also fix that). When you first boot any of these 2, you'll be greeted with a firmware update for your accessory once connected.
The update should be 1.3.9, that will fix the right side having "stuck buttons" or the "analog drift" that occurs while using the Left side analog. From my personal testing, I was able to rollback to an older firmware with the problem no longer occuring, as long as the accessory was updated to 1.3.9 firmware.
As for the M1 and M2 buttons located behind the Kunais, when using the central unit, they can be used as extra buttons. When used in handheld mode, the hardware values leave you with two buttons that, yes can be mapped, but do not natively act as Select nor Start. That can be a problem in games/programs such as Stadia, Moonlight, or anything that do not let you remap in the software itself.
This can be fixed but will require root access. Assuming that you do:
-open up Root Explorer (quick Google search for "Root Explorer apk" if you don't have it and install that)
-once in Root Explorer, go to the root folder and click on "Mount R/W" it should change to "Mount R/O"
-Go to folder /system/usr/keylayout/
-Hold click on file "Vendor_0b05_Product_4500.kl" and make a Copy in the same folder
-It should create a copy, rename it to "Vendor_0b05_Product_7900.kl"
-Click on file you just renamed and pick "Text Editor"
-Add another blank line under "key 318..."
-Type "key 264 BUTTON_START"
-Enter another blank line
-Type "key 265 BUTTON_SELECT''
-Click on 3 dots top right and choose "Save and Exit"
From there, you can disconnect AND reconnect your Gamepad and your M1 and M2 buttons should now behave as START and SELECT respectively as would any BT gamepad.
If for any reason, that does not work, it is possible the your Kunais revision bears a different Vendor and Product ID. In such case, I would recommend getting any free Gamepad Tester program from Play Store and when testing, most if not all, should give you the name, vendor ID and product ID of your hardware being tested. If these numbers are different than the values in this guide, simply swap the values of the .kl file and that should work.
Cheers!
Your method works to reassign m1 and m2 into start and select, but unfortunately it makes left and right triggers into some key representing (|) for both. If there is a way to fix this then your method would be great. I tested it in a gamepad tester.
Left and right trigger register as key 313 in the gamepad tester.
iBluesurge said:
Your method works to reassign m1 and m2 into start and select, but unfortunately it makes left and right triggers into some key representing (|) for both. If there is a way to fix this then your method would be great. I tested it in a gamepad tester.
Left and right trigger register as key 313 in the gamepad tester.
Click to expand...
Click to collapse
That 313 trigger seems to come from "Keyboard" if anything, I'd assume whichever game you ran tests with probably has AirTrigger or a Gamepad Mapping still functional because that Keyboard trigger for 313 would most likely be something mimicking the touchscreen OR some BT device. But for reference, that is what my .kl looks like.
# Asus Gamepad
key 304 BUTTON_A
key 305 BUTTON_B
key 307 BUTTON_X
key 308 BUTTON_Y
key 310 BUTTON_L1
key 311 BUTTON_R1
key 316 BUTTON_MODE
key 317 BUTTON_THUMBL
key 318 BUTTON_THUMBR
key 265 BUTTON_SELECT
key 264 BUTTON_START
key 158 BACK
key 172 HOME
axis 0x00 X
axis 0x01 Y
axis 0x02 Z
axis 0x05 RZ
axis 0x09 RTRIGGER
axis 0x0a LTRIGGER
axis 0x10 HAT_X
axis 0x11 HAT_Y
WhyKlwd said:
That 313 trigger seems to come from "Keyboard" if anything, I'd assume whichever game you ran tests with probably has AirTrigger or a Gamepad Mapping still functional because that Keyboard trigger for 313 would most likely be something mimicking the touchscreen OR some BT device. But for reference, that is what my .kl looks like.
# Asus Gamepad
key 304 BUTTON_A
key 305 BUTTON_B
key 307 BUTTON_X
key 308 BUTTON_Y
key 310 BUTTON_L1
key 311 BUTTON_R1
key 316 BUTTON_MODE
key 317 BUTTON_THUMBL
key 318 BUTTON_THUMBR
key 265 BUTTON_SELECT
key 264 BUTTON_START
key 158 BACK
key 172 HOME
axis 0x00 X
axis 0x01 Y
axis 0x02 Z
axis 0x05 RZ
axis 0x09 RTRIGGER
axis 0x0a LTRIGGER
axis 0x10 HAT_X
axis 0x11 HAT_Y
Click to expand...
Click to collapse
Would you be willing to show me that left and right trigger still function for you on a gamepad tester? Also I copy and pasted what you have shown and it still shows a keyboard key for left and right trigger in the gamepad tester.
Is it possible to change the right analog sensitivity using this method?
iBluesurge said:
Would you be willing to show me that left and right trigger still function for you on a gamepad tester? Also I copy and pasted what you have shown and it still shows a keyboard key for left and right trigger in the gamepad tester.
Click to expand...
Click to collapse
Uh....That's interesting, it wasn't registering as button 312 and yet, now it does... Both L2 and R2 does it. I'll have to dig deeper and see what causes that but yeah, it seems you are right, there must be a trigger of some kind.
UPDATE: You are absolutely right, it breaks the mapping. I'm working on fixing it, if not in the next hour, it'll be updated in the next 12hours.
Hello, I've tested the WW .64 firmware, and I can confirm that it really fix the issue with the right controller. But im also encountering right now an issue with the right analog. When i gently press the right analog to the left and let it go, it seems like the input doesn't properly go back to the center. I've already tested with the holder directly connected to the phone and it doesn't occur. Can you please also test if it is also happening to your controller? Thanks
@xenken: I might be too tired to read this properly but at least when trying to recreate your conflict, I haven't had any issues as you seem to encounter, but I'll try again tomorrow.
Alright, I will make edits for the guide tomorrow cause right now, I'm exhausted and my bed is calling me. That being said, here is an edited .kl which is, so far, the best compromise I found. All keys work and have values that they should, L2 and R2 can now be mapped independently in ASUS's software but SELECT (M2) does not map any longer.
I get the feeling that some HEX path overlap between keys and is what causes the conflict, I tried many alternatives to no avail.
# Copyright (C) 2014 The Android Open Source Project
#
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
# Asus Gamepad
key 264 BUTTON_START
key 265 BUTTON_SELECT
key 304 BUTTON_A
key 305 BUTTON_B
key 307 BUTTON_X
key 308 BUTTON_Y
key 310 BUTTON_L1
key 311 BUTTON_R1
key 312 BUTTON_L2
key 313 BUTTON_R2
key 316 BUTTON_MODE
key 317 BUTTON_THUMBL
key 318 BUTTON_THUMBR
key 158 BACK
key 172 HOME
axis 0x00 X
axis 0x01 Y
axis 0x02 Z
axis 0x05 RZ
axis 0x09 RTRIGGER
axis 0x0a LTRIGGER
axis 0x10 HAT_X
axis 0x11 HAT_Y
Click to expand...
Click to collapse
THREAD CLOSED because a thread regarding this subject already exists:
https://forum.xda-developers.com/rog-phone-2/accessories/figuring-whats-wrong-kunai-t4015171
The posts from this thread have been copied to there.
XDA Forum Rules (excerpt):
...
5. Create a thread topic or post a message only once, this includes external links & streaming media.
As a large forum, we don't need unnecessary clutter. You're free to edit your message as you like, so if you do not receive an answer, revisit your message and see if you can describe your problem better. Not everyone is online at the same time so it might take a while before you receive an answer.
You can bump your unanswered question once every 24 hours
Duplicate threads and posts will be removed
Always post in an existing thread if a topic already exists, before creating a new thread.
Use our search function to find the best forum for your device.
Links to an external source are only allowed if relevant to the topic in hand. A description must be included, no copy & pasting from the original source.
Self-promotion is forbidden, this includes blogs, social media and video channels etc. Random links will be removed.
...
Click to expand...
Click to collapse
Related
Since MiniSquadron! needs MT, D-pad or trackball normally, makes it almost impossible to play it on X10i without ripping out your hair and crack your head on the wall(in some serious case )
Because it is a great game, I googled for a solution, and found this:
You have to make sure that you have ROOT.
Edit your es209ra_keypad.kl located in /system/usr/keylayout/ with your preferred method(I made it with vi).
When you open it, something similiar will greet you:
Code:
# Copyright (c) 2009, Code Aurora Forum.
# Copyright (C) 2010 Sony Ericsson Mobile Communications AB.
#
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
#
# NOTE: This file has been modified by Sony Ericsson Mobile Communications AB.
# Modifications are licensed under the License.
key 158 BACK
key 107 ENDCALL WAKE_DROPPED
key 62 ENDCALL WAKE_DROPPED
key 229 MENU
key 59 MENU
key 231 CALL WAKE_DROPPED
key 61 CALL WAKE_DROPPED
key 102 HOME WAKE_DROPPED
key 115 VOLUME_UP WAKE_DROPPED
key 114 VOLUME_DOWN WAKE_DROPPED
key 116 POWER WAKE
key 212 CAMERA
key 213 MENU
key 215 FOCUS
key 226 HEADSETHOOK
Our mission is to modify the line "key 215 FOCUS" to "key 215 DPAD_CENTER WAKE_DROPPED".
Now you have to replace the original file then reboot.
Pros: You can play MiniSquadron! Yaaay =]
Cons: As you modify the function of FOCUS to DPAD_CENTER, you can't take photos like focus-wait-capture, but focus-capture. Don't like it? Don't do it!
EDIT: Any good idea, what else we can do with FOCUS would be nice
IMPORTANT: AS YOU CAN SEE IN THE HEADER OF THIS FILE, IT IS UNDER LICENCE, SO MODDING IT CAN VOID WARRANTY. AND I AM NOT RESPONSIBLE FOR ANY DAMAGE WHAT ONE MADE WITH CONFIGURING BAD ADDRESSES IN ONE'S PHONE.
Before you bring it to a service for some reason, it's recommended to wipe your phone(updatr via SEUS or PCC)
Thank you for your understanding
Regards, Adolf1994
Adolf1994 said:
Since MiniSquadron! needs MT, D-pad or trackball normally, makes it almost impossible to play it on X10i without ripping out your hair and crack your head on the wall(in some serious case )
Because it is a great game, I googled for a solution, and found this:
You have to make sure that you have ROOT.
Edit your es209ra_keypad.kl located in /system/usr/keylayout/ with your preferred method(I made it with vi).
When you open it, something similiar will greet you:
Code:
# Copyright (c) 2009, Code Aurora Forum.
# Copyright (C) 2010 Sony Ericsson Mobile Communications AB.
#
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
#
# NOTE: This file has been modified by Sony Ericsson Mobile Communications AB.
# Modifications are licensed under the License.
key 158 BACK
key 107 ENDCALL WAKE_DROPPED
key 62 ENDCALL WAKE_DROPPED
key 229 MENU
key 59 MENU
key 231 CALL WAKE_DROPPED
key 61 CALL WAKE_DROPPED
key 102 HOME WAKE_DROPPED
key 115 VOLUME_UP WAKE_DROPPED
key 114 VOLUME_DOWN WAKE_DROPPED
key 116 POWER WAKE
key 212 CAMERA
key 213 MENU
key 215 FOCUS
key 226 HEADSETHOOK
Our mission is to modify the line "key 215 FOCUS" to "key 215 DPAD_CENTER WAKE_DROPPED".
Now you have to replace the original file then reboot.
Pros: You can play MiniSquadron! Yaaay =]
Cons: As you modify the function of FOCUS to DPAD_CENTER, you can't take photos like focus-wait-capture, but focus-capture. Don't like it? Don't do it!
EDIT: Any good idea, what else we can do with FOCUS would be nice
Regards, Adolf1994
Click to expand...
Click to collapse
Hoooo Yeaaaaah! Finally we can! Mini squadron is... hard :/ and so cool!
Sent from my X10i using XDA App
I'm not sure how to repeat this trick consistently, but it seems if you press the shoot touch-screen key and the movement touch-screen d-pad at around the same time, I can get auto continuous shooting. Once you get it, you can just control using the D-pad touch-screen key while it auto-shoots.
I can't always get this mode right away, but I give it a minute or two and I can usually get it right such that the shoot touch-screen key is somehow stuck in shooting mode.
I'm not sure how this hack works, but it seems you're remapping the keys to the game and as a side-effect it also affects the rest of the functions of the phone for that key. I probably wouldn't go that far just to play a game, but that's just me.
@pally777, because the X10i yet not capable of MT, but has a button which is not needed for me(I'm ok with that focus-shot), one can associate almost every button, e.g. I can replace it with 'Q', just becaise I love that letter
What you are trying to say is to mess with the game till it somehow stuck on auto-shot, what isn't... practical :/
@Koutch974, I'm glad, you are glad
Is there Any way to associate fire button to the photo button? it will bebe very cool.
Regards.
Sent from my X10i using XDA App
Koutch974 said:
Is there Any way to associate fire button to the photo button? it will bebe very cool.
Regards.
Sent from my X10i using XDA App
Click to expand...
Click to collapse
Doing this would affect your system more, and even your photo button. My choice of FOCUS is because it isn't important to take photos(I mean the button, not the function ), and it's easy to press
Its possible, but not recommended.
If you want to do this, then replace
Code:
key 212 CAMERA
with
key 212 DPAD_CENTER WAKE_DROPPED
This isn't confirmed to work, cuz I don't want to try this
Saw a new version v1.13. Changelog says the Camera button now alternate to fire...
Updating from market atm
EDIT: Nope, it doesn't work
any new idea? ver.1.14 said the camera button act be as the firebutton, but it doesnt work
In the newes version of this game, i downloaded by AppPlanet ... camera button can use to fire !! You can try it !! Xperia X10 . 2.1
Yeah, I can confirm that the camera button works from 1.15. Now no need for my method
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
I have a joystick with 6 axes an 2 buttons. If I connect that joystick to my device (nexus 7) through an otg cable it gets recognized as HID device.
The two buttons are both mapped by android to ENTER and the X + Y axes to direction keys.
So it is already possible to control some UI sections (ie app icon selection on launcher).
I added a key layout map in "/system/usr/keylayout/Vendor_046d_Product_c626.kl" to customize the two buttons.
I was also able to remap and invert all 6 axes.
Code:
# left / right
axis 0x00 RX
# forth / back
axis 0x01 RY
# up / down
axis 0x02 RZ
# roll forth / back
axis 0x03 Y
# roll left / right
axis 0x04 X
# turn left / right
axis 0x05 Z
# left button
key 256 VOLUME_DOWN
# right button
key 257 VOLUME_UP
As you can see I mapped the two buttons to the volume controls, which works fine.
Unfortunately I'm not able to figure out how to map axes to keystrokes.
As the X + Y axes are mapped to direction keys, there must be a setting somewhere for this.
I would like to use all 6 axes and map them to simple keystrokes.
Can sombody help?
Hello g-e-c-o.
I know this thread is a lil bit older but I'm getting faced with the same problem soon. Did you find any solution for mapping the axes?
Try this
key 105 DPAD_LEFT
key 106 DPAD_RIGHT
key 108 DPAD_DOWN
key 103 DPAD_UP
key 256 BUTTON_1
key 257 BACK
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.