|
06/19/2012, 09:03 AM
#149
Since my last post, I've been exploring pulseaudio and alsa configurations for the 2.2.4 ROM for the Veer. I've learned that the setup is very different from 2.1.2, and very closely resembles the TouchPad and Pre3. Many of the ALSA control names are the same between my Veer and my TouchPad, for example.
Yesterday, I found a file in the /sys filesystem (I lost the name now) that when 'cat' -ed, displayed the current state of each ALSA control, in real-time - whether it was on or off. So I played a file with the Music Player on the Veer, and saved off the contents of this file. Then I repeated but this time with stereo headphones connected to the Veer. Each Mixer and other ALSA device was listed, along with whether the device was on or off. The ones for mono output with just the rear speaker were on when they should have been, and the ones with the headphones connected for stereo output were on as they should have been - at least I didn't see anything obviously wrong.
I also found reference in the kernel config file for the 2.2.4 image to the WM8994 audio chip used by the Veer. I found some schematics and reference material on-line that I'll study, as many of the ALSA controls seem to be named exactly as they appear in the reference material I found.
I thought I might be able to re-configure pulseaudio on the Veer to play sound over a network connection to my TouchPad, just to see if it played in stereo or not. But webOS does not include the Pulseaudio modules necessary to do this.
Anyway, I'm starting to think there is nothing wrong at the ALSA or Pulseaudio level, and that it is a problem that is deeper, like the audio driver. Problem seems to be that the audio driver is "compiled in" with the kernel - it's not a loadable module like you would find in a desktop version of Linux. So it's not as if we can easily swap audio drivers from the 2.1.2 image.
|
|
|