#258 GT-I5500 : echo

[Anonymous]

Originally created by: i...@gcint.it
Originally owned by: r3gis...@gmail.com

CellPhone: Samsung GT-I5500

Connection to my 3CX PhoneServer via WiFi (local connection) and 3G,HSPDA,GPRS,... so to configure my mobile as an internal/external extension on my 3CX PhoneServer.

Testing both the two profiles an echo at remote-party can be heard. Also tryng to call an internal extension on my 3CX I experienced the same behaviour.

I tried also to change the echo queue from 200 to an higher value of 300 and 400 but with no success.

Anyway, let me say that you are doing a great job and my opinion is that your project can be figure out as one of the best sip client available on android market up today. If possible I'd like to join your project.

Paolo

What steps will reproduce the problem?

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

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

Please provide any additional information below.

[Anonymous]

Originally posted by: r3gis...@gmail.com

Is the sound outgoing from earpiece or rear-speaker and is the sound loud or quiet? Most of the time there is echo because actually outgoing sound is captured back.

However, there is maybe things I have to check with echo cancellation feature that comes from the pjsip native stack used in this project. I'm not sure it's working well and/or it's well configured.

[Anonymous]

Originally posted by: i...@gcint.it

The sound at earpiece is loud as expected. It seems that a part of the sound comes also from rear-speaker. That's could be the problem.

Thanks
Paolo

[Anonymous]

Originally posted by: i...@gcint.it

I've conducted some more tests:
- setting the speaker gain parameter to 0 (changing the default level to 0) the echo disappears;
- muting  the conversation the echo disappears;

Regards
Paolo

[Anonymous]

Originally posted by: r3gis...@gmail.com

Once again... sounds to be a great implementation from Samsung :)
I recently fix something on galaxy S (i9000), it was exactly the same problem.
You can try to download and use the version -13-02 available on the download section. *Remove the market version before installing this one*.

-13-02 fix things for samsung i9000. However you'll not be able to reduce the volume with volume key, but can be performed using Preference > media > speaker amplification (set to lower than 1).
Galaxy S owners, before I fixed the speaker issue usually set it to 0.2 to remove echo. I don't know now with my last fix what is a good value.
But if it fixes it for you too and avoid to output on rear-speaker it will significantly delete echo. Rear-speaker usually spread the sound through the whole phone, and so the micro record output.

[Anonymous]

Originally posted by: i...@gcint.it

Just to let you know that I'm already using last build available 13-02.
Setting the speaker amplification to 0.2 does not solve the issue even if echo seems to be reduced but the volume is too low for a good quality conversation. Headset does not help also.

[Anonymous]

Originally posted by: r3gis...@gmail.com

Ok, if headset doesn't help solution is probably to find elsewhere.

Did you tried another android sip application (sipdroid, linphone)? Are you experimenting same echo issues?

[Anonymous]

Originally posted by: i...@gcint.it

Yes, I tried 3CXPhone and SIPdroid both of them with same echo problem.

[Anonymous]

Originally posted by: r3gis...@gmail.com

Ok, so probably an issue with what is done by samsung on this device.
I think, it's exactly the same problem that the one present on 5700 solved by samdroid on his custom rom :
http://forum.samdroid.net/f9/sipdroid-voip-i5700-problems-983/

Could make sense, 5500 and 5700 are probably two devices based on some common hardware/ driver implementation. Solution on 5700 is to install the custom rom...But AFAIK there is no custom rom with this fix on 5500.

The only thing we can hope is that there is a workaround. You can maybe try to pickup randomly some of my builds. I did many tests on the audio routing stuff between 0.00-12-02 and 0.00-12-29.

You could for example try : -07 that is really interesting since there is an option in settings>media to choose the exact audio mode you want to use. MODE_IN_CALL, MODE_NORMAL are interesting to test usually.
-10, -19, -25 could be interesting too (the audio mode is hard coded in these versions but flow on audio setup can differ).

If you are going on an older version you'll need to uninstall the app. (Maybe between each test even if an upgrade... but I'm not sure it's necessary for an upgrade).

Summary: Samsung GT-I5500 : rear-speaker + echo
Status: Accepted

[Anonymous]

Originally posted by: i...@gcint.it

Thank you for your comments.

I think that the echo problem on samsung device could be generated by more then one single root cause. Since echo at calling party varies in terms on volume and delay I think that automatic gain control working feature (samsung microphone) could be to investigate more in detail.

Hope this could help
Regards
Paolo

[Anonymous]

Originally posted by: r3gis...@gmail.com

I just tag the issue to precise that's a defect from the manufacturer driver.

In this case the only thing we could do is wait for samsung to fix the issue or wait for a custom ROM (such as samdroid one to fix it).

However I'll try to see if there is nothing I can do improving the echo canceller but as here the problem is that recording actually record the played track, I don't think that the pjsip echo canceller is designed to solve this kind of problem but more to solve it when what is re-recorded is delayed and louder than what is emmited. I've to investigate how the pjsip echo canceller works, but I've not much hope on this side.

