#51 Bluetooth support

[Anonymous]

Originally created by: Djonas2...@gmail.com
Originally owned by: r3gis...@gmail.com

What steps will reproduce the problem?
1.Pair and connect headset
2.Initiate a call with cSipSimple ( cSip Simple )
3.Press bluetooth button

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

My bluetooth headset should take over the audio for the call.

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

Latest version as of this issue submission.

Please provide any additional information below.

Not sure if this is an enhancement request or what, but bluetooth should work seamlessly.

[Anonymous]

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

Issue 1341 has been merged into this issue.

[Anonymous]

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

Issue 1376 has been merged into this issue.

[Anonymous]

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

With the current (CSipSimple-[r1096]-trunk.apk) version, Desire HD/stock Android 2.3 and Nokia BH-900 (not a2dp, but I guess the best headset I ever tried):

- With "Use WebRTC implementation" on:
  - Connecting BT headset does not change anything
  - Pressing on-screen "bluetooth" button does not change anything (i.e., voice RX/TX goes normally through the phone).

- With "Use WebRTC implementation" off:
  - Connecting BT headset (without pressing "bluetooth" button) immediately results in no RX/TX at all, either on phone or BT headset
  - Pressing "bluetooth" does not change anything, silence everywhere.

  - Note that as before, this "use WebRTC implementation"=off setting results in phone working as speakerphone irrespectively of "speakerphone" button setting, apparently audio is routed to speakerphone speaker in the same way for both settings, so typically I use "WebRTC".

[Anonymous]

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

What's interesting, this hardware configuration (Android 2.3/Desire HD/Nokia BH-900) works perfectly with the current Skype version -- bluetooth works fine. Which makes me think there is nothing terribly special about this configuration...

[Anonymous]

Originally posted by: ursu.adr...@gmail.com

Hello.I'm having problems with Bluetooth support. I can't hear anything and pressing the Bluetooth button doesn't help.Do I need to change some options from the app's settings menu? I have attached the logs. Thank you.

Based on the GPL CSipSimple version : 0.04-00 [r1114]
Here are important informations about Device :
android.os.Build.BOARD : GT-S5570
android.os.Build.BRAND : samsung
android.os.Build.DEVICE : GT-S5570
android.os.Build.ID : GINGERBREAD
android.os.Build.MODEL : GT-S5570
android.os.Build.PRODUCT : GT-S5570
android.os.Build.TAGS : release-keys
android.os.Build.VERSION.INCREMENTAL : XXKPF
android.os.Build.VERSION.RELEASE : 2.3.3
android.os.Build.VERSION.SDK : 10

[Anonymous]

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

Interesting: I've seen a couple of times this exact BT (Nokia BH900) on this exact phone (Desire HD)  CSipSimple working when I set "Audio Mode for sip calls to NORMAL" instead of its default IN_COMMUNICATION; this also enabled me to have normal in-call volume control _without_ enabling WebRTC option.

The problem is this usually works first time only -- after that, one toggle back/forth with Audio Mode trying to isolate its effect -- and I cannot made BT to work (or change volume without WebRTC again)... Weird :)

[Anonymous]

Originally posted by: t...@ful.net

Same issues with Bluetooth support as everyone else. Got it working on a Samsung Galaxy S II as of stable build 0.03.00 I believe. Then upgraded to the Galaxy Note (GT-N7000) and bluetooth is broken again. Tried stable builds 0.03.00 and 0.03.01, currently trying latest nightlies. None work. Here is my device profile, with logs attached. I hope you can implement a fix soon Regis for all us Galaxy Note users, thank you!

Based on the GPL CSipSimple version : 0.04-00 [r1158]
Here are important informations about Device :
android.os.Build.BOARD : GT-N7000
android.os.Build.BRAND : samsung
android.os.Build.DEVICE : GT-N7000
android.os.Build.ID : GINGERBREAD
android.os.Build.MODEL : GT-N7000
android.os.Build.PRODUCT : GT-N7000
android.os.Build.TAGS : release-keys
android.os.Build.VERSION.INCREMENTAL : XXKK9
android.os.Build.VERSION.RELEASE : 2.3.6
android.os.Build.VERSION.SDK : 10

[Anonymous]

Originally posted by: t...@ful.net

Hi Regis,

Did a little more messing around with settings in Expert mode to see if I could get audio over bluetooth working. By changing "Audio Mode for SIP calls" from "IN_COMMUNICATION" to "NORMAL", I can get the speaker to work, but the microphone still does not register. I've tested every available mic source option in Expert mode, as well as toggling and mixing all possible combinations of "Echo Cancellation", "Use WebRTC Implementation", "Use routing API", "Use Mode audio API" and "Use Samsung Galaxy Hack" and "Tone Hack" without any success.

Interestingly, microphone source also seems to effect how well the bluetooth earpiece speaker is able to function, at least when audio mode "NORMAL" is selected. "VOICE_CALL" mic source seems to be the only choice that will allow for a completely smooth listening experience. Any of the others usually cause a loss of earpiece speaker audio after just a few seconds into a call, or no audio at all.

