-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issues with J416 support #41
Comments
Some initial points:
What distro are you using? Please post the output of |
Hi, Thanks for the clarification. I'm currently using Fedora Linux Asahi Remix 40 (Forty). Here's the output of ̀
Here's the diagnosis as well: Thanks! |
Speakersafetyd is launching at boot, so you shouldn't try to start it manually. Again, please do not try to change the device's profile. You need to keep it at default. Can you try to delete |
Done. For now, I'll just use the headphones instead since the J416 is rather unstable on GNOME and the convolver doesn't work. Let me know if you need further tests/feedbacks. |
Hello,
I'm running a Macbook M2 Pro from 2023 with J416 speakers, on GNOME.
I've noticed some issues with this hardware:
I guess the J416 support isn't ready yet. Or did I miss something?
Let me know how can I help otherwise.
Thanks a lot for your work!
EDIT: I've found
/usr/share/speakersafetyd/appl/j416.conf
but for an unknown reason, speakersafetyd looks for the profile from/usr/local
, I'll investigate why...The text was updated successfully, but these errors were encountered: