Dolphin, the GameCube and Wii emulator - Forums

...never mind, i probably misunderstood your posts. I took this issue to the LinuxonAndroid forum.

One more thing: which Dolphin video backend is used in this setup? Even the software rendering backend requires basic OpenGL support, which the Xvnc server doesn't provide?

It uses the mesa software rasterizer, so it still works over VNC.

Right. Setting USE_GLES is the key here.

(03-24-2013, 10:08 PM)bl0 Wrote: [ -> ]I know LinuxonAndroid isn't your project. The device on which you're working is your device. It's certainly possible to take steps to find out why sound isn't working.
I took one Android device. (It's actually a Windows Mobile device to which Android has been ported unofficially.) I set up a minimal chroot with only glibc, busybox and alsa.

Code:

# cat /proc/asound/cards
0 [msmaudio ]: MSM-CARD - msm-audio
msm-audio (MSM-CARD)
# ls -l /dev/snd
crw-rw---- 1 1000 1005 116, 0 Mar 23 11:07 controlC0
crw-rw---- 1 1000 1005 116, 24 Mar 23 11:07 pcmC0D0c
crw-rw---- 1 1000 1005 116, 16 Mar 23 11:07 pcmC0D0p
crw-rw---- 1 1000 1005 116, 33 Mar 23 11:07 timer
# mount --bind /dev /tmp/chroot/dev
# chroot /tmp/chroot /bin/sh

BusyBox v1.17.1 (Debian 1:1.17.1-8) built-in shell (ash)
Enter 'help' for a list of built-in commands.

/ # aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: msmaudio [msm-audio], device 0: ASOC CODEC_DAI-0 []
Subdevices: 1/1
Subdevice #0: subdevice #0
/ # aplay -f cd sample.wav
Playing WAVE 'sample.wav' : Signed 16 bit Little Endian, Rate 44100 Hz, Stereo

Sound is played successfully. If you use LinuxonAndroid and it sets up a chroot, it should be similar. I don't see any problems here. Maybe this hardware configuration is an exception rather than the norm?

I'm sorry,my English is not good.
I follow your practice,do something, but I can't play sound, can you tell me your phone model, Linux on android, which you use? Debian or Ubuntu, or backtrack from where to download? What do you do to configure the Linux ALSA?

My phone is HTC EVO 4G LTE, EVO4G Android sound driver is ALSA 1.0.24
Ubuntu 12.04,13.04 (ALSA driver 1.0.25), Debian's V4 (ALSA driver 1.0.16), backtrack 10 (ALSA driver 1.0.22)
/ dev bind mount into Linux, but are not voice.

phone to play music when I can use 'alsamixer' setting controls phone'volumn under linux, up or down, it looks like the Linux driver is correct.
what I need to do other system configuration in Linux?
The loaded modules only wlan


In the following code: 'alsactl restore' are set the MSM8960-SND card .Before I set some parameters.

These are all controllers default parameters

I was being a little ignorant in my posts. The output you posted is evidence that it's not going to be easy to get alsa sound on some android devices. Ok, let's start with this:

Quote:

Code:

root@localhost:~# aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: msm8960sndcard [msm8960-snd-card], device 0: MultiMedia1 null-codec-dai-0 []
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: msm8960sndcard [msm8960-snd-card], device 1: MultiMedia2 null-codec-dai-1 []
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: msm8960sndcard [msm8960-snd-card], device 2: CS-Voice null-codec-dai-2 []
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: msm8960sndcard [msm8960-snd-card], device 3: VoIP null-codec-dai-3 []
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: msm8960sndcard [msm8960-snd-card], device 4: LPA null-codec-dai-4 []
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: msm8960sndcard [msm8960-snd-card], device 5: SLIMBUS_0 Hostless null-codec-dai-5 []
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: msm8960sndcard [msm8960-snd-card], device 6: INT_FM Hostless null-codec-dai-6 []
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: msm8960sndcard [msm8960-snd-card], device 7: AFE-PROXY RX msm-stub-rx-7 []
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: msm8960sndcard [msm8960-snd-card], device 9: COMPR null-codec-dai-9 []
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: msm8960sndcard [msm8960-snd-card], device 10: Slimbus Playback tabla_rx1-10 []
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: msm8960sndcard [msm8960-snd-card], device 12: Internal BT-SCO Playback msm-stub-rx-12 []
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: msm8960sndcard [msm8960-snd-card], device 14: Internal FM Playback msm-stub-rx-14 []
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: msm8960sndcard [msm8960-snd-card], device 16: HDMI Playback msm-stub-rx-16 []
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: msm8960sndcard [msm8960-snd-card], device 17: AFE Playback msm-stub-rx-17 []
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: msm8960sndcard [msm8960-snd-card], device 19: AUX PCM Playback msm-stub-rx-19 []
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: msm8960sndcard [msm8960-snd-card], device 21: Voice Farend Playback msm-stub-rx-21 []
Subdevices: 1/1
Subdevice #0: subdevice #0

Quite a number of sound devices. Can you post the output of 'cat /proc/asound/card*/*/*/hw_params' (or better 'grep ^ /proc/asound/card*/*/*/hw_params' as it displays the filenames), then start an android audio player in the background and repeat? This should tell you which sound device is the one to use.

Quote:In the following code: 'alsactl restore' are set the MSM8960-SND card .Before I set some parameters.

What are the parameters you set before? According to 'man alsactl', with recent alsa versions, if there is no saved state, 'alsactl restore' should be equivalent to 'alsactl init' so perhaps this is what made a difference?

Quote:

Code:

root@localhost:~/home# aplay send.wav
Playing WAVE 'send.wav' : Signed 16 bit Little Endian, Rate 44100 Hz, Stereo
aplay: pcm_write:1540: write error: Input/output error

Does the -M option to aplay make any difference? From man aplay:
"-M, --mmap Use memory-mapped (mmap) I/O mode for the audio stream. If this option is not set, the read/write I/O mode will be used."
Can you try with '-D hw' too?

Quote:I follow your practice,do something, but I can not play a sound, can you tell me your phone model, Linux on android, which you use? Debian or Ubuntu, or backtrack from where to download? What do you do to configure the Linux ALSA?

My phone is HTC EVO 4G LTE, EVO4G Android sound driver is ALSA 1.0.24
Ubuntu 12.04,13.04 (ALSA driver 1.0.25), Debian's V4 (ALSA driver 1.0.16), backtrack 10 (ALSA driver 1.0.22)
/ dev bind mount into Linux, but are not voice.

The phone I used is HTC Touch Pro. (It's from 2008, not a native Android device. I have XDAndroid on it.) Later I tried on a cheap Android tablet (the name on the box is "goclever tab l101") with results similar to HTC Touch Pro (except I had to chmod -x and kill one android process because it was keeping the sound device busy). I don't readily have access to other Android devices.
I did not use a full distribution. I unpacked a few binary arm packages from debian, just enough to chroot into and test alsa. (If you want to replicate this, I can point you to download links for these packages, but it's unlikely to help with your problem.)
You have tested with alsa versions both older and newer than alsa in your kernel (did you check /proc/asound/version to verify this version number?) so I don't think compatibility is the problem. Even if you try a version with the exact same number, you can't be sure that the codebases match. The kernel for your device could have been modified beyond recognition.

We've moved away from the topic of Dolphin on Android, is it ok that we're posting here or should we switch to the off-topic forum section?

Edit: This discussion has been going on in private.

Thank you very much, according with your guidance, it sound ok，
phone play music at the same time 'alasctl store' command to save the parameters,
turn off the music, and then 'alasctl restore' parameter, I can play the sound,

now is only headphone sound, speaker is no sound, your speaker can sound?

Hello friends,
I registered in this forum just to ask:

there is a minimal possibility that Dolphin can reach some games run 100% on Xperia Play???
(it only has a single-core processor 1GHz & 512 ram) and asks the emulator android 4.0 .. (but thanks to XDA we have (Jellybean 4.1.2) completely stable)
I hope I can answer this simple question ..
Sorry if this question bothers ..
Greetings, and thanks in advance ..

No chance at all

i'm another xperia play owner .

as you may know , NDS emulator has been released and workd like charm even on my singe core phone ...

i love mario series games more than my life

i just will change my phone the first day that i can play mario series sable( specially paper mario ) on a quad core phone ( xperia Z ultra ) .

anyone knows how much does it take time to be stable on our android phones ?