Thank you for having put so much info !
My mixer_path.xml wasn't taking in the mixer initialisation, i replaced the
audio.primary.default.so with mine and it worked great.
Mika
--
--
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-port
Ok, I think I'm going to close this thread, as I figured out that the issue
arise from not powering the mixer device first of all. Unfortunately the
power control was last one in the list, so initialization of HAL failed all
control settings, until last one (power) was reached. I patched
audio_
Adding a few debug statements to audio_route.c, I noticed that the
"Playback Switch" is wrongly set to a value of "9", which is out of range:
V/audio_hw_primary( 75): Path: speaker, length: 3
V/audio_hw_primary( 75): 0: Playback Switch -> 9
V/audio_hw_primary( 75): 1: CODEC Power Switch
I found out that I was missing a file that is mandatory for JB,
media_codecs.xml, and after adding it mp3 and mp4 are reproduced as expected.
Now I'm debugging the hal to see why it doesn't set mixer controls. I hope I
can figure it out soon...
--
--
unsubscribe: android-porting+unsubscr...@g
Main issue (i found out) is the first one I posted above, i.e. HAL doesn't
set mixer controls as expected.
And that I can't play the .mp3 I uploaded (I will try with a few other ones
soon...).
D/MediaPlaybackService( 632): Opening for playback:
'content://media/external/audio/media/27'
V/Med
> I'd like to understand what PCM output is produced by the Android
MediaPlayer. Does it depend on the origin file being decoded (e.g. an
.mp3)?
> If it's not producing exactly what the PCM expects, I may get an error
from the player.
Stagefright media framework decodes formats such as .mp3 to
Reporting what I found so far. Hopefully someone can give a hint...
First of all, preparing some tools:
$ cd $AOSP
$ adb push ./out/target/product/emev/symbols/system/bin/tinymix
/system/bin/tinymix
$ adb push ./out/target/product/emev/symbols/system/bin/tinyplay
/system/bin/tinyplay
$ adb push
Thank you Glenn!
On Wednesday, 30 January 2013 03:14:13 UTC+1, Glenn Kasten wrote:
>
> 1. It's code in the HAL. The HAL code figures out what the use case is,
> constructs the corresponding mixer path string, then uses mixer_paths.xml
> to apply the right settings corresponding to that path.
> S
1. It's code in the HAL. The HAL code figures out what the use case is,
constructs the corresponding mixer path string, then uses mixer_paths.xml
to apply the right settings corresponding to that path.
See also audio_policy.conf, but it's not directly related to this.
2. I'm not aware of such a
I think I'm starting to figuring out what to fix. My ALC5621 kernel driver
includes these control definitions:
static struct snd_kcontrol_new emxx_codec_controls[] = {
EMXX_CODEC_INTEGER("DAC Volume", 0, MIXER_VOL_DAC),
EMXX_CODEC_INTEGER("Headphone Volume", 0, MIXER_VOL_HP),
EMXX_COD
Hi Glenn, thanks a lot for answering.
I hope you don't mind if I ask you to guide me through these steps. I have
both the kernel driver code, the datasheet and device schematics, so I have
all's required to complete this... I think. Except experience :)
For example, I've posted the device cont
Usually you can find the names of the mixer controls from the kernel device
driver implementation.
For example, for grouper which you're using as a model, I did this search
on the kernel source code:
cd kernel
grep -r 'DAC IF1 SWITCH' sound/
sound/soc/codecs/rt5640.c: SOC_ENUM("DAC IF1 SWITCH",
The Audio chipet is a Realtek ALC 5621 and this is what I can find in my
kernel driver:
static const char *in_sw_control_texts[] = {
"OFF", "MIC_normal", "MIC_ringtone", "MIC_incall", "Headset_normal",
"Headset_ringtone", "Headset_incall"
};
static const char *fs_sw_control_texts[] = {
I'm now pretty sure I made a mistake when I thought I solved: I simply used
a different Android file system (of which I don't have source... of
course).
So I really need some guidance here?
Someone who could help me in fixing my tinyalsa implementation?
What should I check first?
How should I
...Well, I'm not really sure I've solved... I probably simply used the
deafult ausio library in one of my builds. Possibile? After using the
latest build I can't have any sound out of my device.
I'm a bit confused now. Here's something I've collected, after my latest
build:
$ adb logcat | gre
Ok. I think I solved. Thanks again for the suggestions!
I just compiled the audio/ as is (adapting only my .mk files), and it goes
just fine on my device:
https://github.com/Renesas-EMEV2/Renesas-device_emev/commit/70ca2d4f00c58374982a78ea86a2997fe7b15200
I thought I had to change mixer control na
Hi Glenn,
I'm back on this after some time.. Thanks for the useful suggestion, to
start from one such examples. I think tinyalsa it's much easier than going
for the full ALSA-lib integration.
After studying a bit the device/asus/grouper/audio implemenation, I adapted
this to make it boot on my
I am not familiar with the Renesas code you mention,
so this will be a generic answer and may not answer your specific question
...
I recommend looking at external/tinyalsa and a few of the recent audio HAL
implementations in JB that use tinyalsa, such as device/samsung/tuna/audio
and device/asus
Forgot to link my project's discussion board:
https://groups.google.com/forum/?fromgroups=#!forum/renesas-emev-osp
On Thursday, 8 November 2012 14:42:21 UTC+1, ffxx68 wrote:
>
> Hi
>
> I'm trying to port a ICS implementation of ALSA audio to JB, or a tablet
> device, under this project:
>
> Mainl
19 matches
Mail list logo
