Roon interface volume plus and minus buttons (+/-) sometimes get stuck [Fixed with Build 1364/1365)

Roon Server Machine

Pink Faun 2.16x, 32GB Ram, Euphony OS

Networking Gear & Setup Details

Ethernet, no WiFi apart from the mobile/UI which uses WiFi to talk soon core

Connected Audio Devices

CH Precision C1.2 dac/streamer/Pre

Number of Tracks in Library

49,000

Description of Issue

When using the Google pixel 5a, with Room UI/App on the phone (latest Android 14 and latest build 1357 on the phone and server). When I go to increase the volume on Roon App, it increases the volume, but some times it keeps increasing the volume - even after I have stopped increasing the volume. It automatically makes the CH C1.2 go to maximum volume. This happens reasonable regularly. The only way make it work is be closing the app and restarting the app.
This started occurring about 4 months ago.

Hi everyone,

We’re aware of the ongoing issue/regression and the ticket is in the queue. We’ll post updates here as soon as they’re available from development. Thank you for your patience.

1 Like

This seems to have forever been a bug looking at prior times this was raised. It’s been observed in all manner of Roon controllers (I think playback device is irrelevant as it is the controller that must be restarted to stop it).

I myself have had it when using the physical volume up control on a Bluesound Node 2i a year ago and a phone running Android 13 just now (Motorola G54 with same Roon build as you). I set a limit to stop this bug from blowing up my speakers and ears.

I would guess something is causing the ā€˜volume up’ request to be resent infinitely. How often does your app get into this state? Does the volume tick up one notch at a time (like 1/sec)?

If you see this state occur more often in a particular environment like Android 14, maybe its likelihood is influenced by a change in some underlying stack. It could also be related to the new Roon build since we have that in common.

I’m thinking some kind of request retry logic could be responsible. Whatever the cause is, it’d be nice to finally get this fixed.

1 Like

This is unacceptable as I’ve probably ruined my ears and 2 sets of speakers. It has happened 2-3 times a month and about every time I’m setting up a new device. Can we get refunds of our lifetime subscriptions?

2 Likes

I was asked to provide examples. 13.55 Christmas day, adjusting volume whilst nothing was playing - BBC radio six showing in play window, but thankfully in stopped state.

It happens at least once a month, is clearly an issue with the android client software and not related to the content being played or the server. This refers to volume bar increasing by itself, not jumping to 100, ive never had that and thats even worse…

This is show stopping bug that has potential to seriously damage users equipment, has been regularly reported and is clearly very serious.
Like others here, I find it extremely worrying that so little resource is being used to fix this and the entire system seems designed to ā€˜sweep it under the carpet’ like all the previous reports of this bug have been.
This is not the service level I would expect for such an expensive ā€˜premium’ piece of software.

1 Like

Well done mate. Thanks from all of us suffering this bug, youve captured it perfectly.

Has there been a fix applied to the latest build? I was getting this issue daily and now it’s been at least a week since I last ran into the bug.

Hi @Exile72
just testet: not fixed in build #1357

1 Like

Hi everyone,

Thank you to those of you who have provided timestamps. The Roon team has reproduced this bug in-house, isolated the underlying cause in the UI, and development is working on a fix.

For affected users, the triggering mechanism involves a vertical swiping gesture while clicking and holding near the Volume Up (+) button. The liminal pixel space to the right of the Volume Up (+) button is particularly sensitive. Once the bug has been triggered, only restarting the Roon Remote (no need to restart RoonServer) will relieve symptoms and allow you to regain control of the volume. Note this bug will affect other Zones, too, until a Roon Remote restart; it’s UI-related and independent of your endpoints and signal path.

If you are encountering this issue, we strongly recommend setting Volume Limits for affected Zones to protect any speakers in your audio chain. Hard setting any downstream physical attenuator will more thoroughly protect these devices for due diligence.

We will post updates on the progress of this issue here.

7 Likes

Any update to the very resilient volume bug?

I too have been suffering this bug for over a year. Roon seems extremely slow at addressing it. I would have expected better.

1 Like

I have to agree. I would consider this a very large bug issue with the software and yet Roon has only recently addressed the issue and two months later still does not have a solution.

Hi everyone,

There is a fix for this issue released in #early-access
. If you are eager to resolve symptoms, you can follow these instructions to move your RoonServer and Remotes to Early Access. This fix will merge into the public build of Roon with the next release.

Hi everyone,

The fix for this issue is now on the public build of Roon. Please download the latest release and post here if the issue still recurs.

Precisely, we fixed an issue in which a vertical swiping gesture in the pixel space adjacent to the volume control buttons on Roon Remote would trigger repeating volume increase/decrease requests until RoonServer restarted.

Thank you again for your patience.

4 Likes

Great news for those of us that run amps which technically can burn through our speakers!

3 Likes

This topic was automatically closed after 2 days. New replies are no longer allowed.