Xbox360 wireless controllers - receiver connectivity issues

rossoe

Having the same odd behavior with my wireless xbox controller. since update from 3.6 to 3.8 I seem to lose connection, sometimes after the sleep screensaver, sometimes after a reboot. thought it was down to batteries in the controller at first as it usually behaves odd when they are low. but replaced those and still getting the issue. I'm only using 1 controller.

Why is everyone jumping back to 3.6, what's wrong with 3.7?

backstander

I'm also having the same issues. I've tried upgrading from 3.6 to 3.8 and I've also tried a fresh flash of 3.8 but neither seams to consistently work and if I do get it to work, it seams to break on the next reboot. I sometimes can get it to temporarily work by SSH into my Pi and typing "sudo killall xboxdrv" then reloading the Xbox driver with "sudo xboxdrv --trigger-as-button --id 0 --led 2 --deadzone 4000 --silent & sleep 1".

I just hope the awesome people at RetroPie can release a fix for this soon :)

pomme

Will downgrading to 3.7 break anything with my Kodi 16 install? That's the main reason I upgraded, working controller (when it works!) and clean exits from Kodi.

Could anyone be so kind as to post a link to downgrade instructions?

mediamogul

Is it possible these two incidents are related?

https://retropie.org.uk/forum/topic/1686/up-down-y-axis-not-working-in-3-8
The issue there was that, after the 3.8 upgrade, the joystick codes that were received from the controllers did not match up with the codes that were automatically mapped in the config files under 3.7 and below. Could it be that xboxdrv is outputting a virtual joystick device that is having the same problem?

Edit: Or even that xboxdrv expects to find certain input codes that are no longer the same?

trixter1981

Hi guys,
I've tested several kernels (including the latest) and it seems that there's an issue with xboxdrv and libusb starting with kernel 4.4.6-3.
See the discussion here: https://discourse.osmc.tv/t/april-update-xboxdrv-not-working/15291/3

To fix the issue I've performed a downgrade to kernel 4.1.21-v7+.
This is doable with rpi-update, unfortunately the script had some issues so I patched it to skip the certificate check. You can find it here: http://pastebin.com/e2ZKSMr1.
Just copy and paste the script, save it in /usr/bin/rpi-update. Then chmod +x rpi-update /usr/bin/rpi-update.

The command to use is this one:

rpi-update 771a503cfc2a1130e2df2a4ddfc45ffa0f592b3f

that downgrades to this precise committed version: https://github.com/Hexxeh/rpi-firmware/commit/771a503cfc2a1130e2df2a4ddfc45ffa0f592b3f

hope this will help!

all the best and thanks! I really love the retropie project!

pomme

@trixter1981 said in Xbox360 wireless controllers - receiver connectivity issues:

Just copy and paste the script, save it in /usr/bin/rpi-update. Then chmod +x rpi-update /usr/bin/rpi-update.

The command to use is this one:

rpi-update 771a503cfc2a1130e2df2a4ddfc45ffa0f592b3f

This didn't work for me, but I think the problem might be my noobness.

I did not have a file called rpi-update in my /usr/bin directory. So i copied your script and put it in notepad++ and saved it without and extension. I had permission problems and errors about the file not existing, even though i could nano into the file and see that it looked normal.

Basically, I got to where I was in the directory and attempting to run rpi-update 771a503cfc2a1130e2df2a4ddfc45ffa0f592b3f - it wouldn't work, i tried sudo rpi..., sudo ./usr/bin/rpi.. then finally I tried sudo sh rpi-update 771a503cfc2a1130e2df2a4ddfc45ffa0f592b3f and it didn't throw and error and it kicked me to the next line. I thought maybe it worked, but it didn't (was expecting some scrolling text if it were to finally work.

Do you care to elaborate a little more on applying the rollback with your script? You're speaking a little above my level (and my even nerdier friend I had on the phone with me).

trixter1981

@pomme

