IssueTracker

yes the compatibility is a must have.

must have.

Must have

woah thanks for the fix! this is very helpful

must have+1

Awesome! how do i install it though?

Right how to install?

You need root to install it at the moment.
1. Download the file from the first post
2. Copy the file to /system/usr/keylayout
3. set the permisions of the file to 644

And make sure the controller's firmware is updated.

This is awesome! TY!
Now I just wish that someone would add support for the Gamecube WII USB Adapter. That would be amazing!  Any chance you could look into it? I guess it's working on Linux... so if you're techy, you should be able to convert it over pretty easily.

Thanks for this, works great!

Works great but have to reroot and reinstall the keymap after each android update... Please include this keymap for next version of Android / Android TV. Thanks.

It seems like someone made a patch that needs to be approved first.
https://android-review.googlesource.com/#/c/284883/

[Comment deleted]

This worked on my Shield K1 Tablet great. Thanks!

Any chance we can get a keylayout for the 02e6 (Xbox Wireless Adapter)? I can't seem to find it anywhere.

With the latest controller update from MS these controllers work with stock setup. If you don't have an Xbox one, you need to download the xbox accessories app from the windows 10 store to update the firmware on the controller.

Anyone else having issue with the controllers not working after the system reboots? I find myself constantly having to repair the controllers to make them work.

A forum on NeoGAF found this issue is caused by steam. The controller would stop working after it goes to sleep the first time after computer reboot. I was able to get the controller working again by restarting steam.

I can't pair mine with my Xperia Z5 (says wrong pin number) does anyone have the same problem ?

[Comment deleted]

God Sent!

Edit: Just updated the Xbox One (Bluetooth) controller's firmware today (Jan 4th 2017) and now the mapping of the buttons are all messed up again... ARGH!!

Do we need a new keylayout file or is there a way to reconfigure the file in the OP?

It seems like Microsoft changed the layout with the new update. I will look into it in the next few days.

Thank you so much! I also noticed that the update changed my remote Device ID from 02e0 to 02ea. By renaming your file to match the new Device ID made it a lot better however I noticed it's no longer optimized. It works most of the time but periodically something will trigger one of the buttons out of the blue. For example in Order and Chaos, when you run with the left joystick for like 5 seconds, all of a sudden character menu opens, or midway through combat your inventory pops up.
Same thing happens in Space Marshal 2 and Fallout 4 (Stream via Moonlight)

Looking forward to you working your magic :)

Talking about Device ID... My XBox One S bluetooth controller's ID (before last update) seems to be 02fd, and not 02e0. Am I the only one?

it seems the key mapping is no more needed,
Microsoft fixed the mapping with a internal firmware update.
if you added the key mapping you have to remove it.
but now the new bug is
on some device when pairing it ask a password.
but it affect only some devices.

I have the same 02fd ID and I didn't got a Jan 4th update, I updated it on Dec, 31 with the firmware 3.1.1221.0. The Xbox Accesories app doesn't show a new update from the one I currently have. I didn't rooted my device (yet), in order to put the Vendor_045e_Product_02e0.kl mapping, but this would definitely not do anything since I have 02fd product and not 02e0. Also the controller connected to a Fire Tablet, without any custom mappings, has the controls mapped wrong.

I suggest we reference all data in a sheet. I started.

https://docs.google.com/spreadsheets/d/1BXAxNLbt9N344yd1EPZWGzkXboSD65B-4Zri703t-vY/edit?usp=sharing

Andi,
Rename the custom file in the original post to match your device id and it'll work.
Or alternatively try to update your controller via someone else Xbox or PC and see if that works.

Tails,
It appears that deleting custom key layouts fix most of the issue so far.  Hopefully it stays that way with future updates as well

I'm on latest pad firmware (December one, previous versions paired more or less succesfully) and on CM13, this pad now doesn't pair at all, saying "wrong PIN". Is there a possibility to edit this PIN in config files? Also I checked this on I9300 (Galaxy S3) with CM14 (Resurrection Remix, early December version) - the same error.

Max, try this:
Find out what your remote's Device ID is (google this. Can be done on PC by going to driver's properties)
Then rename the file above to match your device ID. That should bypass the PIN bug and connect but your key mapping will be all weird. Then once you "Smart Connect and save it as trusted device" then delete the key layout file mentioned earlier. Now your device should connect to the remote without asking for PIN.
I'm not sure if this workaround works everytime or not.

[Comment deleted]

Thank you, Kevin, I wonder though if key definition file bypasses the PIN requirement? Is there any possibility to edit default PIN having root privileges?
I have 02e0 ID, it seems, at least in W10 as BT device :)

