greyjedi

joined 1 year ago
[–] greyjedi@lemmy.world 2 points 8 months ago

Yeah, I tried that. Didn't make a difference, unfortunately.

[–] greyjedi@lemmy.world 3 points 8 months ago (1 children)

Yeah, at this rate I'm probably just going to get a USB wireless adapter since it's not playing nice with my bluetooth

[–] greyjedi@lemmy.world 1 points 8 months ago

I updated the firmware on Sunday, before even attempting to connect it to bluetooth

[–] greyjedi@lemmy.world 2 points 8 months ago

It has bluetooth. I'm able to connect it to bluetooth on Windows 10 with the same computer and was able to connect it to a Fedora 39 KDE laptop via bluetooth, as well.

I suspect the issue is the Linux driver for the MediaTek MT7921K or the bluetooth configuration on my arch linux system needs to be adjusted somehow

 

Hello,

I can not get my bluetooth to discover my xbox core wireless controller. I'm running a dual boot with a Windows 10 install. There are no issues connecting to bluetooth on windows. I am also able to connect the controller to a laptop running Fedora 29 KDE.

I have already upgraded the firmware of the controller. I have installed xpadneo.

I have tried installing xone-dkms and xboxdrv-stable-git, neither of those worked. I have since uninstalled those to avoid any conflict with xpadneo.

Bluetoothctl sees other bluetooth devices, but never shows the MAC of the controller when I start a scan and put the controller in pairing mode. I verified that it has LE enabled.

Waiting to connect to bluetoothd...[bluetooth]# hci0 new_settings: powered bondable ssp br/edr le secure-conn cis-central cis-peripheral 

My bluetooth device is an RZ608 (MediaTek MT7921K), which is using the kernel driver to work.

What am I missing that could potentially keep my Arch Linux desktop from even seeing the broadcasted MAC of the controller in order to even start the connection process?

EDIT:

So, the issue is definitely Bluez. I can see the controller broadcasting if I use bettercap and run the command 'ble.recon on'. Still haven't found a good solution, though.

Tried switching to the arch lts kernel. Didn't make a difference. Tried forcing bluetoothctl to only use le and scan le. No devices.

Tried adding the changes to /etc/bluetooth/main.conf and restarting the bluetooth service (and rebooting the computer)

Privacy = device
JustWorksRepairing = always
Class = 0x000100
FastConnectable = true

No changes in behavior.

I know it's not a driver issue, because bettercap could see the bluetooth devices. BlueZ must have a bug or something.

[–] greyjedi@lemmy.world 80 points 1 year ago (11 children)

You can permanently activate it with the scripts from massgravel: https://github.com/massgravel/Microsoft-Activation-Scripts

[–] greyjedi@lemmy.world 33 points 1 year ago (6 children)

What are the chances that it's just not rendering something due to the DX12 to Vulkan translation?

[–] greyjedi@lemmy.world 5 points 1 year ago (7 children)

A few years ago, before Google introduced YouTube music, they had the Google Play Music app that let you listen to their entire catalog, download/cache the songs beforehand, listen to your own audio files on local storage (including .flac files), and subscribe and listen to Podcasts.

Literally was one of my most used apps until YouTube Music happened and they had less features for double the price.