sudo su -
curl 'http://pastebin.com/download/e2ZKSMr1' -o 'patched_rpi-update.sh' -L -B
cp patched_rpi-update.sh /usr/bin/rpi-update
chmod +x /usr/bin/rpi-update
/usr/bin/rpi-update 771a503cfc2a1130e2df2a4ddfc45ffa0f592b3f

the script is not from me, this awesome guy created it but I had issues with the curl command (certificates?!?) https://github.com/Hexxeh/rpi-update

if you want to upgrade to the latest firmware simply use:

/usr/bin/rpi-update

good luck! let me know how it goes

raelik

@trixter1981 your post is missing some necessary line breaks:

sudo su -
curl 'http://pastebin.com/raw/e2ZKSMr1' -o 'patched_rpi-update.sh' -L -B
tr -d '\015' < patched_rpi-update.sh > /usr/bin/rpi-update
chmod +x /usr/bin/rpi-update
/usr/bin/rpi-update 771a503cfc2a1130e2df2a4ddfc45ffa0f592b3f
rm ~/patched_rpi-update.sh
exit

JPL

Sorry, but I'm having trouble getting the instructions above to work properly. I get this error after following them and running the rpi-update script:

-bash: /usr/bin/rpi-update: /bin/bash^M: bad interpreter: No such file or directory

I undid my work and followed the instructions again and got the same error.
Is it reading an ^M character after the shell declaration on the top line? I tried re-typing that line with nano and vim and neither made a difference.

raelik

@JPL I've edited my post to reflect how to fix that.

JPL

@raelik This works for me, thank you very much!

pomme

Getting good results so far with most recent commands posted. Thanks you! This was driving me crazy!

UDb23

@trixter1981 thanks for posting this downgrade script.
I'll try it to solve the Logitech controller not working issue after 3.8 update.

Did you report the kernel problem on Github ?
I would do it but I'm not skilled enough to technically explain this kernel problem.

rossoe

Can you please tell me what I'm doing wrong here with permissions?

First line works ok:

sudo curl 'http://pastebin.com/raw/e2ZKSMr1' -o 'patched_rpi-update.sh' -L -B
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 11038 0 11038 0 0 90959 0 --:--:-- --:--:-- --:--:-- 91983

Then I have trouble with:

sudo tr -d '\015' < patched_rpi-update.sh > /usr/bin/rpi-update

-bash: /usr/bin/rpi-update: Permission denied

which means I get the certificate errors carrying on with the further commands.

pomme

@rossoe said in [Xbox360 wireless controllers - receiver connectivity issues]

-bash: /usr/bin/rpi-update: Permission denied
which means I get the certificate errors carrying on with the further commands.

I got this error too. Make sure you are logged in as root user. You may need to create a root user account.

raelik

@pomme Yeah, I should have mentioned you should run sudo su - (to switch to root) before doing any of this. Fixed my post (again).

rossoe

worked perfectly thank you.

can we easily upgrade to the newly released 3.8.1 without the kernel jumping back up to the broken version?

trixter1981

done the upgrade to 3.8.1, it's okay. The kernel is untouched.

zanie420

RPI 3
Retropie 4.0-dev

Having the same issues getting wireless 360 receiver to work consistently after fresh install and enabling xboxdrv via the script. Tearing my hair out! No output from jstest /dev/input/js0.

However, I too can get it to work by logging into SSH as root and using:

killall xboxdrv
xboxdrv --trigger-as-button --id 0 --led 2 --deadzone 4000 --silent & sleep 1

This didn't work until I blacklisted xpad and installed xboxdrv via apt-get

Randomly the controller stops working and you have to redo it. Restarting puts you back a square one, but the workaround IS consistent it seems.....

What the hell am I doing wrong?

backstander

@zanie420 if you read down below my post (trixter1981 & raelik posts), there is a workaround that will downgrade the kernel. The xboxdrv seams to work pretty consistently after this downgrade.