Summary: [Manufacturer driver] Samsung GT-I5500 : echo
Labels: -Type-Defect -Priority-Medium Type-Other Priority-Low

[Anonymous]

Originally posted by: r3gis...@gmail.com

(No comment was entered for this change.)

Summary: GT-I5500 : echo
Labels: Manufacturer-driver

[Anonymous]

Originally posted by: r3gis...@gmail.com

I've done an update that could help to debug the problem :

Could you try to install https://code.google.com/p/csipsimple/downloads/detail?name=CSipSimple_0.00-15-16.apk .

It include 3 hidden settings. To activate it :
Go in Settings > press menu and switch to "Expert mode".
Then in Settings > Media scroll to the bottom.
The 3 settings are :
Use Routing API => It enforce to use the old API that is deprecated in android 2.0. Some ROM however are based on old audio drivers but are > to 2.0. In this case activating this setting can help
Use Mode API => It enforce to use something that is actually not an API but that is considered by some manufacturer to be the way to route audio... It's a very bad idea to use that on some device cause it use mode_in_call that directly plug GSM chipset to audio hardware. But sometimes on some devices that's the only way to get routing goes through earpiece.
In Call Mode => (Useless if you use "Mode API"), Force to use one audio mode. On most device should be set to Normal. But sometimes could be interesting to test others.

Echo is maybe due to some routing problem with the micro + earpiece/speaker so worth to try.
Thanks

[Anonymous]

Originally posted by: i...@gcint.it

First of all let me say thank to you to continue taking care about this
issue.

I installed the new build as per your request and set the following:
- Use routing API -> enable
- Use Mode audio API -> enable
- Audio mode for SIP calls -> Normal (first) / MANUFACTURER_EXTRA (2nd try)

I got an excellent improvement using WiFI connection (the ones more affected
by echo at called party)
By using (Audio mode set to NORMAL) the echo is still audible even if quite
far. Using MANUFACTORER_EXTRA it seems to be no echo at all.

After that let me give to you some more details on my GT-I5500 samsung
mobile europen/italian version, so if someone match the following the above
settings can solve definitively the problem also when there is no official
possibility to upgrade the firmware due to branded devices.

- The firmware installed is:
* PDA / PHONE / CSC version JH1
* Android 2.1 update1 Build ERE27

Kindly Regards
Paolo

[Anonymous]

Originally posted by: r3gis...@gmail.com

Extremely strange :

If you enable "Mode audio API" the "audio mode" setting is not taken into account. So I guess that you were just more lucky the second try.
Actually here are interesting combination that you could try :

---
Routing API = on
Mode API = off
Audio Mode = NORMAL
---
Routing API = off
Mode API = on
Audio Mode = (not relevant since "mode api" is enabled)
---
Routing API = off
Mode API = off
Audio Mode = IN_CALL
---
Routing API = on
Mode API = off
Audio Mode = IN_CALL
--- (the default configuration)
Routing API = off
Mode API = off
Mode = NORMAL

Actually mode MANUFACTURER_EXTRA is not allowed on most devices (if actually used - mode audio api disabled- I think that you'll get nothing at all, or a crash, or it will silently fallback to NORMAL).
That's a private API for only one manufacturer that contact me directly and that has created a special and optimized mode for VoIP.

If you can just quickly test these settings and say me which is the best (try also to activate/deactivate rear-speaker to see if it correctly switch in each case).

But well sounds to be a really good news. (I think what actually solve the problem on your phone is the "Mode audio API" not sure that routing API is really needed).

So, to integrate the default settings to the source code I'll need some constant defined in the phone.
You can't get that from the android interface, but in development version there is an easy way to send me this information : Go in Help > Press record logs. Then go in help again and press stop log recording & send logs. Then you should be prompted to send trace by mail. (In these traces I put the exact device name as defined in the android system could be different of the "commercial" name)

Thanks a lot for testing that

Owner: r3gis.3R
Status: Started

[Anonymous]

Originally posted by: i...@gcint.it

Hi,

I've conducted a lot of tests and the best result was obtained using 'Mode
API' set to ON.
The volume is much higher then before both at called and caller party with
no more far voice: in one word excellent!

I found a new issue to submit about 'transfer' feature. Is this one still
under dev or should be already working ?

[Anonymous]

Originally posted by: r3gis...@gmail.com

Transfer is far to be stable yet ;).
You can follow my progress on that point on issue 305. You can add your comments but indeed, it's not yet useable for now.

For this issue, I'll add by default mode routing api to GT-I5500. So that next users will benefits of your test.

Thanks a lot for time spent testing.

[Anonymous]

Originally posted by: r3gis...@gmail.com

(No comment was entered for this change.)

Status: NextRelease

[Anonymous]

Originally posted by: fluffybu...@live.co.uk

my samsung gt i5500 wont let me on to market, i click it and it loads for a second then throws me out, ive tried taking the battery out but nothing happens. what am i suppose to do?:\