Deleted js0 file for controller [SOLVED]

DefLeper · 2025-12-06 08:40:09

Might be a weird one. I bought a pair of 3rd party AceGamer ps4 controllers on the very cheap. They have been connecting via bluetooth well for about a year now. They both had a slight problem of both needing the "initial connection" procedure every time, instead of just doing the initial connection once then connecting automatically when activated.

I wanted to solve this, and while working out the options I think I may have destroyed the js0 file. Not exactly sure how, but whenever I use the gamepad now, it will connect (via that same initial connection process) but it will not be recognized as a gamepad controller by my computer.

As I bought this in a pair order, its twin still functions now, with a js0 file. Is it possible to delete the js0 file created/associated with a controller? Is it possible to fix? It even still works when plugged in by USB.

I'm not sure what to provide here, I updated my system yesterday, the controller doesn't appear in dmesg, and within /dev/input there is no js0 file while the game controller is bluetooth connected, jstest(joystick test program) also of course detects nothing without the js0 file. If anyone wants to help let me know what you need on my end!

Last edited by DefLeper (2025-12-09 10:47:27)

DefLeper · 2025-12-06 08:58:09

The only think I can think to provide is the Bluez bluetoothctl output showing the controller is connecting, paired, and trusted, but produces no js0 file still. Would it be best to show the /dev/input file even though there are only two folder, many events, and a mouse inside?

[bluetoothctl]> connect 9B:15:EE:33:AF:73
[CHG] Device 9B:15:EE:33:AF:73 Connected: yes
[CHG] Device 9B:15:EE:33:AF:73 Paired: yes
[CHG] Device 9B:15:EE:33:AF:73 ServicesResolved: yes
[Wireless Controller]> trust 9B:15:EE:33:AF:73 
Changing 9B:15:EE:33:AF:73 trust succeeded

Last edited by DefLeper (2025-12-06 08:58:40)

Lone_Wolf · 2025-12-06 12:29:29

That's not a file but a link to access the device directly.
Typically they are created/deleted when the device is plugged in/out .

Please boot the system, perform the "initial connection" procedure for the "faulty" controller.

As root / with root rights run

# journalctl -b | curl -F 'file=@-' 0x0.st

That command will upload your system journal of the current boot to a public hosting site and output a link.
post that link.

seth · 2025-12-06 15:26:26

Also run

udevadm monitor

while connecting the device.
Is this a dual-boot system (windows) and/or do you also use the controller on other devices (PC or PS4)?

DefLeper · 2025-12-07 00:10:02

Thank you for your responses!

For Lone_Wolf, here is the journalctl link: https://0x0.st/KvMs.txt

For seth, here is the udevadm output:

$ udevadm monitor
monitor will print the received events for:
UDEV - the event which udev sends out after rule processing
KERNEL - the kernel uevent

KERNEL[638.696964] add      /devices/pci0000:00/0000:00:01.2/0000:04:00.0/0000:05:08.0/0000:08:00.3/usb3/3-1/3-1:1.0/bluetooth/hci0/hci0:3 (bluetooth)
UDEV  [638.703927] add      /devices/pci0000:00/0000:00:01.2/0000:04:00.0/0000:05:08.0/0000:08:00.3/usb3/3-1/3-1:1.0/bluetooth/hci0/hci0:3 (bluetooth)

That was while connecting the device, which does connect but still does not register as a gamepad. This is not a dual-boot system, it only runs Arch. The controller is used for no other devices, only for this singular arch linux system.

DefLeper · 2025-12-07 00:33:51

This one was after removing the device via bluetoothctl and thena restarting the full "initial connection" procedure https://0x0.st/KvMb.txt
I can't see much different from the two though, but "Rejected connection from !bonded device" in both links seems promising

Last edited by DefLeper (2025-12-07 00:36:17)

seth · 2025-12-07 09:45:23

Dec 06 16:25:49 jamdesk bluetoothd[1256]: profiles/input/device.c:hidp_add_connection() Rejected connection from !bonded device /org/bluez/hci0/dev_9B_15_EE_33_AF_73
Dec 06 16:26:21 jamdesk kernel: logitech-djreceiver 0003:046D:C537.0005: Unexpected input report number 128
Dec 06 16:26:21 jamdesk kernel: logitech-djreceiver 0003:046D:C537.0005: Unexpected input report number 128
Dec 06 16:26:23 jamdesk kernel: logitech-djreceiver 0003:046D:C537.0005: Unexpected input report number 128
Dec 06 16:26:23 jamdesk kernel: logitech-djreceiver 0003:046D:C537.0005: Unexpected input report number 128

Can you test this w/o the logitech dongle attached and logitech-djreceiver being loaded?

DefLeper · 2025-12-09 00:11:31

Yes, here are the results without the Logitech dongle connected: https://0x0.st/Kwda.txt

The controller once again connected but is not recognized as a gamepad by any package, nor is there a js0 link within /dev/input/

I am unsure if this is helpful, but one of many things I did while tinkering was attempt to view the js0 "file" (which I had thought was a file at the time) with a text editor. Once I saw that "js0 is not a directory or file" I made sure to quit without saving. Could this have somehow destroyed the link? I am not sure anything else I did was very invasive, its hard to remember everything I examined, and I actually did very little.

also, should I change the title of the thread to more accurately state "js0 link not appearing" or keep the title as is?

seth · 2025-12-09 08:52:28

Could this have somehow destroyed the link?

Did you use emacs ?
But even if, a reboot would sanitize that.

