01:02 <Mr0btain> Hmm, I plan to try other window managers but I'll dive into mutter and see if I can magically stumble upon the perfect fix all that solves all the audio gpu and Bluetooth. lol.

01:07 <Mr0btain> I'd have better luck running for president and enacting that everything be open sourced. But a man can dream.

01:08 <HdkR> Don't worry, a different DE won't solve GPU

03:28 <Mr0btain> Got any ideas what might be the problem?

03:30 <steev> the problem is we don't have the gpu stuff in the kernel yet, mainly

03:31 <steev> i push the stuff out so people can *work* on it, not so that they can test and say it still doesn't work, we already know that :)

03:31 <steev> bluetooth also isn't in yet. i have the numbers around here somewhere but i haven't looked recently

03:32 <clover[m]> Yay

03:32 <clover[m]> Sick of my bt dongle

03:33 <steev> the fixes will be kernel side, not userland side

03:43 <steev> iirc, the driver itself doesn't know about the firmware, maybe i'll try to find some time this week

04:02 <steev> yeah, nothing in the kernel seems to know about hpnv which is the prefix for the x13s bt firmware i have

04:15 <steev> at least, i'm showing the firmware is hpnvXX

05:53 <steev> re audio, there are still a few hacks, and the ucm2 configs haven't been sent upstream, and we still need to (afaik) figure out with it works on 21BY but not on 21BX

07:26 <Mr0btain> steevdave[m]: Ohh sorry I misunderstood, I was under the impression it was implemented but something with gnome just wasnt playing nice with it.

07:26 <Mr0btain> steev* damn Android app keeps correcting things it has no business in 🤣

16:47 <steev> it's okay, that's my matrix account

20:08 <Mr0btain> Might be a noob question but what is a matrix account? lol

20:11 <qzed> Matrix is another chat network/protocol thing. It has a bridge to OFTC IRC so you can participate here with any Matrix client

20:31 <Mr0btain> ohhh okay that's pretty cool. I'm about as new as it gets to irc. Didn't even know it existed untill a month ago

20:40 <Mr0btain> Also on the x13s sound I read about the WSA881x and the order of port enables being very picky. They said if they were off it caused DC to buildup in the line and caused clicking and popping. Which sounds on par with what steev had going on. But I failed to find a difference between the two variants. i can't recall if it was the bx or by that it w

20:40 <Mr0btain> orked on. Either way I got the unlucky one

21:02 <Mr0btain> for clarity I know the wsa881x isn't what's in the x13s, it's the wcd9385. just sounded like the same thing was happening in this case

21:04 <Mr0btain> The codec anyway

21:42 <steev> well a similar clicky poppy thing is happening on the c630 which iirc does have wsa881x

21:54 <steev> from what i can tell, when audio does work (the first time playing) it hits an underflow and then... it starts popping and goes wonky

21:54 <steev> on the x13s

22:05 <Mr0btai93> Interesting. I was nervous about attempting it at first but I'm willing to risk losing a speaker, I have protection through Verizon so they'll fix it when I call in and say "Idk man it just exploded while I was watching skin flicks"

22:26 <steev> i need to go back through my patchsets folder to find the audio ones