- Alsa-devel - mailman.alsa-project.org

Dinosaur Game: A Simple Offline Game with Endless Fun
by wallaceholcomb610＠gmail.com 06 Jan '26

06 Jan '26

Dinosaur Game is a simple yet iconic browser game that appears in Google Chrome when there is no internet connection. At first glance, it looks very basic, but behind its minimalist design lies an addictive and surprisingly challenging experience that has entertained millions of players worldwide. https://dinosaur-game.io The game starts when a small pixelated dinosaur appears on the screen along with a message saying there is no internet connection. By pressing the spacebar or tapping the screen, the dinosaur begins to run automatically across a desert landscape. The goal is simple: avoid obstacles for as long as possible and achieve the highest score you can. Gameplay in Dinosaur Game is extremely easy to understand. The dinosaur runs forward nonstop, and players must jump over cacti and later dodge flying pterodactyls. As the game continues, the speed gradually increases, making obstacles appear faster and closer together. This rising difficulty keeps the game exciting and forces players to stay focused at all times. One of the most interesting aspects of Dinosaur Game is its visual style. The game uses black-and-white pixel graphics that are clean and simple. There are no unnecessary details, which helps players clearly see obstacles and react quickly. Occasionally, the background switches between day and night, adding a small but enjoyable visual change. Unlike many modern games, Dinosaur Game has no background music. This silence allows players to concentrate fully on the timing of their jumps. The lack of sound also makes the game suitable for playing anywhere, such as at school, work, or in public places. Dinosaur Game is popular because of its accessibility. It requires no download, no account, and no internet connection. Anyone using Google Chrome can play it instantly. This makes it enjoyable for players of all ages, including people who do not usually play video games. Although Dinosaur Game is mainly designed for fun, it also helps improve reaction time and concentration. Players must learn to anticipate obstacles and respond quickly as the speed increases. Because each round restarts instantly after failure, the game encourages repeated attempts and self-improvement. In conclusion, Dinosaur Game proves that a great game does not need complex graphics or advanced mechanics. With simple controls, clean visuals, and increasing difficulty, it turns a moment of frustration—losing internet—into a fun and memorable experience. The running dinosaur has become a symbol of offline entertainment and remains one of the most beloved browser games of all time.

1 0

Discover the Fun: How to Play the Connections Game
by marginal.mammal.xmif＠protectsmail.net 06 Jan '26

06 Jan '26