Attached is a log file for a phone call attempted to FedEx with bluetooth headset on and paired. Audio mode "NORMAL" and mic source "VOICE_CALL". Only "echo cancellation" and "focus audio" were toggled on from the main media menu of options.

[Anonymous]

Originally posted by: t...@ful.net

Profile for the previous log:

Based on the GPL CSipSimple version : 0.04-00 [r1184]
Here are important informations about Device :
android.os.Build.BOARD : GT-N7000
android.os.Build.BRAND : samsung
android.os.Build.DEVICE : GT-N7000
android.os.Build.ID : GINGERBREAD
android.os.Build.MODEL : GT-N7000
android.os.Build.PRODUCT : GT-N7000
android.os.Build.TAGS : release-keys
android.os.Build.VERSION.INCREMENTAL : XXKK9
android.os.Build.VERSION.RELEASE : 2.3.6
android.os.Build.VERSION.SDK : 10

[Anonymous]

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

I'm getting very interesting bluetooth experience: it's working but only for a first time after start of application. After that bluetooth is silent and pressing speaker button isn't working either.
When I kill app and start it again, it works for the first call again.
Today I have updated to the last nightly build.
Phone: samsung gs2 with MIUI 1.2.30 with siyah kernel
I have reverted to factory defaults and did just couple of changes typical for this model and my network: disable tcp, change mic source to "mic", disable "focus audio" cause it was preventing both mic and earpiece from working.

[Anonymous]

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

I just changed in "expert settings"  "audio mode for sip mode" from "IN COMMUNICATION" to "NORMAL".  Everything seems to be perfect now. Xperia RAY

[Anonymous]

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

Hi Regis, I have noticed great progress with CSS and bluetooth. I've tested it with my SG II working on new android 4.0.3 connected to my car's (Mini) bluetooth system, and now it works perfect. However, I have also tested it on my Wife's HTC Sensation with our car, and it does not work at all. This probably means, some change in new android version makes a difference, but I wonder if you have made recently any changes  regarding bluetooth as well.

[Anonymous]

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

Issue 1584 has been merged into this issue.

[Anonymous]

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

Hi Regis,

I am using a Nexus One, with 2.3.6 Android. I'm trying to use CSipSimple with bluetooth and it doesn't work at all. I have installed the CSipSimple version 0.03-01 [r1108]

Thank you for your help. 

[Anonymous]

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

I just saw your comment 117 and wonder if you can give more details about it... I have a SG II also with Sprint in USA Android version 2.3.6 However I can see you have version 4.0.3 Would you mind to share how you upgraded your SG II please? What kind of car's (Mini) bluetooth sytem are you using? Is it a car manufacturer built in one? THANKS buddy!

[Anonymous]

Originally posted by: enrico.g...@gmail.com

Samsung GT-9100 (galaxy S II) updated to 4.0.3 works wonderfully with Audi bluetooth.
one minor thing (but very important for me): Csipsimple should activate bluetooth automatically when paired with the car.
say I am driving, and I want to call from the car's input mechanism, the phone does it right (hands free) but to hear something from the car's speakers I have to enable csipsimple's bluetooth feature on the screen of the telephone (by hand) thus voiding the benefits of hands free bluetooth... :-)
keep up the good work.

[Anonymous]

Originally posted by: af...@remacservices.net

Cmment #114 worked for me too. Samsung Galaxy S 4g with 2.3.7

[Anonymous]

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

@enrico : there is an option now to automatically enable bt routing. (it's in Media settings "Auto connect bluetooth" option).

@Acidhellr : thanks a lot for the tip, I'll try to enable that automatically when BT is activated. Mode IN_COMMUNICATION is normally better because it could enable the hardware echo canceller if available so for regular routing I'll try to keep the mode setup :)

[Anonymous]

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

