Thread: SIP on Kindle
View Single Post
Old 07-04-2012, 11:43 AM   #24
twobob
( ͡° ͜ʖ ͡°){ʇlnɐɟ ƃǝs}Týr
twobob ought to be getting tired of karma fortunes by now.twobob ought to be getting tired of karma fortunes by now.twobob ought to be getting tired of karma fortunes by now.twobob ought to be getting tired of karma fortunes by now.twobob ought to be getting tired of karma fortunes by now.twobob ought to be getting tired of karma fortunes by now.twobob ought to be getting tired of karma fortunes by now.twobob ought to be getting tired of karma fortunes by now.twobob ought to be getting tired of karma fortunes by now.twobob ought to be getting tired of karma fortunes by now.twobob ought to be getting tired of karma fortunes by now.
 
twobob's Avatar
 
Posts: 6,586
Karma: 6299993
Join Date: Jun 2012
Location: uti gratia usura (Yao ying da ying; Mo ying da yieng)
Device: PW-WIFI|K5-3G+WIFI| K4|K3-3G|DXG|K2| Rooted Nook Touch
The problem lies here: BLAH

EDIT: NOPE IT DOESN'T IT CAN PROBABLY WORK AS IS

'division by zero' in kernel error seems to hang the audio.
Perhaps this is the issue.

I say this because the "CLICK" you hear when initialising your audio is the same click I was hearing when trying to test:

arecord -D 'plughw' -r 8000 -f S16_LE -c 2 | aplay -D 'plughw'

this does not work initially for the reasons outlined below.

perhaps this could be addressed.


I tested pjsua again and once again the kindle side eventually died on:

Code:
--end msg--
 13:01:30.740    pjsua_app.c  Call 1 is DISCONNECTED [reason=408 (Request Timeout)]
 13:01:30.740    pjsua_app.c  
  [DISCONNCTD] To: sip:192.168.1.65
    Call time: 00h:00m:00s, 1st res in 32006 ms, conn in 0ms
    SRTP status: Not active Crypto-suite: (null)
 13:01:31.740  pjsua_media.c  Closing sound device after idle for 1 seconds
 13:01:31.740  pjsua_media.c  Closing mx35luigi:  (hw:0,0) sound playback device and mx35luigi:  (hw:0,0) sound capture device

>>>>
I know this can be prevented with flags (the closing the device) but I suspect it speaks of a deeper error.

One more thing all this set DEV=0 as opposed to -1 stuff. from my reading that is basically saying Choose Device 0 as opposed to choosing the first from a list of ANY - containing one item - device 0

I.E. pointless

Hope that helps


The vague lead on a fix:
=======================================

FROM http://elinux.org/RidgeRun_LeopardBoard_SDK_Hints

Solutions to known issues
'division by zero' in kernel error when I try to use ALSA input

This is a known issue that has been discussed on the ASOC mailing list. The problem is that the function davinci_pcm_enqueue_dma performs this operations:

data_type = prtd->params->data_type;
count = period_size / data_type;

The first time, data_type is set to zero, so we get the error Division by zero in kernel. This is the reason why the pipe arecord | aplay works after running arecord or aplay first.

Apply the Media:Asoc-davinci-pcm.patch to the kernel 2.6.29 to resolve this issue.

================================================== ======

Last edited by twobob; 07-06-2012 at 08:12 AM. Reason: added cohesive evidence, and possibly a lead to a fix
twobob is offline   Reply With Quote