Powered by

# Sound Issues

When running our builds on real hardware, sometimes the sound is not detected properly. We can troubleshoot this issue a number of ways.

Option 1

The initial way we should troubleshoot is to first see if it is a volume issue. Typically, you can install an app like Goodev Volume Booster, and that will add gain to the main sound channels.

  1. Open Play Store
  2. Install "Volume Booster GOODEV" or any other sound booster app
  3. Open the AudioFX app if installed and turn it off
  4. Go to Home, open the Volume Boost app and boost it to 15%-25% and test

This will solve most sound issues.

Option 2

Using the alt-f1/f7 console from Android 9 or a terminal app from Android 11/12, we can run:

$ lsmod

This will list all the devices that have been detected on the device. Search the output for anything sound related. If you see multiple audio or sound drivers loaded, refer to Option 1 to boost gain, otherwise you can reload the modules:

rmmod snd_hda_codec_hdmi
modprobe snd_hda_codec_hdmi

Option 3

There is also tools added to Gearlock Recovery that can help with most sound issues. Read the details about that here.

Option 4 - (Advanced)

For some users, the simple sound fixes don't work. This means we will need to go into experimental mode on the issue. This method was provided by cjeu100 From XDA-Developers threads.

Start by using the alt-f1 console (use alt-f7 to get back) or the Terminal app (may require you to run Remount System as Read/Write first) and type following commands:

su
cat /proc/asound/cards

0 [HDMI ]: HDA-Intel - HDA Intel HDMI HDA Intel HDMI at 0xb0610000 irq 46 1 [PCH ]: HDA-Intel - HDA Intel PCH HDA Intel PCH at 0xb0614000 irq 44

ls -l /dev/snd

now you see your sound devices

In this example, the we picked the top one, (pcmC0D7). If that doesn't work, repeat these steps and choose a different card.

On Bliss OS builds < 15.8.8:

setprop hal.audio.out pcmC0D7p
pkill audioserver

This will restart the audio server and hopefully result in sound working with the right output. Use alt-f7 to get back to the Android UI and test.

Option 5 - snd-intel-dspcfg.dsp_driver

On Bliss OS builds <= 15.8.8, we have different drivers we can try (1/2). We use the snd-intel-dspcfg.dsp_driver=# cmdline option to switch between those drivers on boot:

snd-intel-dspcfg.dsp_driver=1