Sound problems riotboard Android

Hi Matthias,

   I've got the same situation here, standard Android install out of the box:

1. HDMI cable into monitor - no sound output from monitor on anything

2. Headphones / amp connected into headphone socket - no sound output.

So, on my phone (HTC Desire HD) the audio obviously works ok using the headphone jack. I haven't checked my image version yet. Anyone with info on Android audio jack / HDMI and switching between them would be helpful. I think another post on here said it wasn't possible to switch between HDMI and audio jack? If that's so, I'm not going to use Android as I'd like to develop some media apps so switching / using the onboard codec is rather essential...

Sorry that's not a solution, I'll let you know if I get anywhere.

I just got my RIoTboard in the mail today, and have been using it for the last hour (started right after I got home from work)!

I'm having audio problems as well, but I am actually getting audio, but the audio output is off, so the singing sonds much deeper, and the temp of the music is slowed down some.

The problem is system wide - Music player, XBMC, Web Browser with Flash or HTML5.

I didn't see any android settings that would do this.

I don't have a solution to this, but wanted to confirm that this must be an inherent problem in the firmware as I get exactly the same thing- songs are about 30% low in pitch, and tempo similarly too slow. I am guessing that the sound/ codec drivers "think" they are operating with a clock rate that is about 30% higher than it really is.

That's a good observation.  I've been pretty busy this week and my weekend may be as well, but when I get some free time, I'm leaning towards re-flashing Android, to see if that does any good.

Well, my problem with sound is no sound rather than slow sound. This post here details my problem. Seems that sound is through the HDMI if you're using an HDMI display, and through the audio jack if you're uising LVDS. Maybe you could try and LVDS display and see if the sound still plays slow? Might point to an HDMI streaming problem in that case. It could be the main clock rate or it might be the playback / streaming rate.

To test the main clock rate you could write a short app that performs calculations at a certain / known speed. If you have a "known good" system you could compare against this and put up a toast (msg box) and check that the board is running at 900MHz maybe?

If they don't provide us with a solution, then I'm gonna club this baby seal!

lol..  can't see that convincing them to sort it though

I'll admit that I was really excited to get the board.  Connected it up, and I was really surprised at how responsive it was.  Then I tried the audio.  It was quite a letdown.  When you are using a third party unofficial build of an OS you can kind of expect this, but I guess I had higher expectations for Element14.  As for Android, I've been using my Radxa Rock and have been quite pleased. 

I've pretty much given up on Android on the RIoTboard, but as long Ubuntu/Debian works, I can still use it as test web server on my home network.

I am looking forward to the release of MinnowBoard Max.

Phillip Lineburg wrote:

 

I've pretty much given up on Android on the RIoTboard, but as long Ubuntu/Debian works, I can still use it as test web server on my home network.

I find it quite interesting that people posting here generally seem to to be heading for Linux even though it's been targetted at Android from the outset.

I am looking forward to the release of MinnowBoard Max.

Which I'm guessing will come with Angstrom.. and most people will quickly wipe it and put Debian on instead.

Which I'm guessing will come with Angstrom.. and most people will quickly wipe it and put Debian on instead

I think you are 100% right!  That's  exactly what I did after getting my BeagleBone Black, several months ago.