Android audio use fake device to emulate driver so all the calls to
the actual driver should be blocked.So return all the calls to from
AudioHardwareInterface file.
Emulator also works on the same concept.
There should be a better way to stop audio by changing some make
files.
On Feb 16, 6:07
What is the problem you are facing from your description it is
unclear??
On Feb 14, 5:09 pm, Murali K. Vemuri
vemuri.muralikris...@gmail.com wrote:
Hello group,
I further verified with OMAP 3530 EVM Board that these proc entries are
indeed correct.
The problem is yet un-solved, and any
Hello Murali,
Generally XRUN happens due to improper buffer size settings.Try
changing your buffer size.
You can use aplay utility to check different buffer sizes and for
recording you can use arecord.
Still if it doesn't work then it would be better if you can show us
the driver logs.Enable
I think audioflinger needs to be changed a lot for this to be
achieved.
Android is no longer restricted to mobiles only as it is being used in
many other areas like Notebooks.
I think android team would be already working on your question.So we
can expect the solution for
your problem soon as a
what exactly the root cause? I want to check
whether it's the same problem with mine.
--thanks
wxc200
On Sep 13, 8:21 am, ani anish198519851...@gmail.com wrote:
check from where are these logs coming unable to attach.
I think your kernel has not created properly your device files
check from where are these logs coming unable to attach.
I think your kernel has not created properly your device files for
mixers.
In case it has not then you need to first fix that or you can get help
from alsa mailing list(Very good group and they reply most of the time
if your question is
You should better ask this in alsa mailing list.
As it is not android but ALSA specific.
--
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting
AudioFlinger::ThreadBase::TrackBase::TrackBase()
In this function i think we create shared memory between mediaserver
and audioflinger.
This function exists in AudioFlinger.cpp file.
--
unsubscribe: android-porting+unsubscr...@googlegroups.com
website:
Thanks for sharing this site.
There are many question unanswered like the one below in the site
mentioned:
AudioFlinger and mediaServer use shared memory (called Heap in
android) to IPC, general idea was raw data in Heap
Where is this part of code??
--
unsubscribe:
/system/media/audio/ringtones check here...if your files are present
or not.
If present then it should be listed in your settings as well.
--
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting
To unsubscribe, reply using remove me
/system/media/audio/ringtones check here...if your files are present
or not.
If present then it should be listed in your settings as well.
--
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting
try with this alsa_aplay -D hw:0,0 Dil_Vil.wav some.wav
--
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting
To unsubscribe from this group, send email to
android-porting+unsubscribegooglegroups.com or reply to this email with the
I think your media player which you mentioned was playing some music
will not be able to play if alsa_aplay itself is not working.
Because your device itself is not opening.
Is your media player using some other driver other than alsa
--
unsubscribe:
It would be better if you ask alsa mailing list these questions.
# alsa_amixer -c 0
# alsa_aplay -l
shows my devices info correctly.
Check whether your device nodes are getting created or not.
It should be
/proc/asound/card0/pcm0P -Playback device
/proc/asound/card0/pcm0C -Capture device
If
libasound_module_rate_speexrate.so is an alsa plugin which needs to be
downloaded.
aplay runs because it works directly above your driver layer i.e. your
driver supports 8k playing.
Whereas libasound_module_rate_speexrate.so is loaded by the platform
code.
Try downloading this file.
--
I guess your asound.conf file doesn't match your drivers.
Please google for this file and details.
--
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting
To unsubscribe from this group, send email to
There are lot of buffer underrun issues because of no drain function
in AudioHardwareAlsa.cpp file.
Is it done deliberately??
--
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting
If you are talking about headset button which we generally use to
recieve the call then you can send one of your own defined scancode to
platform and then platform will convert that scancode to keycode.You
should add your defined keys in keycodelabels.h and some other
files.For adding your keys to
OEM's define their own keycode for this key and if you want to know
the keycode of this key then just put some prints in your onkeyup or
onkeydown of your foreground application and check it.
--
unsubscribe: android-porting+unsubscr...@googlegroups.com
website:
Hi Sean,
I have a question regarding mixers in android.
Lets say my mixer control name is MIC RECORDING
Then how below line changes so that i can use that mixer for setting
the right values.Like if i want to enable the mic using above control.
Then in alsamixer.cpp how the below line changes.
Hi Sean et al,
This api getCaptureMuteState is failing the google CTS test for
Android ECLAIR 2.1 platform.
Reason:
It is returning INVALID_OPERATION(large negative value,how ???)
Two successive prints of this value results in two different
values.How???
Though setCaptureMuteState is also
I also faced this issue because my apk had system permission.I think
it is difficult to find out a workaround for this as the permission
((probably in init.rc) ) is not granted for system user to access
sdcard.
Only workaround would be to downgrade yourself to normal user set in
manifest file.
ani, I don't think there is an external/libaudio in AOSP.
Where do you get the tree?
Thanks Chih you are right.
This external/libaudio is there in my local setup however David if you
want to see the audiohardwarealsa and related files you can use this
url.
http://android.git.kernel.org/?p
Hi Sean et al,
I have some suggestions in the form of code changes which i would like
to merge with the main line alsa files.Please guide me about this.
Regards,
anish
--
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting
You need to comment the mediaserver server which is using your
device.Comment it in init.rc file and then try.
--
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting
No, dmix requires posix shared memory and Android doesn't support it.
This (http://gitorious.org/android-on-freerunner/platform_bionic/
commit/f7fc4a3c25d71017f8327563d182396e35a259cd) is the change which
we need to do to enable shared memory in android and then we need to
back port some changes
Answer From Sean McNeiL:
The simple answer to your questions below is that POSIX shared memory
will not be supported by Google, so this is all moot. The commit
mentioned below will most likely never be accepted by Google. You can
use the dmixer support if you like, but you'll have to do a number
this facility of alsa not exploited or given the OEM's some way to
use their own code if they have better re-sampler and mixer codes
available through ALSA?
Best Regards,
ani
--
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting
Just use AudioHadwareAlsa.cpp file for doing that.This file directly
interacts with ALSA lib to write data to the below hardware,but in
this case you need to take care of synchronization issues which can
come up and many other issues which you will come across.Because in
this case audioflinger
This is how it looks as of now. Can anyone tell me what are hooks ?
Let me give you an example of hooks.
Lets say you have asound.conf file as shown below:
pcm.AndroidPlayback_Speaker {
type hooks
slave.pcm {
type hw
card omap3beagle
device 0
}
hooks.0 {
30 matches
Mail list logo