In the ever-evolving world of online gaming, some games stand out due to their unique blend of challenge and fun. One such game is the Connections Game. It’s accessible, intriguing, and offers players a fantastic way to flex their cognitive muscles while enjoying their time. In this article, we will delve into how to play the Connections Game, some effective tips to enhance your experience, and why it’s worth a try. https://connectionsgamefree.com Gameplay The Connections Game is all about linking words in groups based on their connections. At first glance, it may seem simple, but as you dive deeper, you’ll find layers of complexity that make it both fun and engaging. Here’s a breakdown of how to play: 1. Objective: The main aim of the game is to find and connect a series of related words that belong to a specific category. Think of it as a mixed bag of words with hidden relations that you need to uncover. 2. Setup: Upon starting the game, you’ll be presented with a grid of words. These words can belong to various themes or categories—anything from animals to famous landmarks, and everything in between. 3. Finding Connections: Your job is to scan through the grid and identify groups of words that are connected. You’ll click or tap on the words to select them, and once you have selected four related words, the game will confirm that they are indeed a correct cluster. 4. Winning the Game: The more words you manage to connect, the higher your score. You can either play against the clock or take your time, depending on your preference. As you progress, the game may introduce more complex word sets or require more skilled connections. 5. Variety: Another exciting aspect of the Connections Game is that each round can be different. With numerous sets of words to choose from, every game provides a fresh experience, keeping players engaged and challenged. Tips for Playing the Connections Game Now that you have a grasp of the gameplay, let’s explore some tips to improve your skills and enhance your experience: 1. Start With Familiar Words: When you first look at the grid, focus on words that you recognize. Connecting familiar terms can give you the confidence to explore more unfamiliar words and connections later. 2. Think Categorically: As you scan through the words, try to think in categories. Is one of the words related to animals? Perhaps another word hints at food? By grouping ideas in your mind first, you can more easily spot connections. 3. Practice Makes Perfect: Like any game, the more you play the Connections Game, the better you will become. Familiarity with various types of word relationships will allow you to identify connections quicker. 4. Play With Friends: If you’re looking to add a social aspect to your gaming experience, invite friends to play alongside you. Friendly competition can heighten the enjoyment, and you can discuss strategies on how to find word connections. 5. Stay Focused: Sometimes, it’s easy to get distracted during gameplay. Make sure to focus your attention on the task at hand to enhance your performance. A clear mind can spot connections that may previously have escaped your notice. 6. Review Past Games: After finishing a game, take a look at the words you missed. Reviewing these words can help you understand the connections you previously overlooked and can boost your learning for future games. Conclusion The Connections Game offers a delightful blend of mental challenge and entertainment. It encourages players to think critically and in connections, providing an enriching way to strengthen cognitive skills. Whether you enjoy playing alone or wish to share the experience with friends, this game has something for everyone. The enjoyment lies in both the challenge and the satisfaction that comes with successfully identifying the connections among seemingly random words. So why not take a break from your usual routine and give the Connections Game a try? You might just find yourself hooked on the challenge and fun it presents. Start connecting words today! Visit Connections Game and experience the thrill firsthand. With each round, you’ll find yourself becoming more adept at spotting those crucial connections. Happy gaming!

1 0

SSL2.conf Defines Incorrect Number of Capture Channels
by GitHub issues - opened 06 Jan '26

06 Jan '26

alsa-project/alsa-ucm-conf issue #676 was opened from TheBakedPotato: The file at `ucm2/USB-Audio/SolidStateLabs/SSL2.conf` has the line ``` Define.DirectCaptureChannels 4 ``` However, I believe that should actually be ``` Define.DirectCaptureChannels 2 ``` since the SSL2 (**not** the SSL2+) only has 2 physical inputs. As well, now, with that change, a third audio "profile" appears ago for the SSL2 output device of `Direct SSL 2`. <img width="416" height="78" alt="Image" src="https://github.com/user-attachments/assets/14998079-d81d-444f-80b1-b198ad04…" /> The `[ALSA UCM error]` still appears, but now the correct "profile" is available. As well, now my music player, Amberol, is able to persist the volume change between songs. Before if I changed the volume and proceed to the next song the audio in the Amberol application would get set to max. The output in `journalctl` is still present ``` Jan 05 18:11:39 endeavour-zone wireplumber[1533]: spa.alsa: Error in ALSA UCM profile for _ucm0001.hw:S2,0 (HiFi: Mic2: source): CaptureChannels=4 > avail 2 Jan 05 18:11:39 endeavour-zone wireplumber[1533]: spa.alsa: Errors in ALSA UCM profile for card SSL 2 Jan 05 18:11:40 endeavour-zone wireplumber[1533]: spa.bluez5: BlueZ system service is not available ``` if the HiFi profile is selected. I'm assuming because the file `SSL2-HiFi.conf` needs to be updated for the correct number of hardware capture channels. Issue URL : https://github.com/alsa-project/alsa-ucm-conf/issues/676 Repository URL: https://github.com/alsa-project/alsa-ucm-conf

1 0

Fix scarlett 18i20 channel detection
by GitHub pull_request - opened 05 Jan '26

05 Jan '26

alsa-project/alsa-ucm-conf pull request #675 was opened from perexg: It's a follow-up for #660 . Request URL : https://github.com/alsa-project/alsa-ucm-conf/pull/675 Patch URL : https://github.com/alsa-project/alsa-ucm-conf/pull/675.patch Repository URL: https://github.com/alsa-project/alsa-ucm-conf