Dec 08 15:52:30 jamdesk bluetoothd[889]: profiles/input/device.c:hidp_add_connection() Rejected connection from !bonded device /org/bluez/hci0/dev_9B_15_EE_33_AF_73

sudo journalctl -f

Does connecting the gamepad trigger that error?
=> https://bugs.launchpad.net/ubuntu/+sour … ug/2046084

DefLeper · 2025-12-09 09:30:20

seth wrote:

Did you use emacs ? wink

Lol no emacs scares me, I just use nvim. I have rebooted many times too at this point with no return to functionality. Testing it with journalctl -f, yes the error happens at the exact same time as when the device connects.

I read through the thread and I am not sure this is my problem. Its a similar error message for sure, I do find it interesting his error doesn't have the filepath listed. But even the guy there wonders if that is a red herring. The problem appears to be an issue with a bluez update, and that would have presumably affected all his controllers. Mine only affects the one I was messing with, the other exact same controller still connects and is recognized as a gamepad. It's hard to say its the same glitch, but I am more than willing to try the method user Mark Esler suggests:

If you wish to to enable legacy devices (and the vulnerability) with the most recent version of BlueZ set `ClassicBondedOnly=false` in `/etc/bluetooth/input.conf`, and then run `systemctl restart bluetooth`.

I don't think regressing the package as also suggested will work either but I will try both and report back. I don't think its a anything to do with the package I think its probably something I did to the pathway.

I fear this is now a problem with the device itself and I need to look inside of it. No idea how.

Last edited by DefLeper (2025-12-09 09:30:46)

DefLeper · 2025-12-09 10:11:13

Changing the bluetooth input config file and then rebooting bluetooth did not work.
I tested the following package downgrades:
bluez-5.77-1-x86_64.pkg.tar.zst 09-Jul-2024 05:08 558K
bluez-5.78-1-x86_64.pkg.tar.zst 09-Sep-2024 12:34 563K
bluez-5.79-1-x86_64.pkg.tar.zst 02-Nov-2024 08:31 571K
bluez-5.80-1-x86_64.pkg.tar.zst 17-Mar-2025 14:56 579K
bluez-5.80-2-x86_64.pkg.tar.zst 27-Mar-2025 05:37 579K
bluez-5.81-1-x86_64.pkg.tar.zst 01-Apr-2025 15:31 579K
bluez-5.82-1-x86_64.pkg.tar.zst 02-Apr-2025 13:13 580K
bluez-5.83-1-x86_64.pkg.tar.zst 02-Jun-2025 15:59 565K
bluez-5.84-1-x86_64.pkg.tar.zst 19-Sep-2025 22:07 571K
bluez-5.84-2-x86_64.pkg.tar.zst 10-Nov-2025 20:19 571K
bluez-5.85-1-x86_64.pkg.tar.zst 21-Nov-2025 17:48 575K

After downgrading I then restarted bluetooth just in case. The error message appeared in journalctl exact moment when the device connected every time in the same way. I don't think downgrading will work, but should I try the next 10?

DefLeper · 2025-12-09 10:44:32

It brings me great confusion to mark this problem as "SOVLED"

If anyone else somehow finds themselves in this same odd situation, it appears that while I used bluetoothctl in the terminal to pair my controller, that it didn't work completely.

The blueman-applet that I normally use to handle connecting devices still had the key icon above it to "create a pairing" (even though the info from that same blueman-applet also did say the device was paired when I right-clicked on the device and selected "info") All I had to do was click the key to create the pairing that was already there and it worked. No other device required this.

This was also after reinstalling bluez and restarting bluez many times.

I am not fully sure what happened. But to summarize, if you use the blueman-applet to manage your devices, make sure the key icon on the device is NOT lit up. If it is lit up, click it and make sure to pair the device. It should fade, and your device should work.

Last edited by DefLeper (2025-12-09 10:50:06)

DefLeper · 2025-12-09 11:30:44

A hopefully final follow up, this is my own fault. While using bluetoothctl I tried to "connect" the device first instead of "pair" the device. Always make sure to PAIR the device first if you are having this problem! Even if after it says "device paired" after connecting it does not fully pair. It must only mean that for that instance. My mistake!

Arch Linux

#1 2025-12-06 08:40:09

Deleted js0 file for controller [SOLVED]

#2 2025-12-06 08:58:09

Re: Deleted js0 file for controller [SOLVED]

#3 2025-12-06 12:29:29

Re: Deleted js0 file for controller [SOLVED]

#4 2025-12-06 15:26:26

Re: Deleted js0 file for controller [SOLVED]

#5 2025-12-07 00:10:02

Re: Deleted js0 file for controller [SOLVED]

#6 2025-12-07 00:33:51

Re: Deleted js0 file for controller [SOLVED]

#7 2025-12-07 09:45:23

Re: Deleted js0 file for controller [SOLVED]

#8 2025-12-09 00:11:31

Re: Deleted js0 file for controller [SOLVED]

#9 2025-12-09 08:52:28

Re: Deleted js0 file for controller [SOLVED]

#10 2025-12-09 09:30:20

Re: Deleted js0 file for controller [SOLVED]

#11 2025-12-09 10:11:13

Re: Deleted js0 file for controller [SOLVED]

#12 2025-12-09 10:44:32

Re: Deleted js0 file for controller [SOLVED]

#13 2025-12-09 11:30:44

Re: Deleted js0 file for controller [SOLVED]

Board footer