Not pointless but redundant. . It's so much work that needs to constantly be worked on every time there is an update and it has very little payoff. Just upgrade your controllers to the Bluetooth version. Its a nice idea just redundant these days
Doea this work on the lastest 7.2 sheild experience update?Because of the annoying constantly blinking LEDs of the wireless Xbox 360 controller I decided to compile an updated kernel myself.
I was Inspired by this post.
This kernel is 100% Nvidia source. The only difference is the backported xpad driver.
It is intended for use with Nvidia Shield Marshmallow firmware including zulu99's StockRestyle and full Android Marshmallow firmwares.
I have only tested it with the Pro model. It has been reported that it works with the 16GB model also.
Xbox One controllers are working also but only wired.
You can test the kernel by booting the new kernel with fastboot boot boot_xpad.img before flashing it.
If you are using systemless SuperSU (v2.56+) keep in mind that you will lose root when you flash or boot a new kernel.
Afterwards you can install SuperSU again by booting into recovery and installing the SuperSU.zip.
v1.4 kernel for firmware v3.3.0 with latest xpad driver from kernel.org
v1.3 kernel for firmware v3.2.0 with xpad driver from Linux kernel 4.7 rc6
v1.2 kernel for firmware v3.1.0 with latest xpad driver from Valve
v1.1 kernel for firmware v3.0.0 with latest xpad driver from Valve
v1.0 kernel for firmware v3.0.0 with xpad driver from Linux kernel 4.5
Thanks for being a smartass but okay prick
adb reboot bootloader fastboot flash boot boot_xpad.img
v1.4 - kernel for firmware 3.3.0 v1.3 - kernel for firmware 3.2.0 v1.2 - kernel for firmware 3.1.0 v1.1 - found a newer version of the xpad driver directly from Valve - support for Xbox One Elite and a few other third party controllers has been added
He has to wait for the source of the last update to get released to compile the latest kernel. In the past Nvidia releases them a few weeks after the update and socksi is on it pretty quickly. However Nvidia updated again before the source was released for the first one, so I'm unsure what kind of timeframe we're looking at.
# Dpad key 704 DPAD_LEFT key 705 DPAD_RIGHT key 706 DPAD_UP key 707 DPAD_DOWN
Doesn't seem that I have an 0291. I see 028e and 0719, which are the files I've been modifying...... hmmm seems I have some more poking to do on this system
Sent from my SM-G930T using XDA Labs
Do you feel giving enough to provide a copy of your kl? If not, it's cool you've provided a lot of help already!
# Copyright (C) 2011 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. # # XBox 360 USB Controller # 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 314 BACK key 315 BUTTON_START key 316 HOME key 317 BUTTON_THUMBL key 318 BUTTON_THUMBR # Left and right stick. # The reported value for flat is 128 out of a range from -32767 to 32768, which is absurd. # This confuses applications that rely on the flat value because the joystick actually # settles in a flat range of +/- 4096 or so. axis 0x00 X flat 4096 axis 0x01 Y flat 4096 axis 0x03 Z flat 4096 axis 0x04 RZ flat 4096 # Triggers. axis 0x02 LTRIGGER axis 0x05 RTRIGGER # Hat. axis 0x10 HAT_X axis 0x11 HAT_Y # Dpad key 704 DPAD_LEFT key 705 DPAD_RIGHT key 706 DPAD_UP key 707 DPAD_DOWN