Audio Stops Working

[Oknbji]

Knulli build version

40-dev-d3b520f949

Your architecture

RG35xx 2024

Issue description

Since updating to new build option my audio stops working.

Detailed reproduction steps

Installed new build onto my sd card plugged it in and audio worked fine until I turned it on for the another time to play. Noticed that when pressing volume buttons the bar does not show up when issue is present.

Details of any attempts to fix this yourself

I figured out if I format the internal storage and restart the device the audio works until the next time I boot it up and then I have to repeat the format

Details of any modifications you have made to Knulli.

I have no modified anything

Logs and data

No response

[HoroTW]

I don't have the same device as you and am not able to reproduce the issue...
Did you try to do a clean reflash of the whole knulli image?

[Oknbji]

I just tried reflashing it and I’m still getting the same problem

[HoroTW]

Sorry to hear that, maybe someone else with the same device can chime in and tell if they have had similar experiences.
You could try connecting via SSH and sending the output of dmesg, maybe we can see what is going on there.

[gas-was-taken]

Hello!
I have the same device and I'm having the exact same issue. Sound is working during the first boot, but after restarting there isn't any way to get sound.
Hope this can be fixed, I will look a bit into dmesg

Edit: I got it to work!
There is 4 different audio profiles. 2 of them are working: AHUBHDMIDPRO AUDIO and AUDIOCODECSTEREO OUTPUT. But the other 2 simply don't work: AHUBHDMISTEREO OUTPUT and AUDIOCODECPRO AUDIO.
I think the AUTO behavior is broken and select an audio profile that is not working :)

[HoroTW]

just to clarify:
So you can get it to work through the UI by selecting these audio profiles?
Do these also not work on the first boot or do they stop working? (can you explicitly select them and test on first boot?)

[Oknbji]

For me it the audio was functional on first boot but when I switch the storage to my second sd card and reboot it doesn’t work. Just to see I put both cards in my rg35xxh(it’s the os for the plus/2024model on the cards) and it functions fine, I have a hunch it might be an issue specific to the rg35xx 2024 model unless it’s also happening on the plus as well.

[gas-was-taken]

just to clarify: So you can get it to work through the UI by selecting these audio profiles? Do these also not work on the first boot or do they stop working? (can you explicitly select them and test on first boot?)

Yes, I can get them working by selecting them through the UI in the settings on the second and following boots. It's even persistent across reboots.

I don't know if at first boot they are working but I'm pretty sure they are. I didn't tested, that would mean reflashing an SD card, and since it's now working, I don't really see any point in doing that. But if it's really useful for you I could test?

