Hi guys,
Have just installed skype but for some reason it outputs to the device loud speaker rather than the earpiece speaker. Any idea how to change this?
Cheers
I discovered the same thing - using the earplugs that come with the phone will isolate it though, and I assume a bluetooth handsfree set as well.
Bluetooth headset doesn't work for me in Skype, only the wired headset that ships with the device (which is fine).
I have used Skype on the Orbit2. It appeared the same problem and i think there is no solution at the moment. Maybe you can test it with the fring client.
I using Fring for my VOIP and output is on loud speaker as well
Does Fring work for you? The latest version always deletes my WiFi settings (does the same on my Prophet), and I have the hideous malarky of re-entering the WEP key.
yeah this is an old problem, it existed back in the day of the TyTn. It appears it's still unclear if this is a WM or Skype problem. You can use a bluetooth device if you reroute the audio using a third party application:
http://pocketpccentral.net/help/a2dp.htm
http://www.davidmays.com/blog/?postid=6
http://handheld.softpedia.com/get/Audio/BlueTooth-Audio-Today-42630.shtml
Skype forum dealing with this issue:
http://forum.skype.com/index.php?showtopic=96266&st=20
Related
Hi,
How to set up my bluetooth headset and TC to call over Skype?
Thanks!!
As far as I know, this is a software limitation of Skype, so its not possible. Although, I would think if you could somehow keep the bluetooth gateway open, Skype and bluetooth could work, but you would have to manually enable the gateway and close the gateway...
yeah, you can use BTaudio
of course you have to enable it before using skype.
It works both for audio in (hearphone) and audio out (microphone).
My SE 662 headset which I used for conferencing through http://www.rhubcom.com are also integrated with skype but there was no way to use the buttons or display on my headset to interface with skype. Now my buttons can dial people, or hangup skype not just disconnect the BT connection.
Hi all,
I have a problem with MS Voice Command 1.6.
It 'sorta' works right now ... when I press the button on my BT headset (Motorola H700) it initiates the voice command on the Treo. However, the 'beep' is played from the treo speaker, not the BT headset. When I spoke the voice command, I must also speak to the Treo mic, not the BT headset. This sucks when you are in a noisy environment.
When the call is connected, it does go through the BT headset so that's good. But it's just when you want to initiate a voice command, you have to speak to the mic on the phone. All the announcements also come through the phone's speaker only, not the BT headset.
Has anybody found a fix to this?
Thanks in advance
Try deleting the headset and reacquiring it via bluetooth. I had to do this a couple of times before this corrected
Hmmm I've done it quite a few times already ... but I can try it again.
Mine does this too. If there is no fix, I will have to go back to the at&t one.
Removing and re-adding BT headset doesn't work. After doing some more homework, it seems like the problem is Treo 750, among a # of other phones (like Hermes) uses a BT stack that is incompatible with MS's and that is the reason why.
Searching on the Hermes site there IS actually a workaround which fixes half the problem.
To make long story short, after trying to fix recommended by that site, now I can speak to the BT headset to issue voice command.
Meaning, when I press the BT headset button, I hear the VC chime from my headset, not from the phone's speaker. And when I issue voice command I also speak to the BT headset, not the phone's mic.
What it doesn't fix, is notification STILL comes through the phone's speaker and not the BT headset, even with all the correct settings under MVC.
But I'm ok with that ... I can live with this.
number16 said:
Removing and re-adding BT headset doesn't work. After doing some more homework, it seems like the problem is Treo 750, among a # of other phones (like Hermes) uses a BT stack that is incompatible with MS's and that is the reason why.
Searching on the Hermes site there IS actually a workaround which fixes half the problem.
To make long story short, after trying to fix recommended by that site, now I can speak to the BT headset to issue voice command.
Meaning, when I press the BT headset button, I hear the VC chime from my headset, not from the phone's speaker. And when I issue voice command I also speak to the BT headset, not the phone's mic.
What it doesn't fix, is notification STILL comes through the phone's speaker and not the BT headset, even with all the correct settings under MVC.
But I'm ok with that ... I can live with this.
Click to expand...
Click to collapse
you have a link to this fix???
I want to record my phone conversations when I am using my Bluetooth headset (Because I drive alot).
At the moment it is not possible to record a conversation while using the Bluetooth headset. (I don't want to use a cable headset, because I get in and out the car alot).
The problem that occurs is that when recording with windows mobile it records your own voice, but not the voice on the other side.
I have tried with many other PocketPC's but I can't find anything that works.
Try it yourself if you don't understand whta I mean.
Does anybody have a solution for me?
Thx!
Possibly the problem is that when the headset is enabled the speaker of the phone is disabled.
So if somehow the speaker keeps working even when bluetooth headset is enabled it will record the conversation on the other side.
I found that both SipDroid and 3CX Phone for Android both play the calls through the speaker and not the earpiece. Also, neither will play through the Bluetooth earpiece. I'm gussing this is a problem with the X10 since I have other friends using both without a problem on different phones.
Anyone have a work-around for this or a SIP program that does work on the X10?
Thanks
The workaround for me is to set sipdroid in speakerphone mode, this gets the audio routed to my bt headset, but I need to use the phone mic. This is the best I can do now, until my phone, a Samsung Captivate gets updated to Android 2.2.
I find that Skype uses the tablet's microphone even when a bluetooth headset is paired and audio is coming out of the headset speakers. Googling it , this seems to be a longstanding Skype bug. Has anyone found a way to get Skype to use the bluetooth headphone mic?
Thanks
Android needs to enable bluetooth mike system wide, just like in other OS.
There are other apps that can use this, not only skype.
Some of them are web based, like making calls with bobsled.
drgkt said:
Android needs to enable bluetooth mike system wide, just like in other OS.
There are other apps that can use this, not only skype.
Some of them are web based, like making calls with bobsled.
Click to expand...
Click to collapse
It's not an Android problem, per se. I use a Motorola stereo bluetooth headset that can be used for phone calls too with my Android phone with no problems on cell phone calls and Sipdroid (for VOIP). I would suspect Skype still has bugs with bluetooth, which is a fairly recent addition to their Android software. OP, the Skype forums might be your best avenue for help. There are numerous users in the Skype forum reporting problems with bluetooth using Skype.
mke1973 said:
It's not an Android problem, per se....
Click to expand...
Click to collapse
What I am trying to say is that, just like when you plug in the wired headset the sound is rerouted to the headset's earphones (disabling the device's speakers) and the microphone input is rerouted to the headset's mike (disabling the device's mike), the same should occur when the device pairs with a BT headset.
This is what happens when I pair my win xp pc to a BT headset. This way, the audio I/O change is system wide, and can be used by all apps.
Furthermore, additional settings in the device's settings screen could allow the user more control, like simultaneous use of the device's speakers and the BT earphone, (say you want to let a person next to you listen in to your conversation).
P.S. I wonder what the right place is to submit this to Android development...