krunal09 / csipsimple

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

(Galaxy S II) - Mic no longer works after upgrading to latest version. #942

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Upgraded to latest market version
2. Made a call.
3.

What is the expected output? What do you see instead?

I expect the other side to hear me.

What version of the product are you using? On what operating system?

Latest market version on Galaxy S II Android 2.3.3

Please provide any additional information below.

The app was working just fine on version 0.01-01 R615. Mic and speaker were 
working as expected. I didn't have to do anything special to get it to work. 
Since the latest upgrade, i can hear the other side but they are not able to 
hear me. I tried changing the MIC source under the Media settings - nothing 
works.
I tried to change the "audio mode for SIP calls" to "NORMAL" (as this is what 
it is set to in R615) but no luck there.
I tried to use the various routing API's - nothing works.

I had to downgrade to the previous version and it is working again.

Any help would be appreciated.

Original issue reported on code.google.com by jonathan...@gmail.com on 9 May 2011 at 11:46

GoogleCodeExporter commented 9 years ago
Thanks for reporting.

Can you try to get logs (see HowToCollectLogs wiki page). If you can try with : 
 * Use mode API : disabled
 * Use routing API : disabled
 * Audio mode for SIP calls : "NORMAL"
 * Micro source : "DEFAULT"

Logs produced with this may help me to understand what is going wrong (and if 
you can do that with 0.02-01 and with 0.01-01 would be perfect :D

Thanks in advance ;)

Original comment by r3gis...@gmail.com on 10 May 2011 at 7:52

GoogleCodeExporter commented 9 years ago
[deleted comment]
GoogleCodeExporter commented 9 years ago
OK changing BOTH audio mode to "normal" AND Micro source to "default" solved 
the problem with the latest version.
You can make it as solved however it would be great if the device will have 
these settings set by default.

Original comment by jonathan...@gmail.com on 10 May 2011 at 5:53

GoogleCodeExporter commented 9 years ago
Yes your right it should be the default for galaxy s II if it solves the 
problem.

Could you send me logs using the help collect log (no need to reproduce 
anything). It is just to get the model and device name so that I can filter 
using these settings for this device ;-) .

Just an additional question : is there the stock sip application on the galaxy 
S 2 ? I'm wondering so because the new micro source and audio mode are the one 
that the stock sip app should use (unless samsung modified it).

Original comment by r3gis...@gmail.com on 10 May 2011 at 6:24

GoogleCodeExporter commented 9 years ago
It seem that the stock SIP client is not included with the device which is a 
bit odd.

here is the info you need from the log:

Based on the GPL CSipSimple version : 0.01-01 r615
Here are important informations about Device : 
android.os.Build.BOARD : GT-I9100
android.os.Build.BRAND : samsung
android.os.Build.DEVICE : GT-I9100
android.os.Build.ID : GINGERBREAD
android.os.Build.MODEL : GT-I9100
android.os.Build.PRODUCT : GT-I9100
android.os.Build.TAGS : release-keys
android.os.Build.VERSION.INCREMENTAL : XWKDD
android.os.Build.VERSION.RELEASE : 2.3.3
android.os.Build.VERSION.SDK : 10
android.os.Build.VERSION.SDK_INT : 10

Original comment by jonathan...@gmail.com on 10 May 2011 at 6:32

GoogleCodeExporter commented 9 years ago
Ok, 
The fact the stock sip client is not there, is maybe due to the fact Samsung 
always had difficulties with audio drivers :/. 
Obviously this device seems to not support the new android audio API for this 
feature... as consequence they probably decided to postpone the feature while 
they implement things correctly in their driver ;).

Thanks a lot for logs, I'll integrate it to the tests I do at install time to 
select correct audio hacks for this device.
To be sure: I see that you are using r615(0.01-01) in logs, you confirm that 
the audio mode and the mic source fix it on 0.02-01 as well?

Original comment by r3gis...@gmail.com on 10 May 2011 at 9:26

GoogleCodeExporter commented 9 years ago
This issue was closed by revision r845.

Original comment by r3gis...@gmail.com on 10 May 2011 at 9:35

GoogleCodeExporter commented 9 years ago
The issue anew observed from the r. 865 and possibly till the latest revision 
906.
I've tested r 865, 905, 906, through installing apk.
R.  905, 906 - builded from the sources.
Result was the same in every revision : 

On the HTC Desire Android 2.2 it works fine.
On the Galaxy S II Android 2.3.3 - the other side can't hear me.

P.S. The issue also observed in the latest version from Android Market.

Original comment by oles...@gmail.com on 7 Jun 2011 at 4:44

GoogleCodeExporter commented 9 years ago
Im seeing this also - think this issue should be re-opened.

Original comment by b...@solidstategroup.com on 8 Jun 2011 at 8:03

GoogleCodeExporter commented 9 years ago
same issue with galaxy i9003 after upgrade to gb

Original comment by leplong...@gmail.com on 30 Aug 2011 at 2:16

GoogleCodeExporter commented 9 years ago
Hi, I have same problem with galaxy i9003, they can't hear me.

Original comment by jillamas...@gmail.com on 21 Dec 2011 at 10:51

GoogleCodeExporter commented 9 years ago
Could you try to play with audio troubleshooting option and tell me how it goes.
See : 
http://code.google.com/p/csipsimple/wiki/FAQ?wl=en#Audio_routing_troubleshooting

Most of the time, simply changing these option can really help and solve the 
issue. Samsung is known to do crappy things with their audio layer on their 
ROM. And each audio driver implementation has its own interpretation of what 
should be the correct settings for voice over IP :S

So mainly what you can try to change is : 
Mode for sip call (try normal)
Try also to disable/enable "Use mode api"
You can also try to play with mico source.
And you may also need to disable the software echo cancellation if the micro 
source supports hardware echo cancellation (normally it should be the case for 
in_communication source... but depending on what samsung did could affect other 
sources)

Original comment by r3gis...@gmail.com on 23 Dec 2011 at 1:22