Hey Max,
I'm not sure if that actually bypass the PIN or if it just trick the device into thinking it's an older firmware that didn't require PIN. I read online that some had success in using that method while others didn't. Being rooted I'm sure you can find an API editor or some type of App that bypass the PIN via entering the MAC address manually. I'll look on my days off but as of right now I'm stumped as well. Thankfully it works flawlessly on both my S6 Edge and Tab S2, but not on my son's Tab 2 :(

Unfortunately, this method doesn't work for me here ^_^
Thank you for your time with pinpointing this problem, I'll also try to look further :)

For now,there's simply no way do to that - Microsoft crippled the device with December firmware update. Dick move, MS. In addition there's no way to downgrade for now.

got this issue,, the newest xb1 controller firmware only work on old mid-end device(lg g3 stylus, nexus7-2012) and not work with high-end device, I think this is caused by bluetooth version 4.0, 4.1.

Hey can it work on mcpe? Microsoft added a key mapping of controller there

worked like a charm, I'm not on never firmware, and at this point I see no need  to do so.

I am going to do a bit of a writeup.

I have a OnePlus 5 on Android 7.1.2 and I bought an Xbox One Bluetooth (black/military green monocolor with orange underneath thumbsticks, Lot No/Date 1647 (indicating built in year 2016) with Model No 1708 and WL3-00035. I was trying to play Geometry Wars 3 with the Xbox One controller out of the box and the left stick worked great, however the right stick was not functioning as expected. After a couple hours of research, I stumbled upon this thread and tested out the keyboard input files by placing them into /system/usr/keylayout with permissions 644, and the right stick started working properly and the start button which used to be the middle Xbox button was now the start button as expected. All was good. I updated the firmware of my Xbox One controller using the Xbox Accessories app with a Micro USB cable on my Windows 10 laptop and then tested out the controller again on my OnePlus 5 - the start button is now the right bumper (RB) button, but both sticks and A and B are still working fine. I would suggest not updating, unless someone can somehow update the mapping files. However, I tested the latest Xbox One controller firmware with and without the mapping files and without it, the right stick would not work again indicating that the mapping files are still working.

My OnePlus 5 has Bluetooth 5.0 but I can also try out my Nexus 6P which has Bluetooth 4.2 to see how well the Xbox One controller works both with and without the mapping files on the latest Xbox One controller firmware. I suspect it will work about the same as my OnePlus 5.


All in all, this is awesome, thank you so much, OP! <3

Sorry for double posting but it seems that the Google issue tracker does not allow editing of comments - that's a shame. After disconnecting and reconnecting my Xbox One controller again to my OnePlus 5 with the latest Xbox One controller firmware, it seems like all the buttons are working again as expected - start is the start button, RB is what it is supposed to be, X is working again, etc. It seems that updating the firmware didn't seem to affect the mapping files for me whatsoever - all is working fine for me. Just thought I would inform people of my experiences with this and the latest (presumably December, although I am unsure how to check) Xbox One controller firmware. :)

The keys are all corresponding, but LT and RT still cannot be used. Is there a solution?

I'm having the same issue. Trigger buttons are not working or rather are not mapped correctly.

When I boot up Gamepad Tester and fiddle around with the controller, all the buttons are correctly mapped except for LT and RT which are mapped to the BRAKE axis (assigned to 'axis 0x17').
Additionally, only the LT button seems to alter the BRAKE axis (increases the value) and yet the RT button doesn't do anything at all (does not decrease the value even if I hold LT).

I'm using an Xbox One Wireless Controller (uses Bluetooth) on a Galaxy S7 freshly updated with Oreo.
Gamepad Tester is reporting my gamepad is using the Vendor_045e_Product_02fd.kl file for the mappings.

Hey! My xbox controller syncs up fine and for the first couple of runs, worked fine.  Then my android tv forgot the device and had to resync.  Ever since the triggers are the wrong way round and i also have to resync the device everytime i start my controller or tv.  Does anyone know how i can fix this?  Seems weird that it actually worked for a time.  Im also runnig steam link through the android tv.

I made my own key layout but the triggers still don't work. Any help?
Any way to change the triggers to buttons?

update: got the triggers working but the left trigger is also bound to the BRAKE axis, the select button now works as intended

I was able to get it working with proper mapping by updating the firmware for the controller. I connected it to my PC then opened the "Xbox accessories" app from the windows store and followed the instructions to update.
No root required.

Do the triggers work?
Does the select(view button) work?

Just fired up Minecraft on my phone (mainly because it shows you what buttons are supposed to be what and you can rebind controls if needed.) and both triggers and the menu/select buttons work great.
No root or modifications to my phone.

This bug should be fixed in P, see:
https://android.googlesource.com/platform/frameworks/base/+/refs/heads/sdk-release/data/keyboards/Vendor_045e_Product_02e0.kl
Therefore, marking this as fixed.

Now, I am seeing in comment #41 and comment #44 that there's a slightly different device with product id 02fd. Is that a newer model? Where did you buy it?

Hello, gamepad works like a charm on Android running Pie, but vibration is only supported via USB connection. Is it possible to add vibration support over bluetooth as well?

Can you please file a new bug, provide some more information, and link to it here?

This is broken again with Android 10
Triggers are not mapped at all
Start/Select is incorrectly mapped
Right joystick is mapped to buttons
X and Y are flipped

Gamepad: 02E0 product ID according to Gamepad Tester
Pixel 3: Android 10 Build Number QP1A-191005.007

I am using Android 9, and it has mapping problems over USB now even. Right analog stick is being detected as if it's just being constantly pulled up-and-to-the-left, and pressing the triggers actually moves what's supposed to be a right analog stick.

I made this for xbox 360 wireless controller works in android 9

Regarding comment #53,

could you please let us know which device you tested your layout on, and whether the device has CONFIG_XPAD enabled in the kernel?

Same i tested my wired xbox one controller with a usb pord to my galaxy a50

Is this cool? I want it!

.