[KERNEL]Kernel with full support for XBox 360 / One controllers[v1.3]

darksabre_x

Senior Member
Nov 8, 2008
115
41
0
Hello socksi since the sources of 5.1 are released....can we expect some new kernel from you please? Thx
Looks like 5.1 shares it's kernel with 5.02.
I just tested the version I shared and it works with 5.1.

No need for a new kernel to be compiled. We already have it. :D
 

Toniooo

Senior Member
Oct 31, 2009
89
42
0
Crotone
Looks like 5.1 shares it's kernel with 5.02.
I just tested the version I shared and it works with 5.1.

No need for a new kernel to be compiled. We already have it. :D
i've tested your kernel with a simple boot but my wireless gamepad not respond like expected, back button and xbox button not respond, maybe because is not installed? or obviously because is not updated?the kernel worked fine for the rest
thank for your work
 

Con21

Member
Apr 22, 2015
12
3
0
i've tested your kernel with a simple boot but my wireless gamepad not respond like expected, back button and xbox button not respond, maybe because is not installed? or obviously because is not updated?the kernel worked fine for the rest
thank for your work
This can likely be fixed by adding the corresponding keylayout (requires root). I had the same problem with earlier versions of the kernel and the Xbox One Controller. I did the following:
https://forum.xda-developers.com/showpost.php?p=69673388&postcount=49

For the Xbox 360 Controller you could try this: https://forum.xda-developers.com/showpost.php?p=67691145&postcount=40
 
  • Like
Reactions: darksabre_x

Toniooo

Senior Member
Oct 31, 2009
89
42
0
Crotone
This can likely be fixed by adding the corresponding keylayout (requires root). I had the same problem with earlier versions of the kernel and the Xbox One Controller. I did the following:
https://forum.xda-developers.com/showpost.php?p=69673388&postcount=49

For the Xbox 360 Controller you could try this: https://forum.xda-developers.com/showpost.php?p=67691145&postcount=40
if i ask for kernel is because i'm alredy rooted and already have a correct keylayout for my contorller,
simply the system freeze for a while when i push xbox button or select
 

darksabre_x

Senior Member
Nov 8, 2008
115
41
0
if i ask for kernel is because i'm alredy rooted and already have a correct keylayout for my contorller,
simply the system freeze for a while when i push xbox button or select
Con21 is spot on.

The kernel just provides drivers for the controllers to be fully recognized, especially in situations where you are using a clone/3rd party dongles. Everything else is stock on this kernel, except for the replaced xpad driver.

Issues with specific buttons not working as expected can be traced back to your keylayout files as it controls the mapping of the buttons. I recommend starting there to compare your keylayout files with the links Con21 provided.

I'm not sure what you are using to modify the keylayouts, but I recommend staying away from Notepad++. It does weird encoding things to the files and gave me tons of headaches when I first started messing about with keylayouts.
 
  • Like
Reactions: Toniooo

Toniooo

Senior Member
Oct 31, 2009
89
42
0
Crotone
Con21 is spot on.

The kernel just provides drivers for the controllers to be fully recognized, especially in situations where you are using a clone/3rd party dongles. Everything else is stock on this kernel, except for the replaced xpad driver.

Issues with specific buttons not working as expected can be traced back to your keylayout files as it controls the mapping of the buttons. I recommend starting there to compare your keylayout files with the links Con21 provided.

I'm not sure what you are using to modify the keylayouts, but I recommend staying away from Notepad++. It does weird encoding things to the files and gave me tons of headaches when I first started messing about with keylayouts.
ok if the proble was in kl even in the stock kernel they don't work
but not. iv'e tried many kl that work well on stock kernel even the kl that work on earlier kernel version with the correct driver loaded.
anyway this kernel won't work on my shield 2016 16gb 5.1 with wireless controller :(
 

darksabre_x

Senior Member
Nov 8, 2008
115
41
0
ok if the proble was in kl even in the stock kernel they don't work
but not. iv'e tried many kl that work well on stock kernel even the kl that work on earlier kernel version with the correct driver loaded.
anyway this kernel won't work on my shield 2016 16gb 5.1 with wireless controller :(
There is no Shield Tv 2016. This kernel was built using the Shield Tv 2015 sources. If you have one of the newer Shield Tv's(2017) with the geometric controller, then this kernel won't work for you. The Shield Tv 2017 has different kernel sources.
 

Toniooo

Senior Member
Oct 31, 2009
89
42
0
Crotone
There is no Shield Tv 2016. This kernel was built using the Shield Tv 2015 sources. If you have one of the newer Shield Tv's(2017) with the geometric controller, then this kernel won't work for you. The Shield Tv 2017 has different kernel sources.
sorry my mistake my shield is the first model the 2015
i think if i did somthing of this on the new model i brick it!!
 

darksabre_x

Senior Member
Nov 8, 2008
115
41
0
sorry my mistake my shield is the first model the 2015
i think if i did somthing of this on the new model i brick it!!
You're right, you'd probably either brick it or it would refuse to flash if it was a 2017. Just checkin' off all the boxes.:good:

Ok just to gather all your info into one place:

You have a Shield TV 2015
You have Xbox360 wireless controller adapter connected to your Shield Tv
The back button and the xbox guide button are not working after flashing this kernel, but were working on a stock kernel. (Which is odd to me, as the xbox guide button never worked for me on stock.)


If you don't mind me asking, why are you trying to flash a custom kernel? Just for the blinking button fix?
Would you mind providing the KL file you have been checking, or just post the contents?

Your issue is definitely in the KL files, now we just have to find the lines that are causing the funky behavior.
 

Toniooo

Senior Member
Oct 31, 2009
89
42
0
Crotone
You're right, you'd probably either brick it or it would refuse to flash if it was a 2017. Just checkin' off all the boxes.:good:

Ok just to gather all your info into one place:

You have a Shield TV 2015
You have Xbox360 wireless controller adapter connected to your Shield Tv
The back button and the xbox guide button are not working after flashing this kernel, but were working on a stock kernel. (Which is odd to me, as the xbox guide button never worked for me on stock.)


If you don't mind me asking, why are you trying to flash a custom kernel? Just for the blinking button fix?
Would you mind providing the KL file you have been checking, or just post the contents?

Your issue is definitely in the KL files, now we just have to find the lines that are causing the funky behavior.
ok i don't have many time to testing but i have a little update even the right stick not work well,
however on stock kernel with stock kl my gamepad have the analog stick not setting well and i must be forced to modifyng the kl even on stock and there everything work well even the xbox button setted to home...
the correct kernel solve many problem on gamestrem that detect only the connected controller and not four controller where the only controller connected numbered 3 was useless.
the strange thing is that from the beginning the same modified kl that have worked from fw 3.1 to 5.1 stock or modified here no
here my kl
 

Attachments

darksabre_x

Senior Member
Nov 8, 2008
115
41
0
ok i don't have many time to testing but i have a little update even the right stick not work well,
however on stock kernel with stock kl my gamepad have the analog stick not setting well and i must be forced to modifyng the kl even on stock and there everything work well even the xbox button setted to home...
the correct kernel solve many problem on gamestrem that detect only the connected controller and not four controller where the only controller connected numbered 3 was useless.
the strange thing is that from the beginning the same modified kl that have worked from fw 3.1 to 5.1 stock or modified here no
here my kl
Do you have Vendor_045e_Product_0291.kl? If not you need to check out this post: https://forum.xda-developers.com/showpost.php?p=67691145&postcount=40

Add that into a Vendor_045e_Product_0291.kl file in /system/usr/keylayout/ and set the proper permissions. Reboot and see if that fixes your issues.
 

iacob

Member
May 18, 2010
43
6
0
Hi, have you ever found the answer on this one?
I am in the same situation... could be keylayout related but I have not identified the "right" values.
Sorry for the post necromancy :)

Thanks!
 

Toniooo

Senior Member
Oct 31, 2009
89
42
0
Crotone
Do you have Vendor_045e_Product_0291.kl? If not you need to check out this post: https://forum.xda-developers.com/showpost.php?p=67691145&postcount=40

Add that into a Vendor_045e_Product_0291.kl file in /system/usr/keylayout/ and set the proper permissions. Reboot and see if that fixes your issues.
ok i have pushed the kl for the usb gamepad Vendor_045e_Product_0291.kl but nothing has changed
i can assume there isen't a kl problem...
i have tried tons of kl from different sources
no way
:(
 

darksabre_x

Senior Member
Nov 8, 2008
115
41
0
ok i have pushed the kl for the usb gamepad Vendor_045e_Product_0291.kl but nothing has changed
i can assume there isen't a kl problem...
i have tried tons of kl from different sources
no way
:(
Sorry it's not working for you. Unfortunately I'm all out of suggestions other than wiping your system fresh and then installing the kernel, or trying your hand at compiling your own. The instructions for compiling your own kernel are linked in the first post, along with the link directly to the Nvidia sources. If a wipe doesn't work (or isn't something you are trying to do) then I would go that route to see if you can compile one that works for you.

The kernel I offered up is from the stock sources with only the xpad.ko replaced. Any .kl files compiled along with it are stock.

The only thing we haven't ruled out is your wireless dongle itself. Maybe it's reporting a different vendor and product code than the ones suggested thus far.

You could always adb in and run this command:
Code:
cat /proc/bus/input/devices
Find your wireless dongle in the list and note down the vendor and product id. It comes in a format like this:
Bus=0003 Vendor=062a Product=2901 Version=0110

This will help ensure we are modifying the correct kl file.



Other than the suggestions above, I'm all out of ideas. Best of luck.
 
  • Like
Reactions: Toniooo

Toniooo

Senior Member
Oct 31, 2009
89
42
0
Crotone
ok i've found a solution!
into new kernel Vendor_045e_Product_0291.kl became Vendor_045e_Product_02a1.kl
make a copy of Vendor_045e_Product_0291.kl rename an put in system/usr/keylayout whit correct permission and
all goes fine now!
if someone have problem this is the solution
cheers