olleb3 / csipsimple

Automatically exported from code.google.com/p/csipsimple
0 stars 0 forks source link

Samsung Galaxy S (i9000) audio problem on version 0.00-12-24 #178

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
Samsung Galaxy S (PBXes.org in Sip2Sip A/C)
Nexus One (PBXes.org in Sip2Sip A/C)
Two different GSM providers

Samsung Galaxy S heard the voice sometimes high and sometimes low from Nexus 
One but the content can be heard.  

On the other hand, Nexus could not heard the content clearly from the Samsung 
Galaxy S and was feeling the other side was murmuring.

Original issue reported on code.google.com by runner...@gmail.com on 28 Aug 2010 at 5:21

GoogleCodeExporter commented 9 years ago
I would say that it is a good news since a few days ago was simply not working 
on galaxy s. 
I'm pretty interested in the codec in use (use the little i on the in call 
screen)
If you can also say me the audio frequency set on each device. It s 8khz by 
default but some tests shows that sometimes 16khz is better.
You can also try to tune micro and speaker amplification on galaxy s. But that 
would be just a work around. Actually I'm not able to directly test on a galaxy 
s and as manufacturers audio implementation varies a lot from one to another, i 
can't really ensure the compatibility for each device but I hope that many 
tests will help us. Besides there is still a lot of things I'm discovering each 
day on audio API.

Original comment by r3gis...@gmail.com on 29 Aug 2010 at 12:09

GoogleCodeExporter commented 9 years ago
The clock rate at the Samsung Galaxy S and Nexus One are set to 16khz, Echo 
cancellation is enabled and voice audio detection is enabled.

Nexus One communicates with Samsung Galaxy S on 0.00-12-24 :

(1) on Samsung Galaxy S, hear a very low volume at the beginning and then the 
high volume.  The conversation will be in low and high volume by turns.  The 
content can be heard.

(2) on Nexus One, hear like someone talking under water.  The content cannot be 
heard.

I think I can conduct the test on Samsung Galaxy S in the future as my friend 
has one and he is willing to test with me.  :-)

Original comment by runner...@gmail.com on 29 Aug 2010 at 8:16

GoogleCodeExporter commented 9 years ago
Ok. 
Seems that I have still issues with ALSA implementation. But sounds better :)

I would be really interested in logs from the galaxy S.

See on the wiki : HowToCollectLogs section for a tutorial about how you can 
grab logs and send it to me.

Original comment by r3gis...@gmail.com on 30 Aug 2010 at 8:02

GoogleCodeExporter commented 9 years ago
I cannot promise as my friend does not know much about Android and computer.

By the way, how to collect the log with the apps mentioned at HowToCollectLogs 
for the problem?

Original comment by runner...@gmail.com on 31 Aug 2010 at 12:27

GoogleCodeExporter commented 9 years ago
You have just to launch the app logcollector it will then propose you to send a 
mail.

Last version includes an implementation test based on sipdroid experience. Not 
sure it will improves things but worth to try

Original comment by r3gis...@gmail.com on 3 Sep 2010 at 9:05

GoogleCodeExporter commented 9 years ago

Original comment by r3gis...@gmail.com on 3 Sep 2010 at 9:09