1 0

Re: [PATCH] ASoC: amd: acp: Add support for Huawei Matebook D14 (NBM-WXX9)
by Mark Brown 05 Jan '26

05 Jan '26

On Sun, Dec 28, 2025 at 04:53:18PM -0800, Andres Ballesteros Gallegos wrote: > This patch adds the DMI quirk entries for the Huawei Matebook D14 > (2020 AMD Renoir model), identified as NBM-WXX9. > diff --git a/sound/soc/amd/acp-config.c b/sound/soc/amd/acp-config.c > index 8e45f2a..1234567 100644 --- a/sound/soc/amd/acp-config.c +++ > b/sound/soc/amd/acp-config.c @@ -148,6 +148,17 @@ static const struct > config_entry config_table[] = { {} }, }, > > { > .flags = FLAG_AMD_LEGACY, This has been badly mangled by your mail client, it looks like at a minimum all tabs have been converted into spaces. If it's hard to sort your mail client it might be easier to use b4's web submission: https://b4.docs.kernel.org/en/latest/ > > Signed-off-by: ANDRÉS BALLESTEROS GALLEGOS ANDRES.BALLESTEROSGALLEGOS(a)GMAIL.COM This should come at the end of the changelog before the actual patch.

1 0

Bluetooth: Suddenly corrupted SCO packet
by GitHub issues - opened 03 Jan '26

03 Jan '26

alsa-project/alsa-ucm-conf issue #674 was opened from wwidesoft: Bluetooth headset stopped working after upgrading package alsa-ucm-conf to version 1.2.15.1-1 (Arch Linux kernel 6.18.2-zen2-1-zen 64-bit) downgrading to version 1.2.14-2 solved the issue **dmesg** kernel: Bluetooth: hci0: corrupted SCO packet kernel: Bluetooth: hci0: SCO packet for unknown connection handle 257 Issue URL : https://github.com/alsa-project/alsa-ucm-conf/issues/674 Repository URL: https://github.com/alsa-project/alsa-ucm-conf

1 0

Generic HDA UCM (HDA/HiFi-analog.conf + HiFi-mic.conf) creates phantom devices on jackless Framework Laptop 16 (ALC285, f111:000d) causing wrong PipeWire defaults
by GitHub issues - opened 03 Jan '26

03 Jan '26

alsa-project/alsa-ucm-conf issue #673 was opened from dniku: **DISCLOSURE**: the text below was written with heavy assistance from a language model. --- ### Summary On Framework Laptop 16 (AMD Ryzen AI 300 series) with `alsa.mixer_name = "Realtek ALC285"`, `alsa.components = "HDA:10ec0285,f111000d,00100002"`, the generic HDA UCM profile creates a `Headphones` playback device even though the codec exposes no headphone jack/controls. WirePlumber then selects a phantom `Headphones` sink by default (higher UCM priority than `Speaker`), requiring a manual switch to `Speaker`. Separately: UCM also exposes an HDA “Stereo Microphone” capture path (`Mic2`) which records silence; the real microphone is provided by the ACP/DMIC path. This is reproducible after wiping WirePlumber state and restarting PipeWire/WirePlumber. ### Hardware / software - Machine: Framework Laptop 16 (AMD Ryzen AI 300 series) - Codec: Realtek ALC285, subsystem id f111:000d - Distro: NixOS 25.11 - PipeWire: 1.4.9 - WirePlumber: 0.5.12 - alsa-ucm-conf: 1.2.14 ### Steps to reproduce 1. Ensure you are using the stock alsa-ucm-conf UCM2 files (no overrides). 2. Clear WP state and restart user audio services: ```sh wpctl clear-default rm -rf ~/.local/state/wireplumber systemctl --user restart wireplumber pipewire pipewire-pulse ``` 3. Observe the default sink: ```sh wpctl status -n wpctl inspect @DEFAULT_AUDIO_SINK@ ``` ### Observed behavior (before fix) Default sink becomes the phantom Headphones profile: ```sh $ wpctl status -n # ... ├─ Sinks: │ * 59. alsa_output.pci-0000_c2_00.6.HiFi__Headphones__sink [vol: 0.40] ``` ```sh $ wpctl inspect @DEFAULT_AUDIO_SINK@ # ... device.profile.name = "HiFi: Headphones: sink" * node.name = "alsa_output.pci-0000_c2_00.6.HiFi__Headphones__sink" ``` But ALSA exposes no headphone controls on that codec/card: ```sh $ amixer -c 2 scontrols Simple mixer control 'Master',0 Simple mixer control 'Speaker',0 Simple mixer control 'Bass Speaker',0 Simple mixer control 'PCM',0 $ amixer -c 2 controls numid=7,iface=CARD,name='Speaker Front Phantom Jack' numid=8,iface=CARD,name='Speaker Surround Phantom Jack' numid=6,iface=MIXER,name='Master Playback Switch' numid=5,iface=MIXER,name='Master Playback Volume' numid=13,iface=MIXER,name='PCM Playback Volume' numid=4,iface=MIXER,name='Bass Speaker Playback Switch' numid=3,iface=MIXER,name='Bass Speaker Playback Volume' numid=2,iface=MIXER,name='Speaker Playback Switch' numid=1,iface=MIXER,name='Speaker Playback Volume' numid=10,iface=PCM,name='Capture Channel Map' numid=9,iface=PCM,name='Playback Channel Map' numid=11,iface=PCM,name='Capture Channel Map',device=2 numid=12,iface=PCM,name='Capture Channel Map',index=1,device=2 ``` The codec dump also contains no “Headphone/Headset” pins: ```sh $ grep -nEi 'Headphone|Headset|Front Headphone' /proc/asound/card2/codec\#0 # (no output) ``` ### Root cause hypothesis [`ucm2/HDA/HiFi-analog.conf`](https://github.com/alsa-project/alsa-ucm-conf/blob/5d175e1f7e3df15973945a9cc15e82fa7ca0d7b6/ucm2/HDA/HiFi-analog.conf) defines `SectionDevice."Headphones"` unconditionally and assigns it `PlaybackPriority 200`, while `Speaker` is `PlaybackPriority 100`. On jackless hardware with no headphone controls/jack, this results in a “Headphones” UCM device that WirePlumber prefers. Similar problem exists in [`ucm2/HDA/HiFi-mic.conf`](https://github.com/alsa-project/alsa-ucm-conf/blob/5d175e1f7e3df15973945a9cc15e82fa7ca0d7b6/ucm2/HDA/HiFi-mic.conf) ### Proposed fix Guard creation of `SectionDevice."Headphones"` so it is only instantiated when relevant headphone controls/jack controls exist (e.g. `Headphone Playback Volume`, `Headphone Playback Switch`, or `iface=CARD,name='Headphone Jack'`). Similarly guard the HDA analog capture device on this platform when it is not functional, leaving the working ACP/DMIC capture path as the only mic. --- (end of section written with language model assistance) I have proposed a patch for Framework 16 in https://github.com/NixOS/nixos-hardware/pull/1718. Please see the diagnostics shared in that PR. I would appreciate feedback on the specific workaround that is implemented there from someone familiar with `alsa-ucm-conf`. For the output of `nix shell nixpkgs#alsa-utils -c alsa-info --no-upload --stdout` before/after applying the patch, as well as the diff between the two, please see [this gist](https://gist.github.com/dniku/d9b5095aef0e926399ebd772d0b40bd0). Issue URL : https://github.com/alsa-project/alsa-ucm-conf/issues/673 Repository URL: https://github.com/alsa-project/alsa-ucm-conf

1 0

[PATCH v11 3/4] ASoC: dt-bindings: realtek,rt5575: add support for ALC5575
by Oder Chiou 02 Jan '26

02 Jan '26

Audio codec with I2S, I2C and SPI. Signed-off-by: Oder Chiou <oder_chiou(a)realtek.com> Reviewed-by: Rob Herring (Arm) <robh(a)kernel.org> --- .../bindings/sound/realtek,rt5575.yaml | 61 +++++++++++++++++++ 1 file changed, 61 insertions(+) create mode 100644 Documentation/devicetree/bindings/sound/realtek,rt5575.yaml diff --git a/Documentation/devicetree/bindings/sound/realtek,rt5575.yaml b/Documentation/devicetree/bindings/sound/realtek,rt5575.yaml new file mode 100644 index 000000000000..981ebc39b195 --- /dev/null +++ b/Documentation/devicetree/bindings/sound/realtek,rt5575.yaml @@ -0,0 +1,61 @@ +# SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause +%YAML 1.2 +--- +$id: http://devicetree.org/schemas/sound/realtek,rt5575.yaml# +$schema: http://devicetree.org/meta-schemas/core.yaml# + +title: ALC5575 audio CODEC + +maintainers: + - Oder Chiou <oder_chiou(a)realtek.com> + +description: + The device supports both I2C and SPI. I2C is mandatory, while SPI is + optional depending on the hardware configuration. SPI is used for + firmware loading if present. + +allOf: + - $ref: dai-common.yaml# + +properties: + compatible: + const: realtek,rt5575 + + reg: + maxItems: 1 + + spi-parent: + description: + Optional phandle reference to the SPI controller used for firmware + loading. The argument specifies the chip select. + $ref: /schemas/types.yaml#/definitions/phandle-array + +required: + - compatible + - reg + +unevaluatedProperties: false + +examples: + # I2C-only node + - | + i2c { + #address-cells = <1>; + #size-cells = <0>; + codec@57 { + compatible = "realtek,rt5575"; + reg = <0x57>; + }; + }; + + # I2C + optional SPI node + - | + i2c { + #address-cells = <1>; + #size-cells = <0>; + codec@57 { + compatible = "realtek,rt5575"; + reg = <0x57>; + spi-parent = <&spi0 0>; /* chip-select 0 */ + }; + }; -- 2.52.0

2 3

Remove outdated DisableSequence elements
by GitHub pull_request - opened 02 Jan '26

02 Jan '26

alsa-project/alsa-ucm-conf pull request #671 was opened from mstrozek: cs42l43's 'Headset Microphone' and 'Microphone' devices were both used to control mic mute LED in the past, but this was changed [1] to only allow the built-in microphones to control the LED. Thus clean up the DisableSequences to remove the switching off that is no longer needed. Also, cs42l45 had those Sequences copied over from cs42l43, so remove them here as well. [1]: https://github.com/alsa-project/alsa-ucm-conf/blob/master/ucm2/common/ctl/l… Request URL : https://github.com/alsa-project/alsa-ucm-conf/pull/671 Patch URL : https://github.com/alsa-project/alsa-ucm-conf/pull/671.patch Repository URL: https://github.com/alsa-project/alsa-ucm-conf

1 0

ucm2: Qualcomm: disable broken companders and low power modes (fix #595)
by GitHub pull_request - opened 02 Jan '26

02 Jan '26

alsa-project/alsa-ucm-conf pull request #670 was opened from valpackett: It's 2026. Let's finally land the fixes for #595 maybe? :) // Not (yet?) tested on wcd934x, wcd937x and wcd939x.. but let's see if we can get any testers with different devices to show up.. Request URL : https://github.com/alsa-project/alsa-ucm-conf/pull/670 Patch URL : https://github.com/alsa-project/alsa-ucm-conf/pull/670.patch Repository URL: https://github.com/alsa-project/alsa-ucm-conf

1 0