Edit: and just to clarify, I have an RG35XX 2024 (the one with a small "+" at the back in the model name, even if it's not a plus model and if I recall correctly, the real plus model has the word "plus" in full letter at the back)

[ChrisBeWithYou]

This just happened to me while configuring my wife's RG35XX SP. I can't pinpoint when it happened but the order of operations I did was:

Change default host name, connect to WiFi (Audio Working)
Add Retro Roms (Audio Working)
Add a single PS1 game to test (can't remember if audio was working but I think so)
Add a bunch of random BIOS files to the /BIOS folder (I think it stopped working around here)

This was probably after 3 hours of on-time while plugged into a charger. I also can't get the share portion to show up anymore in my network and can't access the SD card. The time on the clock never updated either when connecting to the network. I've tried hard power cycle, connecting to a different network (phone hotspot) and back, and toggling the WiFi on/off. Very weird. No issues on the last image I made with same version lol.

Edit: Just realized it was plugged in and charging/powered on, but only the amber charge light was lit, not the green power. When I unplugged it froze up so I hard cycled via the power button again. Audio started working on next boot up and the clock is right. Very weird! Still can't get back onto it via the network but it's a start...

[ChrisBeWithYou]

It happened again last night (brief audio drop out) when the network was disconnected and then reconnected on the unit. Also if anyone else sees this, I am able to access the share folder on windows explorer via typing in the IP address of the device into the search bar "\192.168.1.xxx"

[Techbane]

I'm trying to set up the 35XX 2024 of a friend and am consistently running into this issue. First bootup after a fresh flash is fine; then I format the SD2 to EXT4, restart, and audio is completely and permanently broken systemwide. Doesn't necessarily seem to have anything to do with using the SD2, since I don't even get a chance to select it as the storage device before everything breaks.

Sadly the above fix of trying different Audio Profiles has no effect for me.

[Techbane]

Experimenting further now that I have a little time. Using the Format A Disk function on the device itself to tell it to format the internal memory as EXT4, then rebooting, also works to fix the audio, I'm assuming since it's effectively the same as doing a first-time boot again. But, like clockwork, whether I choose reboot, shutdown, or just hold the power button for a couple seconds, every subsequent launch no longer has sound.

It's perhaps noteworthy that on subsequent launches, it also hangs for a very long time (~30 seconds) at the end of the load bar, when it says COLLECTIONS on the screen.

Downgrading to the 20240530 release seems to fix it.

[ExpiredPepsi]

I had this as well on a RG35XX SP that I just flashed yesterday, everything worked fine until I copied over BIOS files and then the sound stopped working.

I removed all BIOS files, rebooted, and the sound started working again. Copied over the ones necessary for the systems I was running games for and everything continued to work like normal.

Seems like if you're using a BIOS pack (like the Retroarch one on archive.org) there's a file that Knulli just doesn't play well with and it kills the sound. Not sure which one, but will be happy to recreate the issue and send over log data if needed.

[matiasba]

Just to add some info tho this issue. For me only the very first boot after flashing a new SD card has audio working. Every time that I restart after that the audio is dead and the volume buttons do nothing. I also found a very strange workaround on the discord channel, if I spam the B button during start up the audio is fixed and the whole start up is much faster. I found that restarting the /etc/init.d/S27audioconfig fixes the audio but it dosent show the audio indicator when pressing the volume buttons.
I tried to run the dmseg and this is the output:

[  259.147870] rcq unprotect not at safe region!
[  259.448174] [DISP] disp_mgr_protect_reg_for_rcq,line:1002:
[  259.448175] rcq unprotect not at safe region!
[  262.317699] [DISP] disp_mgr_protect_reg_for_rcq,line:1002:
[  262.317700] rcq unprotect not at safe region!
[  262.618005] [DISP] disp_mgr_protect_reg_for_rcq,line:1002:
[  262.618006] rcq unprotect not at safe region!
[  263.085138] [DISP] disp_mgr_protect_reg_for_rcq,line:1002:
[  263.085139] rcq unprotect not at safe region!
[  263.385457] [DISP] disp_mgr_protect_reg_for_rcq,line:1002:
[  263.385458] rcq unprotect not at safe region!
[  263.986052] [DISP] disp_mgr_protect_reg_for_rcq,line:1002:
[  263.986053] rcq unprotect not at safe region!
[  264.069429] [DISP] disp_mgr_protect_reg_for_rcq,line:1002:
[  264.069430] rcq unprotect not at safe region!
[  264.453185] [DISP] disp_mgr_protect_reg_for_rcq,line:1002:
[  264.453186] rcq unprotect not at safe region!
[  264.753483] [DISP] disp_mgr_protect_reg_for_rcq,line:1002:
[  264.753485] rcq unprotect not at safe region!
[  265.053788] [DISP] disp_mgr_protect_reg_for_rcq,line:1002:
[  265.053790] rcq unprotect not at safe region!
[  265.704579] [DISP] disp_mgr_protect_reg_for_rcq,line:1002:
[  265.704580] rcq unprotect not at safe region!
[  266.004722] [DISP] disp_mgr_protect_reg_for_rcq,line:1002:

[ben-willmore]

My experience (RG 35XX +, I believe this is the 2024 model) is similar to @matiasba. These are the steps I tried:

reflashed with 2024-07 release
sound works

shutdown system
turned on again
long pause on collections (>30 sec despite no games other than stock)
no sound

shutdown system
turned on again
mash b
no pause on collections
sound works

shutdown system
turned on again
(didn't mash b)
long pause on collections (>30 sec)
no sound

reflashed with 2024-05 release
sound works

shutdown system
turned on again
no pause on collections
sound works

(and continues to work on successive reboots, after installing games and BIOS files)

[ben-willmore]

I was able to work round this by disabling connman (network manager) as follows, using an ADB connection. It means that wifi won't work, but I don't often need that:

cd /etc/init.d
mkdir disabled
mv S08connman disabled/
batocera-save-overlay

This can be reversed with:

cd /etc/init.d/disabled
mv S08connman ../
batocera-save-overlay

[Falkonsinger]

rollback to 05 worked for me too.( 35xx 2024)

[BonciuADV]

Same device, same issue.
Changing audio output from auto to built in stereo and back fixes it.
Sometimes rebooting constantly fixes it as well.