Hello
With my eee pad transformer (ASUS tablet based on ICS) I could not use my Hands-free bluetooth headset (mono headset). The logs show this error when I enable debugging in android:
W/ActivityManager(  170): Permission Denial: broadcastIntent() requesting a
sticky broadcast from pid=2988, uid=10085 requires
android.permission.BROADCAST_STICKY
E/SIP SRV ( 2988): run task: com.csipsimple.service.SipService$1$5@4115c710
E/SIP SRV ( 2988): java.lang.NoClassDefFoundError: android/media/AudioRecord
E/SIP SRV ( 2988):     at org.pjsip.pjsua.pjsuaJNI.call_make_call(Native
Method)
E/SIP SRV ( 2988):     at org.pjsip.pjsua.pjsua.call_make_call(pjsua.java:278)
E/SIP SRV ( 2988):     at
com.csipsimple.pjsip.PjSipService.makeCall(PjSipService.java:793)
E/SIP SRV ( 2988):     at
com.csipsimple.service.SipService$1$5.doRun(SipService.java:251)
E/SIP SRV ( 2988):     at
com.csipsimple.service.SipService$SipRunnable.run(SipService.java:1774)
E/SIP SRV ( 2988):     at
com.csipsimple.service.SipService$SipServiceExecutor.executeInternal(SipService.java:1687)
E/SIP SRV ( 2988):     at
com.csipsimple.service.SipService$SipServiceExecutor.handleMessage(SipService.java:1679)
E/SIP SRV ( 2988):     at android.os.Handler.dispatchMessage(Handler.java:99)
E/SIP SRV ( 2988):     at android.os.Looper.loop(Looper.java:137)
E/SIP SRV ( 2988):     at android.os.HandlerThread.run(HandlerThread.java:60)
E/SIP SRV ( 2988): Caused by: java.lang.SecurityException: Permission Denial:
broadcastIntent() requesting a sticky broadcast from pid=2988, uid=10085
requires android.permission.BROADCAST_STICKY
E/SIP SRV ( 2988):     at android.os.Parcel.readException(Parcel.java:1327)
E/SIP SRV ( 2988):     at android.os.Parcel.readException(Parcel.java:1281)
E/SIP SRV ( 2988):     at
android.media.IAudioService$Stub$Proxy.startBluetoothSco(IAudioService.java:1090)
E/SIP SRV ( 2988):     at
android.media.AudioManager.startBluetoothSco(AudioManager.java:975)
E/SIP SRV ( 2988):     at
com.csipsimple.utils.bluetooth.BluetoothUtils8.setBluetoothOn(BluetoothUtils8.java:118)
E/SIP SRV ( 2988):     at
com.csipsimple.service.MediaManager.actualSetAudioInCall(MediaManager.java:268)
E/SIP SRV ( 2988):     at
com.csipsimple.service.MediaManager.setAudioInCall(MediaManager.java:154)
E/SIP SRV ( 2988):     at
com.csipsimple.pjsip.PjSipService.setAudioInCall(PjSipService.java:1018)
E/SIP SRV ( 2988):     at
com.csipsimple.pjsip.UAStateReceiver.on_setup_audio(UAStateReceiver.java:474)
E/SIP SRV ( 2988):     at
org.pjsip.pjsua.pjsuaJNI.SwigDirector_Callback_on_setup_audio(pjsuaJNI.java:1049)
E/SIP SRV ( 2988):     ... 10 more
W/SRS_Routing(   90): BT SCO HEAD

for info i upgraded my galaxy S2 to ICS and i have the same behaviour

[Anonymous]

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

Yes this one is known and fixed in nightly build. (google added a necessary permission to register bluetooth changes that was not granted to csipsimple).

The very last nightly build is broken, but I'm doing a new nightly. You'll be able to download it in 30minutes here (or use something prior to [r1505])

Nightlies : http://nightlies.csipsimple.com/trunk/

[Anonymous]

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

I would like to add some input here regarding Bluetooth specifically to how to relates to a Samsung Galaxy TAB (sgh-t989). In my scenario the MIC was always routed to the tablet, never to the headset (even with adjustments in advanced for mic source). It seems the headset was connected to CSS via the media path not the headset path. This is not a CSS problem, the carrier has restricted the use of the headset profile on this model. I have found in '/system/etc/bluetooth/audio.conf' my carrier (TMO) has disabled all but the A2DP profile. No matter what I have tried I was unable to get Bluetooth via CSS working until I enabled the other profiles (will require root) and rebooted. Additionally, I have also found that if you enter the settings menu on CSS the bluetooth MIC stops routing to the headset (even if you don't edit anything), and returns back to the media routing profile only. The bluetooth button is greyed out as well, until you force close CSS and restart it.  Then after the force close, CSS resumes using the headset again under the correct headset BT profile. I can re-create this every time. Build [r1629].

[Anonymous]

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

I just wanted to revise my comment above. I have confirmed the BT failure when entering settings on CSS to also exist on the Samsung Galaxy S II phone. It is not just limited to the Samsung tablet.

[Anonymous]

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

Hi there: I'm using a Motorola Atrix2, with Android version 2.3.6, with nightly build 0.04-00 [r1686] and a Motorola T225 bluetooth device.

About a heavily distorted audio when using BT: The workaround in post #51 worked well for only the first call after setting SIP Audio mode to NORMAL (instead of IN_COMMUNICATION). The next call would also have a seriously distorted sound and the only way to correct it is by redoing the workaround.

Am I doing something wrong?

Thank you / JLB.

[Anonymous]

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

Thank you for the excellent job! After the latest nightly build 0.04-00r1751 I've got my Plantronics Voyager Pro working with my rooted Galaxy S3 GT-I9300 Android 4.0.4, kenel 3.0.15-782020.

The only problem is that I have very big echo from the mic of my Voyager back to it's earpiece, so my voice is much louder than the other partys one. Played around the echo canceling, mic source and audio mode but havn't had any results. Some suggestions?

Wanted to add one more note - the call answering button of the headset doesn't function neither.

[Anonymous]

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

One more issue - when phone's BT losts pairing with the headset, SIP calls don't come in anymore (while still in registered state) until the BT is turned off from the phone.